Privacy Policy
Last updated: 25 August 2026
What the add-ins send
Parapet apps never upload your Revit models or project data to us. (If you choose to link a Google Sheet, the data you select moves directly between your computer and Google under your own Google account; we are not in that path.) When you start a trial, register a free app, activate, or during periodic license check-ins (about every 12 hours while Revit is in use) the add-in sends: your license key, a one-way hash derived from your Windows machine identifier and user name (never the name itself), a pseudonymous device label derived from that hash (so your account's device list can tell two computers apart), Revit version, add-in version, Windows version, and your IP address (received by our server). Your computer's hostname and your Windows user name are not sent. This is used solely to enforce seat limits and detect abuse. Add-in builds before 1.10.1 sent the computer name and Windows user name as the device label; if a device in your account still shows one, deactivating and re-activating that computer replaces it with the pseudonymous label.
When you share an audit
Sharing an audit from Parapet Audit is an explicit action - nothing is uploaded until you press Share, and a dry-run popover shows what the page will contain first. The shared page at parapet.app/a/<id> contains exactly what the report shows: the findings and per-file checks, health scores and counts, the model title, and the names of external files - their full folder paths only if you pick "Full paths" instead of "File names only". Where your model records who created or last changed an element (Revit worksharing usernames), those names can appear inside findings, because they are part of the audit data you review in the grid before sharing. What is never uploaded: geometry, the model itself, or your Windows user name. Free shares are visible to anyone who has the link (the address is unguessable and the page is not indexed); Audit Pro can make an audit private. You can delete a shared audit at any time from your audits.
What the website stores
When you subscribe we store your email, name (if provided to Stripe), license keys, subscription status and Stripe customer/subscription identifiers. Card details are handled entirely by Stripe; we never see them. We use Google Analytics to measure site traffic; we do not use advertising trackers and we do not sell or share your data with advertisers.
When you download
Downloading the installer or a portable ZIP asks for your email address, which we verify with a one-time code and store with the download. Each download (including automatic updates, which need no email) is logged so we can see how many people are using Parapet and which Revit versions to support. We record the file, the time, your IP address, the approximate location and network operator Cloudflare derives from it (country, region, city, and the organisation that owns the connection), your browser and operating system as reported by your browser, the page or search that referred you, and any campaign tags in the link. After the download starts you can optionally tell us your role and company; both questions are voluntary and skipping them changes nothing. We do not set a cookie to do this. Download logs are kept for 24 months.
When you ask about a pilot
The pilot form sends us what you type: your email address, and optionally your firm, your country and a note about what you want looked at. If you paste a link to a shared audit into the form, we record which audit it points at, so we can look at the right page before replying - nothing attaches an audit to your enquiry unless you include one. We also record when you asked, which page the form was on, and - when you arrived through a link with campaign tags - those tags and the page they landed on. A salted hash of your IP address is kept to spot abuse of the form; we do not store the address itself. The form is a work list for us to reply to, nothing more: it is not a mailing list, we do not add you to one, and nothing automated emails you as a result of filling it in. Ask us at support@parapet.app and we will delete your enquiry.
Signing in
Signing in to parapet.app uses a 6-digit code sent to your email address - there is no password, so we never store one. A successful sign-in leaves one cookie (pp_s) holding a random token; we store only a one-way hash of that token, together with the date, a salted hash of your IP address and your browser's user-agent string, so you can review and end your sessions. Sessions last 30 days and you can end all of them at once from your account. The cookie is strictly necessary to keep you signed in and is not used for tracking or advertising.
Teams
If your practice uses a Parapet Team, the team record stores its name, the seat count, and for each member their email address, role and the date they joined. Team admins can see the member list and roles; they cannot see another member's license key. Audits, sheets and link run history created while you are on a team are recorded against the team as well as against you, so they remain available to the firm if you leave. Invitations store the invited email address until they are accepted, revoked, or expire after 14 days.
Transactional email only: license keys, payment and renewal notices, replies to support requests.
Retention and deletion
License records are kept while a subscription is active and for up to 3 years afterwards for accounting. Sign-in sessions expire after 30 days and are deleted when you sign out. Team invitations expire after 14 days. Shared audits and Parapet Sheets are kept until you delete them, subject to the per-model limits described on their pages. Email support@parapet.app to request deletion; we remove everything not legally required to keep. If you are on a team, work recorded against the firm is deleted on the team owner's request rather than an individual member's.
Infrastructure
Cloudflare (website, API, database) and Stripe (payments). Data may be processed in the United States and the European Union.
Contact
support@parapet.app