Riar app privacy policy
Last updated 9 November 2026
This is how the Riar app will handle your data when it launches. Items [marked like this] are confirmed before then. For the waitlist and riar.ie today, see the waitlist privacy notice.
1. Who we are and what this policy covers
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 for the personal data this app collects. We're based in Ireland, and this policy is written to comply with the EU General Data Protection Regulation (Regulation (EU) 2016/679), the Irish Data Protection Act 2018, and the ePrivacy Directive (2002/58/EC, as amended by 2009/136/EC), transposed into Irish law by S.I. No. 336 of 2011.
This policy covers the Riar mobile app, the riar.ie website, and any account you hold with us. Riar is currently built, marketed and supported for Ireland only. We don't operate, advertise, or provide support in any other market.
It also covers the waitlist on riar.ie, which collects a small amount of data before you have an app account (in short, see the waitlist privacy notice).
We haven't appointed a Data Protection Officer. Under Article 37 GDPR one isn't currently required for a service of our size and type, and we'll review that as Riar grows. The contact address below reaches the person responsible for data protection directly.
Questions about this policy or your data go to privacy@riar.ie. Full detail is under "How to contact us" at the end of this page.
2. What personal data we collect, and where it comes from
We only collect what the app actually needs to work. Specifically:
- Account and sign-in data: your email address, phone number, or Apple/Google/Microsoft account identifier, depending on how you sign up, and the date you confirmed you're 18 or over. Passkey credentials if you set one up. If you sign in with your phone number (Irish mobile numbers only), we send the sign-in code by text message through Sinch, in the EU; if you sign in with your email address, we email you the code (see Section 7). Signing in is optional: Riar works on your phone without an account. From launch (see Section 2a) you can sign in with your mobile number (we text you a 6-digit code; Irish +353 numbers only at launch), your email address (we email you a code), or Sign in with Apple, Google or Microsoft, with a passkey as an option. Your mobile number is used only for sign-in codes and one account warning before deletion (a single text if your account hasn't been used for nearly 2 years, see Section 9): never for marketing, never shared, and deleted with your account. We ask Apple, Google and Microsoft for your email address only, never your name, photo or profile, and you can use Apple's Hide my email. Google's sign-in always sends your name and a link to your profile photo as well; our server deletes them as they arrive, so they're never saved. We use your email address only to sign you in and to send you messages about your account; never for marketing unless you agree to that separately, never shared, and deleted with your account. Signing in with Microsoft doesn't give Riar access to your Outlook mail.
- Signed-in phones: for each phone signed in to your account, its model name (such as iPhone 15 or Pixel 8, which the app reads on the phone without any permission), when it signed in and when it was last used. This is so Account and sign-in can show your signed-in phones and you can sign one out. It's kept until that phone signs out, and deleted with your account. Before launch, the model name will be encrypted on your phone, so our servers keep only a session id, the dates, whether it's an iPhone or an Android phone and the IP address that phone last connected from (Section 2a; built, switched off for now). The IP address is there for security, so a signed-in phone can be shown and signed out, and it goes when that phone signs out.
- Your access list (built, switched off for now: it appears in Settings, Your data, Access to your data, when it launches): a list of what our servers can know about who and what reached your account, so you can see it. Each entry is the kind of event (a sign-in, a phone signed out from another phone, your recovery key saved or replaced, a helper or a household member starting or ending, or Riar staff opening your account record), the time, a random id for the phone or the other person's account id where one applies and, for Riar staff, what was opened and why (chosen from a fixed list, never free text). It never holds a reminder, a name, an IP address or a place; your phone fills in names. It's kept for 30 days and then deleted, and deleted straight away with your account. Our rule is that nobody at Riar has standing access to your account record, and that anyone who opens it records that first, so you see it here.
- Your Outlook email, if you connect it (not in the app yet: this applies when the Outlook connection launches; Outlook comes with the Plus and Household plans only): read-only access to an Outlook, Hotmail or Microsoft 365 mailbox through Microsoft, covering the look-back you choose (3, 6 or 12 months; 12 by default) and new mail after that. Riar never reads mail older than the date you chose. The connection is made by your phone, not by Riar's servers: the sign-in tokens stay on your phone, in its secure storage, and Riar's servers never receive them or your mail. Your phone looks only for the item types Riar supports; anything else is ignored and never stored. You can disconnect at any time, which deletes Riar's access from your phone immediately. Microsoft keeps its own list of the apps you have allowed, where you can also remove Riar. Work accounts may be blocked by your organisation, and your workplace may not allow personal apps to read work mail.
- Emails you forward, import or share: the emails you forward to your private Riar address (by hand or with a forwarding rule you set up; the forwarding address isn't in the app yet, so this applies when it launches), a one-off import of past bills (for example a Google Takeout file of one Gmail label, which your phone filters so only bill-like emails within your chosen look-back are sent), and the PDFs, screenshots or text you share into the app. Anything else is ignored and never stored, and the email itself is deleted once it has been read. What Riar finds in a forwarded email is locked to your phone's key before our server stores it, so the server keeps only something it can't read until your phone collects it (see How long we keep it). A forwarded email from a sender that isn't a biller or official sender on Riar's list, and isn't one you chose to read, isn't read at all until you tap Read it once or Always read from this sender on it; when you choose Always read from this sender (or remove a sender, or undo a removal), your phone sends that address to our server, which keeps only a fingerprint of it made with a secret key, never the address itself. Riar never asks for your email password and doesn't connect to Gmail.
- Photos and documents you take or share in. Photos are read on your phone (by Apple's or Google's text recognition on the phone itself). Riar then looks for the date, amount and provider on your phone first, with no AI and no connection; only when it isn't sure, and only if you've agreed, does the text go to the AI. What Riar read on your phone waits in Check these for you to confirm. If the AI can't read it now, because your phone is offline or this month's photo reads are used up, what Riar found on your phone goes to Check these for you to check or fill in, and nothing else is kept: Riar doesn't hold the photo, the share or its words to read later. To have the AI read it, take the photo or share it again when you're back online or once the month resets. Riar never keeps the photo or PDF: it reads it, asks you to confirm what it found, saves the reminders and deletes its copy of the file. If you want the file, save it on your phone yourself. A photo or PDF you kept with a reminder before 8 November 2026 (an attachment) stays on your phone only, in Riar's encrypted storage, until you remove it or its reminder is deleted: Riar deletes a kept file only with its reminder or when you sign out and remove your reminders from the phone, never on its own while the reminder stays. It's never uploaded, synced to your other phones, shared with your household or read by the AI, and it doesn't move to a new phone. It's also deleted when you sign out and choose to remove your reminders from the phone, and with Delete everything, and it's included in your data export.
- Quick add: what you type or say to add a reminder. Speech is turned into text on your phone. The text only goes to the AI when Riar needs help working out the date.
- Content you actively forward: screenshots, text, SMS or WhatsApp messages sent via your phone's share function, or emails forwarded to your personal Riar email address. We never access these unless you send them to us yourself.
- Item details you type in: titles, dates, amounts, the next step, a phone number or link, a reference such as a policy number, notes, for bin day, each bin's kind and colour, and for electricity, gas, broadband and bin service, when your contract ends (so Riar can remind you to compare). Riar never needs an ID, card or account number and warns you before one is saved. A PPS, card or bank account (IBAN) number in a reminder's name, reference or note can only be removed or changed, never kept: Riar won't save the reminder until it's gone, and a name Riar reads from a photo, an email, an import or your calendar is saved without one. Our servers check again: they refuse a PPS, card or IBAN number in a name, a reference, a phone number or link, or a note, so a reminder saved with one before this check stays on your phone and isn't saved to your account until the number is removed.
- Where your reminders are kept: on your phone, in the app's private storage, so your reminders fire even without a connection. Signing in is optional: without an account, your reminders stay on your phone only. Once you sign in, they're also kept on our servers in the EU (Supabase, in Ireland) and kept in step between your phones (sync), so they're safe if you lose or change your phone. What syncs: your items, the changes to their dates (moved, skipped, done, snoozed), whether you chose to keep 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. See Sections 9 and 10.
- Widgets: if you add a Riar widget to your home or lock screen, Riar saves what it shows on your phone: tonight's reminder and the next three, by title and day, or by type only ("Appointment") for anything hidden on the lock screen. The lock screen widget never shows a name. Widgets never contact our servers. On iPhone the snapshot sits in storage shared only between Riar and its widget; it's replaced with every change and emptied when you sign out and choose to remove your reminders from the phone, or use Delete everything.
- Dates from your calendar, only if you choose to import them. Your phone gives Riar access to all your calendars, so Riar limits itself: it reads only the calendars you pick, looks only for dates that repeat every year (such as birthdays and anniversaries), and does this on your phone. Only the dates you tick are saved, as a title you can edit and the date. Riar never uploads your calendar, keeps a copy of it, or sends it to our AI provider, and after an import we suggest you turn calendar access off.
- Adding reminders to your calendar: if you choose this, Riar opens your phone's own Add event screen with the details filled in. You pick the calendar and confirm. Riar can't read your calendar this way and receives nothing back.
- The on-phone calendar (Plus): if you turn this on, your phone asks if Riar can use your calendar. Riar makes a calendar called Riar on your phone, or uses one you pick, and adds one all-day event for each reminder date, then keeps those events up to date. It changes only the events it added. This happens on your phone: Riar's servers receive nothing. If you pick an iCloud, Google or Outlook calendar, that provider holds the events under its own terms. Reminders marked Sensitive, and health, money owed, children's and immigration reminders, show as their type only (for example Appointment), and amounts and notes go in for the other reminders only if you turn that on. You can remove Riar's events at any time. When you sign out and remove your reminders from the phone, or use Delete everything, Riar first removes the events it added, and the calendar it made, from your phone's calendar. If it can't (for example you turned calendar access off for Riar, or the calendar was deleted), signing out carries on and the events stay in your calendar, where you can delete them yourself in your calendar app (or delete the calendar called Riar). Riar can't find them again once your reminders are cleared from the phone.
- Calendar: Calendar file and Add to calendar are made on your phone and never sent to us. Riar's live calendar feed was turned off before launch (19 October 2026) because it kept a readable copy of your reminder titles on our servers; we deleted every stored feed, and its old links no longer open anything. We keep no calendar of your reminders on our servers.
- Household data: the household's name, who is in it, and a first name you choose for the household (other people in your household see it; nobody else does). Before launch, first names will be encrypted on your phone so only household members can read them. If you share items with other people in your household, they see what you've explicitly shared and nothing else. Invites are one-time links that you send yourself; we keep only a scrambled copy (a hash) of each link, so the link itself can't be read back from our servers, and it stops working once used, cancelled or after 7 days. We delete an invite's record 30 days after it stops working. On Household, the photos and emails Riar's AI reads are counted together, and everyone in the household sees the total; the count never says who read what, or what was read.
- Your children's admin: Riar has no profiles for children. If you're a parent or guardian, reminders about your children (a school form, the back to school allowance, childhood vaccinations, childcare fees, a baby's passport) are your own items. Riar never asks for your child's name, date of birth, PPS number or health details, and suggests general titles like "School form". See Section 5.
- Device and diagnostic data: app version, device type and the push notification token for your phone, needed to keep the app running and send reminders. For each phone you are signed in on, our sign-in provider also keeps the IP address that phone last connected from (an IP address is the number your internet connection shows to the sites and apps you use). We keep it for security: it lets Riar show you a signed-in phone and sign it out. Only Riar's founder can read it, and it is encrypted where it is stored. It stays for as long as that phone stays signed in, and goes when you sign that phone out, the sign-in otherwise ends, or you delete your account. Riar has no analytics or crash-reporting tool inside the app. We see the crash reports Apple and Google provide, which don't name you, and we count totals on our own server (such as how many reminders were acted on each day), never tied to what your items say.
- Waitlist (riar.ie): your first name, email address, which form on the page you used, and when you signed up, plus the reminder types you picked on the page, if any. Only types from our list are saved, never anything you typed as a custom reminder. Health, new baby, immigration and welfare types are never saved with your name or email. You also confirm you're 18 or over.
- Beta emails: we don't track whether you open our emails or click their links.
- Information other people give us about you: if someone invites you to their household, they send you a link themselves, so we don't receive your email address or phone number. Opening it shows the household's name, the first name of the person who invited you and the kinds of things they share (before launch this changes: the preview says only "You've been invited to a household" until you join, because members' first names will be encrypted so only members can read them); you can decline, and if you join, the owner confirms you before you see anything. If someone shares an item with you, or sets up a "managing for" profile with your recorded consent, we receive the items they choose to share. You can leave at any time.
- Subscriptions: if you subscribe to Plus or Household, which plan, whether it's monthly or yearly, whether you're in the free trial, when it renews or ends, and whether the store reported a payment problem. Apple or Google take your payment. RevenueCat checks the purchase with the store for us, knowing you only by your Riar account's id (a random number), never your name, email address or phone number. 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); managing for someone pauses until the helper is on Household again, and the person's consent stays as it was. Nothing is deleted.
- What we don't collect: payment card details (Apple and Google handle subscription billing), your contacts, anything from your calendars beyond the yearly dates you tick, or anything from your Outlook inbox, your import or the emails you forward or share that isn't a supported item type.
2a. What our servers see: now, and from launch
We're changing how Riar handles your data before the public launch (v1.0), in steps during the beta. The rule we're building to: nothing our servers store or receive should be readable as part of your life. The first step is live: your own reminders are encrypted on your phone before they leave it (privacy phase 3a, 25 October 2026), as the Now column says. Until each later step ships, the rest of this policy describes what happens today, and we'll update this section as each one arrives. Nothing in the From launch column is a claim that a step is already built. Encrypted households are built and switched off: they stay off until older versions of Riar have been asked to update, and the app doesn't offer or describe them until then.
| What | Now (the beta today) | From launch (v1.0) |
|---|---|---|
| Your account | Your email address, phone number or Apple, Google or Microsoft account identifier, and passkeys if you set one up | Your mobile number or email address and, if you use Apple, Google or Microsoft, that account's id, plus a passkey if you add one. Our servers can read these: they're personal data, kept until you delete your account. No name, photo or profile from Apple, Google or Microsoft (Google sends a name and photo link anyway; our server deletes them as they arrive), and Apple's Hide my email works. Your number is used only for sign-in codes and one account warning before deletion, and your email only to sign you in and for messages about your account |
| Getting back into your reminders | Signing in gets you into your account, but it can't unlock your own reminders. That needs your recovery key (12 words you save after signing in, which you can also print or give to someone you trust). Without it you can start fresh, and your old reminders stay locked (Section 9) | Also a phone that's already signed in (it shows a QR code), or your phone's own backup where it's end-to-end encrypted (iCloud Keychain on iPhone; Google's Block Store on Android phones where Google encrypts it end to end), which is on by default and needs nothing from you |
| How safe a text code is | (as now) | A text code is the weakest way to sign in, because someone could take over your mobile number (a SIM swap). But signing in alone can't unlock your reminders, so they'd find a locked account with nothing readable in it. After you sign in, Riar offers to add a passkey. We limit how many codes can be sent, codes stop working quickly, and we never log them |
| Your reminders, their date changes and your settings | Your own reminders and their date changes are encrypted on your phone before they leave it, once you've saved your recovery key, with keys only your phones hold. 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 chose to keep it, a code naming which of your keys locked it, and one yes or no: whether someone helping you may see it). Reminders shared in a household (sharing a reminder returns it to this form), ones a helper adds for you while that help lasts, and your settings are kept on our servers in readable form, protected by encryption at rest and Row Level Security, with amounts and the titles and notes of health and Sensitive items encrypted again on their own (Section 10). What a helper adds for you is encrypted on your phone once that help ends | Encrypted on your phone before they leave it, with keys only your phones (and the household members you choose) hold, reminders shared in a household and your settings included. Our servers keep only the encrypted copy |
| Household and "managing for" | Shared items readable on our servers by the people you share them with, through Row Level Security | Shared reminders encrypted on the owner's phone with a household key, which is locked to each member's phone so we hold only locked copies (helping someone works the same way, with a key of its own for each helper, see the next paragraph). The household's name and everyone's first name are locked with that key too, from the moment a household is started on the latest version of Riar (older households keep a readable name until they are converted, which isn't built yet), so for those they never reach us readable, and the invite link's secret stays in the link: we keep only a scrambled copy of it, and the owner's and the new member's first names travel locked with it. When someone joins, both phones work out the same 6-digit code from the link and their keys, and the owner and the new member each confirm on their own phone that they match; neither phone trusts the other's key before that, we never receive or keep the code, and if the codes don't match the person leaves. When someone leaves or is removed, the owner's phone makes a new key and locks each shared reminder again with a new key of its own, so they can't read anything new, even with keys they kept. Sharing a reminder again later also gives it a new key. A reminder you share with chosen people rather than the whole household is locked the same way, with its own key locked to each person you choose, so nobody else in the household (and not us) can open it; you can choose only people whose 6-digit code your phone has checked or, if you're a member, the other members whose code the owner's phone checked (the owner's phone vouches for their keys inside the household's locked details, which only members can read, so we can't add anyone), and when you take someone off, or they leave, it's locked again with a new key. A reminder is never shared before it's locked: if it isn't locked yet, the app asks you to try again in a moment. Other members can mark a shared reminder done or snooze it; only the owner edits it. Those limits on dates are kept by each phone, not by our servers (they can't tell a locked done from a locked move), so a member who changed their copy of the app could overwrite a shared reminder's date changes, including who marked one done. A reminder you mark Sensitive is never shared with the household. Helping another adult (built, switched off for now): the helper's request link carries a secret only the two phones see, and both first names travel locked with it. Both phones show the same 6-digit code, and each person confirms it on their own phone before the person's phone hands the helper a key of its own for that help. The person's phone then locks, for the helper, only the reminders a helper may see (never health items, health insurance included, money owed, items marked Sensitive or household items); we can't open any of it. What a helper adds is locked on the helper's phone and taken in by the person's phone. When the help ends, every reminder the helper could open is locked again with a new key of its own, so they can't read anything written after, even with keys they kept. The person can also keep any one reminder private from everyone helping them ("Keep this private"): their phone locks it again with a new key of its own and gives no helper a key to it, and each helper's phone removes its copy the next time it syncs. Which reminders a helper added is kept only inside the encrypted reminder, so we can't see it once the person's phone has taken the reminder in, and how many a helper added is counted only on the person's phone, never sent to us |
| What our servers still see, after every step | (as now) | Your account id, your mobile number or email address and the id of the Apple, Google or Microsoft account you sign in with; for each signed-in phone, a session id, the dates, whether it's an iPhone or an Android phone (its model name is encrypted) and the IP address it last connected from, for as long as that phone stays signed in; for your settings, which of your keys locked them, a revision number and when they last changed (the settings themselves are encrypted); your items' random ids, version numbers, the time each last changed and whether it was deleted (for your own reminders, also when each was made and completed, whether you kept it, which of your keys locked it, and whether a helper may see it); your household's members and roles, which household each shared reminder belongs to and that it is shared, who each reminder you share with chosen people is shared with and the number of its key, how big each encrypted item is, and the number of each household key (each shared reminder's type, title, notes, amount and dates, and, for a household started on the latest Riar, its name and members' first names, are encrypted so only members can read them; an older household keeps a readable name until it is converted, which isn't built yet, and the invite's secret and the household key never reach us); for reminders sent from our server, the time to send and your phone's push token; your plan (from the store); the access list described in Section 2, once it launches (kinds of events, times and random ids, 30 days); and your IP address in our hosting logs, kept for 7 days. This is still personal data, and the rest of this policy applies to it |
| Reminders sent from our server | The push says only "You have a reminder. Open Riar to see it." | The same text on screen, with the details in an encrypted part only your phone can open |
| Reading with AI | On your phone first; when it isn't sure, and you've agreed, the text goes to Anthropic (Section 6) | On your phone first, then your phone's own built-in AI where it has one (Apple's on iPhone; Google's Gemini Nano on some Android phones), which sends nothing anywhere. Our server AI only if you turn it on, with names, numbers, addresses, Eircodes and email addresses removed on your phone first, run in the EU, and nothing kept |
| Calendar | Calendar file and Add to calendar, made on your phone | Also Riar writing your reminders into your phone's own calendar, if you ask. Your calendar provider (such as iCloud, Google or Outlook) then holds those events under its own terms |
If you lose your recovery key. If you lose every phone signed in to Riar and your recovery key (and, from launch, your phone's backup), your own reminders can't be recovered, by you or by us, even though you can still sign in with your mobile number, email, Apple, Google or Microsoft. We'll say so plainly when you set up, in Settings and in our Terms. From launch, the same applies to everything else that's encrypted on your phone. This is the cost of a design where we can't read your reminders.
What our support team can't do. Once your reminders are encrypted on your phone, nobody at Riar can see, search, fix or restore them, or reset a lost recovery key. We can explain how the app works, check your plan and delete your account.
What we won't say. We won't tell you "no data leaves your phone", that Riar is "anonymous" or that "we collect nothing": the data in the last rows above has to reach our servers. We'll only say "Riar can't read your reminders" once an independent security firm in the EU has reviewed the encryption and the app (we'll publish a summary of its findings), and we'll list these exceptions next to it.
3. Why we process your data, and our legal basis
| Purpose | What this covers | Legal basis (GDPR Art. 6) |
|---|---|---|
| Running the core service | Extracting items, scheduling reminders, showing your daily card | Necessary to perform our contract with you: Art. 6(1)(b) |
| Reading what you send in | Reading the emails you forward or import, your Outlook mail if you connect it, and the photos, PDFs, screenshots, shared text and quick adds you give Riar, on your phone first and with AI only after you've agreed; holding mail from a sender Riar doesn't recognise until you choose to read it; keeping a fingerprint of each sender you chose to read | Contract: Art. 6(1)(b), because reading what you send is the service you asked for. The AI permission screen is how we make sure nothing goes to the AI before you agree, and you can turn it off any time; health information also needs your explicit Health consent (Art. 9(2)(a), Section 4) |
| Limits that protect the service | The daily and monthly AI limits, the monthly AI cost ceiling, the daily limit on emails each forwarding address accepts, and the fingerprints that stop an email being processed twice | Contract: Art. 6(1)(b) for the limits of your plan; legitimate interests: Art. 6(1)(f) for the cost ceiling and duplicate checks, which stop misuse and keep Riar affordable |
| Your account and household sharing | Sign-in, passkeys, sharing items with people you invite | Contract: Art. 6(1)(b) |
| Optional features you switch on | Importing dates from your calendar | Consent: Art. 6(1)(a), withdrawable any time in Settings or in your phone's settings |
| Keeping the service secure and reliable | Fraud prevention, bug fixing, abuse prevention | Legitimate interests: Art. 6(1)(f), balanced against your rights. We don't rely on this basis for anything that would surprise you |
| Your children's admin | Reminders you add about your children, such as school forms and vaccinations, kept as your own items with no profile for the child | Contract: Art. 6(1)(b), as with your other items. Vaccination reminders are health items and need your explicit Health consent (Art. 9(2)(a)) |
| Helping another adult ("managing for") | Reminders another adult lets you see and add (never their health items, health insurance included, money owed, items they mark Sensitive or household items), and your first name, which they see. Until households and helpers are encrypted (3b), reminders they've upgraded aren't visible to people helping them (decided 24 October 2026). What you add for them is encrypted on their phone once your help ends | Their consent: Art. 6(1)(a), given on their own phone and withdrawable any time |
| Knowing whether Riar works | Daily totals on our own server, such as how many reminders were acted on in time and how many people turned notifications off. No analytics tool, no names and nothing about what your items say | Legitimate interests: Art. 6(1)(f), keeping reminders reliable |
| Legal and tax recordkeeping | Only if applicable (e.g. payment records for a paid subscription) | Legal obligation: Art. 6(1)(c) |
| Waitlist and beta emails | Telling you when the beta opens, sending your invite (the first 100 to join, in the order they joined), and one reminder if you haven't installed it | Consent: Art. 6(1)(a), and Regulation 13 of S.I. No. 336 of 2011 for electronic messages. Withdraw any time with the unsubscribe link in every email |
| Planning the build | Using the reminder types you picked on riar.ie, if any, to decide what to build first | Consent: Art. 6(1)(a), given when you join the waitlist |
| Support emails and reports | Answering emails you send us, including reports that something Riar says is wrong or has changed, and fixing it | Legitimate interests: Art. 6(1)(f), replying to you and keeping Riar's information correct |
| Feedback calls | Arranging a short call, only if you reply to say you'd like one | Consent: Art. 6(1)(a) |
| Unsubscribe list | Keeping the email address of anyone who unsubscribes on our email provider's do-not-email list, and nothing else, so we never email them again by mistake | Legitimate interests: Art. 6(1)(f), respecting your objection |
| Service messages | Account security notices, changes to these terms or this policy, service outages, and the one warning before an account unused for nearly 2 years is deleted (by email, or by text to your sign-in mobile number). Not marketing, so you can't opt out while you hold an account | Contract: Art. 6(1)(b); for the warning before deletion, also legitimate interests (Art. 6(1)(f)): giving you the chance to keep your account and reminders |
We also look at which custom items (ones outside our built-in categories) come up often, to decide what to add as a new built-in category. We only do this if you say yes. In the app, under Your data, there is a switch called "Share custom reminder totals". It is off until you turn it on, and your choice is kept with your account on our servers, so it is the same on every phone you use. While it is off, your phone doesn't count your custom reminders for this and sends nothing. Our basis is your consent (Art. 6(1)(a)), which is also what Regulation 5(3) of S.I. No. 336 of 2011 asks for before an app reads information on your phone for something you didn't ask it to do. Once you turn it on and you're signed in, your phone counts its own custom reminders by the closest built-in category (never one you mark Sensitive, and never Health or any other category that is sensitive by default) and, when you open the app and at most once a week, sends only those totals: the names of built-in categories and numbers, never a title, note, date or anything else you wrote. Our servers keep one row of totals for your account, replaced each time. The row carries your account's id, so it is still personal data and not anonymous; the report we read counts people, is aggregated and de-identified, and never lists a category until at least 20 different people have it. Our servers keep a record that you turned the switch on or off and when, for as long as your account exists, so we can show what you chose. Turning it off on any phone turns it off for your account: our servers delete your row at the same moment and refuse totals from any of your phones until you turn it on again. If your phone is offline when you turn it off, that phone stops at once and tells our servers the next time it can (also before it signs out, if you choose to remove your reminders from it), so the row can stay until then; see Signing out below for what is kept if the phone is cleared first. You can also turn it off from any other phone, which takes effect at once. Turning it off never changes anything else in Riar. Signing out stops it too, and the row is deleted with your account.
We do not process your data for advertising, profiling for marketing purposes, or any purpose you haven't been told about here.
Do you have to give us this data? No law requires you to. Your sign-in details are needed to create an account, because we can't run the service without them. Everything else is optional: if you don't connect Outlook, forward or import emails, share documents or send photos, Riar simply has less to remind you about, and you can add items by hand instead. Joining the waitlist is entirely optional and has no effect on whether you can use Riar later.
Information about other people that you add
Some reminders are about other people: a friend's birthday you import or type in, money someone owes you, or a deadline you look after as a landlord. For these we store only what you enter (usually a name you choose, a date and perhaps an amount), and we never ask for anyone else's contact details or, for landlords, tenants' names or details, use it only to remind you, and delete it when you delete the item or your account. Who money owed is from is encrypted on our servers, like amounts. We rely on legitimate interests (Art. 6(1)(f)) for this: it's what you asked us to do, it's minimal, and the people concerned aren't contacted by Riar. We don't notify them individually, because that would mean collecting more about them than we hold (Art. 14(5)(b)).
People named in what you send in. An email you forward or import, your Outlook mail, a PDF, a photo or a shared message can mention other people: whoever sent it (a biller, but sometimes a person, such as a landlord writing from a personal address), someone else named on a bill, or a person in a thread you forwarded. Riar reads that text only to find the reminder you asked for. The email itself is never stored, what Riar finds is locked to your phone's key before our server stores it, and on your phone only the sender's address and the subject are shown until you confirm. For a sender you choose to always read, our server keeps only a fingerprint of their address made with a secret key, which can't be turned back into the address. We rely on legitimate interests (Art. 6(1)(f)) for these people's details: it's what you asked us to do, we keep as little as we can, and Riar never contacts them. We don't tell each of them individually, because we usually can't identify or reach them without collecting more about them (Art. 14(5)(b)); this section is how we make the information public. Anyone who thinks Riar holds something about them can contact privacy@riar.ie, though in most cases we can't find or read it, because it's locked to the user's phone.
4. Special category (health) data
The optional Health pack lets you track appointments, repeat prescriptions, medical card and GP visit card reviews, vaccinations (including your children's vaccinations, which you add as your own items) and similar items. Some of this counts as "special category" health data under Article 9 GDPR, which needs a higher bar than ordinary personal data.
- We only process it with your explicit consent, under Article 9(2)(a). We ask the first time you add a health-related item, however it arrives: from a pack, the list of reminder types, a photo, an email or quick-add. Until you've agreed, nothing health-related reaches our AI: mail from health senders (such as the HSE and Healthmail) and text that reads as health-related are held back before the AI step, and Riar asks you first. We record when you agreed and to which version of this wording. Turning it off in Settings deletes every health item.
- A due date counts as health information, because it means a pregnancy. The New baby pack asks for this consent before it saves the date, and every item it creates has its details hidden on the lock screen and isn't shared with your household unless you share it.
- We minimise what's stored by default: Health pack items use generic titles like "Appointment" rather than the specific reason for a visit, unless you choose to add more detail yourself.
- Health data is never used for anything beyond reminding you: no analytics, no profiling, and no sharing with anyone. The only other parties that see it are our email provider, Mailgun, which passes a health email you forward to our server without keeping it (once forwarding launches), and our AI processor, Anthropic, which reads the text of a photo or email, or a quick add you typed or said, under a data processing agreement, only to find the date, and never uses it to train models.
- Calendar import skips one-off events, which keeps appointments out. If a date you choose to import looks health-related, Riar asks for Health pack consent before saving it.
Other sensitive things a bill can reveal. Some bills and letters can say something else sensitive about you: a trade union subscription, a donation to a church, a marriage notice, a social welfare review, an immigration permit or a fine. Riar doesn't look for these, doesn't label or count them, never uses them for anything except the reminder you asked for, and never shares them. Your own reminders are encrypted on your phone. If the AI helps read the text, it sees what the text says, the same as for any other bill, and nothing is kept by Riar.
5. Children, and Article 8
Riar is for people aged 18 and over. Riar asks before you use it, with or without an account, and nobody under 18 holds a Riar account or agrees to anything themselves through the app. If we learn we've collected data from someone under 18, we delete it. Some of the phone's own reading tools Riar uses on Android are offered by Google only for apps whose users are 18 or over, which is why Riar's age is 18.
Under Irish data protection law, anyone under 18 is a child (section 29 of the Data Protection Act 2018). Because Riar is only for adults, it isn't offered to children, and the Article 8 GDPR question of a parent's consent for an online service offered directly to a child (16 in Ireland, section 31 of the Data Protection Act 2018) doesn't arise. Everyone gets the same protections by default, without asking: no ads, no marketing, no profiling, no tracking, health information only with explicit consent, and details hidden on the lock screen for sensitive reminders.
If you said you were 16 or over before Riar's age changed to 18 (beta testers only), Riar asks you again the next time you open it, and stays on that question until you answer. If you're under 18, your reminders stay on your phone, nothing more is sent, and we delete your account if you ask us to.
Riar has no profiles for children: there's no account, name, date of birth or year of birth for a child anywhere in Riar. If you're a parent or guardian, you can still keep track of your children's admin, such as school forms, the back to school allowance, childhood vaccinations, childcare fees or a baby's passport, as your own items, the same as any other reminder. Riar never asks for your child's name, date of birth, PPS number or health details, and we suggest you keep titles general ("School form", "Childhood vaccinations") rather than adding them yourself. What you type in a title or note is your own content, kept only to remind you.
A reminder about a childhood vaccination is still health information, so it's a health item under your own Health consent (Section 4). Children's items, including vaccinations, school and the back to school allowance, have their details hidden on your lock screen by default, and are never shared with anyone in your household unless you share that item yourself.
Everyone in a household is 18 or over. If you help another adult with their admin (a "managing for" profile), you send them a one-time request link from your own phone (Riar never receives their contact details), and they agree on their own phone first. You see their reminders except health items (health insurance included), money owed, items they mark Sensitive and household items, which stay private; what you add becomes their own reminder, which they can also keep private from you. Until households and helpers are encrypted (3b), reminders you've upgraded aren't visible to people you help: their phones couldn't open them yet (decided 24 October 2026). What a helper adds for you stays visible to them while they help you, and is encrypted on your phone like your other reminders once that help ends. Either of you can end it at any time, straight away. Every 6 months Riar asks them whether to keep it going. Request links are deleted 30 days after they're used, cancelled or expire, and an ended "managing for" record 30 days after it ends; the record of their consent, and when they withdrew it, stays while their account is open.
6. How automated extraction and AI processing works
Riar reads photos, screenshots, shared text and imported emails on your phone first, with fixed rules and no AI: when it finds a known kind of reminder with one clear due date, nothing is sent anywhere and what it found waits in Check these for you to confirm. When you connect Outlook, forward an email, or Riar isn't sure what a photo, share, import or quick add says, Riar uses automated processing, including AI language models, to identify dates, amounts, providers and item types. Before the first time any of these sends text to the AI, Riar shows one plain screen asking your permission and naming Anthropic. You can turn this off in Settings, Your data, and keep adding items by hand.
Before the text of an email, photo, share or import reaches the AI, our server removes what Riar never needs: 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, because 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 the text you send.
Quick add reads what you type on your phone first, with no AI and no connection. If you use Say it, your phone turns your speech into text on the phone itself: no audio leaves it and no recording is kept, and the words are treated exactly like typing. Only when Riar can't work out the date, and only if you're signed in and have agreed, does it send the words (up to 200 characters) and today's date to the AI: nothing else about you or your reminders. Text with a PPS, card or bank number, a passport number or a password is never sent, and health-related text isn't sent until you've given Health consent. What the AI read is shown for you to check, and nothing is saved until you tap Save. To keep to the daily limit, our servers count how many times the AI helped you each day; they never keep what you typed or what the AI said.
Outlook comes with the Plus and Household plans only. From Outlook, your phone asks Microsoft for who sent each message, its subject line and the date it arrived, within the look-back you choose (with each message's ids, used only to open the right message and to avoid reading the same message twice), keeps only that in its memory while it works, and opens (downloads the text of) only messages from the billers and official senders on Riar's list and from the senders you add yourself (a website like a landlord's, or one address; at most 50). The senders you add are personal data kept on your phone only: they are never sent to us, and Disconnect, every sign out and Delete everything delete them. It never opens the rest of your mailbox. So that a later check doesn't read the same message twice, your phone keeps a one-way fingerprint of each message it has read (not its id, sender or subject) for up to a year; Disconnect deletes them. None of this goes through Riar's servers. Riar matches senders, the ones you add as well, on the address a message says it is from, which a sender can fake; a message like that is still read on your phone first, and goes to the AI only if you've agreed.
This isn't a solely automated decision with a legal or similarly significant effect on you under Article 22 GDPR: nothing acts on your behalf without your review. Anything below our confidence threshold goes to a "Check these" list for you to confirm yourself, rather than straight into your reminders.
The transparency duties in Article 50 of the EU AI Act (Regulation (EU) 2024/1689) apply from 2 August 2026. Riar doesn't chat with you as an AI and doesn't publish anything an AI wrote, but we tell you plainly where AI is used: extraction is AI-assisted, not read or reviewed by a person at Riar, and what it finds always waits for you to check. Extraction currently runs through Anthropic's Claude models (Claude Haiku 4.5, on Anthropic's own service). We plan to move it to Claude running on Google Cloud in the EU, once it passes our accuracy tests, and we'll update this policy before we do. Before launch, your phone's own AI comes first and our server AI becomes something you turn on (Section 2a). See "International data transfers" below for how that's handled. Dates imported from your calendar are never sent to an AI model.
7. Who we share your data with
We do not sell your data, and we do not show ads or share data with advertisers. This is a permanent product commitment, not a launch-phase promise.
Data is shared only with processors acting on our instructions, under contract:
| Processor | What they handle |
|---|---|
| Supabase | Database, authentication, file storage (EU-hosted) |
| Google, Microsoft, Apple | Sign in with Apple, Google or Microsoft, if you choose it (your name and email address only; before launch, your email address only, never your name, photo or profile, and Apple's Hide my email works; Google sends a name and photo link with every sign-in, which our server deletes as they arrive). Signing in with Microsoft never gives Riar access to your mail |
| Microsoft | Read-only access to your Outlook mail, only if you connect it, within the look-back you choose |
| Anthropic | AI-assisted extraction (see Section 6), until it moves to Google Cloud in the EU |
| Google Cloud (Vertex AI, EU region), not used yet | AI-assisted extraction with Claude, run in the EU, once it replaces Anthropic's own service: the text being read only, never stored. Named here before it's switched on |
| RevenueCat (USA) | Checking App Store and Google Play subscriptions for us, so your plan works on all your phones: your Riar account's id and the store's purchase records (the product, dates, price, currency and the store's country). Never your name, email address or phone number |
| Expo (EAS) | Building the app and delivering 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; it carries the item's random id so the app can open it. Built, switched off for now: to a phone whose Riar can open them, a push from our server carries what it says encrypted (Expo, Apple and Google can't read it) with the waiting reminder's random id and time instead of the item's id |
| Sinch (Sweden; its EU region) | Sending sign-in codes and one account warning before deletion by text message, if you sign in with your mobile number: only your number and the text with the code, or with the date an unused account will be deleted. Riar never uses your number for marketing and never shares it |
| Mailgun (Mailgun Technologies, Inc., a Sinch company, USA; its EU region) (not used yet: the forwarding address isn't in the app yet) | Receiving emails you forward to your personal Riar address and passing them straight to our server, with nothing stored by Mailgun for Riar |
| Lovable | Hosting the riar.ie website, its host statistics (totals only), and storing waitlist signups (hosted in the EU) |
| Zoho (Zoho Mail, EU data centre) | Our support@, privacy@, legal@ and security@riar.ie mailboxes: the emails you send us and our replies |
| Zoho (Zoho Campaigns, EU data centre) | Sending waitlist and beta emails from support@riar.ie, with open and click tracking switched off |
| Account email provider (an EU-based sender, named here before email code sign-in goes live) | Sending sign-in codes and account messages (such as a code to confirm a deletion request or a warning before an unused account is deleted, sent to your email if you sign in with one) from no-reply@riar.ie: only your email address and the message |
Your email. Emails Riar reads from your Outlook, and emails you forward, import or share, are used only to find the items you asked Riar to track. They are never used for advertising, never sold, never used to train AI models, and no person at Riar reads them unless you ask us to for support, it's needed for security, or the law requires it.
Comparing before you renew. Before a renewal or the end of a contract, Riar shows where you can compare: the regulators' own tools first (ComReg Compare for phone and broadband, the Health Insurance Authority for health insurance, and the CCPC for mortgages, loans and current accounts), the comparison sites the Commission for Regulation of Utilities accredits for electricity and gas, and a list of other providers to check. These are plain links that open in your browser, with no data shared and no tracking. Riar has no commercial or referral relationship with any of them and earns nothing if you switch. Some comparison sites are paid by providers when people switch through them; that is between them and the provider, never Riar.
We'd only disclose data if legally compelled to (for example, a valid court order). This hasn't happened, and we'd tell you if we were legally permitted to.
8. International data transfers
Our database (Supabase) is hosted in the EU. Parts of the service go outside the EEA: the AI that reads the text of your photos and emails, and quick adds Riar can't read on your phone (Anthropic, a US company, whose AI may run in any country where Anthropic operates), push notifications (Expo, Apple and Google), and checking subscriptions (RevenueCat, a US company, which receives only your Riar account's id and the store's purchase records).
Some processors (Anthropic, RevenueCat, Expo, Apple, Google, Microsoft and, once forwarding launches, Mailgun, whose service runs in its EU region but whose company is in the USA) process data outside the EEA as part of their own infrastructure. For each, we rely on the EU-US Data Privacy Framework where the company is certified, or on Standard Contractual Clauses, as required by GDPR Chapter V, and only ever send what's strictly necessary for the feature involved. Anthropic receives only the text of the email or photo being read, or the quick add you typed with today's date, never your account details, and doesn't use it to train models. Under its commercial terms Anthropic deletes what it received within 30 days, or keeps it for up to 2 years if its automated safety systems flag it as breaking its usage policy. The EU-US Data Privacy Framework is being challenged at the Court of Justice of the EU (case C-703/25 P); it stays valid until the Court decides, and where a processor also offers Standard Contractual Clauses we keep them in place.
When we move AI reading to Claude on Google Cloud in the EU, the text will be processed in EU member states. Google is part of a US group, so we'll rely on Google's EU-US Data Privacy Framework certification and the Standard Contractual Clauses in its cloud data processing terms, and before switching we'll assess the risk of a request from outside the EU (a transfer impact assessment).
You can ask us for a copy of the safeguards that apply to any transfer, using the contact details in Section 14.
The riar.ie website and the waitlist run on Lovable's Europe hosting region, and beta emails are sent through Zoho's EU data centre.
9. Retention, and your control over your data
You can delete your account in the app. Without the app, the page at riar.ie/delete-account explains how: email support@riar.ie from the email you sign in with, or with the mobile number you sign in with, plus your deletion code if you made one. With the code, we delete your account straight away. Without it, we first send a sign-in code to that email or number and ask you to read it back to us, so we know the account is yours. You can make the one-time deletion code in Settings, Account and sign-in (our servers keep only a scrambled copy of it, a hash). An account that hasn't been used for 24 months is deleted, after we warn you in the app and by email or text. If you delete your account, shared items you own disappear for the other people in your household, anyone helping you through "managing for" is told it has ended, your Sign in with Apple link is revoked, your Outlook access tokens are deleted (once the Outlook connection launches), and we ask RevenueCat to delete its record of your purchases. Deleting your account doesn't cancel a subscription: cancel it in the App Store or Google Play. If you own a household, it passes to the member you choose (or, if you don't choose, the member who joined first), and members keep their own items; if nobody else has joined, the household is deleted. You can also remove Riar from your Microsoft account under its app permissions.
Signing out keeps your reminders in your account, so nothing is deleted from our servers; Riar first sends any changes still on the phone. On your phone, you choose. Signing out asks whether to keep your reminders on that phone (the default: they stay in Riar's encrypted storage and keep reminding you there, but stop syncing until you sign in again) or remove them from it. Items other people share with you leave the phone either way, because your access to them ends. If you remove them, or delete your account, Riar clears its storage on that phone: your items, their dates and settings, the key that encrypts them, every reminder notification Riar has scheduled or shown, and any calendar file still in the app's temporary storage, after first removing the events the on-phone calendar added to your phone's calendar; if you remove them while some changes haven't reached your account, Riar asks first. One thing can stay: if you turned off "Share custom reminder totals" on that phone and it couldn't yet tell our servers (offline), Riar tries once more before clearing the phone, and if it still can't, keeps only a one-way fingerprint of your account id (not the id, and nothing else), so it can finish turning the switch off when you next sign in on that phone; until then your totals row stays on our servers, at most 12 months after it was last sent. Signing out another phone from Signed-in phones asks why: if it's lost, stolen or no longer used, Riar clears its storage on that phone the next time it opens Riar with a connection (we keep that choice, linked to that phone's sign-in, until then and for 30 days at most; the same fingerprint is kept there if a custom totals switch-off was still waiting, since that phone is no longer signed in to send it); if you still use it, it keeps its reminders and stops syncing. Signing in to a different account on a phone that still has someone's reminders asks first whether to add them to that account or remove them from the phone, so nothing is mixed without a yes. Uninstalling the app removes its storage too. Deleting a single item removes it from your phone straight away, and from our servers the next time your phone syncs.
The app's "Your data" screen shows what's stored and where your reminders came from. 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). Export and delete-all are one tap away whenever you want them.
We keep your data while your account is active. If you delete your account, we delete your data within 30 days: when you delete it in the app, it's deleted from our servers straight away. The exception is where we're legally required to keep something longer (for example, payment records, if you're a paying subscriber).
| Data | How long we keep it |
|---|---|
| Your account and items | While your account is open. Deleted straight away when you delete your account in the app, and within 30 days of a request by email |
| An account nobody uses (from launch) | Deleted after 24 months without use, once we've warned you in the app and by email or text, at least 30 days before. The text is one message to your sign-in mobile number (Irish mobiles), sent once, with the date we'll delete the account and no link; we don't delete before that date. To know, our servers keep the date you last opened Riar while signed in (updated at most once a day) and whether we've warned you; opening Riar again cancels the warning. We don't delete an unused account until a warning by email or text has gone |
| Your deletion code (from launch) | Only a scrambled copy (a hash) and the date you made it, replaced when you make a new code, deleted with your account. Your phone makes the code and shows it once; our servers never see the code itself until you use it to delete your account, and it's never logged |
| Your recovery key backup | Your phone makes your 12-word recovery key and keeps it, with your account key, in its own secure storage (this phone only). Our servers keep only your account key locked with a key that only those words can make, plus the random numbers needed to unlock it with them. We can't open it, and we never see the words. The backup also carries a code naming which account key it locks (a key id), so your other phones can tell when it changed. Your own reminders are encrypted only once you've seen and saved your words. Replaced when you make a new recovery key or start fresh. When you start fresh, the old backup is kept for 12 months, so your old words can still open your old reminders if you find them, and is then deleted (checked every night). Deleted with your account. Your phone forgets the key and the words when you sign out or delete your account |
| Your public key and your locked private key | Your phone also makes a pair of keys for your account, used from the household and helper updates before launch so the people you choose can share keys with you. The public half is kept on our servers with your account id; it's personal data tied to your account, but it opens nothing. Only the people in your household and the people you help, or who help you, can look it up. The private half is kept on our servers only locked with your account key, inside your recovery key backup, so it comes back with your 12 words; we can't open it. From the app it can only be replaced by the public key in your own recovery key backup (when you start fresh, or when your phone puts its own key back); with it we keep how many times it has changed and when it last changed, kept so a later version of Riar can show you a change you didn't make (no version shows it yet). Deleted with your account. The keys shared with you in a household, or between you and someone you help, are kept locked to your public key, and go when you leave, when the help ends, or with your account |
| Household key copies (from encrypted households, switched off for now) | One locked copy of the household key for each member and each key version, locked to that member's public key. Deleted when you leave the household or are turned away, and with your account; all of them go when the household ends. When someone leaves, the owner's phone makes a new key; the copies of earlier versions stay for the people who are still in the household, because reminders shared or handed back to their owner may still be locked with them, and go when each of them leaves |
| Helper keys (from encrypted helpers, switched off for now) | For each help: the key the person's phone made, one copy locked to the person and one to the helper; for each reminder the helper may see, that reminder's own key locked with it; whether the helper's phone said the 6-digit codes match, and when; and a mark on a reminder that must be locked again with a new key. We can't open any of them. A reminder kept private from helpers just has no helper key: the choice itself, and who added a reminder, are inside the encrypted reminder. The helper's copy and every locked reminder key go as soon as the help ends (from either side), and with either account; the reminders the helper could open are then locked again on the person's phone. A reminder the helper adds is kept like the person's other reminders |
| The household's name and first names (from encrypted households) | Locked on the owner's phone with the household key from the moment a household is started on the latest version of Riar (an older household keeps a readable name, and its members' profile first names, until it is converted; no conversion is built yet), so we can't read them and never receive them readable. The same locked details also hold 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 other members can't read it either, and shared between the owner's phones so each one vouches for the same people. Replaced each time the owner's phone makes a new key, which is also when someone who left is dropped from them. Deleted when the household ends |
| Shared reminders (from encrypted households) | The locked content and the metadata in Section 2a, kept like your other reminders: completed ones go 12 months after they're done unless the owner keeps them, and all of the owner's go with their account. When the owner leaves or is removed, or the household ends, a reminder stops being shared and goes back to its owner, whose phone locks it for them again; until then it keeps the household's id |
| A reminder's key for each person you share it with (from encrypted households) | When you share a reminder with chosen people, one locked copy of its key for each of them, locked to their public key so only they can open it, with the number of that key. Replaced each time you change who sees it (it gets a new key each time). Deleted when that person leaves the household, is removed or deletes their account (your phone then gives the reminder a new key for the others), when you share it with the whole household instead, with the reminder, and with your account |
| Locked reminders after you start fresh | If you start fresh without your recovery key, your old reminders stay on our servers, still encrypted, with a code naming the old key, for 12 months in case you find the key, and are then deleted (checked every night). Deleted with your account |
| Your items on your phone | In the app's private, encrypted storage until you delete them, sign out and choose to remove them from the phone, sign out that phone from another one as lost, stolen or no longer used, delete your account or uninstall the app. Signing out keeps them by default. On iPhone your own iCloud or computer backup holds an encrypted copy, like any app's data, until that backup is replaced, but the key isn't in the backup, so the copy can't be read on another phone; Android app backup is turned off. Items you marked done more than 12 months ago are deleted from your phone too, unless you keep them |
| Your custom reminder totals (built-in category names and counts, no wording), only if you turn on "Share custom reminder totals" | One row, replaced each time your phone sends it (at most once a week, while you're signed in). Deleted when you turn the switch off on any phone, when you delete your account, and 12 months after it was last sent if your phone stops sending (checked every night) |
| Whether you turned "Share custom reminder totals" on or off, and when (with a version counter that goes up by one each time your switch is set, even to what it already was: a change from your phone is applied only if the counter is still where your phone last saw it, so a turn-on or turn-off that arrives late can never undo a newer choice; your phone then shows what our servers hold) | One row for your account, changed each time you turn the switch on or off. Deleted with your account |
| Completed items | 12 months after you mark them done, unless you choose to keep them, on your phone and on our servers (our servers check every day) |
| A record that you deleted an item | When you delete an item, our servers keep only its random id, your account's id and the time for 30 days, so your other phones delete their copy too. Deleted straight away when you delete your account |
| Calendar contents during an import | Not stored. Read on your phone while the import screen is open; only the dates you tick are kept, as items |
| Outlook access tokens (when the Outlook connection launches; not in the app yet) | On your phone only, in its secure storage (never on Riar's servers). Deleted immediately when you disconnect Outlook, sign out (whether you keep your reminders on the phone or not) or delete everything |
| Fingerprints of Outlook messages already read (when the Outlook connection launches) | On your phone only: a one-way fingerprint of each message Riar has read, so a later check doesn't read it twice, and how many checks and AI sends couldn't read a message (Riar stops trying after 3 checks or 6 sends). Never the message, its id, sender or subject; pseudonymous rather than anonymous, as the same message always gives the same fingerprint. Kept up to a year, deleted when you disconnect Outlook, sign out or delete everything |
| Sign-in and warning texts | Riar keeps no copy of the text or the code, and for a warning text only when it went and the date it gave, deleted with your account; the code stops working after 10 minutes, with up to 5 tries an hour for each number. Sinch keeps the message only as long as our contract with them allows, to deliver it, deal with delivery problems and bill us |
| Emails read from Outlook, forwarded, imported or shared | Deleted once Riar has read them; only the items you confirm are kept |
| Text read by our AI provider | Riar keeps none of it. Anthropic deletes it within 30 days under its commercial terms, or keeps it up to 2 years if its automated safety systems flag it (Section 8) |
| Your forwarding address and what it finds (when the forwarding address launches; not in the app yet) | Our server makes your address from random characters and keeps only a one-way fingerprint of it made with a secret key (a keyed hash), never the address itself; a copy of the address locked so only your phones can open it; how many emails arrived today and today's date, only so the limit of 30 emails a day works (cleared each night after midnight (by about 4am Irish time); our server doesn't keep the day your last email arrived, and your phone works out "Is forwarding still on?" from what it has collected), how many emails from senders Riar doesn't recognise were kept for your phone today and today's date, only for the limit of 5 a day below (cleared each night after midnight, and when you turn forwarding off), and the day you last made a new address and how many you made that day (at most 5 a day). What Riar finds in a forwarded email, or the email's text when it can't be read yet (you haven't agreed to AI reading; it looks health-related and you haven't agreed to Riar reading health information; this month's allowance or Riar's monthly AI spending limit is used up; Riar's AI isn't available; or the AI couldn't read it), and the email's text when a PDF came with it (Riar's AI then doesn't read it on our server; our server only checks, in memory, who it is from and whether it looks like a bill or health-related, and your phone reads the text and the PDF together), is locked to your phone's key before it is stored, so Riar's server can't read it; it waits until your phone collects it and is deleted then, or after 14 days if your phone never does. The email itself is never stored. When a forwarded email has a PDF attached, the first PDF (up to 4 MB) is locked to your phone's key in the same way before it is stored, padded to one of three fixed sizes so its size says little about it, so Riar's server can't read it; it is read on your phone, not on our server, and is deleted from our server once your phone has collected it, when you turn forwarding off, or after 14 days, whichever comes first. Your phone keeps the locked PDF until it's read, for up to 14 days from when the email arrived, then deletes it; once its words are read, the PDF is deleted. Riar never keeps the PDF with a reminder. At most 20 such PDFs wait for your phone at a time; past that, a new PDF isn't kept (the email's text still is). Other attachments, and every attachment's file name, are never kept. On your phone, a forwarded email's text that couldn't be read yet waits as Not read yet for up to 14 days, whatever it was held for, the same as any PDF that came with it, showing only its sender and subject, and is sent to Riar's AI to be read only with your agreement to AI reading (and, for health-related email, your agreement to Riar reading health information), then deleted from your phone; Gmail's forwarding confirmation code stays on your phone only for as long as it is useful (shown for one day from when the email arrived, after which Riar drops its digits; forgotten when you leave the screen after copying it, and at most 30 days in any case); for "Is forwarding still on?" your phone keeps, in its own settings and never sent to us, when forwarding was first seen on there, when the last bill or held email arrived and when you chose Not now (deleted when you turn forwarding off, sign out and remove your reminders, or use Delete everything); and the ids of the results your phone has collected (random ids, nothing from the email) are remembered for 16 days and an hour so none is shown twice. Turning the address off or changing it stops the old one at once, and turning it off also deletes anything Riar found that your phone hasn't collected yet. Senders Riar reads: when you choose Always read from this sender on a forwarded email Riar held because it didn't recognise the sender, your phone sends that sender's address to our server (it does the same when you remove a sender, or undo a removal, so the server can find the fingerprint), which turns it into a fingerprint made with a secret key and your account's id (a keyed hash) and keeps only that, never the address (the address is used in memory for that moment and not stored or logged). The readable list stays on your phone. Mail from a sender Riar doesn't recognise is held unread, with no AI reading and nothing taken from your monthly email allowance (it still counts toward the 30 emails a day your address accepts), and its text waits on your phone as above until you choose to read it, add it yourself or ignore it. At most 5 such emails are kept for your phone a day, and only while fewer than 50 results are waiting for it; any more from senders Riar doesn't recognise that day are not kept at all: nothing is stored or sent to your phone, nothing is read, nothing is taken from your monthly email allowance, and the sender isn't told. Emails from billers on Riar's list and from senders you chose are never affected by this limit. The fingerprints are kept until you remove the sender (Remove on Senders Riar reads deletes it from your phone and our server), turn forwarding off, or delete your account; at most 50. If we change the secret key, fingerprints made with the old key are deleted once the change is finished (they could no longer match), and a sender you chose is then held once more until you choose Always read from this sender again. Sign out removes the list from your phone, not the fingerprints; Senders Riar reads offers Remove all for those. All of it is deleted with your account. To stop a forwarded email being processed twice, our server keeps one-way fingerprints of the email provider's one-time delivery code and of the email's message id (with your address's fingerprint) for a day. An email over 10 MB is turned away without being read and leaves no record |
| Waitlist name and email | Until the beta opens and you've had your invite; deleted within 3 months of that invite if you don't create an account, or straight away if you unsubscribe |
| Unsubscribe record | Your email address only, on our email provider's do-not-email list, kept so we never email you again by mistake |
| Your plan | Your current plan only, while it lasts; removed when it ends and when you delete your account. RevenueCat keeps the store's purchase records under our contract with them until you delete your account, when we ask RevenueCat to delete them; Apple or Google keep the payment records, and we keep payment records for tax for 6 years where the law requires |
| Crash reports | Kept by Apple and Google under their own terms; they don't name you |
| Push notification tokens | Deleted when you sign out on that phone (whether or not you keep its reminders) or delete your account |
| Reminders scheduled on your phone | Held by your phone's notification system until each one is shown; cleared when you delete the item, sign out and choose to remove them from the phone or delete your account. Items with hidden details carry only their type |
| Reminders waiting to be sent from our server | The item's random id, its type and send time only, deleted once sent, and never kept more than 24 hours after the time it was due to be sent. The push itself says only "You have a reminder". Built, switched off for now (encrypted notification contents): your phone may also send what the reminder should say, encrypted on your phone so only your phones can open it, under a random id it chooses; one waiting reminder may then cover several reminders due at the same time; and each phone's push token records whether that phone's Riar can open them (a yes or no, nothing else). The encrypted text is deleted with its row |
| Quick-add help count | Your account's id, the day and how many times Riar's AI helped with quick add that day, so the daily limit works; and a monthly total (on Household, on the household owner's account), so the monthly limit works. Never what you typed or said, or what the AI said. The daily count is deleted after 31 days and the monthly total after 400 days, or straight away when you delete your account |
| AI read count | Your account's id (or, on Household, the household owner's), the month, whether it was an email or a photo and how many of that kind Riar's AI read that month, so your monthly allowance works and This month can show it; and, for each past bills import, a random id, when it started and how many emails Riar's AI read in it, so the import limit works. Never what was read, the sender, the subject or what the AI said. Deleted after 400 days, or straight away when you delete your account |
| AI cost count | Your account's id (or, on Household, the household owner's), the month and what Riar's AI cost that month, in fractions of a cent, so a ceiling can stop misuse. Never what was read or what the AI said. Deleted after 400 days, or straight away when you delete your account. Each AI call also writes one line to our server's logs saying which feature it was, the AI model, how many tokens went in and out and what it cost, with no account id and nothing that was read; it's kept as long as the server logs (below) |
| Outlook read count (Plus and Household, when the Outlook connection launches) | Your account's id, a random id your phone makes for each Outlook check, whose allowance it counts on (on Household, the household owner's), when the check started and how many emails Riar's AI read in it, so Outlook's own limits work (emails a check, checks a day and a monthly total). It isn't your past bills import. Never the sender, subject or text of an email, or what the AI said. Deleted after 60 days, or straight away when you delete your account |
| Daily usage totals (no names, no item details) | 24 months |
| Items waiting in "Check these", including emails waiting as Not read yet | On your phone only, until you confirm or dismiss them (or, for Not read yet, until Riar reads them), and at most 30 days; Not read yet (only email: a photo or share never waits for the AI): a forwarded email, and any PDF that came with it, at most 14 days, whatever it was held for; an Outlook email over a limit, of which only its sender and subject wait here (the email stays in your Outlook), at most 35 days, so it is still here when the monthly limit resets: anything older is deleted from your phone when you next open Riar. Words of a photo or share that an earlier version of the app kept waiting are deleted from your phone the first time the updated app opens |
| Your data export | Made on your phone; no copy is kept on our servers. The file stays in the app's own storage until your next export, signing out (either way) or Delete everything |
| A photo or PDF kept with a reminder before 8 November 2026 (Riar no longer keeps files) | On your phone only, in Riar's encrypted storage, until you remove it or delete the reminder, sign out and choose to remove them from the phone or use Delete everything; a completed reminder's goes with it after 12 months unless you keep it. Never on our servers. An open copy, made so your phone can show or share it, is deleted when you close it |
| What your widgets show | Saved on your phone only while you have a Riar widget: the titles and days of tonight's reminder and the next three (types only for anything hidden on the lock screen). Replaced with every change, and emptied when you sign out and remove your reminders from the phone, or use Delete everything |
| A calendar file you make | Made on your phone and never uploaded. It stays in the app's own storage until you make a new one or sign out (either way); any copy you save or share is yours |
| Household invites and "managing for" request links | A scrambled copy (a hash) of the link, who made it and when it was used, cancelled or expired. From encrypted households, an invite also holds the owner's and the joiner's first names, locked with the link's secret, and the joiner's public key as it was when they joined (so the code can be worked out); the joiner's locked name and key are cleared as soon as they leave, are turned away or delete their account. An invite can also be a new link for someone who is already in the household and can't open its reminders (for example after they started fresh): it holds the same things, plus a mark that it is for someone already in the household, with no name for that person; when the owner confirms it, that member's key copies are replaced. From encrypted helpers, a request link also holds the helper's and the person's first names, locked with the link's secret; the person's is cleared when the help ends or with their account. Deleted 30 days after it stops working, and the invites you made go with your account |
| Ended "managing for" | Who helped whom and when it ended, deleted 30 days after it ends. The consent record stays, withdrawn, while the account is open |
| A phone you signed out from another phone | Whether to clear Riar from it, until that phone next opens Riar, and at most 30 days |
| Done, snoozed or "not relevant" choices | 12 months, used only so Riar doesn't suggest the same thing again. When you say "Not a reminder" to something Riar read, your phone keeps only the sender's name (such as "Electric Ireland") and how many times, so after 3 Riar stops offering what it isn't sure about from that sender. You can show it again in Settings, Suggestions |
| Website visit counts (daily totals, no identifiers) | 24 months |
| Server logs (our host's request logs, including IP addresses) | 7 days, once that setting is confirmed on our live servers; until then at most 30 days |
| Sign-in records (our sign-in provider's log of each sign-in: your email address or phone number, IP address and time) | 7 days (checked every night) |
| Signed-in phones (for each phone you are signed in on, our sign-in provider keeps a session id, dates, whether it is an iPhone or an Android phone and the IP address that phone last connected from, so a sign-in can be shown and ended; separate from the two rows above) | For as long as that phone stays signed in. It goes when you sign that phone out, when the sign-in otherwise ends, or straight away when you delete your account |
| Your access list (what our servers can know about who and what reached your account; no IP address, place, name or reminder content) | 30 days (deleted every night), and straight away when you delete your account |
| Consent records (Health, AI, calendar) | While your account is open, so we can show when you agreed |
| Encrypted backups | Up to 35 days, after which deleted data is gone from backups too |
| Emails you send us, including reports | 2 years after your last message. A report we act on is logged without your name or email address |
| Payment records (paid tiers only) | 6 years, as Irish tax law requires |
We don't keep a copy of your inbox or of the emails you forward, import or share. Once the Outlook connection and the forwarding address launch (they aren't in the app yet), disconnecting Outlook deletes the access tokens from your phone immediately (they were never on Riar's servers), and you can reset your forwarding address at any time, and the old one stops working.
Waitlist details are kept until the beta opens and you've received your invite. If you don't go on to create an account, we delete them within 3 months of that invite. If you unsubscribe, we remove you from the list straight away and keep only your email address on the do-not-email list described in Section 3.
10. Security
- Outlook (not in the app yet) will connect with read-only access only: Riar can never send, delete or move email. Riar never asks for your email password and doesn't connect to Gmail; for other providers it only sees the emails you choose to forward, import or share.
- Data is encrypted in transit (HTTPS only) and at rest. On our servers (Supabase, in the EU) the database and its backups are encrypted, and Row Level Security means each account can reach only its own items and the items shared with it.
- On top of that, payment amounts, and the titles and notes of health items and anything you mark Sensitive, are encrypted again on their own (AES-256) before they're stored on our servers. The key is kept apart from the data in Supabase's secure vault, so these details can't be read from the database or its backups without it. In the app, they're shown only to you and to the people you share an item with.
- Reminders are scheduled on-device, so they fire reliably even without a network connection, and don't depend on our servers being reachable. On your phone, Riar keeps your items in an encrypted database. Its key is made on your phone and kept in your phone's secure keychain or keystore: it never leaves your phone, never reaches our servers and isn't in your backups. So if you move to a new phone from a backup, Riar starts empty there and, if you have an account, gets your items back from our servers. Underneath, Riar's storage is private to the app and protected by your phone's own encryption, which works with your passcode: on iPhone, Data Protection keeps it unreadable until the phone is first unlocked after a restart; on Android, the app's storage is sandboxed and encrypted on every phone Riar supports (Android 10 or later). Use a passcode on your phone: it's what protects everything on it, Riar included.
- Sign-in details on your phone are kept in its secure keychain or keystore (on iPhone, this device only, so never in a backup), never in ordinary app storage. Signing out deletes them; it clears Riar's storage on your phone too if you choose to remove your reminders from it.
- Your own reminders and their date changes are encrypted on your phone before they leave it, with keys only your phones hold, once you've saved your recovery key (Section 2a). Coming before launch: reminders shared in a household, a helper's reminders, your settings and your phones' names encrypted the same way, and pushes our server can't read (Section 2a). Until then, the points above are what protects them.
- Access to production data is restricted to what's needed to run the service; we run a formal Data Protection Impact Assessment for higher-risk processing (such as the Health pack) before launch.
- If something goes wrong. We record every personal data breach. If one is likely to put your rights at risk, we tell the Data Protection Commission within 72 hours of finding out (Article 33 GDPR), and if it's likely to put you at high risk, we tell you directly without undue delay, with what happened and what to do (Article 34).
What's in place today, in short:
- On your phone: your items are kept in a database encrypted with SQLCipher. The key is made on your phone and kept in the iPhone Keychain or the Android Keystore; it never leaves the phone.
- On our servers: Supabase, in Ireland, with Row Level Security turned on for every table, so each account reaches only its own items and the items shared with it.
- Encrypted again on their own: amounts, who money owed is from, price change notices, and the titles and notes of health items and anything you mark Sensitive, with AES-256 (PostgreSQL's pgcrypto). The key is kept apart in Supabase Vault and used only by database functions the app can't call directly.
- Before the AI: nothing personal goes to the AI until you've agreed, and before any text does, our server removes PPS numbers, card and bank account numbers, passport numbers, passwords and codes, email addresses and Eircodes (see Section 6).
- No tracking: Riar has no analytics or crash-reporting tool in the app.
- Logs: our server functions log only short event names and counts (such as "found 2" or "monthly limit reached"), never what your items or emails say. How long the logs are kept is in Section 9.
[Each point in this section is confirmed against the build before launch, and the access control model and incident response process are added here]
11. Your rights
Under GDPR and the Irish Data Protection Act 2018, you can:
- Access the data we hold about you (also available directly in-app via "Your data")
- Correct anything that's wrong
- Delete your data (also available in-app, one tap)
- Restrict or object to certain processing
- Take your data with you in a portable format (export, also in-app)
- Withdraw consent at any time for anything based on consent, without affecting what happened before
- Complain to the Data Protection Commission if you think we've got something wrong (see Section 14)
Your right to object. Where we rely on legitimate interests (Section 3), you can object at any time, for reasons to do with your situation, and we'll stop unless we have compelling grounds that override your interests or need it for a legal claim. Email privacy@riar.ie.
Most of these you can do yourself, instantly, in the app. For anything else, contact us using the details in Section 14 and we'll respond within one month, as GDPR requires (we can extend that by two more months for a complex request, and we'll tell you why within the first month). We may ask you to confirm the request comes from you, for example with a sign-in code sent to your sign-in email or number.
How your rights work when your reminders are encrypted. Your export (Settings, Your data) is made on your phone and holds your reminders, their date changes, your settings, your sign-in methods and anything you kept with a reminder, as a spreadsheet and a full copy in JSON. Some things only our servers hold: for example the dates on your account, your plan, the counts behind your AI limits, your consent records, your access list, the fingerprints of senders you chose to read and your signed-in phones. Ask privacy@riar.ie and we'll send you a copy of those. Content locked to your phone's key we can only give you as it's stored, encrypted, because we can't open it; your phone is where it can be read. Deleting your account deletes all of it from our servers, encrypted copies included, and from our backups within 35 days. If we correct or delete something because you asked, we tell anyone we shared it with, unless that's impossible or would take disproportionate effort (Article 19).
To stop beta emails, use the unsubscribe link in any of them, or reply with "unsubscribe".
12. Cookies and the website
The Riar app itself doesn't use cookies, because it's a mobile app, not a browser. Riar's code on our website (riar.ie) sets no cookies, stores nothing on your device and runs no advertising trackers or analytics scripts. Its fonts are served from our own site rather than from Google, so visiting it doesn't send your IP address to any third party beyond our host.
Website visit counts. To see whether the site works, riar.ie keeps simple daily counts: how many times each page was viewed, how many times someone tried the reminder demo, and how many people joined the waitlist. Each count is just a date, a page, an event name and a number. These counts record no IP address, browser, device, the page you came from or any identifier, so they can't be linked to you or anyone else, and nothing is stored on your device. The counts are kept on our host (Lovable) and deleted after 24 months. We rely on legitimate interests (Art. 6(1)(f)): knowing whether the website is working, with no effect on you.
Host statistics. Lovable, which hosts riar.ie, counts visits from the requests your browser makes: the pages viewed, the site that sent you, whether you're on a phone or a computer, and your country. We only see daily totals in Lovable's dashboard, never who visited, and Riar adds no analytics script for this. We rely on the same legitimate interests.
The waitlist section also shows how many of the first 100 beta places are left. That's a single number worked out from the signups; nobody visiting the site can see who signed up.
13. Changes to this policy
We'll update this policy as the product changes, and the date at the top will always show the latest revision. If a change is material, we'll tell you directly in the app rather than relying on you checking this page.
14. How to contact us, and how to complain
For anything to do with your data or this policy: privacy@riar.ie.
If you're not satisfied with our response, you have the right to lodge a complaint with Ireland's Data Protection Commission:
Data Protection Commission21 Fitzwilliam Square South
Dublin 2, D02 RD28
Ireland
www.dataprotection.ie