Security & Confidentiality
This page describes how we handle the records you upload to The Sentinel Flow. It is maintained by The Sentinel Flow to answer common security and privacy questions and is not an independent certification.
Document Handling
Invoices, entry summaries, and broker statements you upload are stored in an access-controlled workspace scoped to your account. Files are processed only to surface recovery opportunities, generate evidence packages, and support claim filing. We do not sell, share, or use your records to train third-party models.
Encryption
Uploads use TLS 1.2+ in transit. Files at rest sit in encrypted managed storage provided by our infrastructure partners, with keys managed by the platform provider. Database fields containing your records are encrypted at the storage layer.
Data Retention
Active records are retained while your account is open so we can monitor for new recovery opportunities and respond to CBP inquiries. You can request export or deletion of your records at any time by emailing privacy@thesentinelflow.com. Closed-account records are deleted within 30 days unless a regulatory hold applies.
User Privacy
We collect only the information needed to operate the platform: your account profile, the records you upload, and usage signals for product reliability. We do not run ad-tech profiling. See the privacy policy for the full data-use disclosure.
Access Controls
Authentication is required for every workspace action. Internal access to customer records is limited to recovery specialists assigned to your claims, and is logged. Privileged operations use service-role credentials that are never exposed to the browser.
Infrastructure
The application runs on a serverless edge runtime backed by managed Postgres with row-level security. Public read endpoints are scoped by policy and never expose other customers' records.
Secrets & Keys
Payment processing, AI analysis, and storage credentials are held as server-side secrets. They are not embedded in the browser bundle and are rotated when staff with access change.
Authentication
Managed authentication via Supabase Auth. Email + password with optional Google sign-in; passwords are never stored in application code. Sessions are bound to the workspace and expire automatically.
Authorization & RLS
Every customer table enforces row-level security keyed to the workspace. Server functions layer authorization on top with an explicit owner check before returning or mutating any record.
Webhook Security
Inbound webhooks (billing, third-party integrations) verify signatures with timing-safe comparison before any payload is processed. Unverified requests are rejected before touching the database.
Audit Logging
Workforce actions, approvals, and claim stage transitions are recorded with actor identity and timestamp. Administrators can review the history of decisions taken inside the platform.
Versioning & Immutable Records
Claims move through a 12-stage lifecycle with an append-only stage history. Evidence attached to a claim is retained alongside the record for later review.
Approval Workflows
Workflow actions that would touch external systems or customer-visible artifacts require an explicit human approval before execution. There is no unattended execution path.
Monitoring
Application errors, latency, and abuse signals feed an on-call queue. Alerts trigger investigation and, when warranted, the incident-response process.
Backup Strategy
Daily automated backups with point-in-time recovery are provided by the managed Postgres layer. File storage is redundantly replicated by the storage provider.
Disaster Recovery
The platform runs on a globally distributed edge runtime with automatic failover. Restoration procedures are validated as part of routine engineering work.
Responsible Disclosure
Coordinated vulnerability disclosure is documented separately. Good-faith researchers who follow the policy operate under safe-harbor terms.
Shared responsibility
The Sentinel Flow is responsible for application security, access controls, and the integrity of customer records inside the platform. Customers are responsible for keeping login credentials confidential, choosing strong passwords, and granting workspace access only to authorized staff.
Questions about a specific control?
For data-residency requests, signed DPAs, or vulnerability disclosure, email security@thesentinelflow.com.