CipherDrive™ is designed to minimize unnecessary access to your file contents, but the service still needs information to create accounts, operate encrypted storage, manage subscriptions, enforce limits, secure the platform, and support sharing.
Zero-knowledge does not mean zero data collection. It means that, for supported encrypted-storage workflows, Ackaia does not ordinarily possess the cryptographic keys required to decrypt stored file contents after client-side encryption is complete.
CipherDrive may receive or process information associated with your Ackaia ID, including:
name or display name;
email address;
account identifier;
account type and status;
subscription status and plan information;
organization or billing profile information;
security settings;
product entitlements and feature eligibility;
account creation and recovery information.
To protect accounts and sessions, Ackaia may process:
login and logout timestamps;
session identifiers;
IP addresses;
approximate location inferred from IP;
browser, device, operating-system, and user-agent information;
failed-login attempts;
security challenges;
session revocation records;
suspicious-activity signals;
audit logs and account-recovery events.
CipherDrive needs operational information about encrypted objects. Depending on the feature and client, this can include:
object identifiers;
file or folder type;
encrypted file size and storage usage;
MIME or generalized file category;
upload, update, deletion, and trash timestamps;
parent-folder relationships;
sharing and Public Link status;
storage and transfer quota usage;
object state, such as active, deleted, processing, failed, or blocked;
encrypted filename or metadata values where supported;
encrypted file-key material;
protocol versions and non-secret cryptographic parameters.
To operate downloads, previews, sharing, quotas, and fair-use controls, Ackaia may process:
uploaded and downloaded bytes;
transfer sessions and authorizations;
byte ranges requested or served;
preview activity;
transfer timestamps and status;
the object or Public Link associated with a transfer;
authenticated-recipient identifiers where applicable;
pseudonymous guest or network identifiers;
quota counters and limit-exceeded events.
A transfer record can show that bytes were authorized, requested, or served. It does not necessarily prove that a recipient successfully received, decrypted, viewed, or consumed the entire file.
If an authenticated user saves shared content into their own CipherDrive storage, Ackaia may process limited provenance and accounting information linking the source and destination objects or accounts.
This can include source and destination identifiers, copy timestamps, storage impact, operational status, and relationships between original and later copies.
If you use a paid plan, Ackaia may process subscription, invoice, transaction, tax, billing-contact, and limited payment-method metadata.
Where a third-party payment processor handles card payments, Ackaia does not intend to store full payment-card numbers.
CipherDrive may process technical signals and records for security, fraud prevention, abuse prevention, child safety, malware detection, and enforcement. These can include hashes, fingerprints, risk scores, blocked-upload records, flags, alerts, trust-and-safety case information, and related account, object, transfer, or sharing identifiers.
If you contact Ackaia, the company may process your message, contact information, account identifier, support history, diagnostic information, and any logs, screenshots, or attachments you choose to provide.
Do not send passwords, private keys, vault secrets, recovery phrases, or unrelated sensitive file contents through ordinary support channels.
For supported encrypted-storage workflows, file contents are encrypted in your browser or client before ordinary storage. Ackaia stores encrypted blobs and encrypted key material and, under normal operation, does not possess the keys required to decrypt the stored file contents.