Folders help you organize files and other objects in CipherDrive™ without changing the core zero-knowledge protection applied to supported encrypted file contents.
From your CipherDrive drive, use the current new-folder action, choose a folder name, and create it in the desired location.
The exact button or menu can change over time, but folders are represented as storage objects that CipherDrive can associate with files and other folders.
Use the current move, drag-and-drop, or organization controls offered by CipherDrive to place an object into another folder.
Moving a file within CipherDrive generally changes the object's organizational relationship rather than requiring Ackaia to decrypt the file contents.
Zero-knowledge storage protects supported file contents, but CipherDrive still needs operational metadata to maintain a usable drive.
For example, Ackaia may need to know:
whether an object is a file or a folder;
which account or storage vault the object belongs to;
the parent-child relationship between objects;
how much encrypted storage an object uses;
whether an object is shared;
timestamps or object identifiers required for service operation.
This lets CipherDrive build a folder hierarchy without requiring Ackaia to read the plaintext contents of the files stored inside it.
CipherDrive may encrypt selected metadata, including filenames where supported by the active client and object type.
Metadata encryption is selective rather than absolute. The service may still require visible or partially visible metadata to operate storage, quotas, sharing, reliability, and object relationships.
Do not assume that every descriptive property associated with every file or folder is hidden from Ackaia. The exact protection can depend on client version, feature support, migration state, and product configuration.
Use CipherDrive's current rename control for the folder. Where the name is protected by client-side metadata encryption, the updated name can be encrypted before the new value is stored.
Renaming an object does not change the plaintext contents of files inside the folder.
A folder can be reorganized when the current CipherDrive client allows it. Moving a folder changes its parent relationship in the drive hierarchy.
Because CipherDrive must know enough structural information to represent the hierarchy, parent-child relationships are examples of operational metadata that may remain visible to Ackaia even when file contents or supported names are encrypted.
CipherDrive may support sharing of files or folders through public or controlled mechanisms. Sharing can introduce additional metadata and security considerations, including:
sharing status;
public-link status;
transfer usage;
access events;
recipient behavior after decryption.
Anyone who obtains the complete share information and required key material may be able to access shared content. Revoking a share cannot erase copies a recipient has already obtained outside your control.
Folders themselves represent organizational structure, while files and other stored objects contribute to your actual encrypted storage usage according to current CipherDrive accounting rules.
Storage limits and feature availability can vary by plan and configuration. Use the current storage indicator in CipherDrive rather than relying on a fixed number in documentation.
Use folders to separate personal, work, archive, and shared material.
Avoid placing unrelated sensitive material inside a folder you plan to share.
Review public or shared folders regularly.
Use clear names on your own trusted device, while remembering that metadata protection can vary.
Maintain independent backups of important folder trees or files where appropriate.