What data BIM Automation Studio collects, how it's used, and your rights as a visitor or client.
BIM Automation Studio is a one-person software business operated by Eric Upshur. I build custom Revit automation tools for architecture, MEP, and design-build firms.
Questions? Email bimautomationstudio@gmail.com.
This site uses Google Analytics 4. It collects pages viewed, time on site, general location (country/city), device type, browser, and traffic source. Google anonymizes IP addresses by default. I use this to understand which content is useful. I don't identify individual visitors. You can opt out with the Google Analytics Opt-out Browser Add-on. Google's full privacy policy is at policies.google.com/privacy.
I also have Google signals turned on in Google Analytics. For visitors who are signed in to a Google account and have Ads Personalization turned on, Google adds aggregated demographic and interest data (for example, age range and general interests) and counts visits across devices. I only see these as group totals, never tied to a person, and I don't use them to show you ads. You can turn this off for your Google account at myadcenter.google.com, and see or delete the activity Google keeps at myactivity.google.com.
When you submit the contact or inquiry form on this site, I collect your name, work email address, company name, and message. This is used solely to respond to your inquiry. I don't add you to any mailing list or share your information with third parties. Inquiry data is retained as long as needed for follow-up and deleted upon request.
I don't set any first-party cookies. Google Analytics sets its own cookies to track sessions and page views. See Google's Cookie Policy for details. No other tracking cookies are used on this site.
If you're a paying client using my pyRevit buttons or MCP tools, my license management system collects operational data from your workstations. This collection is required for license enforcement, seat management, and usage analytics. A full technical disclosure is available on request, and every client gets a copy before setup.
| Data Type | What Is Collected | Why |
|---|---|---|
| Identity | Windows username, computer hostname, client ID (your license key is sent with each request but never logged) | License seat enforcement; prevent duplicate seat claims |
| Application | Revit version number, process IDs | Multi-instance support; releasing a seat when a Revit window closes or crashes; compatibility tracking |
| Session | Session start/end timestamps, heartbeat signal (every 10 min), session status | Automatic seat release after inactivity; seat availability |
| Usage | Names of tools/scripts executed | Usage analytics; product improvement; client ROI reporting |
| License | Seat limit, seats in use, seat claim/release events | Enforce license agreement; real-time seat availability |
| Billing | Subscription status, seat count, billing contact email, Stripe customer and subscription IDs | Turn tool access on or off and match the seat limit to your subscription |
| Extension | BIM Automation Studio version number | Support, troubleshooting, update notifications |
License and session data is stored in Google Sheets and Google Apps Script (all US-based Google infrastructure). Your subscription status and seat count are copied from Stripe to the license sheet once an hour. All data is transmitted over HTTPS (TLS 1.2+).
A small signed seat file is also kept in your local Windows temp folder (%LOCALAPPDATA%\Temp\). It expires within 72 hours and is replaced every 10 minutes while Revit is open. No background process runs on your computer.
Active session records are deleted when the session ends. Event logs (tool usage, errors) are deleted automatically after 90 days. Upon subscription cancellation, account and configuration data is deleted within 60 days. You may request immediate deletion at any time by emailing bimautomationstudio@gmail.com.
My MCP system connects your Revit model to Claude, Anthropic's AI assistant. When you type a command in Claude Desktop, your prompt goes to Anthropic's servers. The MCP server runs locally on your machine, reads only what your question needs from Revit, and passes that result back to Claude. That means the information in the result (for example element names, categories, and parameter values) goes to Anthropic's servers along with your prompt. Your .rvt file and model geometry stay on your machine.
How Anthropic handles your prompts and conversation data depends on which Claude plan you're using:
I don't control how Anthropic processes your data. If your firm needs a DPA or has GDPR requirements, Claude Team or Enterprise is the right fit. Email me if you want to talk through which plan works for your setup.
I don't sell your data or use it for advertising.
Depending on where you're located, you may have the following rights:
To exercise any of these rights, email bimautomationstudio@gmail.com.
If you're in the EEA, GDPR rights apply. I process client data on the basis of legitimate interest in operating a licensed software product. EU clients can request a Data Processing Agreement (DPA); I handle those on a per-client basis.
California residents have the right to know what I collect, request deletion, and opt out of the sale of personal information. I don't sell personal information.
All data transmitted between my software and Google's servers is encrypted in transit (HTTPS / TLS 1.2+). Payments go through Stripe, which is PCI-DSS compliant. I never see or store your full card details.
No system is perfectly secure. If you have a specific security concern, email bimautomationstudio@gmail.com.
I may update this policy as my practices change. The "Last updated" date at the top of this page reflects the most recent revision. Active clients will be notified by email before any material changes take effect.
For any privacy questions or requests, email bimautomationstudio@gmail.com. I respond within 30 days.
