Version 2.4 - 2026-11-09. Replaces version 2.1 of 2026-11-06 (earlier versions are in the archive).
SAGG is an API gateway for AI models. It is run by Oleg Dorofeev, operating as SAGG / PrivateDeskAI, British Columbia, Canada. This policy covers the SAGG API and this website. It applies when you use SAGG directly and when you reach it through an aggregator such as OpenRouter.
The service is for professional and business use by people who are 18 or older.
Contact for privacy questions and requests: support@privatedeskai.com. We have not named a separate data protection officer or a representative in another country; this address is the contact for all privacy matters.
We do not store the text of your requests or of the answers. The text passes through the memory of our server while your request is being handled. We do not write it to our logs, databases or files.
We checked this by reading our code and by searching our logs for message text. We found none.
This is a statement about us only. It says nothing about the companies that process your requests (see section 5).
| What | Why | How long we keep it |
|---|---|---|
| Account data: your e-mail address, your API keys, the date each key was issued and its status, your prepaid balance | to run your account and check your keys | Until you ask us to delete it or the account is closed. A registration that is never confirmed by a payment is deleted after 48 hours (7 days if a payment was started). |
| Record of your acceptance of the Terms, the Privacy Policy and the Acceptable Use Policy: your client ID, the time, the version numbers of the documents, and whether you accepted at registration or at a top-up | to show that you accepted the texts that applied | As long as the account exists |
| Payment records: payment ID, amount, currency, time, status. For crypto payments also the public wallet address of the payer. | to credit your balance, to keep accounts as the law requires | These records are kept without a fixed deletion date, because we need them to keep our accounts and to meet accounting and tax duties. We have not set a shorter period. |
| Card details | - | We never receive them. You type them into a payment form that Stripe provides on our page. |
| Technical service records: request ID, time, your client ID, the line and provider used, token counts, delay, status and error codes, and the short technical error text a provider returns | billing, abuse prevention, finding faults | 30 days in the service log archive and 30 days in a compact request record (one line per request: the fields listed here, never the text of your requests or answers). The live log is cleared when we update the service. |
| Web server records: for every request the time, the address requested, the status, the size and the browser name (User-Agent), without your IP address. Records of web server errors may contain your IP address. | finding faults, blocking abuse | Until a size limit is reached, which is usually between a week and several months. |
| Request-rate counters per client | rate limits | 24 hours |
| Short request trace (IDs, steps and outcomes, no text) | finding faults | Up to 6 hours |
| Daily page and sign-up counters | to see if the service is used. They are not linked to any person or IP address. | About 30 days |
| Usage counters for partner platforms | to check invoices | 90 days |
| Short-lived records: a key recovery code, a note for a visit to the account page, and the IDs of Stripe events already handled (so that a payment is never credited twice) | security and correct payments | Recovery code 1 hour; account-page visit note 20 minutes; Stripe event IDs 30 days |
| Backups of the above | recovery after a failure | One plain archive per day, the last 7 are kept, on the same server as the data. Deleted data can stay in a backup for up to about 7 days. |
We use this data to run your account, to take and record payments, to bill, to prevent abuse, to find faults and to keep accounts as the law requires. We use it for no other purpose.
Cookies and browser storage. We do not set cookies, and our pages do not use localStorage. Our pages use the session storage of your browser tab (sessionStorage) for one function: when a card payment takes you to Stripe or your bank and back, the page keeps a temporary note in the tab (your e-mail address, the session token of your current visit, your balance before the payment and the time) so that it can show your updated balance when you return. The note is removed when it is read back and when the tab is closed, and it is ignored if it is older than 10 minutes. It stays on your device: the page does not send it to us by itself; after you return, the page uses the e-mail address and the session token in its ordinary requests to us, as it did before the payment. The payment form comes from Stripe, which may set its own cookies, use browser storage and collect device information under its own terms.
Our server and backups are in a data center in Nuremberg, Germany, run by Hetzner. Our payment and e-mail providers work in other countries, and the hosts of the Gonka network (section 5) are anonymous and their location is unknown to us. By using the service you accept that your data is processed outside Canada. We do not claim any special legal mechanism for these transfers beyond what this policy says.
Independent brokers and hosts of the Gonka network. SAGG sends your requests to independent access brokers of the Gonka decentralized network. The brokers pass them to independent hosts that run the model. The hosts are anonymous and outside our control. We cannot promise that data is encrypted all the way to the host, that it is not stored, or that it is not used to train models. We give no zero-retention (ZDR) and no "no training" promise for this path. Our /models listing shows this as zdr: false.
Insurance provider (Standard line). The Standard line can use a provider outside the Gonka network as a backup. It works under its own published terms. We are not responsible for them.
Payments. Stripe (Stripe, Inc. and its group companies) processes card payments. We send Stripe your e-mail address so it can send you a receipt. Crypto payments (x402) are verified and settled on the Base network through an independent payment facilitator; the payer's wallet address and the amount are also visible on the public blockchain, and we cannot erase them there.
Hosting and e-mail. Hetzner hosts the servers. Brevo sends our e-mails (for example the verification code, "balance credited" and "balance low"). Namecheap forwards mail sent to our domain addresses to us.
The Gonka brokers and hosts and the Standard-line provider are named on request.
Do not send medical or health data, payment card or bank account data, government ID numbers, other data covered by special regulation, or personal data of other people without a lawful basis to send it. We do not sign data processing agreements (DPA).
Write to support@privatedeskai.com. Within 30 days we will tell you (and give you a copy in a common file format), correct or delete what we hold about you: your e-mail address, balance, key records and service records linked to your client ID. We may ask you to prove that the account is yours.
You may also ask us to restrict our use of your data or object to it. Which rights apply depends on the law where you live. If you are not satisfied with our answer, you may complain to the privacy authority where you live (in Canada, the Office of the Privacy Commissioner of Canada; in the EU, the data protection authority of your country).
We cannot take back what the Gonka network or another provider has already received and processed, and we cannot erase blockchain records.
Access to our servers is by SSH key only; password login is switched off. Our database listens only on the server's own address (127.0.0.1) and requires a password. Backups are plain archives on the same server, readable only by the server's administrator; we do not encrypt them. No system is perfectly safe. If a breach of our safeguards creates a real risk of significant harm to you, we will tell you without undue delay after we confirm it, and we will report it to the authority where the law requires.
Each version has a number and a date. Old versions are in the archive. If we make a change that is not in your favour, we will e-mail registered customers at least 14 days before it starts.
support@privatedeskai.com (privacy requests, security and abuse reports, and general questions).