Privacy addendum: buying and activating ConsoleMouse
Controller
Controller: naKlaro e.U., owner Stefan Mueller, , . For privacy questions, contact [email protected].
Buying through Stripe
When you click "Buy", our page generates a random request identifier (32 hexadecimal characters) and sends it with your language choice ("de" or "en") to our licence server license.consolemouse.com. The licence server creates a Checkout Session at Stripe and redirects you to checkout.stripe.com. The request identifier contains nothing about you; it prevents a repeated purchase attempt from being created twice.
On the Stripe page you enter your details directly with Stripe. Stripe processes:
- billing address (if Stripe asks for it), name and e-mail address,
- payment details (card number, expiry date, security code); these never reach us, we only see the last digits and the card brand,
- technical data such as IP address, browser details and fraud-prevention signals,
- an optional Stripe Link account, if you use one with Stripe.
Stripe (Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Dublin 2, Ireland) is an independent controller for payment processing insofar as it processes data for the payment, fraud prevention and its own legal obligations, and our processor insofar as it creates invoices for us. Stripe may transfer data to Stripe, Inc. (USA) and other Stripe entities under the EU-US Data Privacy Framework or standard contractual clauses. Details are in Stripe's privacy policy.
After payment we receive from Stripe: session and payment identifiers, amount, currency, payment status, your e-mail address, name, billing country and the last digits of the payment method, plus later events such as refund or chargeback.
Legal bases: performance of the contract (Art. 6(1)(b) GDPR) for payment, invoice and delivery; legal obligation (Art. 6(1)(c) GDPR) for invoicing and tax duties, in particular § 132 Austrian Federal Fiscal Code (BAO); legitimate interest (Art. 6(1)(f) GDPR) in preventing payment fraud.
Licence server license.consolemouse.com
The licence server runs as a Cloudflare Worker with a Cloudflare D1 database. Cloudflare (Cloudflare, Inc., USA; contracting entity for EU customers: Cloudflare Netherlands B.V.) is our processor. In operation, Cloudflare processes technical connection data such as IP address and request time; the licence server itself does not log requests and never places keys or pickup tokens in URLs, logs or analytics.
The licence server stores:
- Purchase mapping: request identifier, language, Stripe session and payment identifiers, processed Stripe event identifiers, licence identifier (32 hexadecimal characters) and the time of issuance.
- Pickup: a random pickup token that your success page uses after payment to retrieve the key once. The key is held encrypted for this and deleted at most seven days after the purchase. The token is never in a URL, never stored in the browser and never logged.
- Delivery: the recipient data needed for the confirmation e-mail (e-mail address, language, key) in an encrypted outbox that is deleted at most 24 hours after the purchase. Encrypted remnants may persist longer in database backups.
- Blocks: after a refund (including a partial refund) or a chargeback, a permanent record that the licence may no longer be activated. This record remains as long as the licence exists.
- Abuse prevention: for the limit of 30 requests per minute, a hash of the IP address is stored briefly. Such a hash remains personal data.
Legal bases: performance of the contract (Art. 6(1)(b) GDPR) for issuance, delivery and pickup; legitimate interest (Art. 6(1)(f) GDPR) in abuse prevention, rate limits and the block after a refund.
Activating ConsoleMouse
On Windows, Mac and Linux the app checks the licence key offline. It sends no data when you activate it, neither to us nor to anyone else. The key is stored only locally in the app on your device.
When you enter the licence key on your Raspberry Pi's local setup page, the Pi sends to the licence server:
- the licence key,
- a public device key that the Pi generates itself at first start,
- a device identifier value: a hash of the Pi board's serial number and the operating system's machine ID. The serial number itself never leaves the Pi; it cannot be recovered from the hash, but the same Pi always produces the same value,
- for a device change, the indication that the previous device is to be replaced,
- a response signed by the Pi to a one-time server challenge (nonce, valid for 60 seconds).
Per licence, the licence server stores the currently bound device identifier value and device key, the time of activation and the times of device changes in the last 365 days (at most three). It answers with a signed activation receipt that the Pi stores locally in a protected directory. The licence server receives nothing about your console, your PSN or Microsoft account, pairing data, inputs or game pictures. Activation uses no cookies and no analytics services.
Your Pi stores locally: the private device key, the activation receipt and the machine ID. The licence key itself is not stored permanently on the Pi. These files do not belong in a support export; do not send them to us.
Legal bases: performance of the contract (Art. 6(1)(b) GDPR); legitimate interest (Art. 6(1)(f) GDPR) in limiting use to one device and three changes per 365 days to make sharing harder.
Confirmation e-mail
After the purchase we send you an e-mail with the contract confirmation, the withdrawal notice and the licence key or pickup instructions. For this we use an e-mail service as processor. The service processes your e-mail address, subject, content and delivery information. We keep the delivery data in the licence server for at most 24 hours (see above); the e-mail service keeps delivery logs under its own periods. Legal basis: performance of the contract and the legal duty to confirm the contract (Art. 6(1)(b) and (c) GDPR, § 7(3) FAGG).
Support and withdrawal
If you write to [email protected], we process your message, your e-mail address and the details you give for identification (purchase date, e-mail address used at Stripe, Pi model, support code). The legal basis is Art. 6(1)(b) GDPR. We keep support messages only as long as needed to handle your request and as statutory retention duties require. The [email protected] mailbox is forwarded to a mailbox of the controller (see the general privacy notice).
Retention at a glance
- Stripe Checkout Session without payment: closed by Stripe after 24 hours.
- Encrypted key held for pickup: at most 7 days after purchase.
- Delivery data for the confirmation e-mail: at most 24 hours after purchase.
- Licence, device binding, device changes: as long as the licence exists; change timestamps 365 days.
- Block record after refund/chargeback: permanent, as long as the licence exists.
- Purchase, invoice and tax records (Stripe and our bookkeeping): 7 years (§ 132 BAO).
- Hash of the IP address for rate limits: briefly.
- Support messages: as long as needed for your request and as statutory retention duties require.
Recipients and third countries
Recipients are Stripe (Ireland, USA), Cloudflare (USA/EU) and the e-mail service. Transfers to the USA rely on the EU-US Data Privacy Framework where the recipient is certified, otherwise on standard contractual clauses.
Your rights
Subject to the law, you have the right to access, rectification, erasure, restriction, data portability and to object to processing based on legitimate interest. Write to [email protected] or . You can complain to the Austrian Data Protection Authority (dsb.gv.at) or the supervisory authority where you live. We cannot delete purchase and invoice data before the statutory retention periods expire. Providing a billing address and an e-mail address is required for the purchase; without them Stripe cannot complete the payment and we cannot deliver the key.