Privacy notice — public alpha
By RDY Editorial · Last substantive review 2026-09-11
Current data handling, privacy-minimized reliability reports and staff-managed privacy requests for Rdy's United States public alpha.
Your choices and requests
During alpha, access, correction, export and deletion requests are staff-managed after identity verification. Self-service export and deletion are planned rather than currently guaranteed.
What we collect
- Account basics such as email, chosen name and household membership.
- Information a household chooses to enter, such as routines, appointments, notes and logs.
- Consent-limited measurements from public pages only. Analytics is disabled on household, member, account and admin surfaces.
Advertising and model use
- Rdy does not sell household data or use it for targeted advertising.
- Household, account and managed-minor surfaces remain advertising-free.
- Public-page sponsorships, if enabled during beta, must be contextual and clearly labelled.
- Optional provider processing is disclosed at the point of use and must not be represented as local-only processing.
Where production data lives
Production data is currently hosted in Supabase us-east-2 (Ohio). Platform encryption is used in transit and at rest. The current backup posture is daily backups with seven-day retention; point-in-time recovery is not enabled.
How to make a request
Use the form on this page or email privacy@rdyadhd.com. Rdy verifies identity before acting. The current alpha operating target is a staff response within 14 days; applicable legal deadlines may differ.
Strictly necessary reliability reports
If a page cannot finish loading, Rdy may send a privacy-minimized diagnostic report even when optional analytics is off. The browser turns the technical error into a one-way fingerprint before sending it; the application does not send or retain the error text, stack, page URL, query values, account identifiers, email address, IP address, user-agent string or household content in this report. Rdy's application database keeps the keyed fingerprint, coarse route and device classes, release identifier, timestamps and a random reference for up to 30 days. Service providers may process request metadata to deliver and protect the endpoint; network metadata is used transiently by Rdy for abuse rate limiting and is not added to the diagnostic record.