Your money moves only when your people say so.

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.

Schedule a call 30 minutes with Chris. See how it would run for your business.
AES-256 encryption Two-factor sign-in US data storage Certified Metrc vendor
Sample data for illustration. Not a real payment, customer or person.
AES-256

Bank numbers, tax IDs and accounting tokens, each under its own key.

2FA

Two-factor sign-in on every account, and again before money moves.

US only

Your data is stored in the United States, on AWS in Virginia.

7 days

Restore to any moment in the past week from continuous backups.

Defense in layers

Four layers between anyone and your money.

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.

Your money + your records

Network

Everything between your browser and ShelfSpace travels encrypted, and automated traffic is screened before it reaches a sign-in form.

  • HTTPS everywhere. Every page and API call uses TLS, and browsers are told to refuse anything else (HSTS, preloaded).
  • Encrypted live updates. Real-time screens use secure WebSockets only.
  • Bot protection on public forms, so scripted sign-up and sign-in attempts are turned away.
  • Encrypted partner connections. Calls to banks, accounting systems and Metrc all go over TLS.

Identity

A password alone never gets anyone in, and a signed-in session alone never moves money.

  • Two-factor sign-in is required on every account.
  • Step-up before money moves. Approving a payment, sending a payment or connecting a bank asks for a fresh two-factor check, even mid-session.
  • No magic links. Email links never sign anyone in to payments, settlements or bank details.
  • Passwords are hashed by our authentication provider and never stored in readable form.

Access

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.

  • Row-level security on every table. Customers share one database, but never each other's records.
  • Per person, per company, per feature. Your admin decides who sees collections, bill pay or expenses at each of your companies.
  • Checked twice. Our servers confirm the person's role again before any change, on top of the database rules.
  • Staff are read-only. Anyone on our team besides the founder and one designated backup gets a read-only account.

Data

All stored data is encrypted on disk. The most sensitive fields are encrypted again inside the application before they are saved.

  • AES-256-GCM field encryption for bank routing and account numbers, tax IDs, system credentials and accounting tokens, including Xero and QuickBooks.
  • Separate keys by type, so bank data, tax IDs and accounting tokens never share a key.
  • Last four only. Screens show bank and tax numbers masked. Viewing a full tax document is logged and the owner is told.
  • Secrets stay out of code. Keys live in our host's encrypted secret store and can't be read back once saved.
Access control

Each person sees only what you allow.

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.

  • Company admins set access themselves, no ticket required.
  • Turning a feature off blocks its pages, its data and its emails for that person, on the server, not just in the menu.
  • Every access change is written to the audit log.
Team accessSample data
Person · companyCollectionsBill payExpenses
Maya ChenAR lead · North Farm LLC
Sam OrtizAP clerk · North Farm LLC
J. RiveraController · all companies
Dev PatelField sales · South Labs Inc.
Sample data, not real people. Off means off: no page, no data, no email for that feature.
Payments

Money never moves on its own.

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.

01 · Prepare
Bill or invoice is ready

Matched, coded and waiting. Anyone with access can prepare it.

02 · Approve
A person approves

Signed in, with a fresh two-factor code, in a role allowed to pay.

03 · Send
Sent from your bank

By e-check or bank transfer through our banking partner, Alero Financial.

04 · Record
Logged and synced

The audit log records who approved it, and the payment posts to your books.

Your bank login stays yours

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.

Bank changes need a person

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.

Duplicate and mismatch checks

Payments are checked against what was already paid and what was invoiced, and a warning has to be cleared by a person.

Field encryptionSample
You enterAccount 004417
We store 
Screens show••••4417
AES-256-GCM · banking key
Sample data. The account number, stored value and key label are made up, not real customer data or keys.
Encryption

Encrypted twice. Readable by no one who shouldn't.

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.

  • In transit: TLS on every connection, HSTS preloaded.
  • At rest: full-disk encryption for the database and every uploaded document.
  • Field level: AES-256-GCM with separate keys for banking, tax IDs and credentials, and for accounting connections.
  • Keys: rotated at least once a year and immediately if anything looks wrong.
Audit trail

Every change, on the record.

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.

Audit logAppend-only
Payment approved, INV-1042
J. Rivera · two-factor confirmed
status: readystatus: approved
Access changed
Company admin · North Farm LLC
Sam Ortiz · bill pay: offSam Ortiz · bill pay: on
Tax ID viewed
Maya Chen · owner notified
W-9 opened · logged
Sample entries, not real activity. Logs are kept for at least three years; financial records for at least seven.
AI safeguards

AI that answers and prepares. Never pays.

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.

One account at a time

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.

Fake senders turned away

Inbound mail must pass sender authentication. Anything that changes data needs the sender's domain proven and a known contact on the account.

Hidden instructions stripped

Before the AI reads an email, we remove hidden text, scripts and invisible characters, and treat everything in it as information, never as instructions.

Replies checked by code

Code masks bank, routing and tax numbers in every AI reply and stops claims that don't match our records before anything is sent.

Your books, with consent

Xero data reaches the AI only after someone on your team agrees when connecting, and only while that connection is live.

Never used for training

We use Anthropic's Claude under commercial terms that prohibit training on your data, and Anthropic deletes it within 30 days.

Backups and recovery

Tested restores, not just backups.

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.

  • Restore drill on 08/04/2026: a full restore finished in under three minutes, and every table matched the original exactly.
  • Hosting: the application runs on Vercel, and the database and files are on AWS in us-east-1 (Virginia).
  • Written plans for incident response and business continuity, with a designated backup who holds the keys.
  • Breach notice within 72 hours of discovery.
7 days agoNow
Restore to any minute
< 3 min

Full restore in our 08/04/2026 drill

190 / 190

Tables matched exactly after restore

~5 min

Most data that could be lost

Who else touches your data

Our service providers, in plain view.

We share only what each provider needs to do its job, over encrypted connections.

ProviderCategoryWhat it does for us
Supabase (on AWS, US)InfrastructureDatabase, sign-in and file storage
VercelInfrastructureApplication hosting and encrypted secret storage
Alero FinancialPaymentsBank transfers (ACH)
PlaidPaymentsConnecting bank accounts, without sharing your bank login
Check processing partnerPaymentsPrinting and sending e-checks and mailed checks
AnthropicAIAI that reads invoices and drafts replies; no training on your data
ResendMessagingEmail delivery
TwilioMessagingText messages
SentryMonitoringError monitoring
CloudflareSecurityBot protection on public forms
Xero, QuickBooks, MetrcYour connectionsOnly the connections you turn on, to sync your books and state records
Security program

Written down, reviewed every year.

Our policies are reviewed at least once a year and whenever how we handle data changes. Customers can ask for copies.

Information security policyRoles, access, change review and how we handle a security event.
Data security and retentionHow data is classified, encrypted, kept and disposed of.
Key managementHow encryption keys are created, stored, rotated and retired.
Incident response and continuitySeverity levels, who does what, customer notice and restore steps.
Payment controls and fraud monitoringPayment validation, anti-money-laundering and red-flag procedures.
Every change reviewedEach code change gets a security review, and every release is scanned for known vulnerabilities.

Security review for your team

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.

Found a problem?

Report a suspected vulnerability to chris@shelfspace.pro with "Security report" in the subject. We read every report and reply to you directly.

FAQ

Security, answered.

Where is my data stored?

In the United States. The application runs on Vercel, and the database and uploaded files are stored on AWS in us-east-1 (Virginia).

Do other customers share the database?

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.

Does ShelfSpace need my online banking login?

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.

Can ShelfSpace staff see my data?

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.

Is my data used to train AI models?

No. Our commercial agreement with Anthropic prohibits training on customer data, and Anthropic deletes API data within 30 days.

Can you complete our security questionnaire?

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.

Get started

See the controls on your own data.

We'll walk your team through access, approvals and the audit log on a live account.

Schedule a call 30 minutes with Chris. See how it would run for your business.