- Home
- Trust and data
Trust and data
Your model stays yours.
ClashFree runs inside Revit on your PC. Your model, your clash reports and your project, file, user and machine names never leave it. Here is exactly what does, where it goes and how to stop it.
Your PC
- The Revit model and its links
- Clash reports (Navisworks XML, BCF)
- Project, file, user and machine names
- Your coordination profile and decisions log
- Your Anthropic API key, encrypted for your Windows user
- Replay inputs for support, only on disk
of the clashstraight from
your PC
Your AI provider
- Both runs, sizes, systems and fittings in millimetres
- Free space, nearby obstacles and walls
- The scored options and the profile entries
- Your chat message, if you revise
- Billed to your API key, or to your own Claude plan over MCP
and scrubbed recordsbeta only
ClashFree beta server
- Usage analytics: counts and codes (imports, proposals, keeps, rejects, flags, timings, token counts and cost). A condition of the beta.
- Scrubbed diagnostics: error types and hashes.
- Clash content: scrubbed Keep and Reject records, on by default, off in Settings.
- Your activation: a random install id, a hash of your invite code, your e-mail, version, dates.
The full list of fields is in the beta data terms; website and sign-up data are in the privacy policy.
Never collected
What we do not want, and do not take.
Clash content records are scrubbed on your PC before they are sent: names become short hashes, paths and identifiers are removed, and anything that looks like a project, file, user or machine name is replaced.
- Your Revit modelNo geometry file, no RVT, no NWC, no export of it.
- Your clash reportsNot the XML, not the BCF, not their titles.
- NamesNo project, file, user, machine, level or room names in clear.
- Your API keyIt goes only from your PC to your AI provider.
- ScreensNo screenshots or snapshots of your model.
- Selling or advertisingData is used to improve ClashFree, never sold, never shared beyond our hosting and e-mail providers.
Your model, your call
Five rules the add-in never bends.
They are built into the code path every fix takes, from the pane's AI, the queue and Claude alike.
1 · The AI never outputs coordinates
It picks a strategy from a fixed list with millimetres, degrees and a direction, and explains why. Deterministic code builds the geometry.
2 · Nothing is committed without you
Every fix runs in one Revit transaction group: preview, verify, then Keep as one undo step, or Reject and the model is restored exactly.
3 · Links and other trades are read-only
They are obstacles, never targets. When the right fix is theirs, the clash is flagged for a person with the reason.
4 · Units are converted at the edge
Revit works in feet internally; ClashFree's logic and the AI work in millimetres, converted once at the boundary.
5 · Revit is never blocked
AI calls run in the background; model changes happen only on Revit's main thread, through Revit's own event mechanism.
And: no engineering claims
A fix lists what an engineer must re-check (airflow, hydraulics, falls, firestops). ClashFree never says it is fine.
Your controls
See it, stop it, delete it.
Everything is in the pane's Settings. You do not need to write to us, though you can.
- 1
See what is sent
Settings › Usage › "Open queue folder" shows the exact events waiting on your PC before they go.
- 2
Stop clash content
Turn clash content sharing off in Settings, or answer No when a Reject asks.
- 3
Delete server data
Settings › Beta › "Delete my data on the server" deletes every event, diagnostics file, clash content record and the activation record of your install at once, and stops sending.
- 4
Uninstall
Uninstalling offers to remove ClashFree's local data. Your e-mail and trial dates are kept so a trial is not restarted, and deleted on request to [email protected].
Security
How the beta is protected.
A small surface, kept small on purpose: the add-in talks to your AI provider and to one ClashFree endpoint, over HTTPS.
Signed tokens
Each install gets a token signed with HMAC on activation by e-mailed code. Tokens expire with the trial and are renewed by the server, never minted on your PC.
Protected sign-up and admin
The sign-up is rate-limited and checked by Cloudflare Turnstile. The admin console sits behind Cloudflare Access, closed to everyone but the team.
Your key stays local
Your Anthropic API key is stored encrypted for your Windows user and is never logged or sent to ClashFree.
Scrubbed before sending
Diagnostics and clash content are scrubbed on your PC: names hashed, paths and identifiers removed, strings allow-listed.
Release builds
Release builds compile out every developer command, are obfuscated, and carry a beta expiry. Installers are code-signed once our certificate is in place; until then Windows may ask you to confirm the publisher.
Per-user install
The installer needs no administrator rights and installs only into your user profile and the Revit versions you tick.
Questions about data?
Ask us anything.
We would rather answer a hard question before you install than after.