Privacy Policy

Last updated: May 25, 2026

This Privacy Policy describes how BIM Monkey ("we", "us") collects, uses, and shares information when you use the BIM Monkey service ("Service"). By signing up, you agree to this policy.

1. Information we collect

Account information. When you sign up, we collect your name, firm name, and email address.

Billing information. Payments are processed by Stripe. We do not store your credit card number, CVV, or bank details — those are held by Stripe under their own Privacy Policy. We store your Stripe customer ID to link your account to your subscription.

Drawing and project data. When you upload drawings or run generations, we store page image renders, AI analysis data, Revit model summaries, and generation history. See Terms of Service §2–4 for a full description of what is stored, how it is used, and your right to delete it.

Usage and technical data. We collect server logs, error reports, and aggregated usage metrics (features used, sheets generated, error rates) to operate and improve the Service. This data is not linked to individual users externally.

Plugin usage metadata. When you use the BIM Monkey Revit plugin (including the Banana Chat panel), we collect anonymous usage metadata: which Revit tools were called, how long each call took, whether it succeeded, and session frequency. We also collect message length (character and word count) when you send a message to Banana Chat. We do not collect the text content of your messages or any project-specific data through this channel. This metadata is used solely to understand product usage patterns and improve reliability.

Workflow signals. The WorkflowObserver component of the Revit plugin collects architectural workflow events during your sessions: which views you activated, how long you spent in each view, what categories of model elements were modified (e.g. walls, doors, windows), and session start and end times. These events are uploaded to BIM Monkey's servers at session end and used exclusively to synthesize firm-wide working standards for your account. They are not shared with other firms and are not used for advertising.

Autodesk Construction Cloud (ACC) data. If you connect your Autodesk account via the Integrations page, we store your Autodesk OAuth access and refresh tokens, your Autodesk user ID, and the ACC hub and project you link to your account. When your linked project syncs, we retrieve and store a model snapshot containing element counts by category (rooms, doors, windows, walls, levels, floors) and associated properties from the AEC Data Model. This data is used to provide model context to Banana Chat and is stored under your firm account. Disconnecting your Autodesk account from the Integrations page deletes all stored tokens and model snapshots.

Site data queries. When you use the Parcel Data, Permit History, Site Climate, Zoning Data, or EPD search tools in the Revit ribbon, the project address or keyword query you enter is sent to BIM Monkey's servers and forwarded to third-party data providers (Regrid for parcel records; city and county open data portals for permit history; Open-Meteo ERA5 for climate data; Building Transparency for EPD carbon data; Zoneomics for zoning data). These queries are logged for service reliability but are not stored in your drawing library.

Local storage. We store your BIM Monkey API key in your browser's localStorage to keep you logged in. We use browser localStorage rather than HTTP cookies for session state. During installation, the installer saves your Anthropic API key to a local configuration file on your machine (~/.claude/settings.json); BIM Monkey does not transmit or store this key on its servers.

Website analytics and consent (bimmonkey.ai only). When you visit bimmonkey.ai, a consent banner gives you the choice to accept or opt out of analytics tracking. If you click Accept: a stable anonymous visitor ID (bm_vid) is stored in your browser's localStorage to recognize your browser across sessions; Google Analytics 4 may be loaded to collect standard page metrics (pages visited, session duration, device type, and approximate country); and the LinkedIn Insight Tag may be loaded to measure conversions from LinkedIn advertising campaigns. If you click Opt out: no visitor ID is generated, any existing visitor ID is deleted, and no third-party analytics scripts are loaded. Your consent choice is saved in your browser's localStorage under the key bm_cookie_consent. To withdraw consent at any time, clear localStorage for bimmonkey.ai in your browser settings.

Google Drive data. If you choose to import a PDF from Google Drive, we request read-only access to that specific file. We access only the file you select — we do not access your full Drive, contacts, email, or any other Google account data. The selected file is downloaded to your browser and processed identically to a file you upload directly. We do not store your Google account credentials or any Google user data beyond the PDF content of the file you chose to import, which is stored as described under "Drawing and project data" above.

2. How we use your information

To create and manage your account.
To process subscription payments through Stripe.
To power AI-assisted generation personalized to your firm's drawing standards.
To send transactional emails — account creation, subscription receipts, trial reminders, and service notices.
To improve platform reliability and develop new features using aggregated, non-identifiable metrics.
To respond to support requests.

We do not use your data for advertising. We do not sell your data to third parties. We do not use your firm's drawing content to train shared AI models or improve output for any other firm. Your project data is never used to train other users' accounts. See Terms of Service §3.

When you save a correction in Banana Chat, the text of that correction is sent to Claude Haiku (via Anthropic's API) to classify it as a permanent workflow rule or a plugin-version-specific workaround. This classification is stored in your firm account and used to personalize future generation sessions.

3. Third-party processors

We share data with the following processors solely to operate the Service:

Anthropic — page image renders are sent to Anthropic's API for AI analysis when you upload drawings. Generation sessions also call the Claude API directly from your machine. Correction classification calls are made to Claude Haiku via Anthropic's API. Anthropic does not train on API data by default. Under Anthropic's standard API terms, inputs and outputs may be retained for up to 30 days for trust & safety review, after which they are deleted. Anthropic does not use your firm's drawing content to improve its models for other customers. Anthropic is SOC 2 Type II certified. Enterprise Zero Data Retention (ZDR) agreements — where no data is stored beyond the time needed to process each request — are available directly from Anthropic for firms that require them. Subject to Anthropic's Privacy Policy.
Autodesk Platform Services (APS) — if you connect your Autodesk Construction Cloud account via the Integrations page, your OAuth access and refresh tokens are stored on BIM Monkey's servers to enable ongoing ACC model data access. Model element data retrieved from your linked ACC project is stored as a model snapshot. Subject to Autodesk's Privacy Statement.
Building Transparency — EPD keyword searches entered in the EPD search tool are forwarded to the Building Transparency EC3 API to retrieve material carbon data. Subject to Building Transparency's Privacy Policy.
Clerk — user authentication and account management. Account credentials, session tokens, and identity data are processed by Clerk. Subject to Clerk's Privacy Policy.
Cloudflare — DNS, CDN, and network security. Web traffic to bimmonkey.ai is proxied through Cloudflare's network for DDoS protection and performance. Subject to Cloudflare's Privacy Policy.
Dropbox — optional Dropbox integration for importing PDF files. When you use the Dropbox Chooser, Dropbox's OAuth service is used to authenticate you. We request only access to the file you select. We do not receive, store, or transmit your Dropbox account credentials. Subject to Dropbox's Privacy Policy.
Google — optional Google Drive integration for importing PDF files. When you use the Drive Picker, Google's OAuth 2.0 service is used to authenticate you. We request only the drive.readonly scope, limited to the file you select. We do not receive, store, or transmit your Google account credentials. Subject to Google's Privacy Policy.
Google Analytics 4 — if you consent to analytics on bimmonkey.ai, Google Analytics 4 is loaded to collect page-view data (pages visited, session duration, referrer, device type, and approximate country). IP addresses are anonymized before processing. Subject to Google's Privacy Policy.
LinkedIn — if you consent to analytics on bimmonkey.ai, the LinkedIn Insight Tag is loaded to measure conversions from LinkedIn advertising campaigns. LinkedIn may collect data about your visit for ad measurement. Subject to LinkedIn's Privacy Policy.
Loops — transactional email delivery (signup confirmations, API key emails, account notifications). Your email address is shared with Loops solely to send these messages. Subject to Loops's Privacy Policy.
Microsoft — optional OneDrive integration for importing PDF files. When you use the OneDrive file picker, Microsoft's OAuth service is used to authenticate you. We request only access to the file you select. We do not receive, store, or transmit your Microsoft account credentials. Subject to Microsoft's Privacy Statement.
Municipal open data portals — project addresses entered in the Permit History tool are forwarded to city and county open data APIs (across 13 supported cities) to retrieve permit records. These are public government APIs.
Netlify — web frontend hosting.
Open-Meteo (ERA5) — project addresses entered in the Site Climate tool are forwarded to Open-Meteo's API, which serves ERA5 climate reanalysis data, to retrieve design temperatures, climate zone, and related data. Subject to Open-Meteo's Terms.
Railway — backend API and database hosting. Data is stored on Railway's infrastructure.
Regrid — project addresses entered in the Parcel Data tool are forwarded to Regrid's API to retrieve parcel IDs, lot areas, and coordinates. Subject to Regrid's Privacy Policy.
Stripe — payment processing and subscription management. Subject to Stripe's Privacy Policy.
Zoneomics — project addresses entered in the Zoning Data tool are forwarded to Zoneomics's API to retrieve zoning designations and land use data. Subject to Zoneomics's Privacy Policy.

We do not share your personal data or drawing content with any other third parties.

4. Google user data

BIM Monkey uses the Google Drive API solely to allow you to import a PDF drawing set from your Google Drive into the BIM Monkey upload flow. Our use of Google user data complies with the Google API Services User Data Policy, including the Limited Use requirements.

Data accessed. When you use the Google Drive import feature, we request drive.readonly access limited to the specific file you select in the Google Picker. We do not access any other files, folders, contacts, email, calendar, or Google account data.
Data usage. The selected PDF file is downloaded directly in your browser and submitted to BIM Monkey's upload pipeline — identically to a file you upload manually. It is used solely to analyze your firm's drawing standards and improve AI-generated construction documents for your account.
Data sharing. The PDF content is sent to Anthropic's API for AI analysis as part of the normal upload process. It is not shared with any other third party and is not used to train shared models.
Data storage and protection. Processed drawing data is stored in our Railway-hosted PostgreSQL database. We use encrypted connections (TLS) for all data in transit. Access to the database is restricted to our backend API service.
Data retention and deletion. Google Drive–imported drawing data is retained as long as your account is active, under the same policy as all other uploaded drawing data. You may delete individual projects from the dashboard at any time. To delete your entire account and all associated data, email [email protected].
Google credentials. We never receive, store, or transmit your Google account password or refresh tokens. OAuth tokens are used only in-browser during the file selection session and are not persisted to our servers.

5. Data retention & deletion

We retain your account information and drawing library for as long as your account is active. You may archive or delete individual projects at any time from the dashboard. To delete your entire account and all associated data, email [email protected]. See Terms of Service §4 for full details on deletion timelines.

6. Your rights

You may request access to, correction of, or deletion of your personal data at any time by emailing [email protected]. We will respond within 30 days.

7. Data isolation

Your project data is never used to train other users' accounts. Each firm's drawing library, approved examples, and generation history are strictly isolated to that firm. BIM Monkey does not share one firm's data with another firm under any circumstances.

8. Changes to this policy

We may update this policy. We will notify you by email at least 14 days before material changes take effect.

9. Contact

Questions? Email us at [email protected].