Exporting your data and avoiding lock-in
Getting started · 3 min read
What real data ownership looks like — one-click JSON export, your own payment accounts, and your own AI keys — plus a practical checklist for evaluating lock-in in any client tool.
The best time to think about leaving a tool is before you join it. Lock-in rarely announces itself; it accumulates as your proposals, contracts, time logs, and invoices pile up inside software that makes leaving just hard enough that you never quite do. This guide is about the opposite stance — keeping your data, your money, and your AI portable — and it doubles as a checklist for evaluating any client tool you're considering, Kliently included.
Your data: one-click JSON export, anytime
The clearest test of data ownership is simple: can you get all of it out, right now, without asking permission or filing a support ticket? In Kliently the answer is a one-click JSON export, available anytime, covering your workspace data. JSON matters because it's structured and machine-readable — you can move it into another system, back it up, or hand it to a developer, rather than receiving a locked PDF that's technically "your data" but practically inert.
Export is one click, on demand — not a queued request you wait days for.
JSON is portable: structured, readable, and re-importable elsewhere.
Because you can always leave, staying is a choice, not a trap.
Your money: payments flow to your own accounts
Data lock-in gets the headlines, but money lock-in is sneakier — when a platform sits in the middle of your payments, switching tools can mean disrupting how you actually get paid. Kliently takes itself out of that path: you connect your own Stripe, PayPal, Wise, and the regional rails, and money flows directly to your accounts. Kliently is not in the middle of the money.
That design has a quiet but important consequence for lock-in: your payment relationships belong to you, not to the tool. If you left tomorrow, your Stripe account, your customers, and your payout history all stay exactly where they are. Six rails — Stripe, SSLCommerz, Razorpay, PayPal, Wise, and manual bank transfer — and 18 currencies synced daily, all pointed at accounts you own. See the full setup in invoicing.
A tool that holds your money has more leverage over you than one that holds your data. Make sure you own both paths out.
Your AI keys: bring your own, keep your prompts
AI features are a newer flavor of lock-in, and a subtle one — if a tool runs AI on its own keys and stores your prompts, your content is feeding someone else's system. Kliently's AI assist is bring-your-own-key: you supply your own OpenAI, Anthropic, or Google key. Those keys are encrypted at rest, and your prompts are never stored or used for training. You get AI drafting on your terms, and if you switch tools you simply take your key with you.
A checklist for spotting lock-in
Use these questions on any client tool you evaluate. The answers tell you how free you'll be to leave long before you've committed years of work to it.
Can I export all my data, on demand, in a structured format like JSON?
Does my money flow to my own accounts, or does the platform sit in the middle?
If there's AI, whose keys run it, and are my prompts stored or used for training?
How many clicks and how many days does it take to leave — honestly?
Is my data protected while I'm in (encryption, isolation, an audit trail) so it's worth keeping?
Ownership is a feature, not an afterthought
Notice that none of these protections cost you anything while you stay — they simply mean staying is a decision you keep making, not one you got cornered into. Kliently pairs that portability with real protection of the data while it's there: secrets encrypted with AES-256-GCM, workspace isolation, Postgres row-level security, and an append-only audit log of sensitive actions. Strong security and easy exit aren't in tension; together they're what "your data is yours" actually means. Read more on how Kliently secures your workspace.