Security and trust
Trust the operating model, not the slogan.
StayLayer keeps the public site, team workspace, and live guest website intentionally separated so customer operations stay private and the guest journey stays clean.
🔒
Role-based separation for owners, editors, billing contacts, and support teams
🛡️
Rate-limited public login, signup, and contact entry points
⚡
Audit trails for important workspace and site changes
✓
Published legal documents and clear data-handling policies
Security and Data Handling
Full security documentation.
Access and authentication
Workspace access is protected through authentication controls, session security, membership roles, and separate support access paths.
The customer-facing site is kept separate from internal support access so the public journey does not become the entry point for platform administration.
Operational controls
StayLayer uses rate limiting, audit logging, deployment tracking, and domain-status monitoring to reduce abuse and improve operational traceability.
A formal breach-notification SLA is still being finalized and will be published in the legal hub when approved.
Data minimization
Public marketing surfaces omit unsupported customer claims, fake testimonials, and unverified metrics.
Only customer-facing pricing, legal, and marketing information is published in the public site.
Our commitment
Transparency is a feature, not an afterthought.
Customer work stays private. Public entry points are protected. Important workspace changes stay traceable.
Workspace isolation
Each customer workspace stays separated from the others.
Rate limiting
Public login, signup, and contact paths are protected against abuse.
Versioned docs
Every legal change is published with an effective date.
Audit logging
Important workspace changes remain traceable over time.