Your data is yours.
Your business records belong to you. The privacy policy explains what Kwilo holds, why it is used, and when legal or service reasons mean it must be retained.
Trust centre
Plain answers. Real limits.
How Kwilo handles business data, Customer details, AI-assisted features, cookies and service responsibilities. Written in English, not legalese — with the long-form documents linked underneath if you want the full version.
Last reviewed · 8 July 2026
Four things, in plain English.
The approach in four short rules. If anything feels out of line with these, tell us and we will look at it properly.
I never sell it.
Not now. Not later. Not anonymised. Not “aggregated”. Your data is for running your books — not for somebody else's ad targeting.
Handled carefully.
Kwilo is designed for business records, Customer details and money workflows, so access, support and retention need to be handled with care.
You stay in charge.
Important Customer, money and HMRC actions should be reviewed by you or an authorised person before they leave Kwilo. AI helps; it does not take responsibility.
What you can verify today.
Trust is not a badge collection. These are the practical points a cautious user is likely to check before moving business records in.
PointWhat to expectStatus
Early access
The public CTA opens the app sign-in page. That is where early access is requested while rollout is limited.
Rolling outSupport contact
No public support inbox is linked from this site yet. A contact route needs to be added before wider rollout.
Not public yetBilling
Card details are not needed to request access. Subscription billing applies when a user chooses a paid plan.
Not required for accessData export and deletion
Your business records belong to you. The privacy policy explains retention, deletion rights and service/legal limits.
Explained in policyAssistant, not authority.
AI may help with drafting, transcription, summaries or suggestions. It should stay assistive and reviewable, especially around Customers, money and tax.
It is not there to train on your records.Your Customers, Quotes, Invoices and receipts are not there to train general-purpose AI models.
Every output is reviewable.AI-assisted drafts should be reviewed before they are sent, relied on for pricing, or used for tax or compliance work.
Edit, override, or ignore.If a draft is wrong, change it. If a category looks wrong, review it. If a figure matters, check it before relying on it.
Necessary first. Consent for the rest.
The public site should stay light — only what is needed to make it work unless non-essential tools are clearly explained and consented.
No forced wall.Public pages should stay readable without non-essential tracking. If that changes, the notice should explain what is being used and why.
No advertising-tracker default.Advertising or cross-site tracking is not part of the intended setup. If analytics are added, the cookie notice should say so clearly.
Consent should be clear.Non-essential cookies should only be used where a proper consent setup explains what they do and how to manage them.
What I store, why, and for how long.
The practical categories of data Kwilo may hold, why they are needed, and how retention is handled. No surprises buried in a 40-page privacy policy.
DataWhy I have itHow long I keep it
Your account & sign-in
So I know it's you, and to send you receipts & reminders.
Until you deleteQuotes, invoices, jobs
So I can show them, search them, send them and bill from them.
As needed for service or legal dutiesCustomer contact details
So you can email/text them, and I can route invoices & reminders.
While needed for the recordVoice notes & receipt photos
To turn into quotes, categorise expenses, and back up your records.
As explained in policyBilling details
To manage subscription billing where payment is set up.
Handled by payment providersUsage logs
To spot bugs and figure out which features are useful.
As needed to run and secure the serviceLocked on the way, locked at rest.
The security baseline is encrypted transport and appropriate protections for stored business data before wider rollout.
Locked down by default.
Production access is treated as limited and auditable: only people who need it should have it, with logs for support or security investigation.
If something goes wrong.
If a serious incident affects users, the response should explain what happened, what was affected, and what changed afterwards.
The long-form, if you want it.
Plain-English summaries above. Full versions here. Pick the one you need.
Not covered here? Just ask.
A public contact route is not linked here yet. It needs to be added before wider rollout.
Contact route not public yet
Plain-English help before wider rollout