Legal

Privacy

Last updated 15 November 2026

1 · Who we are

General Sequences Company, a Delaware corporation (Sequences, we), is the controller of the personal data described here. Questions and requests: founders@generalsequences.com.

2 · What we collect

The contact form. When you send it we store your name, the email address you enter, the domain of that address and whether it is a company or a free-mail address, your message, the page that referred you (where your browser sends one), and the country your request came from, which our hosting provider derives from your IP address. An earlier version of the form asked for the arm you deploy and the task you describe; answers given to it are kept on the same terms. To stop one visitor from sending too many, we count each visitor’s submissions for the day under a hash of their IP address with a salt of that day’s own, and delete the counts and the salt within two days; we do not store the address itself.

Your account. Your email address and account name, how you sign in, and — if you sign in with Google — the name, email address and profile photo Google shares with us; a profile photo you upload; your timezone and time-format preferences; and your account ID.

Billing. Your plan, balance, credit purchases, usage charges and invoices. Card details are collected and held by Stripe, not by us. From Stripe we receive the billing name, email address, postal address and tax ID you give it, so that we can put them on your invoices.

What you run on the service. Requests you send to hosted models, which can contain text and images; the observations your robots send to your policies — camera frames, robot state, instructions — and the actions returned; the code, weights and files you upload for policies, benchmarks, adapters and storage; and the results, logs and recordings your workers and evaluations produce. A camera frame taken in a workplace can show a person, so we treat this content as capable of containing personal data.

Records of use. Metering records (what ran, on what, for how long, and what it cost), an audit log of actions taken on your account — with the IP address a teleoperation console connected from and the one a command-line sign-in was approved from — each command-line sign-in asked for, with the IP address it came from, and server logs that include IP addresses, user agents and timestamps.

On a GPU machine you add. Once a minute, a program on the machine, outside your container, reads how busy each card is, how much of its memory is in use and how much power it draws; the names of the processes using the cards; and the IP address and port at the other end of each of your container’s network connections. It does not read your files or anything sent over a connection. We check each reading for signs of cryptocurrency mining, which our Acceptable Use Policy prohibits — the name of a known mining program, a port that mining pools use, the address of a known pool — and keep only what matches, with when it was first and last seen and that minute’s card readings. The rest is not kept.

Page speed. When you view a page of the website or the console, your browser reports how quickly the page loaded and responded: five measurements with their ratings, which page it was (never the address you typed or its parameters), whether it was the website or the console, the address of the site, whether your device is a phone or a computer, and how you reached the page (for example a reload or the back button). The reports carry no cookie or identifier and are not linked to your account. To stop one visitor from sending too many, we count each visitor's reports for the day under a salted hash of their IP address and delete the count within two days; we do not store the address itself. A browser that sends the Global Privacy Control signal sends no reports.

We do not ask for a phone number or a job title, and we do not buy data about you from anyone else.

3 · How we use it

To provide and operate the service, run your workloads and bill them; to keep the service secure and available and to investigate errors and abuse; to measure and improve how quickly the website and the console load; to reply to enquiries and support requests; to send you notices about your account and the service; and to comply with the law. We do not use your content to train models, we do not sell personal data, and we do not use it for advertising. We may keep aggregated or de-identified statistics that do not identify you or your organisation.

Where the law requires a legal basis, we rely on the performance of our contract with you for your account and the service; on our legitimate interests in securing, operating and improving the service; on your consent when you send the contact form; and on legal obligations, such as keeping tax and accounting records.

5 · Cookies and local storage

The website sets no cookies and runs no advertising or tracking scripts; its one measurement script reports page speed as described in section 2, without a cookie or an identifier. The console keeps your sign-in session and display preferences in your browser's local storage so that you stay signed in; it is not used for tracking.

6 · Who receives it

We share personal data only with service providers that process it for us, and only as far as they need to:

  • a cloud hosting provider hosts the website and the console, and receives the contact form and page speed reports;
  • a cloud database provider hosts our database, sign-in records and uploaded files, in the United States (Oregon);
  • cloud infrastructure providers run your workers, builds and evaluations and store their files. Your volumes, recordings, captured data and the secrets you set are stored in the United States; copies of your policies' weights and images may be stored outside it. A robot's worker runs in one of our seven regions, all in the United States, the one nearest the robot; the machines that run builds, checks, evals and benchmarks are placed by the platform and may run outside the United States; a deployment cannot choose its region;
  • Stripe processes payments and holds your card and billing details;
  • Google provides sign-in with Google;
  • when you call a hosted model, the content of that request is sent to the infrastructure that serves the model and is handled under its provider's terms.

We may also disclose data where the law requires it, to enforce our terms, or to protect the rights or safety of any person; where the law allows, we will tell you.

7 · Where it is stored

Your account and its records, what you send through the contact form, your volumes, your recordings, the data your policies captured and the secrets you set are stored in the United States. Copies of your policies' weights and images and our server logs, which include IP addresses, are kept by providers that may store them outside the United States. A robot's worker runs in one of our seven regions, all in the United States, the one nearest the robot; the machines that run builds, checks, evals and benchmarks are placed by the platform and may run outside the United States; a deployment cannot choose its region. If you are in the European Economic Area, the United Kingdom or a jurisdiction with comparable rules, using the website or the service involves a transfer of personal data to the United States, and possibly to the other countries where these providers store it or your workloads run.

8 · How long we keep it

  • Contact form: until you ask us to delete it, or until twenty-four months after our last contact with you, whichever comes first; while you have an account with the same email address, as long as that account is open.
  • Account data and content: while your account is open. When you delete your account, we delete its data and content, captured data included, within 30 days, except records we must keep; copies in our backups are overwritten within a further 7 days.
  • Your account’s audit log, the IP addresses in it included, and its approved command-line sign-ins: while your account is open, deleted with it. A command-line sign-in that was never approved belongs to no account and is kept, with the IP address it came from, until you ask us to delete it.
  • Content you delete: removed from the service and permanently deleted within minutes; we cannot bring it back. Data a policy captured is not deleted with the policy: it stays in your account as a dataset until you delete that dataset or your account. Copies in our backups are overwritten within a further 7 days.
  • Logs from your workers and evaluations, and the daily counts and totals made from them: each kind for the time How long logs are kept says, then deleted; an evaluation’s records as long as the evaluation, and a build’s log as long as its version.
  • Request logs on our servers (the IP address a request came from, the address it asked for and when): up to 30 days.
  • What we keep from a GPU machine’s readings (section 2): 30 days after it was last seen.
  • Page speed reports: 30 days; daily summaries per page, which contain no personal data, 13 months; the per-visitor daily count: deleted within two days.
  • Requests to hosted models and observations sent to your policies: not stored after they are served, unless you ask us to investigate a specific failure. While a robot’s Record is on, each step goes from the worker serving it straight to your own recorder, and we store none of it; what Record stored in your account while it kept episodes there stays until its retention ends, or until you delete it. Every evaluation keeps a record of what its policy was sent and answered, for as long as the evaluation. A policy that keeps spare workers saves each running episode's state as it runs, so that a spare can take it over, and deletes it when the episode ends, an hour after its last save at the latest.
  • Metering records, invoices and payment records: for as long as we need them for billing, accounting and tax, or as the law requires.
  • Your payment details at Stripe: when you delete your account, what it owes — the due the Invoices page shows — is first charged to your payment method on file if it is $0.50 or more; if that charge fails, or there is no payment method to charge, the account is not deleted. Less than $0.50 is not charged, and the account is deleted. Once your account is deleted, we have Stripe detach every payment method on it and delete you as its customer, so no card of yours stays there and nothing more can be charged; a Team plan ends at once, its current month not refunded. Each invoice already issued keeps the billing name, email address, postal address and tax ID it was issued with: Stripe keeps issued invoices, and so do we, as tax and accounting records.

9 · Your rights

You can see and correct your account details, and delete your account, in the console. Subject to the law that applies to you, you may also ask us to:

  • tell you what we hold about you;
  • correct anything that is wrong;
  • delete it;
  • send you a copy in a portable format;
  • stop processing it, or object to our doing so.

Email founders@generalsequences.com. We will respond within the period the applicable law requires, and we may need to verify your identity first. Some requests are limited by law, for example where we must keep records for tax or accounting. If you are in the EEA or the UK you may also complain to your supervisory authority.

10 · California

We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined by California law. We have not done so in the preceding twelve months, and we do not knowingly sell or share the personal information of anyone under sixteen. California residents may exercise the rights listed above, and may designate an authorised agent to do so. We will not discriminate against you for exercising them. Email founders@generalsequences.com to make a request.

11 · Security

The website, the console and the API are served over HTTPS. Database access is controlled so that the public key the website uses cannot read form submissions or any account's data, and each signed-in account can read only its own records. Access by our staff is limited to the people who need it. API keys and access tokens are credentials: keep them secret, and revoke any you no longer need. No system is perfectly secure; if a breach affecting your personal data occurs, we will notify you and any regulator where the law requires it, within the time that law allows.

Our Security page describes how we protect your data and how to report a vulnerability to founders@generalsequences.com.

12 · Children

The service is for organisations and is not directed at children. We do not knowingly collect data from anyone under sixteen; if we learn that we have, we delete it.

13 · Changes

If what we collect or how we use it changes, we update this page and move the date at the top. Where a change materially affects data we already hold, we contact the people concerned.