Security

How we protect the books you keep in EasiBooks.

Your data in transit and at rest

• Every connection to EasiBooks is encrypted with HTTPS.
• Passwords are never stored. We keep only a one-way bcrypt hash.
• Backups are made every day, stored encrypted with Amazon Web Services, and restores are tested.
• Uploaded files, such as receipts, are kept in versioned storage, so an overwritten or deleted file can be recovered.

Each company kept apart

Every company's books are kept apart from every other company's. A user sees a company only when an administrator of that company has added them, and only with the role they were given.

Controls inside the books

• Activity log: every change is recorded with who made it and when. Each entry is chained to the one before it, so any later change to the log can be detected.
• Closed periods: once a period is closed, entries cannot be posted into it. Reopening one is itself recorded.
• Approvals: companies can require a second administrator for sensitive actions, such as large payments, stock adjustments, or loosening a control.
• Sign-ins: users can see where their account is signed in and end any session.

Payments

EasiBooks never sees card or bank account numbers. When a customer pays an invoice online, they pay on a page run by Stripe, into the company's own Stripe account.

The AI assistant

The assistant works only inside the companies the user can reach, with the same role. Each company decides what it may do on its own and what needs a person's approval, and its actions are recorded in the activity log.

Reporting a problem

If you believe you have found a security problem, please write to support@easibooks.com. We will answer promptly and keep you informed while we fix it.