Security
What we do to keep your company’s information safe, and how to tell us about a problem.
- Reporting a vulnerability
- How and where we store your data
- Encryption
- Signing in
- Protecting your account
- How FaultFinder uses AI
- API keys
- Security headers
- Cookies
- Your information
- If something goes wrong
- FAQs
Reporting a vulnerability
Found a security problem? Tell us privately at [email protected] with SECURITY in the subject, or through the support form. Please give us reasonable time to fix it before telling anyone else. Our contact is also published at /.well-known/security.txt.
How and where we store your data
- FireSeq runs on a dedicated server in Sydney, Australia. Your records, photos and documents are stored there.
- The database is backed up every night, and each backup is checked before it is kept.
- A few services outside Australia handle limited information for us: Cloudflare (network security and protection from attacks), Resend (sending our emails) and Anthropic (the AI integrated into FaultFinder, which receives only what you type into FaultFinder and the matching extracts from the FaultFinder database). See the privacy policy.
- The services behind FireSeq are not reachable from the internet. Only Cloudflare can reach our web server, and it has to prove itself with a certificate to do so.
- Each company’s records are kept apart in the database itself, not only by the app, and each company has its own web address that works only for its own people.
Encryption
- Every connection uses HTTPS with TLS 1.2 or higher, and browsers are told to use nothing else (HSTS).
- Authenticator app secrets, site access codes and webhook secrets are encrypted at rest with AES-256-GCM.
- Passwords are stored only as argon2id hashes with a server-side pepper. Invite, setup and reset links are stored only as a hash, and the secret part of each link never reaches a server log.
Signing in
- Sessions are short: the access part lasts 10 minutes and the rest is replaced every time it is used. If an old one is ever used again, that whole session is signed out.
- Sign-in cookies are httpOnly, Secure and SameSite, so the page’s own scripts cannot read them.
- Two-step sign-in with an authenticator app (Google Authenticator, Microsoft Authenticator, Authy and others) is available to everyone, with recovery codes.
- Sensitive changes, such as bank details, adding an owner or creating an API key, ask for your password or authenticator code again.
- Passwords must be at least 12 characters, and cannot be a common password or be made from your email or company name.
- Every change checks that it came from FireSeq’s own pages, which blocks cross-site request forgery.
Protecting your account
- Sign-in, password resets, invites, setup links and the API are rate limited.
- An account locks for a while after repeated wrong passwords. Devices already signed in keep working, so nobody can lock you out of your phone by guessing.
- Sign-ins, failed sign-ins and changes are logged. Owners and admins see their company’s log under Settings, Activity.
How FaultFinder uses AI
- FaultFinder receives only what a technician types or picks for a fault: the panel, the fault code or display text, and the question. It does not receive your client list, pricing, invoices or other company records.
- When a technician writes a service report from FaultFinder, it also receives the site, task number, technician’s name, visit date and notes for that report.
- Questions are processed by Anthropic under its commercial terms. Your questions and answers are not used to train its models.
- One company’s FaultFinder chats are never shown to another company. Only short fault labels and counts per panel are shared across companies, as common issues.
- Chats are kept with your company’s records so you can look back at what was suggested. Archiving hides a chat but does not delete it.
- FaultFinder gives guidance only. Always follow the manufacturer’s instructions, the relevant Australian Standards and your own professional judgement.
API keys
- Keys are made with cryptographically secure randomness, shown once, and stored only as a hash.
- A key can be revoked at any time and stops working at once. Creating one asks for your password or authenticator code again.
Security headers
Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy are set on every page of the app and of this site, and server version details are hidden.
Cookies
The app sets only the cookies it needs to keep you signed in. This site sets none and loads nothing from anyone else. There are no advertising or analytics cookies and no third-party trackers.
Your information
- Owners can download everything their company has in FireSeq, every table and file, at any time from Settings, Company.
- You can ask for your login and personal details to be deleted on the delete my account page.
If something goes wrong
If a data breach affects your information, we will tell affected customers by email within 72 hours of confirming it, and report it to the Office of the Australian Information Commissioner where the Notifiable Data Breaches scheme applies.
FAQs
Email [email protected].