Legal
Privacy Policy
The short version. We collect what the app needs and nothing more. No location, no contacts, no advertising identifiers, no cross-app tracking, no data sold to anyone.
Two things worth stating plainly rather than burying: signing in with Apple or Google means we do hold an email address for you, so your account is not anonymous. And crash reports carry your account identifier and nickname, so we can answer "my alarm didn't ring" — they are linked to your account, not anonymous. Detail in sections 02 and 04.
01Who we are
AlarmFriends is built and operated by Samouraï Coop, a cooperative established in France. For the purposes of the EU General Data Protection Regulation (GDPR), Samouraï Coop is the data controller for the data described here.
Questions, requests, complaints: support@samourai.coop.
02Signing in
AlarmFriends supports two ways to sign in: Sign in with Apple and Sign in with Google. There is no password to create and we never see your Apple or Google credentials — the provider verifies you and hands us a signed token.
From that token, and from what your provider chooses to share, we store:
- Account ID
- A UUID we generate. It is the key everything else hangs off.
- Provider ID
- The stable identifier Apple or Google gives us for you, so we recognise you on the next sign-in.
- Email address
- Used to identify your account and to reach you about it. If you use Apple's "Hide My Email", we only ever receive the private relay address — we never learn your real one.
- Nickname
- Seeded from the display name your provider supplies, or your device name. You can change it at any time; it is what friends see.
- Avatar URL
- Only if your provider supplies a profile picture URL.
Because an email address is attached, your account is identifiable, not anonymous. We say this explicitly because an earlier version of this policy claimed otherwise, and that was wrong.
03What the app stores
- Alarms
- Times, labels, repeat days, sound choice and enabled state.
- Friends
- Invite codes you generate or redeem, and the friend connections that result.
- Voice messages
- The audio you record for a friend, held only long enough to deliver it — see section 05.
- Reactions & streaks
- The reactions you send and the wake streaks they feed.
- Safety records
- Users you have blocked, and any content report you file — kept so blocks keep working and so we can act on reports.
- Subscription state
- Whether your account currently has Premium, and when a promotional grant expires.
Alarms ring locally on your device using the platform's alarm and notification facilities. We do not need or use push tokens to make your alarm go off.
04Diagnostics, crashes and product analytics
We use Sentry, on an instance we host ourselves, to collect crash reports and error diagnostics: the error and its stack trace, your device model and OS version, the app version, and a short trail of alarm-lifecycle events (scheduled → fired → dismissed) that lets us investigate "my alarm didn't ring" reports.
These reports carry your account ID and your nickname. That is deliberate: without it we cannot connect a report you email us to the crash we recorded. It also means crash data is linked to your account — it is not anonymous, and the previous version of this policy was wrong to say it was.
What crash reports do not carry: your email address, your recordings, your alarm labels, or your friends. The SDK's "send default personal information" setting is off, so no IP address or user agent is attached by default. Diagnostics are only sent from release builds, and a sample of performance traces is collected to spot slowness.
Clearing this context happens on sign-out. Deleting your account does not retroactively purge crash reports already recorded; ask us and we will remove them.
We also use PostHog, on its European cloud, to see how the app is actually used. It records a short, fixed list of product events: a paywall was opened and from where, a purchase was started, completed or failed, a voice message was attempted, sent, or blocked by the weekly free allowance, an alarm was created, an invite was sent or accepted. It also records the app being opened and backgrounded, which is how we tell whether people come back.
Those events carry your account ID, the app version, your device type and its operating system version. Nothing else. No location, at any precision: the country and city an analytics service normally infers from your IP address are switched off in our configuration, so section 06 stays literally true. No nickname, no email address, no alarm labels, no recordings, and no capture of your screen.
Analytics run in release builds only, and only once a project key is configured; without one the app never loads the analytics library at all. Signing out detaches your account ID from any events that follow.
05How long we keep things
Voice messages are the sensitive part, so they are the most aggressively deleted.
- Audio file
- After delivery to your friend's device, the app requests deletion of the server copy. An undelivered recording becomes unavailable for delivery after 10 minutes. Expiry and physical deletion are separate: scheduled cleanup removes eligible server files, and failures require retry. The ten-minute delivery window is not a guarantee that every stored copy has been erased at that instant.
- Delivery record
- The small row noting who sent what and when (it holds no audio) becomes eligible for cleanup 30 days after delivery, so your friend can still react to your voice in the meantime. Records referenced by reactions may remain so the reaction still has something to point at. Failed cleanup is retried.
- Unattached upload
- A recording that was uploaded but never attached to a delivery becomes eligible for cleanup 24 hours after upload.
- Invite codes
- Expire 7 days after they are created.
- Account data
- Kept while your account exists. Deleted when you delete the account — see section 08.
- Safety records
- Blocks and reports are kept while the accounts involved exist, so a block cannot be reset by re-adding someone.
06What we never collect
- No location data, of any precision.
- No contacts or address book. Friends are added by invite link only — the app never reads who you know.
- No clipboard reading beyond one check at first launch for an invitation. If you tap the App Store badge on an invitation page, the page copies that invitation link to your clipboard, so the app can connect you to your friend once installed. Nothing else on the clipboard is used or sent anywhere.
- No advertising identifiers, no ad networks, no cross-app or cross-site tracking.
- No browsing history.
- No microphone access outside a recording you deliberately start.
- No sale of personal data, and no sharing it for anyone else's advertising. Ever.
07Why we are allowed to process this (GDPR)
- Performing our contract with you — your account, alarms, friends and voice messages. Without this data there is no service.
- Legitimate interest — crash diagnostics to keep alarms reliable, product analytics to see which parts of the app work, and abuse prevention so blocks and reports work. We keep all three minimal.
- Legal obligation — retaining what we must in order to act on reports of illegal content, and to respond to lawful requests.
You can object to processing based on legitimate interest at any time; write to us and we will weigh it.
08Deleting your account
In the app: You tab → Delete account. This starts removal of:
- Server-held audio files associated with your account, including recordings you sent or received.
- Your account row, and by cascade your alarms, friendships, invite codes, reactions, blocks and notifications.
- Your sign-in record, so the Apple or Google link is severed.
If storage cleanup fails, account removal stops so you can retry. Some files may already have been removed: storage and account deletion are not one atomic operation.
You can also request deletion without the app: email support@samourai.coop from your account email and include your nickname. We verify ownership before acting. If you use Apple Hide My Email or cannot access the account email, explain this in your request. Do not send passwords or sign-in codes. Account deletion help.
Deleting server data does not remotely erase recordings already downloaded to another person's device. Diagnostic records already collected are handled separately; include them in your deletion request.
Residual copies may persist briefly in our provider's encrypted database backups until those backups roll over. They are not accessible to the app and are not used for anything.
Deleting your account does not cancel a Premium subscription — cancel that in your App Store or Google Play settings.
09Where your data lives, and who processes it
Your account, alarms, friend connections and voice messages are stored in the European Union, with Supabase. Traffic is encrypted in transit, and database access is constrained by row-level security policies so one account cannot read another's rows.
Supabase (Paris) and PostHog process our data in EU regions. RevenueCat, Expo, Apple, Google and Netlify are US companies, and what they receive may be processed in the United States. Each receives only what its row describes.
- Supabase
- Authentication, database and file storage. EU region (Paris). Privacy policy
- RevenueCat
- Subscription state. Receives purchase events keyed to your account ID. We never see your card details — Apple and Google handle payment. Privacy policy
- Sentry
- Crash reporting, using the open-source Sentry software on a server we run ourselves: reports go to us, not to Sentry the company. See section 04.
- PostHog
- Product analytics, on its European cloud, with IP geolocation switched off. See section 04 for the app, and the /download entry below for the website. Privacy policy
- Expo (app updates)
- Each time the app starts from scratch, it asks Expo's update service (u.expo.dev) whether a newer version of its code is available. That request carries your IP address, your platform, the app's version and a random installation identifier generated by the update library. It carries no account ID, nickname or email address. Privacy policy
- Apple & Google
- Sign-in, app distribution and payment. Their own privacy policies govern what they hold.
- This website
- alarmfriends.samourai.app is hosted by Netlify, which receives each visitor's IP address and request details in order to serve the pages, and logs them. The site sets no cookies, stores nothing on your device and serves its own fonts, so your browser contacts no other company when you load a page. The QR code on an invitation page is drawn by your browser; the link is not sent anywhere. Privacy policy
- The /download link
- The address we put in our social media posts counts how many people followed it, so we know which post worked. It records the campaign written in the link, which of our own short links was used, and whether the visitor was sent to the App Store, to Google Play or to our download page. Nothing else: anything else in the address is discarded rather than recorded. The count is made on our server, from a fresh random number each time: no cookie, no identifier, and your IP address and browser are not sent on. The counts are held by PostHog, on its European cloud, with location lookup switched off. Nothing links one visit to another, or to your account. Privacy policy
10Your rights
Under the GDPR you have the right to access your data, to have inaccurate data corrected, to have it deleted, to restrict or object to processing, and to receive it in a portable format.
Deletion is available immediately in the app (section 08). For everything else, write to support@samourai.coop and we will respond within one month.
If you think we have handled your data badly, you may complain to your national supervisory authority. In France that is the CNIL.
11Children
You must be at least 13 to use AlarmFriends. If the law where you live sets a higher age of digital consent, that age applies, as section 04 of the Terms says. We do not knowingly collect data from anyone younger. If you believe an underage person has an account, write to us and we will delete it.
Because the app delivers recorded audio from other people, we also enforce the content rules in section 07 of the Terms with no exceptions.
12Changes to this policy
We will change the date at the top when this policy changes, and tell you in the app when a change materially affects you.
13Contact
Samouraï Coop — France
support@samourai.coop
samourai.world