Privacy Policy
The Reserv is a plan-first dating app: you pick a restaurant and a time, and the app helps you match with someone who's actually going to show up. This policy explains what we collect, why, and how to get rid of it.
What we collect
The data you give us when you use The Reserv falls into a few buckets:
- Account. Your email address and a password (or, if you sign in with Apple or Google, a verified identity token from that provider that we exchange for a Supabase session). We never see or store your Apple or Google password.
- Profile. Your first name, date of birth (used only to compute your age and confirm you are 18+), height, gender, who you're interested in, your neighborhood, a short bio, three photos, and a small set of "dining vibe" tags. You enter all of these during onboarding; you can edit or remove any of them later.
- Plans, requests, and messages. Details of the plans you host (restaurant, date, time, party size, optional note, payment preference) and the requests you send to join other people's plans. Once a plan is confirmed, the chat between confirmed participants is also stored so it survives across devices.
- Push notification token. If you grant push permission, your device's Expo push token so we can send you transactional notifications (a new request on your plan, a host accepting you, a plan being cancelled).
- Location — only when you ask. If you tap "Use my current city" while creating a plan, we ask iOS for your when-in-use location, look up the nearest supported city, and throw the precise coordinates away. We never request background location and we never store coordinates.
- Reservation confirmation. If, as a host, you choose to upload a screenshot of your booking confirmation, that image is stored in private storage and visible only to confirmed participants of that plan.
- Google Calendar — read-only, only with your permission. If you connect Google Calendar to verify a reservation, we request read-only access to your calendar events. We use it to check whether an event OpenTable added to your calendar matches the restaurant, date, and time of the plan you're publishing. We do not create, edit, or delete any calendar event, and we do not store your full calendar contents — only the minimal details of the matched event (such as its identifier, start and end time, location, and a short summary) needed to confirm the reservation.
- Reports and blocks. If you report or block another user, we record the report (reason, optional notes, who you reported, when) and the block. Reports are visible only to our trust & safety team; the person you reported is never told who reported them.
- Website waitlist. If you join the prelaunch waitlist, we collect your first name, email address, Austin launch status, optional requested city, optional launch preferences, your referral code, and attribution data such as UTM parameters, click IDs, landing page, and referring site so we can understand which campaigns are working. We do not send your name, email, requested city, neighborhood, or other free-text answers to behavioral analytics tools.
What we use it for
- Running the app. Authentication, showing you plans whose host is mutually compatible with your preferences, letting you join and host plans, keeping the chat in sync.
- Notifications. Transactional email (a new request, an acceptance, a cancellation, a plan you're hosting being full) and the matching push notification on your device. We do not send you marketing email from the app.
- Safety. Acting on reports, enforcing blocks, removing accounts that violate our community standards.
- Improving the product. Aggregate, non-identifying counts of how features are used. The marketing website may use PostHog for manual, non-identifying funnel analytics; the app does not run third-party analytics SDKs today.
Who else sees it
We use a small set of vendors that store and process data on our behalf. We do not sell your personal data, and we do not share it for advertising.
- Supabase (database, authentication, file storage, realtime sync). All app data lives here.
- Resend (transactional email delivery). Your email address is shared so we can deliver notification emails.
- Expo Push Notification Service (push delivery on iOS and Android). Your push token is shared so notifications can be relayed to your device.
- Apple and Google (only if you choose to use Sign in with Apple or Google). They handle the authentication itself; we receive only the verified identity token.
- Cloudflare (DNS, marketing site, edge functions for the waitlist). Standard request logs apply.
- PostHog (marketing-site funnel analytics). We use it for anonymous behavioral events such as funnel step views, button clicks, and signup outcomes. We do not send PostHog your name, email address, requested city, neighborhood, referral URL, update token, or free-text profile answers.
- OpenTable (linked when you tap "Open in OpenTable" on a plan you're hosting). The link itself is built client-side; we do not share your account data with OpenTable.
Google Calendar access
The Reserv requests read-only access to your Google Calendar (the calendar.events.readonly scope) only after you grant permission, and only to verify a reservation. When you book a table through OpenTable, the booking adds an event to your Google Calendar; we read your calendar events solely to confirm that an event matches the restaurant, date, and time of the plan you are trying to publish. The app does not create, edit, or delete any calendar event, and we never store your full calendar contents — we retain only the minimal matched-event details needed to confirm the reservation.
We do not sell Google user data, use it for advertising, or share it with anyone for any purpose unrelated to this reservation check. The Reserv's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
You can revoke The Reserv's access to your Google Calendar at any time from your Google Account's permissions page at myaccount.google.com/permissions. Revoking access stops all future calendar reads.
Security
Security procedures are in place to protect the confidentiality of your data. We use encryption to protect your information in transit and at rest. Access to personal data, including any Google user data accessed via Google Calendar, is restricted to authorized personnel only.
Other people in the app
Anything you put on your profile (first name, age, neighborhood, bio, photos, dining vibes) is visible to other users of The Reserv whose preferences are a mutual match for yours. Plan content (restaurant, time, your note) is visible to everyone browsing plans in the same city. Once a plan is confirmed, your chat with the host or guest is visible only to the confirmed participants.
How long we keep it
We keep your data for as long as your account is active. When you delete your account in the app — Profile → Delete my account — we permanently remove your profile, photos, plans, requests, chats, and push tokens. We do not retain a backup copy. You can sign up again later with the same email; you would just start fresh.
Reports you've filed and blocks you've placed may be retained in a non-identifying form so the safety system continues to work for other users; the underlying details are removed with your account.
Your choices
- Edit anything. Profile fields, photos, and plans are editable in the app at any time.
- Turn off notifications. Profile → Notifications opens the iOS settings page where push, sound, and badge are controlled.
- Block someone. Open their profile, choose Block. You won't see each other anywhere in the app.
- Delete your account. Profile → Delete my account. Permanent and immediate.
- Email us. If you want a copy of your data or have a question we haven't answered, write to [email protected]. We aim to respond within two business days.
Children
The Reserv is for adults only. You must be 18 or older to create an account. We do not knowingly collect data from anyone under 18; if you believe a child has signed up, write to [email protected] and we will remove the account.
Changes to this policy
If we change this policy in a way that meaningfully affects what we do with your data, we'll update the effective date below and let active users know in the app before the change takes effect.