Legal · last updated

Privacy policy

What we collect, why, who processes it, how long we keep it and how to use your rights — in plain language.

1. Who we are

GetBakeryPOS (“we”, “us”) provides hosted point-of-sale software for bakeries and runs this website, getbakerypos.com. The legal entity and registered address responsible for your data will be published here at launch; until then, contact us through the details at the end of this page.

This policy covers two kinds of data: data about visitors to this website, and data that merchants (bakeries) store in the GetBakeryPOS software.

2. What we collect from website visitors

  • Forms: name, email, phone/WhatsApp, bakery name, country, topic and your message, plus the page you were on and campaign parameters (utm tags) if you arrived from an ad or link.
  • Preferences stored in your browser (theme, accent colour, text size, country, cookie choice, recent searches). These never leave your device.
  • Analytics, only if you accept: pages viewed, device type and approximate location, through Google Analytics 4 with IP anonymisation.
  • Security: Cloudflare Turnstile checks that forms are sent by people, which processes technical signals from your browser.

3. How we use it

  • To reply to you, book demos and set up your account.
  • To understand which pages help bakers (analytics, only with consent).
  • To keep forms free of spam.
  • We do not sell personal data, and we do not use it for third-party advertising.

4. Who processes it for us

Form submissions go to our CRM (GoHighLevel) and a notification goes to our team’s chat (Discord). The website is hosted on Cloudflare. Analytics, if accepted, is provided by Google. Each processes data on our instructions.

5. Data merchants store in GetBakeryPOS

Bakeries using the software store their products, sales, staff accounts and customer details (such as names and phone numbers for pre-orders). The bakery is responsible for that customer data; we process it on the bakery’s behalf to provide the service, keep it secure and back it up. We do not use merchants’ customer data for our own marketing.

Card numbers are not stored in GetBakeryPOS: card payments run on the merchant’s own processor terminal.

6. How long we keep data

  • Enquiries: up to 24 months after our last contact, then deleted unless you became a customer.
  • Merchant accounts: while the account is active; after cancellation, 30 days to allow export, then deleted (except records we must keep by law, such as invoices).
  • Analytics: according to the retention set in Google Analytics (14 months).

7. Your rights

Depending on where you live, you can ask to access, correct, delete or export your data, and to object to or restrict its use.

  • California (CCPA/CPRA): you can request to know, delete and correct personal information, and you will not be discriminated against for using these rights. We do not sell or share personal information for cross-context behavioural advertising.
  • UAE (Federal Decree-Law No. 45 of 2021): you can request access, correction, deletion and restriction of processing.
  • Pakistan: we apply the same rights to visitors in Pakistan.

Use the data request page. We answer within the time your local law requires (generally within 30–45 days).

8. Cookies and browser storage

See the cookie policy for the full list. Analytics cookies are only set after you accept them.

9. Security

The site and software use HTTPS. Access to systems is limited to staff who need it. See security & data.

10. Children

This website and the software are for businesses and are not directed at children under 16.

11. International transfers

Our providers may process data in the United States, the European Union or other countries. Where required, we rely on the safeguards those providers offer.

12. Changes to this policy

We will update the date at the top when this policy changes and highlight material changes on this page.

Contact

Questions about this page: or use the contact form.

Questions about how this applies to your bakery? Ask us — or start with the setup overview.