Sub-processors

Last updated: 2026-04-18 (version v1.1-2026-04-18)

Draft notice. This page is an AI-drafted starting point. PrayerJar is not a law firm. Consult qualified counsel before relying on this list for a signed customer commitment.

PrayerJar uses the third-party services ("sub-processors") below to operate the platform. Each sub-processor is engaged under terms no less protective than those in our Data Processing Addendum.

We give enterprise customers 30 days' notice before adding a new sub-processor that processes their data. To be notified, email legal@prayerjar.org.

ProcessorPurposeData categoriesRegionDPA
Vercel, Inc.Web application hosting, edge runtime, file/blob storage (Vercel Blob), analytics, and image rendering. Primary platform provider.All application data transits Vercel infrastructure. IP addresses, request metadata, uploaded media, OG images.United States (global edge)View
Neon, Inc.Primary PostgreSQL database (Neon serverless). Stores users, prayers, church records, pastoral notes, and all application data.All personal data stored by PrayerJar including prayer content and pastoral-care content.United StatesView
Resend, Inc.Transactional email delivery — magic-link sign-in, notifications, digest emails, admin alerts.Recipient email address, email body (may include prayer-related content).United StatesView
Stripe, Inc.Payment processing for subscriptions and donations. Checkout, invoicing, webhook events.Billing contact, payment method metadata (no card numbers stored by PrayerJar), church/plan identifiers.United StatesView
Vercel AI GatewayAI request routing used to call downstream model providers (see Anthropic below) for prayer categorization and content moderation.Prayer text and image URLs sent for categorization / moderation. No training use.United States (global edge)View
Anthropic, PBCAI model provider reached via Vercel AI Gateway (claude-haiku-4.5). Used for prayer categorization and content moderation only. Anthropic's zero-retention commitments via the Gateway apply.Prayer text and image URLs sent for categorization / moderation.United StatesView
Sentry (Functional Software, Inc.)Application error and performance monitoring.Error stack traces, scrubbed request context, limited user identifiers. Prayer content is not intentionally logged.United StatesView
Google LLC — Places APIChurch-finder lookup (Google Places) on the public /find-a-church experience.Search queries (e.g., city/zip), approximate device location if provided. No personal account data.United States (global)View
Planning Center Online, Inc.Optional Church Management Software (ChMS) integration. When a church admin connects PrayerJar to their Planning Center account, PrayerJar reads member rosters and small-group membership over OAuth-scoped API access. Connection is opt-in per church.Inbound from PCO to PrayerJar: member names, primary email addresses, phone numbers (where the church stores them), membership status, small-group membership. Outbound from PrayerJar to PCO: weekly prayer-activity summary written to the person's Notes record (only for churches that enable the push-back feature).United StatesView
Apple Push Notification service & Google / Firebase Cloud MessagingDelivery of push notifications to iOS and Android devices via Capacitor push. Device push tokens are sent to the respective platform.Device push tokens, notification payload (title/body).Global (Apple / Google regions)View

Questions

Email legal@prayerjar.org with any data-processing question, or read our Data Processing Addendum, Privacy Policy, and Terms of Service.