Effective date: August 17, 2026 · Last updated: August 17, 2026
Reeve is operated by Vantage XO LLC, a Georgia limited liability company.
Questions? privacy@reeve.day
Reeve is a household operating system. That means we handle some of the most personal information a family has: schedules, documents, children's ages, health notes, and connected email accounts. We take that responsibility seriously. This policy explains exactly what we collect, why we collect it, how we protect it, and what control you have over it. No legalese. No surprises.
1. What We Collect#
Information you provide directly#
- Household and member information: household name, member names, member types (adult or child), date of birth (optional), and member roles.
- Documents: scanned government documents (passports, driver's licenses, vehicle registrations, insurance policies, estate documents). These are processed on your device. Extracted fields, meaning document type, expiry date, and document number, are stored encrypted in your account. Raw scan images are not stored.
- Health notes: allergies, medications, dietary restrictions, and medical conditions. These are always entered manually. Reeve never infers health information. Health notes are encrypted on-device and never transmitted to external services.
- Loyalty and account information: loyalty program names, membership tiers, and point balances. Account numbers are optional and encrypted. Reeve never stores passwords.
- Service account metadata: utility provider names, account types, and account holders. Reeve stores account names only. No passwords. No credentials.
Information from connected services#
- Calendar data (Google Calendar, Apple Calendar, or iCal URL): event titles, start and end times, and attendee counts. We read calendar data to power scheduling intelligence and coverage gap detection. We do not read event descriptions, attachments, or meeting notes unless they are part of the event title.
- Email data (Gmail): Reeve reads email metadata and body content to detect events, appointments, travel confirmations, school communications, and purchase receipts. Email body content is parsed in memory and immediately discarded. We never store email body content. Only extracted metadata is written to your account: detected event type, date, time, and sender for event emails; item category, size, delivery date, and retailer for receipt emails. Purchase amounts are not stored unless directly relevant to a household record (for example, a vehicle deposit amount). Credit card numbers and payment methods are never stored.
Information generated by Reeve#
- AI action log: a record of actions Reeve's AI has taken, including proposals created, events detected, and coverage gaps surfaced. Visible to you in Settings, where you can also clear it at any time.
As Reeve's household memory features expand, this policy will be updated, with 30 days' notice per Section 9, before any new category of data collection goes live.
Information we do not collect#
- No email body content is ever stored.
- No location data. Reeve does not track where you are.
- No financial account data. Loyalty points only, not bank accounts, credit card numbers, or transaction history. Purchase amounts from receipts are not stored unless directly relevant to a household record.
- No raw OCR output. Only user-confirmed extracted fields.
- No conversation history. NLP inputs are processed and discarded.
- No inferred health information. Health notes are always manually entered.
- No advertising identifiers. Reeve does not use tracking pixels, ad SDKs, or behavioral profiling for advertising.
2. How We Use Your Information#
We use the information we collect to:
- Operate the household OS: surface events, detect coverage gaps, track document expiry, and coordinate household logistics.
- Power AI intelligence: parse emails for event detection, generate coverage gap alerts, and surface proactive proposals for your review.
- Send reminders: document expiry alerts and coverage gap notifications at the intervals you set.
- Improve Reeve: aggregate, anonymized usage data may be used to improve the product. Your personal household data is never used to train AI models.
We do not:
- Sell your data to third parties. Ever.
- Use your data for advertising targeting.
- Share your household data with other Reeve users or households.
- Use your email content, documents, or health notes to train any AI model.
3. How We Protect Your Information#
On-device encryption#
Documents, health notes, and loyalty account numbers are encrypted on your device using Expo SecureStore and the iOS Secure Enclave. The encryption key never leaves your device. These items are not accessible to Reeve employees or systems without your device.
Cloud security#
All data transmitted between your device and Supabase (our backend provider) is encrypted in transit using TLS 1.3. Data at rest in Supabase is encrypted using AES-256. OAuth tokens for connected accounts (Gmail, Google Calendar) are stored encrypted. Disconnecting a connected account immediately revokes Reeve's access to it; the stored OAuth token itself is deleted within 24 hours.
Email and receipt processing#
Email body content is parsed in memory on our servers using the Gmail API. The body is read, parsed for event and receipt signals, and immediately discarded. Only extracted metadata is written to your account. Reeve employees cannot read your emails.
Health notes#
Health notes are encrypted on-device and never transmitted to external APIs. They are included in AI processing only when directly relevant to a specific task you initiate (for example, a grocery list that accounts for dietary restrictions). They are never surfaced on the dashboard.
4. Third-Party Services#
Reeve integrates with the following third-party services. Each is governed by its own privacy policy.
- Supabase: database, authentication, and storage backend. Your household data is stored in Supabase's infrastructure. supabase.com/privacy
- Anthropic Claude API: natural language processing for email parsing, NLP input, and capability generation. anthropic.com/legal/privacy
- OpenAI: document OCR and passport scanning. openai.com/policies/privacy-policy
- Google: Gmail API and Google Calendar API via OAuth 2.0. policies.google.com/privacy
- Apple: Sign in with Apple, EventKit (calendar), and iOS Secure Enclave for encryption. apple.com/legal/privacy
- Expo / EAS: app build, delivery, and push notifications. expo.dev/privacy
We do not sell data to, share data with, or allow data access by any advertising networks, data brokers, or analytics platforms beyond those listed above.
5. Data Retention#
- Account data: retained for the life of your account. Deleted within 30 days of account deletion.
- Email metadata (detected events): retained until you delete the event or delete your account.
- Email and receipt body content: never stored. Discarded immediately after parsing.
- Documents: retained until you delete them or delete your account. Encrypted at rest.
- Health notes: retained until you delete them or delete your account. Encrypted on-device.
- AI action log: retained on a rolling, indefinite basis so you have a complete record of what Reeve has done. You can clear your activity log at any time in Settings.
- OAuth tokens: access is revoked immediately upon disconnection of a connected account; the stored token is deleted within 24 hours.
6. Your Rights and Controls#
You have full control over your data. From within the Reeve app:
- Disconnect any connected account at any time from Settings → Connected Accounts. Disconnection immediately revokes access; the stored OAuth token is deleted within 24 hours.
- Delete any document, health note, or household data at any time.
- Clear your AI activity log from Settings → Data Controls.
- Export your household data by contacting privacy@reeve.day.
- Delete your account entirely from Settings → Data Controls → Delete Account. This permanently removes all household data, documents, connected accounts, and preferences within 30 days.
Instructions for deleting your account, including how to request deletion if you no longer have access to the app, are available at reeve.day/delete-account.
If you are located in California, the EU, or another jurisdiction with specific privacy rights (CCPA, GDPR, or equivalent), you may have additional rights including the right to access, correct, or delete your personal data. Contact privacy@reeve.day to exercise these rights.
7. Children's Privacy#
Reeve is designed for use by adults to manage household information. That household information may include records about the adult's own children, for example a name, a birth date, an activity schedule, or a scanned document like a passport.
These child profiles are entered and controlled exclusively by the adult account holder. In the current version of Reeve, children do not have their own account, login, or any way to access or interact with Reeve directly. A child cannot view, edit, or be shown anything through the product. Nothing is collected directly from a child.
We are continuing to review how this area of the product should work as Reeve grows, including any future version that would let an older child hold their own limited account. Any such feature will require its own parental consent process, and this policy will be updated to describe it in detail, with notice per Section 9, before it becomes available.
If you believe a child has provided personal information to Reeve directly, or has access to an account of their own, contact privacy@reeve.day and we will investigate and, where appropriate, delete it promptly.
8. Google API Disclosure#
Reeve's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- Reeve uses Gmail data (gmail.readonly scope) only to detect household-relevant events and receipts from your inbox. Email content is parsed in memory and never stored.
- Reeve uses Google Calendar data (calendar.readonly scope) to read your events for scheduling intelligence and coverage gap detection.
- Gmail and Google Calendar data is not used to develop, improve, or train generalized AI or machine learning models.
- Gmail and Google Calendar data is not transferred to third parties except as necessary to operate the service (Anthropic Claude API for parsing, Supabase for storage of extracted metadata only), to comply with applicable law, or as part of a merger or acquisition.
- Humans at Reeve do not read your Gmail or Google Calendar data.
9. Changes to This Policy#
We will notify you of material changes to this Privacy Policy via in-app notification at least 30 days before the changes take effect. Continued use of Reeve after the effective date constitutes acceptance of the updated policy. The current version of this policy is always available at reeve.day/privacy and within the Reeve app under Settings → Privacy Policy.
10. Contact#
Questions, requests, or concerns about this Privacy Policy:
Email: privacy@reeve.day
Vantage XO LLC 113 S. Perry Street, Suite 206, Lawrenceville, GA 30046 Georgia, United States