Subprocessors
The short list of outside companies that process data on our behalf — what they do, what they touch, and where it sits.
A subprocessor is a third party we engage to process personal data so we can run Wesprs. Each one serves a single stated purpose and appears on this list before it begins processing for us. Because Wesprs holds no legal name, no email identity, and expires content server-side within 24 hours, there is structurally very little personal data for any of these companies to touch.
| Subprocessor | Purpose | Data category | Region |
|---|---|---|---|
| Hetzner Online GmbH | Cloud infrastructure and hosting — the servers Wesprs runs on. | Encrypted application data and first-party server logs. | Germany (EU) |
| Cloudflare, Inc. (R2) | Object storage and delivery for photos and video, served only through short-lived signed URLs. | Media with metadata stripped server-side; no plaintext message content. | EU residency |
| Apple Inc. (APNs) | Push-notification delivery to iOS devices. | Opaque device token and an empty signal — no message content, no sender, no plaintext. | United States / global |
| Apple Inc. (App Attest & Declared Age Range) | Sign-up verification — a cryptographic check that the genuine Wesprs app is running on a genuine Apple device, and the 18-or-over signal from the age range declared on the device's Apple Account. | A device attestation and a yes/no adult signal — no camera image, no biometric, no name. We keep only the five-field, non-biometric snapshot described in the Privacy Policy. | United States / global |
What is deliberately not on this list
Our database (ScyllaDB) and our analytics (Plausible) are operated by us on the hosting listed above — the hosting provider supplies the servers, and no separate database or analytics company processes that data, so they are not subprocessors. There are zero advertising or tracking SDKs anywhere in the apps or on this website, a fact verified by an automated check in our build pipeline. We do not use third-party advertising networks, data brokers, tracking pixels, or session-replay tools, so none of those appear here either.
A note on verification
Sign-up verification never creates a biometric: there is no face scan, no video selfie, and no ID upload. The check runs entirely on Apple's App Attest and the age range declared on the device's Apple Account, as listed above, and what we keep is the five-field, non-biometric snapshot described in the Privacy Policy. If we ever add a dedicated verification vendor — for example a liveness or age-estimation provider — it will appear on this list before it goes live, never after.
Changes to this list
If we add, remove, or replace a subprocessor, we will update this page before the change takes effect. If a future feature requires a new vendor — for example, web billing — it will appear here first. Questions about our processors go to our Data Protection Officer.
- dpo · [email protected]
For the full picture of what we process and why, read the Privacy Policy.