This agreement is between Blinki Limited ("Blinki", "we") and you, the customer or partner whose account the data sits under ("you"). It forms part of our terms and applies from the moment you have an account. You do not need to sign anything: using the platform for a business means these terms apply, and you can quote this page to anybody who asks what your website host does with their customers' data. It is written to meet Article 28 of the UK GDPR and the equivalent in the EU GDPR.
The short version. Your customers' details are yours. We hold them to run your website, inbox and phone number, we do nothing else with them, we keep them in the UK and EU with a short list of suppliers we name below, we delete them when you tell us to or when you leave, and we tell you straight away if anything goes wrong.
Who this covers
Every Blinki account: a business running its own website, a partner running the platform under their own name, and the partner's own clients. Where a partner's client has an account with the partner rather than with us, the partner is our customer under this agreement and is responsible for passing its terms on to their client.
Who decides what
For the personal data that passes through your website, inbox and phone number ("customer data") you decide why it is collected and what happens to it. You are the controller, and Blinki is your processor: we handle it only to provide the service, and only on your instructions. Your instructions are the settings you choose, the things you do in the dashboard and through the connector, and this agreement.
For the details of your own account with us (your name, email, billing, support messages) and for people visiting blinki.co.uk itself, Blinki is the controller. That part is covered by our privacy notice, not this page.
What we process, and why
- Enquiries. What somebody types into a contact form on your website: typically a name, an email address, a phone number and a message. Stored so you can read and answer them, counted so your dashboard can say how many came in, and emailed to you if you have asked for that.
- Visitor statistics. Page views, time on page, taps on your phone number, email address and map link, and a daily count of distinct visitors. A visitor is told apart by a one-way hash of their internet address and browser made with a secret we hold; the address itself is never stored. Nothing is placed in the visitor's browser beyond two session-only markers that vanish when the tab closes, and no third party is involved.
- Shop orders, where you sell through your website: the buyer's name, address, email, what they bought and what they paid. Card details go straight to your payment provider (Stripe or Square) and never touch us.
- Mailbox contents, where you have a mailbox with us: the mail itself, held on the mail platform we use (below) and read by nobody at Blinki unless you ask us to help with a specific problem.
- Calls and voicemail, where you have a phone number with us: the numbers that called, when, for how long, and any voicemail left, held so you can see and hear them.
- Your website content, including anything personal you have chosen to put on it, such as staff names and photographs.
We do not use customer data to build profiles, to sell to, to train anything, or for any purpose of our own. Aggregated figures that identify nobody (how many enquiries the platform handled this month) are ours to use for running the service.
What we commit to
- To process customer data only on your instructions and for the purposes above, and to tell you if we believe an instruction would break data protection law.
- To make sure everybody at Blinki who can see customer data is bound to keep it confidential.
- To keep it secure in the ways set out below.
- To use only the suppliers named below, under written terms that hold them to the same standard, and to tell you before adding one so you can object.
- To help you answer requests from the people whose data it is (access, correction, deletion and the rest). Most of these you can do yourself from the dashboard; where you cannot, we will do it for you within ten working days of being asked.
- To help you with any security assessment, impact assessment or question from the Information Commissioner that concerns the data we hold for you.
- To delete or return customer data when this agreement ends, as set out below.
- To let you see what we hold for you and how it is kept. The dashboard is the first place for that; ask us for anything it does not show.
Who else touches it
These are the companies whose systems customer data passes through. Each one is under a written data processing agreement with us, and each is used only for the job named.
- Google Cloud (Firebase): our database, our application code and our file storage, in Google's London region. Also the hosting and edge network for the published pages of websites on blinki.co.uk addresses and staging addresses.
- Vercel: hosting and edge network for published websites on their own domains. Published pages are public pages, cached at the edge worldwide; customer data is not held there.
- Stripe: payments to us and, where you take card payments through your website with Stripe, payments to you. Stripe is a controller in its own right for card data.
- Square: where you take card payments through your website with Square. Same position as Stripe.
- Resend: sends the emails the platform sends on your behalf (an enquiry forwarded to you, a receipt to your buyer).
- Mailcheap: runs the mailboxes you buy from us. Mail is held on their servers in the EU.
- Namecheap: registers the domains you buy from us. The registrant details you give us are passed to them, and to Nominet for .uk names, because the registry requires them.
- Telnyx: provides the phone numbers you buy from us, carries the calls and stores voicemail.
Where one of these moves data outside the UK or EU (Stripe, Square and Telnyx operate globally), the transfer is covered by the UK International Data Transfer Agreement or the EU Standard Contractual Clauses, as applicable, in our contract with them.
Where it lives
Our database, application code and file storage run in Google Cloud's London region (europe-west2). Mailboxes are in the EU. Published website pages, which are public by design, are cached on Google's and Vercel's edge networks around the world so they load quickly wherever your visitors are.
How long we keep it
- Enquiries and shop orders: until you delete them from the dashboard, or 30 days after your account closes, whichever is first.
- Visitor markers (the daily hashes): deleted within a few days of the day they were made. The daily totals built from them hold no personal data and are kept so your statistics still work.
- Mailbox contents: until you delete the mail, or 30 days after the mailbox is closed.
- Call records and voicemail: until you delete them, or 30 days after the number is given up. Deleting a voicemail deletes the recording itself, not just the entry.
- Website content: until you change or delete it, or 30 days after your account closes.
- Request logs on our servers (which pages were asked for, from which address, when): 30 days, which is Google Cloud's standard log retention.
- Backups: website content is backed up nightly so a site can be put back if something goes wrong. Backups cover content only, never enquiries, orders, mail or calls, and are deleted with the account.
When your account closes, you have 30 days to ask for a copy of anything you want (we provide it as files on request), after which it is deleted.
How we keep it safe
- Everything travels over HTTPS; every published website gets its own certificate.
- Data at rest is encrypted by the platforms it sits on (Google Cloud, Mailcheap, Telnyx).
- Access to the database and the application is limited to the people who run Blinki, each with their own sign-in and a second sign-in step, and every change to the application is recorded.
- Your dashboard offers two-step sign-in under Security and we recommend it. Members of your team see only the businesses you have added them to.
- Contact forms carry protection against automated posting, so what reaches your enquiries is what a person sent.
- We keep our application dependencies current and take security reports at security@blinki.co.uk.
If something goes wrong
If we become aware that customer data has been lost, exposed or accessed by somebody it should not have been, we will tell you without undue delay and within 48 hours of knowing, with what happened, what data was involved, what we have done about it and what we suggest you do. We will keep you informed as we learn more, and we will help you with anything you need to tell the people affected or the Information Commissioner.
Your side, and ending it
You confirm that you have the right to collect the customer data you put through the platform and that you have told the people it concerns what you do with it, which usually means a privacy notice and, where you use cookies or similar technology, a way for visitors to choose. Our visit counter can be held back until a visitor agrees; see our cookies page for how.
This agreement lasts as long as you have an account. It ends when the account closes, and our obligations to delete or return the data survive it. Where this page and our terms disagree about personal data, this page wins.
Changes
We will update this page when our practices or suppliers change, bump the version at the top and email active customers about anything material, at least 14 days before it takes effect where that is possible. If you object to a new supplier you can close your account before the change applies and we will delete your data as above.
Anything about this agreement, or a request under it: privacy@blinki.co.uk. Blinki Limited is registered in England and Wales.