Role-based permissions
Separate who writes playbooks, who approves exceptions, and who can change connections or thresholds. Approval rights are never implicit.
Permissions
Automation you can audit line by line.
Sending on your behalf is a serious permission. This page describes how that permission is bounded, what is recorded, and what DueHello does not do.
One action. Three enforced layers.
Change the invoice, then inspect the rule, approval and evidence behind the decision.
Permission engine live
InvoiceINV-2455
€8,940 - Client
- Kesselring Partners GmbH
- Relationship
- Tier A
- Next action
- Reminder 2
Inside automatic threshold
Rules · 4 checks passed
Amount, quiet hours, relationship tier and stop conditions permit the next reminder.
Action permitted
What bounds every automatic action.
Six controls, each enforced by the product rather than by policy alone.
Complete audit history
Every rule change, automatic send, approval, pause and stop is recorded with an actor and a timestamp, and can be exported.
Bounded sending
Quiet hours, maximum touches, per-client caps and stop conditions apply to automatic actions exactly as they do to manual ones.
Data minimisation
Invoice and contact data only, held to do the job. No ledger, no payroll, no bank access, no payment initiation.
EU processing
Data is processed inside the EU. Sub-processors are listed publicly and change with notice.
Deletion on request
Workspaces and their history can be exported and deleted. Deletion covers drafts, logs and synced invoice data.
What DueHello will never do.
These boundaries are part of the product, not a promise in a policy document.
Boundary 01
Send without a mode being switched on
A new workspace starts in Draft. Nothing reaches a client until someone deliberately enables Assisted or Autopilot.
Boundary 02
Contact anyone outside your contact list
No enrichment, no guessing at addresses, no contacting a payer you have not recorded.
Boundary 03
Take a legal step on its own
Collection and legal routes are prepared and evidenced. Triggering one is always a human decision.
Boundary 04
Move money
DueHello has no payment rails and no bank credentials. It asks for payment; it never takes it.
Boundary 05
Create or send invoices
DueHello is not an invoicing tool and does not replace your accounting system. Your ledger stays the source of truth; DueHello is the follow-up layer between sending an invoice and being paid.
Boundary 06
Act as a debt collection agency
Collection and legal routes are prepared and evidenced, never executed. DueHello does not buy debt, does not collect on your behalf, and does not give legal advice.
Controls in place today.
Formal assurance is listed only when independently verified. The product controls below are active now.
EU-only processing
All processing and storage inside the European Union. Sub-processor regions are listed on the Legal page.
LiveRole-based access control
Separate rights for writing playbooks, approving exceptions and managing connections.
LiveImmutable audit log
Every rule change, automatic send and approval recorded with actor and timestamp. Exportable.
LiveData minimisation
Invoice and business-contact data only. No ledger, no payroll, no bank credentials, no payment initiation.
LiveBounded automatic sending
Quiet hours, maximum touches, per-client caps and stop conditions apply to automated actions too.
LiveExport and deletion
Workspaces, logs and synced invoice data can be exported and permanently deleted on request.
LiveRead the details with your team.
We will walk your security reviewer through permissions, logging and sub-processors before you connect anything.
Book a demo