Revoking a CipherDrive™ shared link disables future access through that sharing path according to the current product and server-side link state.
Revoke a share when:
the recipient no longer needs access;
you sent the link to the wrong person;
the link was posted somewhere unintended;
you suspect the link was copied or leaked;
the sharing purpose has ended;
you are replacing the share with a new access method;
the content has become more sensitive.
Use the current CipherDrive sharing controls for the object and choose the available option to disable, revoke, or remove the link.
At the infrastructure level, CipherDrive can stop serving the encrypted object through that public-link authorization path or mark the link as no longer valid.
Not necessarily. The important effect of revocation is that CipherDrive refuses future access through the revoked sharing path.
The exact cryptographic and key-management behavior can vary by sharing protocol and version. Do not assume that revocation means every copy of every piece of key material disappears from every browser, message, cache, or recipient device.
Revoking a link cannot reliably erase content that a recipient already:
downloaded;
saved locally;
copied;
screenshotted;
screen-recorded;
forwarded;
re-uploaded to another service;
saved as an independent copy where supported.
Once decrypted information has left your control, CipherDrive cannot guarantee remote deletion from the recipient's devices or other services.
The text of an old link can remain in emails, chats, browser history, screenshots, or documents after revocation. That does not necessarily mean the server will continue authorizing the request.
Always test the current share status through CipherDrive rather than assuming that the continued existence of the URL text means the share is still active.
Yes. Ackaia may restrict or disable sharing for security, abuse prevention, policy enforcement, copyright procedures, legal compliance, severe-risk events, or other permitted reasons.
If the content still needs to be shared, revoke the compromised link first and create a new sharing path using the current product controls. Send the replacement only through a trusted channel.
Revocation stops future platform-mediated access. It cannot recall information already obtained by a recipient.