Deleting a file or folder removes it from normal use according to CipherDrive's current deletion workflow. However, deletion should not be understood as a promise that every related byte and record disappears from every system at the same instant.
Use the current delete or remove action in CipherDrive for the selected object.
Depending on the active product configuration, an object may be moved to trash, scheduled for deletion, or removed from active storage through another lifecycle process.
Always review the confirmation message shown by CipherDrive, especially if the object is shared or contains files you cannot reproduce.
A deleted encrypted object may pass through one or more lifecycle stages before all applicable storage copies are removed.
For example, encrypted file blobs may temporarily exist in:
trash or recovery states where available;
encrypted backups;
disaster-recovery systems;
replicated storage undergoing deletion;
systems subject to security, abuse, dispute, or legal-preservation requirements.
Ackaia does not publish one universal recovery or retention period that applies to every object, account, backup, and situation. Do not assume a specific number of days unless CipherDrive currently shows one for the relevant feature.
No.
If a trash or restore feature is currently available, use the period and controls shown in the product. Once an object leaves the applicable recoverable state, recovery may be impossible.
Even when encrypted data still exists temporarily in a backup or retention system, that does not mean Ackaia can restore it on request. Product lifecycle state and zero-knowledge key availability can both prevent recovery.
Do not use trash or retention as your backup strategy. Keep an independent copy of anything you cannot afford to lose.
A folder can contain files, nested folders, shared objects, or organizational relationships. Before deleting a folder, review its contents and any sharing state carefully.
The current CipherDrive interface should indicate how nested objects will be treated. Do not assume that removing a folder label automatically preserves or automatically destroys every contained object unless the confirmation screen explicitly says so.
If a deleted source object is no longer available through CipherDrive, associated access through that source can also stop working according to the current product state.
Deletion cannot reliably recall data already obtained by someone else. A recipient may already have:
downloaded the file;
saved it to another device;
copied or forwarded it;
cached or screenshotted it;
saved an independent copy into their own storage.
If another user has saved a shared file as an independent encrypted copy in their own CipherDrive storage, deleting your source object does not necessarily delete that independent copy.
The recipient's copy has its own storage and account lifecycle and becomes subject to the recipient's actions and applicable policies.
Yes. Limited operational records may remain for purposes such as:
billing and storage accounting;
security and fraud prevention;
transfer accounting;
copy provenance;
trust and safety investigations;
abuse prevention;
dispute resolution;
legal, accounting, tax, or evidence-preservation obligations.
Metadata retention does not imply that Ackaia can decrypt the associated stored file contents.
Download anything you may need later.
Open the exported copy and verify that it is readable.
Maintain an independent backup.
Review whether the object is shared.
Remember that recipient copies may survive source deletion.
Do not erase the only vault keys needed to export other encrypted content.