Security and trust
How rupibooks keeps your books safe
rupibooks encrypts your data in transit and at rest, and bank account numbers, sign-in secrets and keys get a second layer of encryption. Your books are hosted on Amazon Web Services in Mumbai, India. 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.
- 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 HTTPS with HSTS. Your database, files and backups are encrypted at rest.
- Bank account numbers, two-step sign-in secrets, API keys and payment-provider keys get a second layer of encryption (AES-256-GCM), with a separate key for each organisation. The master key is kept encrypted in AWS Systems Manager, never in the code or the database.
- 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), a one-time email link or a passkey. Sign-in with Google, Microsoft or Apple is on the way.
- 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-step verification with an authenticator app or a passkey (Face ID or fingerprint on phones), plus recovery codes.
- Every device and session is listed, with "sign out everywhere", and new-device sign-ins trigger an email alert.
- Single sign-on with your own identity provider (SAML or OIDC) is planned for the Business plan.
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, reopening a closed period, changing who's an admin or approving year-end statements, ask you to confirm it's you again.
- rupibooks support staff can open your organisation only while an owner or admin has granted time-limited access. Platform administrators can open it without a grant only to keep the service secure, fix a serious fault or meet a legal duty. Each visit goes into your audit log, with who it was and when.
- Turning off a customer's two-step verification needs a check of who they are and a second member of our team to approve it.
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.
- Documents and questions you send to AI features are processed by Anthropic's Claude API, whose terms don't allow it to train its models on your data.
- 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?
- A full backup of the database every night, stored encrypted in Amazon S3 in Mumbai and kept for 35 days.
- We aim for 99.9% availability each month. A live status page is on the way; until then, service status explains what we monitor.
- If a security incident affects your data, we'll tell you without undue delay, and tell regulators where the law requires.
Where is my data hosted?
On Amazon Web Services in Mumbai, India (the ap-south-1 region): the servers that run rupibooks, your files and the nightly backups. The database is MongoDB Atlas, also running on AWS in Mumbai. Emails are sent through Zoho Mail's EU data centre, and AI features use Anthropic in the United States. The privacy notice lists every provider, where it works and the safeguards for data sent abroad.
Which standards do you follow?
- Built to OWASP ASVS Level 2. We haven't had an independent penetration test yet. We plan the first one within our first year, then one every year.
- Strict Content Security Policy, CSRF protection and input validation at every boundary.
- The UK GDPR and Sri Lanka's Personal Data Protection Act. See the privacy notice.
- 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 your reports, invoices, registers and year-end packs (CSV, Excel and PDF) at any time, or use the API on paid plans. For a full copy in one go, email support@rupibooks.com. Cancelling never deletes your books: you move to the Free plan and can still see them.
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.