On your phone
- The session token lives in the phone's secure storage — Keychain on iPhone, Keystore on Android — never in plain files, and never in a place the web view can read.
- Journal pages are encrypted on the device with a key held in secure storage. Without the phone unlocked, the pages are not readable as text.
- Screen Time and Usage Access data stays on the phone. On iPhone, Apple gives the app an opaque token; the names of the apps you block and the time you spend in them never reach us. The shield is drawn by Apple's own extension.
- Health data is read on the device, only when you open the screen that shows it, and only what you allowed.
- The app's files are excluded from iCloud and Android auto-backup where they hold private content, so a backup does not quietly copy your journal.
On the way
Everything the app sends goes over HTTPS with TLS 1.2 or newer. The app refuses a plain-HTTP API in a production build, and it pins no third-party analytics into the request path.
On our servers
- Data is encrypted at rest by the platform that stores it.
- Passwords are hashed with a modern, salted algorithm. We cannot read them.
- Tokens and keys are held as secrets, not in the source, and are rotated when someone with access leaves.
- Access to production data is limited to the people who need it to run the service, and is logged.
- Every request is authenticated, rate limited, and scoped to the account that made it. A deleted or replaced session stops working at once.
AI messages
Your message and the context needed to answer it are sent from the app to Floe's own server, and from there to the model provider for that one turn. The provider is listed on the subprocessors page.
- Journal pages, mood check-ins and blocked-app data are not sent.
- Your messages are not used to train models.
- A reply is Markdown text. It is stored as text and rendered as text — it cannot run code, load a script, or reach anything the app did not allow.
- Deleting a thread deletes it from the active store.
Your account
Use a unique password, and a passkey or a password manager where you can. Sign in with Apple and Google never give us your provider password. If you think someone else has your session, sign out on that device and change your password; every other session is closed when you do.
Report a problem
If you find a security problem, write tohi@arisyn.studio withSecurity in the subject. Tell us what you found and how to repeat it. Please do not test it on someone else's account, and give us a reasonable time to fix it before telling anyone else.
We will confirm we received it, keep you updated, and credit you if you want to be named. We do not pursue someone who reports a problem in good faith.
What we never ask for
- Your password, in an email or a message.
- A one-time code, or a screenshot of one.
- Your card number. The store handles payment, not us.
- Remote access to your phone.
If a message asks for one of these, it is not from Arisyn Studios. Send it to us so we can warn others.