# Privacy

> What Gomry Cloud stores when you call an API, what it does not store, who processes it, and how long each category is kept.

Source: https://cloud.gomry.com/privacy

This page describes what Gomry Cloud does with data as a **developer platform**. Gomry's product-wide privacy policy covers the event platform and the account you sign in with; this covers the API.

## What we store

- `Account and organization` — Your Gomry user id, the organizations you belong to, and your role in each. Identity comes from your existing Gomry account — Cloud creates no separate login.
- `API keys` — A SHA-256 hash of each key, never the key itself, plus its prefix, last four characters, scopes and expiry. A lost key cannot be recovered, only revoked and replaced.
- `Usage records` — One row per billable request: the project, the service and operation, the quantity metered, the response status, the duration and the request id. This is the record an invoice is built from.
- `Billing` — A Stripe customer id and the consent timestamp captured when a card was added. Card details are held by Stripe and never reach our systems.

## What we do not store

**We do not retain the content you fetch.** A page scraped through `/v1/scrape` or `/v1/fetch` is returned to you and not kept as a record of what you looked at; a task's cached pages exist to stop the same task paying twice for the same URL and are scoped to the project that created them. Request and response bodies are not written to our logs — logs carry the request id, the key id and the outcome, which is what a support question actually needs.

We never log a full API key, an `Authorization` header, or the body of a page a service fetched on your behalf. That is a rule in the codebase, not a preference.

## Who else processes it

Calling an API means calling the providers behind it: a scrape reaches the page you named through a rendering provider, a tool run reaches the vendor that publishes that tool, and a research task reaches the search and inference providers it needs. The URL you send and the input you supply go to those providers because that is the work you asked for. Billing is processed by Stripe. Identity is Firebase Authentication.

> **Important:** Do not send personal data you are not entitled to send to a third-party processor. An `input` passed to a tool through ToolsAPI is forwarded to that vendor unchanged — we do not inspect or filter it, and we cannot unsend it.

## Retention

Usage records are kept for as long as they may be needed to substantiate an invoice, and an unbilled usage row is never deleted — it is unbilled revenue and its absence would be a silent loss. Account, key and billing records live for the life of the organization. Revoking a key removes its ability to authenticate immediately; the usage it already generated remains, because the invoice it belongs to does.

## Access, export and deletion

Write to `info@gomry.com` from the address on your Gomry account. We will tell you what is held against your organization, export it, or delete what is not required for a settled invoice or a legal obligation. See [Contact](https://cloud.gomry.com/contact) for the rest of the addresses.