Effective September 10, 2026
Privacy Policy
This policy explains how SupperSafe handles information in its mobile app and public support pages. Questions can be sent to hello@suppersafe.com.
Information used without an account
- Search and location: restaurant searches, filters and coordinates are sent to our Supabase service to return and sort directory results. Location is requested only after you choose the location control. SupperSafe does not add your location to an account profile.
- Saved restaurants: favourites are stored locally on your device. They remain until you remove them, clear the app's data or uninstall the app.
- Restaurant photos: when an eligible restaurant is viewed, its identity may be sent to our server to request one attributed Google Places photo. SupperSafe does not ask for or upload your personal photos.
- Technical data: service providers may process IP addresses, request times, device or app details and error information needed to operate and secure their services.
iOS launch emails
If you select Notify me, we save your email address, signup date and consent to receive the iOS launch email in a private Supabase list. Resend sends our team a notification of your signup. This does not create an app account or subscribe you to restaurant alerts. To leave the list, email hello@suppersafe.com.
Optional account and alert information
If account features are enabled and you choose to use them, SupperSafe processes your email address, authentication identifiers, watched restaurants, alert preferences, private update history and registered push token. Authentication sessions and the app's installation identifier are stored in encrypted device storage where supported. Notifications remain optional.
How information is used
- Provide search, distance sorting, saved places, account access and inspection-update features.
- Display attributed restaurant photos and open directions or source links you choose.
- Protect the service, diagnose failures and prevent misuse.
- Respond to support, privacy and deletion requests.
Service providers and public sources
SupperSafe uses Supabase for database, account and server functions; Resend for sign-in email delivery; Expo for app and optional push-notification services; and Google Maps Platform for maps, directions and attributed place photos. Published inspection records come from the City of Toronto under the Open Government Licence – Toronto. These providers process information under their own terms and privacy practices. SupperSafe does not sell personal information and does not include advertising or third-party analytics SDKs.
Retention and deletion
Local favourites remain on your device as described above. Optional account data is kept while your account is active so the service can operate. Deleting your account removes the SupperSafe authentication account, watch preferences, registered phones, private update history and queued deliveries. Infrastructure and email providers may retain limited security or delivery records under their own retention rules or where legally required.
You can delete an account inside the app from Updates, or initiate a request through the account-deletion page. We verify ownership before acting on an emailed request.
Security and choices
Connections use HTTPS. Private account tables require authentication, server credentials are not included in the app, and Android sessions use encrypted storage. You may browse without an account, decline location, keep phone notifications off, remove saved places, sign out or delete your account.
Children and changes
SupperSafe is a general restaurant-information service and is not directed to children under 13. We may update this policy when the app or its providers change. The effective date at the top will be revised when changes are published.