Metadata is information about an account, file, object, transfer, or event rather than the plaintext content of the encrypted file itself.
CipherDrive™ needs some metadata to operate a usable cloud drive. Zero-knowledge storage does not mean zero metadata.
Depending on the current feature and client, Ackaia may process:
storage object identifiers;
file or folder type;
encrypted file size and storage size;
MIME or generalized file category;
upload, update, deletion, and trash timestamps;
parent-folder relationships;
object status;
storage quota usage;
encrypted filename or other encrypted metadata values;
encrypted file-key material;
protocol version;
non-secret cryptographic parameters needed for decryption.
Public or controlled sharing may create metadata such as:
shared object identifier;
link creation time;
sharing and revocation status;
link-access timestamps;
recipient account identifier where applicable;
guest or pseudonymous visitor identifiers;
IP addresses associated with access;
preview, download, save, or copy activity;
transfer usage and limits.
To account for bandwidth and enforce quotas, CipherDrive may process:
uploaded or downloaded bytes;
transfer sessions and authorizations;
byte ranges requested, authorized, or served;
transfer timestamps and status;
rate-limit or throttling events;
the source object and Public Link associated with the transfer;
authenticated-recipient or pseudonymous guest identifiers.
A transfer record does not necessarily prove that a recipient fully downloaded, decrypted, viewed, or consumed the file.
When shared content is saved as an independent copy, Ackaia may maintain limited relationships among source and destination accounts, objects, shares, and later copies.
This can help with storage accounting, fraud prevention, abuse investigations, disputes, enforcement, auditability, legal compliance, and evidence preservation.
Ackaia may process:
session and login events;
IP and device information;
risk indicators;
flags and alerts;
trust-and-safety case status;
review and enforcement records;
audit records associated with authorized personnel.
Potentially. Even without plaintext file contents, metadata can reveal patterns. For example:
a large file was uploaded at a particular time;
objects are grouped in a particular folder structure;
a file was shared frequently;
an account transferred a certain volume of data;
a Public Link was accessed from particular networks.
That is why Ackaia treats metadata as privacy-relevant information rather than pretending that encrypted content is the only data that matters.
Yes. CipherDrive may encrypt filenames or selected metadata where supported. Metadata encryption is selective and can depend on client version, feature support, protocol, or migration state.
Privacy-first storage means minimizing and protecting metadata where practical, not claiming that the service can function with no operational metadata at all.