Welcome to BIM Monkey! By using our website, you consent to our use of all cookies per the privacy policy.

BIM Monkey BIM MONKEY
  • Capabilities
    Sheet & viewport automation Dimension placement Drawing audits Custom skills & live scripting Model memory Firm training Redline reviews Vicinity maps Code checks Site data
    Platform
    Workflow integration API access Agent access
  • By firm size
    Solo / 2-person Growing firm (3+) Enterprise & multi-office
    By workflow
    Construction documents Design development Permit & CA
  • Security
  • Pricing
  • Install guide How it works Videos Release notes API reference Agent access Blog About Contact us
  • Sign in

Privacy Policy

Last updated: July 6, 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. When you log in, we derive your approximate country and city from your IP address using a local geolocation database. This is used for service analytics only and is not shared 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.
  • Amazon Web Services — drawing page images are stored in BIM Monkey's S3 storage (United States) by default. On the Pro and Enterprise plans, firms using customer-hosted data residency store drawing images in their own storage bucket instead, and this default storage does not apply to them. Subject to AWS's Privacy Notice.
  • 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.
  • Nominatim (OpenStreetMap) — project addresses entered in the Parcel Data, Zoning, Permit History, and Site Climate tools are geocoded using Nominatim, OpenStreetMap's free geocoding service, to convert addresses to coordinates. No account or API key is required; queries are made to the public Nominatim endpoint. Subject to OpenStreetMap Foundation's Privacy Policy.
  • OpenStreetMap Overpass API — when the Digitize Footprint tool is used, the project address coordinates are sent to the OpenStreetMap Overpass API to retrieve building footprint polygons. No account or personal data is transmitted beyond the coordinates. Subject to the OpenStreetMap Foundation's Privacy Policy.
  • Regrid — when configured, project addresses entered in the Parcel Data tool may be forwarded to Regrid's API to retrieve parcel IDs, lot areas, and coordinates. Nominatim is used as a fallback when Regrid is not configured. Subject to Regrid's Privacy Policy.
  • Stripe — payment processing and subscription management. Subject to Stripe's Privacy Policy.
  • RapidAPI — when the property analysis feature is used in Banana Chat, a property ID or address is forwarded to RapidAPI to retrieve listing photos and property features from third-party real estate data providers. This data is used solely to assist with as-built documentation in Revit. Subject to RapidAPI'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.

Private AI (Enterprise plan). When Private AI is enabled, AI inference does not use Anthropic's shared API. Instead, Claude models run inside your firm's own cloud tenancy — your AWS account via Amazon Bedrock, or your Google Cloud project via Vertex AI — under credentials your firm supplies and controls. In that configuration, AWS or Google Cloud acts as a processor selected and contracted by your firm, not as a BIM Monkey sub-processor, and drawing content sent for AI processing stays within your firm's cloud tenancy. Inference charges are billed by your cloud provider directly to your firm. Your firm may disable Private AI at any time from Settings, which returns AI processing to Anthropic's API as described above.

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. International data transfers

BIM Monkey is a United States company. Our servers and database are hosted in the United States (AWS us-east-2), and our sub-processors listed in Section 3 — including Anthropic, Stripe, Clerk, and Autodesk — process data in the United States. If you access the Service from outside the United States, your information will be transferred to, stored, and processed in the United States, which may not have data protection laws equivalent to those of your home jurisdiction.

Where applicable — for example, for users in the European Economic Area, the United Kingdom, or Switzerland — we rely on our sub-processors' own data processing agreements, which incorporate Standard Contractual Clauses (SCCs) or an equivalent recognized transfer mechanism, to safeguard these international transfers. Contact [email protected] for a copy of the safeguards applicable to a specific sub-processor.

Customer-hosted data residency. Firms with data-locality or data-sovereignty requirements can configure BIM Monkey to store their firm's data — scripts, skills, generations, corrections, project data, and drawing images — in a database and storage bucket the firm provisions and controls, in a region of the firm's choosing (for example, a database in the firm's own cloud account). When customer-hosted data residency is active, that firm's data is stored in the firm's infrastructure rather than on BIM Monkey's US infrastructure. Account, login, billing, and anonymous usage telemetry remain on BIM Monkey's US infrastructure. AI processing uses Anthropic's API by default; on the Enterprise plan, Private AI additionally moves AI inference itself into the firm's own cloud tenancy (see Section 3). Configure both in Settings → Data Residency.

8. Legal basis for processing (EEA/UK users)

If the GDPR or UK GDPR applies to you, our legal bases for processing your personal data are: performance of a contract (to provide the Service you signed up for); legitimate interests (to secure, maintain, and improve the Service, and to prevent fraud and abuse); consent (for optional website analytics and marketing cookies, which you may withdraw at any time as described in Section 1); and legal obligation (where we must retain or disclose information to comply with applicable law).

9. Additional rights for EEA, UK, and Swiss residents

In addition to the rights described in Section 6, if you are located in the European Economic Area, the United Kingdom, or Switzerland, you have the right to: access, correct, or erase your personal data; restrict or object to our processing of your personal data; receive your data in a portable format; and withdraw consent at any time where processing is based on consent. You also have the right to lodge a complaint with your local data protection supervisory authority.

BIM Monkey Incorporated has not yet formally designated a representative in the European Union under Article 27 of the GDPR. Until a representative is designated, please direct any EU/UK/Swiss data protection inquiry to [email protected] and we will respond directly.

10. Additional rights for California residents

If you are a California resident, the California Consumer Privacy Act (CCPA), as amended, gives you the right to: know what categories of personal information we have collected about you in the preceding 12 months (see Section 1 for the categories we collect); request deletion of your personal information; correct inaccurate personal information; and opt out of the "sale" or "sharing" of personal information. BIM Monkey does not sell or share your personal information, as described in Section 2. We will not discriminate against you for exercising any of these rights. To exercise any California privacy right, email [email protected].

11. 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.

12. Changes to this policy

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

13. Contact

Questions? Email us at [email protected].

Product

Capabilities Platform App

Solutions

Construction docs Design development Permit & CA

Resources

Install guide How it works Videos Release notes API reference Agent access Blog

Company

About Security Pricing [email protected]
© 2026 BIM Monkey Incorporated Terms of Service  ·  Privacy Policy