Privacy Policy
Draft for attorney review. This page describes how the product works. It is not legal advice.
Effective and last updated: October 7, 2026
We collect what we need to build your store and run orders. We don’t sell personal information, we don’t share it for targeted advertising, and we never share phone numbers or text-message consent with anyone for their marketing.
1. Who we are and what this covers
Grant Corporation (“KitchenCheckout,” “we”) runs kitchencheckout.com and hosts online ordering stores for independent food businesses (“cooks”). KitchenCheckout is a JustBuildNGo product; JustBuildNGo is a Grant Corporation web agency. This policy covers our website, the stores we host (yourname.kitchencheckout.com and custom domains), the cook portal and owner dashboard, and our texts and emails.
When you order from a cook’s store, the cook is the business you’re buying from. We host the store and process your order information for that cook. The cook may also have its own privacy practices for how it uses your information.
2. Information we collect
From cooks (our customers)
- Account and business details: name, email, phone, kitchen name, city, social media handles, hours, and how you take payments today.
- Build material you send: menus, food photos, logos and notes.
- Billing: handled by Stripe. We keep your Stripe customer and subscription IDs, plan and payment status — never your full card number.
- Payouts: your Stripe account ID and whether it can accept payments. Your bank details stay with Stripe.
- Your consent to automatic renewal (the time, and the terms you agreed to) and to our Terms.
- If you get your own domain: the registrant name and contact details, which domain rules require us to send to the registrar and registry. We turn on the registrar’s free privacy protection where it’s offered, so they aren’t shown publicly.
- Support requests and messages you send us, including information you choose to share with Mike, our AI chat assistant.
From people who order from a cook’s store
- Name, phone number, and (optionally) email.
- Delivery address, event date and order notes when you provide them.
- What you ordered, prices, discounts, tax, and whether you paid by card or at pickup.
- Card payments are entered on Stripe’s secure checkout page. We never see or store card numbers.
From everyone who visits
- Device and usage information: IP address, browser type, pages viewed and referring site, collected by our servers, by Cloudflare (which protects and speeds up our sites) and by Google Analytics.
- Cookies and similar storage: a login cookie (only if you sign in), your cart and signup progress saved in your own browser, and Google Analytics cookies that measure how the site is used. The same points are restated on the cookies page.
3. How we use it
- To build, host and run stores, take orders, and send order information to the cook.
- To send order updates (email, and texts on Store Plus stores) and account, build, billing and security messages.
- To bill subscriptions, prevent fraud and abuse, keep the service secure, and meet legal obligations.
- To understand how the site is used and improve it.
- To provide support, answer chat questions, qualify prospective cooks and prefill a signup draft for your review.
4. Who we share it with
- The cook you order from gets your order details and contact information so they can make and hand off your food.
- Service providers that work for us under contract: Stripe (payments and payouts), Twilio (text messages), our own mail server (email), Anthropic (processing Mike AI chat messages), Google Analytics (site statistics), Cloudflare (security and delivery), and Namecheap (domain registration). Our servers are in the United States.
- Legal reasons: when required by law, or to protect people, our users or our rights.
- Business transfers: if KitchenCheckout is sold or merged, under this policy’s protections.
Mike is an AI assistant, not a human. Chat messages and limited account or signup context are sent to Anthropic to generate replies. A chat does not complete payment, consent, or account changes. We keep aggregate token and cost records, not complete chat transcripts; if you submit a support ticket, we retain the message in the support thread. Do not enter card numbers, passwords or sensitive customer information in chat.
We do not sell personal information and do not share it for cross-context behavioral (targeted) advertising. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text-messaging opt-in data and consent are not shared with anyone. We don’t share personal information with third parties for their own direct marketing (California “Shine the Light”).
5. Text messages
If you give a phone number when ordering, you may get texts about that order from the cook’s store (about 1–3 per order). Message and data rates may apply. Reply STOP to opt out or HELP for help. See the text message terms.
6. Do Not Track and tracking by others
Our sites don’t change their behavior in response to browser “Do Not Track” signals. Google Analytics may collect information about your online activity over time and across different websites. You can block it with your browser’s cookie settings or the Google Analytics opt-out add-on. We don’t allow other companies to track visitors on our sites for advertising.
7. How long we keep it
- Cook account and store data: while the plan is active, then for 6 months while the store is dormant so it can be reactivated; then deleted.
- Photos selected during signup upload privately before Stripe checkout. If signup is not completed, the staged photos are removed from live storage after 7 days; encrypted backups can retain them for up to 90 days. If signup is paid, the photos become private build material in the cook’s account.
- Order and customer records: while the cook’s store is active or dormant (cooks need them for taxes and customer service), then deleted with the store.
- Automatic-renewal consent records: at least 3 years, or 1 year after the subscription ends, whichever is longer, as California law requires.
- Billing and tax records: as long as tax law requires (generally up to 7 years).
- Server and security logs: kept briefly for security, then deleted.
8. Security
We use encryption in transit (HTTPS), restricted access to production systems, locked-down file permissions, rate limits and monitoring. Uploaded photos and menus are private until they’re published on your store. No system is perfectly secure; if a breach affects your personal information, we’ll notify you as the law requires.
9. Your choices and rights
- Cooks can view and update most information in the portal and dashboard.
- Anyone can ask us to access, correct or delete their personal information by emailing [email protected]. We’ll verify the request and answer within 45 days. We won’t treat you differently for asking.
- If you ordered from a cook’s store, you can also contact that cook directly; we’ll help them handle your request.
- California residents: KitchenCheckout is currently below the size thresholds of the California Consumer Privacy Act, but we honor the same access, deletion and correction requests for everyone.
10. Children
Our service is for adults running food businesses and their customers. We don’t knowingly collect personal information from children under 13. If you believe a child gave us information, contact us and we’ll delete it.
11. Changes to this policy
We’ll post changes here and update the date at the top. If a change is material, we’ll email cooks before it takes effect.
12. Contact
KitchenCheckout is a JustBuildNGo product. JustBuildNGo is a Grant Corporation web agency. Grant Corporation · 1012 East Ave J Suite 16, Lancaster, CA 93535 · [email protected] · (661) 441-3970