Trust and securityThis page states the commitments we can support today, the security practices that apply to the public site and the product, and how to raise a security question.
Last reviewed: October 2026.
Public commitment
SeekBytes has signed the Cloud Security Alliance AI Trustworthy Pledge, affirming our commitment to responsible AI development and operation.
We are preparing our AI security self-assessment for submission to the CSA STAR Registry. A published Level 1 entry is a self-assessment. It is not an independent audit or a certification, and it is not listed here until the registry entry exists.
These are the controls we operate for the public website and the SeekBytes product. They are written for a buyer review, not as an architecture guide.
Sign-in is required for customer and operator areas. Permissions are checked on the server, and a customer account cannot grant itself operator access.
Each customer's records stay with that customer. One customer's list does not include another customer's work.
An API credential is shown once, stored only as a one-way hash, and can be limited, expired, or revoked on its own. Signing in to the dashboard is separate from holding an API credential.
Videos, images, and documents used for a run are deleted when that run finishes, including when the run fails. Short-lived run evidence is not published as a public folder.
The public website and the API are served over HTTPS in production.
API access and important account actions are recorded. Those records keep the request path, result, and network address. They do not keep secrets.
The product database is backed up on a schedule and older backup copies are removed after a limited time.
The pledge and these practices cover the SeekBytes public website and the products below. They do not, by themselves, describe a customer's own systems.
Turns operational recordings and documents into a reviewable manual. A person approves what is published.
Compares what an automated run claimed with what the screen showed, and keeps that comparison for review.
Runs the local steps on the customer's own computer, including work that stays on that machine.
Recordings and documents you submit are used to produce a reviewable manual or a verification result. A person approves what is published. In a customer-managed deployment, processing stays in the environment you operate. This page does not claim that every model provider retains nothing, and it does not claim an independent security certification.
For a security question, a document request, or a report about the public website, use the contact form. Please do not include passwords, API credentials, or customer data in the first message.
