BAMF Books
In developmentMulti-entity double-entry bookkeeping you own
- Web
BAMF Books (engine name: BAMF Ledger) is a self-hosted, multi-entity double-entry bookkeeping engine built to replace QuickBooks. It ingests read-only bank, card, and payment feeds, auto-classifies the routine 80% with a deterministic rules engine, and produces per-entity and consolidated financial reports for tax prep. You run it on your own server with your own database. The publisher never sees your data.
Features
- True double-entry ledger with a balanced-transaction invariant enforced in the database
- Any number of fully isolated sets of books (entity isolation as a hard liability wall)
- Read-only ingestion from bank/card feeds (SimpleFIN) and payments (Stripe) that never moves money
- Deterministic classification rules engine that auto-posts routine activity and flags the rest for review
- Internal-transfer and Stripe-payout reconciliation via clearing accounts (the part QuickBooks gets wrong)
- Trial balance, P&L, balance sheet, and consolidated roll-up reporting
- Loan/note amortization with automatic principal/interest splits
- Role-based access (admin / accountant / viewer) with self-hosted accounts
- Live UI updates over WebSocket (no manual refresh to see ledger changes)
- Integrates with the BAMF Power ERP over HTTP/JSON
Third-party services
- SimpleFIN (backed by MX): Read-only bank and credit-card transaction connectivity; contacted by your self-hosted instance using your own access token
- Stripe: Read-only retrieval of gross charge / fee / payout / refund detail using your own restricted read key
Data & privacy disclosures
BAMF Books: Data Disclosures
Context: BAMF Books is a self-hosted web application. It is not currently distributed through the Apple App Store or Google Play, so neither nutrition label is being submitted today. The tables below are filled out as they would be submitted, from the perspective of the publisher (BAMF Apps LLC), which is the perspective these labels require.
The publisher operates no servers for BAMF Books and collects no data. All financial data, user accounts, and credentials live in the operator's own self-hosted database. Outbound connections to SimpleFIN and Stripe are made by the operator's own instance, using the operator's own credentials, and read-only. They are not collection by the publisher. Accordingly, both labels report Data Not Collected by the publisher.
Apple: App Privacy ("nutrition label")
Summary: Data Not Collected.
The publisher does not collect any data from this app. There is no analytics, advertising, tracking, or crash-reporting SDK, and the app makes no network calls to the publisher.
| Data type | Collected by publisher? | Linked to You | Used to Track You |
|---|---|---|---|
| Contact Info | No | N/A | N/A |
| Financial Info | No | N/A | N/A |
| Identifiers | No | N/A | N/A |
| User Content | No | N/A | N/A |
| Usage Data | No | N/A | N/A |
| Diagnostics | No | N/A | N/A |
| Location | No | N/A | N/A |
| Any other data | No | N/A | N/A |
Note for reviewers: the app does process the operator's own financial and contact data, but that data is stored only on the operator's self-hosted infrastructure and is never transmitted to or accessible by the publisher. Under Apple's definition, data processed and stored only on the user's own device/server and not sent to the developer is not "collected."
Google Play: Data Safety
Summary: No data collected or shared by the publisher.
| Field | Answer |
|---|---|
| Does the app collect or share any required user data types? | No (by the publisher) |
| Is all user data encrypted in transit? | Operator-configured. The app should be served over TLS; outbound calls to SimpleFIN and Stripe use HTTPS. |
| Do you provide a way for users to request data deletion? | Yes. The operator controls the database and can delete any data directly; see Account Deletion. |
| Is data collection optional? | N/A: no collection by the publisher. |
Data types: collected vs. shared (by the publisher)
| Data type | Collected | Shared | Ephemeral | Required/Optional | Purpose |
|---|---|---|---|---|---|
| Personal info (name, email) | No | No | N/A | N/A | N/A |
| Financial info | No | No | N/A | N/A | N/A |
| App activity / Usage | No | No | N/A | N/A | N/A |
| App info & performance (crash, diagnostics) | No | No | N/A | N/A | N/A |
| Device or other IDs | No | No | N/A | N/A | N/A |
Note for reviewers: BAMF Books stores names, emails, and financial records, but only within the operator's own self-hosted instance. The publisher neither receives nor has access to that data, so nothing is "collected" or "shared" under Google Play's definitions.
For operators / self-hosters (informational, not a store label)
If you deploy BAMF Books and grant other people access, you become the data controller. For transparency, here is what the Software stores in your database and what leaves your server:
- Stored locally: ledger data (entities, accounts, transactions, postings, rules, reconciliations, sync history, loans); imported bank/card/Stripe records; user accounts (email, name, role, scrypt-hashed password); sessions; and, if you store them in-app, AES-256-GCM-encrypted integration secrets.
- Transmitted (read-only, only if you configure it): outbound requests to SimpleFIN (bank/card data) and Stripe (payment data) using your credentials.
- Transmitted to the publisher: nothing.
See privacy-policy.md for the full description.