How we handle your data
Updated October 11, 2026. SotaYard is an early-access service for training and deploying classification models. This notice describes the data used by the current beta.
Account and sign-in information
We use your email address to send sign-in codes and associate your account with its projects. Account information, sessions, API key records, and request usage are handled through Cloudflare. Sign-in uses essential, HTTP-only cookies.
Datasets and trained models
Your uploaded examples, task descriptions, data preparation reports, model artifacts, evaluation results, and saved corrections are stored on SotaYard’s dedicated application server hosted by Hetzner. They are used to perform the task you request and serve predictions for your account.
We do not use one customer’s uploaded data to train another customer’s model. Do not upload data you are not authorized to use. The beta is not intended for highly sensitive information or regulated workloads requiring a separate agreement.
Predictions and corrections
Inputs submitted for prediction are processed by the deployed model. Saving a correction explicitly stores the inputs, the expected label, and the model version so you can export them for a future dataset. A saved correction does not automatically update a model.
Retention and deletion
Projects retain their uploaded data, reports, model artifacts, and saved corrections until you delete the project. Deleting a project removes those records and its deployment and requests cancellation of active work. The worker cleans up the deleted project’s remaining artifacts.
Operational usage counters and one-way fingerprints used to prevent reuse of final evaluation data may remain after project deletion. These fingerprints are not copies of the uploaded examples. Account information remains associated with your sign-in account.
Service providers
The current service uses Cloudflare for its public website, authentication, email delivery, and API gateway, and Hetzner for application storage and model computation. Requests pass through these providers to operate the service.
Your controls
You can revoke API keys in Account, export saved corrections from the deployment page, and delete a project from Task details. Keep a copy of your original datasets. Beta operation can change as the service develops.