Help › Account and privacy › Security
Security: who can see your data
Heft reads your bank account and your mailbox so it can find the receipt for every payment. Here's what Heft never does, who can see your data, and how you stay in control.
Updated 13 Nov 2026
What Heft never does
- Move money
- Bank accounts are connected read-only. Qonto is the exception: its API key could also move money between your company's own Qonto accounts, but Heft only sends read requests with it. You make payments yourself.
- Send or delete mail
- Your mailbox is connected read-only. Heft can't send, change, delete or move anything in it.
- Read accounts you don't pick
- Nothing is pre-ticked when you connect; you tick the company's accounts yourself. Heft never reads the payments or balances of any other account, including your private one.
- Send anything without you
- Letters to others, such as cancelling a subscription, can only be sent by a person, never by Heft alone. They go out from Heft's address, with you in copy.
Who can see your data
- Heft support
- Only if you grant it, as the owner or a director. Support can then read but change nothing, for 30 days at most. You can end the access early at any time.
- Heft's team
- Reads records of Heft's work, to find and fix its mistakes: what the AI model was given and answered, with the tools it used and their results. These can include your messages, payments and receipts. They are kept with PostHog in Frankfurt, in full for 30 days.
- What you send Heft
- If you report a part of the chat, Heft's team reads that copy, for 90 days. If you ask Heft to find you a tax adviser, a person at Heft sees your question and the payments and receipts it names, for 30 days at most.
- Anyone else at Heft
- Nobody opens your books, except where security, such as investigating abuse, or the law requires it.
- Your team
- Each member sees what their role allows. An assistant helps match receipts but can't lock a month or change access.
- Your tax adviser
- They see your books and work only on what their mandate covers, such as bookkeeping or VAT. They can never change access or your company details.
How you find out
When someone or something gets access, whether a member, a tax adviser, an AI agent or a login for a supplier portal, the owner and directors get an email straight away, and a push notification where notifications are on. The message names only the kind of access, so nothing confidential shows on a lock screen. You see who it is in the app.
What Heft itself does is listed under Activity, each with Undo.
Signing in and approving
You sign in with a code Heft emails you. There is no password.
You approve important steps yourself: connecting a bank, saving a login for a supplier portal, locking a month, sending something or accepting a proposal from Heft. Heft first shows you in words what you're approving, and one tap approves it.
Heft keeps a record of every approval: who gave it, when, in which session, and the exact text you were shown. So it can always be shown later who approved what.
If someone takes over your mailbox
Because the code comes by email, whoever controls your mailbox can sign in. They can then act in Heft as you, including approving steps. So protect your mailbox well, for example with two-step sign-in at your email provider.
When someone signs in with an email code, your devices that are already signed in get a push notification, where notifications are on. When someone gets access to your company, the owner and directors hear about it straight away, as described above.
For more protection, add a passkey under Settings › Account. With it you sign in with Face ID, your fingerprint or your device's screen lock; your face or fingerprint never leaves your device. Once you have a passkey, a sign-in by email code can't send anything, change access or save logins for you. Your mailbox alone is then not enough for that.
Encryption and login details
Every connection to Heft and between Heft's services is encrypted, and stored data is kept encrypted on Google Cloud.
Login details, such as your mailbox's app password, a bank's API key like Qonto's or a supplier-portal login, get an extra layer: Heft encrypts them with a key of their own, kept apart from the database. A copy of the database can't open them.
Heft uses a supplier-portal login only to fetch invoices there: in a fresh, sealed-off browser that can reach only that portal and is deleted afterwards.
If your phone is gone
Whoever has your phone and can unlock it can approve in Heft while it's signed in. So sign it out as soon as it's gone: under Settings › Account you see every signed-in device and can sign each one out, or tap Sign out everywhere. That's also where you remove a passkey. On a new device you sign in again with an email code.
If you added passkeys and have lost them all, you recover your account by email. That takes 24 hours, and the owner and directors are told straight away. If someone signs in with your passkey in the meantime, the recovery is cancelled.
Disconnecting
Under Settings › Connections you disconnect your bank or your mailbox at any time; a bank is disconnected by whoever connected it. Heft then stops reading from it within minutes. Bank access also ends on its own; the app shows you when. A bank's API key, like Qonto's, has no end date: Heft uses it until you disconnect the bank or the bank stops accepting it, then deletes it.
Where it's processed
Your data is stored on Google Cloud in Frankfurt, and the AI models, Claude and Gemini, run on Google Cloud in the EU. None of it is used for AI training.
Three service providers are US companies: Resend for email, PostHog for the records of Heft's work, and Browserbase for the browser on your suppliers' websites. With them, your data can be processed in the United States or reached from there. The privacy policy says how that is safeguarded; for Browserbase there is no safeguard yet.
Found a security issue? Write to support@namequick.app.
Data and privacy