Privacy Policy

Digit Steam Innovations LTD, Agiou Georgiou 43, Neo Chorio Paphou, 8852 Paphos, Cyprus (“we”) is the controller for the data in this policy. Contact us about privacy at hello@nullrouter.dev.

• The site runs on a server we rent from Hetzner in Helsinki, Finland. It writes no access logs. To limit abuse, it counts requests per IP address in memory only. Our app logs only the type of an error, never your data.
• Our site sets no cookies and loads no third-party scripts; fonts and images come from our own server. (Stripe's checkout page, where you pay, sets its own cookies: see Stripe's policy.)
• To count visits, the site loads Plausible Analytics from our own server (analytics.digitsteam.com, the server that also holds our mail, on hardware rented from Hetzner in Finland). For each page you open it records the page's address without anything after “?” or “#” (except campaign tags such as utm_source), the site that sent you, the location your IP address points to (at most the city), and your browser, operating system and type of device. It may also count clicks on links to other sites and form submissions, never what you type. It doesn't store your IP address: to count each visitor once a day, it turns your IP address and browser details into a fingerprint (hash) mixed with a secret that is replaced every 24 hours, and the old secrets are deleted. The statistics have no time limit; once the day's secret is gone, they can't be linked to you. The pages that show your API key (nullrouter.dev/access) are never counted, and the site works the same if you block the analytics.
• For checkout, your browser keeps a few things on your device only: a note that this browser holds an order, and while you buy, the order's details and a key that lets only your browser unlock your API key. The order details are deleted the next time you visit after 30 days, or 60 minutes after a canceled payment.

Why: to show you the site, keep it secure and see how it is used (our legitimate interest, GDPR art. 6(1)(f)), and to deliver what you buy (art. 6(1)(b)).

• You pay on Stripe's checkout page. Stripe collects your email address, your payment details (card or Link), the country and, where needed, postcode used to work out VAT, and for an invoice your billing address and, if you add it, your VAT number. Stripe also runs fraud checks.
• In Stripe we can see your purchases: email address, cardholder name, card brand, last four digits and expiry date, amount, VAT and country, and the invoice if you asked for one. Never your full card number or security code. Stripe emails your receipt and invoice.
• When your order is processed, our servers read your payment from Stripe, including your email address, name and address, in memory only, to check it and create your key.
• On our own systems we keep, per purchase: the order and payment references, your customer ID, the credit, the VAT amount, the invoice reference and a fingerprint (hash) of your API key. No name or email address. These order records are deleted 400 days after their last change. Your key's own record keeps the payment references of its purchases and top-ups until the key is deleted.
• Stripe and we keep payment and invoice records for as long as tax and accounting law requires.

Why: to perform our contract with you (art. 6(1)(b)) and to meet tax and accounting duties (art. 6(1)(c)). You need to give Stripe your email address and payment details to buy; without them we can't sell you credit. Stripe also processes data as a controller for its own duties, such as fraud prevention; see Stripe's privacy policy.

• Prompts and answers are processed in memory on our gateway and our GPU servers in Cyprus and are not saved. We never use them to train or improve any AI model, and our staff don't read them unless you ask us in writing to look into a problem.
• The exceptions: to speed up repeated prompts, our GPU servers may keep a cache made from your prompt in their memory, which only your API key can use, with no fixed time limit; they may also keep processed images in their memory for a while. And those GPU servers can still write to disk (memory overflow files, crash reports and, rarely, error logs), so parts of a prompt could end up there.
• Usage records, with no content: for billing and limits we keep per request the key fingerprint, model, token counts, cost and timing for 90 days, counts of refused requests for 90 days, daily totals per key for 400 days, and a deleted key's record for 30 days.
• Your IP address is held in memory on our relay in Finland, for at most 10 minutes after your last connection, to handle connections and limit floods; the relay's rare crash reports can contain a scrambled (keyed-hash) form of it. Our gateway doesn't store it.

Why: to answer your requests (art. 6(1)(b)); usage records and the flood limits also protect our service from abuse (art. 6(1)(f)). If you are a business and your prompts contain other people's personal data, we process that data for you as your processor: email us first, and we agree a Data Processing Agreement (DPA) with you.

The form at nullrouter.dev/withdraw asks for your name, your email address, and your customer ID or which purchase (one of the two). Without them we can't find your purchase or confirm your withdrawal. We email the statement to our own mailbox and a confirmation to you; the website itself stores nothing. To stop abuse, the site counts submissions per IP address and per email address, as scrambled fingerprints (hashes) held in memory for 24 hours.

Why: to handle your withdrawal as the law requires (art. 6(1)(c)); the abuse counters and keeping the emails to deal with any later claims are our legitimate interest (art. 6(1)(f)).

Email to hello@nullrouter.dev is stored on a mail server we run, on hardware rented from Hetzner. If you call us on +357 96 594941, we see your number (unless you hide it) and hear what you tell us. We use your email or call only to answer you (art. 6(1)(b) when it concerns your purchase, otherwise our legitimate interest in answering, art. 6(1)(f)) and keep them only as long as needed for that.

• Stripe: payments, VAT calculation, fraud checks, receipts and invoices.
• Hetzner Online GmbH (Germany): the servers that host the website and the relay (in Finland), our mail and our visit statistics. The relay only passes on encrypted traffic and holds no key to unlock it. Hetzner also filters network attacks in front of its servers.
• Cloudflare, Inc. (USA): our domain's DNS. It answers lookups for nullrouter.dev and never sees your requests or their content.
• Our accountant and the tax authorities, for invoices and tax returns; and authorities or courts when the law requires it.

The gateway and the GPU servers that answer your requests are our own hardware in Cyprus. The makers of the models we run receive no data from us.

Cloudflare is a US company and Stripe is part of a US group, so some data about payments or DNS lookups may be processed in the USA. Where it is, they use the safeguards the GDPR requires: the EU-US Data Privacy Framework or the European Commission's standard contractual clauses. Email us for a copy of these safeguards.

You can ask us for a copy of your data, to correct or delete it, to restrict its use, and to receive it in a portable format. Email hello@nullrouter.dev; we answer within one month. Because we keep no name or email address with your API usage, tell us your customer ID or how you paid, so we can find your records.

Your right to object: where we rely on our legitimate interest, you can object at any time, for reasons about your situation, and we then stop unless we have compelling grounds or need the data for legal claims.

You can also complain to the Office of the Commissioner for Personal Data Protection in Cyprus (dataprotection.gov.cy) or to the authority where you live. We make no automated decisions about you that have legal or similar effects.

Requests stay encrypted (HTTPS) from your app to our gateway in Cyprus; the relay in Finland that forwards them holds no key to unlock them. Your API key reaches your browser encrypted end to end. Until you press Finish (at most 7 days), we also hold that encrypted copy, which only your browser can unlock; after that, we keep only the key's fingerprint. The website writes no access logs.

The version and date are at the top of this page. If we change how we use your data in a way that matters, we say so on this site before the change applies.