Privacy Policy

Last updated: 14 August 2026

Pixy is operated by Surfy Ltd, a company registered in England and Wales (company number 15026168), registered office at 14-2e Docklands Business Centre, 10-16 Tiller Road, London, E14 8PX, United Kingdom. When this policy says we, it means Surfy Ltd.

Pixy is built to hold as little of your data as possible, the architecture makes that easy, because your own page does the work and our side is only a relay. This page lists everything we do hold.

What we collect

Your email address. It is your account. You sign in with a one-time code sent to it, there are no passwords. We use it for sign-in codes, for billing messages if you are on a paid plan, and for rare service notices, never for marketing lists.

Your projects and credentials. A name per project, the public key that goes in your script tag, and the credentials that grant access: an editor token per browser and site, an extension token per browser, and the agent secret your coding agent uses. We keep the time each was last used, because you cannot safely revoke what you cannot see.

Edit records. What you change in design mode: the page URL, a CSS selector, a short text sample of the target element, and the property with its old and new values at a given viewport width. Where you add or rewrite content, the record carries that markup and text, it has to, because that is the change. Comments and notes you leave ride along in the same record.

Session messages. In a live session, the messages between you and your coding agent pass through the relay and are stored with the task they belong to.

Images you drop in. Stored per project, re-encoded, and never served publicly.

An activity log. Which credential pulled or acknowledged what, and when, the audit trail behind your project.

Billing. If you subscribe: your Stripe customer reference, the state of your plan, and a record of each payment and refund. Card details never reach our servers, see Payments below.

When you visit pixydesignapp.com. A visitor identifier in your browser's local storage, the country and city your address belongs to, your browser's user-agent, the page you arrived on and the site that referred you, and your screen size. Your IP address itself is not stored: it is resolved to a place against a database on our own server and then dropped.

When you write to us. Your message, your email address, the same approximate place, and the page it came from.

Roadmap posts and votes. Tied to your visitor identifier, and to your account when you are signed in. Guests get a generated nickname; we never ask for a real name, anywhere.

What we never touch

We do not capture, copy, screenshot or store your pages. The editor runs in your browser, on your live site, and only the record of what you changed leaves it. Pages behind a login, on localhost, or on a staging box are never reachable by us, because nothing on our side goes and fetches them.

We use no cookies at all, no third-party analytics, no ad trackers, no tracking pixels. Nothing on our site is loaded from someone else's server, fonts, styles and scripts are all our own.

Your coding agent

The agent that receives your edits runs on your own machine, under your own account with whichever provider you use. Pixy is the relay between the two: we send your content to no AI provider, and we run no models of our own.

An agent authenticates with a project secret and can reach only that project, its records, its conversation, its images. It cannot reach your account, your other projects, or your billing.

The browser extension

The extension holds one token per browser, granted from your account page. That token proves who you are, and it lives in the browser's extension storage, never in the local storage of any page, so no site you edit can read it.

Which project a site belongs to is a note kept in your own browser's extension storage, not a registry on our side. We learn a page's address only when you actually open the editor on it. The extension asks for no standing access to the sites you visit: it acts on a page when you invoke it, and not before.

Visitors to your site

The script tag runs for everyone who loads your page, so it is worth being exact about what that costs them.

A visitor who has never seen your project makes one connection to our relay, carrying the project key and the address of the page. We answer whether the project has been connected, their browser writes that answer down, and it never asks again, every later page view reaches us zero times. We create no visitor record for these connections, and the address the connection came from is not stored.

If you install Pixy on a site, you are the one with a relationship to your visitors: your own privacy notice should say that Pixy is in use.

Payments

Paid plans are billed through Stripe. Your card details are entered on Stripe's own checkout page and never touch our servers, we never see, hold or process a card number.

To bill you, we give Stripe your email address and your account identifier, and Stripe collects your billing address so it can work out the tax included in your price. What comes back to us is the state of your subscription and a record of each payment. Stripe is a payment processor in its own right; its handling of your data is covered by Stripe's privacy policy.

Cookies and browser storage

No cookies, on our site or on yours. What we use instead is your browser's own storage:

  • On pixydesignapp.com: your visitor identifier and your colour theme.
  • On a site you have connected: the editor's authorisation for that site, a note that the project is connected, and your editor panel layout.
  • During a live session: the conversation, in session storage, which your browser discards when the tab closes.

Sharing

We never sell your data, and we run no advertising.

It leaves our servers in only two directions: to Stripe, to bill you, and if the law requires it. Our email is sent from our own mail server on our own domain, so your address does not pass through a third-party email service. Location is resolved against a database held on our server, so no address is ever sent anywhere to be looked up.

Where your data lives

Our servers are in the United States. Stripe processes payments on its own infrastructure. We are a UK company, and UK GDPR governs how we handle your data wherever it sits; transfers outside the UK rest on the safeguards those rules require.

How long we keep it

  • Drafts and parked records: no clock. An intent waits for its agent, five days or ninety-seven; deleting your work on a timer would be the wrong behaviour.
  • Built and declined records: thirty days on your dashboard, then thirty days archived, then deleted.
  • Session messages: with the task they belong to, on the same clock.
  • Images: as long as a record still refers to them.
  • The activity log: ninety days.
  • Editor and extension tokens: expire after 180 days without use, not at a fixed age. Revoking one is immediate.
  • Sign-in codes, pairing codes and agent invitations: minutes.
  • Your account, projects and keys: while your account is open.
  • Payment records: six years, which is how long UK tax law requires us to keep them.
  • Visit records and messages you send us: twelve months.

Your rights

You can ask us what we hold about you, request a copy, correct it, have it deleted, or object to how we use it. The contact page is the way in for all of it, and we answer within a month.

Ask us to close your account and we remove it along with your projects, keys, records, images and conversations. If you are unhappy with how we handled something, you can also complain to the UK Information Commissioner's Office at ico.org.uk.

Age

Pixy is a tool for people who build websites, and it is not intended for children. You need to be at least 16 to have an account.

Changes

When this policy changes, the new version appears here with a new date.