If you can sign in to CipherDrive™ but cannot access your files, first identify which layer is failing.
Successful Ackaia ID authentication does not automatically prove that your vault keys, product entitlement, storage objects, and transfer permissions are all available.
If your files or folders do not appear at all, check:
that you signed in with the intended Ackaia ID;
that you are looking at the correct CipherDrive account or vault;
whether the account has the expected product entitlement;
whether the objects were moved, deleted, or placed in trash where supported;
whether the interface reports a loading, synchronization, authorization, or service error.
If filenames or objects appear but CipherDrive asks you to unlock the vault, the issue is cryptographic access.
You may need the vault secret, local key material, device key, or recovery mechanism used by the current client.
A decryption failure can occur when:
the required file key cannot be unwrapped;
required local key material is missing;
the wrong vault is active;
encrypted data is incomplete;
a chunk fails authenticated-decryption checks;
the local browser or device cannot complete the operation.
AES-GCM authenticated encryption is designed to reject altered or corrupted ciphertext rather than silently treating it as valid plaintext.
Product access may be affected by:
an expired session;
account restriction;
subscription or entitlement changes;
payment failure;
storage or transfer limits;
security controls;
trust-and-safety enforcement;
legal restrictions.
Read any account banner or error message carefully before assuming the problem is cryptographic.
Clearing local browser storage can remove remembered key state while leaving the encrypted cloud objects intact.
If another trusted device still works, preserve that access until you have restored or backed up the vault.
A new device may authenticate successfully but still lack the key material needed to decrypt an existing vault.
Use the current CipherDrive recovery or device-enrollment flow where available.
If most files work and one object fails, the problem may be object-specific rather than account-wide.
Record:
the affected object;
the exact error;
whether download starts;
whether decryption fails at a particular point;
whether the same file works on another trusted device.
The most useful first sentence is one of these:
“I can sign in, but my files are not visible.”
“I can see my files, but the vault will not unlock.”
“I can see the file, but download is denied.”
“The encrypted file downloads, but decryption fails.”
That distinction helps support choose the correct troubleshooting path.
Do not send vault secrets or encryption keys to support. A legitimate troubleshooting process should not require you to expose private cryptographic material.