Security & trust
Trust starts with records that stay private, traceable and explainable.
Berlvis Books handles business records, customer balances and payment history. This page separates product behavior we can explain today from claims we will not make without evidence.
No certification theatre. No invented compliance badges. No vague security promises presented as facts.
What matters
Security is more than hiding numbers behind a login.
A trustworthy record also needs to preserve where a number came from, what changed later and whether the system has enough history to present a complete financial view.
Trust ledger
What the product is designed to make reviewable
These are product behaviors visible in the current Berlvis Books implementation. They are not claims about certifications or infrastructure controls we have not separately verified.
- Business records
- Private by purpose
- Sales, expenses, customer balances and reports live inside the account experience rather than being published publicly. A receipt is shared only when the user chooses to share it.
- Local-first changes
- Visible state
- Supported changes can be saved locally before remote sync. Pending and failed changes remain visible in the outbox instead of quietly disappearing.
- Financial corrections
- History preserved
- Payment corrections and archived entries are designed to preserve the earlier record while updating affected balances and reports.
- Conflict handling
- No blind overwrite
- The local-first flow surfaces multi-device conflicts and avoids silently force-overwriting newer financial data.
- Financial exports
- Completeness check
- PDF and Excel financial exports are blocked when historical hydration is known to be incomplete, reducing the risk of presenting a knowingly partial financial picture as complete.
- Receipts
- Scoped proof
- Sale and later-payment receipts can show the transaction and payment context without exposing the full business record.
Honest limits
What we will not claim without verified evidence.
Trust gets weaker when a product borrows security language it cannot substantiate.
- We do not publish certification or compliance claims unless they have been independently verified and are current.
- We do not invent encryption levels, backup guarantees or infrastructure practices for marketing copy.
- Berlvis Books is a record tool, not a bank, tax filing service, legal adviser or replacement for an accountant.
- Account security still depends on responsible user habits such as protecting login details and reviewing unusual activity.
User practice
Good product controls still need good operating habits.
Record transactions close to when they happen, correct mistakes through the product rather than hiding them, protect account credentials and review pending sync or conflict states instead of ignoring them.
Questions before you start
Security questions
Get started
Keep the record clear enough to review later.
Record sales, payments, expenses and customer balances in one traceable business history.
Free to start. No accounting knowledge required.