Security
Your records are yours.
A shop's books are private. This page says what protects them and, just as plainly, what has not been proven yet.
Only your shop reads your shop
Access rules sit in the database itself, not only in the app. Even a tampered phone cannot read another shop.
Roles with limits
Owner, manager and seller each see and change only what their job needs. Staff sign in with one-time codes. Every change is logged.
A second step and a PIN
Owners can turn on an authenticator app; the database then refuses access until it is done. A PIN lock guards a shared phone.
Receipts that prove themselves
A code opens a public check page: genuine, changed or removed, and nothing else about the shop.
Clean input only
Names and text accept letters, numbers and a few marks. Emojis, code characters and hidden characters are stripped as you type, and the database refuses them too.
Photos kept private
Page photos go to a private store, are read once, and are removed 30 days after the page is confirmed. The rows stay.
Be honest
What is not proven yet.
- No independent security audit. We test every change ourselves with 430 attack-style checks and 263 automated tests.
- Handwriting accuracy has not been measured on a large set of real notebooks.
- It is an early version with no paying customers yet. The privacy notice and terms are drafts for a lawyer.
Found a problem?
Send what you found and how to repeat it, and please do not look at other people's records while testing. We would rather hear it from you first.
Report it by emailThe tests we run
Weekly open-source scans (Gitleaks, Semgrep, OWASP ZAP, Nuclei), strict headers graded A+ by Mozilla Observatory, and our own checks that try to break access rules on the live app.
Security you can ask about.
Ask us anything, or try the app with a made-up shop.