Service Providers and Third Parties
Last updated: 2026-10-27
This page lists every company or system that receives Kwipsy user data, what it receives it for, and its current status. We call it "Service Providers and Third Parties" rather than "Subprocessors" because some recipients act as independent controllers of the data they handle, not as our processors, and "subprocessor" would misdescribe those rows. Our Privacy Policy explains the data categories, purposes, and legal bases in more detail; this page tracks who has access to them.
Status meanings:
- Active — currently receiving data through normal operation. A row only
carries this status once every field below is filled in; a row cannot be
Activewith an unknown region or an unchosen provider. - Planned — not receiving Kwipsy data — disclosed ahead of use, but not yet integrated or waiting on a dependency. Receives nothing today.
- Suspended — temporarily not receiving new data — integrated in the past, paused now; data previously sent to it may still be held under its own retention schedule. No row carries this status today.
- Inactive — no longer receiving new data — permanently disconnected; historical retention may continue until the provider's own schedule expires it. No row carries this status today.
| Last updated | Category | Role | Status | Data & purpose | Region | Retention |
|---|---|---|---|---|---|---|
| 2026-10-27 | OVHcloud — application and database hosting | Processor | Active | Your account, study content, study activity and purchase records, to run the sync server and its database | Canada | As described in our Privacy Policy |
| 2026-10-27 | Cloudflare, Inc. — Cloudflare Tunnel in front of our servers | Processor | Active | All of the app's requests to our sync server, analytics and crash reporting, in transit, including the IP address they come from, so they reach our servers without opening them to the internet | Global edge network; Cloudflare, Inc. is a US company | Cloudflare's own network logs follow its retention; our own server logs are described in our Privacy Policy |
| 2026-10-27 | Cloudflare, Inc. — R2 object storage | Processor | Active | Images and audio you add to cards | Eastern North America (the storage location we requested); Cloudflare, Inc. is a US company | Until account deletion, as described in our Privacy Policy |
| 2026-10-27 | Cloudflare, Inc. — email sending and email routing | Processor | Active | Your email address and the sign-in and password codes we send you; emails you send to our addresses, forwarded to our mailbox | Global edge network; Cloudflare, Inc. is a US company | Cloudflare's own retention |
| 2026-10-27 | Cloudflare, Inc. — domain, nameservice and hosting for kwipsy.com | Processor | Active | Website traffic metadata | Global edge network; Cloudflare, Inc. is a US company | Cloudflare's own retention |
| 2026-10-27 | Superwall, Inc. — the Kwipsy Pro subscription screen | Processor | Active | Your account identifier, a device identifier for apps from the same developer, device and app information, the approximate location derived from your IP address, subscription-screen views and purchases, to show the Kwipsy Pro offer and complete a purchase | United States | Superwall's own retention |
| 2026-10-27 | Apple Inc. — Sign in with Apple, App Store purchases, App Attest | Independent controller | Active | Your sign-in with Apple and Apple's token for Kwipsy (revoked when you delete an account created with Apple); your App Store subscription; the App Attest check behind Google sign-in | United States and other countries where Apple operates | Apple's own retention |
| 2026-10-27 | Google LLC — Sign in with Google | Independent controller | Active | Your sign-in with Google | United States and other countries where Google operates | Google's own retention |
| 2026-10-27 | Google LLC — Firebase App Check and ML Kit | Processor | Active | The App Check request that proves the app is genuine before Google sign-in; ML Kit's technical information about the device, the app and how on-device language detection performs (the text stays on the device) | United States and other countries where Google operates | Google's own retention |
| 2026-10-27 | Google LLC — Google Play purchases | Independent controller | Planned — not receiving Kwipsy data | None today: Kwipsy is not on Google Play yet. When it is: your Google Play subscription | United States and other countries where Google operates | Not yet applicable |
| 2026-10-27 | Analytics — self-hosted: open-source PostHog on servers we operate | Operated by us — not a third party (requests reach it through Cloudflare Tunnel; see that row) | Active | Analytics events, only after you agree, with the country derived from the IP address; the IP address is not kept in analytics data | Republic of Korea | 12 months |
| 2026-10-27 | Crash reporting — self-hosted: open-source GlitchTip on servers we operate | Operated by us — not a third party (requests reach it through Cloudflare Tunnel; see that row) | Active | Crash reports: a random installation identifier, device and app information, the error and a log of recent events in the app | Republic of Korea | 90 days |
Change log
- 2026-10-27 — Kwipsy's service is running, so the rows describe it as
it runs: hosting (OVHcloud, Canada), Cloudflare Tunnel in front of all our
servers, R2 storage for card media, email sending and routing, Superwall
for the subscription screen, Apple and Google for sign-in and store
purchases, and Google's ML Kit and Firebase App Check (as a processor)
are
Active; Google Play staysPlanneduntil Kwipsy is on Google Play. - 2026-10-10 — Analytics and crash reporting are no longer "not yet chosen": both run on open-source software (PostHog and GlitchTip) on servers we operate in the Republic of Korea, so no analytics or crash-reporting company receives data; requests reach them through Cloudflare Tunnel, which now has its own row. The analytics row now says it derives the country from the IP address and does not keep the address in analytics data.
- 2026-08-27 — Removed two rows for a card-generation feature that is not part of the product today. They will return, correctly scoped, once that feature actually ships.
- 2026-08-12 — Page created, then corrected the same day after a factual check of what was actually running.
We keep this page current as our list of providers changes. We do not
promise advance notice before a new provider is added, since we cannot
guarantee that operationally; we do promise that a provider does not move
to Active for a category of data until this page reflects it, with every
field in its row filled in.
The party popper illustration is from Microsoft Fluent Emoji, used under the MIT licence.