How Riar handles your data
Last updated 9 November 2026
A plain-language, one-page view of what the Riar app will collect when it launches, why, and where it goes. It's the companion to the full app privacy policy, not a replacement for it. For the waitlist, see the waitlist privacy notice.
Riar is a trading name of Riar Technologies Limited, a private company limited by shares registered in Ireland (CRO number 828621), registered office Venture Hub, 136 Capel Street, Dublin, D01 T2C9. Riar Technologies Limited is the data controller. Questions go to privacy@riar.ie.
At a glance
- Email and photos (photos read on your phone)
- Riar's own rules on your phone (no AI, nothing sent)
- Only if they aren't sure: AI extraction (Anthropic, outside the EU, after you agree)
- Confident?If yes: you confirm with one tapIf no: it waits in "Check these"
- Once you confirm it: kept on your phone and, if you sign in, encrypted in the EU.
Anything Riar isn't sure about waits in "Check these" until you confirm or fix it. Health-related mail and photos never reach the AI before you've given Health consent: Riar asks you first. Nothing goes to the AI until you've agreed. Then, before the text of an email, photo, share or import reaches it, Riar's server removes PPS numbers, card numbers, bank account numbers (IBANs), passport numbers (where the text mentions a passport), passwords, PINs and codes given with their value, email addresses and Eircodes. Names and phone numbers are not removed: a provider's name and phone number are often what the reminder is about, so the AI may see the names and phone numbers in that text. Nothing goes into your reminders without your OK. Once you confirm it, it's kept on your phone, so the reminder fires even without a connection, and, if you sign in, on Riar's servers in the EU, encrypted at rest. Signing in is optional; without an account nothing about your reminders leaves your phone.
Now, and from launch (v1.0)
Before the public launch, and in steps during the beta, Riar changes so that nothing our servers store or receive can be read as part of your life. The tables further down show what happens today. This one shows what changes. The first step is live: your own reminders are encrypted on your phone (privacy phase 3a, 25 October 2026). Nothing in the From v1.0 column is built until the app privacy policy (Section 2a) says so.
| What | Now | From v1.0 |
|---|---|---|
| Signing in | Email code, text message code (Sinch), or Apple, Google or Microsoft | Your mobile number (a 6-digit text code through Sinch, Irish +353 numbers only at launch), an email code, or Apple, Google or Microsoft (asked for your email address only, never your name, photo or profile; Apple's Hide my email works; Google sends a name and photo link with every sign-in anyway, and our server deletes them as they arrive, before they're saved), and a passkey if you add one. Our servers hold your number or email and the provider's account id: personal data, deleted with your account. Your number is used only for sign-in codes and one account warning before deletion, and your email only for sign-in and account messages: never marketing, never shared. Signing in with Microsoft gives no access to your mail. Signing in can't unlock your reminders on its own |
| Signed-in phones | Model name, sign-in time and last use | The model name is encrypted on your phone; our servers keep only a session id, the dates, whether it's an iPhone or an Android phone and the IP address it last connected from, while that phone stays signed in (built, switched off for now) |
| Your reminders, date changes and settings on our servers | Your own reminders and their date changes: encrypted on your phone first, once you've saved your recovery key; the server keeps only encrypted content plus the listed metadata (below, Where it's kept). Reminders shared in a household, a helper's reminders while the help lasts, and your settings: readable by our systems, encrypted at rest, some fields encrypted again | Encrypted on your phone first, shared reminders and settings included: our servers keep only the encrypted copy |
| Household and managing for | Shared through Row Level Security | Encrypted with a household key sealed to each member's phone (built, switched off until older app versions are asked to update). The household's name and members' first names are encrypted too, readable by members only (for households started on the latest Riar; an older household keeps a readable name until converted, which isn't built); an invite's preview says only "You've been invited to a household" until you join. Joining is checked with a 6-digit code both phones work out themselves; it's never sent to or kept by Riar. A reminder marked Sensitive is never shared with the household. A reminder shared with chosen people is encrypted with its own key, locked to each chosen person's public key as the sharer's phone checked it with the 6-digit code (or, for a member sharing with another member, as the household owner's phone checked it and vouched for it inside the locked household details), and given a new key whenever someone comes off the list; with encrypted households on, nothing is shared before it's locked; the household's name and the owner's first name are encrypted from the moment a household is started on the latest Riar (never sent readable); a household started on an older version keeps a readable name, and its members' profile first names, until it is converted (no conversion is built yet). Encrypted helpers (built, switched off): a key per helper, handed over by the person's phone after both phones compared a 6-digit code; helpers open only reminders locked for them, never Health, Sensitive, money owed or household ones; when the help ends those are locked again with new keys. The person can keep any one reminder private from every helper (locked again with a new key, no helper key); that choice and who added a reminder are inside the encrypted reminder only |
| What our servers still see | Everything in the tables below | Your account id, your mobile number or email address and the sign-in provider's account id, item ids and their change times, household members and roles, which household a shared reminder belongs to and that it is shared, key versions and sizes, the time and push token for reminders sent from our server, your plan, your IP address in hosting logs (7 days), and, for each signed-in phone, the IP address it last connected from (for as long as that phone stays signed in) |
| Reading with AI | On your phone first, then Anthropic (after you agree) | On your phone first, then your phone's own AI where it has one (nothing sent), then our EU server AI only if you turn it on, with names, numbers and addresses removed on your phone first, and nothing kept |
| Pushes from our server | "You have a reminder" only | The same text, with details only your phone can open |
| If you lose everything | You can still sign in, but without a signed-in phone or your recovery key (which you can print or give to someone you trust), your own reminders can't be recovered, by you or by us | The same for everything encrypted on your phone; your phone's backup (iCloud Keychain or Google's encrypted backup, on by default) is a way back too |
| If you start fresh on a new phone | Your old, locked reminders stay on our servers, still encrypted, for 12 months in case you find your recovery key, then they are deleted | (as now) |
| Deleting your account without the app | By request | The riar.ie page explains how: email support@riar.ie from your sign-in email or with your mobile number, plus your deletion code if you made one (made in Settings; our servers keep only its hash). With the code it's deleted at once; without it, support first confirms with a sign-in code sent to that email or number. Accounts unused for 24 months are deleted after a warning in the app and by email or text, at least 30 days before; until a warning by email or text has gone, nothing is deleted |
Where it's kept
| Where | What | How it's protected | How it's deleted |
|---|---|---|---|
| Your phone | Your items, their dates (moved, skipped, done, snoozed) and your reminder settings, in the app's private storage | Private to the app and encrypted by Riar, with a key made on your phone and kept in its keychain or keystore (never sent anywhere, never in a backup), on top of your phone's own protection (your passcode). Android app backup is off; on iPhone your own iCloud or computer backup holds only the encrypted copy, which can't be read on another phone | Delete an item and it's gone from the phone at once. Items you marked done go after 12 months, unless you keep them. Signing out asks: keep them on the phone (the default; they keep reminding you and stop syncing) or remove them. Removing them, signing the phone out from another phone as lost, stolen or no longer used, or deleting your account clears it all, with its key and every reminder Riar has scheduled. One exception: if you turned off "Share custom reminder totals" and the phone couldn't yet tell Riar's servers, it keeps a one-way fingerprint of your account id (not the id, nothing else) until that account signs in on the phone again and the switch-off is sent. Items others share with you leave the phone on any sign out. Uninstalling removes it |
| Your phone's notifications | Each reminder waiting to be shown | Items with hidden details (health, money owed, children's and other private items) carry their type only | Cleared when the item is deleted, done, or when you sign out and remove your reminders from the phone, or delete your account |
| Riar's servers (Supabase, Ireland) | Your items, if you sign in, so they're safe if you lose or change your phone and the same on each phone you sign in on (sync): the items, the changes to their dates (moved, skipped, done, snoozed), whether you kept a completed item, and your reminder settings (quiet hours, reminder time, daily card, reminder style, what's hidden on the lock screen, which compare reminders are on, and whether Money check is on and its month), so they're the same on each phone. When you delete an item, only its random id, your account id and the time stay for 30 days, so your other phones delete it too; reminders beyond the next few weeks, as the item's type and send time only. For your own reminders, the server keeps only encrypted content plus the listed metadata: each reminder's random id, your account id, when it was made, last changed and completed, whether you kept it, a code naming which of your keys locked it (key id), and one yes or no, whether someone helping you may see it; its date changes as encrypted content with a random id, a code the server can't turn back into a date, the change time and the key id; and a reminder waiting to be sent with no type, its send time only. Once encrypted settings are switched on (built, off for now), your reminder settings are one encrypted record with a code naming which of your keys locked it, a revision number and when it last changed, and the readable copies go back to Riar's defaults. Household reminders stay as now until households are encrypted (3b), and sharing a reminder until then returns it to today's form; a helper's reminders stay as now while the help lasts and are encrypted on your phone once it ends | Encrypted at rest, HTTPS only, and Row Level Security so an account only reaches its own and shared items. Amounts, who money owed to you is from, and the titles and notes of health items and anything marked Sensitive, are encrypted again on their own, with the key kept apart in Supabase's vault. Never a PPS, card or bank account (IBAN) number: the servers refuse one in an item's name, reference, phone number or link, or note, as the app does | Delete-all, or straight away when you delete your account in the app (within 30 days of a request by email); backups within 35 days. Completed items 12 months after they're done, unless you keep them (encrypted ones too: the completed time and keep flag stay readable for this). Reminders still locked with an old key after you start fresh: 12 months after you started fresh (checked every night). A reminder waiting to be sent is deleted once sent, and never kept more than 24 hours after its time. A deleted item is gone from the servers the next time your phone syncs; the record that it was deleted goes after 30 days, or straight away with your account. Signing out deletes nothing from your account |
| Riar's servers (Supabase, Ireland): custom reminder totals | Only if you turn on "Share custom reminder totals" in Your data (off by default, one choice for your account held on Riar's servers, consent under Reg. 5(3) of S.I. No. 336 of 2011 and Art. 6(1)(a)). Then signed in only, at most once a week: one row for your account with the names of built-in categories and how many of your custom reminders are closest to each, and how many have nothing close. Never a title, note, date or a reminder's id, never Sensitive reminders or Health categories | Written only through a function that accepts nothing but those categories and numbers in range, and refuses while your account's switch is off; only you can read your own row (Row Level Security); the report is service role only and lists a category only once 20 different people have it. The row is linked to your account id, so it is personal data | Replaced each time; deleted when you turn the switch off on any phone (set_custom_totals_sharing, in the same transaction; an offline phone tells the server at the next open, or before Remove them wipes it), with your account, and 12 months after it was last sent |
| Riar's servers (Supabase, Ireland): the custom totals switch | Whether your account has "Share custom reminder totals" on or off, when it last changed, and its version, in custom_totals_consent (one row per account, none until you first use the switch). The version is a counter that goes up by one each time the switch is set, even to what it already was. Each phone's change says which version it was based on and is applied only if the switch is still at that version, so a change that arrives late, such as a turn-on that timed out, can never undo a newer choice; the phone then re-reads and shows what the server holds. An off this phone owed while offline is sent later with a fresh read, so it wins even over a newer on from another phone (it errs towards not sharing) | Read and set only by you, signed in, through two functions; no direct access for anyone (Row Level Security with no policy); a call made for another account than the one signed in is refused | Kept while the account exists, as the record of your choice (Art. 7(1)); deleted with your account |
| Riar's servers (Supabase Auth, Ireland) | For each phone signed in to your account: its model name (such as iPhone 15, read on the phone with no permission), when it signed in and when it was last used, shown in Signed-in phones so you can sign a phone out. Once encrypted phone names are switched on (built, off for now), the model name is encrypted on that phone and kept only in that form, with the sign-in's random id and a code naming which of your keys locked it; the sign-in itself then says only iPhone or Android phone | Only you can see your own phones. Signing out another phone asks why: lost, stolen or no longer used clears Riar from it the next time it opens with a connection; still in use only stops it syncing | When that phone signs out or is signed out, and with your account |
| Riar's servers (Supabase, Ireland) | Your account deletion code, as a hash only, and the date you made it; the date you last opened Riar while signed in (at most once a day); whether you've been warned that an unused account is about to be deleted, whether the email or text warning has gone and the deletion date it gave, and whether the account is due for deletion (not your number or address, which are read from your sign-in when it's sent) | Only Riar's own server functions read them; no one can list them. The code is made on your phone and shown once. When support uses it to delete your account, the code goes to our server once, where it's hashed to find the account and never logged or kept; wrong codes are limited by the address they come from, held in the server's memory only | The code is replaced when you make a new one and goes with your account. The warning is cancelled when you open Riar. All of it goes with your account |
| Riar's servers (Supabase, Ireland) | Your recovery key backup: your account key, locked (XChaCha20-Poly1305) with a key made from your 12 recovery words (Argon2id), with its random salt and nonce, the Argon2id settings and a code naming which account key it locks (key id). Never the words, the account key or the key made from the words | Only you can read or change your row (Row Level Security). Useless without your 12 words, which only your phone and you have. Your phone keeps the account key and the words in the iOS Keychain (this device only) or Android Keystore, and asks for Face ID or your passcode before it shows the words | Replaced when you make a new recovery key or start fresh. Goes with your account. Your phone's copy goes when you sign out or delete your account |
| Riar's servers (Supabase, Ireland) | From privacy phase 3b: your account's public key (X25519, made on your phone) with your account id. Personal data tied to your account, though it opens nothing. Its private half travels inside your recovery key backup, locked (XChaCha20-Poly1305) with your account key, next to a copy of the public key | You save your own, and replace it only with the public key in your own recovery key backup, when you start fresh or your phone puts its own key back (since 2 November 2026 Riar's server refuses any other change from the app, and keeps a change count, when it last changed and the id of the recovery key backup it was saved with, kept so a later version of the app can show you a change you didn't make; no phone reads them yet); nobody reads the table directly. Riar's server returns it only to the other people in your household and to the person you help or who helps you (peer_public_keys). The locked private half: only you can read your row (Row Level Security), and it opens only with your account key, which Riar never has | Replaced when you start fresh. Goes with your account |
| Riar's servers (Supabase, Ireland) | From the household and helper updates (household copies are used once encrypted households are switched on; helper copies once encrypted helpers are): the household key, and the key between you and someone you help, each locked to your public key (sealed box), with its version number | Only you can read the copies locked to you. Only the household owner adds household copies, and only for people who have joined; only the person being helped adds the helper copies (Row Level Security and server checks). Useless without your private key | A household copy goes when you leave or are removed (and the owner's phone then makes a new household key; copies of earlier versions stay for the people still in the household, as shared reminders may still be locked with them) or when the household ends; helper copies go when the help ends. All go with your account |
| Riar's servers (Supabase, Ireland): encrypted households (built, switched off; from launch) | Shared reminders: the locked content, the reminder's own key locked with the household key (a new one at every key renewal and every share), the key version and the id of the household it was locked for, plus the item metadata above and that it is shared; for each locked done or snooze, the key version it was locked for. The household's name and members' first names, locked with the household key, with the owner's vouch for each confirmed member's public key inside (member ids and public keys members can already get, a number and a counter for each list, and a box from the owner's phone to each member vouched for; added 25 October 2026, issued again at every new key and dropped for anyone who leaves or whose key changes; each phone keeps the newest list number it took, in its locked keyring on the phone) and the owner's phones' own record of whom they checked and whom they removed (member ids, a short fingerprint of each checked public key, removed marks and counters, at most 10 entries), locked a second time with a key only the owner's phones hold, so members can't read it either (added 2 November 2026, so every phone of the owner's vouches for the same people; each of the owner's phones also keeps it in its locked keyring), from the start of a household started on the latest Riar (an older household keeps a readable name, and its members' profile first names, until converted; no conversion is built yet) (create_sealed_household: the household, its first key copy and the locked details in one call, with no readable name or first name; the name column holds only a fixed placeholder). Reminders shared with chosen people (item_person_keys): the reminder stays the owner's own locked row, plus one copy of its key per chosen person, locked to that person's public key, and the number of the key in use (a new key at every change of who sees it); its done and snooze changes name that number. When the owner changes (household_handovers, added 3 November 2026): one locked statement from the old owner's phone to each person it checked (the household, the key version, the time, and both owners' ids and public keys, in a box only the old owner's key and that person's key open), kept for the person it is for, at most 4 each, deleted after 60 days, when that person leaves or the household ends. Invites by link: a hash of the link's secret, the owner's and the joiner's first names locked with that secret, who made and who used the link, the times, and the joiner's public key as it was when they joined. The 6-digit safety code is worked out on the two phones from the secret and both public keys and is never sent to or stored by our servers | Row Level Security and server checks: only members who hold the household key in use read shared reminders; only the owner shares, renews the key or writes the household details, and a renewal is all or nothing; anything locked for an older key version is refused; a member's phone writes only done and snooze changes to a reminder shared with them (the server can't tell a locked done from a locked move, so a member who changed their app could overwrite a shared reminder's date changes; the phone is the control); a reminder shared with chosen people is read only by the owner and the people holding a copy of its key in use, its key changes only through one all or nothing call that names the version the phone read, and it is hidden from helpers. Unreadable to Riar: the type, title, notes, amount and dates of shared reminders, the names (for households started on the latest Riar; an older household's name and profile first names stay readable until converted), the invite secret, the household key and the reminders' own keys. Still readable: ids, which household, member ids and roles, times, that a reminder is shared, who a reminder shared with chosen people is shared with, the completed time, the keep flag, key versions and sizes | Shared reminders as your other reminders (completed ones 12 months after done unless kept; deleted with the owner's account); one goes back to its owner, unshared, when the owner leaves or is removed or the household ends. Invites 30 days after they stop working; the joiner's locked name and public key are cleared sooner, when they leave, are turned away or delete their account. The household details are replaced at each new key and deleted when the household ends. A chosen person's copy of a reminder's key goes when they leave, are removed or delete their account, when the owner changes who sees it or shares it with the whole household, and with the reminder |
| Riar's servers (Supabase, Ireland): households on older versions of Riar (until the minimum version is raised) | What older builds still use, unchanged: the household's name, each member's first name, shared reminders in readable columns (with the field encryption described above) and who they are shared with, and invites that hold the first names as plain text next to a hash of the link's token | As above for readable columns; invites as the row above | Until the minimum app version is raised to the build with encrypted households, which is also what must happen before they're switched on. These paths are retired in a later release, once no live app uses them |
| Riar's servers (Supabase, Ireland) | After you start fresh: your old recovery key backup (the same locked account key, salt, nonce, settings and key id), so your old words can still open your old reminders if you find them | Only you can read your own; only Riar's server adds one, when you start fresh (Row Level Security). Useless without your old 12 words | 12 months after you started fresh (checked every night); sooner if it locks the account key you still use (a Start fresh that didn't finish) and you make a new recovery key, so your old words stop working as you asked; and with your account |
| Riar's servers (Supabase, Ireland) | After you start fresh: the code naming your old key (key id) and when you started fresh, so reminders locked with it can be deleted on time | Only you can see, add or remove your own (Row Level Security); the server sets the date | 12 months after you started fresh, with the reminders still locked with it (checked every night), and with your account |
| Riar's servers (Supabase, Ireland) | When you sign out another phone: that phone's sign-in id, your account id, whether to clear Riar from it, and when | Only Riar's own server functions read it; no one can list it, and the signed-out phone can only ask about its own sign-in | Deleted when that phone asks, or after 30 days, and with your account |
| A photo or PDF kept with a reminder before 8 November 2026 (attachment) | One file per reminder, kept before Riar stopped keeping files on 8 November 2026. No new one can be added: Riar reads a photo or PDF, you confirm the reminders, and the file is deleted. Riar deletes a kept file only with its reminder or when you sign out and remove your reminders, never on its own while the reminder stays | Kept in the app's encrypted database on your phone only; never uploaded, synced, shared with your household or sent to the AI, and not in an iPhone backup in a readable form | Deleted when you remove it or delete the reminder, sign out and remove your reminders from the phone, or use Delete everything; a completed reminder's goes with it after 12 months unless kept. A copy opened to view or share is deleted when you close it |
| Riar's servers (Supabase, Ireland): encrypted helpers (built, switched off; from launch) | For each reminder a helper may see: its own key locked with that help's key (helper_item_keys), with the key version. A reminder a helper adds: locked content in the person's own format and its key locked with the help's key, until the person's phone takes it in. A mark (rekey_needed) on a reminder to be locked again with a new key; when the helper's phone said the codes match. Request links by hash, with the helper's and the person's first names locked with the link's secret | Row Level Security and server checks: a helper reads only reminders locked for them while the help is active; only the person's phone locks reminder keys for a helper, only for reminders it marks as ones a helper may see, and only once the helper's phone compared the code; the helper's key copy only after that too; a reminder marked to be locked again can't change until it is, and locking again is all or nothing. Unreadable to Riar: the type, title, notes, amounts and dates, the names, the request secret and every key. Still readable: ids, who helps whom, times, the one bit that says whether a helper may see a reminder, key versions. Keep this private and who added a reminder (the helper's account id and first name, recorded when the person's phone takes it in) are sealed inside the reminder, never a column; the server sees only the bit turn off and the helper keys go. The number of reminders a helper added is counted on the person's phone only | Every locked reminder key for a help goes when the help ends (either side), with the reminder, or with either account; the reminders it opened are then locked again on the person's phone. The person's locked first name on the request is cleared when the help ends; the request goes 30 days after it stops working |
| Your phone, from encrypted helpers (built, switched off) | The key for each help you're part of, the other person's public key once you confirmed the 6-digit code matches, and request secrets until used (37 days at most); a phone without these trusts no key for that help | One Keychain or Keystore entry on this phone only, locked with a key made from your account's private key; never in a backup and never sent to Riar | Removed when you sign out (either way), use Delete everything or start fresh; a helper's phone drops a help as soon as it has ended |
| Your phone, from encrypted households (built, switched off) | The household keys you've been given (every version), the household owner's public key once you confirmed the 6-digit code matches (on the owner's phone, each member's, once the owner confirmed theirs); the time of the newest owner handover your phone accepted; a phone without these (a new phone, or one restored with your recovery words) trusts no one's key until the code is checked again by joining with a new link, and invite secrets until the invite is used, turned down or cancelled (37 days at most) | In one Keychain or Keystore entry on this phone only, locked with a key made from your account's private key; never in a backup and never sent to Riar | Removed when you sign out (either way), use Delete everything or start fresh |
| Your widgets (if you add one) | Tonight's reminder and the next three: their titles and days, or just the type ("Appointment") for anything hidden on the lock screen; the lock screen widget shows "Bins tonight" or a type and a day, never a name | Saved on your phone for the widget to show: on iPhone in Riar's own App Group storage shared only with Riar's widget, on Android by the phone's widget system; never sent anywhere | Replaced every time a reminder changes and when Riar opens; emptied when you sign out and remove your reminders from the phone, or use Delete everything, and gone when you remove the widget or Riar |
| A calendar file you make | Titles and dates of upcoming reminders | Made on your phone and never uploaded | Replaced when you make a new one, and cleared when you sign out (either way); any copy you save or share is yours |
| Riar's servers (Supabase, Ireland): household invites, "managing for" request links and ended "managing for" | A hash of each one-time link, who made it, and when it was used, cancelled or expired (encrypted households add the first names locked with the link's secret and the joiner's public key, see above; a link can also be for someone already in the household, with a mark saying so and no name for them, and confirming it replaces that member's key copies); who helped whom and when it ended | Encrypted at rest, HTTPS only; only the owner or helper sees their own; the link itself can't be read back | Deleted 30 days after the link stops working or the help ends (checked every night), and with your account. The person's consent record stays, withdrawn, while their account is open |
| Riar's servers (Supabase, Ireland): sign-in records | Supabase Auth's log of each sign-in: your email address or phone number, IP address and time | Encrypted at rest; only Riar's founder can read it | Deleted after 7 days (checked every night) |
| Riar's servers (Supabase, Ireland): signed-in phones | For each phone you are signed in on, Supabase Auth keeps a session id, dates, whether it is an iPhone or an Android phone and the IP address that phone last connected from (updated each time the phone refreshes its sign-in). This is separate from the sign-in records above. It is there so Riar can show a signed-in phone and sign it out, as a security measure | Encrypted at rest; only Riar's founder can read it | For as long as that phone stays signed in: deleted when you sign that phone out, when the sign-in otherwise ends, or straight away when you delete your account |
| Riar's servers (Supabase, Ireland): your access list (built, switched off) | For each event: its kind (sign-in, phone signed out from another phone, recovery key saved or replaced, helper or household member starting or ending, Riar staff opening your account record), the time, a phone's random session id or another person's account id where one applies, and for staff entries what was opened and why from a fixed list. Never a reminder, a name, an IP address or a place | Encrypted at rest, HTTPS only; Row Level Security: you read only your own rows from the last 30 days, the app can't write any, and only server triggers and one service-role-only function (record_staff_access) add rows | Deleted after 30 days (checked every night, riar-purge-access-log), and with your account |
What we collect, and why
| Source | What it gives us | Why |
|---|---|---|
| Photos you take or share | The text on paper documents, read on your phone (for a bin calendar, the bins and collection dates Riar finds fill in Bin day setup for you to check; nothing is saved until you do); the picture is never kept: Riar deletes its copy once the words are read. What Riar found but wasn't sure about (a title, a date, an amount, a contract end) waits on your phone in Check these until you add it or say it isn't a reminder, for 30 days at most; nothing else from the read is kept. Once this month's photo reads are used up, or when your phone is offline, nothing waits for the AI: what Riar found on your phone goes to Check these the same way (for 30 days at most), and the photo, PDF or share and its words aren't kept to read later; to have the AI read it, you take the photo or share it again. Words an earlier version kept waiting as Not read yet are deleted from your phone the first time the updated app opens, with anything the phone can find in them left in Check these. Our servers count how many emails and photos Riar's AI read for you each month (your account's id, the month, email or photo, and a number; never what was read), kept for 400 days, so the allowance and Settings, This month are right | Same as above, for anything that only arrives on paper |
| Price change and contract end notices | From a bill or notice Riar reads (email, photo or share): the new price, when it starts, the deadline to reply in the notice and the day it arrived, kept with the bill it belongs to on your phone and, if you sign in, on our servers, always encrypted there because it holds an amount; and a contract end found on a bill, with the few words it was found in, which waits on your phone until you say yes or not now. Riar matches a notice only to your own bill of the same type. Removed with Keep my plan, or with the item | So Riar can remind you before a price rise and before a contract ends, in time to compare |
| Outlook (read only, optional; not in the app yet, so this applies when it launches) | Bills, renewals and appointments in your Outlook, Hotmail or Microsoft 365 mail, within the look-back you choose (3, 6 or 12 months) and new mail after that. Your phone (not Riar's servers) asks Microsoft for who sent each message, its subject line and the date it arrived in that window (with each message's ids, used only to open the right message and to avoid reading the same message twice), keeps only that in memory while it works, and opens only messages from the billers and official senders on Riar's list and from the senders you add (websites or addresses you type in, at most 50, kept on your phone only and never sent to Riar's servers; Disconnect, every sign out and Delete everything delete them); the rest of your mailbox is never opened. A one-way fingerprint of each message it has read (not its id, sender or subject; pseudonymous, not anonymous, because the same message always gives the same fingerprint) stays on your phone for up to a year so it isn't read twice, with counts of how many checks and AI sends couldn't read a message (Riar stops trying after 3 checks or 6 sends); Disconnect and every sign out delete them. The sign-in tokens are kept on your phone only, in its secure storage, and are deleted when you disconnect, sign out (either way) or delete everything | So Riar finds them without you doing anything |
| Emails you send us | Your email address and what you write, such as a report that something Riar says is wrong or has changed (the report email is pre-filled with the reminder type, the line Riar shows and the app version only) | To reply and to fix the information. Kept 2 years after your last message; a report we act on is logged without your name or email |
| Forwarding address (not in the app yet, so this applies when it launches) | Emails you forward from any provider, by hand or with a forwarding rule. Read in memory and never stored. Our server makes the address from random characters and keeps a one-way fingerprint of it made with a secret key (not the address), a copy of the address only your phones can open, how many emails arrived today and today's date, only for the limit of 30 a day (cleared each night after midnight (by about 4am Irish time); the day the last email arrived isn't kept), how many held emails from senders it doesn't recognise were kept today and today's date, only for the limit of 5 a day (cleared the same way, and when you turn forwarding off), the day you last made a new address and how many that day (at most 5), and what it found (or, if it couldn't read the email yet or a PDF came with it, its text: with a PDF Riar's AI doesn't read it on our server, which only checks in memory who it is from and whether it looks like a bill or health-related, and the phone reads the text and the PDF together) locked to your phone's key until your phone collects it or you turn forwarding off, 14 days at most, and the email's first PDF (up to 4 MB) locked to your phone's key the same way, padded to one of three fixed sizes, at most 20 waiting, read on your phone and deleted from our server once your phone has collected it (your phone keeps it locked until read, up to 14 days from when the email arrived, and never keeps it with a reminder), when you turn forwarding off or after 14 days (other attachments, and every attachment's file name, are never kept). To stop one email being read twice, one-way fingerprints of the delivery code and of the email's message id are kept a day. An email over 10 MB is turned away unread. Mail from a sender Riar doesn't recognise (not a biller or official sender on Riar's list, and not one you chose) is held unread: its text is locked to your phone's key as above and read only if you tap Read it once or Always read from this sender. At most 5 held emails are kept a day (and only while fewer than 50 results wait); further held emails that day are dropped with nothing stored, read or counted against your allowance, while mail from billers on Riar's list and senders you chose is never limited by this. For Senders Riar reads, our server keeps a fingerprint of each sender address you chose to read, made with a secret key and your account's id (never the address, which your phone sends once when you choose it and our server doesn't keep), at most 50, until you remove it, turn forwarding off, delete your account, or we retire the key it was made with; the readable list stays on your phone | So new bills from Gmail and other email reach Riar, and mail from senders you don't know isn't read without your say |
| One-off import | Past bills from a Gmail Takeout file of one label, filtered on your phone, or a batch you forward. The file stays on your phone and Riar's copy is deleted once read; the phone's own rules read up to 300 bill-like emails from the last 12 months, and only the text, subject and sender of those its rules aren't sure about are sent to be read by AI, up to 60 an import. Our server keeps only how many emails each import read, to hold the limit of 60 AI reads an import and 1 import a year, for 400 days | So older bills are covered once |
| Share sheet | PDFs, screenshots, photos, selected text, texts and WhatsApp messages you share in. A PDF's first 3 pages and a screenshot's words are read on your phone and Riar's copy is deleted; Riar's own rules then read the words on the phone, and only when they aren't sure do the words go to Riar's AI, after the AI permission, counting as a photo read. Nothing is kept unless you add it or send it to Check these | So anything on your phone can become a reminder |
| Manual entry | Whatever you type in or pick yourself (Riar no longer keeps a photo or PDF with a reminder; one kept before 8 November 2026 stays on your phone, as above). For bin day that includes each bin's kind (such as recycling) and colour: item details, kept on your phone and synced like the rest | Full control when you'd rather not forward or share anything |
| Your calendars (opt-in import) | Yearly dates you tick, such as birthdays and anniversaries, from the calendars you pick. Read on your phone; nothing else is uploaded or sent to AI | Occasion reminders, only when you run an import |
| Adding to your calendar (optional) | Nothing. Riar opens your phone's own Add event screen and can't read your calendar | So a reminder also shows in your calendar, if you want that |
| The on-phone calendar (optional, Plus) | Nothing leaves the phone. Riar writes one all-day event per reminder date into a calendar it makes (or one you pick) and keeps the event ids on the phone, in its encrypted store, never synced. Sensitive, health, money owed, children's and immigration reminders go in by their type only. Sign out (removing reminders from the phone) and Delete everything first remove those events, then the calendar Riar made; if that fails, they stay in the calendar | So your reminders sit next to everything else in your calendar |
| Calendar file (optional) | Nothing new. Riar writes your upcoming reminders into a file on your phone: titles and dates, plus amounts and notes only if you choose; sensitive items by their type only. Nothing is uploaded | So you can open your dates in any calendar app |
| Calendar file and Add to calendar | Nothing new about you: made on your phone and never uploaded. The live calendar feed, which kept a calendar of your reminder titles on our servers, was turned off before launch (19 October 2026) and every stored feed deleted | So you can see your dates in your own calendar app |
| Your children's admin | Nothing about your child: no profile, name, date of birth or PPS number. School forms, the back to school allowance and childhood vaccinations are your own items, with general titles. Vaccinations are health items under your own Health consent; children's items are hidden on the lock screen and never shared unless you share them | So school dates and vaccinations aren't missed, without Riar holding your child's details |
| Managing for (another adult, with their agreement) | Their reminders, except health and other private types (health insurance included), money owed, items they mark Sensitive and household items (until households and helpers are encrypted (3b), reminders they've upgraded aren't visible to people helping them, decided 24 October 2026; what a helper adds is encrypted on their phone once the help ends); the reminders you add for them (theirs); your first name; who helps whom, when they agreed and when they last confirmed it; one-time request links, kept only as a hash, working once for 7 days | So you can help a parent or relative who asked for it |
| Household members | Items you've explicitly chosen to share; the household's name; who is in it and when they joined; a first name you choose, seen only by your household; one-time invite links, kept only as a hash, working once for 7 days; on Household, the household's shared count of photos and emails read by AI (a total, never who read what) | So a shared bill or bin schedule shows up for everyone in the house |
| Custom items (voice/text quick-add) | The reminder you asked for, tagged as custom if it doesn't match a built-in type. Your phone also notes the closest built-in category and how close it is (a score from 0 to 1), or that nothing is close; never for items you mark Sensitive. Only if you turn on "Share custom reminder totals" in Your data (off by default; one choice for your account, held on Riar's servers) and you're signed in, your phone also sends totals of your custom reminders by closest category (names of built-in categories and numbers only, never a title, note or date, never Sensitive reminders or Health categories), when the app opens and at most once a week Quick add is read on your phone, and Say it turns speech into text on the phone (no audio leaves it, no recording is kept); only when Riar can't work out the date, and only if you're signed in and have agreed, is what you typed or said, as text (up to 200 characters) sent with today's date for Riar's AI to read. Our servers count how many times a day the AI helped you (your account's id, the day and a number, never the text), deleted after 31 days, and how many times this month (your account's id, or on Household the owner's, the month and a number), deleted after 400 days | To remind you and, only in aggregated, de-identified form across many users, to spot patterns worth adding as new built-in categories |
| Subscriptions (optional) | Your plan (Plus or Household), monthly or yearly, trial, renewal or end date, and any payment problem the store reports. Apple or Google take the payment; RevenueCat (USA) checks it for us with your Riar account's id only, and we ask it to delete its record when you delete your account. Our server keeps only your current plan, removed when it ends. When a Household plan ends, items shared with everyone or with more than 1 person go back to their owner, private (a share with 1 person stays), and managing for someone pauses; nothing is deleted. | So your plan works on every phone you sign in on, and the extras it pays for turn on |
| AI read count (on Riar's servers, Supabase, Ireland) | Your account's id (a Household's is counted on its owner's), the month, whether it was an email or a photo, and how many times Riar's AI read one that month; and, for each past bills import, a random id, when it started and how many emails Riar's AI read in it. Never the text, sender, subject or what the AI said. You can see your own month's numbers in the app (This month); nothing else is readable from the app. Deleted after 400 days, or with your account | So the monthly allowance and the limit on past bills imports work |
| AI cost count (on Riar's servers, Supabase, Ireland) | Your account's id (a Household's spend is counted on its owner's), the month and what Riar's AI cost that month. No one can read it from the app; only Riar's server functions. Deleted after 400 days, or with your account | Used only to stop misuse at a monthly ceiling ($0.20 on Free, $0.28 on Plus, $0.45 for a Household): just before each AI call the most it can cost is held against the ceiling, then replaced by what it really cost. Each AI call also writes one line to our server's logs with the model, the tokens in and out, the cost and which feature it was (email, photo, quick add), with no account id, no text and no sender, so we can see what reading really costs; kept as long as the server logs |
| Outlook read count (on Riar's servers, Supabase, Ireland; Plus and Household, when the Outlook connection launches) | Your account's id, a random id for each Outlook check, whose allowance it counts on (a Household's is its owner's), when the check started and how many emails Riar's AI read in it. No sender, subject, text or answer. No one can read it from the app; only Riar's server functions. Deleted after 60 days, or with your account | Keeps Outlook's own limits (emails a check, checks a day, and a monthly total, a Household's shared), apart from the past bills import and the monthly allowance. Outlook comes with the Plus and Household plans only. An email over Outlook's limits stays in your Outlook, and its sender and subject wait on your phone in Check these until Riar reads it |
| Website visit counts on riar.ie | Daily totals only: page views per page, demo uses and waitlist joins. Our counts record no IP address, browser, device, referrer or identifier, and nothing is stored on your device. Lovable, our host, also counts visits by page, referring site, device type and country; we only see the totals | To see whether the website works. Deleted after 24 months |
| Waitlist form on riar.ie | Your first name and email, and which reminder types you picked on the page (never custom text you typed) | To email you about the beta, only with your consent. Unsubscribe any time and we stop |
We never collect more than a source needs to do its one job, and every optional source stays off until you turn it on yourself.
Who else can see it
Nobody, beyond what's needed to run the service:
- Supabase stores and encrypts your data, hosted in the EU
- Anthropic (a US company; its AI may run in any country where Anthropic operates, outside the EEA) reads the text of an email or photo, or a quick add Riar couldn't read on your phone, to extract dates and amounts, under a data processing agreement, and never uses it to train models. Riar asks your permission before the first time, and it never sees your calendar. We plan to move this to Claude on Google Cloud in the EU once it passes our accuracy tests, and we'll update this page first
- Sinch (Sweden, EU region) sends your sign-in code by text, and one account warning before deletion if your account hasn't been used for nearly 2 years, if you sign in with your mobile number: only your number and the text with the code or the deletion date (no link). Never marketing, never shared. Riar keeps no copy and never logs codes, and the code stops working after 10 minutes, with up to 5 tries an hour for each number
- Mailgun (a US company in the Sinch group, using its EU region; not used yet, as the forwarding address isn't in the app yet) receives emails you forward to your Riar address and passes them straight to our server
- RevenueCat (a US company) checks App Store and Google Play subscriptions for us, knowing you only by your Riar account's id, never your name, email address or phone number
- An account email provider (EU-based, named here before email code sign-in goes live) sends sign-in codes and account messages from no-reply@riar.ie
- Zoho (EU) runs our support@ and other mailboxes, and sends waitlist and beta emails
- Lovable (EU) hosts riar.ie and the waitlist
- Expo builds the app
- Expo, Apple and Google deliver push notifications. A push sent from our server says only "You have a reminder. Open Riar to see it.", never the item's title, type, amount or notes, and carries the item's random id so Riar can open it. Built, switched off for now (encrypted notification contents): the phone may send what a reminder from our server should say, encrypted so only the person's phones can open it; our server keeps it with the waiting reminder (deleted with it) and hands it to Expo, Apple and Google only for phones whose Riar can open it, with the waiting reminder's random id and time. Each push token then also records whether that phone can open them. Riar has no analytics or crash-reporting tool in the app
- Apple, Google, Microsoft handle the sign-in you choose (from launch, Riar asks them for your email address only); Microsoft also provides read-only access to your Outlook mail if you connect it
We do not sell your data, show ads, or share it with advertisers. Not now, not later. The links shown before a renewal (the regulators' comparison tools, accredited comparison sites and other providers' websites) send nothing at all: they're plain links with no tracking, no data passes to them, and Riar earns nothing if you switch.
How long we keep it, and how you delete it
While your account is active. Deleting your account in the app deletes it from our servers straight away (a request by email is done within 30 days), and from backups within 35 days. Deleting your account, or signing out and choosing to remove your reminders, also clears Riar's storage on your phone (except a one-way fingerprint of your account id while a custom totals switch-off is still waiting to reach our servers, deleted once it is sent); signing out keeps them on the phone by default. Completed items are deleted 12 months after you mark them done, unless you keep them, on your phone and on our servers. Disconnecting Outlook (once it launches) deletes Riar's access immediately. Results from your forwarding address (once it launches) are deleted when your phone collects them, or after 14 days. Anything waiting in Check these is deleted from your phone after 30 days at most, and Not read yet after 14 days at most for a forwarded email and any PDF with it (35 days for the sender and subject of an Outlook email held over a monthly limit; the email stays in your Outlook). Ended household invites, "managing for" request links and ended "managing for" records go 30 days after they end, and sign-in records after 7 days. Our host's request logs (with IP addresses) are kept 7 days, once that setting is confirmed on our live servers (until then, at most 30 days). Deleting your account also asks RevenueCat to delete its record of your purchases. Emails Riar reads, and emails you forward, import or share, are deleted once read.
The "Your data" screen in the app shows what's stored, with export and delete-all available in one tap, any time. Its "Getting emails in" row opens the screen that shows whether Outlook is connected and its look-back, and your forwarding address (once those launch). No need to ask us.
Other people in what you send
An email, PDF, photo or message you send in can name other people, such as a landlord who emailed you or someone else on a bill. Riar reads it only to find your reminder, never stores the email, locks what it finds to your phone's key and never contacts them. For a sender you choose to always read, our server keeps only a fingerprint of their address made with a secret key, not the address. Anyone who thinks Riar holds something about them can email privacy@riar.ie.
Your rights
You can see, correct, export and delete your data in the app. Things only our servers hold (such as your plan, your AI counts, your consent records and your access list) are sent to you if you ask privacy@riar.ie, within one month. You can object to anything we do on the basis of legitimate interests, and complain to the Data Protection Commission (dataprotection.ie).
Full legal detail is in the app privacy policy; this page is the plain-language summary.