Privacy

1 · Who we are

Sequences, Philadelphia, Pennsylvania, United States, is the controller of the personal data described below. Questions and requests: founders@generalsequences.com.

2 · What the website collects

When you submit the access request form we store:

• the email address you enter;
• the domain of that address, and whether it is a company or a free-mail address;
• the arm you deploy and the task you describe, as you wrote them;
• the page that referred you, where your browser sends one;
• the country your request came from, derived by our hosting provider from your IP address.

We do not ask for a name, a phone number, a job title or a company name, and we do not enrich what you give us with data bought from anyone else. If you later correspond with us by email, that correspondence sits in our mailbox in the ordinary way.

3 · What the API receives

If you are given access to the API, requests you send may contain camera frames, robot state, and text instructions. Those are workplace observations rather than consumer data, but a camera frame taken in a workplace can contain a person, so we treat them as capable of holding personal data and describe them here.

We do not use the content of your requests to train models, and we do not sell it or share it for advertising. We use it to serve and meter the request, to keep the service secure and available, to investigate errors and suspected abuse, and to comply with law. We keep the metering — model, token counts, timing, status — because it is what a bill is made of. We retain request content only as long as those purposes require, and we may keep aggregated or de-identified statistics that do not identify you or your organisation.

Requests are forwarded to the provider of the model you name. That is what the service does, and it means the content of a request leaves our infrastructure and is handled under that provider's terms and privacy policy. If that matters to you, the model catalogue marks which models can be served without a third-party provider in the path.

4 · Why we collect it, and on what basis

Form data: to reply to your enquiry and, if it is relevant to both of us, to discuss access to the API. Request data: to perform the service you asked for and to bill it correctly. Where a lawful basis is required, we rely on your consent in submitting the form, and on the performance of a contract for use of the API.

We do not use your address for marketing campaigns, we do not run advertising, and we do not sell, rent or trade personal data.

5 · Cookies and analytics

This site sets no cookies and runs no third-party analytics, advertising or tracking scripts.

6 · Who processes it

Vercel Inc. hosts this site and the database that stores access requests, and acts as our processor. Vercel keeps standard operational logs (IP address, user agent, timestamp) for its own operational purposes.

For API requests, the provider of the model you name receives the content of that request. Which providers those are is published in the model catalogue, per model, so the list is visible rather than described. Where we serve a model on our own infrastructure, no additional provider is involved.

Apart from those, we share personal data only with service providers acting on our instructions — such as hosting, error monitoring, payment and support tooling — and only as far as they need it to provide that service to us. We do not sell personal data or share it for advertising. We may disclose data where we are legally required to, to enforce our terms, or to protect the rights or safety of any person; where the law allows it, we will tell you.

7 · Where it is stored

On infrastructure in the United States. If you are in the European Economic Area, the United Kingdom, or a jurisdiction with comparable rules, submitting the form or sending a request involves a transfer of personal data to the United States, and onward to a model provider where you name a model that is hosted by one.

8 · How long we keep it

Form data: until you ask us to delete it, or until twenty-four months after our last contact with you — whichever comes first. Metering records: for as long as we need them for billing and accounting. Request content: not retained beyond serving the request, other than where you have asked us to investigate a specific failure. Records we are required to retain for tax or legal reasons are kept for as long as the law requires.

9 · Your rights

Subject to the law that applies to you, you may 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 retain 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 site and the API are served over HTTPS. The database is not publicly reachable and access is limited to the people who need it. API keys are held by you and are the credential that authorises requests, so treat them as a secret. No system is perfectly secure. If a breach affecting your personal data occurs, we will notify you and any regulator where the applicable law requires it, within the time that law allows.

12 · Children

This site is aimed at 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.