Most tools in this category start by asking for your accounting login or a live connection to your bank. DueBell asks for two files and a way to reach your clients. This page lists exactly what that means: every field we store, everyone who could ever look at it, how you take it all back — and which rules apply in your country and your client’s.
Not through open banking, not through a read-only feed, not through a third-party aggregator. There is no connection to revoke because there was never one to begin with.
You log into your own online banking, download a statement — CSV, OFX, QFX or camt.053 — and upload that file to DueBell. It is read once, compared against your open invoices, and used for one purpose: to mark paid invoices as paid so nobody gets chased for money they already sent.
We never see your banking credentials, cannot initiate a payment, cannot look at your balance between uploads, and cannot see any account you did not export yourself. If you stop uploading, DueBell simply stops learning anything new about your money.
What ends up storedInvoices on one side, a statement file on the other. Nothing on this screen asks for a password to anything.
We hold no banking logins, no OAuth tokens to your bank, no API keys into your accounts. A breach of DueBell cannot become access to your money.
No background sync, no overnight pull. Between your uploads, DueBell’s picture of your finances simply stops at what you last handed over.
Transactions are compared to open invoices and then kept as the audit trail behind “paid”. They are not profiled, not scored, not sold, not used to train anything.
A client in DueBell is a name and a way to reach them. That is a deliberate limit — the less we hold, the less there is to worry about, on both sides.
Minimising data does not mean hiding it from you. Everything above is visible in your own account, in plain language, at any time — and exportable in one click. Data minimisation is about what leaves your hands, not about what you are allowed to see.
The honest version: a support engineer can, in principle, reach your records — that is true of every SaaS you have ever used. What matters is under which conditions, and whether you find out.
Support access to your data is opened only when you ask for help with a specific case, and only for that case.
The access window closes automatically when the ticket does. Nothing stays open “in case it comes up again”.
Every access is recorded — who, when, which records, which ticket. You can request that log for your own account.
Team roles are scoped to the job. Nobody has standing access to production data as part of their daily work.
Every internal system requires two factors and hardware-backed keys. No shared logins, no exceptions for founders.
Your invoices, clients and statements are not sold, not shared with advertisers, and not used to train any model.
Photo placeholder
Owner at a kitchen table with a laptop, exporting a statement — private, unglamorous, real
That was the starting point for DueBell. Not a compliance checklist — a specific feeling that most owners of small service businesses recognise instantly, and that almost no finance tool takes seriously.
So the product was designed backwards from it: connect to nothing, ask for the minimum, and let people leave with everything. It costs us a bank integration we would otherwise have. We think that is the right trade.
The unremarkable part, spelled out anyway — because “we take security seriously” is not information.
Every connection to DueBell — browser, upload, webhook, API — runs over TLS 1.3 with HSTS. No plaintext route exists, including for file uploads.
Databases, uploaded invoice files and statement exports are encrypted at rest with AES-256, on managed infrastructure with hardware-isolated storage.
Your account data is held in the EU whether you invoice from Manchester, Austin, Toronto or Auckland. Where delivery requires a transfer — an SMS to a US number, for instance — it happens under standard contractual clauses. Encrypted backups roll for 30 days and are then destroyed, including after you delete your account.
Sending an email or an SMS means a third party carries it. Here is every company involved, what they handle, and what they never see.
| Provider | What it does | What it can see | Data location |
|---|---|---|---|
| Email delivery | Sends your reminder emails and receives replies on per-invoice addresses | Message content, client email address, delivery status | EU · global delivery network |
| SMS delivery | Sends reminder texts on registered sender IDs | Message text, client phone number, delivery status | EU · US · regional carriers worldwide |
| Hosting | Runs the application and the encrypted database | Encrypted storage only — no application-level access | EU (Frankfurt) |
| Payments | Charges your subscription | Your card and billing details — never your invoices or clients | EU · US |
| Product analytics | Counts feature usage so we know what to fix | Anonymised events only — no invoice amounts, no client names | EU |
This list is versioned. When a subprocessor is added or replaced, the change is published here and on the changelog before it takes effect — not quietly, and not after the fact.
Export is a button, not a support ticket. Deletion is permanent, not a flag on a row that stays in our database forever.
Deletion: your records are removed from the live system immediately and from encrypted backups within 30 days, as the rolling backup window expires. Billing records are kept only as long as tax law requires, and nothing else survives.
DueBell messages people on your behalf, in your name, about invoices you issued. That is a different legal animal from debt collection, and we keep it that way on purpose.
We do not buy debt, do not report anyone to a credit bureau, do not add fees on our own initiative and never threaten legal action in your name. Every message is a reminder you could have written yourself.
Registration, sender format, opt-out wording and quiet hours are chosen by your client’s country — not by yours. If a rule cannot be satisfied for a given number, DueBell sends email only rather than sending something non-compliant.
You are the controller of your client data and we are the processor, under whichever regime applies to them. A data processing agreement is available on request, and any access, correction or deletion request can be honoured from your own account.
| Where your client is | How SMS is sent | Sending window | Privacy regime |
|---|---|---|---|
| United States | A2P 10DLC campaign registered to your business, with STOP handling | 8:00–21:00 in the recipient’s timezone | CCPA / CPRA where applicable |
| Canada | Carrier-registered long code, bilingual opt-out on request | Business hours, recipient’s timezone | PIPEDA · CASL for consent |
| United Kingdom & Ireland | Alphanumeric sender ID showing your business name | 8:00–20:00 local | UK GDPR & PECR · GDPR in IE |
| EU / EEA | Alphanumeric sender ID, per-country registration where required | 8:00–20:00 local | GDPR |
| Australia & New Zealand | Sender ID with unsubscribe facility in every message | Business hours, no public holidays | Privacy Act 1988 · NZ Privacy Act 2020 |
| Everywhere else | Email by default; SMS enabled once carrier rules for that country are met | Working hours, recipient’s timezone | Local law, plus our DPA |
Everything on this page is the plain-language summary. The binding documents — privacy policy, terms of service and the data processing agreement — say the same things in the language lawyers need, and are linked in the footer of every page.
Photo placeholder
Close-up of a phone showing a reminder SMS as a client would receive it — plain, polite, signed by the business
No, and it is not a policy choice — it is architecturally impossible. DueBell has no connection to your bank, no credentials and no payment initiation capability. It reads a file you exported yourself. The only thing it can do with money is tell you that some of it arrived.
The transactions relevant to your open invoices are kept as the audit trail behind each “paid” status, encrypted at rest. You can delete an uploaded statement at any time from the upload history; matched invoices keep the match, without the underlying line.
Messages go out in your business name, in wording you approved, from your address or a reply address that reaches you. We do not brand your reminders, do not add “sent via DueBell” and do not contact your clients for our own purposes — ever.
No. AI is used in one place only: helping you draft reminder templates when you set up your account, on text you provide. Your invoices, clients, statements and message history are never used as training data, by us or by anyone else.
A fair question that most vendors dodge. Your export works at any time and gives you everything in open formats, so there is no state where your records exist only inside DueBell. If we ever wound the service down, you would get notice and a window to export before anything was deleted.
Free for your first 5 invoices a month. No card, no bank connection, no accounting software.
Sign up free