Your data.
Clearly explained.
PRIVACY NOTICE · VERSION 2026-10-16 · LAST UPDATED 16 OCTOBER 2026
Meet Ror turns the services you choose to connect into one daily briefing. This notice explains what personal data we use, why we use it, who receives it and the choices you have.
You choose which health, mail, workspace, location and market sources to connect.
We do not sell personal data or use health data for advertising, marketing or data-broker profiling.
Use the connection control where available, revoke access with the original provider, or ask us to remove it.
1. Who we are
Meet Ror is the data controller for personal data used to provide the Meet Ror website and iPhone app. Meet Ror is currently operated in the United Kingdom. For privacy questions or to exercise a data-protection right, email admin@meetror.com with “Privacy request” in the subject line.
This notice applies to the website, mobile app, widgets, daily briefings, support channels and optional connections offered by Meet Ror. A connected provider also handles data under its own privacy notice.
2. The personal data we use
What we use depends on the features you select. You can use Meet Ror without enabling every connection.
Account and profile
- Email address, account identifier and authentication session information.
- Early-access registration, verification status and a securely hashed, short-lived verification code when code verification is enabled.
- Your display name, time zone, onboarding progress and account settings.
- Briefing length, voice, scheduling and wake-time preferences.
- Consent records, connection status, selected plan, subscription status, trial dates, access grants and usage counts.
Locations, travel and markets
- Weather places and coordinates you select.
- Commute origin, destination, travel days, arrival time, route timing, traffic delay and roads returned for the route.
- Up to three market symbols on your watch list and the public quotes returned for them.
Connected health and fitness
- WHOOP data such as recovery, sleep, HRV and resting heart rate.
- Oura Ring data such as readiness, sleep, HRV and resting heart rate.
- Apple Health sleep duration and stages, heart-rate variability and resting heart rate. The iPhone app reads raw HealthKit samples on the device and uploads one daily summary, not the raw samples.
- Connection identifiers, permissions, sync times and encrypted authorisation credentials.
Health and fitness information can be special category data under UK data-protection law. It is optional and used only after you give explicit consent.
Mailboxes
- Mailbox provider, account email, account label, connection status, permissions and encrypted OAuth token or IMAP credential.
- For recent inbox items: sender, recipients, subject, time received, read, flagged and reply indicators, and a short preview where Gmail or Microsoft makes one available.
- Meet Ror reads mail in read-only mode to rank likely important messages. It does not create a separate archive of full messages or attachments.
Workspaces, calendars and reminders
- Slackbot reminder notifications, recent Microsoft Teams chat messages checked for likely reminders, or selected Google Workspace task and calendar information.
- For Apple Calendar and Reminders: title, source label, type, scheduled time and all-day status for a limited set of upcoming items.
- Apple event identifiers are hashed on the device. Notes, event locations, attendees and raw calendar identifiers are not uploaded by the iPhone app.
Briefings, support and technical data
- Generated briefing text, the sources available for that briefing and generation time.
- Support messages, issue reports and any information you include in them.
- IP address, browser or device information, request time and limited security and reliability logs created by our hosting providers.
3. Where the data comes from
We receive data directly from you when you join the early-access list, create an account, choose settings, enter locations or contact support. Subscription status comes from Stripe or Apple when you purchase through that provider. We receive connected-service data from the provider you authorise, including WHOOP, Oura Ring, Apple Health, Google, Microsoft, Slack and your mailbox provider. Weather, route, market and major-news information comes from the public-data providers listed below.
4. Why we use data and our lawful bases
| Purpose | Data involved | UK GDPR basis |
|---|---|---|
| Create and secure your account | Account, profile, session and security data | Contract, and legitimate interests in protecting the service |
| Create your account and send a verification code | Email address, signup status, verification challenge and delivery information | Your request to take steps before entering a contract; legitimate interests in preventing abuse |
| Manage trials, subscriptions and paid access | Selected plan, provider, trial dates, payment status and transaction identifiers | Contract; legal obligation for required transaction records |
| Provide the briefing, scheduling and features you request | Preferences, personal briefing instructions, connected-service summaries, locations, commute, reminders, mail signals, markets and generated briefings | Contract for core features; consent for optional connections |
| Use health and fitness information in your briefing | Selected WHOOP, Oura Ring or Apple Health fields | Consent under Article 6(1)(a) and explicit consent under Article 9(2)(a) |
| Operate, troubleshoot and protect Meet Ror | Connection state, limited logs, usage counts and error information | Legitimate interests in reliability, fraud prevention and security |
| Respond to support and privacy requests | Account details, request content and relevant service records | Contract, legitimate interests and legal obligation where applicable |
| Meet legal and regulatory duties | Records reasonably required for the relevant duty or claim | Legal obligation and legitimate interests in establishing or defending legal claims |
You must provide an email address and authentication information to create and secure an account. Other profile fields and every connected source are optional, although a feature cannot work without the information it needs. We do not use personal data for third-party advertising or sell it.
5. AI generation and spoken briefings
Health AI processing requires a separate, explicit permission, not merely agreement to our terms or connection of a wearable. Review, grant or withdraw health AI permission here. Withdrawal stops new health AI requests after it is recorded; it cannot undo a request already sent or automatically erase saved transcripts, audio, backups or provider records. Use account deletion controls or contact admin@meetror.com to request erasure, subject to applicable exceptions.
Briefing data is processed on servers and is not end-to-end encrypted. Administrators with sufficient system privileges may technically access stored briefing text and audio. Access must be restricted to a necessary, authorised service, support, security or legal purpose, not personal curiosity. We do not claim that an API connection means zero provider retention or that provider contracts and settings alone guarantee compliance.
Meet Ror uses Anthropic to turn the enabled signals into concise briefing text. Major-news candidates are discovered through GDELT and official GDACS disaster alerts, then filtered to high-impact world events and events affecting the country you select. The request to Anthropic can contain your first name, personal briefing instructions you choose to save, and the minimum relevant health summary, weather, mail metadata or preview, reminder text, market quote, selected news headlines and derived commute timing needed for that briefing. OAuth tokens, mailbox passwords and full email attachments are not included in the AI prompt.
When a premium spoken briefing is prepared, the generated briefing text is sent to ElevenLabs to create audio. The latest audio may be held in a private, user-specific cache so reopening the same briefing does not send it for voice generation again. It is served only through an authenticated request and is replaced when a different briefing is voiced. If ElevenLabs or the cache is unavailable, your browser or device may read the text using its built-in speech feature. Meet Ror does not use briefing data to make solely automated decisions with legal or similarly significant effects. Briefings are informational and are not medical, financial, legal or emergency advice.
7. International transfers
Some providers may process data outside the United Kingdom, including in the United States. Where UK law treats this as a restricted transfer, we use an applicable safeguard such as UK adequacy regulations, the UK Extension to the EU-US Data Privacy Framework where available, the UK International Data Transfer Agreement or the UK Addendum to standard contractual clauses. You may ask us for more information about the safeguard used for a particular provider.
8. How we protect data
Meet Ror uses encrypted network connections, authenticated encryption for stored OAuth and IMAP credentials, server-only access to credential stores, and database row-level controls that restrict user-owned records to the authenticated account. We minimise the data requested from connected providers and do not place credentials in briefing prompts or return them to the interface. No online service can guarantee absolute security, so we also limit access and review safeguards as the service develops.
9. How long we keep data
We keep personal data only for as long as needed for the purpose described, then delete or anonymise it unless law requires longer retention.
- Account, profile and preferences: while your account is active and for the limited period needed to complete a deletion request, resolve disputes or meet legal duties.
- Early-access registration: until you unsubscribe, ask us to remove it, or the purpose of the list ends. Used verification challenges expire after ten minutes and are removed under the service's cleanup schedule.
- Subscription and transaction records: for the life of the account and as long as reasonably needed for accounting, tax, fraud prevention, disputes and legal duties.
- OAuth and mailbox credentials: until you disconnect the provider, replace the connection or delete the account. Disconnecting removes the stored credential record from Meet Ror.
- Apple Health daily summaries: while Apple Health remains connected. Disconnecting Apple Health deletes stored daily summaries from the active database.
- Apple Calendar and Reminders summaries: replaced when the iPhone app next syncs and deleted when that connection is removed.
- Mail and third-party live data: fetched when needed. We do not keep a separate full-message, weather, route, quote or provider-health archive, although selected details may appear in generated briefing text.
- Generated briefing text: saved for replay and to avoid unnecessary regeneration, with an expiry determined by the selected plan. Expiry stops the briefing being reused by the generation and cloud-voice endpoints; it is not a promise of physical erasure from databases or backups at that instant. Automated production erasure schedules still require verification. You can request earlier deletion through account controls or admin@meetror.com.
- Consent evidence: versioned grant and withdrawal events contain account identifiers, permission types and timestamps, not health measurements or prompt text. These records are kept while the account exists to evidence your choices and are removed with permanent account deletion.
- Generated briefing audio: only the latest premium audio cache is retained for an active user. It is replaced when a different briefing is voiced and removed when the account is deleted or earlier on request.
- Support and operational records: for as long as reasonably needed to resolve the request, maintain security and establish or defend legal claims.
Encrypted backups and provider logs may remain for a short additional period under the provider's backup or security schedule before being overwritten.
10. Your controls
- Change your name, time zone, briefing time, enabled sources and any saved personal briefing instructions in account settings.
- Use Meet Ror's connection control where available, revoke access in the provider's own account settings, or ask us to remove the stored connection.
- For Apple Health, change Meet Ror's permissions in the Health app. Removing Health permission stops future collection; disconnecting in Meet Ror also removes stored daily summaries.
- Turn off scheduled briefings, weather, commute, markets or major news without deleting your account.
- Request a copy, correction or deletion of your data using the contact details above.
- Connect only accounts you own or are authorised to use, particularly an employer's mailbox or workspace.
11. Your data-protection rights
Depending on the circumstances, UK data-protection law gives you rights to be informed, access your personal data, correct it, erase it, restrict its use, receive portable data and object to certain processing. Where we rely on consent, you can withdraw it at any time without affecting processing that was lawful before withdrawal. Some rights are limited by law and depend on our lawful basis.
You have the right to object to processing based on legitimate interests. Tell us what you object to and why, and we will stop unless we demonstrate compelling legitimate grounds or need the data for legal claims.
Email admin@meetror.com to exercise a right. We may need to verify your identity and normally respond within one month. You may also complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint, although we would appreciate the chance to address your concern first.
12. Account deletion
You can permanently delete your account from the account area on the website or in the Meet Ror iPhone app. We explain what will be removed and require confirmation. Deletion removes the active account, profile, connected credentials, preferences and saved briefing history and cannot be undone. Future website subscription renewals are stopped before account deletion. Subscriptions billed by Apple must be cancelled in your Apple Account subscription settings. Resetting your account instead removes connected data and preferences while preserving your login, subscription, billing and usage records.
If you cannot access the app, email admin@meetror.com from your account email. We may retain limited transaction, security or legal records where required, and will explain that retention when applicable. Optional exit feedback is stored without your name, email or account identifier.
14. Children
Meet Ror is intended for adults and is not directed to anyone under 18. Do not create an account or connect another person's health, mailbox or workspace data if you are under 18. If we learn that a child's information has been provided, we will take steps to delete it.
15. Changes to this notice
We will update this notice when Meet Ror's features, providers or legal obligations change. We will publish the new date and version here and, where a change materially affects consent-based processing, ask you to review it before continuing that feature.
16. Email and marketing choices
We send requested verification messages and essential account and billing notices. Optional product emails require a separate, unticked opt-in, which can be withdrawn in Account or through the unsubscribe link in an optional email. Unsubscribing from marketing does not stop security or billing notices and does not cancel your subscription. We do not currently collect phone numbers for SMS marketing or send marketing texts. We would ask for separate, specific consent before introducing them.