Amida MakerTakeKApp

Amida Maker / Support

Privacy policy

How Amida Maker handles information, including the external services used for ads, purchases, analytics and diagnostics.

  • Draw lists saved on your device
  • External ad & purchase services
  • Production analytics & diagnostics are automatic

Last updated: November 16, 2026 · Operated by TakeKApp

On this page
  1. 1. Data on your device
  2. 2. Sharing and support
  3. 3. Retention and deletion
  4. 4. Backups and external websites
  5. 5. Changes and contact
  6. 6. Advertising and choices
  7. 7. Purchases and restoration
  8. 8. Usage analytics and crash diagnostics
  9. 9. Retrieving ad serving settings
  10. 10. Watching an Amida room

1. Data on your device

The app saves participant names, prizes/results, named setups and lists, draw progress, up to 20 recent completed results and their replay data, and language, sound and theme settings on your device. Advertising and one-time ad removal use the services described below. Firebase provides usage analytics and crash diagnostics to improve app quality. Advertising and purchase SDKs also process data needed for their services.

2. Sharing and support

When you choose to share a result card, the app passes the generated images to your chosen app using the operating system's sharing feature. The destination's policies govern subsequent storage and sending. Hiding participant names affects only the participant column, not the title or prize text. Review the whole card before sharing.

Support messages open in your mail app for you to review and send. Participant and prize text is not attached automatically. Information and email addresses received through support are used to answer requests and investigate issues. We delete information when it is no longer needed after handling the request.

3. Retention and deletion

Use “Delete all saved data” in settings to clear the app's saved content. Uninstalling removes local app data, but system backups and previously shared images are managed separately. The app cannot delete images already sent to another app. Generated images may remain in temporary storage managed by the OS or sharing feature.

Deleting saved data keeps your display language, purchase entitlement, ad consent and images already shared. Deleting local data does not delete information already sent to external services.

4. Backups and external websites

Android automatic app backup is disabled. On iOS and other systems, manage any backups containing app data through the operating system's settings. External support or store websites may process access information when you visit them.

5. Changes and contact

If data handling changes, we will update this policy and the relevant in-app information. Privacy contact: takekapp1990@takekapp.com

6. Advertising and choices

The free version shows Google AdMob banners on the input screen and may occasionally show a full-screen ad when returning to the input screen after reviewing draw results. The one-time ad-removal purchase removes both formats. Google Mobile Ads and UMP may process IP addresses, device or advertising identifiers, ad views and interactions, diagnostics and consent choices for advertising, measurement and fraud prevention. Approximate location may be inferred from an IP address. The app does not pass participant names, prizes or draw results to ad SDKs.

Consent screens are presented according to region and configuration. When available, “Ad privacy choices” in settings lets you change your selection. iOS tracking permission can be changed in system settings. Draws remain available when you decline. Ad removal stops new ad requests by this app; it does not delete previously transmitted information.

Google policy: https://policies.google.com/privacy

Advertising mediation also uses Unity Ads and Liftoff Monetize (formerly Vungle). Depending on the ad served, these providers may process approximate region inferred from IP addresses, device or advertising identifiers and SDK-generated identifiers, app/device information, ad-related purchase history or purchasing tendencies, ad views and interactions, diagnostics, and consent choices for ad delivery, measurement and fraud prevention. Privacy signals are applied before ad requests. The app does not grant sale/sharing consent to either provider. European consent follows vendor-specific TCF signals from UMP, and iOS ATT restrictions also apply.

Unity Ads: https://unity.com/legal/privacy-policy

Liftoff Monetize: https://liftoff.io/privacy-policy/

7. Purchases and restoration

Apple App Store / Google Play and RevenueCat provide one-time ad removal. RevenueCat processes a randomly generated app user ID, receipts or purchase tokens, purchase history, entitlement status, and device/app information to verify and restore purchases and prevent fraud. We do not send names, email addresses or input lists as RevenueCat user attributes. The store processes payment details; the app does not receive card numbers.

Deleting local data does not erase store transaction records, purchase rights or external service records. Contact us at the address above for purchase-data access or deletion requests. Records needed to maintain transactions or meet legal obligations may be retained.

RevenueCat policy: https://www.revenuecat.com/privacy

Apple policy: https://www.apple.com/legal/privacy/

Google policy: https://policies.google.com/privacy

8. Usage analytics and crash diagnostics

Production builds automatically enable Firebase Analytics and Crashlytics reporting at startup to improve quality and reliability. There is no reporting toggle in the app. This operates separately from advertising consent and tracking permission; analytics advertising-ID collection and advertising-related data use remain disabled. Google processes usage counts, ad load outcomes, impressions, clicks, SDK-provided revenue information, app/OS/device information, identifiers such as app instance IDs, approximate region derived from IP addresses, and crash stacks. We do not add participant names, prize or result text, shared images or custom user IDs to events or diagnostic attributes. Dart exception messages are replaced with fixed categories. Native crashes include diagnostic information generated by the SDK.

Deleting saved game data does not delete information already sent. Retention at Google follows service settings and policies. Contact us at the address above for inquiries.

Firebase privacy: https://firebase.google.com/support/privacy

9. Retrieving ad serving settings

Production builds use Firebase Remote Config to retrieve operational settings such as stopping ads. This serves a separate purpose from analytics and diagnostics reporting. Google processes Firebase installation IDs and other information needed to provide the service. Participant names, prizes and draw results are not sent when retrieving settings.

10. Watching an Amida room

If you host a room, the app sends the spectator board, participant names and icons shown on it, visible prizes, draw progress, and revealed results to Firebase Realtime Database. They are displayed to devices that join using the room code. The app uses an identifier issued by Firebase Anonymous Authentication when you host or join. Rooms are accessible for up to two hours, and room data is deleted after expiry. The hosting reward uses a signed AdMob notification and a reward verification identifier. The expiry time for the ad-free reward is saved on your device.

Questions? Contact support

Get help with the app, purchases or how your data is handled.

Support