Security
How we protect your books.
Your books hold your business. Here is exactly what we do to keep them safe, in plain language, with nothing we cannot back up.
Last updated October 13, 2026
Encryption
You see
•••-•••-482
Stored
enc:v1:q8Zt…:4fXa…:9fK2…
- Receipts and documents at restAES-256
- Everything in transitHTTPS
- Sensitive fields like SIN
- Face ID or fingerprint on mobile
Encrypted at rest and in transit
Receipts and documents are stored encrypted with AES-256. Everything between your device and NumKeep travels over HTTPS, and backups are encrypted. Sensitive fields, such as a Social Insurance Number, are encrypted one by one before they are saved to the database.
Where your files live
Receipts and documents are stored with Cloudflare R2 in Eastern North America. We never sell your information, and we do not share it with advertisers.
Your company, walled off
Every record belongs to exactly one company, and every request is checked against your membership in it. Roles decide who can change your books and who can only read them.
Signing in
Sign in with your email, Google or Apple. On the mobile app, you can lock NumKeep behind Face ID or your fingerprint.
Receipts and AI
An OCR service reads each receipt to pull out the vendor, date and amounts. Nothing posts to your books until you review and approve it.
Tested against real attacks
In September 2026 we reviewed the whole API against common attack patterns, from broken access control to injection and race conditions, and shipped fixes from that review.
Found a security issue?
If you find a vulnerability or have a concern about your data, write to our security team. We read every report.
[email protected]