Privacy
Privacy Policy
Effective date: September 1, 2026
This Privacy Policy explains how Spatial Memories (“we”, “us”) handles data in VibeFood, our iOS app. By using VibeFood, you agree to the practices described here.
Data stored on your device
The following is stored locally on your iPhone:
- Dining personas you create
- Saved restaurants (your Vault)
- Vetoes (places you don't want to see)
- Your taste profile (“food DNA”)
- Your dining log
- Your mood-check date
- An anonymous device ID
- Your email, only if you choose to link it
Data synced to the cloud
If you link your email, the following is synced to our cloud database (Supabase), keyed to your anonymous device ID so your Vault and taste follow you across devices:
- Your taste profile (“food DNA”)
- Saved places
- Vetoes
- App settings
- Your email (only if you link it)
Data we collect
- Email — for contacting you and optional sign-in
- Device ID — an identifier that ties your data to your device
- Precise location — used to rank nearby restaurants
- User content — saved restaurants and your preferences
Third-party processors
We use the following services to operate VibeFood:
- Supabase — cloud database for syncing your data
- Google Places API — restaurant data and photos; receives your location to perform nearby search
- Resend — delivers your magic-code sign-in emails
- Cloudflare — hosts our backend
During a real-time “Duet” session, your pick data is temporarily shared only between the two people in that session so you can decide together.
What we don't do
- No ads
- No analytics or tracking SDKs
- No sale or sharing of your data for advertising
- No purchases or subscriptions
Your rights
You can request access, correction, deletion, or an export of your data at any time by emailing vrtualized@spatialmemories.io. The in-app reset wipes your local data immediately; cloud deletion is honored within 30 days.
Children
VibeFood is not directed at children under 13, and we don't knowingly collect data from them.
Changes to this policy
If we change this policy, we'll post the updated version on this page with a new effective date.