# Privacy policy What we hold about a developer and about traffic, for how long, and how to see and delete it. Effective 2026-09-04 ## Who we are We are Diet Bloxy Cola, an independent Roblox game studio in New York, and we run the API at api.dietbloxycola.com. For the data this page describes, we are the controller: it is data about you, the developer, and about the traffic your keys send. This page does not cover players of your games, because the products offered today hold no player data; see [products not yet offered](https://api.dietbloxycola.com/docs/privacy#later). ## What we hold about you - Your Roblox user id and display name, from the sign-in with Roblox. We do not receive a password. - An email address, if you give one, for the notices these policies promise. - The hashes of your keys, their prefixes, their scopes and the dates they were made, used, expired or revoked. We do not hold a key: it is shown once when it is made and stored as a hash. - Your account's audit trail: keys made and revoked, switches flipped, a deletion asked for, with a date and who did it (you, or us). ## What we hold about traffic Every request to the API writes one log line with these fields and no others: `ts`, `level`, `event`, `requestId`, `tenantId`, `keyId`, `product`, `route`, `method`, `status`, `code`, `durationMs`, `upstreamMs`, `ip` and `detail`. The `ip` is the address the request came from, which for a Roblox game is a Roblox server's address. Log lines are kept 30 days, for security and for finding a fault, and then deleted. From those requests we also count usage per account, product and route, by hour: requests, errors and two latency percentiles. The counts hold no address and no request content and are kept 13 months, so you can see a year of your own usage. ## What we do not collect - No request bodies and no response bodies are ever logged. - No player data on the keyless endpoints or on the proxy: they serve data that is public on Roblox about games, never about a person. - No analytics on the developer portal beyond the request log above; no advertising identifiers, no tracking across sites. ## Products not yet offered The analytics product (events your game sends about its players) and the erasure product (requests to delete a player's data) are not offered yet. When either ships, this page changes ahead of it, a Data Processing Agreement is offered with it, and the [retention schedule](https://api.dietbloxycola.com/docs/retention) already states what each will keep. ## Where it lives Everything above lives in the United States, in the US East region of the vendors on the [sub-processors](https://api.dietbloxycola.com/docs/subprocessors) page. There is no EU residency option in the beta; we say so rather than imply otherwise. ## Seeing and deleting it `GET /v1/account/export` answers everything we hold about your account as one JSON document, and the portal shows the same. `DELETE /v1/account`, or the portal's delete page, starts the deletion: keys die at once, the rows go after the grace the [retention schedule](https://api.dietbloxycola.com/docs/retention) states, and a written confirmation follows. A request by mail is honoured the same way once we have matched it to the account. ## Security - Everything travels over TLS. - Keys are stored as SHA-256 hashes and compared by hash; a secret you give us (a webhook URL, a signing secret) is encrypted at rest under a key that lives outside the database. - The database enforces row-level isolation per account: the application role can read one account's rows and no other's, whatever the code asks for; only a separate, audited role reads across accounts, and only for the studio's own desk. - Access to the stores is limited to the people who run the service, and every administrative action on an account is written to its audit trail. ## If something goes wrong If we confirm an incident that affects your account's data, we tell you by mail within 48 hours of confirming it, with what happened, what was affected and what we did. ## Children The developer portal is for adult developers. We do not knowingly hold an account for anyone under 18; one we learn of is closed and its data deleted. Players of your games are not our users and are not described by this page. ## Contact Write to hello@dietbloxycola.com about anything on this page, including a request to see, correct or delete what we hold. A change to this page is announced on the [changelog](https://api.dietbloxycola.com/docs/changelog) and, for a material change, by mail 30 days ahead.