Privacy Policy
Who we are. Craves is operated by [YOUR NAME or COMPANY], [CITY], Texas, USA. Contact: privacy@craves.studio. We are the controller of the personal data described here.
What Craves does. Craves recommends a restaurant to you or to a group of friends, learns from your feedback, and lets you log and share meals with friends you choose.
1. Information we collect
| Category | What | Why | Legal basis (GDPR, where it applies) |
|---|---|---|---|
| Account | Email address, display name, username, password hash or the identifier from Sign in with Apple / Google | Create and secure your account | Contract |
| Taste profile | Your onboarding answers (favourite restaurants, food-choice priorities, openness to new foods, spice preference, photo-quiz choices, how often you eat out with others) | Personalise recommendations | Contract |
| Dietary preferences | Vegetarian, vegan, gluten-free and similar lifestyle preferences | Filter recommendations | Contract |
| Sensitive dietary data (optional) | Food allergies; religious dietary rules such as halal or kosher | Exclude unsafe or unsuitable restaurants for you and any group you join | Explicit consent, which you can withdraw in Settings at any time. Health-related and belief-related data are “special category” data under GDPR and “sensitive personal information” under California and Texas law. |
| Location | Your approximate or precise location only while you use the app to request a recommendation | Find restaurants near you | Consent via the OS permission prompt; you can use the app with a typed location instead |
| Activity | The recommendations you receive and accept or reject; the visits you log (restaurant, date, “would you go back”, optional dish, optional photo, optional vibe tags); reactions on friends’ posts | Improve your recommendations, build your history and your year-end recap, show posts to friends you choose | Contract; legitimate interest in improving the service |
| Friends and groups | Friend connections you make; optional hashed phone contacts if you choose “find friends from contacts” (we never upload raw contact lists); group memberships | Let you connect and decide together | Consent (contacts); contract (friends, groups) |
| Device and diagnostics | Push notification token, device type and OS version, app version, crash reports, coarse usage events (screen opened, button tapped) | Send notifications you enabled; keep the app working | Legitimate interest |
We do not collect precise location in the background, contacts’ names or emails, payment card data, or advertising identifiers.
2. How we use information
To decide where you eat; to learn what you like from your feedback; to run group decisions using each member’s filters; to show your posts to the friends you select; to send the post-visit follow-up notification you opted into; to create an optional year-end recap; to keep the service secure; to measure what works, in aggregate.
We do not sell personal information and do not share it for cross-context behavioural advertising. We do not use your data to train general-purpose AI models.
3. Where your information goes (processors)
| Provider | Purpose | Data involved |
|---|---|---|
| Supabase (hosted Postgres, auth, storage), USA | Database, login, photo storage | All categories above, encrypted in transit and at rest |
| Google Maps Platform (Places API) | Live restaurant ratings, review counts and opening hours at the moment you ask for a recommendation | Your approximate location and the restaurant lookups; we store none of Google’s content except restaurant identifiers |
| Anthropic (Claude API) | Generating the one-sentence explanation of a recommendation | A summary of your taste profile and the candidate restaurants’ attributes; no name, email, contacts, or precise location |
| Expo push service, Apple APNs, Google FCM | Delivering notifications | Push token |
| [Cloud Run / Fly.io] | Running our recommendation service | Request data in transit |
| Meta (Instagram) | Only if you choose to share a card to Instagram Stories | The image you chose to share, sent from your device |
Restaurant catalogue data comes from Foursquare OS Places and OpenStreetMap (© OpenStreetMap contributors, ODbL); this is data about restaurants, not about you.
4. What friends and others see
By default your logged visits are visible to accepted friends only. You can set each visit to private. Your dietary preferences and sensitive dietary data are never shown to other users, never included in share cards, and are used in a group decision only as a filter without revealing who set it. Public sharing happens only when you export a card to another platform.
5. Retention and deletion
- Account and profile data: until you delete your account.
- Recommendation and visit history: until you delete it or your account; you can delete individual visits any time.
- Location: the coordinates you send with a request are used to answer it and are not stored; we keep only the restaurant chosen and a timestamp.
- Google Places content: fetched live, kept for the duration of the request only. Restaurant identifiers may be kept.
- Diagnostics: up to 90 days.
- Backups: deleted data leaves backups within 30 days.
Delete your account in the app under Settings → Account → Delete, or at craves.studio/delete-account. Deletion removes your account, profile, history, photos and friend connections within 30 days, and revokes Sign in with Apple / Google tokens.
6. Your rights
Depending on where you live, you may have the right to access, correct, export, delete or restrict the use of your data, to withdraw consent, and to object to processing. Texas (TDPSA), California (CCPA/CPRA) and other US state laws, and the GDPR in the EU/UK, give you these rights; we honour them for everyone. Use Settings → Privacy → Export my data, or email privacy@craves.studio. We respond within 45 days (30 days in the EU/UK). We will not discriminate against you for exercising your rights. If you are in the EU/UK you may complain to your supervisory authority.
7. Children
Craves is not directed to children under 13 (16 in the EU) and we do not knowingly collect their data. [Store age rating: 12+/Teen due to user-generated content; confirm.]
8. Security
Encryption in transit (TLS) and at rest; sensitive dietary data stored in a separately encrypted column; row-level access controls so users can read only their own and their friends’ permitted data; least-privilege API keys; no Google Maps or Anthropic keys in the mobile app.
9. International transfers
Data is stored in the United States. If you use Craves from the EU/UK, transfers rely on the providers’ standard contractual clauses.
10. Changes
We will notify you in the app before material changes take effect. Version history: v0.1 draft, 20 September 2026.