Trust & Security Center
Subprocessors.
The services Winglark relies on to run, and what each of them touches. This list reflects the product as configured today; the Privacy Policy remains the governing document.
Last reviewed 26 September 2026
| Service | Purpose | Data involved | Location | Status |
|---|---|---|---|---|
| Vercel | Hosting and delivery of the application | All application traffic | EU (Frankfurt) for application functions | Active |
| Neon | Production database | Workspace, event and guest data | EU | Active |
| Resend | Sending and receiving email | Recipient addresses and message content | Per provider infrastructure; may be outside the EU | Active |
| Sign-in with Google; advertising measurement after consent | Sign-in identity; consenting visitors’ measurement data | Global | Active | |
| OpenAI | AI Studio text and image generation | Event details and the organiser’s instructions — no guest data | United States | Active, when AI Studio is used |
| PostHog | Website analytics after consent | Consenting visitors’ page usage, without cookies | United States | Active |
| Paddle | Payments | Billing details, handled by Paddle | Per provider infrastructure | Not processing live payments yet |
| Infobip | SMS, WhatsApp and RCS | Phone numbers and message content | Per provider infrastructure | Configured, not sending |
- Winglark does not store card details; payments, when switched on, are handled by the payment provider.
- Where a location depends on the provider’s own infrastructure, we say so rather than guess.