SavvyWin Privacy Policy

Last updated: October 3, 2026

This Privacy Policy explains how SavvyWin ("SavvyWin", "we", "us", or "our") collects, uses, discloses, stores, and protects personal information when you use savvywin.app and related services (the "Service").

SavvyWin is operated from British Columbia, Canada unless otherwise stated. We aim to follow privacy principles reflected in Canadian privacy laws, including accountability, identifying purposes, consent, limiting collection, limiting use and retention, accuracy, safeguards, openness, individual access, and challenging compliance.

By using the Service, you agree to the collection, use, and disclosure of information as described in this Privacy Policy.

Privacy Snapshot

Here are the key points:

1. Information We Collect

We collect only the information we reasonably need to provide, secure, improve, and develop SavvyWin.

Information you provide

You may provide information when you:

This information may include restaurant names, seller names, boat or stall notes, meal or product names, descriptions, prices, price tiers, addresses, map coordinates, phone numbers, source links, order or information links, comments, review text, ratings, correction details, sold-out report details, report reasons, images, photo categories, upload metadata, and contact information if you choose to provide it.

Structured offer reviews may include your WIN choice, Portion and Taste choices, selected meal tags, optional review text, the price version you reviewed, and a snapshot of your appetite, taste, and price-sensitivity profile at review time. Public review cards may show your nickname and broad reviewer-profile context, but not your account ID.

Repeat-review records may include a restaurant-scoped visit identifier, the restaurant-local experience date, verification method and status, a public verification label, whether the review updates an earlier visit, a relationship disclosure, moderation state, reports, integrity flags, and links between current and superseded review versions. Public review reads do not include your account ID, exact coordinates, private evidence file, or private evidence path.

If you choose receipt, order, or reservation evidence, we may collect a private masked image and limited upload metadata such as file type, size, dimensions, evidence type, upload status, moderation status, retention deadline, account, restaurant, and visit identifiers. For supported JPEG, PNG, and WebP evidence, the upload is held in a private temporary path while SavvyWin removes embedded EXIF, XMP, text, and similar location metadata; the temporary source is scheduled for deletion within three hours, and only the sanitized copy is used for review and normal retention. Automated metadata removal does not hide information visible in the image, so cover or remove names, contact details, addresses, payment details, order numbers, barcodes, and other visible personal information before upload. This evidence is not published with the review.

If you upload a photo or other source evidence, we may collect the image file, file name, file type, file size, dimensions, upload status, moderation status, the listing or submission it relates to, and guest or account attribution. The app may resize, compress, or re-encode images before upload to reduce file size and help remove embedded metadata. You should still avoid uploading photos that include faces, payment details, private documents, or sensitive personal information. User uploads remain in private storage while pending, rejected, replaced, hidden, or under review. If a photo is approved, SavvyWin may publish a separate processed copy with the related listing. That public copy may be visible without an account and may be cached or copied by third parties outside SavvyWin's control.

Account, member, and preference information

If you choose guest mode for a contribution feature, Supabase may create a temporary anonymous authentication account and session. We may collect its authentication user ID, anonymous status, session and token metadata, account timestamps, and the guest nickname you choose. We use that authenticated user ID, rather than an anonymous browser or device identifier alone, to protect access to your private contribution history and reserve your nickname.

If you later link a sign-in method to the same anonymous account, the authentication user ID, contribution ownership, private contribution notification history, and notification preferences may remain associated with that account. If you sign in to a different existing account, SavvyWin may process a verified server-side ownership transfer, record an audit receipt, or require manual review where identities or nickname ownership conflict. Related private notifications and processing records move only after the verified ownership transfer succeeds. If the destination account already has notification preferences, the destination account's preferences take priority. We do not automatically assign past contributions or notification history based only on an anonymous client identifier.

If you choose to sign in, we may collect account and member information such as your authentication user ID, sign-in provider, display name or nickname, avatar URL, member type, onboarding status, account timestamps, saved-item sync status, and related account settings. Google may provide an authentication identifier, email address, name, and profile image. Apple may provide an authentication identifier and, where you choose to share it, an email address. SavvyWin uses this provider information to establish or access your account.

If you choose guest setup, member setup, or future personalization features, we may store preference information such as your Main area, whether that area matches a supported market, broad reviewer profile answers about appetite, taste expectations, and price sensitivity, preferred cuisines, meal categories, drink categories, deal types, price preferences, dietary preferences, disliked cuisines, notification preferences, or food-game/taste-profile results that you choose to save.

Authorized SavvyWin owner or administrator operators may view a restricted internal member directory and a bounded account, profile, preference, restaurant-owner-claim, and Winspector-assignment detail view when reasonably needed for account support, trust and safety, quality assurance, or program administration. This view does not expose authentication sessions or tokens, raw provider metadata, private review or receipt evidence, or payment-routing details. Direct changes from Member detail are limited to Location Bypass. Winspector assignment and revocation use the separate restricted Winspector operations workflow, and both types of administrative change require a recorded reason.

We may create owner-private in-app notification records about the status of your Food or Drink offer, restaurant correction, or restaurant-hours contribution. A record may include the notification type, server-written title and message, contribution reference, source event and creation times, read status, expiry status, and authenticated account ownership. We may also store whether you want to receive future "Action needed" and "Published results" in-app notifications.

If you identify yourself as a restaurant owner, manager, or staff member, we may collect restaurant-owner claim information such as the restaurant you selected, your claimed role, claim status, source notes, review notes, and related timestamps. Selecting Restaurant Owner or submitting a claim does not by itself verify ownership or grant restaurant-management permissions.

Location information

SavvyWin may use location information to show meals near you or within the map area you are viewing. This may include:

You can usually disable browser or device location permissions through your browser or device settings. Some location-based features may not work without location access.

Meal Card approximate travel estimates are calculated within SavvyWin from the current location and selected restaurant coordinates using straight-line distance and general travel-mode assumptions. SavvyWin does not send this calculation to a third-party routing provider, include precise coordinates in product analytics, or intentionally persist them as a location history.

Nearby and Meal Card flows do not request device location automatically at app start. SavvyWin first shows a just-in-time explanation when you choose a location-dependent action. You can decline and continue browsing without device location.

If you choose `Verify your visit to review`, SavvyWin sends the current device latitude, longitude, and reported accuracy to a Supabase Edge Function to determine whether you are near the selected restaurant. The raw coordinates are used for that check and are not stored. We may store the account, offer and restaurant identifiers, verification and expiry timestamps, verification method, and coarse distance and accuracy buckets. A successful verification normally permits review access for 48 hours.

If you decline location or it is unavailable, you may continue browsing and, where offered, choose private receipt, order, or reservation evidence or an unverified self-attestation. We store the restaurant-local visit date at the time of the verification or attestation. The 48-hour period is a completion window and does not create a later visit date.

Usage and technical information

We may collect technical and usage information such as:

SavvyWin may collect privacy-friendly analytics events such as app opens, approximate session activity, page or screen views, filter clicks, map pin clicks, detail opens, Add Value Meal starts or submissions, reports, Correct/Wrong actions, and favorite actions. Analytics events are intended for product improvement and operational monitoring. We aim not to include exact device location, raw search text, menu notes, phone numbers, full addresses, or other sensitive free-text content in analytics event payloads.

SavvyWin may also keep a first-party history of Food and Drink Meal Card actions such as Share, Hide, Info, Keep, Navigate, Save, Remove from saved, and Undo. A record may include the selected offer type and identifier, action time, card/deck position, a random per-click identifier used to prevent duplicate records, an anonymous client identifier, a session identifier, and account attribution when you are signed in. It does not need to include precise device coordinates, raw search text, restaurant phone numbers, or free-text notes. We may use this history to operate the feature, understand interactions, prevent duplicate processing, improve ranking, and, where enabled and permitted, personalize meal recommendations.

When you ask SavvyWin to create a guest contributor account or perform another abuse-sensitive action, SavvyWin may require a Cloudflare Turnstile security check. Cloudflare may process limited security signals such as your IP address, TLS fingerprint, browser or User-Agent information, site key, and the associated site origin to distinguish people from bots and protect the Service. Supabase may process the short-lived challenge token as part of the authentication request. SavvyWin does not use the token for advertising or intentionally place the raw token, IP address, or provider response in SavvyWin application logs or product analytics.

Community trust and moderation information

We may collect information about Correct/Wrong feedback, confirmation votes, sold-out reports, seasonal price updates, reports, ratings, reviews, favorites, submission history, device-level identifiers, and moderation decisions to protect the quality and safety of the Service.

For structured offer reviews, we may keep current-price review contributions, prior price-version review history, edits and revision records, visit-verification results, reviewer-profile snapshots, selected tags, and aggregate counts. For designated internal QA or developer accounts, we may also keep whether a device-location bypass is enabled, who enabled or disabled it, the reason, bypass provenance, and later administrator publication or reimbursement decisions. These records help prevent duplicate or manipulated contributions, preserve the context of a review, and show community evidence for the price people actually reviewed.

AI-assisted processing information

SavvyWin may send limited submitted text, such as restaurant names, menu names, descriptions, cuisine/category signals, deal terms, corrections, and related listing metadata, to AI providers to help translate, classify, summarize, normalize, moderate, or enrich meal information.

If you upload a photo, SavvyWin may send the image and limited listing context to AI providers to check safety, relevance, photo type, quality, manipulation, or compliance with our rules before the image appears publicly. Automated results may approve, reject, label, or route a photo for human review. We aim not to send account identifiers, precise device location, or unnecessary sensitive personal information to AI providers unless necessary for a disclosed feature.

Winspector pilot information

If you participate in the Winspector pilot, we may collect your assignment dates and status; mission, offer, restaurant, local visit date, deadline, and workflow records; coarse location-verification results; private food, venue, menu or order, and receipt images; limited receipt fields such as merchant or target menu, date, food amount, tax, tip, currency, and confidence; automated and administrator check results; correction, resubmission, appeal, conflict, and override records; reimbursement calculations; e-Transfer email and payee name; payout status, reference, and date; audited receipt-access events; and operational incident and deletion records.

Precise coordinates used to start a standard Winspector mission are processed transiently for the proximity check and are not stored in mission history. We store coarse distance and accuracy buckets. If an authorized administrator has enabled Location Bypass for an account, SavvyWin does not request device coordinates for that check and instead stores the Location Bypass status and related approval audit. Receipts are private, are never placed in the public review, and are excluded from product analytics. If the original offer becomes non-public after a Winspector mission starts, we may accept a structured review linked to that mission and offer for private review of the work and reimbursement eligibility. Such a review is not displayed as a public review card, badge, or community summary contribution while kept non-public. Public review cards may show your nickname, the Winspector badge, program disclosure, and Location Bypass label where applicable, but not the receipt, payout amount, payment details, mission exception, administrator reason, or internal notes.

We may send a private image to an AI provider to check safety or expected image type, or to extract the limited receipt fields needed for mission and reimbursement review. We instruct the provider not to transcribe unrelated names, payment numbers, addresses, contact information, barcodes, or order numbers and disable provider-side storage where the provider supports that control. Automated results may be wrong and can be routed to an authorized administrator. AI never initiates an e-Transfer.

2. How We Use Information

We use information to:

3. Consent and Your Choices

Where required by law, we rely on your consent to collect, use, or disclose personal information. Your consent may be express or implied depending on the circumstances and applicable law.

You may:

You can use SavvyWin without enabling device location by searching manually or browsing the map. Device location can usually be turned off in your browser or device settings.

When in-app contribution notifications are available, you can independently turn future "Action needed" and "Published results" notifications on or off. Preference changes apply only to future events and do not remove existing notifications. The current in-app notification feature does not request operating-system notification permission or send mobile push or marketing notifications.

SavvyWin loads the Turnstile security check only when you choose a protected guest or contribution action. You may cancel the check and continue browsing without creating a guest contributor account. Turnstile is used as a necessary security measure, not for SavvyWin advertising. SavvyWin configures Turnstile in Managed mode, requests interaction only when Cloudflare determines it is necessary, and disables Turnstile feedback collection for this feature. SavvyWin does not use Turnstile pre-clearance or Enterprise Ephemeral IDs for this feature.

4. How We Disclose Information

We may disclose information:

We do not sell personal information in the ordinary meaning of selling a user's personal information for money. If future advertising, analytics, or data sharing practices are considered a "sale" or "sharing" under an applicable law, we will update this Privacy Policy and provide required choices.

We do not sell precise device location information. We do not use precise device location for third-party advertising unless we first provide a clear notice and obtain any consent required by law.

5. Third-Party Services

SavvyWin may use third-party providers such as:

Your use of Google Maps features may be subject to the Google Maps/Google Earth Additional Terms of Service and Google Privacy Policy. Third-party services may process information according to their own terms and privacy policies.

6. International Transfers

SavvyWin and our service providers may process and store information in Canada, the United States, and other countries. Privacy laws in those countries may differ from the laws where you live.

By using the Service, you understand that information may be transferred to and processed in other jurisdictions, subject to safeguards required by applicable law.

7. Retention

We keep personal information only as long as reasonably necessary for the purposes described in this Privacy Policy, unless a longer retention period is required or permitted by law.

Retention periods may differ based on the type of information:

We may retain de-identified, aggregated, or non-personal information for research, analytics, product improvement, and business purposes.

8. Security

We use reasonable administrative, technical, and organizational safeguards designed to protect personal information against unauthorized access, use, disclosure, loss, theft, or alteration.

Internal member-directory and detail access is limited to active owner or administrator operators through service-mediated controls. Normal users and read-only administrator viewers cannot access this directory, and supported setting changes create audit records.

No online service is completely secure. You should avoid submitting sensitive personal information through SavvyWin unless we specifically request it through an appropriate secure process.

9. Security Incidents

If we become aware of a security incident involving personal information, we will assess the risk and provide notices to affected individuals, regulators, or other parties where required by applicable law.

10. Accuracy, Access, Correction, and Deletion

You may request access to, correction of, or deletion of personal information we hold about you, subject to legal and practical limits.

When the feature is available, you can access your owner-private notifications through the in-app notification inbox, mark individual or all notifications as read, and manage future notification categories. These notifications are available only through the authenticated account that owns the related contribution.

When the account-deletion feature is available, a signed-in or authenticated guest contributor must confirm the irreversible request from the account that owns the data. SavvyWin first revokes active sessions and blocks further contributor access, then removes personal ownership and profile data, detaches or schedules associated media, and deletes the authentication account. A request that has been accepted cannot be cancelled. The process is idempotent and may continue or retry in the background after the app signs out; a temporary processing failure does not restore contributor access or create a second deletion request.

Account deletion removes the account profile, nickname, saved preferences and favorites, active owner-private in-app notifications, related notification-processing records, and notification preferences. Public restaurant, offer, and hours facts may remain as unattributed factual information, and minimal audit history may remain in anonymized form for security, moderation, legal compliance, and proof of deletion. SavvyWin does not use an anonymous browser or device identifier by itself to claim or delete another account's history.

After an accepted request, SavvyWin stops displaying associated photos publicly and normally deletes private originals within 30 days, except where a narrow legal, safety, fraud, dispute, or security hold applies. Removing SavvyWin's copy may not remove copies already cached or saved by third parties.

Because SavvyWin may allow anonymous use, we may not always be able to identify information as belonging to a specific individual unless you provide enough information to verify the request.

We may retain certain information where needed for legal compliance, fraud prevention, security, dispute resolution, backup integrity, moderation history, or legitimate business purposes.

11. California and Other Regional Privacy Rights

Some laws, including California privacy laws, may provide rights such as the right to know, access, delete, correct, opt out of certain sale or sharing practices, limit certain uses of sensitive personal information, and avoid discrimination for exercising privacy rights.

SavvyWin is an early-stage service and may not meet the thresholds for every regional privacy law. Where a law applies to us, we will honor applicable rights.

To make a request, contact us using the information below.

12. Children

SavvyWin is not directed to children under 13. You may not use SavvyWin if you are under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to SavvyWin, contact us and we will take appropriate steps.

13. Cookies and Similar Technologies

SavvyWin may use cookies, local storage, and similar technologies to:

Google and its partners may use advertising cookies to serve ads based on a user's prior visits to SavvyWin or other websites. Users may opt out of personalized advertising by visiting Google Ads Settings or using browser/device controls where available.

You can adjust browser settings to limit cookies or local storage, but some features may not work properly.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. The updated version will be posted with a new "Last updated" date. If changes are material, we may provide additional notice where appropriate.

15. Contact

For privacy questions, requests, or complaints, contact:

SavvyWin Privacy Email: privacy@savvywin.app

If you are not satisfied with our response, you may have the right to contact the privacy regulator in your jurisdiction, such as the Office of the Information and Privacy Commissioner for British Columbia or the Office of the Privacy Commissioner of Canada.

The interactive app is loading. If it does not load, enable JavaScript and reload this page.