Privacy policy

Last updated 12 November 2026

pilotfish is a service of gAI Ventures (“we”, “us”). It runs web tasks in a cloud browser for you and for agents you connect. This policy explains what we collect when you use pilotfish, this website, or our MCP servers, and what we do with it. It adds pilotfish's specifics to gAI Ventures' privacy policy, which covers our other services. Questions go to contact@gai.ventures.

Personal information

Personal information is anything that identifies you, on its own or combined with other data. Giving it to us is optional, but pilotfish can't run tasks for you without an account. We may also use aggregated or de-identified data that can't be linked back to you, for example to see which kinds of tasks are slow.

What we collect

Your account. Your name, email address and Google account ID, from signing in with Google.
Your tasks. What you ask pilotfish to do, follow-ups, files you attach, and each task's settings (start page, country, model).
What the browser does. The pages a task visits, the steps it takes, screenshots and a screen recording for its replay, and files it downloads.
Saved logins. Usernames, passwords, authenticator keys, recovery codes, passkeys and site passes you save, and the cookies that keep a site signed in. These are kept encrypted in our vault (see “Your credentials and the vault”).
Your end users' data, if you are a company using identities. The logins your end users save on a pilotfish login link or that you send us, their signed-in sessions, and the tasks you run for them, kept under the identity you made for each. See “End users of companies”.
A connected Gmail inbox, only if you connect one. See “Google user data” below.
Usage and billing. The model tokens, residential traffic, CAPTCHA solves and browser time each task used, your spending limits, and your MCP keys (stored encrypted).
Enquiries. What you send through Talk to sales: your name, email, company, role, what you want to do and how you heard about us.
Your acceptance of the terms. Which version you accepted, when, and the IP address and browser you accepted it from.
Technical data. IP addresses and browser details in our server logs. We use one cookie, to keep you signed in, and browser storage for preferences such as a draft task. No advertising or analytics cookies.

How we use it

To run your tasks, sign in to sites for you, and show you history, replays and files.
To count usage, apply spending limits and bill your workspace.
To keep the service secure, prevent abuse, and fix problems.
To reply to enquiries and support requests.

We don't sell your personal information, show you ads, or train models on your tasks, pages or logins. We may send account holders product updates, and you can opt out of them.

AI models

To do a task, pilotfish sends the task and the pages it reads to an AI model provider: Anthropic, or OpenAI when you choose one of its models. Saved passwords, codes and keys are never sent to a model; pages are sent with them masked. Those providers process the data to answer our requests under their API terms.

Your credentials and the vault

Passwords and the other sign-in details above are the most sensitive things we hold, and we treat them that way:

Encrypted before they are stored. Each one is sealed with AES-256-GCM under a data key of its own owner (a person, a project, or one end user's identity), and that data key is itself encrypted with a master key held apart from the database. A sealed value copied to another owner or another site does not open.
Never sent to an AI model. The model that drives a task sees only a placeholder such as {{site.password}}; the browser types the real value into that site's own sign-in field, and pages are masked before any model reads them.
Never shown back. No API response, MCP tool, webhook, event or log contains a saved password, code, key or cookie. You can view your own saved password in the app while signed in; nobody else can: not your org's admins, not an API key, not an agent you connect, and not a company that made an identity.
Used for one thing. A credential is used only to sign in to the site it was saved for, for tasks of the person or identity it belongs to. We never sell, share or analyse it, use it to train models, or use it for anything else.
People. Our staff don't look at credentials. Access to production systems is limited to the people who run the service, and is used for security, support you ask for, or when the law requires it.
Gone when you delete it. Deleting a saved login removes it at once. Deleting an identity also destroys its encryption key, so nothing it kept can be opened again.

End users of companies (identities)

A company can use pilotfish for its own customers: each of its end users is an identity that keeps their logins, signed-in sessions, network region (the country and city its residential IP comes from) and browser identity together. For that data the company decides what pilotfish does, and we process it for the company and on its instructions. The company gets back only an identity's id, the label and user id it gave, its country, masked usernames (such as p•••@example.com), the ids of its saved logins and what its tasks cost; never a password, a cookie, an IP address or a device fingerprint. End users who want to see, correct or delete their data should ask the company that serves them; we help it answer, and you can also write to support@gai.ventures. When the company deletes an identity, its logins, sessions and device data are wiped and cannot be recovered; the record of its tasks and their cost stays for billing.

Google user data

If you connect a Gmail inbox, pilotfish asks Google for read-only access. It uses that access for one thing: while one of your tasks waits for a one-time code or sign-in link from a site, it looks for that email and uses the code or link. Nothing read from the inbox is stored, and you can disconnect it at any time in pilotfish or in your Google account.

pilotfish's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Gmail data is not used for advertising, not used to train models, not transferred except as needed to provide this feature, and not read by people unless you ask us to for support, it's needed for security, or the law requires it.

Who else processes your data

Cloud hosting: Amazon Web Services, in the United States.
AI model providers: Anthropic and, when you choose its models, OpenAI.
A residential network provider, which carries a task's traffic when a site needs a local address. It never receives saved credentials in the clear: they travel only inside the encrypted connection to the site.
A CAPTCHA-solving service, which receives the challenge on the page when a check needs it.
Google, for sign-in, a connected inbox, and our email.

We may also disclose data to public authorities when the law requires it, or to protect people or the service. If gAI Ventures is part of a merger, acquisition or sale of assets, data may pass to the company that takes over pilotfish, under this policy.

How long we keep it

Deleting a session from History removes it from the app: it no longer shows or opens anywhere. Its record (the task, its replay and files, and what it cost) is kept for billing and account records. To have it erased, email support@gai.ventures. Saved logins stay until you delete them (or the identity they belong to is deleted, which destroys its key). A site's saved sign-in expires 400 days after it was last used, or 30 days if it isn't signed in. Enquiries are kept while we're in touch and then deleted on request. Server logs are rotated. To delete your account and its data, email support@gai.ventures.

Security

Data is encrypted in transit. Saved logins, keys and sign-in cookies are encrypted at rest with keys held apart from the data, and each person's, project's and identity's are kept separate (see “Your credentials and the vault”). API keys are stored only as a hash, or sealed when you can view them again; the sign-in tokens of AI tools and terminals you connect are stored only as a hash. Access to production systems is limited to the people who run the service. No way of sending or storing data over the internet is completely secure, but we use industry-standard safeguards and keep them up to date.

Your choices

You can delete sessions, logins and keys in the app at any time, and disconnect a Gmail inbox. To access, correct, export or delete your data, email support@gai.ventures; we reply within seven business days. Depending on where you live, you may have further rights under local law, such as those of California residents under the CCPA, and we'll honour them.

Children

pilotfish isn't intended for anyone under 18.

Changes

If we change this policy, we'll update the date above, and tell account holders by email about changes that matter.

Contact

Privacy questions: contact@gai.ventures. Requests about your data: support@gai.ventures. Phone: +1 415 707 0523.