CipherDrive™ uses Ackaia ID for account authentication. After you sign in, CipherDrive verifies your account and product access before your client can open the encrypted-drive experience.
A typical sign-in flow looks like this:
Open CipherDrive.
Choose the option to sign in.
You are directed to Ackaia ID for authentication.
Complete the requested sign-in and security checks.
Ackaia ID returns you to CipherDrive through the authorized authentication flow.
CipherDrive checks your account status, product entitlement, session, and relevant security requirements.
If your encrypted vault is not already unlocked on the device, you may also need the vault-specific secret or local cryptographic material required to decrypt your files.
The exact screens can change as Ackaia improves its identity and security systems, but the identity layer and the file-encryption layer remain separate.
There are two different access checks:
Ackaia ID authentication verifies your account and session.
CipherDrive vault access requires the cryptographic material needed to decrypt encrypted content.
You can therefore sign in successfully and still be asked to unlock your vault.
If the required cryptographic material has been lost, Ackaia may be unable to decrypt the files even though your Ackaia ID account itself is working correctly.
Ackaia may require reauthentication or additional verification when reasonably necessary to protect your account or the service. Examples can include:
an expired or revoked session;
a new browser or device;
cleared cookies, browser storage, or session data;
a security-sensitive account action;
suspicious or unusual sign-in activity;
an account-recovery event;
updated security requirements;
a product or entitlement change;
a session that Ackaia has invalidated for security reasons.
Ackaia processes authentication and security information such as login timestamps, session identifiers, IP addresses, device and browser information, failed login attempts, security challenges, suspicious-activity signals, session revocation records, and account-recovery events to protect accounts and troubleshoot access problems.
Even when your Ackaia ID session remains valid, CipherDrive may no longer have the local key state needed to decrypt your vault.
This can happen after:
clearing browser or site data;
using a different browser profile;
using a new device;
removing remembered local access;
signing out or revoking local sessions;
a security-related reset;
changes to the client or local storage environment.
Depending on the feature and client, CipherDrive may store wrapped key material or other cryptographic state in browser or device storage to reduce how often you need to enter a vault secret.
Check the following:
you are using the intended Ackaia ID;
your browser allows the cookies and local storage required for authentication;
your browser and operating system are current;
you have not blocked an Ackaia authentication domain or redirect;
your account or subscription has not been restricted;
you can complete any requested security or recovery verification.
If the problem is specifically that you can sign in but cannot decrypt files, treat it as a vault-access issue rather than a normal account-password issue.
Sign in only through official Ackaia and CipherDrive domains.
Do not share passwords, recovery codes, vault secrets, or cryptographic keys.
Avoid unlocking sensitive vaults on public or shared computers.
Keep your browser, device, and operating system updated.
Review suspicious account activity promptly.
Revoke sessions or local access on devices you no longer control.