Privacy
Privacy Policy
Last updated 14 November 2026
Insight FastPass is run by Dom Trip Code ("we"). This page says what information the site collects, what we do with it, and what we do not. It is written from what the site actually does rather than from a template.
The short version: we keep what you need to have an account, we count how the site is used without identifying who is using it, and we do not sell your information or share it with advertisers. There are no advertising or social-media trackers on this site, and we do not send marketing email.
Your account
When you create an account, we store:
- your first and last name, and the display name made from them
- your email address
- your password, as a salted hash - the password itself is never stored, and it is encrypted in your browser before it is sent
- when the account was created and last used, and whether it is active
To confirm it is you, we email a six-digit code when you sign up, sign in or reset your password. The latest code for each purpose is stored against your email address as a keyed hash, not as the code itself. It stops working after 15 minutes or five wrong tries, and works once. A copy of every email we send - the address, the subject and the message, with any code removed - is kept for 90 days as a record that it was sent.
The site does not accept file uploads yet. When it does, this page will say how uploaded spreadsheets are stored before that goes live.
Your answers about the full release
If you answer "What would you need from the full release?", we store your answers against your account: the plan that would suit you, whether you would use live connections, where you would work, when you would start, anything you write in the free-text box, whether we may email you when it launches, and whether you answered on the website or in the desktop app. Saving them also adds your vote to the community topic about the full release. You can change or remove your answers at any time, and deleting your account removes them.
Cookies and browser storage
- When you sign in, the site sets one cookie: a session cookie that keeps you signed in while you keep using the site, for up to 90 days between visits and never more than 180 days in all. It is httpOnly, so scripts on the page cannot read it, and it is removed when you log out.
- Your browser also keeps a small flag saying whether you were signed in, so the site knows whether to check your session when it loads. It holds nothing else.
- A random visit identifier is kept in session storage, as described below. It is gone when you close the tab.
What the site records as you use it
When the site loads, your browser makes up a random identifier for the visit. It is kept in your browser’s session storage - not in a cookie - and it is gone when you close the tab. Nothing connects one visit to your next one, or to your account. Against that identifier the site records:
- which pages you open, and which sign-up and log-in buttons you press
- that the sign-up form was started or sent, and which plan it was opened from - not what was typed into it
- that a row was saved in the write-back demo - not the values; those never leave your browser
- the page you arrived on and the address of the page that linked you here - both without anything after a question mark - and any campaign tags on that link
- your browser’s user-agent string, the size of your browser window, your timezone and your browser’s language
We use this to see whether the site is doing its job: which pages are read, where people leave, and whether a change helped. It is looked at in aggregate.
What the site does not do
- It does not store your IP address. Your address is used for about a minute, in memory, to stop automated requests flooding the site, and is never written down.
- It carries no advertising, no advertising or social-media tracking pixels, and no third-party analytics service.
- It does not fingerprint your device or try to recognize you across visits or across other websites.
- It does not send marketing or newsletter email. The only emails are the codes described above.
Who else is involved
We do not sell, rent or trade your information, and we do not give it to advertisers or data brokers. Two companies are involved in running the site, and handle information only as part of doing that:
- Microsoft Azure hosts the site, its database, its file storage and its outbound email. Like any hosting provider it keeps its own operational and security logs of the requests it serves, which can include IP addresses.
- Google Fonts supplies the typefaces. Your browser fetches them from Google’s servers, so Google receives the request - your IP address and browser details - as it would for any site that uses them. No information from this site is sent with it.
We would disclose information if the law required it. If the business were ever sold or merged, accounts would pass to the new owner under the terms on this page.
How long it is kept
Your account is kept until you delete it, from your settings or by asking us. Deleting it removes your password, your name, your phone number and any pending codes at once. Your email address stays attached to your account’s identifier, so that anything shared with the address is there again if it ever registers again; email us and we remove the address entirely as well.
Verification codes are replaced each time a new one is sent and stop working after 15 minutes or five wrong tries. Records of sent emails are kept for 90 days. Visit records carry nothing that identifies you and are kept as usage statistics.
Your choices
Email Dtripodi@DomTripCode.com to ask what we hold about you, to have it corrected, or to have your account deleted. We will do it, and tell you when it is done. Depending on where you live you may have further rights under your local privacy law - to object to or restrict how your information is used, or to complain to your data-protection authority - and nothing here limits them.
Closing the tab ends the visit identifier, and your browser’s own settings can block session storage entirely - the public pages work without it. Signing in needs the session cookie.
Security
The site and its API are served over HTTPS. Passwords are encrypted in your browser before they are sent and stored only as a salted hash, signing in needs a code sent to your email, sign-in attempts and the public endpoints are rate limited, and sessions end after 180 days at the most. No method of storing or sending information is perfectly secure, and we cannot promise that yours never will be exposed - but we will tell you if we learn that it has been.
Children
The site is not directed at children and we do not knowingly collect information from them.
Changes to this page
If what the site does changes, this page changes with it and the date at the top moves. Questions about any of it: Dtripodi@DomTripCode.com.
See also the Terms of Service.