Privacy Policy

Carte is made and run by Brainy Circles OÜ, registry code 17226352, VAT EE102854879, Sepapaja tn 6, 15551 Tallinn, Estonia (“Brainy”, “we”). Write to us about anything here at hi@brainy.ink.

This policy covers eat.brainy.ink (the website, the live demo, the start and payment pages, Ask Boon) and the ordering apps we host for restaurants (their menus, carts, order pages, table bookings, kitchen screens and staff apps).

For the website, the requests restaurants send us and their payments, we decide what is collected and why: we are the controller.

In a restaurant’s own app, the restaurant decides what it does with its guests’ orders, bookings and notes: the restaurant is the controller and we process that data for it, only on its instructions (see our Terms, Data processing). Guests with a question about their data should ask the restaurant first; we help it answer.

• Analytics, only if you accept. If you choose Accept on our cookie notice, PostHog records which pages you open, what you tap and where you came from (the link’s utm tags and the referring site), with a random id kept in a cookie and in your browser’s storage. If you decline, PostHog is not loaded at all.
• Which version of a page you see. When we test two versions of a page, a cookie keeps you on the same one. It lasts for your visit, or 90 days if you accepted analytics. We count how many visitors each version gets and how many of them go on to make an app or ask for one, with nothing that says who you are.
• How long a visit lasts, only if you accept. If you accepted analytics, the pages of a test send our own server how long they were on screen, with a random id for that visit only, so we can compare the versions.
• Your choice itself is kept in your browser’s storage, so we do not ask again.
• The live demo keeps your demo orders in your browser’s storage so the demo kitchen can show them, and fills in a sample name and number: you never need to type your own. Demo orders are closed by themselves after two hours.
• Ask Boon answers from a fixed set of answers on the page. If you send a question to our team, we keep the question, the page you asked from and the email or WhatsApp number you give, to reply.

• Your request: the plan and options you choose, your restaurant’s name, city and country, its website or Instagram if you add it, your name, email and WhatsApp number, and where you came from (the link’s utm tags, the referring site, the page you started on, the version of the page, and the analytics id if you accepted analytics).
• Restaurant Pro calls: also the number of branches, size, orders a day, how you deliver, which delivery apps you use, a good time to call, your note and your time zone.
• Payments are taken by Stripe. Your card details go to Stripe and never reach us. We keep what Stripe tells us: your Stripe customer and subscription ids, what was paid and when, the receipt link, renewals, failed payments and refunds. Stripe’s own privacy policy applies to what it collects on its page.
• What you send us to build your app: photos or files of your menu, your logo, food photos and your note.
• Messages we exchange with you by email or WhatsApp.

We use this to answer you, take payment, build and run your app, support you, keep our accounts, and see which of our posts and pages bring restaurants to us.

• An order: the name and phone number you give, your table, pickup or delivery address, what you ordered, your note and the order’s status. Your app remembers your name and number on your phone for your next order.
• A table booking: your name, phone number, the number of guests, the day and time, and your note.
• The restaurant’s own notes about regular guests (for example a birthday or an allergy), if its staff add them.
• Alerts: if you allow it, your browser’s push service carries a note when your order is ready.
• Your cart and language stay in your browser’s storage.

Guests pay the restaurant directly; the apps do not take card payments from guests.

For each team member: a name, a role, a PIN (we keep only a scrambled form of it, never the PIN itself), clock-in and clock-out times, and a record of changes made in the staff app (who changed a price, marked a dish sold out, moved an order), so the owner can see what happened.

• A contract with you, or steps you asked for before one: your request, your payment, building and running your app.
• Our legitimate interests: keeping the service safe and working, stopping abuse, learning which posts and pages bring restaurants to us, and replying to questions.
• Your consent: analytics cookies, and push alerts in your browser. You can withdraw it at any time.
• The law: keeping accounting records.

• Vercel (USA): hosts the website and the apps.
• Convex (USA): our database and file storage.
• Stripe (Ireland and USA): payments and receipts.
• PostHog (USA): analytics, only with your consent.
• Apple, Google and Mozilla push services: carry alerts you allowed in your browser.
• Meta (WhatsApp) and our email provider: when we message you.

Where data leaves the European Economic Area, it is protected by the European Commission’s standard contractual clauses or the EU-US Data Privacy Framework, as each provider offers. We do not sell personal data, and we do not use it for advertising profiles.

• Requests that never become a customer: up to 24 months, then deleted.
• Customers: for as long as your plan runs, then up to 12 months to close things properly. Payment and invoice records for 7 years, as accounting law requires.
• Files you send us to build your app: while your app is being built and runs; deleted within 90 days after your plan ends.
• Guests’ orders and bookings: as long as the restaurant keeps its app with us, unless it deletes them sooner; removed within 90 days after it leaves.
• Questions to our team: up to 12 months.
• Analytics: up to 12 months.

You can ask us to show you, correct, delete or hand over your data, to limit or stop how we use it, and to withdraw a consent you gave. Write to hi@brainy.ink; we answer within a month. For a restaurant’s app, we pass your request to the restaurant and help it answer.

You can also complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee) or the authority where you live.

Everything travels encrypted. Staff screens need each person’s own PIN; the team’s tools need a key. Payment pages are Stripe’s. Each request’s payment and upload pages open only with its own unguessable link. Only the people at Brainy who build and support your app can see its data.

Carte is for restaurants and their guests. We do not knowingly collect data from children under 16 for our own purposes.

When we change this policy we update the date above, and tell customers by email if the change matters to them.