Savora Privacy Policy
Last updated: November 19, 2026
Savora connects adults with restaurants for food ordering, payment and delivery. Savora uses restaurant information to filter menus and relay dietary requirements. The app and its filters do not guarantee that food is safe for allergies. Restaurant information and nutrition estimates are not medical advice. Contact the restaurant about severe allergies. In an emergency, call 911 or your local emergency number; do not wait for a reply from us.
Who is responsible
Nutrify Technologies Inc., British Columbia, Canada. Mailing details are on our support page.
Contact [email protected] for account, order, deletion, privacy access, correction and consent requests. Our support team handles these requests and verifies ownership before disclosing or deleting account information. You can also use Help in the app for order problems and conversations with the Savora team.
Savora is intended for people aged 18 and over. We do not collect birth dates or verify age. Contact us if you believe a minor has an account.
Accounts, guests and consent
Browsing opens an anonymous Firebase account. Its identifier can hold dietary filters, carts, campaign attribution and a Health export choice. Usage events can also be recorded before registration. Uninstalling does not erase server records. Guests can delete their current account from Settings without registering.
Registration uses a verified phone number and name. Email is optional with phone registration; Apple or Google sign-in can supply name and email, including an Apple private relay address. Firebase handles verification messages and authentication credentials. Older versions may have used Firebase email/password authentication. We record the accepted terms/policy version and time. The acceptance checkbox does not verify age. Allergy and intolerance filters have a separate acknowledgment.
Linking a new sign-in provider keeps the guest identifier and its data. When signing in to an existing account, the app captures the current checkout cart and filters, deletes the old guest through the account-deletion service, then signs in and reconciles the captured information. Cleanup failure stops that switch for retry. Abandoned guest accounts and their carts expire after 30 days without sign-in. Server cleanup removes their personal records before their authentication identity.
Information and purposes
| Information | Purpose and recipients |
|---|---|
| Name, verified phone, optional email, account/provider identifiers, sign-in and consent records | Account access and order contact. Google/Firebase hosts these. Restaurants receive order contact; Stripe receives customer details and identifiers; delivery recipients go to Uber Direct. |
| Delivery and saved addresses, coordinates, unit and instructions | Address search, delivery quotes, routing and fulfilment through Google address/maps services, restaurants and Uber Direct. Pickup does not require a delivery address. |
| Optional foreground device location, including precise coordinates | Nearby restaurant and address suggestions, location bias and reverse geocoding. You can decline permission and use manual addresses. We do not request background location tracking. Map/address services also receive network information such as IP addresses. |
| Items, options, quantities, amounts, payment/credit identifiers, order status, kitchen notes and ratings | Preparing and fulfilling orders, support, refunds, payment and financial records. Restaurants see their orders. Stripe processes payments; Uber receives delivery items, recipient and instructions. Savora does not store full card numbers. |
| The arrival or ready time promised at checkout, and the order's delivery and readiness times | Checking lateness and applying credit and refund rules. |
| Courier status/location, tracking links and delivery-proof photos | Uber/couriers supply delivery evidence. The consumer app displays an order-linked photo; it does not take or upload a consumer photo. Provider copies follow provider retention. |
| Allergy/intolerance and diet filters, health filter level, calorie target/goal, acknowledgments | Menu filtering, kitchen requirements and dietary-safety investigations. These can reveal health information. Restaurants receive requirements for their orders, not your whole profile or nutrition log. Google hosts profile and operational records. |
| Daily nutrition totals and order nutrition | Paid orders automatically add nutrition totals to your Savora account. This has no separate off switch or clear-history control; account deletion removes the daily logs. Totals represent food ordered, which may be shared or uneaten, not measured personal intake. |
| Health export choice, platform and decision time | Optional export of completed-order energy, protein, carbohydrate, fat, fibre, sugar and sodium to Apple Health or Health Connect, with completion time. This is separate from automatic Savora logs. |
| Push token/binding, installation/session identifiers, device/OS/app version, integrity and security information | Order and support-reply notifications, authentication integrity, diagnosis and operation through Firebase App Check/Crashlytics, Expo, Apple APNs and Google FCM. Notifications can contain order/restaurant identifiers and status. |
| Usage and campaign events, first-open/platform information and account-linked or hashed identifiers | Savora's first-party Google-hosted analytics and generic registration/purchase lifecycle evaluation. A hashed identifier is still linkable. Lifecycle evaluation remains in shadow mode: it does not send marketing nudges. Dietary/health values, their presence and their setup timestamps are excluded from current marketing eligibility and evaluation. |
| Support cases: the order and problem you choose, your answers and messages, assistant and team replies, language, times, assistant routing choices, money requests and outcomes | Answering requests, investigating order problems, deciding credits and refunds, and resolving disputes. Google hosts these records. Authorised Savora team members can read them; OpenAI receives the limited information described below. Do not send card numbers, passwords or unnecessary health information. |
| Allergy and food-safety reports: dishes, allergens or restrictions, what happened, when symptoms began if provided, whether you sought medical attention, whether others ate the food, your contact-sharing choice and any additional details | Investigating reports, reviewing restaurant information and applying label pauses where the report matches a saved order restriction. These reports contain health information. We also record when the emergency information was shown. |
| Reports about assistant replies: the reply you report, your selected reason and our review outcome | Allowing Savora's owner to review replies and handle concerns. |
| Credit and refund records: rules or reasons, amounts, expiry, order references and outcomes | Processing and displaying credits and refunds, managing program budgets and keeping financial records. Stripe processes card refunds. |
| Claim-counting evidence: account identifiers and one-way hashes of verified phone numbers and Stripe card fingerprints | Counting support claims across accounts and deciding which requests need team review. A card fingerprint is an identifier supplied by Stripe, not a card number. |
| Support correspondence by email | Answering requests, verifying ownership and resolving issues. Help can open your external email app; do not send card numbers or unnecessary health information. |
Before the first paid order, registration explains automatic nutrition logs and the separate optional export. Export permission is requested only if you choose it. No Health Connect records are read. On iOS, Savora can inspect metadata on its own written samples to recover export identifiers and avoid duplicates. It does not import health history from other apps or send that history to Savora servers. Turning export off or revoking permission stops new exports. Earlier exports remain in your health store until you remove them there, including after account deletion.
Support and order help
Savora's support assistant runs on OpenAI's API. When you use the assistant, OpenAI receives the order status, item names and quantities, the problem and language, support-request types, references and status, and customer messages after the removals described below. Messages are sent as text, rather than a summary. Earlier customer messages from the same conversation may be included as context. Team replies and structured allergy reports are not included in this input.
We do not send the name, phone number, email, address or payment details saved in your account or order as separate fields. We remove matching saved name, phone number, email and address text from messages, including matches with different capitalisation. We also try to remove common email, number and street-address patterns and phrases that introduce a name. These checks cannot recognise every personal detail. The remaining message text is sent to OpenAI, including health information or other personal details you type that the checks do not remove. Please do not type card numbers, passwords or unnecessary personal details.
OpenAI processes these messages for Savora and does not use them to train its models. OpenAI normally retains API inputs and outputs for up to 30 days for abuse monitoring; it may retain them longer where required by law or necessary to prevent harm. Savora requests that responses not be stored as application history. OpenAI processing may take place outside Canada, including in the United States.
Savora's systems supply the amounts, order status and deadlines shown in support replies and apply the limits on credits and refunds. The assistant does not give diagnosis or treatment advice. You can report an assistant reply in the app or choose to speak with the Savora team. You can send your message to the team instead of the assistant.
You and authorised Savora team members can read your conversation. Restaurant accounts and other customers cannot read it through the app. Notices to Savora's owner use fixed wording and case references; they do not include your message or health narrative in the subject line or email body.
If you enable notifications and have a current push registration, we may send a notification when the Savora team replies. The notification contains a generic reply notice and a reference to the conversation, not the reply text or health details. Notifications may not arrive; the reply remains available in Help.
Credits and refunds
We use order timing and fulfilment records to apply automatic credit and refund rules. For support requests, we also use the problem, claimed items, prior claims and available program budget to decide the response or refer it to the Savora team. The assistant can offer a credit or refund within set limits; a money request from that offer is made only after you tap to accept it.
To count claims across accounts, we use the account identifier and one-way hashes of its verified phone number and the card fingerprint Stripe supplies. These counts can change whether a request is handled automatically, waits for review or requires the team's decision. They do not by themselves deny a claim. You can ask the Savora team to review the decision. Advertising and device identifiers are not used for these claim counts.
Separately, a fraud-prevention check can block in-app claims for missing or wrong items when your verified phone matches a retained hash from a deleted account. Messages to the Savora team and reaction reports are not blocked. If this happens, message the team in the app or email [email protected].
Allergy and food-safety reports
When you submit a reaction or food-safety report, the Savora team receives the structured answers and any additional details you provide. We use this information to investigate the report and review the restaurant's information. The report alerts Savora's owner and goes to a person, not the support assistant. If you type health information into an assistant conversation instead, the message handling described above applies.
For a reported restriction that the order recorded, the system requests a pause on the corresponding dish label. A label pause means the statement is treated as not verified while it is reviewed; it does not establish that any food is safe. A report about an unlisted allergen, illness or a foreign object can require team review without a matching label pause. Pauses may need follow-up processing, and new evidence is required to lift them. Filing a report does not itself notify the restaurant. Your choice about sharing contact details with the restaurant is recorded for the team. Emergency information is available before a report is sent.
Providers and processing locations
- Google/Firebase/Google Cloud: authentication, database/storage, functions, first-party BigQuery analytics, crashes, installation/session metadata and App Check (App Attest on iOS, Play Integrity on Android). Functions and warehouse use us-west1; this does not mean every Google service stays in that region.
- OpenAI: support-message processing as described under "Support and order help".
- Google Places, Geocoding, Maps and Routes: search text, coordinates/location bias, place/session identifiers, map/route requests and network metadata.
- Stripe: embedded payment sheet, card/wallet and saved-method processing, customer/payment identifiers and fraud/security information. It maintains its own transaction/compliance records; deleting a customer is not erasing every Stripe transaction record. Stripe also supplies the card fingerprint used for support claim counts.
- Uber Direct and couriers: delivery quote/dispatch, recipient phone/name, address/coordinates, instructions, items/quantities and delivery evidence.
- Restaurants: order contact, items, personal dietary requirements, notes and ratings needed to prepare, fulfil and support their orders.
- Expo, Apple APNs and Google FCM: optional push delivery and routing. Expo Updates checks for app updates at launch; requests expose IP/network, build, runtime and update metadata even if no update is installed.
- Apple and Google sign-in: provider identities and authentication tokens. Apple-linked deletion on iOS reauthenticates and asks Firebase's server to revoke Apple authorization before requesting Savora cleanup. Server deletion requires verified revocation or documented impossibility; support handles this step on iOS and Android without requiring an iOS device.
- Apple Health and Health Connect: optional device-store export described above.
- FatSecret: restaurant-backend ingredient queries and food identifiers for menu nutrition. The implemented integration does not send consumer profiles, account identifiers, dietary settings or nutrition logs to FatSecret.
Information may be processed outside Canada, including in the United States. Information held abroad is subject to local laws and may be accessible to courts, law enforcement or other authorities there. Provider roles and their own legal obligations differ; we do not describe every recipient as an exempt processor. We do not use data outside the app for website pixels, advertising campaigns, manual exports or additional recipients. We do not sell personal information or use health information for advertising. Our native analytics remains first-party.
Deletion and retention
Settings → Delete account is available for guests and registered customers and asks for two confirmations. Active orders block deletion. Accepted deletion blocks new orders and may wait for payment cancellation/refunds. Partial cleanup cannot be undone; retry or contact support if it does not finish.
Cleanup removes the profile, addresses, daily nutrition logs, carts, checkout and restriction-consent operation records, current verified-phone bindings, push-token bindings, user-targeted notification deliveries, live tracking, Stripe customer and saved payment methods, then Firebase Auth identity. On retained terminal orders, contact fields, street/unit/instructions, coordinates, personal dietary requirements, notes, rating comments and name-search prefixes are neutralised. Dish nutrition and labels, city/province/postal prefix, star rating, amounts and financial identifiers remain. This is not complete anonymisation.
Unused credit is lost when you delete the account. Pending discretionary money requests that are not yet payable are cancelled. Deletion does not cancel a reimbursement already owed.
Account deletion removes ordinary support messages and reply reports, including those in cases involving money or safety. It also removes assistant routing and internal conversation-state records. We keep the case records needed for money or safety, financial requests and claim evidence, and structured incident and emergency records. Retained incident reports include their structured answers and any text submitted with the report. These records can retain account and order identifiers and health information; they are not anonymous. An open safety case does not require us to keep the rest of your account. If support cleanup cannot finish with account deletion, the remaining cleanup is recorded and retried.
| Retained category | Period and purpose |
|---|---|
| Order, payment, tax, credit and refund records, including settlement evidence | Seven years for bookkeeping, tax, payment settlement, refunds and disputes. |
| Dietary-safety incident records and dispute evidence | Seven years for investigating incidents and resolving disputes. Dietary-safety copies that are not incident records are erased at deletion. |
| Support case records involving money or safety that remain after account deletion | Seven years from case closure, or longer while related financial work remains unresolved. Financial requests and claim evidence use their latest relevant activity, which can be later than case closure. Open cases remain until resolved. |
| Other support conversations | Stored with your account and erased on account deletion. You can contact support to request earlier erasure. |
| Support claim counters | Claims count for 180 days. Older entries are removed when counters are updated; account-deletion cleanup also removes expired entries. Inactive counters can remain until that cleanup occurs. Separate financial claim evidence follows the longer period above. |
| A one-way hash of the verified phone number | Seven years for fraud prevention, including promo-credit abuse. It is not used for sign-in lookup or account recovery. The account's phone binding and saved phone number are erased at deletion. |
| Diagnostic and analytics events | Kept, but stripped of account identifiers when the account is deleted. Existing event expiry still applies. |
| Everything else that identifies the person | Erased at deletion, including personal settings, non-incident dietary copies and manual exports. |
Support records are not all erased on a fixed anniversary while an account stays open. The deletion rules and periods above describe the cleanup that runs after account deletion and the claim counters' use. Contact [email protected] about information you no longer want us to retain. No single legal maximum applies to all records.
Backup copies must remain unavailable to normal use. Before restored data serves users, accepted deletions must be replayed and expired records removed. Independent providers may retain records under their own legal obligations.
Deletion does not erase independent Stripe/Uber records or exported device-health entries. For a request without reinstalling or signing in, email [email protected] with the account phone number (email if present). Never send an SMS code/password. Support must verify control of the phone or another reliable account/session route; knowing a phone number or guest identifier alone is not proof of ownership. See deletion instructions.
Your choices and requests
You can change filters, clear individual saved addresses in Settings → Saved addresses, decline location/notifications, and disable Health export. Removing a saved address does not remove past order copies or nutrition history. You can choose the Savora team instead of the assistant or select "Talk to a person" in a Help conversation. This stops new assistant processing for that conversation; it does not recall messages already sent to OpenAI. There is no general in-app data-only erasure service. Contact [email protected] for access, correction, withdrawal or other requests, including access to your support cases and the reasons for credit and refund decisions; we verify identity and explain lawful exceptions. Withdrawing information required for ordering can prevent that feature.
Restaurant staff accounts and agreements also involve business contact, authorisation, signature and device records; deleting a consumer account does not terminate or erase a restaurant agreement. Security uses access controls and encrypted transport, but no security certification is claimed.
Changes to this notice
This notice replaces earlier versions. We publish updated versions with a new "Last updated" date. New customers accept the notice during registration. When an updated app requires a new terms and privacy policy version, signed-in customers are shown a screen to review and accept the updated terms and privacy policy before continuing. Savora is for adults aged 18 and over.