Security

Last updated 12 November 2026

pilotfish, a service of gAI Ventures, signs in to websites for you with the logins you save. That is what lets it finish real tasks, and it is why we treat those logins as the most sensitive thing we hold. This page sets out how. The privacy policy and terms make the same commitments.

Where your logins and sessions are stored

In pilotfish's vault, on Amazon Web Services in the United States. Saved passwords, authenticator keys, recovery codes, passkeys and the cookies that keep a site signed in are all kept there.
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). 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.
Encrypted in transit. Everything between you, your agents and pilotfish travels over TLS. When a task uses a residential network, saved logins only ever travel inside the encrypted connection to the site itself.
API keys are kept as a hash, or sealed when you can view them again.

Who can reach them

Only the browser of your own task, to sign in to the site the login was saved for. A login is used for nothing else.
Never an AI model. The model that drives a task sees only a placeholder such as {{site.password}}. The browser types the real value into the 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, an API key, an agent you connect, or a company that made an identity.
Codes go on pilotfish's own page. When a task needs a one-time code or a sign-in from you, you enter it on pilotfish's answer page, never in the chat with your agent.
Our people. Our staff don't look at credentials. Access to production systems is limited to the people who run the service, and is used only for security, support you ask for, or when the law requires it.
Never sold, shared, analysed or used to train models.

How long they are kept, and how to delete them

Saved logins stay until you delete them in Sites & logins. Deleting one removes it at once.
A site's saved sign-in expires 400 days after it was last used, or 30 days if it isn't signed in.
An identity (one of a company's end users): deleting it also destroys its encryption key, so nothing it kept can be opened again.
Task history: deleting a session removes it from the app. Its record (the task, its replay and files, and what it cost) is kept for billing. To have it erased, or to delete your account and its data, email support@gai.ventures.

What waits for your approval

Steps you can't undo. Paying, placing an order, sending a message, deleting, transferring money or cancelling an account wait for your yes, unless you allowed that kind of step up front (optionally with an amount limit).
Each site's settings are yours. In Sites & logins you choose, per site, whether it uses a residential IP and whether bot checks are solved.
Some sites are never automated: ticket sellers covered by the US BOTS Act and India's Aadhaar (UIDAI) sites. A task that reaches one stops.
You can take over at any time. Watch any task live, take control of its browser, or stop it.

Audit trail

Every task keeps its steps, with timings, what got in the way and what it cost, and a replay video you can watch afterwards.
Org admins see the org's history: roles, invitations, people joining and leaving, API keys made and revoked, credits, limits and allowances.
Each API key's use (its tasks and spend) is shown to the org's admins.

Compliance

pilotfish doesn't hold a SOC 2 report yet. If you're reviewing pilotfish for your company, write to support@gai.ventures and we'll answer your security questions.

Who else processes data

Amazon Web Services (hosting), Anthropic and OpenAI (the AI models; they see masked pages, never saved credentials), a residential network provider (carries a task's traffic when a site needs a local address), a CAPTCHA-solving service (receives the check on the page when one needs it), and Google (sign-in, a connected inbox, and our email). The privacy policy has the details.

Report a problem

If you think a credential has been misused, or you've found a security issue, email support@gai.ventures at once.