Security

This page says what protects a Fire Trajectory account today, in plain terms, and how to tell us if you find a problem. It lists what is built, not what is planned; the last section says what is coming next.

1 Your sign-in

• Passwords are stored as salted hashes by Supabase Auth; nobody at Fire Trajectory can read them. When you choose a password, our server checks it against the Have I Been Pwned list of leaked passwords, sending only the first five characters of a hash, never the password itself or anything that identifies you.
• Two-factor authentication is available under Settings › Security with any authenticator app. Once it is on, sensitive actions such as changing what your account can reach require the second factor again, enforced by the database, not only by the app.
• Sign in with Apple, Google or Microsoft hands the password step to that provider; we receive your name, email address and a provider account identifier, nothing else.
• Sign-in history and Sign Out Others under Settings › Security show recent sessions and end every session except the one you are using.
• Sign-in answers the same way whether or not an address has an account, and repeated attempts are rate limited, so an attacker cannot use the sign-in form to learn who uses the Service.

2 Your data

• In transit, every connection uses HTTPS (TLS). At rest, the database and uploaded files live on Supabase infrastructure on AWS, which encrypts stored data.
• Row-level security in the database means each signed-in account can reach only its own rows. The browser holds a public key that can do nothing without a signed-in session; the elevated key exists only in server functions and is never sent to a browser.
• Partner Mode shares only the areas you turn on, and you can turn any of them off or dissolve the household at any time. The household activity record is readable by household members only and is written by the server only.
• Deleting your account under Settings › Security asks for your password and then removes your profile, planner data, uploads, household membership, activity and consent records in one sweep.
• Exports are yours to download at any time, on every plan, under Settings › Export Data, so your data is never locked in.

3 Payments

We do not ask for card numbers anywhere on the Service today. When online billing launches, a payment processor will handle card details on its own pages; card numbers will never be sent to or stored on Fire Trajectory servers.

4 Reporting a problem

If you believe you have found a security issue, email support@firetrajectory.com with “Security” in the subject. Please include the steps to reproduce it, and do not access other people’s data while testing. We aim to acknowledge reports within three business days, we will not take legal action against good-faith research that respects other users’ privacy, and we will credit you if you would like that. We do not run a paid bounty program.

5 What is coming next

• Daily database backups on a paid database plan before online billing opens.
• Bank connections only after a dedicated security review of how connection tokens are stored and rotated.
• Changes to this page are dated at the top; the Privacy Policy covers what we collect and why.