Privacy Policy

Last updated: 31 July 2026 · Version 1.6

This policy explains what personal information we collect when you use the RemindMeVoice website, app and device, why we collect it, who we share it with, and the rights you have over it. We've tried to write it in plain English rather than legalese.

1. Who we are

RemindMeVoice is a trading name of Cornerwise Studio Ltd, a company registered in England and Wales.

• Company number: 17248795
• Registered office: 82a James Carter Road, Mildenhall, IP28 7DE
• Contact: hello@remindmevoice.com

For the purposes of UK data protection law (the UK General Data Protection Regulation and the Data Protection Act 2018), Cornerwise Studio Ltd is the data controller of the personal information described in this policy.

2. Information we collect

2.1 When you visit the website

• Your IP address and basic technical information (browser, device type), used for security and to keep the site working.
• Cookies for analytics — only if you accept them via the cookie banner. See section 8 for details.
• If you fill in the "Register interest" form: your email address, the optional note you wrote about who you're hoping to support, and whether you ticked the early-tester box.
• If you use the "Ask anything" chat assistant: the messages you type. These are sent to our AI provider (Anthropic) to generate a reply and are not stored by us. Please don't enter personal or health details — the assistant is designed for general questions about the product, not advice.

2.2 When you create an account in the app

• Email address and password (the password is handled by Google Firebase Authentication; we never see it in plain text).
• The name and time zone you set on the profile of the person you care for.
• The events you add to the calendar — including titles, dates, times and any notes. If you enter information that relates to someone's health (for example, "GP appointment" or a medication name), that becomes special-category personal data — see section 4.
• The email addresses of any other caregivers you invite to the account.
• Account activity timestamps (last sign-in, account creation date) for security and support.
• If you use the in-app help assistant: the messages you type, plus the account details needed to answer them — the name of the person you care for, their upcoming calendar events (including titles and times), their reminder and voice settings, subscription status, and details of their button(s) (room labels, device identifiers, and when each was last pressed). These are sent to our AI provider (Anthropic) to generate a reply and are not stored by us. Because calendar events can relate to someone's health (for example, "GP appointment"), this may include special-category personal data — see section 4.

2.3 When a device is in use

• A device identifier (derived from the device's hardware MAC address) and which account it belongs to.
• Heartbeat data: the time the device last contacted our servers, its firmware version, and basic connectivity status.
• The time the button was pressed and a reference to the audio that was played. We do not record any audio — our software never uses the device's microphone, and a physical switch on the device turns the microphone off entirely if you want the extra reassurance.
• The Wi-Fi network name and password you enter during setup are stored only on the device itself, never transmitted to our servers.

2.4 When you buy a device or subscribe

• Your name, delivery address and phone number (for the courier), collected by our payment provider Stripe at checkout and shared with us so we can post your button.
• Your order history and subscription status.
• Your card details are handled entirely by Stripe — we never see the full number. Stripe also uses payment data for its own fraud prevention, for which it is a separate data controller (see Stripe's privacy policy).
• Order and payment records are kept with our tax records (see section 7).

2.5 When you contact us

If you email us, we keep the email and our reply so we can help you and refer back to it later.

3. Why we use your information (lawful bases)

What for	Lawful basis (UK GDPR)
Sending you the occasional update if you joined the mailing list	Your consent (you ticked the form)
Running your account: storing events, syncing the button, generating spoken summaries	Performance of a contract with you
Operating the device: heartbeat, registration, audio caching	Performance of a contract with you
Site analytics (page views, basic engagement)	Your consent via the cookie banner
Answering your questions in the website "Ask anything" chat and the in-app help assistant	Our legitimate interest in responding to your enquiry and helping you use the service (and, where a calendar event you ask about reveals health information, your explicit consent — see section 4)
Security, fraud prevention, abuse detection, debugging	Our legitimate interests in keeping the service safe and working (and, where the information involved reveals health details, your explicit consent — see section 4)
Replying to your emails and providing support	Our legitimate interest in helping our users (and, where the information involved reveals health details, your explicit consent — see section 4)
Complying with the law (tax records, lawful requests)	Legal obligation

4. Information about the person you care for, and special-category data

RemindMeVoice is designed so that a caregiver — typically a family member — manages an account on behalf of an older adult (the person you care for), who is usually the person actually pressing the button. They themselves do not normally have an account with us.

Some information you enter about the person you care for may be sensitive. In particular, calendar events that mention appointments with healthcare professionals, medication, or health conditions are special category personal data under Article 9 of the UK GDPR. We rely on your explicit consent as the lawful basis for processing this kind of information, given by you on behalf of the person you care for when you set up their profile in the app (we ask you to tick a box confirming this, and keep a record of when you did). This consent also covers our processing it to run the service — for example, voicing it through the button, and sending the relevant calendar details to our AI provider (Anthropic) when you ask the in-app help assistant about the calendar. Where the wording you agreed to says so, it also covers sending those details to that same provider when we need to look into a problem with the service. For accounts set up before we added that wording, we rely instead on our legitimate interest in keeping the service working, and we avoid looking at health-related details unless the problem genuinely requires it (see sections 3, 5 and 6).

By creating an account and entering information about another person, you confirm that you have the authority to do so — typically as a close family member, legal representative or under a Lasting Power of Attorney. If at any point you no longer have that authority, please delete the account or contact us so we can help.

You can keep things simple by avoiding clinical detail. For example, "Tablets — kitchen" works just as well as the medicine's name.

RemindMeVoice stores what you enter and plays it back — we don't review, verify or interpret it, and it isn't medical advice. Responsibility for the information you enter sits with you, as set out in section 12 of our Terms of Use.

5. Who we share your information with

We do not sell personal data. The one advertising-related exception is that, only if you accept advertising cookies, we share a limited amount of data with Google to measure whether our ads led to a sign-up or purchase (see section 8). We do not otherwise share your data with advertisers. We do use a small number of trusted suppliers ("processors") to run the service. They are only allowed to use your data for the purposes we set, under written data-processing agreements.

Supplier	What they do for us
Google / Firebase	Hosting, authentication, database (Firestore), file storage, Cloud Functions, and text-to-speech (Cloud TTS).
Resend	Sending operational and notification emails.
Stripe	Taking payment when you buy a device or subscribe, and collecting your delivery address at checkout. For most of this Stripe acts on our instructions; for its own fraud prevention and legal compliance it acts as a separate controller under its own privacy policy.
Anthropic	Two things. First, it powers our chat assistants — the website "Ask anything" chat and the in-app help assistant. It processes the messages you type and, for the in-app assistant, the account details needed to answer them (the cared-for person's name, their upcoming calendar events, reminder/voice settings, subscription status, and button details such as room labels and last-pressed times — which can include health-related calendar information). Second, it provides the AI-assisted developer tools we use to build the service and diagnose faults, which can involve your account data — including, where a calendar event relates to someone's health, the kind of information described in section 4. In both cases Anthropic does not use this data to train its models, and may retain it only briefly for safety and abuse monitoring. We do not store the assistant conversations at all. Records of developer-tool sessions are kept on our own systems and cleared periodically — see section 7.

We may also share information when we are required to by law (for example, a valid court order), or where it is necessary to protect someone's life or safety.

6. International transfers

Some of our suppliers — in particular Google, and Anthropic (operated from the United States, whose AI services power both our chat assistants and the developer tools we use to build the service and fix faults) — may process your data on servers located outside the UK. For the in-app assistant, and when we diagnose a fault, this can include account details and health-related calendar information (see sections 2.2 and 4). Where this happens, the transfer is protected using the UK International Data Transfer Agreement (IDTA) or the EU Standard Contractual Clauses combined with the UK Addendum, which are the safeguards recognised under UK GDPR.

7. How long we keep it

What	How long
Mailing-list signups (email, optional note)	Until you unsubscribe, or 24 months without any contact from us — whichever comes first.
Account data (profile, calendar events, members)	For as long as your account exists. After deletion, residual copies in our disaster-recovery backups are kept beyond use and erased within 30 days.
Device telemetry (last-seen, firmware version)	The most recent values are kept while the device is in service.
Button-press history, and records of any inactivity alerts we sent you	Kept for as long as your account exists, so you and the other caregivers can look back at activity patterns over time (this is what the Activity page shows). Deleted when the account is deleted, with residual backup copies erased within 30 days as above.
Operational server logs (security, abuse prevention, debugging)	Around 30 days, then deleted automatically.
Cached audio files	Up to 30 days from last use, then automatically deleted.
Chat-assistant conversations (website "Ask anything" and the in-app help assistant, including any account details the in-app assistant sends to answer you)	Not stored by us. Our AI provider may retain them briefly (up to 30 days) for safety and abuse monitoring, then deletes them.
Records of developer-tool sessions used to diagnose a fault (see section 5)	Kept on our own systems only while they are useful for investigating and fixing problems, and cleared periodically. We don't currently work to a fixed schedule for these; if you want yours removed sooner, ask us.
Support emails	24 months from the last reply.
Orders and delivery details	Kept with our accounting records for the period tax law requires (typically 6 years).
Records we are required to keep by law (e.g. tax)	For the period required by law (typically 6 years).

8. Cookies and similar technologies

We use a small number of cookies and similar storage on your device. You will see a banner on your first visit where you can accept or reject the optional ones. You can change your mind at any time via the "Manage cookies" link in the footer of our website, or on the Settings page in the app.

Cookie / storage	Purpose	Type
rmv-cookie-consent	Remembers your cookie choice so we don't keep asking.	Strictly necessary (no consent required)
Firebase Authentication session	Keeps you signed in to the app.	Strictly necessary
Google Analytics (_ga, _ga_*)	Counts visits and basic engagement across our website and app — which pages and features are used — so we know what's useful. No advertising profile is built from it.	Optional — only set with your consent
Google Ads (_gcl_*, rmv_gclid)	Measures whether clicking one of our ads led to a sign-up or purchase, so we can tell which ads are worthwhile. To match a sign-up to an ad click, a hashed (one-way scrambled) version of your email may be sent to Google. No advertising profile is built about you. See Google's Privacy Policy for how Google handles this data.	Optional — only set with your consent

9. Your rights

You have the following rights over your personal information:

• Access — ask for a copy of the data we hold about you.
• Rectification — ask us to correct anything that is wrong.
• Erasure — ask us to delete your data. You can also delete your account yourself in the app: that removes all of the account's data straight away, and your sign-in (your email and login) stays only until you ask us to remove that too — one email and we'll do the rest.
• Restriction — ask us to pause processing while we sort something out.
• Portability — ask for your data in a portable format (we'll provide a JSON export).
• Objection — object to processing we do on a legitimate-interests basis.
• Withdraw consent — for anything based on consent, you can change your mind any time.
• Complain to the ICO — see section 12. We'd like the chance to fix things first, but you don't have to ask us first.

To exercise any of these rights, email hello@remindmevoice.com. We aim to respond within a week and at the latest within one month, as required by law. The service is free.

10. Children

RemindMeVoice is not directed at children. We do not knowingly collect personal information about anyone under 16. If you believe a child has signed up, please contact us so we can remove the account.

11. Security

All traffic between your browser, the device and our servers is encrypted over HTTPS. Account passwords are handled by Google Firebase Authentication using industry-standard hashing — we never see them. Access to production systems is limited to the founder. No system is perfectly secure, but we take it seriously and will tell affected users without undue delay if a breach ever puts personal data at risk, as required by law.

12. Complaints

If you're unhappy with how we've handled your information, please contact us first at hello@remindmevoice.com — we'd like the chance to put it right. You also have the right to complain to the UK Information Commissioner's Office (ICO):

• Website: ico.org.uk/make-a-complaint
• Helpline: 0303 123 1113

13. Changes to this policy

If we change how we handle your data in a meaningful way, we'll update this page and bump the "Last updated" date at the top. If the change affects you directly and we hold your email address, we'll email you about it.