Security
Security practices for schedule.site tenant workspaces, platform administration, imports, assistant actions, and production configuration.
Last updated: 2026-07-19.
This page is provided for product transparency and operational review. It is not legal advice.
Security model
schedule.site is multi-tenant. Domain tables are workspace-scoped, authenticated routes enforce tenant roles, and platform administration uses a separate identity realm from tenant users.
Authentication
Tenant sessions use secure authentication controls, role middleware, email verification, and account status checks. Platform administration uses separate MFA-protected sessions and live support-session validation.
Assistant safety
Taylor does not receive database credentials. Deterministic server-side services authorize and execute scheduling actions, with confirmation flows for consequential tasks and audit records for mutations.
Data protection
Import credentials are encrypted with AES-256-GCM using workspace context as associated data. Sensitive credentials are not returned by the API and are purged after extraction.
Operational controls
Production startup validation rejects weak secrets, bad origins, and unsafe demo flags. Authenticated mutations are audited, and high-risk public surfaces use rate limits and request-size controls.
Responsible disclosure
If you believe you found a vulnerability, do not access other customers' data. Report the issue with reproduction details through the support channel in your account.