Security
Blitera is built for governed access to sensitive links and documents. This page summarizes the current security posture during the controlled beta.
Security Model
Blitera uses server-side access validation, account isolation, CSRF protection, secure session cookies, access policies, and audit logging to reduce the risk of uncontrolled sharing.
Shared links are resolved server-side from stored records. Public recipient URLs do not accept an arbitrary redirect destination from query string parameters.
Protected Content
Blitera supports encrypted link storage, protected file delivery, password-gated access, expiration rules, revocation, and access logging. Sensitive File Mode can encrypt selected files in the browser before upload, with no server-side passphrase recovery.
During beta, do not upload highly sensitive production material unless this has been agreed directly with Blitera.
Privacy & Crawlers
Recipient routes such as /r/... are intended for
controlled access, not public search indexing. They are excluded
from crawling and marked with noindex protections where applicable.
Blitera does not use advertising trackers or third-party analytics cookies. See the Privacy Policy for details.
Report a Security Issue
If you believe you found a vulnerability, an abuse pattern, or a suspicious Blitera link, please report it through the dedicated channel.