Privacy Policy

01Who we are

EyeCaptain is operated by Anvilfy Ltd, a company registered in England and Wales (company number 17352045), registered office 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. We are the controller of the personal data described in this policy.

Contact us about privacy at hello@eyecaptain.io.

This policy explains how we handle personal data under the UK GDPR, the Data Protection Act 2018, the Privacy and Electronic Communications Regulations (PECR) and, where it applies, the EU GDPR.

02When we are a controller and when we are a processor

We are the controller for data about our website visitors, account holders, team members, leads and customers, as described below.

When you ask us to analyse a web page, the page may contain personal data about other people (for example names, photos or reviews). We process that data only to produce your report, on your instructions, and act as your processor. The Data Processing Addendum governs that processing. If you are a person whose data appeared on a page someone analysed, please contact the owner of that website or our customer; we will help them respond.

03What we collect

We do not knowingly collect special category data, and we ask you not to submit it. The Service is not intended for children under 18.

04How we use it and our legal bases

Where we rely on legitimate interests, we have balanced them against your rights. You can ask us for details at hello@eyecaptain.io.

05AI and automated processing

Reports are produced by sending the content and screenshots of the analysed page, and the business context you give us, to AI models through our providers listed on the Sub-processors page. We do not use your content to train third-party AI models and choose provider settings that do not allow it where available.

We do not make decisions about you that produce legal or similarly significant effects based solely on automated processing. Automated checks limit free audits and detect abuse; if you think one has affected you wrongly, contact us and a person will review it.

06Google user data

If you connect Google Analytics or Google Search Console, we ask Google for read-only access only: https://www.googleapis.com/auth/analytics.readonly for Google Analytics and https://www.googleapis.com/auth/webmasters.readonly for Search Console. We cannot change anything in your Google accounts.

What we read. For Google Analytics: visits, views, engagement, entries that leave or reach a key event, channels and devices for the page being analysed, over the last 28 full days. For Search Console: clicks, impressions, click-through rate and position of the page, the searches that show it, and whether Google indexes it. We read these figures when you run an audit or ask the AI agent about them. We keep only the figures that appear in the report or the answer you asked for, and the access token, stored encrypted, until you disconnect.

How we use it. Only to show it to you inside the Service and to write the report or answer you asked for. To do that, the figures are sent to the AI model provider that writes it (see the sub-processors page), for that request only, and our providers may not use them to train their models. We do not use Google user data to develop, improve or train generalised artificial intelligence or machine learning models. We do not sell it, do not use it for advertising, and do not transfer it to others except as needed to provide the Service, to comply with law, or with your consent. People at EyeCaptain do not read it except with your permission when you ask for support, for security, or to comply with law.

Our use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. This applies to every feature that uses this data: audits, the AI agent and reports shared by link.

If we ever want to use Google user data in a way not described here, we will update this policy and ask for your permission before we do. You can disconnect at any time in your settings, or remove EyeCaptain's access in your Google account at myaccount.google.com/permissions.

07PostHog, Mixpanel and Microsoft Clarity

If you connect PostHog, Mixpanel or Microsoft Clarity, the access is read-only. We read figures for the page being analysed over about the last 28 to 30 days: visits and views, rage clicks and dead clicks, scroll depth and active time, errors and quick backs, split by device or operating system. Which figures exist depends on the tool.

PostHog and Mixpanel are read at the time of the audit, and we keep only the figures that appear in the report. Microsoft Clarity only lets us export one to three days at a time, so we take and keep a snapshot of those figures each day from the day you connect, until you disconnect or delete the client folder. The sign-in or API key is stored encrypted. Each connection belongs to one client folder, so an audit only reads that client's data.

We use these figures only to write the reports and answers you ask for, in the same way as Google user data above: they are sent to the AI model provider for that request, not used to train models, not sold and not used for advertising.

08Live heatmaps and A/B tests: the tracking code

Live heatmaps and A/B tests use a small piece of code that you install on your own website. For the visitors of your website, you are the controller and we are your processor under the data processing agreement. You are responsible for having the right to install it, and for any notice or consent your visitors need under the law that applies to your website.

The code runs only on a page that a running study or test covers, and only on the domains of that client folder. It sends: where visitors click or tap (the element's position in the page, and whether it was a rage click or a click that did nothing); how far they scroll and how long they are active; how long each section of the page is on screen; whether the calls to action we measure were seen or clicked and whether your goal happened; the device type; the referring site's host; campaign parameters such as utm_source; and, for A/B tests, which version the visitor saw.

It never sends what anyone types, the text of the page, the query string of the address, cookies or other identifiers, or the IP address. By default it stores nothing in the visitor's browser. The only information we keep from the request itself is the country code that our network provider adds. It does not record or replay sessions. Known bots are ignored.

We keep the raw figures while the study or test runs and for 45 days after the report is written, so a correction can be applied without asking your visitors again, and then delete them. Cancelling a study deletes them at once, and deleting a client folder or your account deletes them with it. The figures that appear in the report stay with the report.

09Features released in stages

Some features reach accounts in stages. This policy already describes how each one handles personal data, so that you can rely on it from the day the feature is switched on for you.

• AI agent. You ask questions in plain words. We process the questions, the audits and the figures you have connected, and send what is needed to the AI model provider to write the answer. The use is the same as for reports: not used to train models, not sold, not used for advertising.
• Visual mockups. We open your page in a browser, rewrite one section of it, and keep the resulting image with your report. Nothing is changed on your website.
• Figma design audit. We keep the image of the frame you upload, or the layers, text and sizes the plugin reads from the frames you choose, together with the report. The plugin reads nothing else in your Figma files.
• Funnel Audit and User Agent. An automated visitor opens the pages of your website that you name, or finds its own way towards a goal you set, and records what it sees. It never makes a payment and never types a card number or a password. Where a form needs to be filled, it uses clearly marked test details. You are responsible for having the right to run it on the website, and for the test entries it may leave in your own systems.

10EyeCaptain for Chrome

Our browser extension works only on the tab you open it on, and only when you click its icon, press its keyboard shortcut or choose it from the right-click menu. It does not read your browsing history, other tabs, or pages in the background. The one exception is a funnel you choose to record, described below.

When you run an audit with it, it captures that page as your browser shows it: screenshots, the visible text, the layout and position of elements, colours, and the page address and title, together with the window size and browser language. Before capturing, it clears what you typed into form fields and puts it back afterwards, so those values are neither photographed nor sent. A page you are signed in to can still show your own details (for example your name or basket); do not audit a page that shows personal information you do not want in a report. What it sends is processed and kept exactly like any other audit.

A Quick Check reads the same kinds of information from the page (the text, position and colours of its buttons, headings, prices, ratings, forms and images, and how many fields each form has, never what is typed in them) and takes one screenshot of the first screen. We keep the result, the page address and the counts for your account's history and credit billing; the screenshot is sent to our AI provider for the check and is not stored by us.

The extension works with an EyeCaptain account. Until you connect one, it does not check or capture any page; it only offers to create an account or sign in. Heatmap, content and technical audits started from the extension send only the page address: our servers open the public page themselves, exactly as for audits started in the app.

When you record a funnel, you first allow the extension to see one site (Chrome asks you). While the recording runs, and only on that site in that tab, it notes the address and title of each page you open and the text of the link or button you click to move on. Form values are never read. When you press Stop it sends that path to your account to run the analysis, and removes the site access. Cancel discards the recording.

Findings you choose to show on a page are drawn by the extension inside that tab only; the page itself cannot read them.

The popup can show short EyeCaptain offers in a rotating banner (our own, never third-party ads). To choose them, the extension asks our server for the current offers, with your account's access token when a browser is connected so we can tell a Free plan from a paid one; nothing about the page you are on is sent. We count when an offer is shown, clicked or hidden, together with the offer's tracking code and a random id the extension makes for that browser (it is not linked to the pages you visit and it contains nothing about you). The offer's link carries the same tracking code in its UTM tags. When you connect the browser to an account, we link that random id to the account, so we can tell which offer led to a sign-up, a free CRO audit or a purchase. We use this only to measure our own offers. Closing the banner hides it for 24 hours; that choice is remembered on your computer only.

In the browser it stores only an access token for your account (never your password), your last choice of account, workspace and report language, the audits and funnel analyses you started until they finish, a funnel while you are recording it, your last Quick Check result for each open tab until the browser closes, which offers you have seen or hidden, and the random id described above (removed with the extension). The access token stays valid while you use the extension and expires after a year without use. You can disconnect a browser at any time in Settings > Chrome extension, or remove the extension.

The use of information received through the extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements: it is used only to provide the audit you asked for, it is not sold, not used for advertising or to determine creditworthiness, and people do not read it except with your permission, for security, or to comply with law.

11Who we share it with

• Service providers who process data for us under contract, listed on our Sub-processors page (hosting, capture, AI models, payments, email).
• Stripe and Link when a purchase is sold through Link, the payment service of Stripe that acts as merchant of record for that payment. Link collects your payment and billing details at checkout and uses them under its own privacy notice to take payment, work out and pay tax, send receipts and handle payment support; it shares with us what we need to give you access (such as your email, plan and payment status).
• People you choose: anyone you give a share link or embed to, and members of your workspace.
• Professional advisers such as accountants, lawyers and insurers, under confidentiality.
• Authorities where the law requires it.
• A buyer or successor if our business or its assets are sold or reorganised, under the same protections.

We do not sell personal data and do not share it for cross-context behavioural advertising except through the advertising cookies you allow.

12International transfers

Our main database is hosted in the European Union (Frankfurt). Some providers process data in the United States and other countries. When personal data leaves the UK or the EEA, we rely on adequacy regulations or decisions (including the EU-US Data Privacy Framework and its UK Extension where the provider is certified), or on the EU Standard Contractual Clauses with the UK International Data Transfer Addendum, with supplementary measures where needed. You can ask us for a copy of the relevant safeguards.

13How long we keep it

14Your rights

You have the right to:

• access the personal data we hold about you and get a copy;
• correct data that is inaccurate or incomplete;
• have your data deleted in certain circumstances;
• restrict or object to our processing, including at any time to direct marketing and to processing based on legitimate interests;
• receive data you gave us in a portable format;
• withdraw consent at any time, without affecting processing that happened before.

To use your rights, write to hello@eyecaptain.io from the email address on your account. We may ask you to confirm your identity. We reply within one month, which we can extend by two months for complex requests, and we will tell you if we do. There is no fee in most cases.

You can also delete projects and your account in the app, change email preferences from the link in any email, and change cookie choices at any time from the cookie settings.

If you are unhappy with how we handle your data, please contact us first. You have the right to complain to the UK Information Commissioner's Office (ico.org.uk, 0303 123 1113) or, if you live in the EU, to the data protection authority where you live or work (in Greece, the Hellenic Data Protection Authority, dpa.gr).

15Security

We protect personal data with measures that include encryption in transit, encryption of stored access tokens, access controls and row-level security in our database, two-factor authentication for accounts that enable it, rate limits and logging. No system is perfectly secure; if a breach affects your data and is likely to create a high risk to you, we will tell you without undue delay.

16Cookies

We use strictly necessary cookies to run the Service and, only with your consent, analytics and marketing cookies. Details and choices are in our Cookie Policy.

17Changes to this policy

We will update this policy when our processing changes. If a change is significant, we will tell account holders by email or in the app before it takes effect. The version and date are at the top of this page.

18Contact

Anvilfy Ltd, 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. Email: hello@eyecaptain.io.