Sub-processors
Last updated: March 4, 2026
PeekAPI uses the following third-party sub-processors to deliver our service. This list is maintained in accordance with our Privacy Policy and Data Processing Agreement.
Current Sub-processors
| Sub-processor | Purpose | Location | Data Processed |
|---|---|---|---|
| Supabase | Database, authentication, Edge Functions | EU — Ireland (AWS) | Account data, API request metadata |
| Hetzner | Dashboard hosting, Plausible analytics hosting | Germany (EU) | Web requests, marketing page analytics |
| Resend | Email alert delivery | US | Alert recipient email addresses |
| Paddle | Payment processing, merchant of record | UK | Billing name, email, payment method, transaction data |
Customer-Configured Integrations
When you configure alert notifications via Slack, Discord, Telegram, or custom webhooks, data is sent to those services based on your configuration. These integrations are controlled by you and are not PeekAPI sub-processors. You are responsible for the privacy practices of those third-party services.
Changes to This List
We will notify customers at least 30 days before adding a new sub-processor. Notifications are sent via email to the account owner. If you object to a new sub-processor, you may terminate your account within the 30-day notice period.
For questions about our sub-processors, contact us at [email protected].