Legal
Third-Party Notices
1. Required Third-Party Service Disclosures
Wello uses third-party providers to deliver infrastructure, verification, payouts, communications, and map features.
| Provider | Purpose | Typical Data Processed |
|---|---|---|
| Supabase | Backend infrastructure, auth, database, storage, edge functions. | Account, profile, offer, redemption, operational metadata. |
| Google Identity | Optional Google sign-in / OAuth identity flows. | Name, email address, and identity-provider account metadata. |
| Stripe | Business billing and invoicing operations. | Business billing metadata and invoice/payment artifacts. |
| Plaid | Bank-link and purchase verification support. | Linked account metadata and transaction-matching metadata. |
| Checkbook | Bank-transfer payout operations. | Payout recipient metadata and payout status references. |
| Reloadly | Gift card payout and claim fulfillment. | Gift card order/reward references and claim-link metadata. |
| Cloudflare (Turnstile and R2) | Abuse prevention, security, and object storage flows. | Request metadata, anti-abuse tokens, uploaded file metadata. |
| Brevo | Website contact form and support email delivery. | Contact form details and email delivery metadata. |
| Resend | Operational and transactional email delivery. | Withdrawal alerts, billing emails, and delivery metadata. |
| Expo Push | Push notification delivery pipeline. | Push tokens and notification delivery metadata. |
| Apple Maps / Google Maps APIs | Map views, geocoding, and place lookup. | Address search requests, map and location feature metadata. |
2. Open-Source Software Notices
Wello uses open-source packages. Package names, license types, and repository links are published in our machine-readable manifest.
Manifest: Download licenses.json
Generated: loading...
| Package | License | Repository |
|---|---|---|
| Loading license manifest... | ||