Download the app
Download the app

Kurmanco

Privacy Policy

This policy explains how Kurmanco handles personal data in the app, website and support channels.

Legal name
Magical Wedding Effects (eenmanszaak)
Trade name
Kurmanco
Address
Wageningsestraat 33, 6671 DA, Zetten, Nederland
Registration
89929780
VAT
NL004772411B71
Privacy
info@kurmanco.com
Support
info@kurmanco.com
Effective date
2026-10-18
Retention
Losse herstelkopieën: maximaal 30 dagen, behoudens een lopende herstel- of beveiligingsprocedure. Gewone CMS-publicatieaudit: maximaal 12 maanden, behoudens langere wettelijke of aantoonbaar noodzakelijke bewaring. Financiële administratie, noodzakelijke aankoop- en betalingsgegevens en migratiehistorie vallen niet onder deze limieten.

Kurmanco — Magical Wedding Effects (eenmanszaak), Wageningsestraat 33, 6671 DA Zetten, Nederland, KVK 89929780, btw-id NL004772411B71 is responsible for the processing described here. Privacy questions can be sent to info@kurmanco.com.

When you create an account, Kurmanco processes authentication identifiers such as email address and account ID. Guest progress is stored locally. Optional cloud synchronization requires a separate choice and authorization; login alone does not enable it. For Premium, Kurmanco processes entitlement status and trusted Apple App Store or Google Play transaction identifiers needed to verify, restore and maintain access. Kurmanco does not receive your complete payment-card details.

If you contact support, we process the information you choose to send. The app, API, CMS and hosting environment can create limited security and operational logs, such as request time, technical failure category and service health. These logs are not used for advertising profiles.

Supabase is used for authentication and protected application data. RevenueCat processes the account identifier, purchase history and entitlement status to manage Premium, including purchase reporting. Apple and Google process store purchases under their own terms. Expo/EAS supports app delivery and updates, and Vercel hosts the website and server applications. Data is used to provide accounts, synchronize learning progress, deliver authorized content, verify Premium access, secure the service, resolve failures and answer support requests.

Authentication credentials and recent trusted entitlement information can be stored with SecureStore. App preferences, cached runtime content, audio indexes and learning-progress synchronization data can be stored locally with platform storage. Removing the app or clearing its storage can remove these local copies; synchronized server data may remain.

Processing needed to provide an account, learning features and Premium is based on performance of the user agreement. Security, fraud prevention and reliable operation rely on legitimate interests. Where consent is legally required, it will be requested separately. Account and progress data is retained while the account is active and then deleted or anonymized according to the final retention schedule: account and learning data: during the account lifetime, followed by removal from active account systems when deletion succeeds; mandatory business records: the applicable statutory period, generally seven years for Dutch basic financial records, without retaining unrelated learning data; support requests: no longer than necessary to handle the request and any specific legal obligation. Supabase Pro provides a seven-day daily-backup recovery window. Provider technical logs follow the actual service settings. Separate recovery exports are retained for at most 30 days, unless needed for an ongoing recovery or security procedure. Ordinary CMS publication audit records are retained for at most 12 months, unless a longer statutory or demonstrably necessary period applies. These limits do not override obligations for financial records, necessary purchase or payment data, migration history or other legally required records. Store and audit records may be retained where law, dispute handling or fraud prevention requires it.

The listed technology providers may process data outside your country. Kurmanco will use the safeguards required for the applicable transfer, subject to final legal review.

Depending on applicable law, you may request access, correction, deletion, restriction, portability or objection. The app provides an account-deletion route; support can help when you cannot use it. You may also complain to your competent data-protection authority.

Children can learn as guests without an account. A parent or caregiver can manage their own account and subscriptions. An account does not establish the age of the person learning. Guest progress stays on the device and is not automatically imported into an account. Child cloud synchronization is not offered. Guest content requests still send technical request information, including an IP address, to the hosting services. Guest access does not require account, purchase or update processing. Kurmanco has no chat, advertising or social features.

The effective date of this policy is 2026-10-18. Material changes will be communicated through an appropriate product or website notice.

Signing in and managing an account do not require a general adult declaration or date of birth. A profile name is optional and can be entered or changed by the account holder. An account or subscription does not establish the age of the person learning on the device. Guest progress is not imported automatically, and child cloud synchronization is not offered.

You may use Apple, Google or email to sign in. Apple/Google exchange a signed identity proof with Supabase; the provider identity and account ID are used, with email and name only when supplied. Under Supabase’s verified-identity security checks, a provider identity may be linked automatically to an existing account with the same verified email. Kurmanco does not merge accounts by name. Apple Private Relay is supported; a different relay address is not automatically treated as the same account. Explicit linking from an authenticated account remains available. No provider sign-in is required for guest learning. Purchases and Restore use Apple/Google and RevenueCat. Deleting an Apple-linked account requires fresh Apple authorization so the server can revoke Apple tokens before account deletion; provider tokens are not retained by Kurmanco. This draft does not certify compliance or authorize unrelated data processing.

Guest learning does not initialize RevenueCat or an Apple/Google sign-in request. Content and media requests still reach the hosting services with technical connection information, including an IP address. Apple and Google sign-in start only after you select that optional sign-in method; guest learning and email sign-in remain available.

After sign-in and verification of the necessary account permissions, RevenueCat may receive the account ID and technical app, operating-system, locale and currency information to establish purchase access, even before a purchase is made. It processes purchase and entitlement information for verification, restoration and purchase reporting. Kurmanco disables automatic advertising-identifier collection and RevenueCat SDK diagnostics; this does not mean that no account or purchase data is processed.

Native automatic update checks are disabled. Any app-requested update check needs its separate permission and an online connection; the request exposes technical connection, platform and runtime information to Expo/EAS. The installed app version shown in Profile is read on the device and does not require an account or a version-check API.

Delete account

← Kurmanco