Privacy Policy
Effective September 13, 2026 · Operated by Nico Baran
loosie is built to keep your ideas on your device. We collect as little as possible, we don't sell your data, and we don't run ads. This policy explains exactly what happens with your information.
1. What you capture stays local
Your captures and crates — text, audio recordings, photos, sketches, tempo/key data, and any location metadata you attach — are stored in your browser/app storage (localStorage and IndexedDB) on your device. We do not receive or store this content unless you explicitly enable a feature that sends it (below).
2. Account & cloud sync (optional)
If you create an account or enable cloud sync, we process:
- Email address and display name — to authenticate you and sync across devices.
- The crates/captures you choose to sync — stored so they're available on your other devices.
You can use loosie fully without an account; sync and sharing are opt-in.
3. Sharing crates (optional)
When you create a share link for a crate, the content of that crate is encoded into the link or stored so recipients can view it. This can include voice recordings — if a crate holds voice notes, up to three of them travel with the link so the page can play them. Only share links you generate yourself expose that content. Anyone with the link can view it, so treat links as public. To make the link show a preview card in Messages and other apps, we also generate a small image of the crate (its name, colour and a few of its captures). It is stored with the share and removed when the share is deleted.
3b. The launch list on our website
If you type your email address into the form on loosie.pages.dev, we store that address, the date you added it, and the word “site” so we know where it came from. Nothing else: no IP address, no browser details, no tracking.
What we do with it: send you one email on the day loosie is released, and nothing else. No newsletter, and we never sell it or pass it to anyone. Reply to that email, or write to the support address, and we delete your address.
Where it is stored: the same Cloudflare D1 database described below, operated by us.
4. Shared crates you work in together (optional)
You can open one of your crates to other people so several of you can add to it. This is off unless you do it, and it is the one feature where your captures — including the files themselves — are stored on our servers.
What travels: the text that describes each capture — its title, type, notes, lyrics, tags, tempo, key and colours — along with the display name and avatar you have set, and a random identifier generated for your installation. That identifier is not your Apple ID, your email, or any advertising id.
Your files, in a shared crate only: the recording, photo or sketch attached to each capture is uploaded so the other members can play or view it. This happens only for crates you have opened to other people — never for your private crates, and never if you have not shared anything.
How other people receive it: by streaming. When someone opens one of your captures, their phone fetches the bytes, plays them, and keeps nothing. A copy is only written to their device if they switch on Download shared media in Settings, which is off by default.
How long we keep it: shared files are deleted 30 days after upload. A file larger than 25 MB is refused, and each shared crate is capped at 300 MB.
What still never travels: anything in a crate you have not shared. Private captures are never uploaded for this feature, and our server still refuses media embedded inside a capture's text.
Where it is stored: descriptions in a Cloudflare D1 database, and files in Cloudflare R2 object storage — both operated by us. A shared crate holds at most 24 people and 400 captures.
Stopping: open the crate, tap Edit crate, then Stop next to “Shared with others”. Your membership is deleted immediately and nothing further travels in either direction. Captures you already contributed remain visible to the people who were already in the crate, and everything stays on your own device as it was.
Note that a shared crate is different from a share link (section 3): a link is a public read-only snapshot, while a shared crate is a small private group that keeps updating.
5. Contacts & invites
When you add someone to a crate you can type their name or pick them from your contacts. On iOS the system contact picker is used: it runs outside the app, so loosie never gets access to your address book and only receives the one person you tap. That person's name and, if present, their email or phone is stored on your device so the crate can show them. If you go on to share that crate (section 4), the display name you have set for yourself is also stored on our servers so the others can see who is in it — their contact details never are.
Invites are sent by you, from your own email app. loosie opens a pre-filled draft containing the share link; we do not send email on your behalf and we do not store the recipient's address on our servers.
6. On-device AI features
Features like transcription, background removal, pitch/notes detection, and 3D rendering run entirely on your device. To power them, the necessary model files are downloaded once from a content-delivery network and cached. Your audio, photos, and text are processed locally and are not uploaded to us or to the AI providers.
7. Third-party services
To deliver the app we rely on a few providers. As with any website, these receive your IP address and basic request data when your device fetches from them:
| Provider | Purpose | When |
|---|---|---|
| Cloudflare (Workers, Pages, D1) | Hosts the app and, if you sign in, stores your account (email, display name, a hashed password or sign-in provider id), your synced crates, and any share links you create. Servers are in the United States. | Always for hosting; for data only if you sign in or share |
| Apple / Google — only if you use them to sign in | Verify your identity. We receive your email address and name; we never receive your password. | At sign-in |
| Hugging Face (huggingface.co) | The AI features — transcription, photo tagging, pitch detection — run entirely on your device, but the first time you use one, its model file is downloaded from Hugging Face and then cached. Your audio, photos and text are never sent there: only the request for the model file. | First use of an AI feature |
| Analytics (PostHog) — only if enabled | Anonymous usage events (screens, feature use). Not your content. | If configured |
| Error reporting (Sentry) — only if enabled | Crash diagnostics to fix bugs | If configured |
| Payments — Apple, with RevenueCat — if you subscribe | Take the payment and tell the app what you own. The purchase happens inside Apple's App Store; RevenueCat records what was bought against your account. We never see your card details. | At purchase, and at launch to check what you own |
Maps & link icons — Apple Maps (the small map on a Place capture, drawn by iOS), OpenStreetMap (the map view), the website you saved (its own /favicon.ico, which also gives the tile its colour), and Google's favicon service only when that site serves no icon of its own | Show the map view, and the icon and colour of a link you save | If you use those features |
| Reference lookups — Datamuse (rhymes), dictionaryapi.dev (definitions), Open-Meteo and sunrise-sunset.org (weather and light for a Place capture), TheColorAPI (colour names), Nominatim / OpenStreetMap (place names) | Answer one lookup you asked for. The word, colour or coordinate you are looking up is sent; your crates, recordings and account are not. No account is involved and nothing is stored with them. | Only when you use that specific feature |
| Google Fonts — only for Type captures | Load the typeface you named so the capture can show it. Your device downloads the font file from Google, which sees your IP address and browser details, as with any website. The name of the font is the only thing sent; your crates are not. | Only when you open or create a Type capture that uses a Google font |
8. What we don't do
- We don't sell or rent your personal information.
- We don't show ads or use third-party advertising trackers.
- We don't upload your captures for AI training.
9. Your choices & rights
- Delete local data: clear the app's data / uninstall, and your on-device captures are gone.
- Leave a shared crate: open the crate → Edit crate → Stop. This deletes your membership from our servers straight away. Do this before deleting your account if you are in shared crates: a shared crate identifies you by a random per-installation id rather than by your account, so deleting the account cannot reach it.
- Delete your account & synced data: in the app, open Settings → Delete account. This permanently removes your account, your synced crates, your share links and your sessions from our servers. You can also email nicobaran02@gmail.com.
- Access/export: you can export captures from within the app, or request a copy of account data.
- Depending on where you live (e.g. EEA/UK/California), you may have additional rights to access, correct, or delete your data.
10. Children
loosie is not directed to children under 13, and we don't knowingly collect their personal information.
11. Changes
If we make material changes to this policy, we'll update the effective date and, where appropriate, notify you in the app.
12. Contact
Questions or requests: nicobaran02@gmail.com.
loosie · Privacy Policy · Reviewed against the app’s actual data flows on 3 September 2026.