Privacy
Privacy Policy
How Dine Savvy handles information. One policy for diners, one for the businesses on Dine Savvy.
Consumer Privacy Policy
For diners using the Dine Savvy app and website
Version 2.1 · Effective 20 October 2026
The short version
We built Dine Savvy to tell you where to go and to tell a venue you have arrived. Doing that needs your location, and location is the most sensitive thing we hold. So here is what we do with it, stated plainly, before the legal detail.
- We collect your location only while a quest of yours is running — from the moment you start one until it is finished, abandoned, or expires. That includes while the app is in the background, because we cannot tell whether you actually went into a place without checking more than once. When no quest is running, we are not collecting your location.
- Precise location is used for one job: deciding whether you arrived somewhere. It is not an input to our recommendations, and it does not feed an advertising profile.
- We do not sell your personal information, and we do not share it for cross-context behavioral advertising. The one situation in which your data could move to another company is if Dine Savvy is acquired — section 6 says exactly what we will do first.
- A venue is not told who you are. When you tap Let's go, each venue on your night gets a heads-up that a guest is on the way. When you arrive, the venue gets an alert that a guest on a quest has arrived. Neither one names you, and the venue cannot look up later who came. If you want a venue to recognize you, you turn that on yourself, one venue at a time, and section 5.2 lists exactly what they then see.
- Sponsors and brands never see arrivals at a named venue and never see who you follow. They get counts, not people.
- You never earn anything for drinking. Progress advances when you arrive somewhere. Ordering a non-alcoholic drink earns exactly the same progress as ordering wine.
The sections below say the same things with the precision a policy requires. If the two ever appear to disagree, the detailed sections govern — and tell us, because that means we wrote something badly.
1. Who we are and what this covers
This policy is issued by Dine Savvy LLC ("Dine Savvy," "we," "us"), 11660 164th Ct. N., Jupiter, FL 33478.
It covers the Dine Savvy consumer mobile app, the Dine Savvy website, and the notifications, emails, and text messages we send you. It does not cover:
- the separate Dine Savvy products used by restaurants, bars, brands, and distributors — those are covered by the Dine Savvy Business Privacy Policy;
- what a restaurant or bar does with information you give them directly, in person or on their own website;
- other apps and websites we link to.
Where we operate. Dine Savvy is offered in the United States only. We do not direct the service to people in the European Economic Area, the United Kingdom, or Switzerland, and this policy does not attempt to provide GDPR or UK GDPR rights.
Contact. privacy@dinesavvy.com · support@dinesavvy.com · Dine Savvy LLC, 11660 164th Ct. N., Jupiter, FL 33478.
2. Who can use Dine Savvy
You must be at least 18 years old to create a Dine Savvy account.
Some of what Dine Savvy shows and offers involves alcohol. Content, quests, offers, and rewards that involve alcohol are available only to signed-in account holders who are 21 or older, determined from the date of birth you give us at signup.
We ask for your full date of birth — month, day, and year. We do not use a "yes, I'm over 21" checkbox, because a checkbox is not an age check. We use your date of birth to apply the age gates, and to verify your identity if you contact support or make a privacy request.
Under 13. Dine Savvy is not for children. We do not knowingly collect personal information from anyone under 13. If you believe a child under 13 has given us information, email privacy@dinesavvy.com with enough detail to find the account and we will delete it.
3. What we collect
3.1 What you give us
| What | Why we need it |
|---|---|
| Name and email address | To create and operate your account |
| Mobile number, if you provide it | To send messages you have asked for, and for account security |
| Date of birth (month, day, year) | Age eligibility, the 21+ alcohol gate, and identity verification |
| Password or the identity provider you sign in with | Account security |
| Taste preferences | To make recommendations useful |
| Dietary restrictions and allergies, if you choose to enter them | To help you avoid food you cannot eat — see section 4.1 |
| Venues, wines, brands, and distributors you follow | To build your feed and send you the updates you signed up for |
| Wines and places you save | To show them back to you |
| Photos, captions, comments, and ratings you post | To publish what you chose to publish |
| Party members you invite to a quest | To run a group quest |
| Messages you send our support team | To answer you |
3.2 Location
This is the section that matters most, so it is the most specific.
When we collect it. We request location permission when you start a quest. We collect precise location while a quest of yours is active — beginning when you start a quest and ending when it is completed, abandoned, paused, or expired.
Yes, that includes the background. We cannot tell whether you actually went into a place, rather than walked past it, without sampling your location more than once while your phone is in your pocket. So while a quest is active, collection continues when the app is not open. It stops when the quest ends. Your device will tell you when background location is in use, and you can revoke the permission at any time.
What we do with it. We check whether you have arrived at a stop. That check evaluates whether you are inside the venue's boundary, whether the location reading is accurate enough to be trusted, whether you stayed long enough to have gone in, whether you arrived inside the quest's time window, whether the trip from your last stop was physically possible, and whether that arrival has already been counted.
What a passed check produces. Exactly three things: your progress moves forward and you earn the stamp or reward; the venue gets a real-time alert that a guest on that quest has arrived; and we write an arrival record.
What a failed check produces. The arrival does not count toward rewards. We keep the record, because a pattern of failed checks is how we detect people faking arrivals.
Precise location has one job. It is used for arrival verification, for fraud and abuse detection, and to produce aggregate counts. It is not an input to our recommendations and it is not used to build inferences about you. Recommendations use approximate location — roughly, which city or part of a city you are in — and what you have followed and saved.
What we never do with precise location. We do not collect it when no quest is running. We do not use it for advertising or targeting. We do not sell it, and we do not give it to data brokers. We do not disclose it to a government agency except in response to legal process we are required to honor, and we will notify you where the law permits.
Turning it off. Revoke location permission at any time in your device settings. Your account stays; arrival verification will not work, so quests will not progress.
3.3 What we collect automatically
Device type and operating system, app version, a device identifier, IP address, crash and diagnostic data, and how you move through the app — screens viewed, quests started and completed, notifications opened, content viewed and posted.
We use this to run the product, fix it when it breaks, detect fraud and abuse, and understand in aggregate what works. We do not treat time-in-app, session count, or daily active users as goals — that is a product commitment we hold ourselves to, and it is why you will not find an infinite feed designed to keep you scrolling.
3.4 Payments
If you pay for something in the app, a third-party payment processor handles it. We do not receive or store your full card number. We receive a record that a payment succeeded, the amount, and the last four digits.
3.5 What we get from others
Venue information — names, addresses, hours, categories, photos, ratings — comes from mapping and place-data providers. That is information about places, not about you. Where a provider's terms require it, we delete their content on a fixed schedule and refresh it.
4. How we use it
- To run your account and the app.
- To verify arrivals, advance quest progress, and grant rewards.
- To give each venue on your night a heads-up that a guest is on the way, and to alert a venue that a guest on a quest has arrived (section 5 says exactly what the venue is told).
- To recommend places, wines, and quests — using approximate location, follows, and saves, not precise location.
- To send you notifications, emails, and texts you have opted into, and the operational messages an account requires.
- To detect fraud, spoofed locations, and abuse.
- To produce aggregate statistics about how the service is used.
- To meet legal obligations and to establish or defend legal claims.
Model training. We do not use your personal information to train third-party general-purpose AI models, and our AI vendors are contractually barred from training on it. We may use content you have published publicly, and de-identified aggregate data, to improve our own recommendation and content features. We will not use your precise location, your dietary or allergy information, or your private messages for any model training.
What we do not use it for. We do not build advertising profiles about you. We do not use your dietary information or your drinking activity for targeting.
4.1 Health-related information
If you enter an allergy or a dietary restriction, we treat that as health-related information and hold it to a higher standard: we collect it only if you choose to enter it, we use it only to help you find food you can eat and to pass it to a venue you have chosen to share it with, and we do not sell it, share it for advertising, or disclose it to anyone else. You can delete it at any time in your profile, and deleting it removes it from any venue-recognition setting that was carrying it.
Residents of Washington and Nevada have specific rights regarding consumer health data. See section 9.
5. What venues, brands, and sponsors actually receive
This is a hard boundary in how the product is built, not a policy preference.
5.1 What a venue receives by default
When you tap Let's go: a heads-up that a guest on that night is on the way. Not your name. Not your account. Not your photo.
When you arrive: an alert that a guest on a named quest has arrived, at that moment. Not your name. Not your account. Not your photo.
Afterward: aggregate counts and timing — how many verified arrivals happened during a quest window, and when.
What a venue never receives by default: your identity, your contact details, a list of who visited and when, the ability to browse or export attendance, who you follow, what you have saved, or your notes.
5.2 If you choose to be recognized at a venue
Some venues can do better by you if they know it is you. You can turn recognition on for a specific venue you follow. It is off unless you turn it on, it applies to that one venue, and you can turn it off at any time.
When it is on, that venue can see only the following, and nothing else:
- Your first name and the initial of your last name.
- Wines and menu items you have saved at that venue.
- Any dietary restriction or allergy you have entered.
- The number of times you have visited that venue through Dine Savvy, and the date of your most recent visit.
That is the complete list. It does not include your contact details, your activity at any other venue, who you follow, or anything you have saved elsewhere. Turning recognition off is immediate, and we require the venue to stop using the information at that point.
5.3 What a brand, distributor, or sponsor receives
Aggregate engagement figures only. A sponsor is never told how many people arrived at a named venue, is never given your identity, and never sees your follow graph. Where a sponsor originated a multi-venue quest, they see cross-venue totals — never a per-venue breakdown, and never a breakdown that could be reduced to a single venue.
Sponsorship is a flat fee. We do not bill anyone per arrival, which means nobody has a commercial reason to want your individual movements.
5.4 What we say about results
When we report to a venue, we report verified arrivals during a quest window. We do not tell a venue we "brought" them guests or generated revenue, because we have not run the comparison that would make that claim true. This matters to you because a business sold a causal claim will eventually ask us for the individual data that would prove it, and the answer will be no.
6. Who else we share with
- Service providers who run parts of the service for us — hosting and storage, database and search, push notification delivery, email and text delivery, customer relationship and marketing automation, analytics, payment processing, fraud prevention, and AI processing for content and recommendation features. They may use your information only to perform the service for us, and they are contractually barred from using it for anything else, including their own model training.
- Other users, for anything you post publicly or share into a group quest.
- Legal and safety — where required by law or valid legal process, and where necessary to protect someone's safety, investigate fraud, or defend legal claims.
- A business transfer — if Dine Savvy is acquired, merges, or sells assets, your information may transfer as part of it. Before that happens we will notify you and give you the opportunity to delete your account and your data first. We cannot bind a future owner to this policy, so we are not going to pretend we can; what we commit to is the notice and the chance to leave.
A current list of our service-provider categories and the vendors in each is available on request from privacy@dinesavvy.com.
We do not sell or share your personal information
We do not sell your personal information for money or other value, and we do not share it for cross-context behavioral advertising, as those terms are used in California, Texas, and other state privacy laws. We have not done so in the preceding twelve months. This includes precise location data, which we will not sell under any circumstances. The only route by which your data could reach another company is the business transfer described above, and it comes with notice first.
Because there is nothing to opt out of, an opt-out preference signal such as Global Privacy Control has no sale or sharing to stop — but we treat it as an instruction to limit non-essential tracking anyway.
7. Notifications, email, and text messages
Push notifications. You control these in your device settings and in the app. We cap marketing pushes, we observe quiet hours, and we automatically reduce how often we message you if you stop opening what we send. Operational messages — a party invite, a quest expiring, a security alert — follow different rules and are limited to what the feature requires.
Email. Every marketing email has an unsubscribe link. Unsubscribing does not stop transactional email about your account.
Text messages. We send marketing texts only if you gave express written consent. Message and data rates may apply. You can withdraw consent by any reasonable means — reply STOP, reply in your own words, or email privacy@dinesavvy.com — and we will stop within 10 business days and usually immediately. Reply HELP for help. Consent to marketing texts is never a condition of using Dine Savvy.
8. How long we keep things
| Data | How long |
|---|---|
| Account and profile | While your account is open, then 30 days after you delete it |
| Precise location readings collected during a quest | 90 days from collection, then deleted — except as noted immediately below |
| Precise readings that are part of an arrival flagged as failed or suspicious | 24 months, for fraud and abuse analysis, then deleted |
| Arrival records (that an arrival happened, where, and when) | 24 months, then deleted or de-identified |
| Content you posted publicly | Until you delete it, or your account closes |
| Payment and transaction records | 7 years, to meet tax and accounting obligations |
| Support correspondence | 24 months |
| Aggregate and de-identified statistics | Indefinitely |
A note on the two location rows. A failed check is itself a location reading. We are telling you plainly that the 90-day rule has an exception, because a policy that promised 90 days while quietly keeping suspicious readings for two years would be a policy that misled you.
Backups. Deletion propagates to our backups on our backup rotation cycle rather than instantly. Deleted data in a backup is not returned to service.
De-identified data. We de-identify in line with the CCPA standard, we prohibit re-identification contractually and technically, and we will not attempt to re-identify. We are not going to claim location data is impossible to re-identify, because that is not true of location data anywhere.
We may keep information longer where a law, a legal hold, or an active dispute requires it, and only what that purpose needs.
9. Your choices and your rights
If you are in the United States, regardless of your state, you may:
- See what we hold about you and get a copy in a portable format.
- Correct anything inaccurate.
- Delete your account and the data attached to it, subject to the exceptions in section 8.
- Withdraw location permission at any time, in device settings.
- Opt out of marketing email, text, and push at any time.
- Not be discriminated against for exercising any of these. Your price and your service do not change because you asked.
We extend these to every U.S. user rather than only to residents of states that require them, because operating two standards is how mistakes happen.
How to make a request. Email privacy@dinesavvy.com from the address on your account, or use the controls in the app. We acknowledge receipt within 10 business days and respond substantively within 45 days, extendable once by another 45 days for a complex request, with notice before the first period ends. We verify it is you before acting.
Export before you delete. Deleting your account removes your points, badges, and unredeemed rewards. Export your data first — the option appears before you confirm deletion, and we will honor an export request for 30 days after deletion, matching how long we hold the account.
Authorized agents may act for you with written authorization; we may still contact you to confirm.
Appeals. If we refuse a request we will tell you why. Reply to appeal; we answer within 45 days. If we deny the appeal we will tell you how to complain to your state attorney general.
State-specific notes
California. You have the rights above under the CCPA, including the right to know the categories of personal information collected, the sources, the purposes, and the categories of third parties we disclose to — set out in sections 3, 4, 5, and 6. Because we do not sell or share personal information, there is no "Do Not Sell or Share" opt-out to exercise; if that ever changes we will publish the link before it does.
Sensitive personal information. Precise geolocation is sensitive personal information under California law. We use it only for arrival verification, fraud detection, and aggregate counts — not to infer characteristics about you. You may nonetheless direct us to limit its use by emailing privacy@dinesavvy.com or revoking location permission on your device, and we will honor that; we would rather give you the control than argue about whether an exemption applies.
Washington and Nevada. Allergy and dietary-restriction information, and location information that reveals an attempt to acquire health services, may be consumer health data under Washington's My Health My Data Act and Nevada SB 370. We collect this data only with your affirmative consent, use it only as described in section 4.1, do not sell it, and will delete it on request.
Maryland. We limit our collection and processing of sensitive data, including precise geolocation, to what is reasonably necessary to provide the quest features you asked for. Maryland residents may contact us at privacy@dinesavvy.com regarding any processing they believe exceeds that limit.
Texas. Precise geolocation is sensitive data under the Texas Data Privacy and Security Act. We obtain your consent before collecting it and we do not sell it.
Rewards and your data
Our points, badges, and rewards program gives you something of value. It is not conditioned on giving us data beyond what an account requires, and turning off location does not cost you your existing points or badges — it only stops new quest progress, because arrival verification is what quest progress is. If you would like our current statement of the value of the personal information involved in the program and how we calculated it, email privacy@dinesavvy.com and we will send it.
10. Categories of personal information
Stated in the categories state privacy laws use, so you can compare us against other services.
| Category | Do we collect it? | Do we sell or share it? |
|---|---|---|
| Identifiers (name, email, phone, device and account IDs, IP address) | Yes | No |
| California customer records (name, phone, payment information) | Yes | No |
| Protected classifications | Age only, for the age gates | No |
| Commercial information (what you saved, followed, viewed, purchased) | Yes | No |
| Biometric information | No | No |
| Internet and network activity | Yes | No |
| Precise geolocation — sensitive | Yes, only during an active quest, with your permission | No |
| Audio, visual, or similar (photos you post) | Yes, what you post | No |
| Health-related (allergies, dietary restrictions) — sensitive | Only if you enter it | No |
| Professional or employment information | No | No |
| Education information | No | No |
| Inferences (taste and recommendation profiles) | Yes — built from follows, saves, and ratings, not from precise location | No |
11. Security
We encrypt data in transit and at rest, keep point-in-time backups, limit internal access to people who need it, and log administrative access.
On location spoofing, honestly. Arrival validity is decided on our servers, using signals your device reports, together with device-integrity checks, mock-location detection, dwell requirements, and travel-feasibility checks. That makes faking an arrival substantially harder and lets us detect patterns of it. It does not make it impossible, because the coordinates originate on a device we do not control, and we are not going to tell you otherwise.
No system is perfectly secure. If a breach affects your personal information we will notify you and the relevant authorities as the law requires.
12. Changes to this policy
For a material change — a new category of data, a new purpose, a new disclosure, or any change to section 5 — we will tell you by email or in-app notice before it takes effect, not after. Minor changes are posted here with an updated date. We keep the previous version available so you can see what changed.
13. Contact
Dine Savvy LLC 11660 164th Ct. N., Jupiter, FL 33478 privacy@dinesavvy.com · support@dinesavvy.com
US English. This policy is governed by the law of the State of Florida.
Business Privacy Policy
For restaurants, bars, brands, distributors, and their teams
Version 2.1 · Effective 20 October 2026
The short version
You are buying placement in front of diners and a verified signal when one of them walks in. What you are not buying is data about them.
- You are told when a guest on a quest is on the way, and when they arrive. You are not told who. You cannot look up later who came.
- You do not receive individual attendance records, diner identities, or the follow graph. Not on any tier, not as an add-on, not on request.
- A diner can choose to be recognized at your venue. That is their decision, made venue by venue, off unless they turn it on. Section 4.2 lists exactly what you then see — it is a short, closed list.
- Sponsors and brands receive aggregate engagement only — never a per-venue arrival breakdown.
- We do not sell or share personal information, yours or your guests'.
That boundary is not a limitation we apologize for. It is the reason diners turn location on, and a diner with location on is what makes an arrival signal worth paying for.
The rest of this document is about your data — your business information, your team's accounts, and what you upload.
1. Who we are and what this covers
This policy is issued by Dine Savvy LLC ("Dine Savvy," "we," "us"), 11660 164th Ct. N., Jupiter, FL 33478.
It covers the Dine Savvy merchant app, the business and creator web surfaces, the business areas of our website, and our sales and support communications with you. It applies to business users — restaurants, bars, hotels, beverage brands, distributors, agencies, and the people who work for them.
The Dine Savvy Privacy Policy (consumer) covers diners. Where this policy describes what you receive about diners, the consumer policy is the controlling statement of our commitments to them, and we will not agree with you to exceed it.
Where we operate. The United States only.
Contact. privacy@dinesavvy.com · support@dinesavvy.com
2. What we collect from you
2.1 Business information
Legal and trading name, addresses, phone numbers, website, venue category, hours, menu and beverage information, capacity, photographs, alcohol licence details and licence numbers, tax identification, and the bank or card details used to pay us.
2.2 Information about the people who use the account
Business accounts are used by people, and information about those people is personal information even though the account is commercial. We collect: name, work email, work phone, job title, the venue or venues you are assigned to, login credentials, and, where you have chosen to track them, staff alcohol-service certifications and their expiry dates.
A note on certifications: we track whether a certification exists and when it expires. Dine Savvy does not issue certifications, and nothing we provide should be represented as satisfying a state training mandate. Requirements differ by state and some states mandate training only an approved provider can deliver.
2.3 What you upload or connect
- Contact lists you upload for your own marketing.
- Content you create or generate — copy, images, video, offers, quest routes.
- Social account connections you authorize, and the access tokens that come with them.
- Point-of-sale, reservation, or accounting connections you authorize, and the data they return.
2.4 What we collect automatically
Device and browser information, IP address, log data, and how your team uses the product — screens viewed, features used, content generated, approvals given, campaigns run, and notifications opened.
2.5 What we get from others
Public business listings, mapping and place-data providers, licensing registries, and business-data providers we use for prospecting and enrichment. Where a provider's terms require it, we delete their content on a fixed schedule and refresh it.
3. What we do with it
- Run your account, provision your team, and deliver the tier you bought.
- Publish and maintain your listing.
- Run quests you originate or accept, and send you heads-up and arrival alerts.
- Generate, queue, and — after your approval — publish content to your channels.
- Send you operational messages, and marketing about Dine Savvy where you have not opted out.
- Bill you and collect payment.
- Report performance to you.
- Provide support, detect fraud, and secure the service.
- Produce aggregate and de-identified statistics about how the product is used, which may inform our own product and marketing. We de-identify to the CCPA standard, prohibit re-identification, and will not attempt it.
- Meet legal obligations, including those specific to alcohol regulation.
What we do not do. We do not sell your business information. We do not give your data to a competitor. We do not use any purchasing information you share with us, or your guest-facing content, to build a product sold to your suppliers, and we will not accept payment from a supplier for access to it.
4. The diner-data boundary
The most important thing in this document. It is enforced in the architecture, and it does not bend for a large account.
| You receive | You do not receive |
|---|---|
| A heads-up when a guest on a quest is on the way, and a real-time alert when they arrive, identifying the quest | The diner's name, account, contact details, or photo |
| Aggregate counts of verified arrivals during a quest window, and their timing | An individual-level list of who visited and when |
| Aggregate engagement figures for content and offers | The ability to browse, search, or export attendance |
| The closed list in section 4.2, for a diner who has chosen recognition at your venue | Who a diner follows, or what they have saved anywhere other than your venue |
4.1 How recognition works
A diner may turn on recognition for a venue they follow. It is off by default, granted one venue at a time, and withdrawable at any time. You cannot request it, prompt for it inside our product, or condition service on it.
4.2 Exactly what recognition shows you
When a diner has turned recognition on for your venue, you see only the following:
- Their first name and the initial of their last name.
- Wines and menu items they have saved at your venue.
- Any dietary restriction or allergy they have entered.
- The number of times they have visited your venue through Dine Savvy, and the date of their most recent visit.
That is the complete list. It excludes contact details, activity at any other venue, the follow graph, and anything saved elsewhere. This list is the same one published in the consumer Privacy Policy, so the diner and you are reading the same disclosure.
Your obligations when you receive it. Treat it as confidential. Use it only to serve that guest during and around their visit. Do not export it, add it to a marketing list, sell it, or use it for anything the diner did not agree to. Withdrawal is immediate and you must stop using the information at that point. Item 3 is health-related information and carries additional restrictions under Washington and Nevada law.
4.3 What we will and will not say about results
We report verified arrivals during a quest window. We do not report that Dine Savvy "brought" you guests, generated revenue, or lifted your sales, because we have not run the held-out comparison that would make a causal claim true. If you see that language anywhere in our materials, it is an error and we want to know.
Some of our figures are counts we can stand behind. Some would be forecasts, and where we have no distribution of real routes to forecast from, we will say so rather than produce a range.
4.4 Sponsors and industry members
A brand, distributor, or other sponsor receives aggregate engagement only. A sponsor is never told how many arrivals occurred at a named venue, never given diner identities, and never shown the follow graph.
This applies to a sponsor that originated the quest. An originator sees cross-venue totals, not a per-venue breakdown, and we suppress any breakdown that could be reduced to a single venue.
Sponsorship is priced as a flat fee. We do not bill any party per arrival, which removes the commercial incentive to erode this line.
5. When you are the controller and we are the processor
For some data you decide what happens to it and we act on your instructions.
This applies to: contact lists you upload; your own customers' data flowing through connections you authorize; content you create; and your business records inside the platform.
When it applies:
- We process that data only to provide the service and on your documented instructions.
- We do not sell it, and we do not retain, use, or disclose it outside our direct business relationship with you or for any purpose other than the services — the restrictions a service provider is required to accept under California law.
- We require confidentiality from personnel with access.
- We use sub-processors under written terms no less protective than these, and we will give you notice before adding a new sub-processor.
- We help you respond to a data-subject request or a security incident affecting that data.
- We delete or return it on termination, subject to section 7.
- You may take reasonable and appropriate steps to confirm we are using the data consistently with your obligations.
We will sign a Data Processing Addendum containing these terms on request; ask at privacy@dinesavvy.com. Where your own compliance program requires one, sign it before uploading a contact list.
You are responsible for the lawfulness of what you give us. You warrant that you hold the consents and permissions required — including express written consent for marketing text messages and a valid basis for marketing email — and that your own privacy notice covers the sharing. If a regulator or a recipient challenges a list you uploaded, that is your list.
6. Who we share your information with
- Service providers — hosting and storage, database and search, email and text delivery, push notification delivery, customer relationship and marketing automation, payment processing, analytics, fraud prevention, business-data enrichment, and AI processing for content generation and recommendation features. They may use your information only to perform their service for us.
- Publicly, for everything in your listing and any content you publish.
- Other businesses in a shared quest — participating venues see which venues are in the quest and cross-venue aggregate results. They do not see each other's individual guest data, and, per section 4.4, an originator does not receive a per-venue arrival breakdown.
- Legal and safety — where required by law or valid legal process, including a request from an alcohol regulator, and where necessary to investigate fraud or defend legal claims.
- A business transfer — if Dine Savvy is acquired or merges.
A current list of our service-provider categories and the vendors in each is available on request from privacy@dinesavvy.com. Ask and we will add you to the sub-processor change-notification list.
We do not sell or share personal information
We do not sell personal information for money or other value, and we do not share it for cross-context behavioral advertising, as those terms are used in California, Texas, and other state privacy laws. We have not done so in the preceding twelve months. That applies both to information about your team and to diner data.
7. How long we keep things
| Data | How long |
|---|---|
| Business account and listing | While your account is active, then 12 months, then deleted or de-identified |
| Individual user accounts on your team | Until removed by an administrator, then 30 days |
| Content you generated or published | While active, then 90 days to allow export |
| Approval records: who approved which asset, the exact rendered text and media, and when | 7 years — see below |
| Aggregate arrival and campaign reporting | 24 months |
| Billing and transaction records | 7 years, to meet tax and accounting obligations |
| Support correspondence | 24 months |
| Contact lists you uploaded | Until you delete them, or 30 days after termination |
| Aggregate and de-identified statistics | Indefinitely |
Approval records, stated honestly. Seven years is our own compliance standard, not a period any regulation we have identified requires. We chose it because an advertising or trade-practice inquiry can arrive years after a campaign, and the approval record is what answers it. We will not shorten it at a customer's request, and it is an express exception to the individual deletion right in section 8. We could technically delete these records; we have decided not to, and we would rather say that than claim we are unable to.
Content you generated. You have 90 days from termination to export the assets created in your account. After that we may delete them. Ownership is addressed in the Business Terms of Use.
We may retain information longer where a law, legal hold, or active dispute requires it.
8. Rights of the people on your team
The people using your business account are individuals with privacy rights, and we honor them directly.
Any individual with a Dine Savvy business login may ask us to see, correct, or delete the personal information we hold about them, and may opt out of our marketing. Email privacy@dinesavvy.com from your work address. We acknowledge within 10 business days and respond within 45 days, extendable once by 45 days with notice.
Three limits, stated plainly. Deleting an individual's personal information does not delete the business account or the business records that person created — those belong to the business. We cannot delete an approval record, for the reason in section 7. And where we hold the data as your processor rather than as controller, we will route the request to you.
We extend these rights to all U.S. users regardless of state and will not treat you differently for exercising them. If we refuse we will tell you why; reply to appeal; we answer within 45 days; and if we deny the appeal we will tell you how to complain to your state attorney general.
9. Security
We encrypt data in transit and at rest, keep point-in-time backups, restrict internal access to those who need it, log administrative access, and record content approvals with the approver, the exact content, and the timestamp.
Access tokens for connected accounts are stored encrypted and used only for actions you authorized. Revoke a connection at any time from your account settings and from the provider's own settings.
Breach notification. If a security incident affects personal information in your account, we will notify your account administrators without undue delay and no later than 72 hours after we confirm it, with what we know at the time, and we will keep updating you as we learn more. We will not wait for a complete picture before telling you something happened. We will also notify regulators and affected individuals where the law requires.
We will provide a Security Exhibit describing our controls on request, and it may be incorporated into your agreement.
No system is perfectly secure.
10. Regulated-industry note
Dine Savvy serves alcohol licensees and alcohol industry members, which affects how information moves.
- Approval records are compliance artifacts. Every AI-generated asset published to your channels carries a record of who approved it, the exact rendered text and media, and when. See section 7.
- Age-gate and disclosure state is recorded on published content.
- Supplier money and purchase recommendations stay in separate rooms, provably. We do not accept payment from an industry member in exchange for directing a retailer's purchasing, and we do not furnish an industry member with data about a retailer's purchasing decisions in exchange for payment.
- We do not touch alcohol payment funds. Money for alcohol purchases moves between you and your distributor, directly, on your existing rails.
On the federal tied-house exceptions, precisely. Two different provisions are often conflated, and getting them right matters to anyone whose counsel will read this.
27 CFR § 6.98 (advertising service) covers an industry member listing retailers in the industry member's own advertisement. It requires all three of the following: the advertisement does not contain the retail price; the listing is the only reference to the retailers and is relatively inconspicuous in relation to the advertisement as a whole; and the advertisement does not refer only to one retailer or to commonly controlled retailers.
27 CFR § 6.96 (consumer promotions) is the separate provision governing coupons and direct offerings to consumers, on its own conditions.
Our publication controls test the two-or-more-unaffiliated-retailers condition. They do not, and cannot, determine whether a given quest satisfies the "relatively inconspicuous" condition or whether § 6.98 is the right provision for it at all — those are judgments about the finished creative. State tied-house law is stricter than federal in several states and is assessed separately. Any industry-member-funded activity should be cleared by your own trade-practice counsel.
This section describes how we operate. It is not legal advice, and it does not relieve you of your own licensing obligations.
11. Changes to this policy
For a material change — a new category of data, a new purpose, a new disclosure, or any change to the diner-data boundary in section 4 — we will notify account administrators by email at least 30 days before it takes effect. Minor changes are posted here with an updated date. We keep the previous version available.
12. Contact
Dine Savvy LLC 11660 164th Ct. N., Jupiter, FL 33478 privacy@dinesavvy.com · support@dinesavvy.com
US English. This policy is governed by the law of the State of Florida.
