← Back to homepage

Privacy Policy

1. Privacy at a glance

General information

The following notes provide a simple overview of what happens to your personal data when you visit this website. Personal data is any data that can be used to personally identify you.

2. Responsible party

Stefan Laszczyk
Heinrich-Wieland-Allee 33
75177 Pforzheim
Germany
Email: info@plurikey.app

3. Data collection on this website

Server log files

The provider of these pages automatically collects and stores information in so-called server log files, which your browser automatically transmits to us. These are:

This data is not merged with other data sources. The collection of this data is based on Art. 6 (1) lit. f GDPR.

Cookies

This website does not use tracking cookies or analytics tools. No cookies are set for advertising purposes.

4. PluriKey Software

Local data storage

PluriKey stores all passwords and sensitive data exclusively locally on your device. No data is transmitted to our servers unless you explicitly enable a sync feature.

No telemetry

PluriKey does not collect usage data, telemetry, or analytics data. The software works completely offline.

Browser Extension

The PluriKey browser extension communicates exclusively with the locally installed PluriKey server on your device. No data is sent to external servers.

Open Source transparency

The entire source code is publicly viewable and auditable. You can verify at any time what data the software processes: https://github.com/PluriKey/plurikey/a>

5. Your rights

You have the right to receive free information about your stored personal data, its origin and recipients, and the purpose of data processing at any time, as well as the right to rectify or delete this data. You can contact us at any time regarding this and other questions about data protection.

Right to lodge a complaint

You have the right to lodge a complaint with a data protection supervisory authority about the processing of your personal data.

6. SSL encryption

This site uses SSL encryption for security reasons. You can recognize an encrypted connection by the fact that the address line of the browser changes from “http://” to “https://”.