Security & Compliance
How BankReconPro protects your data — encryption, access controls, and compliance standards
Your Data, Your Control
Every document, transaction, and reconciliation uploaded to BankReconPro is visible only to your firm's authorized users, under their individual authenticated accounts. No other customer, firm, or external party can view, access, or interact with your data — ever. You retain full ownership and control over all data uploaded to the platform, and can export or permanently delete it at any time.
AES-256 Encryption
All data encrypted at rest and in transit using AES-256 encryption managed through AWS infrastructure. Zero customer key management required.
Basically, AES-256 is the same encryption that banks and governments use. Your data gets scrambled so thoroughly that even if someone got hold of the raw files, it would just look like gibberish to them. There's no realistic way to crack it.
Mandatory 2FA
All team members must activate two-factor authentication. Accounts without 2FA cannot access the platform.
So even if someone somehow gets your password, they're still locked out — because they'd also need the code from your phone to get in. We don't let anyone skip this step, no exceptions.
Firm-Level Isolation
Each firm operates in a completely isolated namespace. No cross-firm data access is possible by design.
Think of it this way — every firm on BankReconPro has their own completely separate space. There's no way for another company to accidentally (or deliberately) see your stuff. It's not just permissions, the data is actually walled off at the system level.
Infrastructure & Hosting
BankReconPro is hosted on Amazon Web Services (AWS) with dedicated cloud infrastructure and encrypted storage across all layers.
What this means for you: We run on Amazon Web Services — the same cloud that powers Netflix, NASA, and most of the big banks. So your data sits in proper, purpose-built data centres with security guards, backup generators, fire suppression, the works. Not on a server under someone's desk. AWS have spent billions on this infrastructure and we get the benefit of all of it.
| Component | Service | Details |
|---|---|---|
| Compute | AWS Cloud (Dedicated Instance) | Dedicated resources, static IP, encrypted volumes |
| Database | PostgreSQL | Encrypted storage, automated snapshots, connection pooling |
| Web Server | Nginx + Gunicorn | Reverse proxy with SSL termination, HSTS preloaded |
| Real-Time | WebSockets (ASGI) + Redis | Live collaboration, real-time notifications |
| SSL/TLS | Let's Encrypt (Auto-Renewing) | TLS 1.2/1.3, HSTS preloaded, A+ SSL rating |
| Task Queue | Celery + Redis | Background processing, scheduled maintenance tasks |
| Audit & Monitoring | Application-Level Audit Logging | Full action trail with user/IP tracking, 7-year retention |
Scalability
Infrastructure is provisioned on AWS with the ability to scale vertically on demand. Snapshot-based deployments enable rapid recovery and migration.
As the platform grows, we can scale resources up quickly through AWS — and if anything goes wrong, we can restore from a recent snapshot in minutes. The infrastructure is designed to grow alongside demand.
Encryption Standards
What this means for you: There are two moments when data could be vulnerable — when it's moving between your computer and our servers ("in transit"), and when it's sitting on our servers ("at rest"). We encrypt it in both cases. So whether your data is travelling or stored, it's locked up tight. Even if someone intercepted it mid-transfer, they'd just see scrambled nonsense.
Data in Transit
- TLS 1.2/1.3 for all connections (HSTS preloaded)
- Encrypted PostgreSQL database connections
- Encrypted Redis connections for real-time data
- WSS for real-time WebSocket connections
- TLS 1.2 to Azure OpenAI (server-side only)
Data at Rest
- AES-256 encrypted storage volumes (AWS managed)
- Encrypted database on disk via volume encryption
- PBKDF2-SHA256 password hashing (870K iterations)
- SHA-256 hashed tokens (invites, magic links)
- Encrypted backup snapshots (inherits source encryption)
No customer key management required. All encryption is fully managed by the BankReconPro platform via AWS infrastructure. You never need to handle, rotate, or store encryption keys.
You don't have to worry about any of this — we handle it all. The encryption is managed through Amazon's infrastructure automatically. You'll never be asked to manage keys or remember extra passwords for this. It just works quietly in the background.
Authentication & Access Control
What this means for you: We're pretty strict about who gets in and what they can do once they're in. Everyone needs a password and a phone code — no shortcuts. And once logged in, people only see what their role allows. Your junior staff can't go deleting things, and your admin decides who sees which clients. It's layered so that no single point of failure can expose data.
Authentication Methods
- Mandatory 2FA — TOTP required for all team members (superusers exempt for emergency access)
- Passkey / WebAuthn biometric login
- Google OAuth 2.0 federation
- 12-character minimum password policy
- Rate limiting (5 attempts / 5 min)
- New device/IP login alerts
Data Isolation
- Firm-level namespace isolation — queries scoped to your firm only
- No cross-firm data visibility — by design
- RBAC: Admin, Senior, Junior, Viewer roles
- Admin controls which staff see which clients
- 1-hour inactivity timeout + 30-day session
- Full audit trail of all actions (7-year retention)
AI Integration (Azure OpenAI)
BankReconPro uses Microsoft Azure OpenAI Service — not the public OpenAI API — for AI-powered narrative reports, anomaly detection, and variance analysis.
Why Azure OpenAI, not ChatGPT? This is a question we get a lot. We use Microsoft's enterprise AI service, which is completely separate from the public ChatGPT that everyone uses day-to-day. The big difference? Your data never gets stored, shared, or used to train any AI models. Microsoft already have all the data privacy agreements in place — GDPR, SOC 2, HIPAA — the lot. So your financial information is covered under the same contracts that protect banks and hospitals. Once the AI generates a response, it forgets everything. Nothing is retained.
What We Send
Only aggregated, anonymized reconciliation summaries. Never raw bank statements, PII, or client identifiers.
Zero Retention
Microsoft stores zero prompts or completions. Your data is never used to train or improve any AI models.
Certifications: SOC 2 Type II, ISO 27001/27017/27018, HIPAA BAA, GDPR DPA, FedRAMP High
These aren't just badges on a website — each one means an independent auditor has gone through Microsoft's systems and confirmed they meet the standard. The same certifications that hospitals and government agencies require.
Regulatory Compliance
What this means for you: GDPR is the EU's data protection law — it gives you the right to see all your data, download it, or ask us to delete everything permanently. HIPAA is the US equivalent for sensitive information. We designed BankReconPro to comply with both from day one, not as an afterthought. So whether your clients are in London, New York, or anywhere else, the same strong protections apply across the board.
GDPR
- Right to Access — export all your data anytime
- Right to Erasure — full account & data deletion
- Right to Portability — Excel, CSV, PDF export
- Data Processing Agreements with all sub-processors
- 72-hour breach notification procedure
- EU Standard Contractual Clauses (SCCs) in place
HIPAA
- MFA enforcement (§164.312(d))
- AES-256 encryption at rest (§164.312(a)(2)(iv))
- TLS 1.2+ in transit (§164.312(e))
- Audit logging with 7-year retention (§164.312(b))
- Business Associate Agreements executed
- Emergency access procedures documented
Summary of Controls
What this means for you: This is a quick-glance summary of everything we've covered above, mapped to the specific regulation each one satisfies. Worth noting — every item here says "Active". These aren't roadmap items or things we plan to do eventually. They're live, right now, on the platform you're already using.
| Control Area | Standard | Status |
|---|---|---|
| Encryption at rest (AES-256) | GDPR Art. 32, HIPAA §164.312(a)(2)(iv) | ✅ Active |
| Encryption in transit (TLS 1.2+) | GDPR Art. 32, HIPAA §164.312(e) | ✅ Active |
| Multi-factor authentication | HIPAA §164.312(d) | ✅ Active |
| Role-based access control | GDPR Art. 25, HIPAA §164.312(a) | ✅ Active |
| Firm-level data isolation | GDPR Art. 25, HIPAA §164.312(a) | ✅ Active |
| Audit logging (7-year retention) | GDPR Art. 30, HIPAA §164.312(b) | ✅ Active |
| Data breach notification (<72h) | GDPR Art. 33/34 | ✅ Active |
| Right to erasure & portability | GDPR Art. 17, 20 | ✅ Active |
| Business Associate Agreements | HIPAA §164.308(b) | ✅ Executed |
| Backup & disaster recovery | HIPAA §164.308(a)(7) | ✅ Active |
| AI data handling (zero retention) | GDPR Art. 28 | ✅ Active |
Backup & Disaster Recovery
What this means for you: We back everything up automatically, several times a day, and keep copies in different physical locations. If a server goes down — or even if an entire data centre has a problem — your data is safe and the system switches over within minutes. You wouldn't lose any work. The "RPO" and "RTO" columns below basically show how much data you'd lose (almost none) and how quickly things get back to normal (very quickly).
| Component | Strategy | RPO | RTO |
|---|---|---|---|
| Database | Automated snapshots, point-in-time recovery | < 24 hrs | < 1 hr |
| File Storage | Included in instance snapshots, encrypted volumes | < 24 hrs | < 1 hr |
| Application | Git-based deployment pipeline | Zero | < 30 min |
| Configuration | Environment-based, included in snapshots | < 24 hrs | < 30 min |
All snapshots inherit AES-256 encryption from source volumes. Retention: configurable via AWS snapshot policies.
We keep regular snapshots of the entire system, and yes, the snapshots are encrypted too. If anything goes wrong, we can restore from a recent snapshot quickly — so you never lose significant amounts of work.
Third-Party Sub-Processors
What this means for you: We want to be upfront about exactly who else is involved. These four companies are the only third parties that touch any part of your data, and here's what each one actually does: Amazon runs the infrastructure (but can't read your encrypted data). Microsoft powers the AI features (but doesn't keep anything afterwards). Stripe handles card payments (they never see your financial documents — just billing details). And Google is only involved if you choose to sign in with your Google account. All four have signed proper data processing agreements with us.
| Provider | Purpose | Data Accessed | Compliance |
|---|---|---|---|
| Amazon Web Services | Infrastructure, DB, storage | All platform data | SOC 2, ISO 27001, HIPAA, GDPR |
| Microsoft Azure | OpenAI API for AI analysis | Anonymized summaries only | SOC 2, ISO 27001, HIPAA, GDPR |
| Stripe | Payment processing | Billing info only | PCI DSS Level 1, SOC 2, GDPR |
| Google (OAuth) | Federated login | Email, display name | SOC 2, ISO 27001, GDPR |
Questions?
For security inquiries, compliance documentation, or to report a vulnerability:
info@bankreconpro.com