Sub-processors
This register lists the third parties that WINGUARDIAN.NET LLC engages to process personal data on behalf of its clients. It is incorporated by reference into our Data Processing Agreement.
- Version
- 1.0.0
- Effective
- 2026-08-04
Standing sub-processors
Engaged across substantially all engagements.
| Sub-processor | Purpose | Location |
|---|---|---|
Netlify Netlify, Inc. | Application hosting, content delivery, and edge functions | United States |
Supabase Supabase, Inc. | Database hosting, authentication, and file storage | United States |
Resend Resend, Inc. | Transactional and notification email delivery | United States |
Stripe Stripe, Inc. | Payment processing and subscription billing | United States |
Network Solutions Network Solutions, LLC | Domain registration and associated hosting services | United States |
Independent contractors | Specialist engineering and design support, engaged under written confidentiality and data-protection terms equivalent to those in our Data Processing Agreement | United States |
Engagement sub-processors
Some engagements require additional sub-processors that are not used across all clients. Where that applies to your engagement, those sub-processors are identified in the relevant Statement of Work or its schedule, and are subject to the same contractual obligations and the same notice rights described below.
Notice of changes
We give at least 30 days' notice before adding or replacing a sub-processor that processes your personal data. To receive those notices, email legal@winguardian.net with the subject “Subscribe — sub-processor change notices”. If you reasonably object to a proposed change, you may terminate the affected service without penalty as set out in the Data Processing Agreement.
Change log
- 1.0.02026-08-04
Initial publication of the sub-processor register. Standing sub-processors: Netlify, Supabase, Resend, Stripe, Network Solutions, and independent contractors.
Google Analytics is used on this website to measure our own visitor traffic, where we act as controller rather than processor. It is disclosed in our Privacy Policy and is not a sub-processor of client data. Where a client provides its own third-party model or service credentials, that provider is engaged by the client directly and is not our sub-processor.