subprocessor list

jollygig uses a small number of third-party services ("subprocessors") to operate. this page lists every subprocessor that touches data covered by our privacy policy. we update this page when our subprocessor list changes and give customers at least 30 days' notice of any material additions.

if you're a customer with a signed data-processing addendum (dpa), this list forms part of the annex to that agreement. a template dpa is available on request at legal@jollygig.app.

infrastructure & storage

google — firebase auth & cloud firestore

• entity: google llc (google cloud emea ltd for eea customers)
• purpose: authentication (magic-link sign-in via firebase auth); structured data storage for team records, survey-response aggregates, action plans, and billing state (cloud firestore).
• data processed: email addresses, display names, team configuration, aggregated survey signal, action plans. survey responses are stored without a user_id by structural design — see the privacy policy for details.
• processing region: us-central1 (iowa).
• transfer mechanism (eea/uk): standard contractual clauses (scc) — google's data processing addendum includes sccs and is accepted during firebase project creation.
• security certifications: iso 27001, soc 2 type ii, pci dss (level 1). see cloud.google.com/security/compliance.
• subprocessor page: cloud.google.com/terms/subprocessors

google — firebase app hosting

• entity: google llc
• purpose: serving the jollygig web application and api (runs on google cloud run behind firebase app hosting).
• data processed: inbound http requests including ip addresses and request headers. request ids are written to cloud logging; no user content is logged by default.
• processing region: us-central1 (iowa).
• transfer mechanism (eea/uk): standard contractual clauses (scc) via google's data processing addendum.

payments

stripe, inc.

• entity: stripe, inc. (stripe payments europe, ltd. for eea customers)
• purpose: payment processing and subscription management. managers who upgrade past the free trial enter card details directly in stripe-hosted elements — card numbers are never transmitted to jollygig's servers.
• data processed: billing contact details, payment card metadata (brand, last four digits, expiry). full card numbers and cvcs are held only by stripe.
• processing region: united states and ireland (eea customers).
• transfer mechanism (eea/uk): stripe's standard contractual clauses. see stripe.com/legal/dpa.
• security certifications: pci dss level 1 service provider. see stripe.com/docs/security.

email delivery

[email provider — placeholder, board decision pending — see legal@jollygig.app for current status]

• purpose: transactional email only — magic-link sign-in emails, survey invitation emails, and billing notifications. we send no marketing email without explicit opt-in.
• data processed: recipient email address, first name (for personalisation), and delivery metadata (open/click events are disabled — we do not track whether you opened an email).
• this entry will be completed with the provider name, entity, processing region, and transfer mechanism once the board selects an email provider.

no analytics subprocessors

jollygig carries no client-side analytics, ad pixels, or third-party tracking scripts. our no-tracking pledge is described in the privacy policy. the only observability tool we use for the public-facing site is google search console, which does not process visitor data — it analyzes google's own crawl data.

changes to this list

we will update this page when we add, replace, or remove a subprocessor. customers with a signed dpa will receive email notice at least 30 days before any material addition. if you object to a new subprocessor, please contact legal@jollygig.app within 30 days of the notice.

contact

questions about this list, or requests for a data-processing addendum: legal@jollygig.app.