SPHYNX
esc
  • Loading
Open console

Legal

Privacy policy

What data the service handles, where it goes and how long it is kept.

Last updated: November 21, 2026

This policy explains what Sphynx ("we", "us") does with personal data when you use the Sphynx API, sessions, agent runs, MCP server, live view, console, documentation and websites ("the service").

1. Two kinds of data

Data about you as our customer. Your contact details, your API keys, records of your sessions and usage, logs. We decide how this is used. Section 2 lists it.

Data inside the pages you load. What is on the pages a session loads, what you type into them and what you extract from them may include personal data about other people. You decide which pages to load and what to do with what is on them. We process that data only to run the service for you, and we do not use it for our own purposes. Section 3 describes it.

For the second kind you answer to the people the data is about, and we act as your service provider. If you need a data processing addendum, ask at [email protected]. If your data was on a page one of our customers loaded, contact that customer, or contact us and we will pass your request on where we can.

2. Data about you

  • Contact details. Your name, email address, company and the messages you send us.
  • API keys. An ID, the name the key was given, its concurrent-session limit, and when it was created and revoked. We store only a hash of the key itself and cannot read or recover it.
  • Session records. For each session: its ID and the key that created it, its status and why it ended, the region, the sphynx_id and operating system, the proxy type and country, the server address of your own proxy if you used one, the timeouts, and when it was created, last active and ended. Proxy usernames and passwords are never stored. A session record does not hold the addresses of the pages you loaded.
  • Usage. Browser seconds and proxy bytes per session, and for agent runs the number of model tokens.
  • Captcha records. When a session meets a captcha: the time, the session ID, the sphynx_id, operating system, region and proxy type, the hostname of the page (no path, no query), the captcha type, the outcome and how long it took.
  • Agent runs. The task you wrote, the options you set, the result or error, and the run's events: what the agent said it was doing, each tool call with its input, and a short summary of each result with the page address and title. Screenshots the agent takes are held while the run is running. All of this is held in memory only.
  • Live view. Streams what the session's browser shows to whoever opens the live_view_url. We do not record it.
  • Logs. For each API request: the method, the path (which includes session and run IDs), the status, the duration, a request ID and the ID of the key used. Our web server also logs the address you connected from. Logs do not hold your API key, request bodies, page content or screenshots.
  • In your browser. The console keeps your API key and a few display preferences in your browser's local storage. The docs and console do not use analytics or advertising cookies.
  • Payments. We do not charge today. If we start to, a payment provider will collect your payment details; we will hold your billing contact and what you paid, not your card number.

We use this data to provide the service, enforce limits, measure usage and bill it, keep the service secure, find and stop abuse, fix faults, improve the service, answer you, and meet legal duties. We do not sell it and do not use it for advertising.

3. Content of the pages you load

While a session runs, the browser holds the pages you load and their cookies and storage, and we pass back what you ask for: page text, HTML, extracted values and screenshots.

  • We do not keep copies of page content, extracted data or screenshots after the response is sent, apart from screenshots held with an agent run while it is running.
  • A session's cookies and storage are deleted when the session ends. A later session with the same sphynx_id starts empty.
  • We do not use page content to build profiles, train models or advertise.
  • We may look at a session or its traffic where we need to in order to fix a fault, keep the service and other customers safe, investigate a suspected breach of our terms, or comply with the law.

4. What leaves our systems

We use other companies to deliver the service. They receive only what their part needs.

Kind of providerWhat it receivesWhen
Hosting and databaseThe service runs on servers we rent; key, session, usage and captcha records are stored in a hosted databaseAlways
Model providerThe task you wrote, the content and addresses of pages the agent reads, and the screenshots it takesOnly when you start an agent run. Sessions you drive yourself and the MCP tools involve no model on our side
Captcha-handling providerThe address of the page and the site key of the captcha on itOnly when a captcha is being handled and that step is needed
Residential proxy providerThe session's traffic passes through its network. It can see which hosts the session connects to, how much data flows, and the content of traffic that is not encryptedOnly for sessions with a residential proxy
Exit-address lookup providersThe exit address of a session that uses a proxy, to set the browser's time zone and location to matchWhen a session with a proxy starts
Content deliveryThe address you connect from and the pages you ask forWhen you visit our websites
Payment providerBilling contact and payment detailsOnly once fees apply

If you bring your own proxy, the session's traffic goes through the provider you chose. The sites you load receive the session's traffic from the session's exit address, not from yours.

We also share data with authorities, courts and affected parties where the law requires it or where we believe it is needed to stop harm or answer a legal claim, with our advisers, and with a buyer if the business is transferred.

5. Security

  • API keys are stored as hashes only, and connections to the service are encrypted.
  • Session URLs carry a token that expires. Anyone holding one before then can drive or watch that session, so treat it like a password.
  • Proxy credentials you give us are kept in memory for the life of the session and are not stored.
  • Revoking a key can take up to 30 seconds. Sessions the key opened keep running until they time out.

During the preview, sessions of different customers run on the same hosts and are not fully isolated from each other. Another customer's session could reach files of yours while your session is live, and can see the network address you connect from. Do not load or type anything into a session that you could not accept another customer seeing.

No service is perfectly secure. If we learn of a breach that affects your data, we will tell you as the law requires.

6. How long we keep data

DataKept
Key records, session records and usageUntil you ask us to delete them, or we no longer need them
Captcha records30 days
Agent runs, their events and screenshotsIn memory only: lost when the service restarts. A run keeps its last 2000 events, a key its last 100 ended runs
Page content, cookies and storage in a sessionUntil the session ends
Live viewNot recorded
LogsA limited time on the host; older logs are overwritten as new ones are written
Contact details and messagesWhile you are a customer, and after that as long as we need them for legal reasons

We may keep data longer where the law requires it, or where we need it for a dispute or an abuse investigation.

7. Where data is processed

We and our providers process data in the United States and in other countries. A session with a residential proxy sends its traffic through the country you chose.

8. Your rights

Depending on where you live, you may have the right to ask what data we hold about you, get a copy, have it corrected or deleted, and object to how we use it. Write to [email protected]. We may need to check who you are, and we may refuse where the law allows it, e.g. where we must keep records.

9. Changes

We may change this policy at any time by posting a new version. It applies from the date it is posted.

10. Contact

[email protected]