What we store
Short version: we keep the order and payment record. We do not keep who you are or what you say.
If you pay by card or Apple Pay, Stripe (our payment processor) collects your card details, email and IP address on its own page under its own privacy policy. Stripe's replies to our server also contain some of these details. Our software reads only the payment ID, the amount, the fee, the payment type (card, Apple Pay or Google Pay) and the card's country, and stores none of the rest; it never writes them to our database or logs.
What we store
| item | why | how long |
|---|---|---|
| Order record: model, tier, hours, price, state, timestamps | To run the order, refund it, and keep our books | 7 years |
| Per-order deposit address | To receive and match your payment | 7 years |
| Paying wallet address | To send a refund to the right wallet, and to check it against sanctions lists | 7 years |
| Amounts and transaction hashes | To match payments, sweep funds, and keep our books | 7 years |
| Card payments only: Stripe Checkout session ID and PaymentIntent ID | To match the payment, refund it, and answer disputes | 7 years |
| Card payments only: payment type (card, Apple Pay or Google Pay) and Stripe fee | For our books | 7 years |
| Terms acceptance: ticked flag, terms version, time | To show you accepted the Terms and AUP | 7 years |
| Rating and comment, if you give one | To improve the service | 7 years |
| Headline-test data: random browser ID (kept in your browser's localStorage), headline variant, traffic source, funnel step, time | To learn which headline works. The ID is random. If you place an order, it is linked to that order | 90 days |
| Order records in the daily bookkeeping report: order ID, model, tier, amounts, outcome. Sent to the operator's private Telegram (a third party). Operator alerts also go there (e.g. a sanctions hold names the order ID only). No wallet addresses are sent | To keep our books | Kept by Telegram until the operator deletes the message |
| Encrypted backups of the order database (includes paying wallets) | To recover from a failed server | 14 days on the server. Copies pulled to the operator's home server are kept 30 days. Backups include all of the data listed above, so headline-test and order rows can outlive their own period by up to that long |
| Order API key | So your endpoint works until the session ends | 7 years |
The browser ID is not a cookie. You can delete it by clearing site data.
What we do not store
- IP address
- chat content
- prompts
- API request bodies
- name
Card payments: we do not store card number, last 4 digits, card brand, card type (credit or debit), card country, name, email, billing address or receipt link.
The country of your card is checked once at payment against the blocked-regions list. It is held in memory only and is not stored.
The country of your IP address is looked up in memory to apply the sanctions block. It is never stored.
Third parties
- Telegram: the operator's private bookkeeping report and alerts (see the table).
- Stripe: card and Apple Pay payments, on its hosted page.
Limits
Card payments are not anonymous to Stripe, or to the card issuer (your bank). Stripe and the issuer know who you are. We do not store your name or email, but the payment ID we keep lets us look up the payment in our Stripe account, including the name and email you gave Stripe, when we handle a refund or a dispute.
The GPU host is a third party and can see what runs on its machine. See the Terms.
Terms · AUP · What we store · Report abuse · IP geolocation by DB-IP (db-ip.com)