A practical pre-send workflow for protecting client previews, paid work, and sensitive creative files with access limits, watermarks, and clear expectations.
Guides
On the Oblivio blog, we talk about digital privacy, file security, and control over personal information, without turning everything into a technical manual.
We focus on real situations: documents sent too quickly, unexpected screenshots, files that keep circulating, data that seemed safe but wasn’t. From there, we build guides, reflections, and insights on encryption, secure sharing, traceability, anonymity, and digital awareness.
Oblivio starts from a simple idea: when you share something, you shouldn’t completely lose control over what you’ve sent.
This blog is our space to explore that grey area between trust, technology, and everyday life. To better understand the risks, make more conscious choices, and protect what truly matters.
A practical pre-send workflow for protecting client previews, paid work, and sensitive creative files with access limits, watermarks, and clear expectations.
Move through the editorial map by topic.
A practical pre-send workflow for protecting client previews, paid work, and sensitive creative files with access limits, watermarks, and clear expectations.
Leaked photos, videos, and documents can sometimes be traced to a recipient, but attribution depends on evidence such as recipient-specific fingerprints, metadata, and access records.
A practical, non-accusatory guide to preserving evidence, assessing clues, and reducing the chance that private photos are shared again.
A practical guide to tracing a leaked file using recipient records, access logs, forensic watermarks, metadata, and evidence preservation.
Sent a document to the wrong recipient? Act quickly: stop access where possible, ask for deletion, document the incident, and secure future sharing.
A calm, practical response plan for containing an accidental data leak, notifying the right people, documenting the incident, and preventing a repeat.
Practical ways to reduce screenshots of private photos, set boundaries, limit access, and respond if a copy has already been taken.
Blocking screenshots can reduce casual copying, but it cannot stop screen recordings, external cameras, backups, or recipient-side copies.
Apps can reduce the chance of screenshots of private photos, but no app can guarantee that a recipient will never copy an image. Learn what OS controls can do, where they fail, and how to share more safely.
Forensic watermarking can help link a leaked file to a recipient, but it rarely proves who personally leaked it without supporting evidence.
A buyer guide to controlling private photos and documents after delivery, with practical criteria for expiry, revocation, tracing, and local privacy.
Deleting your copy of a sent file rarely deletes every copy. Learn what you can still revoke, remove, limit, and document after sending a file.