Privacy Policy and Terms of Service

Effective Date: January 1, 2025  |  Last Updated: October 10, 2026

Table of Contents

  1. Security Engineering
  2. Privacy Policy
  3. Terms of Service

Security Engineering

We believe that security must not depend on secrecy. We share our security controls openly. This helps us to act before problems occur.

Our Security Controls

The table below shows some of our security controls.

Class Description Purpose Relevant CWE
Architecture, Storage, and Operating System Hardening The application stores data in flat files on GNU/Linux. The application runs as a dedicated user that is not the root user. POSIX file permissions and file ownership control access. The application has no relational database and no SQL layer. This design removes the SQL injection attack surface, because the application has no SQL queries and no database drivers. It also reduces the number of dependencies. The principle of least privilege limits the impact of an attack. CWE-89 (SQL Injection)
Architecture, Storage, and Operating System Hardening The application creates files with permissions that only the service account can use. The service account is not the root user. Only this account and the root user can read the files. This prevents other users and other processes on the host from reading sensitive data. CWE-552 (Files or Directories Accessible to External Parties)
CWE-276 (Incorrect Default Permissions)
Architecture, Storage, and Operating System Hardening The application does not use user input to control file paths. The application calculates file locations internally. Where necessary, it uses only constrained identifiers, for example the username. This prevents an attacker from selecting any file or directory with crafted input. CWE-22 (Path Traversal)
CWE-73 (External Control of File Name or Path)
Container and Runtime Reduction The application runs in Docker as a user that is not root. It uses a multi-stage build. The final runtime image does not contain build tools or extra dependencies. This limits what an attacker can do after the attacker gets a shell or runs code. The image has fewer tools and libraries. This reduces the attack surface. CWE-250 (Execution with Unnecessary Privileges)
CWE-269 (Improper Privilege Management)
Container and Runtime Reduction The container uses Tini as PID 1. Tini handles signals correctly and removes finished child processes. This improves process management. It reduces rare cases of instability that can cause availability problems. N/A
Input Validation and Injection Resistance The application limits user fields to mostly alphanumeric characters. This limit does not apply to passwords. The application validates these fields strictly. This reduces the range of possible input. It blocks the metacharacters that injection attacks commonly use. The needed functions stay available. CWE-20 (Improper Input Validation)
Authentication, Authorization, and Session Management Middleware enforces authorization in the same way on all endpoints. The middleware checks the identity and the claims of an RSA-signed (RS256) JWT. These checks include the role and the uid. This prevents privilege escalation. It also prevents access to the resources of other users. The application applies the authorization rules from one central place, in the same way for all requests. CWE-285 (Improper Authorization)
CWE-863 (Incorrect Authorization)
Authentication, Authorization, and Session Management The application validates JWT claims. This includes the standard time claims iat and exp. The application logs unusual events. Examples are a missing claim, an invalid signing method, a role mismatch, a uid mismatch, and an invalid Content-Type. It also logs other signs of probing or abuse. This prevents common JWT validation errors, for example algorithm confusion. It also improves how we detect and assess authentication attacks, request smuggling, and probing patterns. CWE-347 (Improper Verification of Cryptographic Signature)
CWE-778 (Insufficient Logging)
CWE-223 (Omission of Security-relevant Information)
Authentication, Authorization, and Session Management The application issues JWTs with a configurable expiration time (TTL). The default is 30 days. This makes sure that a token expires. A token does not stay valid for an unlimited time. This limits the time in which someone can misuse a compromised token. CWE-613 (Insufficient Session Expiration)
Authentication, Authorization, and Session Management The application has a sign out function. It uses a jti claim to support token revocation. When you sign out, the application adds the jti of your token to a revocation list. The application saves this list to disk. It checks the list on every authenticated request. The application refuses a revoked token, even before the token expires. A user can end a session immediately. A token that someone copied or leaked has limited use after the user signs out. CWE-613 (Insufficient Session Expiration)
Authentication, Authorization, and Session Management The application supports multi-factor authentication (MFA) with passkeys and hardware security keys (WebAuthn). If an account has at least one registered credential, a correct password gives only an intermediate token that lasts 5 minutes. The application issues a session only after a successful WebAuthn assertion. The intermediate token carries a purpose claim. The session validator rejects this token, so no one can use it as a session token. Users can also use passkeys for passwordless sign-in with required user verification. This protects against password theft, phishing, and credential stuffing. It requires that the user has a cryptographic authenticator. The authenticator works only with the domain of the site. CWE-308 (Use of Single-factor Authentication)
CWE-287 (Improper Authentication)
CWE-294 (Authentication Bypass by Capture-replay)
Authentication, Authorization, and Session Management The application stores only the public key, signature counter, label, and timestamps of each passkey or security key. It never stores a private key. Each challenge is single-use and short-lived, and the application keeps it only in memory. The application rejects authenticators that give a clone warning. An account can have at most ten credentials. To remove a credential or to regenerate recovery codes, the user must enter the account password again. This limits the impact if an attacker gets access to the database or the files. It prevents replay of authentication ceremonies. It also stops an attacker with a hijacked session from removing the second factor in secret. CWE-256 (Unprotected Storage of Credentials)
CWE-620 (Unverified Password Change)
CWE-294 (Authentication Bypass by Capture-replay)
Authentication, Authorization, and Session Management The application gives each account a set of single-use recovery codes at registration, and the user can regenerate them. The application stores the codes only as SHA-256 hashes. It compares the codes in constant time. It invalidates a code after use. A failed password reset returns one generic message, to prevent account enumeration. Sensitive account actions, for example a change to the security settings, need the account password again. This adds a strong secret for each account to protect high-impact operations. It reduces the risk that someone changes a password without permission through a compromised session. CWE-620 (Unverified Password Change)
Authentication, Authorization, and Session Management The main API authentication uses the Authorization header. The application can also use cookie authentication (auth_token), with Secure=true and SameSite=Strict. An API request that changes state must also carry an X-Requested-With header. This reduces the CSRF exposure of the cookie mode. It makes sure that the browser sends cookies only over HTTPS. Header-based authentication stays the default, to reduce the CSRF risk in typical API use. CWE-352 (Cross-Site Request Forgery)
CWE-614 (Sensitive Cookie in HTTPS Session Without 'Secure' Attribute)
Authentication, Authorization, and Session Management Each account has a strong secret that the application generates automatically. The application uses this secret as an account security token for sensitive actions, for example a password change. The application generates a new secret at registration and at reset. This adds a strong secret to protect high-impact operations. It reduces the risk of unauthorized password changes. It also reduces the risk of some account takeover methods. CWE-620 (Unverified Password Change)
Password Storage and Credential Hardening The application hashes passwords with bcrypt at cost factor 13. It prehashes each password with SHA-512. It also uses a hidden pepper that it stores outside the application. The scheme uses an HMAC construction. This makes offline cracking much harder. The pepper makes stolen hashes much less useful without the external secret. CWE-916 (Use of Password Hash With Insufficient Computational Effort)
CWE-256 (Unprotected Storage of Credentials)
Password Storage and Credential Hardening A password must be 16 to 128 characters long. It must also meet strong complexity requirements. This increases password entropy. It reduces the success of guessing and credential stuffing. It also makes passwords stronger against an offline attack on the hashes. CWE-521 (Weak Password Requirements)
Abuse Prevention, Availability, and Performance Custom Go middleware limits the rate of requests. This detects and restricts API abuse. The rate limits cover authentication attempts and request patterns similar to DoS. This makes brute force attacks less feasible. It also limits resource exhaustion from abusive clients. CWE-307 (Improper Restriction of Excessive Authentication Attempts)
CWE-400 (Uncontrolled Resource Consumption)
Abuse Prevention, Availability, and Performance The application keeps its data models small. This avoids costly server-side operations and long load times. This improves availability. It also reduces accidental amplification factors that an attacker can abuse for DoS. CWE-400 (Uncontrolled Resource Consumption)
Abuse Prevention, Availability, and Performance Semaphore-based middleware limits the concurrency of endpoints that use much bandwidth, for example file downloads. It enforces a global concurrency ceiling. It also enforces a separate concurrency limit for each IP address. This prevents one client from taking all resources from other users. It also protects the server from overload during peak download activity. CWE-400 (Uncontrolled Resource Consumption)
CWE-770 (Allocation of Resources Without Limits or Throttling)
Abuse Prevention, Availability, and Performance Middleware sets a global limit on the size of a request body. The middleware rejects an oversized payload before it reads the whole payload. This prevents memory exhaustion and DoS from large request bodies. CWE-400 (Uncontrolled Resource Consumption)
Browser-Side Protections The application uses CSP to restrict the sources and the types of executable content. This reduces the impact of XSS. It limits the ways in which scripts can run, even if an injection occurs. CWE-79 (Cross-Site Scripting)
Browser-Side Protections The client applies output encoding and escaping. It does this in the few areas where the page shows data that users can influence. This prevents the browser from reading an injected string as HTML or JavaScript. It reduces the probability of XSS. CWE-79 (Cross-Site Scripting)
Browser-Side Protections The frontend is custom HTML and JavaScript. It does not interact with external APIs. The only third-party dependency is a chart library. This reduces the supply-chain risk. It also reduces exposure to compromised third-party scripts and services. The overall dependency attack surface is smaller. CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)
Transport Security The application uses HTTPS with a valid, publicly trusted TLS certificate. This protects sensitive data in transit, for example credentials and tokens. It also reduces the MITM risk. CWE-319 (Cleartext Transmission of Sensitive Information)
Transport Security Middleware validates the HTTP Host header against a strict allowlist. The middleware rejects a request when the Host value is unknown or empty. This prevents host header injection, DNS rebinding, and cache-poisoning attacks. These attacks depend on a manipulated Host header. CWE-444 (Inconsistent Interpretation of HTTP Requests)
Transport Security The application accepts POST and PUT requests only with the Content-Types application/json and multipart/form-data. It rejects all other types with the status 415 Unsupported Media Type. This limits the request surface to expected formats. It reduces the risk of content-type confusion and parser-differential attacks. CWE-20 (Improper Input Validation)
Operational and External Controls We register likely typosquatted domains and alternate TLDs. This reduces domain impersonation. This reduces the risk of phishing and brand impersonation. These can lead to credential theft. N/A

Privacy Policy

This Privacy Policy explains how Hashcracky, LLC ("we", "our", or "us") collects, uses, discloses, and protects information. It applies when you visit or use our website and related services. In this policy, the "Service" means our website and our related services. When you use the Service, you consent to the data practices that this policy describes.

1. Information We Collect

We designed Hashcracky to collect a minimum of data. The Service has no function to collect personal identifiers. Personal identifiers include names, email addresses, postal addresses, and telephone numbers. The Service collects the limited data below automatically when you use it:

Note: Some privacy regulations, including the GDPR Article 6(1)(f), can treat IP addresses as personal data. We process IP addresses on the basis of our legitimate interest to maintain the security and integrity of the Service.

2. Cookies and Local Storage

The table below shows the browser storage that the Service uses. The Service uses it only for essential functions. We do not use tracking cookies, advertising cookies, or third-party analytics services.

KeyTypePurposeRetention
auth_token Cookie (essential) Keeps the state of your signed-in session Until you sign out or the token expires. When you sign out, the server also revokes the session token.
hcky.recovery Session Storage Passes new recovery codes to the confirmation page. The page shows the codes one time. The Service clears it immediately after the page shows the codes.

The Service needs these storage mechanisms to work correctly. If you disable cookies or local storage, you cannot access the Service features that require authentication.

3. How We Use Information

We use the information that we collect only for these purposes:

We process this information on three legal bases. The first is your consent when you create an account and use the Service. The second is our legitimate interest to provide and to secure the Service. The third is compliance with legal obligations, where applicable.

4. Disclosure to Third Parties

We do not sell, rent, or share your information with third parties for their marketing purposes. We can disclose information only in these cases:

5. International Data Transfers

DigitalOcean, LLC operates the servers that store and process all data. These servers are in the United States. When you use the Service from outside the United States, you acknowledge and consent to the transfer of your information to the United States. The United States can have data protection laws that are different from the laws of your jurisdiction.

6. Security

We use appropriate technical and organizational measures to protect the security of information that the Service processes. These measures include encryption in transit, strong password hashing, and regular security assessments. They also include optional multi-factor authentication with passkeys and security keys, single-use recovery codes, and session revocation when you sign out. You can enable multi-factor authentication in your account settings. We publish the details of our controls in the Security Engineering section above. No method of electronic transmission or storage is 100% secure, and we cannot guarantee absolute security.

7. Data Breach Notification

If a data breach can compromise user account security, we will post a prominent notice on our website and social media channels. We do not collect email addresses, so public notification is our primary means of communication. If the law requires it, we will also notify the relevant regulatory authorities within the legal time limits.

8. Data Retention

We keep information for the periods below:

9. Your Rights

You have these rights about your information:

To exercise a right that the Service interface does not offer, contact us at contact@hashcracky.com. Use the same address for questions about this policy. We will respond to requests within 30 days.

Residents of the European Economic Area (EEA), the United Kingdom, and some other jurisdictions have additional rights under applicable data protection laws.

10. Children's Privacy

The Service is not intended for individuals under the age of 13. We do not knowingly collect personal information from children under 13. If we learn that we collected personal information from a child under 13, we will take steps to delete it quickly. If you believe that we collected information from a child under 13, contact us immediately.

11. Sensitive Data

We do not intentionally collect sensitive personal data, also known as special categories of personal data. This data includes information about racial or ethnic origin, political opinions, religious or philosophical beliefs, and trade union membership. It also includes genetic data, biometric data, health data, and data about sex life or sexual orientation. The Service has no mechanism to submit this information. If your passkey or security key uses biometrics, for example a fingerprint or a face scan, the verification happens locally on your device. We receive only a cryptographic signature and never any biometric data.

12. Automated Decision-Making

The Service uses automated decision-making only to prevent abuse. This includes IP-based rate limits. These limits can temporarily restrict access when the Service detects suspicious patterns. The Service does not perform user profiling. The Service also does not perform automated decision-making that produces legal effects or similarly significant effects.

13. "Do Not Track" Signals

The Service does not track users across third-party websites. For this reason, the Service does not respond to Do Not Track (DNT) browser signals or similar mechanisms. We limit our data collection to your direct interactions with our Service.

14. Changes to This Policy

We have the right to update this Privacy Policy at any time. A change is effective immediately when we post it to the Service. We will highlight material changes in a notice on our website. If you continue to use the Service after a change, you accept the updated policy.

15. Contact Us

For questions, concerns, or requests about this Privacy Policy or our data practices, contact us at:

Email: contact@hashcracky.com

Terms of Service

These Terms of Service ("Terms") are a legally binding agreement between you and Hashcracky, LLC ("we", "our", or "us"). The agreement governs your use of the Hashcracky website and services (the "Service"). When you access or use the Service, you agree that these Terms bind you. If you do not agree to these Terms, you must not access or use the Service.

1. Use of Service

1.1 Eligibility. You must be at least 13 years old to use the Service. When you use the Service, you represent and warrant that you meet this age requirement.

1.2 Acceptable Use. You agree to use the Service only for lawful purposes and as these Terms allow. You agree not to do the following:

2. Account Responsibility

2.1 Account Security. You are responsible for keeping your account credentials confidential. You are also responsible for all activities that occur under your account. You agree to notify us immediately of any unauthorized use of your account or any other breach of security.

2.2 Accuracy of Information. You agree to give accurate and complete information when you create your account. You also agree to keep this information current.

3. Rate Limits and Abuse Prevention

To protect the integrity and availability of the Service, we use automated rate limits and measures to prevent abuse. A violation of these limits can result in temporary or permanent suspension of your access to the Service. This applies to intentional and to unintentional violations. We have the right to change these limits at any time without notice.

4. Termination

4.1 Termination by You. You can terminate your account at any time with the account deletion feature in the Service.

4.2 Termination by Us. We have the right to suspend or terminate your access to the Service, with or without notice, for any reason. Reasons include, but are not limited to, the following:

4.3 Effect of Termination. After termination, your right to use the Service ends immediately. Provisions of these Terms that must continue after termination because of their nature stay in effect. These provisions include, but are not limited to, ownership provisions, warranty disclaimers, indemnity, and limitations of liability.

5. No Guarantee of Service

WE PROVIDE THE SERVICE "AS IS" AND "AS AVAILABLE". WE GIVE NO WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. THIS INCLUDES, BUT IS NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR COURSE OF PERFORMANCE. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, SECURE, OR FREE OF OTHER HARMFUL COMPONENTS.

6. Intellectual Property

6.1 Our Rights. We, our licensors, or other providers own the Service and all content, features, and functions of the Service. This includes, but is not limited to, information, software, text, displays, images, and graphics. It also includes the design, selection, and arrangement of these items. United States laws and international laws protect the Service. These include copyright, trademark, patent, trade secret, and other intellectual property laws.

7. Randomness of Service

Some features of the Service contain random or pseudo-random elements. We make no representations or warranties about the randomness, fairness, or predictability of these features. Results can vary. We do not guarantee that results meet any particular expectation or standard.

8. Fictional Content

All challenges, scenarios, and data in the Service are fictional. We created them only for entertainment and educational purposes. Any resemblance to real persons, organizations, or actual data is coincidental.

9. Limitation of Liability

TO THE MAXIMUM EXTENT THAT APPLICABLE LAW ALLOWS, WE ARE NOT LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES. THE SAME APPLIES TO OUR AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, SUPPLIERS, AND LICENSORS. THESE DAMAGES INCLUDE, BUT ARE NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS, GOODWILL, USE, DATA, OR OTHER INTANGIBLE LOSSES. THESE LIMITS APPLY TO ALL DAMAGES THAT ARISE FROM OR RELATE TO YOUR USE OF THE SERVICE OR YOUR INABILITY TO USE IT. THE LIMITS APPLY EVEN IF SOMEONE TOLD US OF THE POSSIBILITY OF THESE DAMAGES.

OUR TOTAL LIABILITY TO YOU IS LIMITED TO THE AMOUNT THAT YOU PAID US. THIS AMOUNT COVERS ONLY THE TWELVE (12) MONTHS BEFORE THE EVENT THAT CAUSED THE LIABILITY. THIS LIMIT APPLIES TO ALL DAMAGES THAT ARISE FROM OR RELATE TO THESE TERMS OR THE SERVICE. IF YOU DID NOT PAY US ANY AMOUNT, OUR SOLE LIABILITY IS LIMITED TO THE DISCONTINUATION OF YOUR ACCESS TO THE SERVICE.

SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF SOME WARRANTIES OR OF LIABILITY. IN THESE JURISDICTIONS, OUR LIABILITY IS LIMITED TO THE GREATEST EXTENT THAT THE LAW ALLOWS.

10. Applicable Law

The laws of the State of Delaware, United States, govern these Terms and apply to their interpretation. These laws apply without regard to their conflict of law provisions. You agree to submit to the personal and exclusive jurisdiction of the courts in Delaware.

11. Dispute Resolution

11.1 Informal Resolution. We encourage you to contact us at contact@hashcracky.com if you have a concern or a dispute about the Service. We will make reasonable efforts to resolve any dispute informally.

11.2 Binding Arbitration. For any dispute that you cannot resolve informally, you and Hashcracky agree to the following. The parties must resolve any dispute that arises out of or relates to these Terms or the Service through binding individual arbitration. The arbitration follows the Streamlined Arbitration Rules and Procedures of JAMS ("JAMS Rules"), except as these Terms change them. The arbitration takes place by telephone, online, or only through written submissions, unless the parties agree otherwise. The decision of the arbitrator is final and binding.

11.3 Class Action Waiver. YOU AND HASHCRACKY AGREE THAT EACH PARTY CAN BRING CLAIMS AGAINST THE OTHER PARTY ONLY IN AN INDIVIDUAL CAPACITY. NEITHER PARTY CAN BRING CLAIMS AS A CLASS REPRESENTATIVE OR AS A CLASS MEMBER. Neither you nor we will seek class treatment for any dispute that is subject to arbitration.

11.4 Exceptions. Despite the above, either party can seek injunctive or other equitable relief to prevent actual or threatened infringement of intellectual property rights. The party can seek this relief in any court of competent jurisdiction. Either party can bring an action in small claims court without first trying arbitration.

12. Severability

A court or other authority can decide that a provision of these Terms is invalid, illegal, or unenforceable. In this case, the remaining provisions continue in full force and effect. A valid and enforceable provision replaces the invalid or unenforceable provision. This valid provision matches the intent of the original provision as closely as possible.

13. Changes to Terms

We have the right to change these Terms at any time at our sole discretion. If we make material changes, we will give notice through the Service. If you continue to use the Service after this notice, you accept the changed Terms. If you do not agree to the changed Terms, you must stop your use of the Service.

14. Contact

If you have any questions about these Terms of Service, contact us at:

Email: contact@hashcracky.com