Contact Kardix
Reach the independent operator for questions, corrections, and responsible security reports.
Last updated: June 17, 2026
Kardix is operated by Savvas Katsikas from Rommerskirchen, North Rhine-Westphalia, Germany. This page provides a direct, working contact method rather than an automated support portal.
General contact
Use this address for corrections, partnership questions, accessibility feedback, or questions about the public website.
Project location
Rommerskirchen
North Rhine-Westphalia
Germany
Additional legal details are available in the Imprint.
Safe use reports
If you believe you found a vulnerability in Kardix, describe the affected page, browser, reproducible steps, and the impact you observed. Please use a test phrase created only for the report. Never email a real password, root private phrase, PIN, recovery code, session token, or login generated for an active account.
Kardix is a small independent project, so there is no guaranteed response time or paid bug-bounty program. Good-faith reports that avoid privacy violations, service disruption, and access to other people’s data are appreciated and will be reviewed as reasonably possible.
Article corrections
Safe use guidance changes, and wording can always be improved. When reporting an article problem, include the page address, the sentence or claim in question, and a reliable source that supports the correction. Substantive corrections may be reflected in the article’s visible update date.
What not to send
- Passwords, private phrases, PINs, recovery codes, or private keys.
- Personal information belonging to another person.
- Malware, destructive proof-of-concept code, or unsolicited executable attachments.
- Requests to recover a Kardix private phrase. Kardix does not store private generator inputs and cannot recover them.
Privacy of correspondence
Email necessarily sends information through the providers involved in delivery and hosting. Messages are used to answer the request, maintain a reasonable record of support or legal communication, and protect the project from abuse. More detail is available in the Privacy Policy.