Конфиденциальность

1Without an account

A random identifier is placed in a cookie so your recent 2FA codes and tool settings come back when you return. The same identifier is mirrored in localStorage, and a coarse fingerprint (browser string, language, IP network) is stored so a device that lost its cookie can be matched again. No account, email or name is required or collected.

• 2FA history: kept 3 days, secrets encrypted with AES-256-GCM.
• Tool preferences: kept 180 days.
• Both are deleted automatically once they age out, and immediately if you clear them.

2With an account

We store your username, email address, a hash of your password (bcrypt), your settings, and whatever you choose to keep in the vault. Vault secrets are encrypted before they are written to the database. Deleting your account removes all of it.

3What you type into the tools

Each tool handles your input differently, so here is each case:

• The calculations (subnet, number bases, units, colour, time, cron, JWT, identifiers, QR) run entirely on this server and are sent nowhere.
• QR images are decoded inside your browser where the device supports it; only when it cannot are they sent to the server to decode, and they are not kept.
• What you type into the calculators is NOT written to the database. Only a per-tool usage counter is kept, with no content attached.

4Logs

Sign-ins, account changes and API calls are recorded with a timestamp, IP address and browser string so you and the administrator can spot misuse. Audit rows older than 90 days and API logs older than 30 days are removed during routine maintenance.

5Third parties

Some lookups have to go outside: geolocating an IP address, resolving DNS records, reading domain registration data, finding the manufacturer behind a MAC address, and fetching map tiles. When they do, the address or domain you looked up is sent to the relevant provider, without your own IP address and without any account identifier. Each capability has a backup, so a lookup may reach a second provider when the first does not answer. Individual provider names are not published here for operational security reasons, and are available from the operator on request.

The operator does not control the privacy practices of these services. An administrator can switch off IP geolocation and map tiles entirely in the settings page.

6Advertising

The site is funded by advertising, served by third-party ad networks. Those networks typically set cookies or identifiers in your browser to count impressions, cap how often you see the same ad, and detect fraud; they may use that data under their own policies, which the operator does not control. What you type into the tools is never passed to an advertiser. You can block third-party cookies in your browser or use an ad blocker; the tools keep working.

7How long data is kept

Anonymous 2FA history is kept for 3 days and tool preferences for 180 days, then deleted automatically. Login and API logs follow the operator’s configuration. Account data is kept until you delete the account; deleting it also removes your 2FA vault, password vault, API keys and all preferences.

8Your choices

• Clear the 2FA history with one click on the tool page.
• Delete cookies and site data to drop the anonymous identifier entirely.
• Export or delete your account data at any time from the security page.

9Limits of this policy

This text describes how the software behaves as written, not a legal commitment. Whoever runs the installation you are looking at may have changed the configuration, added their own analytics, or placed the site behind a proxy. If you do not run this server yourself, ask its operator before entering anything sensitive. See also the liability disclaimer in the Terms.

10Questions

Questions about these terms: [email protected].