SECURITY / POLICY
Data Classification & Encryption Policy
How we classify information and protect it in transit, at rest and through deletion.
Last updated: November 7, 2026 · Owner: Data Protection Officer, lin@kolect.ai
Classification
Restricted: passwords, API keys, OAuth access and refresh tokens, database credentials and encryption keys. Never stored in source code, logs or AI prompts; kept only in protected server environment files, a managed secret store, or encrypted in the database; never shown to users after entry.
Confidential: customer business data such as orders, revenue, campaign and advertising performance; creator and seller data received through platform APIs; messages; and personal data of users and creators. Stored only in our production databases and storage, visible only to members of the owning workspace and to staff who need it to operate or support the service. Never sold, used for advertising or shared with other workspaces.
Internal: source code, runbooks, system configuration without secrets, and aggregated cost and usage metrics. Kept in private repositories and company tools.
Public: marketing pages, published policies and public documentation.
Data received from a platform such as TikTok Shop, Meta, Shopify or Google is Confidential and is used only for the purpose the customer or creator authorized, in line with that platform’s terms.
Data minimization
We request the permissions a feature needs. Our Shopify integration does not request or keep shoppers’ names, email addresses, phone numbers or street addresses.
Encryption in transit
All web and API traffic to our services uses HTTPS (TLS), and plain HTTP requests are redirected to HTTPS. Calls from our services to third-party APIs use HTTPS. Enforced TLS for all database connections is being rolled out in November 2026.
Encryption at rest
Our managed databases and cloud server disks and storage are encrypted at rest by the provider with AES-256 and provider-managed keys.
In the Panoverse platform, third-party access and refresh tokens are additionally encrypted by our application with AES-256-GCM before they are written to the database, and each encrypted token is bound to its workspace so it cannot be moved to another tenant. The key is held only in the production runtime environment, so read access to the database alone does not reveal tokens. Application-level encryption of the remaining legacy stored tokens in our older applications is being rolled out in November 2026.
Backups
Production databases are backed up by our database provider with continuous write-ahead-log archiving. Backups inherit the provider’s encryption at rest.
Keys and secrets
Encryption keys and credentials are generated randomly, stored only in protected runtime environments or a managed secret store, and rotated when compromise is suspected or when a person with access to them leaves.
Disposal
When data must be deleted (see our Personal Data Protection Policy), it is deleted from the production database. Copies in provider backups expire on the provider’s backup retention cycle and are restored only for disaster recovery.