This page lists every cookie that flashfixpro.com and FlashFix set, and what else they keep in your browser. In short: we use only what the website and the app need to work. We do not use advertising or analytics cookies, and nothing listed here follows you to other websites.
Our privacy notice explains how we use personal data more widely.
What a cookie is
A cookie is a small file that a website asks your browser to keep, so that the website can recognise that browser on the next page or the next visit. Browser storage does a similar job: a page keeps a few settings in the browser itself. The same rules apply to both, so both are listed here.
Why we do not ask you to accept cookies
A website needs your consent before it stores anything on your device, unless that thing is needed for something you have asked the website to do. Everything on this page is of that kind: signing you in, keeping forms secure, or remembering a choice you made. So there is nothing for you to accept or reject. If we ever want to use a cookie that is not needed in that way, we will ask you first and add it to this page.
Cookies we set
FlashFix itself sets all of these. None of them is passed to another company, and none is used to show adverts or to measure visits. Most are set only once you sign in.
| Cookie | What it is for | How long it lasts |
|---|---|---|
| .AspNetCore.Identity.Application | Keeps you signed in | Until you sign out or close the browser, and no longer than 12 hours. If you tick "Remember me", up to 30 days |
| Identity.TwoFactorUserId | Holds your place between your password and the second step of signing in, and while you sign in with a passkey | 5 minutes |
| Identity.TwoFactorRememberMe | Set only if you tick "Remember this machine": lets this browser skip the second step of signing in next time | 14 days |
| .AspNetCore.Antiforgery | Proves that a form was sent from our own page, which protects your account against forged requests. Its full name ends in a short code | Until you close the browser |
| Identity.StatusMessage | Carries a one-off message to the next page, such as a note that your password was changed | 5 seconds |
| flashfix-nav-rail and flashfix-nav-folded | Remember whether you collapsed the side menu, and which of its sections you folded | 1 year |
| flashfix-mfa-dismissed | Remembers that you put away the reminder to set up two-step sign-in | Until you close the browser |
What else is kept in your browser
| Where | What is kept | Why |
|---|---|---|
| flashfixpro.com | Whether you chose the light or the dark theme, and that you have put the cookie note away | So the website looks the way you left it, and the note is not shown to you again |
| FlashFix, once you sign in | Your theme and accent colour | So the app looks the way you left it |
| Surveys | A survey prepared for a visit with no signal, until it has been sent back to FlashFix | So a surveyor can work with no connection |
| The home visualiser | The photo in use and the products placed on it, until the tab is closed | So stepping back to the picture does not lose the work |
| Help chat | A reference to your open conversation | So the conversation is still there when you come back |
The theme choices, the cookie note and the visualiser's working copy stay in your browser and are not sent to us. A survey is sent to FlashFix when the surveyor sends it back, and the help chat's reference is sent when you reopen the chat.
Files your browser fetches from other companies
To show its pages, FlashFix fetches a few files, such as typefaces and map tiles, straight from other providers. Those providers receive your device's IP address and browser details. They are listed in our privacy notice.
How to control cookies
You can delete or block cookies in your browser's settings, and clear what a website has stored. If you block our cookies you can still read flashfixpro.com, but you will not be able to sign in to FlashFix. Deleting them signs you out and resets the choices above.
Changes to this page
When we add, change or remove a cookie, we update this page and publish it with a new version number and date.