Privacy Policy
Privacy Policy
App: Nab Reservations
Effective date: June 18, 2026
Contact: [email protected]
1. What We Collect
We collect data needed to operate, improve, personalize, and protect the app:
- Account information — name, email address, and profile photo provided by Google Sign-In when you create an account.
- Location (text only) — the neighborhood or city you enter in the filter screen (for example, "Manhattan"). We do not collect your precise GPS coordinates.
- Usage and interaction data — app sessions, saved filters, card impressions, detail opens, swipes, slot selections, booking attempts, booking outcomes, cancellation activity, paywall activity, and availability-check outcomes. This data may be linked to your Nab account, app install, session, restaurant identifiers, and filter context.
- Restaurant and reservation identifiers — OpenTable restaurant IDs, Google Place IDs, selected date/time/party-size buckets, and Nab reservation lifecycle records such as booking status and cancellation status. Nab analytics does not include OpenTable confirmation numbers, special requests, user notes, raw OpenTable HTML, cookies, passwords, or tokens.
- Derived restaurant preferences — aggregate or per-account signals such as cuisines, neighborhoods, restaurants shown, restaurants passed, restaurants liked, booked restaurants, and canceled reservations, used to improve recommendations and app experience.
- Device identifiers — anonymous identifiers used by Firebase and Sentry for crash reporting and analytics.
- Crash and error data — stack traces and device metadata sent to Sentry when the app crashes.
2. How We Use It
- To authenticate you and maintain your session (Firebase Auth)
- To fetch nearby restaurant data (Google Places API)
- To diagnose crashes and improve stability (Sentry)
- To understand how people use Nab, improve the product, debug booking and availability flows, and measure feature performance.
- To personalize restaurant ordering and recommendations while preserving the requirement that every Discover card is availability-checked before display.
- To maintain reservation limits, quota behavior, match history, and cancellation state.
- To create aggregate restaurant demand and availability metrics, such as most viewed, most swiped, most booked, cancellation rates, and unmet demand. Restaurant-facing or partner-facing outputs are aggregated and thresholded; we do not share raw user-level analytics or diner profiles with restaurants.
- We do not sell your data. We do not use it for advertising targeting. We do not share raw diner-level analytics with restaurants.
3. Third-Party Services
- Firebase (Google) — authentication and cloud database. Firebase Privacy Policy
- Google Places API — restaurant search and details. Google Privacy Policy
- OpenTable — reservation availability, login, booking, and cancellation flows may be presented through OpenTable web pages or WebViews. OpenTable may collect information directly when you interact with its service. Nab may maintain session state needed to keep you signed in, but Nab analytics does not include OpenTable confirmation numbers, special requests, user notes, raw OpenTable HTML, cookies, passwords, or tokens.
- Sentry — crash reporting. Sentry Privacy Policy
- RevenueCat — in-app purchase management. RevenueCat Privacy Policy
4. Data Retention
Match history, preferences, and app state may be stored locally on your device and/or in our Firebase database so the app can work across sessions and devices. Per-account restaurant state and reservation lifecycle records are retained while your account is active or as needed to operate the app.
Linked raw analytics events are retained only as long as needed for product analytics, debugging, and internal reporting. Our intended retention window for linked raw analytics is up to 13 months, unless deletion is requested earlier.
We may preserve aggregate, thresholded metrics that no longer identify an individual user, such as restaurant-level daily counts or demand trends.
5. Your Rights & Data Deletion
You may request deletion of your account and associated personal data at any time by emailing [email protected]. We will process your request within 30 days.
Deletion includes linked raw analytics events, per-user restaurant state, account records, and reservation lifecycle records associated with your Nab account, except where retention is required for legal, security, fraud-prevention, or payment-record purposes. Aggregate, thresholded metrics that do not identify you may be retained.
6. Children
Nab is not directed at children under 13. We do not knowingly collect data from children.
7. Changes
We may update this policy. The effective date at the top of this page will reflect any changes. Continued use of the app after an update constitutes acceptance.