Built to be trusted with the money part.
Kliently handles contracts, client data, and payments — so security isn't a feature page, it's an architecture decision made at every layer.
Security isn't a feature here — it's the architecture.
Kliently holds contracts, client data, and the money path. Those stakes shape every layer of the system, from the database row to the payout.
Workspace isolation by default
Every table is guarded by Postgres row-level security and every query is scoped to your workspace — isolation is enforced at the database, not just in application code.
Encrypted in transit and at rest
Traffic runs over TLS. Sensitive secrets — payment credentials and AI keys — are encrypted with AES-256-GCM, and the encryption keys live in the server environment, never in the database.
Least-privilege access
Owner, admin, member, and contractor roles draw hard permission walls. Contractors see only their own projects and time — never client lists, margins, or invoices.
Append-only audit trails
E-signature events and sensitive actions are written to append-only logs — capturing IP, device, country, and timestamps — that can't be edited after the fact, even by us.
Your data, never locked in
Export everything as JSON in one click, any time, and delete your workspace whenever you choose. Your data is yours to take, and yours to remove.
Your money and keys stay yours
Payments flow to your own Stripe, PayPal, and local accounts — Kliently is never in the middle. Bring your own AI keys; they're encrypted at rest and never used to train anything.
What protects your data, layer by layer.
No single control carries the weight. Here is what is actually in place across the stack.
Data protection
- Postgres row-level security on every table
- Every query scoped to your workspace
- AES-256-GCM encryption for secrets at rest
- TLS encryption for all data in transit
Access & authentication
- Passwordless magic-link access for clients
- Per-client portal tokens you can rotate at any time
- Owner / admin / member / contractor roles
- Permission walls keep contractors out of client data
Payments
- Connect your own Stripe, PayPal, and local providers
- Money settles to your accounts, not through Kliently
- Payment webhooks are signature-verified and deduplicated
- Card data is handled by PCI-compliant providers, never stored by us
Integrity & audit
- Append-only e-signature audit trail (IP, device, country, time)
- A signature certificate embedded in every final PDF
- Append-only audit log of sensitive account actions
- Meets the US ESIGN Act and eIDAS simple e-signature standard
Your data, your money, your keys.
The strongest security guarantee is the one you control. Kliently is built so you can walk away with everything, whenever you want.
Export anytime
One-click JSON export of every client, proposal, contract, time entry, and invoice — no support ticket required.
Delete anytime
Close your workspace whenever you like and your data is removed. No retention hostage-taking, no lock-in.
Bring your own AI keys
Use your own OpenAI, Anthropic, or Google key. Keys are encrypted at rest, and prompts are never stored or used to train models.
See exactly what each client can view in the client portal, or read our privacy policy for how data is handled.
Infrastructure
Kliently runs on its own PostgreSQL database and authentication system — no shared multi-tenant black boxes. Data is encrypted in transit with TLS and secrets are encrypted at rest with AES-256-GCM. Payment webhooks verify each provider’s signature and are deduplicated for idempotency.
Reporting a vulnerability
Found something? Email security@kliently.app. We aim to respond within 48 hours, we’ll keep you posted on the fix, and we won’t pursue good-faith security research.
Run your business on something you can trust.
Start free — no credit card, your data exportable from day one.