Verification requests are purpose-limited. Provide only what the request asks for, use only the designated verification workflow, and never send account secrets or identity documents through ordinary support messages.
An Ackaia ID Verification Request is a secure, case-specific request used when Ackaia needs additional evidence before completing a sensitive action, confirming an account-related status, or disclosing protected information.
Verification is not required for ordinary use of Ackaia ID. It is used when the circumstances of a request make additional assurance appropriate.
A verification request may be created when Ackaia needs to establish that a person is authorized to make a sensitive request or qualifies for a particular status.
Examples include:
confirming that a privacy or data-access request is being made by the owner of the affected Ackaia ID;
verifying account ownership for a sensitive support or recovery case;
confirming student status;
confirming journalist or press status;
verifying eligibility for a program, entitlement, exception, or account action that requires additional evidence;
other identity or status checks specifically described in the verification request.
Ackaia's current policies already allow reasonable identity, security, fraud-prevention, and recovery checks, and privacy rights may be subject to appropriate verification.
A verification request tells you what Ackaia needs for that specific case. Depending on the purpose, you may be asked to complete one or both of the following:
MFA confirmation using the multifactor-authentication method associated with your Ackaia ID; and/or
document verification by providing a photo of an accepted document identified in the request.
Do not submit additional documents or sensitive information that the request does not ask for.
If the request requires MFA confirmation:
Open the Ackaia verification request presented for your case.
Review the reason for the verification and the checks required.
Complete the MFA confirmation inside the official Ackaia verification interface.
Continue to any remaining verification step shown for the request.
MFA confirmation proves access to a security factor already associated with the Ackaia ID.
Do not send an MFA code to an Ackaia employee through email or an ordinary support reply. When MFA confirmation is required, complete it only through the verification interface provided for the request.
If the request requires a document, it will specify which types of evidence are accepted for that case.
Depending on the purpose of the verification, accepted evidence may include:
a passport;
a government-issued photo identification document;
a driver's license;
another government identification card;
proof of current student enrollment;
a student credential where applicable;
a journalist or press credential;
another document specifically identified in the verification request.
Not every verification request accepts or requires the same document. Follow the requirements shown for your request rather than submitting an identity document by default.
When a document photo is required:
Use one of the document types accepted by the request.
Make sure the document is current where the request requires a current credential or status.
Take a clear photo with the required information visible.
Avoid glare, blur, heavy shadows, or cropping that prevents the required information from being reviewed.
Do not alter or obscure required fields unless the verification request expressly permits it.
Upload the image only through the Ackaia verification system.
Submit the verification after reviewing the information requested for the case.
If a request requires proof of a status rather than government identity—for example, current student enrollment or journalist status—submit the evidence specified for that status instead of unrelated identification.
Verification documents can contain highly sensitive personal information.
Do not attach a passport, driver's license, government ID, student credential, press credential, or similar verification document to an ordinary support email or ticket unless Ackaia specifically instructs you to use a designated secure process.
The verification system exists so that sensitive evidence can be handled separately from normal support correspondence.
Ackaia's verification system is designed specifically for sensitive identity and eligibility evidence.
End-to-end protection: verification submissions are protected end-to-end through the verification workflow.
Strict authorization: document images are accessible only where review is necessary and under tightly controlled authorization.
Specialized reviewers: document photos that require human review are accessed only by highly qualified personnel authorized for this purpose.
No persistent readable document copy: submitted document images are not retained persistently in readable form.
Immediate destruction after purpose: document images are destroyed immediately after they have fulfilled the purpose of the verification request.
Encryption at rest: encryption at rest is applied whenever technically possible while verification material exists within the workflow.
Where human review is necessary, the document becomes readable only within the authorized verification process for the purpose of completing that review. Access to verification material is not part of ordinary support access.
The destruction of the readable document image does not necessarily mean that Ackaia has no record that a verification occurred.
Ackaia may process verification events, authorization decisions, security records, or other necessary account and audit information in accordance with its applicable privacy and security policies.
This is separate from retaining a persistent readable copy of the submitted document itself.
If you cannot complete one of the required checks:
Do not submit a different sensitive document unless the request lists it as accepted evidence.
Do not attempt to bypass the MFA or document requirement.
Reply to the associated support or account case and explain which verification requirement you cannot satisfy.
Ackaia will determine whether another acceptable verification path is available for that specific case.
An alternative method is not guaranteed. If Ackaia cannot obtain sufficient verification for a sensitive request, it may be unable to complete the requested disclosure, status confirmation, entitlement, recovery action, or other protected operation.
A legitimate verification request should be associated with an Ackaia interaction or action that reasonably requires additional verification.
Remember:
Ackaia Support does not need your password.
Do not send your current MFA code in an ordinary support conversation.
Do not send private encryption keys, recovery phrases, or CipherDrive vault secrets.
Submit requested documents only through the designated Ackaia verification workflow.
Only provide the evidence requested for the specific verification purpose.
If you receive an unexpected request asking for sensitive information and cannot confirm that it belongs to an Ackaia case or workflow you recognize, contact Ackaia Support before submitting anything.
Once the required checks have been completed, Ackaia can continue evaluating the action associated with the request—for example, a privacy request, account-ownership review, student-status confirmation, journalist-status confirmation, or another protected process.
Passing verification confirms the information required for that verification step. It does not by itself guarantee that the underlying request, entitlement, application, appeal, or account action will be approved. The underlying request remains subject to its own requirements and review.