Governance & Trust

Security Standards

Root & Bower preserves material that can be deeply personal. Our security approach is built around limiting access, using established infrastructure providers, and avoiding security claims that exceed what the system can actually guarantee.

Accounts

Authenticated access

Root & Bower uses Supabase authentication to establish user sessions and identify authenticated account holders before protected application actions are performed.

Authorization

Role-based sanctuary access

Sanctuary access is controlled through ownership, membership, stewardship roles, visibility rules, application permission checks, and database-level access policies.

Storage

Separated object storage

Uploaded media is stored using Cloudflare R2-backed object storage rather than being embedded directly in public application records. Application logic determines how display access is provided.

Transport

Encrypted connections

Production traffic is intended to be delivered over HTTPS so information is encrypted while traveling between supported browsers and Root & Bower's web infrastructure.

Access Control

Security is more than a password.

Root & Bower's authorization model is designed so that being signed in does not automatically grant access to every sanctuary. Access depends on the sanctuary's visibility, the authenticated user's membership, and the role or permission associated with that relationship.

Public

Content intentionally made public can be accessed without private sanctuary membership.

Sanctuary Access

Restricted content is intended for authenticated people who have been granted access.

Management

Administrative actions are limited to roles that are permitted to perform them.

What We Do Not Claim

No security system is absolute.

Root & Bower does not claim that the service is impossible to breach, permanently available, "military-grade," or immune to every form of attack, human error, vendor failure, or software defect.

Root & Bower is also not a zero-knowledge or end-to-end encrypted storage service. The application and its service providers must be able to process content in order to provide functions such as image optimization, playback, storage, permissions, backups, and display.

Users should protect their account credentials and retain independent copies of irreplaceable original media.

Infrastructure

Built on established service providers.

Root & Bower currently relies on third-party providers for critical infrastructure, including Supabase for authentication and database services, Cloudflare for object storage and delivery, Stripe for payment processing, and Resend for transactional email. Those providers maintain their own security programs, terms, and operational controls.

Found a security concern?

Please contact Sanctuary Care with enough information for us to understand the issue, but do not send passwords or unnecessary sensitive information by email.

care@rootandbower.com

For formal information about personal-data practices, see the Privacy Policy.