Privacy Policy
Last updated: 7 July 2026
Who we are
AllAddin is operated by MeliUX Ltd, a company registered in England and Wales. When this policy says "we", "us", or "our", it means MeliUX Ltd.
What we collect and why
| Data | When | Why | Lawful basis |
|---|---|---|---|
| Email address, optional note | You submit the waitlist form | So we can get in touch about access | Consent (you clicked the button) |
| IP address, user-agent string | Every request to our server | Rate limiting, spam prevention, security | Legitimate interest |
| Your Revit prompt (natural-language text) | You send a command via the add-in | To generate a response from the AI model | Contract performance |
| A structured abstraction of your model context | With each prompt | Gives the AI enough context to write working code | Contract performance |
| Token hash, request timestamps, token counts | Each API call | Usage tracking, rate limits, abuse prevention | Legitimate interest |
| Prompt, generated code, and execution outcome (improvement corpus) |
After a turn completes, unless you have turned it off.
To turn it off, set share_tricks = false under
[privacy] in
%APPDATA%\AllAddin\alladd.ini. Administrators can
disable it for a whole install with
suppress_background_egress = true in the same
section.
|
Reviewing what worked and what failed so the assistant improves. Identifying fields (file path, document title, worksharing username, project name/number) are redacted by default before any of this leaves your machine. Your original prompt is kept only against your own account and is never shared into the pooled corpus other people retrieve from. | Legitimate interest (improving the product; you can object at any time using the setting above) |
| A published dashboard workspace (share link) | Only when you explicitly publish a share link ("Share Workspace") from a dashboard. | So a recipient can open a frozen snapshot of the dashboard you chose in a browser. The payload is AES-256-GCM encrypted on your device before it is uploaded and stored as ciphertext only in an EU-jurisdiction Cloudflare R2 bucket. It auto-expires (30-day default), is revocable by you at any time, and is hard-deleted on disable or expiry. Never the underlying Revit file itself. | Consent (you clicked Share) |
| Snapshot of your Revit model metadata (legacy upload) | The dashboard snapshot-upload button was removed in July 2026. This row covers snapshots uploaded by earlier versions, which always required an explicit click. (Publishing a share link, above, is a separate, encrypted path.) | Cross-time analytics, diff reports, and team dashboards. Contains element identifiers, categories, levels, and the parameters you selected when capturing the snapshot. Never the underlying Revit file itself. | Consent (you clicked upload) |
What we do NOT collect
- We do not collect your Revit files, drawings, or BIM models. Your files stay on your machine.
- We do not upload your model automatically. The only time model-derived data leaves your machine is if you explicitly publish a share link (see the table above) - and even then it is encrypted on your device first and we store only ciphertext. The legacy dashboard snapshot-upload button was removed in July 2026.
- We do not use cookies, third-party tracking pixels, or third-party analytics.
- We do not share or sell your data to advertisers.
- We do not use your prompts or model metadata to train AI models, and your content is contractually excluded from training by both of our AI providers (Anthropic and Mistral).
Server-side page-view logging
We log aggregate page-view statistics server-side for the alladdin.dev website (not the AllAddin add-in). No cookies, no JavaScript beacons, no tracking pixels: a server-side middleware records one row per HTML page render with the URL path, response status, referrer host, and UTM source if present. Your IP address and user-agent string are not stored in plaintext; they are hashed with a daily-rotating salt (for unique-visitor counts) and a two-hour-rotating salt (for sessionising consecutive pageviews). Those hashes are not persistent identifiers and cannot be used to track you across days or devices. Bots (Googlebot, GPTBot, LinkedInBot, etc.) are detected from the user-agent string and flagged so we can separate crawler traffic from human traffic in our dashboards.
Sub-processors
The current list of third-party services that process personal data on our behalf is on our live sub-processor register. Each sub-processor operates under its own Data Processing Agreement, which includes UK/EU Standard Contractual Clauses (SCCs) or an International Data Transfer Agreement (IDTA) covering transfers outside the UK. The DPA link for each provider is on the register.
How long we keep it
- Waitlist entries - kept until you ask us to remove them, or until we contact you and you decline.
- Audit logs (request timestamps, token usage, IP address) - automatically pruned after 90 days. The audit row stores a one-way hash of your prompt, not its text.
- Security events (failed auth, rate-limit hits) - automatically pruned after 90 days.
- Prompts sent to the AI - the request body is not stored by us beyond the API call. Both Anthropic and Mistral run on zero-data-retention for our account, so neither keeps your prompt once the response is returned, and neither uses it to train models.
- Improvement-corpus submissions (prompt, generated code, outcome - only if you opted in via "Share tricks") - retained as part of our guidance corpus; they do not expire automatically. Email us to have your submissions deleted at any time.
- Published share-link payloads - stored as ciphertext for the link's lifetime and hard-deleted the moment you disable the link or it expires (30-day default).
- Snapshots (uploaded by earlier versions) - automatically deleted after 365 days, or earlier if you email us a deletion request.
Your rights
Under UK GDPR you can:
- Access - ask what data we hold about you.
- Erasure - ask us to delete your data.
- Portability - ask for a machine-readable copy of your data.
- Object - object to processing based on legitimate interest.
- Complain - file a complaint with the Information Commissioner's Office (ICO).
To exercise any of these, email us at hello@alladdin.dev with "Privacy request" in the subject line. We will acknowledge within 7 days and respond in full within 30 days.
Changes to this policy
We may update this policy as AllAddin evolves. Material changes will be posted here with an updated date. We will not reduce your rights without notice.