Trust & security
Private assets. Explicit access. Clear boundaries.
Brarie’s current architecture keeps brand data isolated, files private and recipient permissions checked when access occurs.
Implemented controls, not certification claims.
Brarie does not claim SOC 2, ISO, HIPAA, SSO or other certifications and enterprise compliance features.
Access model
A visible control is never the security boundary.
Permissions are enforced for records and files. Interface controls only reflect what a person is allowed to do.
Files and recipients
Access is checked when the file is requested.
Originals and previews remain private. Short-lived file links are created only after access is verified.
- Private original and preview storage
- Short-lived signed file access
- Verified-email invitation matching
- Invite-only share recipients
- Frozen asset and exact-version manifests
- Rights window checked on recipient read
- Revoked or expired access stops new reads
- Unavailable responses avoid naming private content
Tenant and source boundaries
Brands stay separate. Sources stay untouched.
Search, metadata reads and file operations stay pinned to the active brand and signed-in caller.
Connected-source imports are one-way. Brarie does not rename, move or delete provider originals, and switching brands clears cross-brand client state.
Private by default
Assets stay in private storage and file access uses short-lived links.
Verified access
Recipient and team access is checked against signed-in identity.
Context stays attached
Version, rights and source provenance travel with the asset.
Build around explicit access.
Start small, keep boundaries clear, and expand when the team is ready.