Legal

Privacy Policy

What data BIM Automation Studio collects, how it's used, and your rights as a visitor or client.

Last updated: June 30, 2026  ·  Applies to bim-automation-studio.github.io and all BIM Automation Studio software products

1. Who We Are

BIM Automation Studio is a one-person software business operated by Eric Upshur. I build custom Revit automation tools for architecture, MEP, and engineering firms.

Questions? Email bimautomationstudio@gmail.com.

2. Data Collected From Website Visitors

Google Analytics

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.

Contact Form

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.

Cookies

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.

3. Data Collected From Software Clients

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. Full technical details are available upon request.

What I never collect: File names, file paths, project names, model content or geometry, passwords, clipboard data, screen captures, or web browsing activity. My tools run within your Revit environment and do not access or transmit any project data.
Data Type What Is Collected Why
Identity Windows username, computer hostname, client ID License seat enforcement; prevent duplicate seat claims
Application Revit version number, process IDs Multi-instance support; 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
Extension BIM Automation Studio version number Support, troubleshooting, update notifications

Where This Data Is Stored

License and session data is stored in Google Sheets, Google Forms, and Google Apps Script (all US-based Google infrastructure). All data is transmitted over HTTPS (TLS 1.2+).

Temporary session state files are also created in your local Windows temp folder (%USERPROFILE%\AppData\Local\Temp\) and deleted automatically when Revit closes.

Data Retention

Active session records are deleted when the session ends. Event logs (tool usage, errors) are retained for analytics and compliance. 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.

4. AI Processing: MCP Tools and Claude

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 you asked for from Revit, and passes that back to Claude. Your files, geometry, and project data never leave your machine.

How Anthropic handles your prompts and conversation data depends on which Claude plan you're using:

  • Claude Free / Pro (Consumer Terms): Anthropic may use conversation data to train their models unless you opt out. See Anthropic's Privacy Policy and their data training FAQ for opt-out instructions.
  • Claude Team / Enterprise (Commercial Terms): Includes a Data Processing Addendum (DPA), no training on your data, and Standard Contractual Clauses (SCCs) for EU transfers. See Anthropic's DPA page.

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.

5. Third-Party Services

  • Google Analytics (Google LLC, US): Website traffic analytics. Privacy Policy
  • Google Sheets / Forms / Apps Script (Google LLC, US): License management and event logging for software clients. Privacy Policy
  • Stripe (Stripe, Inc., US): Payment processing. PCI-DSS compliant. I never see or store your full card details. Privacy Policy
  • Anthropic (Anthropic, PBC, US): AI processing for MCP tool users. Data handling depends on your Claude plan; see Section 4. Privacy Policy

I don't sell your data or use it for advertising.

6. Your Rights

Depending on where you're located, you may have the following rights:

  • Access: Request a copy of the data I hold about you.
  • Correction: Request correction of inaccurate data.
  • Deletion: Request deletion of your data, subject to any legal retention requirements.
  • Portability: Request your data in a machine-readable format.
  • Objection: Object to processing based on legitimate interests.
  • Withdrawal of consent: Where processing is based on consent, withdraw it at any time.

To exercise any of these rights, email bimautomationstudio@gmail.com.

EU / GDPR

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 / CCPA

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.

7. Security

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.

8. Changes to This Policy

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.

9. Contact

For any privacy questions or requests, email bimautomationstudio@gmail.com. I respond within 30 days.