Workspace isolation
Customer records are scoped to their Workspace. Database row policies and server-side authorization checks are designed to prevent one tenant from reading or changing another tenant's data.
Data & Security
Clear controls. Honest boundaries.
Klosent combines tenant isolation, role-aware authorization, protected Connections, and redacted operational reporting. This page explains the controls in place without claiming certifications Klosent has not earned.
Core controls
Security follows the work.
Controls are applied across the interface, server actions, route handlers, database access, Connections, and background operations.
Role-aware access
Platform admin, agency admin, manager, member, operator, and customer-facing roles receive different permissions. Sensitive actions are checked again on the server, including direct requests that bypass the interface.
Authentication and sessions
Authentication is handled through Supabase Auth. Private routes require a valid session, and session checks are designed to reject revoked or expired access on the next protected request.
Protected Connections
Provider credentials and API secrets stay on the server. Hosted account authorization returns provider account identifiers that are bound to the intended Workspace and Seat; secrets are not sent to the browser.
Redacted operational logs
Application reporting removes common credentials, authorization values, direct contact details, message content, and sensitive URLs before structured error context is written or forwarded.
Bounded background work
Queues, retries, imports, exports, and provider operations use bounded batches and explicit status records. Provider-dependent actions remain unavailable until the required Connection and delivery setup are approved.
Data handling
What the platform handles, and why.
| Data category | Purpose | Primary control |
|---|---|---|
| Account and Workspace data | Authentication, access control, product operation, and support | Role and tenant scope, protected private routes, server validation |
| Customer CRM and outreach data | Kontacts, companies, deals, Kampaigns, Konvos, and Outkomes | Workspace scope, role checks, row-level database policies |
| Connection identifiers | Attach an approved mailbox or LinkedIn account to the correct Seat | Server-side hosted authorization, signed state, lifecycle checks |
| Billing metadata | Plan and account lifecycle | Payment providers process payment details; Klosent stores limited operational metadata |
Privacy and data requests
The Privacy Policy explains data categories, purposes, retention, subprocessors, and available rights. To request access, correction, deletion, or suppression, contact privacy@klosent.com.
Read the Privacy PolicyReport a security concern
Send a clear description and the affected page or Workspace to privacy@klosent.com. Do not include passwords, API keys, provider secrets, or sensitive message content.
No online service can guarantee absolute security. Klosent reviews confirmed issues and updates controls as the platform changes.