Skip to content
Titus Ledger
Join

Security

How Titus Ledger is being built to protect your books

Titus Ledger is in development. This page sets out the design commitments it is being built to, and what is running today. We'll keep it up to date as the product is built.

Design commitments

Bookkeeping software has to be trustworthy in two ways: nobody should reach books they shouldn't, and nothing already recorded should quietly change. These are the rules the product is being built around.

  • Hosted on Google Cloud, in the US

    Titus Ledger will run on Google Cloud, through Firebase, and your books will be stored in Google's data centers in the United States.

  • Encrypted in transit and at rest

    Every connection to Titus Ledger will use HTTPS, and Google Cloud will encrypt the data we store at rest.

  • Every change goes through our server

    Your browser will never write to the database. Every change will go to our server, which will check who you are and what your role in that company allows before anything is saved.

  • Roles, not shared passwords

    Everyone who works on the books, your accountant included, will have their own sign-in and a role (owner, admin, accountant, bookkeeper or viewer) that sets what they can see and do.

  • Posted entries are never edited or deleted

    A mistake will be corrected with a reversing entry, so the original and the correction both stay on the record and past reports never change underneath you.

  • An audit log of every change

    Each change will be recorded with who made it, when, and what it was before and after. The audit log itself won't be editable.

  • A closing date that locks past periods

    Once you set a closing date, nothing on or before it will be able to change unless an owner or accountant overrides it for one entry and gives a reason, and the override will be logged.

  • Point-in-time recovery and daily backups

    Recent changes will be recoverable to a point in time, daily backups will cover the weeks before that, and a monthly archive copy will be kept in a separate Google Cloud project for 7 years.

  • Export everything, any time

    You'll be able to download all of a company's records, the audit log and its main reports whenever you like, and keep read-only access for 7 years after you cancel.

What's running today

Right now there is this website, its waitlist, and the private beta's invite-only accounts: sign-in, companies and the people who work on them. The bookkeeping screens are still being built.

  • Everything you send goes over HTTPS to our server, which checks it before storing it. Browsers can't write to our databases at all, and a signed-in browser can read only its own account and the companies it belongs to, as its role allows.
  • To stop the form being flooded, we limit sign-ups per connection using a keyed hash of the IP address, not the address itself.
  • Nothing on the site runs analytics or advertising scripts. The website sets no cookies; Titus Ledger sets one, for your sign-in session, which scripts on the page can't read.

Who handles data for us

  • Google Cloud hosts the site and Titus Ledger, and stores, in the United States, the waitlist's sign-ups, the shared Titus accounts (the one sign-in for TitusChat, TitusVoice, TitusFax, Titus Contacts and Titus Ledger, run by Titus Hub Inc.), and Titus Ledger's companies, their members and invitations, and each company's books, in Cloud SQL.
  • Brevo delivers our email: the waitlist's confirmation, account confirmations and password resets, and invitations to join a company.
  • Cloudflare runs the DNS for titusledger.com, which points the address at our hosting, and forwards email sent to our titusledger.com addresses, including sign-up notifications, to our mailbox.

The Privacy Policy has the detail, and it will list every provider that handles your books before Titus Ledger opens.

Report a vulnerability

If you think you've found a security problem in titusledger.com, please tell us privately so we can fix it.

  • Tell us what you found, where, and the steps to see it, with any proof of concept.
  • Please don't access, change or delete data that isn't yours, don't degrade the site for anyone else, and give us a reasonable time to fix the problem before you share it.
  • We'll confirm we received your report and keep you updated while we work on it. We don't run a paid bug bounty.

Security contact

For vulnerability reports only. For anything else, see Contact.
security@titusledger.com

Also published in security.txt.

Questions about how your books will be kept?

Join the waitlist to follow along, or call us and ask. We'd rather explain a design decision than have you guess.

Join the waitlistCall 631-977-7400