Privacy policy
Effective date: November 9, 2026
Last updated: November 9, 2026
This policy explains what personal data Cook to Counter collects, how we use it, who we share it with, and the choices you have. We wrote it in plain English. If something is not clear, email us at hello@cooktocounter.com. Our Terms of Service (at /terms) explain the rules for using Cook to Counter. This policy is part of those terms.
The short version
- Cook to Counter is software. Food businesses use it to run their own online stores. We do not cook or sell food.
- Each business is responsible for how it uses its customers' data. If you buy from a business, read that business's privacy policy too.
- We do not sell your personal data.
- We use Google Analytics, a service from Google, on our public information pages only, on our own main web address only. It never runs on pages that are mainly a form, such as contact, sign-up, catering, sign-in, account, checkout and admin pages. Some public pages have a small sign-up form, such as our waitlist or a business's text sign-up, and Google Analytics never collects what you type into any form. It does not load if your browser sends a Do Not Track or Global Privacy Control signal.
- Our emails can tell us when they are opened and which links are clicked. You can turn this off from any tracked email.
- You can join our waitlist with your email, your phone number, or Google. We use it to tell you when we launch and to send occasional updates. You can leave any time.
- We never sell or share your mobile number or your consent to get texts with anyone for their marketing.
- Browser notifications are off unless you turn them on. You can turn them off any time.
- Our chat helper, Ask Basil, is planned, not built. When it launches, it will be an AI, Basil's voice will be computer-generated, and chats will be saved.
Who we are
Cook to Counter is run by Foodie Guy L.L.C., a North Carolina limited liability company, doing business as Cook to Counter. When this policy says "Cook to Counter," "we," "us" or "our," it means Foodie Guy L.L.C.
Foodie Guy L.L.C.
doing business as Cook to Counter
1933 St Paul St
Charlotte, NC 28216
Email: hello@cooktocounter.com
Who is responsible for your data
Cook to Counter is a platform. Many separate food businesses use it. That means two kinds of websites, and two kinds of responsibility.
Our own sites. These are cooktocounter.com and its pages for signing up, signing in and managing a business account. We decide how data is used on these sites. We are responsible for it.
Each business's storefront. Each business that uses Cook to Counter gets its own storefront. It lives at an address like yourbusiness.cooktocounter.com, or at the business's own web address. The business decides what to sell, what to collect from its customers, and how to use it. The business is responsible for that data. We store and process it for the business so its storefront, orders and messages work.
Here is who does what:
- Foodie Guy L.L.C. (the platform). We run the software and our own sites. We are responsible for data about people who visit our sites, businesses that sign up with us, and their owners and staff. We also use some storefront data for our own limited purposes: to keep the service secure, prevent fraud, fix problems, bill businesses for their plan, verify sellers, and follow the law.
- Each business (the seller). The business is responsible for data about its own customers. That includes orders, customer accounts, its own marketing emails and texts, reviews, and any tools it adds to its storefront. A business may add its own Google Analytics account and its own marketing tools. Those are the business's choices, under its own policy.
- Buyers and visitors. You choose which businesses to buy from. Your data goes to the business you order from.
What this means for you:
- If you shop on a business's storefront, read that business's privacy policy. If the business has published one, its link is in the storefront footer. If you do not see a link, ask the business for its privacy policy.
- To ask a business about your data, contact the business first. If you contact us instead, we will pass your request to the business and help it respond.
- This policy covers our own sites and our own uses of data. It does not cover how a business uses its customers' data.
Data we collect
Data you give us
What we collect depends on how you use Cook to Counter.
Business owners and staff:
- Name, email address and phone number.
- Business name, web address, the types of food you sell, and your plan.
- Business address and pickup locations.
- Settings, menus, photos and other content you add.
- Records of actions in your account, such as setting changes and who made them. Some setting changes are emailed to the business's owners.
Sellers in plates mode: plates mode is planned, not built. Before it launches, we will update this policy to describe the seller verification details we collect.
Buyers:
- Name, email address and phone number.
- Orders, pickup or delivery times, and delivery address if you choose delivery.
- Messages you send to a business, and reviews and photos you post.
- Plan details if you sign up for a weekly plan or membership.
Anyone who contacts us:
- What you send us, such as a contact form message or a support request.
How you sign in
You can sign in three ways:
- Passkey. Your device creates a passkey. We store only the public part. Your fingerprint, face or device PIN stay on your device. We never see them.
- One-time email code. We email you a short code. It stops working after 10 minutes. We keep only a scrambled copy of it, not the code itself.
- Google sign-in. If you choose it, Google shares your name, email address, profile picture and a Google account ID with us. We keep your name, email address, Google account ID and whether Google has verified your email. We do not keep your profile picture. We use these details only to create your account and sign you in. We do not ask Google for anything else, such as your contacts or files.
Data we collect when you visit
- Server logs. When you visit, our servers and our web host (Namecheap) record basic technical details, such as your IP address, browser type, the page you asked for and the time. We use these to run the site, keep it secure and fix problems. We usually keep these logs for up to 90 days, unless we need them longer to investigate a security issue, stop abuse or follow the law.
- Cookies. We use cookies that the site needs to work. They keep you signed in, protect forms from misuse and remember your choices, such as light or dark mode. On some public pages, Google Analytics also sets cookies. See "Website analytics" below.
- Location. When you type an address, we use an address autocomplete service to suggest matches. Geoapify is the default. Google Places is an optional alternative that a business or we may turn on. The service in use receives what you type so it can suggest matches.
Data we get from others
- Payment companies tell us whether a payment went through. Stripe and Square process cards. We do not receive or store full card numbers. They send us limited details so we can show which method you used: card brand, last four digits and expiry month and year. If you pay with a digital wallet, we may also keep the wallet type (for example Apple Pay, Google Pay, Link, Cash App Pay or Amazon Pay) and a short display label.
- Stripe tells us the result of a seller's identity check and the status of a seller's payout account.
- Google shares the details listed above when you use Google sign-in or join our waitlist with Google.
- Delivery partners send updates on delivery status.
How we use data
We use data to:
- Run the service: create accounts, sign you in, show storefronts, take orders and send order updates.
- Process payments and payouts through our payment partners.
- Verify sellers and check permits before they can sell plates.
- Send emails and texts you asked for or agreed to.
- Answer questions through support and Ask Basil.
- Keep the service secure, stop fraud and abuse, and fix problems.
- Understand how people use our public pages, so we can improve them.
- Bill businesses for their Cook to Counter plan.
- Follow the law and enforce our terms.
Our waitlist
Before Cook to Counter opens to everyone, you can join our waitlist.
How you can join. Use your email address, your mobile number, or both. Or use "Sign in with Google."
Accounts. If you join with Google, we set up your Cook to Counter account for launch, marked as verified by Google. If you join with your email address, we set up an account for launch that stays unused until you sign in with a one-time email code. If you join with only your phone number, you are on the waitlist and we do not create an account.
What we collect.
- If you use email: your email address, and your name if you give it.
- If you use your phone: your mobile number, and your name if you give it.
- If you use Google: your name, email address, Google account ID and whether Google has verified your email. Google also sends your profile photo if you have one; we do not keep it. We ask Google only for the basic "openid", "email" and "profile" permissions. We do not get your Google contacts, calendar, files, or any other Google data.
- If you choose, your business name and the kind of food business you run.
- A consent record for each way you agreed to hear from us. See "Email consent records" and "Text messages" below.
Emails when you join. If we have your email address, we send you one thank-you email when you join, and we email you when we launch. That includes joining with email, and joining with your phone number or Google when an email address comes with it. You do not need to click anything in the thank-you email to stay on the list. Every email has an unsubscribe link. We send other updates by email only if you check the box asking for them.
How we use it.
- To tell you when Cook to Counter launches.
- To send occasional updates about Cook to Counter, by email or text, only if you checked the box for that channel.
- To keep a record that you agreed, and to honor it when you opt out.
- To keep the waitlist free of fake and duplicate sign-ups.
We do not sell waitlist data. We do not add your details to any business's customer list.
How long we keep it. We keep your waitlist entry until 12 months after launch, or until you leave the waitlist, whichever comes first. If you open an account, your entry may be linked to it. We keep consent and opt-out records longer, for 5 years after the last message or opt-out, so we can show that we followed your choices.
How to leave the waitlist.
- Email: click "unsubscribe" in any waitlist email.
- Text: reply STOP to any waitlist text.
- Or email hello@cooktocounter.com and ask us to remove you. We will delete your entry, except for the short opt-out record we need so we do not contact you again.
- If you joined with Google, you can also remove Cook to Counter's access in your Google Account settings. That stops Google from sharing new details with us. It does not delete what we already have, so also ask us to remove you.
Website analytics (Google Analytics)
We use Google Analytics 4 to count visits to our public information pages and see how people find them. Here is exactly how we set it up:
- Which website. It runs only on our own main web address, cooktocounter.com, and its www version. It does not run on any other address.
- Which pages. It runs only on public information pages, the kind anyone can read without signing in.
- Not on form pages or private pages. It never runs on pages that are mainly a form: contact pages, text sign-up pages, catering quote and catering order pages, and sign-in, account, checkout, business owner or admin pages.
- Never what you type. Some public pages include a small form, such as the waitlist form on our home page. Google Analytics may count a visit to those pages, but it never collects what you type into any form, such as your name, email address or phone number.
- Your browser signals come first. If your browser sends a Do Not Track signal or a Global Privacy Control signal, Google Analytics does not load at all.
- Web addresses are trimmed. Before a page address goes to Google, we remove everything after the question mark except campaign tags (the "utm" values). That keeps codes and other details in web addresses away from Google.
- No ad features. Google's advertising features and Google signals are turned off.
When Google Analytics loads, your browser sends Google details such as the page you are on and your IP address, and Google may set or read cookies. Google's own policies explain how Google uses this data:
- Google Privacy Policy: https://policies.google.com/privacy
- How Google uses data from sites or apps that use its services: https://policies.google.com/technologies/partner-sites
- Google Analytics opt-out browser add-on: https://tools.google.com/dlpage/gaoptout
Businesses' own analytics. A business may add its own Google Analytics account to its storefront. That account loads only on the business's main web address (and the same address starting with www), with the same page limits: public information pages only, never on pages that are mainly a form (contact, text sign-up, catering quote and catering order, sign-in, account, checkout, business owner or admin pages), and never collecting what you type into a form. Some storefront pages, such as the home page and menu, include a small text sign-up form in the footer; the business's analytics may count visits to those pages but never collects what you type. A business's address on cooktocounter.com counts only if it is that business's main web address. Our analytics account never loads on a business's storefront. The business decides how to use its own analytics. See the business's privacy policy.
We send two kinds of email:
- Service emails, such as sign-in codes, order confirmations, pickup and delivery updates, receipts and account notices.
- Marketing emails, such as news and offers. We send these only as the law allows, and you can unsubscribe at any time.
Businesses on Cook to Counter can also send emails to their own customers through our software.
Open and click tracking
Most emails sent through Cook to Counter contain a tiny image, often called a tracking pixel. When your email app loads it, we record that the email was opened, when, and how many times. Ordinary links in the email go through our site first, so we can count clicks.
- We use this to see whether emails arrive and which messages are useful.
- These signals are not exact. Some email apps block images. Others open emails and links on their own.
- We do not add tracking to sign-in links, order links or other private links.
- We do not keep your IP address, device or location from the pixel.
- To turn tracking off, use the "Turn this off" link at the bottom of any tracked email. We will stop tracking emails to that address from whoever sent that email: that business, or us.
Email log
We keep a copy of each email sent through Cook to Counter in an email log for 90 days. The log shows what was sent, to whom, when, whether it was opened or clicked, and a preview of the email.
- Our staff can see the log for emails we send. A business's owners, and staff they allow, can see the log for that business's emails.
- We do not keep the text of sign-in code emails in the log. Private links are hidden.
- We delete entries after 90 days.
Email consent records
When you join our waitlist with an email address, or check the box to get updates from us, we keep a record of it:
- the email address,
- the date and time you agreed,
- the version of the consent wording you saw,
- where you agreed (for example, the waitlist form or Google sign-up),
- your IP address and browser details (user agent) at that moment, and
- that we sent you one thank-you email when you joined. We do not ask you to confirm by email.
We use this record to show that you agreed and to honor your choices. When you unsubscribe, we record that too. Businesses keep their own consent records for their own emails.
How to stop marketing emails
- Click "unsubscribe" in any marketing email from us. We will stop within 10 business days.
- To stop marketing emails from a business, use the unsubscribe link in that business's email.
- You will still get service emails, such as order updates and sign-in codes, while you have an account or an open order.
Text messages
We and the businesses on Cook to Counter may send texts.
- Order texts are about an order you placed, such as pickup reminders and delivery updates.
- Marketing texts, such as a business's Text Club, are sent only if you agree to get them. You do not have to agree to buy anything.
- How often. The number of texts is shown when you sign up.
- Cost. Message and data rates may apply.
- To stop, reply STOP to any text. You can also tell us or the business in any other reasonable way, such as by email. For help, reply HELP, or contact the business that texts you.
- When you join a business's Text Club, you agree to get texts from that business only. Your consent does not carry over to any other business on Cook to Counter.
Texts from Cook to Counter. If you give us your mobile number on our waitlist and check the box to agree, we send you recurring automated marketing texts from one Cook to Counter phone number: a launch notice and occasional updates about Cook to Counter, up to 4 messages a month. Texting is planned, not built. We will add the number to this policy before we send the first text. Consent is not a condition of purchase, and you do not have to agree to texts to join the waitlist. Message and data rates may apply. Reply STOP to stop, or tell us another way, such as by emailing hello@cooktocounter.com. Reply HELP for help. The full texting terms are in our Terms of Service.
Text consent records. When you agree to get texts, from us or from a business, we keep a record of it:
- the mobile number,
- the date and time you agreed,
- the version of the consent wording you saw,
- where you agreed (for example, our waitlist form or a business's Text Club sign-up), and
- your IP address and browser details (user agent) at that moment.
When you reply STOP, or ask us to stop in another reasonable way, we record that too, and we stop marketing texts to that number from that sender. We may send one text to confirm you are opted out.
Our text provider. We send texts through a text messaging company that acts as our service provider. The provider we use can change. Examples include Bird, Sent.dm, Pingram and Twilio. It may use mobile numbers and messages only to deliver texts for us.
We do not share your mobile number or text consent. We do not sell, rent or share mobile numbers or text opt-in data (your consent to get texts) with any third party or affiliate for their marketing or promotional purposes. We share them only with the service providers that help us send texts. This promise overrides anything else in this policy.
Browser notifications
Cook to Counter can send notifications to your browser, or to the app if you added it to your home screen. Businesses can use this too, to tell their customers about their orders. Owners and staff can get notifications about their business.
- Off unless you turn them on. We first show our own message that explains what you will get. Your browser then asks if you want to allow notifications. Nothing is sent unless you say yes to both. You do not need notifications to order or use your account.
- If you add the app to your phone. When you install the app on your phone's home screen, we may offer you notifications. They stay off unless you allow them.
- No personal details on your lock screen. Notification text does not include personal details. Order notifications use the order number, not your name, what you ordered or how much you paid.
- What we store. When you turn notifications on, we store:
- the push subscription your browser gives us: a web address for your browser's push service and the keys used to encrypt messages to it,
- your browser and device type only, such as "Chrome on Android,"
- when you turned notifications on, and the types of notifications you chose,
- which business or site you turned them on for, and your customer or staff account if you are signed in, and
- when we last sent one, and whether sending failed.
- Who carries the message. Your browser maker runs a push service that delivers the notification to your device. Depending on your browser, that is Google, Apple, Mozilla or Microsoft. The push service handles messages under its own privacy policy.
- Staff who leave a business. When someone is removed from a business's team, they stop getting that business's staff notifications.
- How to turn them off. Use the notification setting in the app or your account. Or turn notifications off for the site in your browser or device settings.
- When we delete it. We permanently delete the push subscription when you turn notifications off, and when your browser's push service tells us it no longer exists.
- Marketing notifications. A business may send news or offers by notification only if you chose that type. It is off unless you turn it on.
Light and dark mode
You can choose a light or dark look for the app, or match your device. We save that choice on your device, in a cookie or your browser's local storage, so the app looks right next time. It is used only to show the look you picked. It is not used to track you.
Payments
Payments on Cook to Counter are handled by payment companies, not by us. When you buy from a business, you pay that business through its own Stripe or Square account. The business is the seller.
- Stripe handles checkout and payments. Stripe also bills businesses for their Cook to Counter plan.
- Square handles payments for businesses that choose Square instead of Stripe.
- We do not store full card numbers. Card details go straight to the payment company (Stripe or Square). Stripe and Square process the card. We keep only limited details they send us: card brand, last four digits and expiry month and year, so we can show you which card you used and remind you before it expires. We may also keep a token or reference the payment company gives us so a saved method can be charged again without re-entering the card. If you pay with a digital wallet, we may keep the wallet type and a short display label. We do not store the wallet's full account number.
The payment companies have their own privacy policies:
- Stripe Privacy Policy: https://stripe.com/privacy
- Square Privacy Policy for buyers: https://squareup.com/us/en/legal/general/privacy-no-account
Ask Basil, our AI chat helper
Ask Basil, our AI chat helper, is planned, not built. Before it launches, we will update this policy to say what chats save, who can read them, how long we keep them and which AI provider we use.
Who we share data with
Service providers. We use companies that help us run Cook to Counter. They may use your data only to provide their service to us. They include:
- Website hosting: Namecheap.
- Email and text delivery: messaging companies that act as our service providers. The provider we use can change. Examples include Bird, Sent.dm, Pingram and Twilio. They may use numbers, addresses and messages only to deliver them for us.
- Payments and identity checks: Stripe and Square.
- Maps and address suggestions: Geoapify is the default. Google Places is an optional alternative that a business or we may turn on.
- Delivery: Uber Direct, for businesses that offer it. When a business books an Uber Direct delivery, Uber and the driver get the details needed to pick up and deliver the order: your name, phone number and delivery address (street, apartment or suite if you gave one, city, state and ZIP code); the pickup business name, pickup address and kitchen phone number; the order number; meal names and quantities; the order value used to book the delivery; the pickup and drop-off time window; any tip you added for the courier; and delivery status updates Uber sends back to us.
- Website analytics: Google Analytics, as described above.
- Sign-in: Google, if you choose Google sign-in or join our waitlist with Google.
- Browser notifications: the push service run by your browser maker (Google, Apple, Mozilla or Microsoft), if you turn notifications on. It gets the encrypted message and your push subscription address, and delivers the message to your device.
The businesses you buy from. When you order, the business gets your name, contact details and order details so it can make and hand off your food.
Other users, when you choose. Reviews, photos and seller profiles you publish can be seen by others.
For legal reasons. We may share data if we believe the law requires it, such as a court order or valid legal request. We may also share it to protect people's safety, to stop fraud, or to protect our rights.
If our business changes hands. If Foodie Guy L.L.C. or Cook to Counter is sold, merged or reorganized, your data may move to the new owner. The new owner must follow this policy for data collected under it. If the new owner will use that data in a materially different way, it will give you notice and a chance to close your account, as this policy describes for other big changes.
With your consent. We may share data in other ways if you ask us to or agree.
We do not sell your personal data. We do not share it for targeted advertising across other companies' sites and apps.
How long we keep data
We keep data only as long as we need it.
- Email log: 90 days, then deleted.
- Waitlist entries: until 12 months after launch, or until you leave the waitlist.
- Email and text consent and opt-out records: 5 years after the last message or opt-out.
- Push subscriptions: until you turn notifications off, or until the push service tells us the subscription no longer exists. Then we permanently delete it.
- Account data: while your account is open, and for 30 days after you close it.
- Order and payment records: 7 years, for tax and accounting.
- Seller verification records: plates mode is planned, not built. We will add this period before it launches.
- Server logs: usually up to 90 days, unless we need them longer to investigate abuse or follow the law.
- Google Analytics data: 14 months.
We may keep data longer if the law requires it, or to settle a dispute.
How we protect data
- Our site uses encrypted connections (HTTPS).
- Passwords for outside services and other secret keys are stored encrypted.
- Staff get access only to what they need for their job. Important actions are logged.
No system is perfectly secure. If a breach affects your personal data, we will tell you as the law requires.
Children
Cook to Counter is not meant for children under 13. We do not knowingly collect personal data from children under 13. If we learn that we have, we will delete it. If you think a child under 13 has given us data, email hello@cooktocounter.com.
You must be at least 18 to open an account, place an order or sell on Cook to Counter.
Your choices
- Marketing emails: click "unsubscribe" in any marketing email.
- Email tracking: click "Turn this off" in any tracked email.
- Texts: reply STOP to any text.
- Waitlist: unsubscribe, reply STOP, or email us to be removed.
- Analytics: turn on Global Privacy Control or Do Not Track in your browser and Google Analytics will not load on our sites. Or install Google's opt-out add-on: https://tools.google.com/dlpage/gaoptout
- Cookies: you can block or delete cookies in your browser. Some parts of the site, like signing in, will not work without them.
- Notifications: turn them off in the app's notification setting, or in your browser or device settings.
- Your account: you can see and update your details in your account. To close your account, go to your account page, choose to close your account and type CLOSE MY ACCOUNT to confirm. Or email hello@cooktocounter.com.
- Google sign-in and Google waitlist sign-up: you can remove Cook to Counter's access in your Google Account settings.
Privacy rights in some states
Some US states have privacy laws that give residents rights over their personal data. North Carolina, where we are based, does not have a law like this today.
Depending on where you live, and whether a state's law applies to us, you may have the right to:
- Know what personal data we have about you, and get a copy.
- Correct data that is wrong.
- Delete your data.
- Opt out of the sale of your data, targeted advertising, or certain kinds of profiling. We do not sell your data or use it for targeted advertising.
- Appeal if we turn down your request.
How to ask. Email hello@cooktocounter.com or write to us at the address above. Tell us what you want and which state you live in. We will check your identity before we act, usually by asking you to confirm details we already have. You may let someone else ask for you. We may ask them for proof that you agreed.
What to expect. We will respond within the time the law that applies to you requires. If we say no, we will tell you why and how to appeal. We will not treat you differently for using your rights.
Browser privacy signals. On our sites, a Global Privacy Control or Do Not Track signal stops Google Analytics from loading. We do not need these signals for anything else, because we do not sell your data or use it for targeted advertising.
Data a business holds. If your request is about data a business holds about you as its customer, contact that business. We will help the business respond.
Changes to this policy
We may update this policy. When we do, we will change the "Last updated" date at the top. If we make a big change, we will tell you before it takes effect, by email or a notice on the site.
Contact us
Questions or requests about privacy:
Foodie Guy L.L.C. (doing business as Cook to Counter)
1933 St Paul St
Charlotte, NC 28216
Email: hello@cooktocounter.com