Klapivo Privacy Policy
1. Information kept on your device
Your selected language, saved sounds, recent-play history and downloaded catalog files are stored locally on your device. They are not uploaded as a user profile. You can clear recent history inside the app and remove the remaining local data by uninstalling the app or clearing its storage in Android settings.
2. Catalog and media requests
When Klapivo checks for catalog updates or downloads an approved sound pack, the Klapivo service and its hosting provider may process standard network information such as IP address, request time, requested path, response status, app version, locale and market. This is used to deliver files, protect the service, prevent abuse and diagnose failures. The app does not upload your favorites, recent history or microphone recordings. It does not request microphone, camera, contacts or precise-location access.
3. Firebase Analytics
When the Firebase integration is available, Firebase Analytics starts automatically and Klapivo sends a restricted set of product events and technical app/device information to Google Firebase so that BloksyMedia can understand reliability and feature usage. Klapivo does not include typed text, filenames, sound content, email addresses or raw error messages in its own analytics events. Advertising storage, advertising user data and ad-personalization signals remain disabled by the app.
4. Firebase Crashlytics
When the Firebase integration is available, Firebase Crashlytics starts automatically and may process crash stack traces, timestamps, app version, operating-system and device information, Firebase installation identifiers and related diagnostics so that faults can be investigated. Klapivo's own non-fatal reports use fixed error categories instead of free-form personal content. Google states that Crashlytics crash traces and associated identifiers are retained for 90 days before removal begins. The current version does not provide a separate in-app switch for this technical service.
5. Advertising and consent
Advertising consent is separate from Firebase preferences. Where required, Google's User Messaging Platform presents the available consent choices before the Google Mobile Ads SDK may request an ad. Depending on your choices and applicable law, Google Mobile Ads may process IP address (including general location inferred from it), ad and app interactions, diagnostics, and device or app identifiers for ad delivery, analytics and fraud prevention. Klapivo blocks the Android Advertising ID permission and never receives AdMob App IDs or ad-unit IDs from the catalog server. A missing consent result, invalid policy or server kill switch keeps ads off without blocking the soundboard.
6. Service providers and sharing
Data is disclosed only as needed to operate Klapivo: to the isolated hosting provider for catalog delivery, and to Google for the Firebase, UMP and AdMob services described above. BloksyMedia does not sell personal data. These providers may process data in countries other than yours under their own contractual and legal safeguards.
7. Retention, security and your choices
Device-local data remains until you clear it or remove the app. Operational server records are retained only for as long as reasonably necessary for security, abuse prevention, troubleshooting and legal obligations. Google-service data follows the applicable Google/Firebase settings and retention rules. Network traffic uses HTTPS. No system can be guaranteed perfectly secure, but access to production systems is restricted and the public catalog does not expose private editorial or rights evidence.
The current version does not provide separate in-app switches for Analytics or Crashlytics. When Google requires it, you can reopen the advertising privacy form from the app. Because Klapivo has no account, BloksyMedia cannot map anonymous device-local history back to you. For questions or a request concerning server-side data, contact wanish.hammouda@gmail.com.
8. Changes to this policy
This page will be updated when Klapivo's data practices or service providers materially change. The new effective date will be shown above. Material changes that require a new choice will not silently reuse a previous opt-in.
9. Contact
Data controller: BloksyMedia
Email: wanish.hammouda@gmail.com
App: com.bloksymedia.klapivo