Back to Perco

Subprocessors

The service providers that process personal data on our behalf to run Perco.

Effective date: 26 August 2026 · Last updated: 2 September 2026

These documents are published in English, and the English version is the governing text.

Overview

To run Perco, LightRoast Studio (KvK 98824546) uses a small number of trusted service providers ("subprocessors") that may process your personal data on our behalf, under contract and only on our instructions. We do not sell your data to anyone.

Current subprocessors

Each entry is in the form provider — role — data it handles — location — transfer safeguard:

  • Supabase — database, authentication and file storage — account, profile, coffee data, social data, uploaded photos — European Union (Frankfurt) — within the EEA.
  • Vercel — application hosting and cookieless web analytics — technical/request data and aggregated, non-identifying analytics — United States — Standard Contractual Clauses.
  • Sentry — error monitoring and (with consent) session diagnostics — technical error data and masked diagnostics — data ingested in the EU region (de.sentry.io); corporate entity in the United States — EU hosting, with Standard Contractual Clauses for any US control-plane access.
  • Resend — sending transactional email such as password resets — email address and message content — United States — Standard Contractual Clauses.
  • RevenueCat — processing in-app purchases made in our mobile apps — your account identifier and the purchase/receipt data the App Store or Google Play returns; card details are handled by Apple or Google and never reach RevenueCat or us — United States — Standard Contractual Clauses.

Apple and Google, and why they are not on the list above

Apple and Google handle two things for Perco, and in both of them they act as independent controllers under their own terms rather than as our subprocessors. They are named here because that distinction is easy to get wrong from the outside, not because we are withholding them from the list.

  • The App Store and Google Play — distributing the app and selling any subscription in it. Each store is the merchant of record for that sale: it takes the payment, holds the card details, issues the receipt and handles refunds under its own privacy policy. We never see a card number. What reaches us is the entitlement — which plan you hold and until when — by way of RevenueCat, which is a subprocessor and is listed above.
  • Sign in with Apple, and signing in with Google — verifying who you are when you choose one of those buttons instead of an email and password. The provider tells us that the sign-in succeeded and gives us an identifier and, if you allow it, an email address. It decides for itself what to record about that, which is what makes it a controller rather than a processor. Sign in with Apple can also hide your real address behind a private relay, and Perco works normally either way.

For what each of them does with your data, see Apple's and Google's own privacy policies.

Changes

We review this list and update it as our providers change. When we add or replace a subprocessor that handles personal data, we will update this page and its "Last updated" date and, where appropriate, notify account holders. To be notified of changes, or if you have questions, contact privacy@perco.app.

Contact

Questions about this document or your data? Email us at privacy@perco.app.