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

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:

What this means for you:

Data we collect

Data you give us

What we collect depends on how you use Cook to Counter.

Business owners and staff:

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:

Anyone who contacts us:

How you sign in

You can sign in three ways:

Data we collect when you visit

Data we get from others

How we use data

We use data to:

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.

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.

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.

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:

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:

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.

Email

We send two kinds of email:

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.

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.

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:

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

Text messages

We and the businesses on Cook to Counter may send texts.

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:

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.

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.

The payment companies have their own privacy policies:

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:

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.

We may keep data longer if the law requires it, or to settle a dispute.

How we protect data

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

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:

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