What pre-release material needs
A cut of an unreleased film, a game build under embargo, a campaign that has not launched, a client’s unreleased product photography: the material is the same shape as any large delivery, but the consequences of a leak are not. Consumer file-sharing links live forever by default, can be forwarded to anyone, and tell you nothing about who opened them. Studios sign NDAs with their clients and then hand the files to a tool that cannot honour them.
Controls on every link, today
Every Boita share link has an expiry. Add a password, which is available on Pro and above, cap the number of downloads, and get an email when someone downloads. The sender dashboard shows views and downloads per file and per recipient, so you know who collected what and when. Send by email from Boita rather than pasting a link into a chat.
Revocation is immediate. Download tokens are minted per download and expire in minutes, so pulling a link stops new and resumed transfers at once, not at the next expiry. A reminder arrives before a link expires, so a live delivery is extended deliberately rather than left open.
Inside the workspace
Workspaces have owner, admin and member roles with invitation by email, two-factor authentication with recovery codes, and an audit log of logins, shares created and opened, downloads, deletions and admin actions. Each workspace has its own storage root on the transfer server with explicit path restrictions, tested for cross-tenant escapes on every change, and every upload or download runs on a token scoped to that operation. Transfer sessions are encrypted end to end by the engine, and web and share pages are HTTPS only.
The server records a checksum for every file at transfer time and shows it in the file details, so both sides can confirm the delivered cut is the one that was sent. The delivery receipt shows who viewed and downloaded, with the integrity check on every completed download, and exports as PDF on Scale and above.
Verified recipients, encrypted deliveries, and what is not claimed
Recipient verification, on Pro and above, restricts a link to named email addresses confirmed by a one-time code before anything about the files is shown, so the receipt names who downloaded. Sender-side encrypted delivery works on every plan: set a passphrase when you send and the files are encrypted on your machine before they leave it; Boita never holds the passphrase. Embargoed links serve nothing before their opening time, view-only links have no download button, and on Scale and above every preview and download can carry the recipient’s name as a watermark. Workspace policies cap link expiry and require a password on every link; single sign-on, IP allow-lists, device policies and DLP hooks are on Enterprise. Enforced MFA for every member is coming.
Boita does not claim any certification today. SOC 2 Type II is in progress and a penetration test follows; staff access to file contents is being put behind a ticketed, approved, time-limited process that appears in your audit log. Ask for the security overview.
- Expiry, password, download limit and download notification on every link
- Instant revocation through per-download tokens
- Roles, two-factor authentication and an audit log per workspace
- Checksums on every file; receipts with a PDF export on Scale and above
- Recipient verification from Pro; passphrase encryption on every plan; SSO and DLP on Enterprise