Privacy policy

This policy explains which personal data zdr.sh processes, why, on what basis, for how long and with whom, and which rights you have. It applies to the website, the dashboard, the API and support. It is published in English, which is the only version.

1. Who runs the service#

Write to support@rackduck.sh about anything in this policy, including to exercise your rights.

2. What data we process#

• Account and security data: name, email address, the password kept only as a hash and never in clear, the secret of the one-time codes of your authenticator app if you enable it, the public keys of your passkeys, the language, the security settings, the active sessions with their IP address and browser, and the history of your consents with date, time and IP address.
• Billing data: the customer type, the name or company name you give for the invoice information, and the amounts, assets, networks, transaction ids and statuses of your payments. No card data and no bank details: we take no card and no bank transfer, so none exists to store.
• Payment data: the address the top-up screen shows you and, for Monero, the payment id that goes with it; the address you name for a refund; the asset and network of each transfer, and the confirmations it reached. A crypto address is pseudonymous, not anonymous: it is personal data when it can be linked to you, and we treat it as such.
• Usage data: for each API request, the account, the key, the model, the tokens, the latency, the cost and the outcome, plus the attribution the client sent with it (an end-user id and the entries of its metadata, bounded and never the request body), written to our analytics store. The usage records never contain the text of the prompts.
• Your content: the text, files and images of the requests and responses, processed while the request runs. We keep no copy of it except in the memory vault you write to, in the response cache if you turn it on, and in the idempotency replay of a request that carries an Idempotency-Key.
• Server logs: the IP address and, when you are signed in or use a key, the account id of each request to the website, the dashboard and the API, with its time and outcome. Logs never contain request bodies.
• Support data: what you write to us and our answers.

We estimate the country of an IP address with a database installed on our own servers, without sending the address to anyone: this product includes IP geolocation data created by DB-IP (https://db-ip.com), licensed under CC BY 4.0.

3. On what basis we process it#

• Contract: to open the account, bill the usage and provide the service. The account and the billing data are necessary to make the contract: without them we cannot provide the service.
• Legal obligation: the accounting and tax rules, which require keeping the records of the payments for the period the law sets.
• Legitimate interest: to keep the service reliable and secure, through the server logs and the usage records of section 2. You have the right to object at any time.
• Consent: for anything marked optional, such as product emails. You can withdraw a consent at any time, with effect for the future.

4. No traces, no profiling#

We do not collect trace copies of requests and responses. There is no trace store, no sample of traffic kept for quality, no automated scrubbing pipeline and no opt-out to look for, because nothing is collected in the first place. The text of a request and the text of an answer exist while the request runs and nowhere on our side afterwards, except in the three places section 2 names: the memory vault, the response cache and an idempotency replay.

Each of the three is a choice, not a default: the vault holds only what you write to it, the response cache is off unless a key turns it on and holds an answer for ten minutes, and an idempotency replay holds the answer to a request that carried an Idempotency-Key for 24 hours so a retry is answered once. None of the three is read to train, score or review a model, and none is shared with anyone.

Because no request content is kept, there is nothing to erase from a trace store, and no dataset can be built from your traffic. Zero retention describes the agreement behind this.

5. No datasets#

We do not build, sell or license a dataset of requests or responses, and no recipient receives one. The dataset recipient licence that an earlier version of this policy mentioned is withdrawn: it covered traces that are no longer collected. If that ever changed, this policy would name the recipients one by one and ask for a separate consent before any data reached them, and nothing in these documents would be read as a consent given in advance.

6. Who receives the data#

A business customer can ask at support@rackduck.sh for the data processing agreement we offer under article 28 GDPR: it names the sub-processors and the transfer safeguards of each category, and it is concluded in writing outside the platform.

Transfers are handled by category of recipient: a recipient that processes inside the European Union needs no transfer tool, and for a recipient that processes outside it the transfer relies on an adequacy decision of the European Commission where one exists, and otherwise on its standard contractual clauses with the supplementary safeguards needed. Ask us for a copy of the tools in force per category. The current sub-processor list, with the providers active for your requests and the countries where they process the data, is available on request from support@rackduck.sh.

7. How long we keep it#

8. Your rights#

You can access your data, rectify it, erase it, restrict its processing, receive it in a portable format, and object to processing based on our legitimate interest. Where something rests on consent, you can withdraw it at any time. In the dashboard you can export the vault and download your usage records, and you can close the account from the dashboard or by writing to support@rackduck.sh. Exercise your rights in the dashboard where possible, or write to support@rackduck.sh: we answer within one month. You can also complain to the Garante per la protezione dei dati personali (https://www.garanteprivacy.it) or to the supervisory authority of the State where you live or work.

9. How we protect it#

We protect data by encrypting the connections in transit and the backups at rest, by storing passwords only as a hash, by sealing secrets with the server key, by restricting access to authorized staff, and by keeping request bodies out of the logs. The services run on infrastructure we control, and content and encrypted backups stay in our own object storage or with a provider bound to act only on our instructions. In case of a personal data breach we notify the Garante within 72 hours where the law requires it, and we tell you without undue delay when the risk to your rights is high.

10. Cookies#

The website and the dashboard use two technical cookies and a few preferences in your browser, and nothing else: the cookie policy names them one by one. No analytics, no advertising, no third-party tracking.

11. Contact and changes#

The version and date at the top identify the text in force; material changes are announced by email before they apply, and no new purpose or category of data is added without a new consent where consent is the basis. For questions about this policy or your data, write to support@rackduck.sh.