PKZ CLIENT / LEGAL

Privacy Policy

Last updated: 16 October 2026

Who is responsible

Lean Speidel, Rosengartenstrasse 10, 9404 Rorschacherberg, Switzerland, operates PKZ Client. Contact [email protected] for privacy matters. Further contact details are in our Legal Notice.

What we use and why

We use your email address, account identifier, verification status and sign-in provider to create and protect your account. Google sign-in supplies basic profile information. Password authentication is handled by Firebase; PKZ does not store your password in its database. Hosting and authentication providers process connection information, including IP addresses and browser information, for delivery and security.

Licensing uses licence identifiers, key hashes, activation and expiry dates, a randomly generated device identifier and a public cryptographic key to enforce the one-device licence. The private device key stays on your computer. Older licence records may contain a Minecraft account identifier. Security records include hashed IP identifiers, challenges and administrative actions; hashing does not make these records anonymous.

Privacy requests store your account identifier, verified email, request type, reference, dates and status. Support emails contain the information you choose to send. Do not email passwords or complete payment-card details.

Live checkout is currently disabled. The separate test shop uses Stripe and stores order, customer and subscription references, email, amounts, currency, payment status and licence associations. Delivered keys are stored encrypted. Stripe handles payment details; PKZ does not store full card numbers. Account-linked purchase services are not yet enabled on this site.

Providers and transfers

Cloudflare provides hosting, Workers, databases and download infrastructure. Google provides Firebase Authentication, Google sign-in and verification/reset emails; Gmail receives support emails. Stripe provides checkout and subscription services when used. These providers also process data for their own security and legal obligations.

Firebase Authentication processes data in the United States. Cloudflare, Google and Stripe use international infrastructure, so data is not restricted to Switzerland or the EU. Their published terms describe safeguards such as applicable adequacy frameworks and standard contractual clauses. The full service-specific country and contractual assessment remains under review before worldwide sales.

Provider information: Cloudflare, Firebase, Google and Gmail, and Stripe. Contact us for information about the safeguards applicable to your data.

Cookies and browser storage

No advertising trackers or website analytics scripts are included in the current site build. Firebase authentication uses browser session storage to keep you signed in across reloads in the same session. Its SDK is loaded from Google when the site opens. Google sign-in and Stripe-hosted pages may use their own necessary authentication and security storage.

The test shop keeps a checkout reference in session storage. Its administrator cookie lasts two hours and is Secure, HttpOnly and SameSite=Strict. The main site's privacy-request API uses your Firebase sign-in token and sets no additional cookie. The separate customer purchase-session cookie is not enabled on this site.

Retention and closure

Account information remains until account closure is processed. Google states that authentication IP logs are kept for a few weeks and that other authentication data is removed from live and backup systems within 180 days after deletion is initiated. Provider backups and legally required records may therefore outlast account closure.

Expired challenges, sessions and rate-limit entries are eligible for cleanup. Hourly automatic cleanup is being tested separately; production licence cleanup is not yet enabled. Our approved retention targets are 30 days for technical security logs and 90 days for administrative logs and closed privacy requests, subject to a necessary legal hold. Those targets are not yet an automatic deletion guarantee across all providers. Active licences, unresolved requests and required transaction records are excluded.

Required Swiss accounting records are generally retained for ten years where the legal obligation applies. This does not justify retaining every account field for ten years. We review other records for deletion or anonymisation when they are no longer needed for service, support, security or legal claims.

Encrypted recovery backups can retain earlier records. Their rotation and deletion schedule remains under review.

Your choices and rights

Contact us for access, correction, deletion, account closure or other applicable rights. Depending on the applicable law, these include portability, restriction, objection and withdrawal of consent without affecting earlier lawful processing. We verify your identity before disclosing or changing account data. Signed-in users can submit a verified request and check its status in Account Settings; you can also email us if you cannot sign in.

A deletion request is not an immediate account deletion or subscription cancellation. We first agree how to handle active subscriptions and purchased licences, remove unnecessary account data and sessions, and retain only records still required. Fulfilment requires manual review; end-to-end automatic deletion is not available. We confirm what was removed and what must remain. You may complain to the Swiss Federal Data Protection and Information Commissioner or another competent supervisory authority.

Where the GDPR applies, account and licence processing serves contract performance, security serves legitimate interests in preventing abuse, and required recordkeeping serves legal obligations. Optional processing requiring consent will require it separately. Providing required account information is necessary to use sign-in features.