Grace Connect Legal Center
Third-Party Provider & Processor List
The main providers Grace Connect may use to operate authentication, storage, notifications, maps, analytics, and giving links.
Last Updated: June 16, 2026
| Provider | Purpose | Data Involved |
|---|---|---|
| Supabase | Authentication, database, storage, row-level security, backend infrastructure, user sessions | Account, church, profile, roles, messages, posts, support, attendance, and app data depending on configuration |
| Firebase / Google Cloud | Push notifications, cloud functions, analytics, diagnostics, messaging support | Notification tokens, app events, device/app diagnostics, user/church identifiers where needed |
| Google Sign-In | Optional sign-in method where enabled | Google account identifier, email, name, profile information allowed by user |
| Google Maps / Geolocation APIs | Maps, church location, geofencing, attendance location support | Location/address/geofence information where enabled |
| External Giving Provider selected by church | Tithes, offerings, donations, payment processing, receipts | Payment details handled by the provider; Grace Connect may store limited references or receipt links |
| Email/Notification Delivery Provider | Account verification, password reset, support emails, platform notices | Email address, name, message content, account status notices |
| Apple App Store / Google Play | App distribution, app review, store listings, crash/diagnostic reports depending on platform | Store account/device/app diagnostics as controlled by Apple or Google |
Provider Changes
This list may change as Grace Connect adds, removes, or replaces service providers. Material provider changes should be reflected in the Privacy Policy and app store disclosures.