Security
Integrity first, because these are financial records.
Most of what protects your books here is built into how the data is stored, rather than left to the software to remember. The database itself turns away anything that would leave your books wrong.
Integrity
Wrong data can't be written in the first place
These are hard rules, not habits. A bug in a feature can't get around them.
Entries can't be saved unbalanced
Both sides of a transaction have to agree before it’s stored, and that’s checked as it’s written. A half-recorded entry can’t exist, even if something fails mid-save.
One org can't see another's books
Every line of your ledger is tied to your organization in the data itself. Data from another organization can’t end up in your reports, whatever the software does.
Whole cents, all the way through
Money is stored and added up as whole cents from end to end, so there’s no rounding quietly accumulating into a difference nobody can account for.
A log that only grows
Every entry, edit and void is recorded with who did it and when, and nothing removes an entry from that record.
Void, never delete
Correcting a transaction voids it and leaves the original in place. History doesn’t silently change under a report you already filed.
Closed periods lock
Close a month or a year and entries on or before that date are refused. Last year’s filed numbers stay the numbers you filed.
Access
Fewer ways in means fewer ways in
No passwords to steal
Sign-in is a one-time code sent to your email. There is no password database to breach, reuse or phish, and codes expire in ten minutes.
Roles that actually restrict
Owner, admin, member and accountant. The accountant role really is read-only — it’s enforced where the data lives, not by hiding buttons.
Checked on every request
Who you are and what you’re allowed to do is worked out on our servers, the same way, every single time. A browser can ask for another organization’s data; it will not get it.
Infrastructure
Where your data lives
Named plainly, so you can evaluate it yourself.
Due North runs on Vercel, with Postgres hosted by Neon in the United States. Traffic is encrypted in transit with TLS, and data is encrypted at rest by the database provider. Email delivery is handled by Resend and payments by Stripe — card details go directly to Stripe and never touch our servers or our database.
The full list of third parties that can process your data, and what each one is used for, is on the subprocessors page.
What we don’t claim: Due North is a small, independent product and has not been through a SOC 2 audit or a third-party penetration test. If your business needs either, you should know that before you sign up rather than after. What is written above is a description of how the system is built, and it can be verified by asking pointed questions — which we will answer.
Reporting a problem
Found something? Tell us.
Security reports get a reply within two business days. We won't threaten you for looking, and we'll credit you if you'd like to be credited.
Start with your real books.
Set up a set of books free, run a real month through it, and see whether the reports come out the way you expect.