Release details
Current published document
- Version
- 1
- Published
- August 23, 2026
- Effective
- August 23, 2026
Provider and Subprocessor Disclosure
Effective date: 21 August 2026
This page identifies the service providers and platform operators used for the current Planique release. It supplements the Privacy Notice and Private Vault Processing Terms.
Planique is operated by Cropol Labs d.o.o., Ulica sv. Ane 30A, 31000 Osijek, Croatia, company number 030322161.
1. How to read this page
The same organization can have different privacy roles for different activities. A provider may process Planique-controlled account information on our instructions, act beneath Planique for account-holder-directed private-vault processing, and independently determine how it handles its own account, store or platform information. The actual activity and contract control the role; the label alone does not.
Supabase is the only current provider to which Planique intentionally sends private-vault content. The other providers below receive only the minimum account, platform, purchase or generic operational information needed for their function.
2. Current providers and platform operators
| Provider or platform | Function and Planique information | Current role and location position |
|---|---|---|
| Supabase, Inc. | Authentication, database, private file storage, server functions, exports, logs and database backups. It receives account information and the private-vault content the user chooses to store. | Processor for Planique-controlled information and subprocessor for account-holder-directed vault processing. The production project uses a specific EU primary region. Supabase support, remote access and subprocessors may nevertheless involve the United States or other countries. |
| Expo / 650 Industries, Inc. | Build, update and credential operations, push token, generic notification text, opaque notification reference, ticket and receipt. | Provider for Planique-directed build and push operations and, where its terms provide, an independent operator for its own account or usage information. US and other remote processing may occur. |
| Apple Push Notification service | App-specific device token, generic notification text, opaque reference and delivery metadata for Apple devices. | Apple operates the delivery platform under its terms. Processing may occur internationally. |
| Firebase Cloud Messaging / Google | App-instance or device token, generic notification text, opaque reference and delivery or diagnostic metadata for Android devices. | Google provides message delivery under the applicable Firebase terms and may independently handle limited service information where those terms provide. Processing may occur internationally. |
| Google Sign-In | Provider subject identifier, email and the minimum authentication claims and security information needed to link the sign-in. | Google independently operates the Google-account authentication service. Planique controls the claims it receives and the resulting account link. |
| Sign in with Apple | Developer-specific user identifier, email or relay email, name only if supplied, and limited authentication or fraud information. | Apple independently operates Apple-account authentication. Planique controls the claims it receives and the resulting account link. |
| RevenueCat, Inc. | Random internal Planique account UUID, aliases required for purchase restoration, store/product/transaction identifiers, entitlement state and subscription events. | Processor for Planique subscription administration and an independent controller only for its own business-account information where its terms provide. RevenueCat and its infrastructure or subprocessors may process information in the United States or elsewhere. |
| Apple App Store and Google Play | Platform account, device/storefront, purchase, payment, tax, transaction, refund and subscription status. Planique receives only the information needed for entitlement and settlement. | Apple and Google generally independently operate their store and payment relationships. Their global platform and transfer terms apply. |
| Vercel, Inc. | Public website delivery and contact-form transit: request and security metadata plus the minimum contact details, inquiry category and non-sensitive message entered by the visitor. The form accepts no attachments. | Processor for Planique website customer data under the applicable agreement and an independent controller for its own contact or service-generated information where its terms provide. Primary US processing, global edge delivery and international subprocessor access may occur. |
3. Providers not currently receiving Planique production data
Sentry is not installed. Planique does not currently send Sentry diagnostic events. It may be enabled only after the public disclosure, contract, region, retention and tested egress controls are updated.
Resend is not integrated. Planique does not currently route transactional email or data-copy archives through Resend. If a future release enables it, Planique will update this page before it receives production information.
Planique has no approved advertising, behavioural-analytics, session-replay or cross-site tracking provider for the app or public website.
4. Strict information boundaries
- Remote notifications contain the generic message “You have a Planique reminder.”, a schema version and one random per-notification UUID. The UUID grants no access without an authenticated, owner-limited lookup.
- Planique does not intentionally send module names, profile labels, medication, appointment, cycle, financial, journal, work or other vault details to Expo, APNs or FCM.
- RevenueCat receives a random Planique account UUID—not a name, email, phone, advertising identifier, Health profile ID or content-derived identifier.
- Planique does not put private-vault content in app-store disclosures, subscription metadata, website analytics, ordinary support tickets or the contact form.
- A prepared data-copy archive is not sent as an email attachment. It remains protected in the authenticated short-lived export process.
5. International transfers
An EU primary storage region does not mean that every provider, support action or subprocessor remains in the EEA. Where EEA information is transferred to a country without an applicable adequacy decision, Planique uses the applicable EU Standard Contractual Clauses, valid EU–US Data Privacy Framework participation, supplementary technical and organisational measures, or another lawful mechanism. We also minimize the information, restrict access and limit retention according to the function involved.
6. Changes and objections
Planique reviews this page before adding or materially changing a provider. We will update the current list and provide any notice or choice required by law before a new provider receives private-vault content or another materially new category of information.
Where applicable law gives you a right to object to a new subprocessor, please contact support or write to planique.planner@gmail.com. Identify the provider and explain the relevant data-protection grounds. If the concern cannot reasonably be resolved, Planique may need to stop the affected feature or support account export and closure.
7. Contact
Privacy Officer: Chief Executive Officer, Cropol Labs d.o.o.
Email: planique.planner@gmail.com
Address: Ulica sv. Ane 30A, 31000 Osijek, Croatia