Sub-processors
Everyone who processes data on Sentinel's behalf, what they do, and where they sit. New sub-processors that process customer data are announced at least 30 days in advance, with right to object — the change log below is the public record.
Last updated 16 July 2026 · maintained by Sentinel Edge Networks LTD
Current sub-processors
| Provider | Purpose | Data touched |
|---|---|---|
| Cloudflare | CDN, TLS termination, edge caching, first-pass scanner verdict at the edge | Request metadata (IP, headers) in transit |
| Railway | Application hosting | All application traffic and data in transit |
| Turso | Primary database (managed libSQL), encrypted at rest | Account data, hashed lookup records |
| Resend | Transactional email (verification, notices) | Email address, message content |
| Sign-In only (OAuth) — no analytics, no advertising | OAuth identity assertion | |
| Have I Been Pwned | Password breach check via k-anonymity | 5-character SHA-1 prefix only — never the password |
| Network & device intelligence providers | VPN/proxy classification and device-integrity signals for evaluations | Request network metadata; named to customers under DPA |
Fonts are self-hosted. There are no advertising or analytics providers on this list because there are none — see the Privacy Policy and Cookie Policy for the full data-handling picture.
Change log
| Date | Change |
|---|---|
| 2026-07-16 | Page published. List matches the sub-processors already disclosed in the Privacy Policy — no additions or removals. |
Getting notified
Enterprise customers under a signed DPA receive direct notification of sub-processor changes. Everyone else can watch this page or the changelog — any change lands in both at least 30 days before a new data-processing sub-processor goes live.
Questions or objections: [email protected].