SECURITY / POLICY
Access Control Policy
How access to Panoverse systems and customer data is granted, reviewed and removed.
Last updated: November 7, 2026 · Owner: Data Protection Officer, lin@kolect.ai
Purpose
Access to our systems and customer data is granted on a need-to-know, least-privilege basis and can be traced to an individual.
Customer and user access
- Users sign in through our authentication provider. Accounts are individual; we do not issue shared logins.
- Every user belongs to one or more workspaces and can see and change only data in those workspaces, within the role and team permissions that the workspace’s administrators assign.
- In the Panoverse platform database, workspace isolation is also enforced by row-level security, so a fault in one request cannot read another workspace’s records through the application’s database roles.
- AI assistants in the product act with the permissions of the user who invoked them, never with broader access.
- Connections to third-party accounts such as Shopify, Meta, TikTok Shop and Google are authorized by the customer through the platform’s own consent screen, request the permissions the feature needs, and can be disconnected by the customer at any time.
Staff access
- Staff use individual company accounts. Production server login uses Google Cloud OS Login, so each session maps to a named person and is logged by the provider.
- Database access is separated by purpose: the services use application roles, schema changes use a migration role available only to the release workflow, and investigations use read-only diagnostic access. Application credentials are not used for manual investigation.
- Source code is kept in private repositories. Production branches are protected so that only our automated release application can update them; people propose changes through pull requests.
- Production secrets are stored only in protected environment files on production servers or in a managed secret store. They are never placed in source code, chat, logs or AI prompts.
Access lifecycle
The Data Protection Officer grants access when a person’s role requires it and removes it no later than the next business day after the role changes or the person leaves. Every quarter the Data Protection Officer reviews who holds owner or administrator rights in our cloud, database, hosting, source-code and authentication services and removes access that is no longer needed. Credentials are rotated when compromise is suspected or when a person with access to them leaves.
Authentication and remote administration
Required two-factor authentication for our source-code organization, enforced multi-factor authentication on administrative consoles, and restricting administrative network access to production servers to Google Cloud’s Identity-Aware Proxy are being rolled out in November 2026.
Device requirements
Devices used for company work must have full-disk encryption turned on (FileVault on macOS, BitLocker on Windows); automatic screen lock after no more than 10 minutes of inactivity; a password or biometric login; the operating system’s built-in malware protection enabled; and automatic operating-system security updates.
Passwords
Passwords must be unique per service and stored in a password manager or the operating-system keychain. We rely on our identity providers’ password-strength rules together with multi-factor authentication rather than forced periodic rotation.