Privacy policy

Effective date: {{EFFECTIVE_DATE}}

Working draft. Highlighted {{markers}} are details still to be filled in before this page is final. The substance of the policy already applies.

This policy explains what personal data BIMIO ("we", "us") processes, why, and your rights. BIMIO is a suite of add-ins for Autodesk Revit.

Data controller: {{LEGAL_NAME}} · {{ADDRESS}} · Tax ID {{TAX_ID}} · contact {{CONTACT_EMAIL}}.

1. Summary (the short version)

2. What we process, why, and on what legal basis

(a) Anonymous product usage telemetry

What: a random install identifier (a GUID, not linked to you); which tool was opened and whether it ran or was blocked by your licence; session start/end and duration; app and Revit version (and build); operating system, .NET runtime and language; coarse environment buckets (e.g. RAM/CPU tier, whether the project is workshared, project-size band); licence state (trial/active) and licence lifecycle events; and — if it fails — an error type with a scrubbed stack trace (file paths and user names removed). We never collect model, project or element data, file names, model paths, machine name, or the client IP as an identifier. Why: to understand which features are used, fix crashes, and prioritise the roadmap. Legal basis: legitimate interest (GDPR Art. 6(1)(f)). Our balancing test is on file. The data is pseudonymous and you may object/opt out at any time.

(b) Licence and purchase data

What: your e-mail, licence key, activation device identifier, and purchase details. Why: to sell, deliver, activate and validate your licence and provide support. Legal basis: performance of a contract (Art. 6(1)(b)).

(c) Feedback you send

What: anything you write in the in-app feedback form (rating + note), plus the version/Revit context. Why: to receive and act on your feedback. Legal basis: legitimate interest / your submission.

We keep the usage telemetry store and the licence/identity store separate — they share no common key, so usage is never tied to a named person.

3. Sub-processors

We use these providers, who process data on our behalf under their own data- processing terms:

ProviderPurposeData
LicenseSeatLicence issuance & validationlicence key, e-mail, device id
Lemon Squeezy (merchant of record)Payments, invoicing, EU VATpurchase data, e-mail, billing
PostHog (EU region)Product-usage analyticspseudonymous telemetry events
SentryCrash/error reportingscrubbed error reports
Google Apps Script / SheetsFeedback + optional raw telemetry archivefeedback text, telemetry events

(Update this list to match what you actually enable. Remove providers you don't use.)

4. Retention

5. International transfers

We prefer EU-hosted providers (e.g. PostHog EU). Where a provider processes data outside the EEA, it does so under an adequacy decision or Standard Contractual Clauses.

6. Your rights

You may request access, rectification, erasure, restriction, portability, and object to processing based on legitimate interest (including telemetry — or just use the in-app opt-out). Contact {{CONTACT_EMAIL}}. You may also lodge a complaint with your supervisory authority (in Spain, the AEPD, www.aepd.es).

Because telemetry is pseudonymous and holds no identifier we can link to you, we may be unable to locate "your" telemetry for an access/erasure request without additional information from you — the simplest remedy is the in-app opt-out.

7. Local storage on your device

BIMIO stores small functional files on your device under %AppData%\FJV\ (settings, a DPAPI-sealed licence record, a random telemetry install id). These are first-party and functional; no advertising or cross-site tracking is used.

8. Turning telemetry off

About → Legal & privacy → untick "Share anonymous usage…". Organisations can disable it fleet-wide via the BIMIO_TELEMETRY=off environment variable or a %ProgramData%\BIMIO\telemetry.off file.

9. Children

BIMIO is a professional tool, not directed at children.

10. Changes

We may update this policy; the effective date above changes accordingly. Material changes will be surfaced in-app.