Legal
Security
What fishline.ai does to keep your account, photos and data safe. Every line on this page describes what our code and our server setup do today.
Effective October 9, 2026
No system is perfectly secure, and we won't pretend ours is. This is what we actually do. What we collect and why is in the Privacy Policy.
1. Your account and sign in
- Passwords are stored only as a bcrypt hash. Nobody at fishline.ai can read your password.
- Signing in gives your device a long random token. Our database keeps only a SHA 256 hash of it, so a copy of the database can't be used to sign in as you.
- On your phone the token is kept in the iPhone Keychain or Android's encrypted storage, never in plain app settings. On the web it sits in a cookie that the page's scripts can't read.
- One account has one session. Signing in somewhere new signs out the old one, resetting your password signs you out everywhere, and deleting your account ends every session.
- Sign in, sign up and password reset are rate limited, so passwords and codes can't be guessed at speed.
- If you use Sign in with Apple, the token Apple gives us is stored encrypted, and we revoke it at Apple when you delete your account.
2. Your photos
- Every photo you upload is decoded and saved again on our server as a brand new image. Location, camera details and any other hidden data in the file are gone before it is stored or sent anywhere.
- Stored photos get a random 32 character name, with nothing from you in it, and live in our cloud storage, not on the web server itself. The one exception is a photo waiting to be measured: it is kept, already cleaned, on our API server for up to 2 hours and deleted if it is never measured.
- The fishline.ai app for iPhone and Android takes the GPS position and other hidden data out of a photo file before uploading it, so it does not leave your phone in the file.
3. Data on the move
- The app, the web app and the websites talk to our servers only over HTTPS (TLS). Our API tells browsers to use HTTPS only, for a year at a time (HSTS).
- Our server talks to its database over TLS, using the database's own certificate authority.
- The keys for measuring and screening live only on our API server. The app and the websites never talk to an AI company directly, so no key can be pulled out of them. The one exception is our team's model testing tool, which runs in our admin dashboard on Vercel and holds its own OpenRouter key there.
4. Our servers and database
- The database is a managed MySQL cluster that accepts connections only from our API server, over the private network.
- The API server accepts only web traffic and SSH, through a cloud firewall and its own firewall. SSH takes keys only (no passwords, no root login), and repeated failed attempts are blocked automatically.
- Security updates for the operating system and PHP install automatically.
- Passwords and keys for our services are kept out of our code, in encrypted secret storage, and are written to the server only when we deploy.
- Queued jobs that carry an email address, such as taking you off our email lists, are encrypted while they wait.
5. Payments
- We never see or store card numbers. App purchases go through Apple or Google, and website purchases through Stripe's own payment form.
- Before a plan is turned on we check the purchase ourselves: Apple's signed receipt and Apple's servers, or Google Play's servers. A purchase can't be faked from the app.
6. Who can see your data
- Only our small team can use our admin tools. Admin sign in is locked for an IP address after 5 wrong passwords in 15 minutes.
- We look at messages only when one is reported to us, or when you write to our support team.
- Words and photos people post for others to see are checked automatically for abuse before they are saved.
7. Backups
- Our database host keeps daily backups for 7 days, so we can recover from a failure.
- Other server files are backed up every night, encrypted on the server before they leave it, to a key whose private half is kept offline. Those backups are kept for 30 days.
- Our host also takes a weekly backup of the whole API server and keeps the last 4. It holds what is on that server's disk, such as the server logs, and stays inside our hosting account.
8. Reporting a security problem
Found a security problem? Email nate@rackline.ai with "Security" in the subject and enough detail for us to reproduce it. Please don't access or change other people's data, don't run tests that slow the service down, and give us a fair chance to fix it before telling anyone else. We will not take action against research done in good faith under these rules, and we will tell you when it is fixed.