Every payment passes the same checks: a signed-in person, a fresh two-factor code, access limited to your company, encrypted bank details and a permanent record of who approved it.
Bank numbers, tax IDs and accounting tokens, each under its own key.
Two-factor sign-in on every account, and again before money moves.
Your data is stored in the United States, on AWS in Virginia.
Restore to any moment in the past week from continuous backups.
Each layer works on its own, so getting past one still leaves the others in the way. Pick a layer to see what it does.
Everything between your browser and ShelfSpace travels encrypted, and automated traffic is screened before it reaches a sign-in form.
A password alone never gets anyone in, and a signed-in session alone never moves money.
Every table in the database enforces row-level security, so a request can only ever return rows that belong to the signed-in person's company.
All stored data is encrypted on disk. The most sensitive fields are encrypted again inside the application before they are saved.
Running several companies? Put them all on one screen and decide, person by person, which companies they can reach and what they can do there. Your AR team can collect at one company without ever seeing expenses at another.
| Person · company | Collections | Bill pay | Expenses |
|---|---|---|---|
| Maya ChenAR lead · North Farm LLC | |||
| Sam OrtizAP clerk · North Farm LLC | |||
| J. RiveraController · all companies | |||
| Dev PatelField sales · South Labs Inc. |
Payments go from your bank account straight to the person you're paying. ShelfSpace never holds your money, and nothing is sent until a person on your team approves it.
Matched, coded and waiting. Anyone with access can prepare it.
Signed in, with a fresh two-factor code, in a role allowed to pay.
By e-check or bank transfer through our banking partner, Alero Financial.
The audit log records who approved it, and the payment posts to your books.
Banks are connected through Plaid. You sign in to your bank in Plaid's window, and that login never reaches us or our banking partner.
Adding or changing a bank account always takes a signed-in person and a fresh two-factor code. No email or AI can do it.
Payments are checked against what was already paid and what was invoiced, and a warning has to be cleared by a person.
The disk underneath is encrypted. On top of that, each sensitive field is locked with its own key before it's saved, so a copy of the database alone shows nothing useful.
Each create, change and delete is written to an append-only log with who did it, when, and the values before and after. No user can edit or delete an entry, and our read-only staff accounts are blocked from writing to it.
Our assistants read invoices, answer questions and draft replies. The rules that keep them in bounds are written in code, not left to the AI.
The hard line: AI can't draw money, add or change a bank account, or change who a payment goes to. In the app, it can only prepare an action, and a signed-in person approves it with a fresh two-factor code.
Our servers set which account an assistant works for before it starts. The AI never picks an account, and no AI tool can read across customers.
Inbound mail must pass sender authentication. Anything that changes data needs the sender's domain proven and a known contact on the account.
Before the AI reads an email, we remove hidden text, scripts and invisible characters, and treat everything in it as information, never as instructions.
Code masks bank, routing and tax numbers in every AI reply and stops claims that don't match our records before anything is sent.
Xero data reaches the AI only after someone on your team agrees when connecting, and only while that connection is live.
We use Anthropic's Claude under commercial terms that prohibit training on your data, and Anthropic deletes it within 30 days.
The database is backed up daily and recorded continuously, so we can restore it to any moment in the past seven days and lose at most about five minutes of data.
Full restore in our 08/04/2026 drill
Tables matched exactly after restore
Most data that could be lost
We share only what each provider needs to do its job, over encrypted connections.
| Provider | Category | What it does for us |
|---|---|---|
| Supabase (on AWS, US) | Infrastructure | Database, sign-in and file storage |
| Vercel | Infrastructure | Application hosting and encrypted secret storage |
| Alero Financial | Payments | Bank transfers (ACH) |
| Plaid | Payments | Connecting bank accounts, without sharing your bank login |
| Check processing partner | Payments | Printing and sending e-checks and mailed checks |
| Anthropic | AI | AI that reads invoices and drafts replies; no training on your data |
| Resend | Messaging | Email delivery |
| Twilio | Messaging | Text messages |
| Sentry | Monitoring | Error monitoring |
| Cloudflare | Security | Bot protection on public forms |
| Xero, QuickBooks, Metrc | Your connections | Only the connections you turn on, to sync your books and state records |
Our policies are reviewed at least once a year and whenever how we handle data changes. Customers can ask for copies.
Send your questionnaire to chris@shelfspace.pro and we'll answer every question in writing. We're also glad to coordinate a third-party penetration test scoped with your team.
Report a suspected vulnerability to chris@shelfspace.pro with "Security report" in the subject. We read every report and reply to you directly.
In the United States. The application runs on Vercel, and the database and uploaded files are stored on AWS in us-east-1 (Virginia).
Yes. Every table enforces row-level security, so each request only returns rows that belong to the signed-in person's company, and our servers check access again before any action.
No. When you connect a bank for transfers, you sign in to your bank inside Plaid's window, and that login never reaches ShelfSpace or our banking partner.
Production access is limited to the founder and one designated backup, behind multi-factor sign-in. Anyone else on our team gets a read-only account that cannot change anything, and viewing bank or tax details is logged.
No. Our commercial agreement with Anthropic prohibits training on customer data, and Anthropic deletes API data within 30 days.
Yes. Send it to chris@shelfspace.pro and we answer every question in writing. We can also share our written security policies and coordinate a third-party penetration test with your team.
We'll walk your team through access, approvals and the audit log on a live account.