Skip to main content
Pay less than Zoho Books, with Sri Lankan tax built in. Growth is LKR 3,390 a month.See pricing →

Security and trust

How rupibooks keeps your books safe

rupibooks encrypts your data in transit and at rest. Salaries, bank account numbers and NIC numbers get extra field-level encryption. Every change goes into an audit trail that can't be edited, and we keep it for at least 7 years. rupibooks is built to OWASP ASVS Level 2, with an independent penetration test before launch and every year after that.

  • EncryptedIn transit and at rest
  • Audit trailEvery change recorded
  • Two-factorSign-in you control
  • Your dataExport it any time

How is my data encrypted?

  • Everything travels over TLS 1.3 with HSTS, and is encrypted at rest.
  • Salaries, bank account numbers and NIC numbers get extra field-level encryption, with keys held in a cloud key management service.
  • Receipts, statements and PDFs are kept in encrypted storage and served through signed links that expire quickly.

How do people sign in?

  • Email and password (at least 10 characters, checked against known-breached password lists without the password ever leaving our server), Google, Microsoft, Apple, or a one-time email link.
  • Passwords are hashed with Argon2id. Sign-in is built in-house on audited cryptographic libraries; there is no third-party identity vendor in the login path.
  • Two-factor authentication with an authenticator app or a passkey (Face ID or fingerprint on phones), plus recovery codes. SMS codes are offered only as a fallback because of SIM-swap risk.
  • Org admins can require 2FA for everyone or for chosen roles, such as anyone who approves payments.
  • Every device and session is listed, with "sign out everywhere", and new-device sign-ins trigger an email alert.
  • SAML and OIDC single sign-on with your own identity provider on Business.

Who can see my books?

  • Only the people you invite, with the role and limits you choose. Roles cover each module separately (create, edit, approve, post, delete, export), with value limits such as "approve bills up to LKR 500,000".
  • Sensitive actions such as changing bank details, unlocking periods, adding admins and bulk exports ask for re-authentication.
  • rupibooks staff can open your organisation only after the owner grants time-limited access. Every screen they open is logged and visible to you.
  • rupibooks' own platform staff must use single sign-on with a hardware security key. For them, 2FA is never optional.

How is my data kept apart from other businesses?

Every record carries your organisation's ID, and rupibooks refuses any database query that doesn't include it. This is enforced in the code and while it runs. On every change, automatic tests try to reach other organisations' data and must fail.

How is the ledger protected from tampering?

  • Posted entries can't be edited or deleted. You correct them with a reversal, credit note or adjusting journal.
  • Each organisation's posted entries are hash-chained, and a nightly job verifies the chain and alerts our platform team to any break.
  • The audit log is append-only and stored separately from the books. No one in your organisation, including the owner, can edit it. See controls and audit.

How is AI used with my data?

  • AI is included and rupibooks runs it. There's nothing for you to manage.
  • We send the AI as little personal data as possible. Bank account numbers, for example, are masked unless the task needs them.
  • AI agents draft and suggest. They never post directly, and every action checks the user's permissions.
  • Every AI action is logged with the model, prompt version and confidence.

What if something goes wrong?

  • Point-in-time recovery for 35 days, a daily backup to a separate region, and a restore drill every quarter.
  • A target of 99.9% availability each month, with a public status page.

Where is my data hosted?

In a cloud region close to Sri Lanka (Mumbai or Singapore), with a backup region. We'll choose the final region after checking Sri Lanka's Personal Data Protection Act for any data-localisation rules, and we'll name it here once it's decided.

Which standards do you follow?

  • Built to OWASP ASVS Level 2, with an external penetration test before launch and yearly after that, plus a public vulnerability disclosure programme.
  • Strict Content Security Policy, CSRF protection and input validation at every boundary.
  • Sri Lanka's Personal Data Protection Act.
  • We aim to get ISO 27001 and SOC 2 Type II within 18 months of launch. We don't hold either certification yet.

Can I take my data with me?

Yes. Export everything (CSV, Excel, JSON and PDF statements) at any time, including for 90 days after cancellation.

How do I report a security issue?

Email security@rupibooks.com with the details. Please don't test against other customers' data.

See how rupibooks fits your business

Start free in minutes, or get a demo instantly. It opens right away with sample books for a business like yours.