SECURITY / POLICY
Information Security Policy
How Panoverse Inc. organizes its security program and protects the information it handles.
Last updated: November 7, 2026 · Owner: Data Protection Officer, lin@kolect.ai
Purpose and scope
This policy describes how Panoverse Inc. protects the information it handles. It covers the Panoverse platform at os.panoverse.com, the related Kolect web applications operated by Panoverse Inc., the infrastructure they run on, and every employee and contractor who can access company systems or customer data.
Security program
Our Data Protection Officer, Lin Shao, owns the security program. It consists of this policy and five supporting policies: Access Control, Data Classification & Encryption, Incident Response, Vulnerability & Patch Management and Personal Data Protection.
Principles
- Managed cloud infrastructure. We run on Google Cloud, Supabase-managed PostgreSQL and Vercel. We do not operate our own data centers or office servers that hold customer data.
- Tenant isolation. Each customer workspace is isolated from every other. In the Panoverse platform database, row-level security is enabled and enforced on application tables, and application services connect with scoped database roles that cannot bypass it. Our other applications enforce workspace and campaign scoping in their service layer.
- Secrets stay out of code. Credentials are kept in protected server environment files or a managed secret store, never in source code, logs or AI prompts.
- Least privilege. People and services receive only the access their work requires.
- Reviewed, reversible change. Production changes go through version control, automated checks and controlled release tooling that can roll back.
- Auditability. Business actions that change customer data, send messages or alter permissions are recorded in audit logs.
Network and infrastructure
Production runs on its own servers and database, separate from staging servers, staging databases and staging credentials. Customer-facing traffic is served over HTTPS, and plain HTTP requests are redirected to HTTPS. Server login uses Google Cloud OS Login, which ties every session to an individual company account. Databases are reached only through the provider’s authenticated endpoints.
Monitoring
Production services run automated health checks, background-job watchdogs and post-release smoke tests. Failures alert the engineering team in its internal operations channel. Our cloud providers supply platform logs that we use for investigation.
Personnel responsibilities
Everyone with access must use company accounts for company systems, protect their credentials and enable multi-factor authentication wherever it is offered, meet the device requirements in our Access Control Policy, never copy customer data or secrets to unapproved locations, and report any suspected security incident to the Data Protection Officer immediately.
Improvements being rolled out in November 2026
- Required two-factor authentication for our source-code organization.
- Enforced multi-factor authentication on administrative consoles.
- Restricting administrative network access to production servers.
- Dependency vulnerability alerts and automated security updates.
- Application-level encryption of the remaining legacy stored tokens.
- Enforced TLS for all database connections.
Certification
We do not currently hold ISO 27001 or SOC 2 certification.
Review and contact
The Data Protection Officer reviews this policy and the supporting policies at least once a year and after any significant change to our systems or a security incident. Security questions and reports: lin@kolect.ai.