Security & data handling

Every customer's data lives in its own separate database

Not a shared table with a "which company" column -- a genuinely separate database file per customer, on its own private path. If a competitor of yours also uses FixTrove, there is no shared table for a bug to ever leak your data into theirs, because your queries never open their file in the first place.

• Physically separate storage -- each customer's manuals, repair history, and account data live in their own database file, not merged rows in a shared one.
• Resolved by your own subdomain -- your login always points at your own data; there's no shared "pick your company" list for anyone else to browse.
• No cross-customer admin view -- your own admin sees your facility's data and usage only, never another customer's.

Real accounts, not a shared password

Every technician signs in with their own account. Login is required across the entire app, on every device -- there's no way to browse a facility's manuals or repair history anonymously, even if someone finds or guesses the URL.

• Passwords are never stored -- only a salted, one-way cryptographic hash (PBKDF2, 200,000 rounds per attempt). Nobody at FixTrove, including your own admins, can ever see a technician's real password.
• One active session per person -- signing in on a new device automatically signs a personal account out everywhere else, so an old device or a shared login can't quietly stay logged in.
• Sessions expire automatically -- 12 hours by default, up to 30 days only if "stay signed in on this device" is checked.
• Resetting a password revokes every active session -- a device that's still logged in doesn't keep working right through a reset.

Encrypted in transit, backed up off-site

• HTTPS everywhere -- every connection to FixTrove, on every subdomain, is encrypted end to end.
• Daily off-site backups -- copied to a second, independent cloud provider separate from primary hosting, so an issue with one provider is never the only place your data exists.
• Backed up one customer at a time -- restoring your data is never a whole-server rollback that touches anyone else's.

Payments never touch our servers

Card details are entered directly on Stripe's own hosted payment page during checkout. FixTrove never receives, sees, or stores your card number -- Stripe is a company built specifically to handle that securely, so this app doesn't have to.

Who else processes data, and why

A short, honest list of every outside service FixTrove relies on -- nothing runs anywhere else.

• Anthropic (Claude) -- receives your troubleshooting questions and the relevant excerpts of your own uploaded manuals, in order to generate guidance.
• Stripe -- processes subscription payments; see above.
• Resend -- delivers account emails (password resets, login links) to the address on file.
• Cloudflare R2 -- stores your encrypted off-site backup copy.
• Render -- hosts the application and your facility's primary database.

Found a security issue?

If you find a security problem with FixTrove, we want to hear about it directly, before anyone else does. Email contact@suguiq.com and mention that it's a security report -- a real person reads every message, and we'll follow up directly.