Legal
Acceptable use policy
In counsel review, not yet published. When it is, it will state what the service may not be used for and what actually happens when it is, rather than listing prohibitions with no process behind them.
01Status
This document is in counsel review and is not yet published
Seldon Compute, Inc. publishes a legal document only once counsel has reviewed it against the system as actually built. That review is not finished for this one, so no version of it is published here. Nothing on this page is operative, and nothing on this page should be relied on when assessing whether to send us data.
We would rather say that plainly than publish borrowed boilerplate. A privacy notice describes what a company actually does with data, and terms of service are a contract. Both are only worth reading if they are true, and neither is true until the words have been checked against the operational practice behind them.
The finished document will be published here with its effective date recorded at the top. If you need the terms that apply to you before then, ask: customers under agreement contract on written terms today, and we will send what governs your account rather than point you at a page.
Contact
Security, privacy, data handling, and vendor due diligence. Also the address for responsible disclosure.
Contracting, commercial terms, and anything a procurement team needs in writing.
Published today
The trust center sets out the security controls and data handling posture running in production today, including the abuse monitoring behaviour that enforces use restrictions, and marks the parts of the platform that are not yet built.
Read the trust center02Intended scope
What the document will cover
A list of topics, not a summary of terms. Each item below describes something the finished document will address, and nothing below is operative until that document is published.
- 01Prohibited categories of use, written specifically enough to be applied consistently by a reviewer rather than interpreted case by case.
- 02How upstream model licences flow through. Several open-weight models we serve carry use restrictions set by their authors, and we cannot grant permissions the licence does not give us.
- 03Detection and review: what we monitor, what we do not, and how that reconciles with the data retention commitments made elsewhere.
- 04The enforcement ladder, from notice through rate limiting to suspension, and the notice period at each step.
- 05Appeals, including who reviews a suspension and the window in which a decision is returned.
- 06Reporting misuse, and what a reporter can expect to hear back.
- 07High-risk deployment contexts where additional review applies before access is granted.
- 08How the policy changes, and the notice given to customers whose workloads are affected by a change.
If you need something in writing before this is published
Security reviews and procurement processes do not wait for a publication schedule. Write to security@seldon.ai and describe what your process requires. Where an accurate answer exists we will put it in writing, and where one does not we will say so rather than send a document that reads well and means nothing.
The trust center lists the controls that are implemented today and the certifications that are not, with the distinction between the two made explicit.