Workspace access
Workspace views sit behind authenticated routes, and media access is handled through signed URLs rather than public bucket links.
Trust
Security overview
A practical summary of how SaliencyLab currently handles access, uploads, and vendor processing, written to be clear about what is true today and what is not yet claimed publicly.
Current controls snapshot
Data in transit and at rest
Public marketing copy and product documentation describe uploads as encrypted in transit and at rest, with private storage paths for workspace assets.
Vendor processing
Creative analysis can involve third-party AI providers. The current product position is that uploads are processed for analysis rather than marketed as open training data.
Operational boundaries
This page describes current product practices. It does not claim SOC 2, ISO 27001, or custom legal terms unless separately agreed in writing.
What enterprise teams usually ask
Most enterprise reviews come down to four questions: who can access raw files, how media URLs are exposed, what vendors touch the content, and what claims the company is willing to make in a procurement process.
- Ask which routes are public and which are authenticated.
- Ask whether uploads are exposed through public bucket URLs or signed access paths.
- Ask which external AI services process content and for what purpose.
- Ask which commitments are already public versus which require a contract or security review.