Privacy

Last updated 4 November 2026

Blinx makes one-page websites for small businesses. This page says what information passes through us when you use one, in plain English, because the people who read privacy policies deserve better than fog. Blinx is operated by Brownbook Limited, registered in England and Wales (company number 06572956, registered office 80 East Street, Brighton, BN1 1NF). Questions, or anything you want corrected or removed: use our support form.

If you visit a business page

We record that the page was viewed and what was tapped: call, WhatsApp, directions, book. That record carries a random visitor number, the rough source of the visit, and no name. It exists so the business owner can see their page working. We do not know who you are unless you tell us.

If you send an enquiry or book an appointment, the name and contact details you type go to that business, and we hold a copy so their diary and inbox work. That information is theirs to act on: we never sell it, share it, or use it to contact you about anything else. Booking confirmations reach you by text or email, and that is the only time we message you. If you send an enquiry or book, the business also sees what you did on its page during that visit, such as viewing it or tapping Call, next to your message.

If you visit blinx.biz itself

We note that you arrived and which site sent you, with the same random visitor number. If you play our tour video, we note that too, with your account if you are signed in. The video comes from our own server.

If you run a business on Blinx

We hold what you give us: your email, your name if you signed in with Google, your business details, your photos and your page content. We note how you use Blinx, such as when you sign in, edit your page or look at plans, and whether our emails are opened or their buttons tapped. We use that to choose which email, if any, is useful to you next, so we never pester anyone twice. A button in our emails signs you straight in, so please do not forward them. Replies to our emails reach our support team. If you unsubscribe, our emails to you stop, all of them, permanently, except ones you ask for (such as a sign-in link), answers to messages you send us, and notices about your own page that you need in order to keep it.

If we have written to your business

Sometimes we write to a business about a Blinx page that is waiting for it, by email and sometimes by text. We hold the business's name, its contact details, including the email address we write to, and the page itself. Reply STOP to a text, or use the link in the email, and we stop writing. A page nobody claims is normally removed once the time to claim it has passed, and it can be removed sooner, for example if its email address cannot reliably receive mail. A page we made for a business that has not claimed it also comes down if the business replies to our email asking us to stop, uses the unsubscribe link in it, or replies STOP to our text. Depending on the page, a removed page is deleted straight away, or kept privately for up to 90 days in case its business gets in touch, and then deleted.

Where information goes, and where it does not

No advertising trackers. No analytics companies. Our own database does that work, on a server we rent from Hetzner in Germany. A few specialists handle the jobs we should not build ourselves:

• Stripe takes payments. Your card number goes to Stripe directly and never touches our servers; we could not store it if we wanted to, and we do not want to.
• Clerk runs owner sign-in, including Continue with Google. It holds your email address, your password if you set one, which it keeps in a form nobody can read, and your name if you gave it. Its sign-in code loads on every Blinx page, so your browser talks to Clerk when you open one.
• Twilio sends texts: booking confirmations, the code that proves a page is yours, and a short note to businesses we write to. It sees the number and the text, and tells us if someone replies STOP.
• Email is sent from our own mail system and delivered by Amazon's email service (Amazon SES). Emails about pages waiting to be claimed, and our notes to businesses we write to, go through Resend. A reply to a booking confirmation, and other mail to our own blinx.biz address, is received for us by Mailgun. Each sees the address and the message. Before some emails about a page, Bouncer checks that the address can receive mail; it is given the address and nothing else. Opens and clicks are measured by us, never by a tracking company.
• Google appears four ways: sign in with Google if you choose it, through Clerk (we receive your email and name, nothing more); business listings, photos, ratings and reviews, which we fetch about businesses, with reviews shown as Google provides them, including each reviewer's name, picture and a link to their Google profile; the map on a business page; and our team's own mailboxes, which Google hosts for us. The map and reviewers' pictures load from Google, so on a page that shows them your browser talks to Google as it would on any site with them. A message to our support team, through the support form, from the app, or as a reply to our emails to owners and to businesses we write to, is also copied to those mailboxes, with our answer; a help chat conversation is not.
• Cloudflare stores the photos and videos owners upload in a private bucket, and holds our nightly database backup, which is encrypted before it leaves our server. It also runs a quick check on our support form and claim screen to keep bots out, which reads signals from your browser.
• Anthropic powers the help chat on our website and in the app, so it receives what you type there and, if you are signed in, your business's name, its web address and your plan; we keep a copy of each conversation. It also rewrites an owner's own words when they ask, helps match a trade to a category, and helps us read our own error reports. It is not given the enquiries or bookings your visitors send.
• Notifications: if an owner turns them on, a short alert, such as a customer's name, reaches their phone through the phone or browser maker's own notification service, sealed so that service cannot read it.

Several of these companies are based in the United States, so some information is handled there.

Videos from YouTube, TikTok or Instagram load only when you press play. Playing a YouTube video uses YouTube's reduced-tracking player; playing a TikTok or Instagram video connects you to those platforms as visiting them would.

Cookies

All are there for the site to work, none for advertising: a random visitor number that ends when you close your browser, so an owner's page statistics work; sign-in cookies, from us and from Clerk, so owners stay signed in; and two short-lived ones while you finish a payment or follow a button in our emails. A map, or a video you choose to play, may set its provider's own cookies.

How long we keep things

Business content and customer enquiries stay while the account stays, so the owner's history keeps working. Deleting a Blinx account is real deletion: the page, its photos and videos, its statistics, its enquiries and bookings, and the account itself are removed at once, not hidden. A few small records outlive it, none of them a copy of the page: a note that a page was deleted, with its web address and nothing about you; records of payments, which tax law asks us to keep, and Stripe's own record of them; your sign-in, if you had it before your Blinx account; if we wrote to your business before you joined, a scrambled marker so we never write to it again; and, in the team's mailboxes, the copies of your messages to our support team and of our own emails to the team that name you. A chat or support message is kept for two years from its last message, or until the account it belongs to is deleted, if that comes first. The copies that reach our team's mailboxes are kept there until our team deletes them. Backups are deleted after 30 days, and are restored only if disaster demands it.

Your rights

UK law gives you the right to see what we hold about you, correct it, take a copy, or have it deleted. Use our support form and a person answers. A page itself is removed by its owner in Settings or, if they cannot sign in, only once that is confirmed from the email address tied to the page, because we cannot know who is writing. A page we made for a business that has not claimed it also comes down if the business replies to our email asking us to stop, uses the unsubscribe link in it, or replies STOP to our text. If a Google review of yours still shows on a Blinx page after you changed or removed it on Google, tell us through the same form and we will bring the page up to date. If you are a customer of a business that uses Blinx, we will also point the business itself at your request, because the information is theirs to honour too.