Certificate Verification Policy

1. Introduction

This Certificate Verification Policy explains HackerHub8's processes and rules for issuing, storing and verifying credentials (certificates, IDs, volunteer badges, team IDs and agreements). The policy helps employers, institutions and participants confirm authenticity and prevents misuse or forgery.

2. Purpose

The verification system exists to:

• Confirm the authenticity of HackerHub8-issued credentials.
• Prevent forged, altered, or duplicated certificates from being used.
• Provide a fast, auditable verification path for employers and institutions.
• Protect the value and credibility of HackerHub8 credentials.

3. Scope

This policy applies to all credentials issued by HackerHub8, including (but not limited to) the types listed below. Only credentials that match the listed ID formats are accepted for verification in our portal or via offline requests.

4. Verification Process (Portal)

To verify a credential online, use our Certificate Verification Portal:

1. Visit: https://hackerhub8.in/check-certificate.
2. Enter the exact Certificate/ID string printed on the credential (copy-paste recommended).
3. Submit the form to retrieve verification results.
4. Valid results will display: Holder name, Credential type, Course/Event name, Issue date, Validity/Status, and Verification ID.

5. Offline / Third-Party Verification Requests

Employers or institutions may request verification by email or by submitting a scanned copy. Requirements for offline verification:

• Provide the full Certificate/ID (exact string) and a scanned image of the credential if available.
• Send requests to hr@hackerhub8.in from an official company/institutional email address when possible.
• Include the certificate holder’s written consent when the request involves personal data.
• Allow up to 5–7 business days for offline verification processing.

6. Data Accuracy & Holder Responsibility

Information shown during verification reflects the details supplied by the participant at the time of issuance. HackerHub8 is not responsible for typos or incorrect data submitted by the holder. If an error is found, the certificate holder should contact support to request correction.

7. Retention & Availability

We retain digital records of issued credentials for at least 5 years from the issue date. Credentials older than this period may not be available for verification unless required by law or specific contractual arrangements.

8. Misuse, Fraud & Consequences

Attempts to forge, alter, duplicate or otherwise misuse credentials are strictly prohibited. Consequences include:

• Immediate invalidation of the credential.
• Permanent ban from HackerHub8 programs and community channels.
• Possible legal action under applicable laws (civil and criminal) where warranted.

9. Limitations of Verification

Verification confirms the authenticity of an issued credential only. It does not certify current skill level, employment status, or future competence. Employers should use verification as part of a broader evaluation process.

10. Amendments to This Policy

HackerHub8 may update this policy occasionally. Updated versions will be published on this page with a revised "Effective Date." Continued reliance on verification after changes implies acceptance.

11. Contact & Support

For verification help, corrections, or offline requests contact:

Report suspected misuse or fraudulent credentials to support@hackerhub8.in. Provide as much detail as possible (copy of the credential, certificate ID, context of use).

HackerHub8 Security & Verification Team