Sub-processors
Version: June 28, 2026
These are the third-party providers we use to operate Piqlo. Where a provider processes personal data for us, we rely on that provider's data processing terms and transfer safeguards, including Standard Contractual Clauses (SCCs) where required. This page is part of our Privacy Policy.
| Provider | Purpose | Data handled | Location & transfer basis |
|---|---|---|---|
| Cloudflare (US) | Our whole platform: database (D1), object storage (R2), cache (KV), compute (Workers), analytics store (Analytics Engine), CDN, and security. | Account and card data, card images, and scan analytics (country, city, device; never a raw IP). | D1 under EU jurisdiction; R2 images in the EU region (Western Europe); KV cache and CDN globally replicated. SCCs cover any limited transfer. |
| Cloudflare Web Analytics (US) | Cookieless page-view measurement. | Aggregate page views and device type. No cookies, no tracking identifiers, no raw IP. | Global edge. |
| Google Firebase (US) | Authentication (Google and email sign-in). | Email, display name, profile picture, and email-verification status. | US (EU SCCs in place). |
| Apple (US) | Apple Wallet (PassKit) loyalty pass delivery and Apple Push Notification service (APNs) for over-the-air pass updates and app notifications. | Device registration identifiers and push tokens, and the pass contents (such as the opaque member token and stamp count). Push messages that signal a device to refresh its pass or that an event occurred. | US (EU SCCs in place). |
| Google (US) | Google Wallet loyalty pass issuance and updates, signed through a Google Cloud Run service we operate. | Pass contents: the opaque member token, stamp count, reward label, optional member first name, branding, and owner-written pass copy. | US (EU SCCs in place). |
| Google Places (US) | Optional business-lookup autofill when you import your business while creating a card. | The business name or search text you type and opaque place identifiers. No end-customer personal data is sent. | US (EU SCCs in place). |
| Replicate (US) | AI QR artwork generation (only if you use AI art). | Your art prompt and the URL the QR encodes (the Piqlo short link for dynamic codes, or the destination URL you set for a static URL code). No account-holder or end-customer personal data is sent. | US (EU SCCs in place). |
| Giphy (US) | GIF search for the free animated-QR tool (only if you use it). | Your search query. No personal data. The animated-QR output is rendered, streamed, and never stored; search-result metadata is briefly cached to save quota. | US (EU SCCs in place). |
| Resend (US) | Transactional email (account, billing, and service messages). | Your account email address, your first name (for the greeting), and the type of message. | US (EU SCCs in place). |
| Grafana Cloud / Faro (EU) | Frontend error monitoring and performance (RUM), via the Grafana Faro SDK. | JavaScript errors and an anonymous session identifier. Email, username, and user ID are stripped before data is sent. | EU (no transfer outside the EEA). |
Payments: Stripe
Stripe processes subscription payments. For payment-card data, Stripe acts as an independent data controller, not a Piqlo sub-processor: your card details go directly to Stripe and never touch Piqlo. We store only your Stripe customer ID and your subscription plan. Stripe is a US company; EU SCCs are in place. We list it here for transparency.
Changes to this list
We keep this page current. Before we add a new sub-processor that handles personal data, or make another material change, we will notify account holders by email or an in-app notice. Business customers may object on reasonable data protection grounds within 30 days, as set out in our Data Processing Agreement. The version date above reflects the most recent update.