Security & Trust

How Billtiq protects your
invoice data and workflows.

We touch your invoices, vendor records, payment data, and ERP credentials. Here's exactly how we secure them โ€” what's live today, and what's on our roadmap.

๐Ÿ”’ AES-256 encryption at rest ยท ๐Ÿ” TLS 1.3 in transit ยท ๐Ÿ“‹ SOC 2 in progress ยท ๐Ÿงพ Full audit trail ยท ๐Ÿ‘ฅ RBAC enforced
Data Protection

Encryption everywhere

Every byte of your data is encrypted โ€” at rest in our database, in transit across the network, and in our backups.

๐Ÿ”’
At rest live

All customer data is stored in PostgreSQL on AWS infrastructure (via Supabase) with AES-256 encryption applied to the underlying disk volumes. Database backups are encrypted with the same standard.

๐ŸŒ
In transit live

All traffic between your browser, our servers, and our database uses TLS 1.3 with HSTS enforced. We never accept unencrypted connections. SSL certificates are managed and auto-rotated by Vercel and Render.

๐Ÿ”‘
Credentials & secrets live

Your ERP credentials (Oracle Fusion passwords, OAuth tokens, API keys) are stored encrypted at the database level and only decrypted server-side at the moment of API calls. They are never exposed to the browser or our logs. Service-role database keys are isolated to backend infrastructure.

Access Control

Your data, only your team

Multi-tenancy means every customer's data is logically isolated. We enforce this at the database level โ€” not just in application code.

๐Ÿ›ก๏ธ
Row-Level Security (RLS) live

PostgreSQL Row-Level Security policies ensure that customer A's invoices, vendors, and POs are physically inaccessible to customer B โ€” even from within the database itself. Every query is filtered by team membership at the database level.

๐Ÿ‘ฅ
Role-based access (RBAC) live

Three roles inside each customer team:

  • Admin: Full access โ€” invite members, configure ERPs, manage billing, mark invoices as paid
  • Member: Process and approve invoices, view team data โ€” cannot delete or modify billing
  • Supplier: View only their own submissions, cannot see team data
๐Ÿ”
Authentication live

Email and password (bcrypt-hashed, never stored in plain text) or Google OAuth. Passwords require minimum 8 characters with mixed-case, numbers, and symbols. Email verification required on signup. Login attempts are rate-limited at the platform level to prevent brute-force attacks.

Visibility & Compliance

Every action, recorded

If a question comes up in your next audit โ€” "who approved this invoice and when?" โ€” you'll have an answer in seconds.

๐Ÿงพ
Audit trail per invoice live

Every action on every invoice is logged: created, edited, approved, rejected, pushed to ERP, payment confirmed. Each entry shows the user, timestamp, IP address, and what changed. Exportable for SOX, internal audits, and finance reviews.

๐Ÿ“‹
SOC 2 Type II in progress

We are pursuing SOC 2 Type II certification. The full report will be available to enterprise customers under NDA once complete. Until then, we operate to the same control standards and can provide a Security Posture Document on request.

๐ŸŒ
Data residency us-only today

All data is currently hosted in US-based AWS data centers (us-east-1). EU and other regional data residency options are on our roadmap for enterprise customers โ€” please contact us if this is a current requirement.

Reliability

Backups, recovery, and uptime

๐Ÿ’พ
Backups live

Daily encrypted database backups are retained for 7 days (Starter), 30 days (Growth), and 90 days (Enterprise). Point-in-time recovery is available within the retention window. Backups are stored in a separate AWS region from the primary database.

โšก
Uptime & monitoring live

Public health checks every 5 minutes. Real-time alerts on any service degradation. Enterprise customers receive contractual SLA commitments (target: 99.9% monthly uptime).

๐Ÿงช
Penetration testing planned 2026

External penetration testing scheduled as part of our SOC 2 process. Reports will be available to enterprise customers under NDA.

AI & Data Handling

How we use AI on your data

Billtiq uses Anthropic's Claude API to extract data from invoice PDFs and assist with classification. Important details:

  • Your invoice data is never used to train Claude or any other model
  • Anthropic processes data only for the duration of the API call and does not retain it for training
  • You can request a full data deletion at any time
  • Confidence scores are surfaced for every extracted field โ€” low-confidence values are flagged for human review, never silently pushed to your ERP
On the roadmap

What's coming next

Reporting a vulnerability

Found a security issue?

We take security seriously and appreciate responsible disclosure. If you've discovered a potential vulnerability, please email security@billtiq.com with details. We'll acknowledge within 24 hours and work with you on a fix.

Please do not publicly disclose vulnerabilities until we've had a chance to address them.

Have a security question we didn't answer?

Enterprise security questionnaires welcome. We'll respond within one business day.

security@billtiq.com โ†’