Your privacy matters. Kepler is designed to collect as little data as possible. By default, your app usage stays on your device.
1. Who we are
Kepler is developed and operated by Leonhard Breuer, Germany. Contact: [email protected].
2. Data we collect
Early access requests
When you request early access, we collect your email address to notify you when access is available. We do not sell it.
License and customer data
When you buy or activate Kepler, our license server processes your email address, customer name if provided, license status, product entitlements, expiry or trial status, and activation limit. License keys are stored as cryptographic hashes. A plaintext key may be included in the one-time response or email that delivers it to you.
Device activation and check-ins
Kepler sends a hardware identifier and may send the device hostname to recognize the device, enforce activation limits, prevent repeated trials, and let you manage activations. The server stores an HMAC-protected digest of the hardware identifier rather than the raw value. It also stores an activation identifier and activation, last-seen, deactivation, and optional deactivation-reason timestamps or details.
License check-ins can include the Kepler version and build, platform, processor architecture, and operating system version. The server keeps the current device state and, when a version is provided, a short-lived check-in record. Daily version-adoption reports contain only the product, date, version, and device count. They do not contain a license, hardware identifier, hostname, or customer identifier.
Update checks
Update requests can include the current version and build, update channel, platform, processor architecture, and operating system version. We use this information to select an update, operate staged rollouts, diagnose update problems, and understand version adoption. A stable client identifier may be used to decide whether a device is included in a staged rollout, but our application does not store that identifier in its update-check records.
Self-service license access
If you request a passwordless link to view or manage your license, the server processes your email address, a hashed temporary token, its creation and use times, your IP address, and your browser's User-Agent. Actions such as revoking an activation or replacing a license update the related license records and may generate an email containing a replacement key.
App usage
Kepler does not send your search queries, launch history, plugin usage, or other local app activity to our servers. This data stays on your device.
Website and service logs
Our website, license service, and infrastructure providers may record the IP address, browser or User-Agent, referrer, request path, status, date, and time of access for security, abuse prevention, debugging, and operation. These logs are not used for advertising or profiling.
3. Cookies
This website does not use tracking cookies or third-party analytics. Passwordless license access uses a necessary session cookie with a one-hour lifetime. It is cleared when you log out.
4. Legal basis
Processing your email address for early access is based on your consent (Art. 6(1)(a) GDPR). You may withdraw consent at any time by emailing us.
We process license, activation, check-in, update, and self-service data to provide Kepler and manage your license (Art. 6(1)(b) GDPR). We process security and service logs based on our legitimate interest in operating and protecting the website and license service (Art. 6(1)(f) GDPR).
5. Your rights
Under GDPR, you have the right to:
- Access the personal data we hold about you
- Request correction or deletion of your data
- Object to or restrict processing
- Data portability
- Lodge a complaint with a supervisory authority
To exercise any of these rights, contact us at [email protected].
6. Data retention
Early access email addresses are deleted within 30 days of the public launch or upon request. Raw client check-ins are normally deleted after 7 days, and update-check records after 90 days. Temporary self-service access records are deleted one day after expiry or use. The self-service email message expires after 15 minutes.
License, customer, device, activation, and aggregated version-adoption records do not expire automatically. They are retained while needed to provide and support your license, prevent abuse, meet legal obligations, or resolve disputes, then deleted or anonymized. We do not currently maintain database backups. Service logs are deleted after 30 days.
7. Service providers and data transfers
We operate the license server ourselves and do not send license data to an independent licensing provider. Our server is hosted by netcup GmbH, Daimlerstraße 25, 76185 Karlsruhe, Germany. netcup may process the connection and service-log data described above to provide and secure the hosting service.
We use Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA, as a DNS proxy and security provider. Requests to our website and services pass through Cloudflare, which may process IP addresses, request metadata, and security data to route traffic and protect the services from abuse. Processing may occur outside the European Economic Area. Where required, transfers are protected by an applicable legal transfer mechanism, such as the EU Standard Contractual Clauses.
Resend processes recipient addresses, message contents, and delivery metadata to send transactional email on our behalf. Update-file hosting providers may also process request data and keep separate security or access logs. Where data is transferred outside the European Economic Area, we use an applicable transfer mechanism and safeguards required by law.
8. Changes to this policy
We may update this policy. Changes will be posted on this page with an updated date.