HateAPI privacy policy

Google sign-in supplies an account identifier, name, email address, and verification status. We store your account identifier, name, email address, sign-in times, and the terms version you accepted and when.

Classification requests include the content (including any image or video attachments), context, model, provider, and options you choose. The service processes the request and stores classification records and usage information, including results, request identifiers, token counts, timing, and available provider cost information. It keeps a fingerprint of each request rather than the submitted content itself, but a result's explanation can quote that content. Do not submit private or confidential material unless separately authorized.

To use your provider account, you supply its API key. Saved provider keys are encrypted with Google Cloud Key Management Service envelope encryption before storage. Account screens show only their last four characters; key-save, replacement, and removal events are recorded. We use the key to send authorized requests to the selected provider. A provider key sent with an individual API request is used for that request and is not stored. HateAPI platform keys authenticate your account, are stored only as a hash, and must also be kept secret.

The site uses only the cookies it needs to work. A session cookie keeps you signed in for up to 24 hours. Short-lived cookies protect the Google sign-in flow and carry your acceptance of the terms until sign-in completes. Cookies that last until you close your browser count free example runs. We do not use advertising or analytics cookies, and the site loads no third-party analytics or tracking scripts.

Your browser also keeps a temporary copy of a request you are working on, so that it survives signing in: edited text and context in session storage until they are restored, and a request handed to the integration guide, including any attachments, in the browser's IndexedDB storage, where it expires after one hour. This copy stays on your device until you run the request.

We process this information to create and secure your account, complete classifications, return and retrieve results, report usage, enforce limits, investigate abuse, and respond to support or legal requests. Google Cloud hosts the service, databases, and operational logs; Google handles sign-in.

Request content and relevant context are sent to the selected model provider, directly or through the routing provider identified by the model configuration. The hosted AddressHate model runs on AddressHate's own Google Cloud infrastructure, so requests to it are not sent to an outside model provider. Free example runs on other models use AddressHate's own provider account. The provider receives the credential needed to authorize the call. Providers have their own billing, data-handling, retention, and model-training terms; review them before submitting content. We do not promise a uniform retention or training policy across providers.

We do not sell provider keys. Supplying content for a classification does not itself authorize its publication as a dataset or its use to train an AddressHate model. Public example content and its recorded annotations are already part of the research resources displayed by the suite.

Operational systems process request metadata such as network address, time, endpoint, and response status. Limited free example runs use a keyed hash of your network address, kept with usage records, and browser cookies to enforce trial limits. Logs and usage records help us investigate failures and misuse. Provider secrets are redacted from application logs.

Saved provider keys, and classification results from the website and playground, use application-level encryption in addition to the protections of the hosting platform. No system is completely secure. Removing a provider key prevents future use of that saved key; it does not cancel provider charges or automatically delete previous classification records.

Account information, classification records, usage records, and key-history records remain stored until we delete them in response to a request; there is currently no self-service account deletion. The service does not currently promise an automatic expiry period for these records. Contact us to request deletion or ask about a particular record. Some records may need to be retained for security, legal obligations, or an applicable agreement. Operational logs are currently kept for about 30 days and database backups for about 7 days; providers keep their own records under their own retention terms.

The service runs on Google Cloud in the United States. Your selected provider may process content in other locations according to its own terms.

You can sign out, remove saved provider keys in Settings, and revoke credentials with the provider that issued them. To request access, correction, or deletion of account information or classification records, email alehavi@addresshate.org. We may need to verify your identity before acting on a request.

Accounts are for adults aged 18 or older. Contact us if you believe a child's information has been submitted. We will update this page when the processing described here changes.