Privacy Policy
Last updated: 27 September 2026
Pixelik Ltd ("Pixelik", "we", "us") is the data controller for pixelik.com and booking.pixelik.com. This page says, in plain terms, what personal data we collect on pixelik.com and booking.pixelik.com, why, who processes it for us, how long we keep it, and how to have it corrected or deleted. It is written from the code that runs those pages, and it changes when the code does.
1. Who is responsible
The data controller is Pixelik Ltd, a company registered in England and Wales (Company No. 17057272), with registered office at First Floor Office, 3 Hornton Place, London, W8 4LZ, United Kingdom. Contact:
2. What we collect, and where
Reading pixelik.com collects nothing about you personally. Traffic statistics are aggregate and cookieless (section 6).
Talking to the Discovery Agent (booking.pixelik.com/intake, also inside the drawer on pixelik.com). The agent asks for your work email, your company and role, and then about the workflow you want to improve: how it runs today, the volume, the systems involved, whether it touches sensitive data, how you would measure success, your timeline and who decides. It never asks for a budget; if you volunteer one, it is recorded. While you chat, the conversation lives in your own browser. Your email is saved to our systems the moment you share it. When the brief is generated, the full conversation and the brief are stored in our systems, together with your email, company, role, IP address and browser details. The agent never asks for a person's name.
Booking a Workflow Audit directly (booking.pixelik.com/book): your name, work email, company (optional) and what you would like to discuss, plus IP address and browser details. Your name, company and reason also appear in the calendar event we create.
Scheduling: the time preference you type and your browser's time zone are read by the model to find a slot; they are not stored.
Writing to us by email: whatever you send, kept in our mailbox.
3. Why, and on what legal basis
- To do what you asked for: answer the agent's questions, produce your brief, book the call, send the invite, and prepare for the conversation (steps taken at your request before a contract).
- Our legitimate interests: following up an enquiry you started, keeping the service secure (IP-based rate limiting, bot checks, abuse prevention), and understanding aggregate traffic.
- Legal obligation: accounting and company records where the law requires them.
AI training: we do not use your data to train any model, and our model provider does not use data sent through its API to train its models (section 4).
4. Who processes it for us
We run the agent and the booking system ourselves. These providers process data on our instructions:
| Provider | What it does with your data | Where, and terms that matter |
|---|---|---|
| Anthropic | Runs the Claude model behind the Discovery Agent. Receives the conversation to answer it, to write the brief, and to read a time preference. | United States. Under its commercial terms it does not use API inputs or outputs to train its models, and deletes them from its systems within 30 days. |
| Supabase | Hosts our database: lead records, conversations and briefs. | Managed PostgreSQL in the EU, Ireland region (eu-west-1). Access is by our server only; the public key has no rights to any table. |
| Google Cloud | Runs the small service that checks our calendar and creates your Workflow Audit event with a Google Meet link, and sends you the invite. | London region (europe-west2) for the service; Google Calendar and Meet for the event and the invite. |
| Vercel | Hosts pixelik.com and booking.pixelik.com, keeps server logs for one day, and provides cookieless, aggregate traffic statistics. | Global edge network; the server functions that handle the agent and bookings run in Vercel’s United States East region. |
| Upstash | Rate limiting, so one visitor cannot flood the agent. Counters are keyed by IP address and expire after 60 seconds. | Managed Redis. |
| Cloudflare | Turnstile, the bot check before a brief is generated or a call is booked. | May set a strictly necessary cookie for the duration of the check. |
Where your data is: stored in the EU (Ireland). Processed, while a request is handled, in the United States by our hosting provider's server functions and by our model provider. For those transfers outside the United Kingdom and the EEA we rely on the UK International Data Transfer Agreement or Addendum, or on Standard Contractual Clauses, in the providers' terms. Where a client engagement requires EU or UK residency for its own data, we build the client's system in the client's cloud and region and agree a data processing agreement; that is described on the enterprise page and is separate from this website.
5. How long we keep it
| Data | Kept for | Why |
|---|---|---|
| Your Discovery Agent conversation and the brief it produces | 12 months from your last activity, then deleted automatically | Kept only while an enquiry could still turn into an engagement; if one does, the brief is kept under that engagement’s contract instead. |
| Your lead record (email, company, role, booking status) | 24 months from our last contact with you, then deleted automatically | Enterprise buying cycles are long; after two years of silence the enquiry is closed. |
| Your name, company and reason from a direct booking | Same as the lead record | Stored on the lead record and in the calendar event. |
| IP address and browser details recorded with a brief or a booking | Deleted with the record they belong to | Recorded for security and abuse prevention only. |
| The calendar event and Google Meet link for your Workflow Audit | Kept in our calendar like any meeting; deleted on request | The invite in your inbox is yours. |
| Server logs | One day (our hosting plan’s default) | Since 27 September 2026 our code writes no email addresses, names or conversation content to logs. |
| Rate-limiting counters keyed by IP address | 60 seconds | Sliding windows; nothing else is derived from them. |
| Your conversation in your own browser (local storage) | Until the brief is generated or 24 hours, whichever comes first | On your device only; we cannot read it. |
| If you become a client | The engagement contract, then accounting records for six years as UK law requires | Client records live in our operating systems under the engagement’s terms and any DPA. |
Deletion after these periods runs automatically, daily, in our database. You do not have to ask for it, and you can ask for it sooner (section 8).
6. Cookies, local storage and analytics
We set no advertising or analytics cookies and use no cross-site tracking on pixelik.com or booking.pixelik.com, which is why there is no cookie banner.
- Bot check: Cloudflare Turnstile may set a strictly necessary cookie while it verifies your browser. It is exempt from consent requirements.
- Local storage: the Discovery Agent keeps your conversation in your browser's local storage while you chat, so you can leave and resume. It is cleared when your brief is generated, or after 24 hours. Once the brief exists, the conversation is also stored in our systems, as described in section 2.
- Traffic measurement: Vercel Web Analytics, a cookieless service that records aggregate statistics only (page views, referrers, country, device type). It sets no cookies and stores no personal identifiers.
7. Security
Data is encrypted in transit and at rest by the providers above. Access to our database is limited to our server and to the founder. The agent runs behind rate limiting and a bot check, and refuses personal data beyond business contact details. If we ever suffer a breach affecting your data, we will tell you and the Information Commissioner's Office as the law requires.
8. Your rights, and how to use them
You can ask for access to the personal data we hold about you, for its correction or deletion, for processing to be restricted, to object to processing based on our legitimate interests, and for a portable copy of data you gave us. Write to from the email address you used with us; that is how we confirm it is you. We reply within one month. A deletion request removes your lead record, your conversations and briefs, and your calendar events on our side. You can also complain to the Information Commissioner's Office at ico.org.uk.
9. Changes
When we change this policy, the date at the top changes and the new version is published here. Where a change materially affects data we already hold about you, we will tell you by email.