Privacy Policy
Privacy Policy
Last updated
The short version.
- Your journal lives on your device. The app's screens read and write a local database on your phone, never the network directly. When you have a connection, that database syncs to a server we operate so your other devices can catch up.
- If an entry carries a location, that location syncs too. We do not claim your coordinates never reach us — when you attach a location to an entry, its latitude and longitude travel with it, the same as its text and photos. See "Location" below for exactly what that does and doesn't mean.
- Signing in gives us the email address and account ID your Qavren sign-in provides. We never see or store a password — Qavren Auth handles that.
- No analytics, advertising, or crash-reporting code ships in the app. There is no email capture on this website.
- You can permanently delete your account and everything in it from inside the app. See deleting your account.
This policy covers the Talebound mobile app and this website, both operated byQavren Solutions. Talebound is not yet available on the App Store or Google Play. If something below changes before or after launch, we'll update this page and change the date at the top.
How the app works, in brief
Talebound is offline-first: a local database on your phone is what every screen reads from and writes to, and it works with no connection at all. When you're back online, that database syncs — your writing is sent to our server and merged with anything your other devices wrote, so all of your devices end up with the same journal. If the same entry was edited in two places before they could sync, we keep both versions rather than silently discarding one.
You don't need an account to read what's already on your phone. An account, via Qavren Auth, is what lets your entries sync to another device.
What we collect
Your account
Talebound uses Qavren Auth (built on Keycloak) for sign-in — authorization-code sign-in with PKCE, the same technique your browser or bank app uses, never a form where the app itself sees a password. Signing in gives our server your email address and an opaque account identifier (a UUID). That identifier, not your email, is what every journal, entry, and photo you create is tied to on our server. Talebound's own database has no password of yours to lose, because it never has one.
Qavren Auth is shared across every app Qavren Solutions operates. Its own account system is not scoped to this document; what we're describing here is whatTalebound does with the identity it's handed.
What you write
Journals and entries — their text, or a voice note if you use that entry type — and any photos, videos, or audio you attach. If an entry carries a location, its latitude, longitude, and (when available) elevation. All of this is what syncs to our server so it can reach your other devices; see "Location" below for the specifics on coordinates.
Your photos
Photos and other media you add to an entry are uploaded straight from your device to our storage — Cloudflare R2 — using short-lived, single-use upload links our API hands out. Our own servers never receive or hold the bytes of your photo; they only track that the upload happened and where it lives.
Location
Talebound touches location in two different ways, and they behave differently. Being precise here matters more than being reassuring.
Camera-roll backfill (finding your trips) is entirely on-device. When you point Talebound at your photo library, it reads each photo's existing timestamp and GPS coordinates and clusters them into candidate trips. To title a cluster with a real place name, it looks the coordinates up against agazetteer of place names bundled inside the app itself — a static dataset, not a network call. Nothing about this step leaves your phone, and a clustered trip is a draft: it stays local and is never synced unless you explicitly keep it.
An entry's own location does sync. Once you keep a trip, or write an entry with a location attached, that entry's latitude and longitude are part of the entry itself — the same as its text — and they sync to our server along with everything else, so the entry looks the same on your other devices. Our server stores that coordinate. The product also has a server-side step that can look up a human-readable place name for an entry's coordinates using a geocoding service; if that lookup runs for your entry, the coordinates involved are the ones you already synced, not a new location we independently gathered.
We do not run any location tracking that operates independently of an entry you wrote — there is no background service reporting where your phone is, and no location data is collected outside of what's attached to your own journal content.
What we don't collect
No analytics SDK, no advertising SDK, and no crash-reporting SDK ship in the app. We don't build a behavioral profile of you, we don't sell or rent your data, and we don't participate in any ad network. We don't ask for or use your contacts, microphone, or calendar. This website has no email capture, no newsletter, and no third-party trackers.
Who else is involved
We keep this list as short as we can. Today it is:
| Who | What they handle |
|---|---|
| Qavren Solutions | Operates Talebound's API, its share of the shared Qavren database, and Qavren Auth. Talebound is one of several apps on this shared infrastructure. |
| Cloudflare | R2 object storage for your photos, videos, and audio, uploaded directly from your device. Cloudflare also hosts this website. |
Both are service providers acting on our behalf. We don't sell your personal information, and we don't share it for advertising.
How long we keep things
Your account data stays until you delete it — seedeleting your account. Our servers keep ordinary operational logs (things like request timestamps and, sometimes, your account ID) so we can debug problems and keep the service secure; we don't use them to build a profile of your behavior.
One record deliberately survives deletion. When you delete your account, we keep a bare audit row recording that your account ID was deleted and when — nothing else. Exactly what that row is for, and what it doesn't do, is spelled out on the account deletion page.
What's shared, and what's shared identity means
Your journal is private to your account. Nothing you write is shown to other users — Talebound has no social features, no public profiles, and nothing you post is ever visible to anyone but you.
Your Qavren sign-in, however, is shared: the same Qavren Auth identity can be used to sign in to other apps Qavren Solutions operates. Talebound doesn't see what those other apps do with it, and this policy only covers what Talebound itself does with your data.
Children
Talebound isn't directed to children under 13, and we don't knowingly collect personal information from them. If you believe a child has created an account, contact us and we'll remove it.
Security
Traffic between the app and our servers is encrypted. Your sign-in tokens are stored in your device's secure storage (the iOS Keychain or the Android Keystore), never in the app's own local database. No system is perfectly secure, and we won't pretend otherwise — but keeping the amount of data we hold small on purpose is the most effective protection available to us.
Changes to this policy
We'll update this page when our practices change, and change the date at the top. If a change is significant, we'll try to say so in the app as well.
Contact
Questions about privacy, or a request about your data:support@gettalebound.com. For anything else, see support.