We publish the smallest set we can stand behind: user-controlled submission, export and deletion request access, a forward model-training commitment, and one infrastructure statement.
The boundary begins with data minimization: you decide what Strategy context to submit, alongside the account, security, and technical data needed to run the service, and you can request export or deletion within the limits our Privacy Notice describes.
What we read
Data minimization is standard practice: you control the Strategy context you submit, alongside the account, security, and technical data the service needs to operate (see our Privacy Notice for the full list).
Not accessed by default
Beyond what you submit and the technical/operational data described in our Privacy Notice, nothing else is accessed by default.
Who decides
You choose what to submit and may request export or deletion of your data, subject to identity verification and the retention limits our Privacy Notice describes.
It shows what you choose to submit, the infrastructure statement, and how to request export or deletion.
You choose what Strategy context to submit; account, security, and diagnostic data are collected automatically to run the service.
Built on Google Cloud & Firebase · strict per-tenant isolation
Request export or deletion through the privacy-request contact form.
Infrastructure
Built on Google Cloud & Firebase · strict per-tenant isolation
Model training
We will not train shared/base models on your data.
Data rights
You control what you submit and may request export or deletion, subject to identity verification and the retention limits our Privacy Notice describes, through the privacy-request contact form.