About Kardix

Last updated: June 17, 2026

Operator

Savvas Katsikas

I am the independent creator and operator of Kardix. I live in Rommerskirchen, Germany, and I built this project to explore a simpler question: can people create strong, unique account logins without placing every password into another online vault?

Rommerskirchen, North Rhine-Westphalia, Germany

Why I built Kardix

I started Kardix because password advice often leaves ordinary users choosing between two uncomfortable options. They can reuse memorable passwords, which is dangerous, or they can place hundreds of logins into a password manager and trust its storage, synchronization, recovery, and browser integration. Established password managers can be excellent tools, but I wanted to study a different model—one in which the login is recreated from information the user knows instead of retrieved from a stored Kardix vault.

The motivation was not to claim that every password manager is unsafe or that repeatable generation solves every security problem. It was to make the trade-off visible. Removing a hosted vault reduces one target, but it also removes recovery and shifts more responsibility to the user. Kardix therefore combines the working generator with detailed explanations about private phrases, labels, Argon2id, phishing, device trust, recovery planning, passkeys, and two-factor authentication.

Who runs and writes the site

Kardix is not a large company, anonymous content network, or automatically generated comparison portal. I, Savvas Katsikas, maintain the product pages, write and review the editorial material, test the browser generator, and make decisions about what the site should and should not promise. Article bylines identify me as the author so readers can connect the advice to a responsible person rather than an unnamed “editorial team.”

The initials image on this page is an avatar rather than a photographic portrait. It is used consistently so visitors can identify the operator without suggesting that Kardix has a larger staff than it does. The project’s location is Rommerskirchen in North Rhine-Westphalia, Germany. Legal and contact details are also available on the Imprint and Contact pages.

What Kardix does

Kardix creates passwords in your browser. You type one private phrase, a website name, and an optional PIN. When you type the same details again, Kardix creates the same password again. That means you can have different passwords for different websites without asking Kardix to save them for you.

Kardix does not create an account for the generator and does not keep your password list. That is useful, but it also means Kardix cannot recover your private phrase if you forget it. The site explains these limits clearly so normal users can decide if the tool fits them.

Editorial principles

The learning library is written for people who want enough context to make a decision, not just a slogan. Articles aim to distinguish architecture from marketing, explain where uncertainty exists, and avoid presenting one authentication method as universally best. A traditional password manager, a password tool without a saved list, passkeys, and hardware-backed two-factor authentication each solve different problems. Many people will reasonably combine them.

I update articles when the project changes or when guidance needs clarification. Each article displays its original publication date and its latest update date. Content is not published merely to create large numbers of search pages. The site keeps a limited collection of focused guides, and older or overlapping paths are redirected to the strongest relevant page instead of being left as thin duplicates.

Funding and advertising

Kardix may use Google AdSense to help cover hosting, development, and the time required to maintain original educational content. Advertising does not determine the generator’s outputs or the conclusions in comparison articles. Ad placements are visually identified, and the Privacy Policy explains cookies, consent choices, personalized and non-personalized advertising, and how visitors can change their preferences.

Visitors in the European Economic Area, the United Kingdom, and Switzerland should be shown a consent mechanism before advertising technology is loaded. The website code blocks the AdSense script until a choice is made. In addition, the live AdSense account must have Google’s certified Privacy & messaging consent solution enabled before ads are served in those regions.

Contact

Questions, corrections, security observations, and accessibility feedback are welcome. The fastest way to reach me is by email at maotaw17@gmail.com. You can also visit the Contact page for the address, expected response scope, and guidance on reporting a sensitive issue. Please do not include passwords, private phrases, PINs, recovery codes, or other private logins in a message.