Privacy Policy
Last updated
Short version. Your recordings never leave your iPhone. Your transcripts do: they sync to our server so your journal survives a new phone, encrypted with AES-256-GCM before they are stored. The features that read your journal back to you — mood, tags and Ask — send that text to OpenAI, and only after you have switched them on. You can turn them off, export everything, and delete your account and every row attached to it at any time.
This policy covers the Daily Unload iOS app and this website.
Who is responsible
Daily Unload is made by Buron Sadiku, an individual developer based in Kosovo, who is the data controller for the processing described here. Questions, requests and complaints go to suebwsapp@gmail.com.
What we hold
| What | Why | Where |
|---|---|---|
| Your email address, and your name if you give one | To create the account, sign you in, and send verification and password-reset codes | Our database |
| Journal entries — transcripts, mood and score, category, tags, themes, duration and timestamps | So your journal is there on every device you sign in to, and so Ask and the weekly reflection can read across it | Our database, encrypted |
| Search vectors built from your entries | To answer Ask questions with the entries they came from | Our database, encrypted |
| Subscription status and which plan | To unlock Premium and to show your renewal date | Our database |
| Product analytics — your user id and which screens and actions you used | To see which parts of the app are used and which are not | PostHog |
| Crash and error reports | To find and fix what breaks | Sentry |
Two things we never receive:
- Your audio. Recordings are written to the app’s private storage and stay there. Nothing streams, uploads or buffers them off the device.
- The content of what you do in the app, in analytics. Events record shape, not substance — that an entry was created, how long it ran to the nearest bucket, whether it had a transcript. Never the text, the mood or the category.
We do not sell your data, share it for advertising, or use your journal to train any model. There is no advertising SDK, no attribution SDK and no cross-app tracking; the app’s privacy manifest declares no tracking at all.
Your account
An account is required, because the journal syncs. You can create one with an email address or Sign in with Apple. With Sign in with Apple you can use Apple’s private relay address and we never see your real one.
Passwords are stored only as a bcrypt hash. Verification and reset codes are hashed too, and expire. Your session is a bearer token held in the iOS Keychain.
The microphone
Daily Unload records only while you are venting — after you tap to start, until you tap Finish or Cancel. iOS asks for permission the first time and shows the orange indicator whenever the microphone is live. You can withdraw the permission at any time in Settings → Privacy & Security → Microphone.
Transcription is on your device. The AI is not.
Speech-to-text runs on your iPhone, with Apple’s on-device speech framework. Your voice is not sent anywhere to be transcribed.
What happens next is your choice. The app asks, in plain words, before any of it is switched on:
- AI on. The text of a vent — never the audio — goes to OpenAI, which returns the mood, the category, the tags and themes, and a cleaner version of the transcript. The same applies to a question you type into Ask, and to your answer when the 30-day look-back asks whether anything has changed. The weekly reflection and patterns are calculated on our own server from the moods and tags already returned; they send nothing further to OpenAI. Under OpenAI’s API terms, that text is not used to train their models.
- AI off. Nothing is sent for processing. Vents are saved as plain transcripts, and Ask is unavailable. You can change your mind either way in Settings.
The mood scores and answers are automated readings of what you said. They are often useful and sometimes wrong — see the Terms of Use.
Where your data lives, and how it is protected
Recordings, and a full copy of your journal for offline use, live in the app’s private storage, protected by iOS file-level encryption and your device passcode. You can add a second lock inside the app, so Face ID, Touch ID or a passcode you set is needed to open your journal even when the phone is unlocked.
The synced copy lives in a PostgreSQL database hosted by Railway. Before an entry reaches the database, its transcript, tags and themes — and the search vectors built from them — are encrypted in the application with AES-256-GCM, with a key held outside the database. Your email address, timestamps, duration, mood and category are stored in plain text, because sign-in lookups and the charts are built from them.
We hold the key, because the service has to decrypt your entries to sync them, search them and answer an Ask question. This is not end-to-end encryption and we will not pretend otherwise: what it protects against is a stolen database, a leaked backup or a snooping host, not us. We do not read your entries.
Traffic between the app and our server is HTTPS only.
If you have iCloud Backup or a local device backup enabled, iOS may include the app’s on-device data in that backup. That copy is made and controlled by Apple under your Apple Account, not by us.
How long we keep it
- A vent you delete is marked deleted immediately, disappears from the app, and is purged from the database — with its search vectors — within 30 days by a housekeeping job that runs every six hours.
- Expired sign-in codes and sessions are deleted on the same schedule.
- Your account and every row attached to it are deleted when you ask; see deleting your data. If you signed in with Apple, we revoke our Apple token for you as part of that.
- Crash reports and analytics are kept for as long as our Sentry and PostHog plans retain them, and are not linked to your journal content.
Everything else we hold, we hold for as long as your account exists.
Who processes it for us
Each of these is a processor acting on our instructions, not an independent recipient, and each gets only what its job needs:
Each processor is bound by contract to protect your data with safeguards equal to or stronger than those described in this policy, and to use it only to provide its service to us.
- OpenAI — mood, category, tags and Ask answers
- Railway — API hosting and the Postgres database
- Resend — verification and password-reset email
- Sentry — crash and error reports
- PostHog — product analytics
- Vercel — hosting this website
- Apple — the App Store, purchases and Sign in with Apple
Apple’s handling of purchases and Sign in with Apple is covered by the Apple Privacy Policy.
Purchases
The subscription is sold and processed by Apple through the App Store. We never see your payment details, billing address or Apple Account. What we receive is the outcome: which product you bought, whether it is active, when it renews, and Apple’s notifications when that changes. We use it to unlock Premium and for nothing else.
Analytics and crash reports
Usage analytics are on by default. Once you sign in they are tied to your user id, so they are pseudonymous rather than anonymous. You can turn them off in the app at Settings → Share usage analytics, which opts the SDK out on the device. Session replay and screen recording are not enabled.
Crash and error reports are sent to Sentry so the app’s failures are visible to us. They contain diagnostic data — the error, the build, the device model — not your entries.
Legal bases
If you are in the EU, the UK or another place with comparable law, we rely on:
- Performance of a contract — holding your account and syncing your journal so the app works as described.
- Your consent — sending vent text to OpenAI. It is off until you accept, and you can withdraw it in Settings at any time, which stops all future sending.
- Legitimate interests — usage analytics, crash reports, rate limiting and abuse prevention, balanced against your privacy and switchable off for analytics.
International transfers
Our processors are in the United States and the EU. Where personal data is transferred out of the EEA or the UK, it is covered by the European Commission’s Standard Contractual Clauses, or the UK addendum, in our agreement with that provider.
Children
Daily Unload is not directed at children under 13, and we do not knowingly collect data from them. If you believe a child has created an account, email us and we will delete it.
Your rights
You have the right to access, correct, export, restrict and erase the personal data we hold about you, to withdraw consent, to object to processing based on legitimate interests, and to complain to your local data-protection authority. Californian residents additionally have the rights described in the CCPA; we do not sell personal information or share it for cross-context behavioural advertising, so there is no such sale to opt out of.
Most of it you can do yourself, immediately, without asking us:
- Export your whole journal — PDF, plain text, or a full archive — from Settings → Export journal.
- Erase every entry, or delete your account outright, from Settings. Here is how.
For anything else, email suebwsapp@gmail.com. We answer within 30 days, and normally within two working days.
This website
This site is a set of static pages. It runs no analytics, sets no cookies and loads no third-party scripts or embeds. The only thing stored in your browser is your light or dark theme choice, which never leaves it.
Vercel, our host, processes standard server request logs (IP address, timestamp, requested URL, user agent) to serve and protect the site. Those logs are not linked to any app data.
App Store privacy label
Our App Store listing declares the data in the table above: your email address, name, user id, purchase history, the content you write, and diagnostic and usage data — all linked to you, none used for tracking. This policy is what that declaration means in practice.
Changes to this policy
If the app changes in a way that affects this policy, we will update this page, change the “last updated” date above, and describe the change in the app before it takes effect. A change in how we process your data will never be applied retroactively without asking you.