Havsala is one person's project, not an advertising business. This page says exactly what leaves your phone, where it goes, and what we have chosen not to build.
Last updated 3 October 2026
The text of your stories is not among it. It is written to your own device — the phone's app storage, or your browser's storage on the web — and is not copied to us.
What we do keep, about your account:
Passwords are handled by Supabase, our authentication provider, and are stored hashed. We never see them. Like any sign-in service, Supabase also keeps a record of sign-ins for security.
Because sagas live on your device, we cannot restore them for you. Deleting the app or clearing its data removes them — unless your phone backs up app data to your Google account (Android's own backup), in which case a reinstall can bring an older copy back. That copy is yours and Google's, never ours.
A story has to be written and read aloud somewhere. Those steps need computers we do not keep in your pocket, so data travels — and this is the whole list.
→ Supabase (authentication), in the EU (Frankfurt)
So that an account exists. Supabase also holds the daily request count and the sign-up details listed above.
→ our server (on Cloudflare) → Z.ai (GLM), in China
To write the next chapter, the model needs the story that precedes it. Requests pass through our own server, which checks your sign-in, counts the request and attaches our API key; your account is never identified to the model.
→ our narration server
To turn it into a voice. This machine is ours, in Türkiye, reached through Cloudflare. Audio is returned and not retained.
→ our illustration server
To draw the chapter's picture. Also ours, also in Türkiye. The finished picture stays on this server, at an unguessable link the app loads it from; it carries no account, so it cannot be traced back to you.
→ Google Play and RevenueCat (subscriptions), in the US
Google Play takes the payment; RevenueCat keeps the record of what you subscribed to, so our server can tell which plan you are on. Your account ID is a random identifier, not your email.
→ Sentry, in the EU (Germany)
When the app hits an error it sends what broke, the app version, your phone's model and system version, and a random identifier the crash reporter makes for this installation — not your account. Story text, wishes and anything you typed are kept out: the app never logs them, a test fails the build if a line tries to, and error text is filtered before it leaves.
→ Sentry, in the EU (Germany)
Only when you use Send feedback: your message, your email so we can reply, the app version, your phone's model and system version, and a short technical trail of the screens you visited just before. Nothing from your sagas.
Text sent for writing is processed by Z.ai, whose service runs outside Türkiye and outside the EU. If you would rather your writing did not cross a border, the honest answer is that Havsala is not able to offer that today, and you should not use it for anything you consider confidential.
This is not a list of intentions. The application contains no code for any of it — no analytics library, no advertising SDK, no third-party tracker of any kind. The one third-party reporter it does contain is the crash reporter above, and it reports errors, not behaviour.
On Android, Havsala asks for no permission you are prompted for — no camera, microphone, location, contacts or files. What it declares is network access, audio playback settings, keeping narration playing when the screen is off, Google Play billing, and vibration.
Your account details and the daily request counts are kept until you delete your account. Your subscription record is kept by RevenueCat until then too, and by Google Play for as long as Google must keep purchase records. Crash reports and feedback are kept by Sentry for its retention period, at most 90 days. The chapter pictures stay on our illustration server; they carry no account, so they cannot be looked up or deleted by account.
Your account: in the app, tap your profile picture at the top of the library, scroll to Account and tap Delete account. It works the same in your browser at app.havsala.app if you no longer have the app and signed up with email — sign in and do the same (how). That deletes, at once, your account and everything held with it: email, Google name and picture, sign-up details, the daily request counts, and your subscription record at RevenueCat. It also clears that account's sagas from the device you do it on. It does not cancel a Google Play subscription — cancel that in Google Play first.
If you would rather not, write to [email protected] from the address you signed up with and it will be done within seven days. Feedback you sent is deleted from Sentry on request, found by your email; crash reports carry no account and expire on their own.
Your stories: delete any saga from its menu in the app. Its cached narration stays on the device until you clear the app's storage in Settings, or delete the app and its data (see the note on Android's own backup above).
Havsala writes fiction for adults and is not directed at children. We do not knowingly hold an account belonging to anyone under 13.
If what we collect ever changes, this page changes with it and the date at the top moves.
Havsala is run by İsmail İbiloğlu. Questions, complaints and requests all go to the same place: [email protected].