Security Policy
How AppSite protects the platform, and what remains your responsibility. The split differs by hosting model.
Your workspace runs on AppSite-operated Google Cloud infrastructure. Your data is stored in shared databases, separated from other customers by tenant identifier and enforced server-side security rules. AppSite operates, deploys, patches, monitors and backs up the platform for you.
Authentication and access control
Authentication is provided by Firebase Authentication. Access is role-based, and authorization is enforced server-side by security rules and functions rather than by the user interface.
Administrative actions are logged with the acting account and timestamp.
Tenant isolation
Every record carries a tenant identifier, and security rules restrict reads and writes to the caller's own tenant. Isolation is logical and enforced server-side; it is not physical separation.
Cross-tenant access attempts are detected, denied, logged as security findings and alerted on.
Encryption
All traffic is served over TLS. Data at rest is encrypted by the cloud provider.
Provider-managed encryption at rest protects against physical media compromise; it does not hide data from an authorized query. Highly sensitive fields should therefore be encrypted client-side before they are written, so the database stores ciphertext only.
Never store encryption master keys in the database, in client code, in remote configuration or in source control.
Secrets
API keys and credentials are held server-side and are never exposed to the browser. Client features that need a third-party service call a server-side proxy rather than holding the key.
Keys are rotated on a schedule, and rotation is tracked.
Patching and updates
AppSite applies platform and dependency updates. Security fixes are prioritized and deployed without waiting for a scheduled release.
Backups
Databases are backed up on a schedule with point-in-time recovery enabled where supported. Backups inherit the same encryption and access controls as live data.
Incident response
Suspected incidents are triaged, contained and recorded. Where an incident affects your data we notify you without undue delay, with what we know, what we are doing, and what you should do.
Reporting a vulnerability
Report suspected vulnerabilities to security@appsite.ca. Please report rather than exploit; good-faith research is welcomed and researchers who follow this policy will not be pursued.
Your responsibilities
Keep credentials secure and enable available account protections. Grant the least access each person needs, and remove access promptly when someone leaves. Review your administrators periodically.
Decide deliberately what sensitive information you store, and encrypt it before storage where warranted.
security v2.0.0 · shared · df48d010d463e699
Your platform runs inside your own Google Cloud organization, on projects and a billing account you own. Your data is never stored in AppSite's shared databases. AppSite delivers the software to repositories you control, and you perform the deployment. AppSite holds no standing access to your environment.
Authentication and access control
Authentication is provided by Firebase Authentication. Access is role-based, and authorization is enforced server-side by security rules and functions rather than by the user interface.
Administrative actions are logged with the acting account and timestamp.
Tenant isolation
Isolation is physical: your platform runs in your own cloud organization and projects, with no shared database and no shared credentials. There is no cross-tenant surface to defend, because there is no other tenant in your environment.
Encryption
All traffic is served over TLS. Data at rest is encrypted by the cloud provider.
Provider-managed encryption at rest protects against physical media compromise; it does not hide data from an authorized query. Highly sensitive fields should therefore be encrypted client-side before they are written, so the database stores ciphertext only.
Never store encryption master keys in the database, in client code, in remote configuration or in source control.
Secrets
API keys and credentials are held server-side and are never exposed to the browser. Client features that need a third-party service call a server-side proxy rather than holding the key.
Keys are rotated on a schedule, and rotation is tracked.
Patching and updates
AppSite releases fixes to your repositories and notifies you of security-relevant releases. Because you control deployment, applying them promptly is your responsibility, and an unapplied fix leaves your environment exposed.
Backups
Backup schedules, retention and point-in-time recovery are configured in your own projects and are your responsibility. AppSite can advise on configuration but does not hold copies of your data.
Incident response
Suspected incidents are triaged, contained and recorded. Where an incident affects your data we notify you without undue delay, with what we know, what we are doing, and what you should do.
Reporting a vulnerability
Report suspected vulnerabilities to security@appsite.ca. Please report rather than exploit; good-faith research is welcomed and researchers who follow this policy will not be pursued.
Your responsibilities
Keep credentials secure and enable available account protections. Grant the least access each person needs, and remove access promptly when someone leaves. Review your administrators periodically.
Decide deliberately what sensitive information you store, and encrypt it before storage where warranted.
security v2.0.0 · dedicated · b2ec7a86a9daba33