Security
A studio's raw files are irreplaceable — there are no reshoots, and no apology covers a lost wedding. This is exactly how Wedding OS protects them, in plain terms.
Your media lives in a private cloud bucket — nothing has a public URL. Every view and download goes through a short-lived signed link minted per request, encrypted in transit and at rest.
Every single query is scoped to your studio on the server — never trusted from the browser. An automated isolation test suite re-proves it on every change we ship.
80+ fine-grained permissions. Your freelance editor sees production, not your P&L; your accountant sees invoices, not client galleries.
Gallery and portal links are unguessable 256-bit tokens, stored hashed like passwords, rate-limited against guessing — and revocable by you in one click.
Proofing galleries serve watermarked previews. Full-resolution files only move when you decide to deliver them.
A full export of your studio — clients, finances, projects, files — is a built-in feature, not a support ticket. Backup and restore procedures are documented and rehearsed.
In more detail
Every query is scoped to your studio on the server and never trusted from the browser. An automated isolation suite re-proves that on every change we ship — it is a test that fails the build, not a policy in a document.
Roles carry 80+ fine-grained permissions across every module, so a freelance editor can move production jobs without seeing your P&L, and an accountant can raise invoices without opening a client gallery.
Gallery and portal links are 256-bit tokens, stored hashed the way passwords are, rate-limited against guessing, and revocable in one click. Reissuing a link kills the old one immediately — which is the point of it.
Counts, biometric descriptors and person groups are three separate consents, each one an explicit act by an administrator. Analysis runs on your own server, nothing is sent to a third party, and turning a stage off deletes what it produced. Age and gender are never computed at all.
Proofing galleries serve watermarked previews. Full-resolution files leave the platform only on delivery, and every view or download is a short-lived signed link minted per request — nothing has a public URL.
A full export of your studio — clients, finances, projects, files — is built into the product. Backup and restore procedures are documented and rehearsed. Loyalty should come from the product being good, not from your data being stuck.
Wedding OS is a young product and we would rather you knew where the edges are. We hold no formal certification such as ISO 27001 or SOC 2, and we publish no uptime SLA — so we are not going to print a badge for either. What is above is implemented and testable today. If your studio needs something specific before it can commit, ask and you will get a straight answer.
Ask a security questionRelated: Privacy Policy · Terms of Service · Storage & pricing