Offload — Privacy Policy
Effective 8 August 2026
Offload is a voice-dump app: you record or type a rambling thought, it gets transcribed and sorted into tasks, ideas, thoughts, feelings and decisions. This page explains exactly what happens to your data.
What's captured
Voice recordings are captured directly in your browser using the device microphone. Typing a dump instead of recording is always available — microphone access is optional, never required.
What's sent off-device, and why
When you record or type a dump, the audio and/or transcript is sent transiently to Cloudflare Workers AI to run the transcription (speech-to-text) and organizing (sorting into items) steps. This data is processed to generate the response and is not stored on Cloudflare's servers afterwards and not used to train models.
If the app operator has configured an Anthropic API key, the organizing step instead uses Anthropic's Claude API as the model provider, under the same transient-processing basis. See Anthropic's Privacy Policy for how Anthropic handles API data as a processor.
Adding tasks to your calendar or Reminders
The native app (Android and iOS) can add an extracted task to your device's calendar, and on iOS, to Apple Reminders — but only when you tap the "Add to calendar" / "Add to Reminders" button yourself. This happens entirely on your device via the system's own calendar/Reminders prompt. Offload never reads your existing calendar or reminders, and no calendar/reminders data is sent to Offload's servers or anywhere else off-device.
What's stored, and where
- On your device only: every recording, transcript, and organized item is saved locally in your browser's IndexedDB storage. It stays there — nothing is synced to a server — until you delete it yourself.
- On the server: anonymous call counters, used to apply your plan's allowance and to stop the app being overwhelmed by abuse — not tied to your identity beyond a randomly generated install ID (stored on your device and sent with each request purely so shared networks don't throttle everyone on them) and, as a coarse backstop, your raw IP address — both used only as rate-limit keys and never stored beyond those counters. The daily counters expire within 48 hours; the monthly allowance counter expires within 35 days, because it has to outlast the month it is counting. Unless turned off in Settings, anonymous usage-analytics event counts are also kept (see below). If you use the feedback form, that submission's text is stored so it can be read (see below). Neither of those carries your dump content.
Error reporting
If the app hits an unexpected error, an anonymous error message and stack trace are sent to our server so we can see that something went wrong. This is not an analytics or crash-reporting SDK — it only fires when an error actually occurs, is not stored (it appears only in transient server logs, not saved to a database), and has no install ID, IP address, or other identifier attached to it.
Usage analytics
Offload records a small set of anonymous event counts (e.g. "app opened", "dump recorded", "transcription succeeded") tagged only with the event name and the same random install identifier already used for rate-limiting — never your dumps, transcripts, or organized content. This is self-owned analytics (Cloudflare Analytics Engine, our own infrastructure), not a third-party tracking SDK. It's on by default and can be turned off at any time in Settings → Share anonymous usage stats.
Feedback
If you use the in-app feedback form, the text you write (and, if available, your anonymous install ID) is sent to our server and stored so we can read it — this is the one place in Offload where you're intentionally sending us content. Don't include anything sensitive in a feedback message.
What Offload doesn't do
- No accounts, no sign-in, no user identifiers beyond the anonymous, opt-out-able install ID.
- No third-party trackers or advertising SDKs — analytics above is self-owned, not resold.
- Your data is never sold or shared for marketing purposes.
Backing up your own data
Settings → Your data → Export backup writes a JSON file containing your transcripts and organized items. Offload never uploads that file — on the web it is a normal browser download, and in the Android app it is written to the app's temporary cache and handed straight to your device's share sheet, so you choose where it goes. Once you have shared or saved it, the copy is yours and this policy no longer governs it; treat it like any other file containing your own notes.
Backups deliberately exclude the original audio recordings, which keeps the file small. Importing a backup only adds dumps you do not already have — it never overwrites or deletes anything already on the device.
Your controls
Delete any single dump from its detail view, or wipe everything at once with Settings → Delete all data inside the app. That action clears local storage immediately and permanently. Export a backup first if you want to keep a copy — deleting is irreversible and there is no server-side copy to restore from.
Deleting your data
Everything Offload stores about you lives on your own device, so deleting it is in your hands: Settings → Delete all data removes every dump, transcript and organised item immediately and permanently, and uninstalling the app does the same. The only server-side records are the anonymous, auto-expiring usage counter and analytics events tied to a random install id — never to you. To have those removed early, email kiran@mdcwebb.co.uk with the subject Offload data deletion; we will confirm within 30 days.
Your rights (UK / EU)
Because almost all data stays on your device under your control, most of this is already in your hands via the in-app delete controls above. If you have any question about the anonymous, auto-expiring server-side counter or anything else on this page, you have the right to access, rectify, erase, or object to the processing of your personal data under UK GDPR / EU GDPR. Contact us using the details below.
Changes to this policy
If this policy changes, the effective date at the top of this page will be updated.
- 6 September 2026: contact address changed to the company's kiran@mdcwebb.co.uk, and a "Deleting your data" section added naming how to request removal of the anonymous server-side records.
- 8 August 2026: added the "Usage analytics" and "Feedback" sections, disclosing the self-owned, opt-out-able anonymous event analytics and the in-app feedback form.
- 29 July 2026: added the "Error reporting" section, disclosing the client-side error beacon that sends anonymous error messages/stack traces to our server logs.
- 22 July 2026: added the "Adding tasks to your calendar or Reminders" section, covering the new on-device calendar / Apple Reminders / share buttons.