Privacy Policy
Last updated: November 15, 2026
We develop and operate the applications listed in this Privacy Policy. This policy explains what information may be processed when you use our applications, why it is processed, and the choices available to you.
This policy applies to:
- Tebak Lagu Nostalgia
- Music Player
- Peterpan Noah
- Didi Kempot
- Jet Rabbit
- Kisah Nyata
The applications have different features and integrations. An app-specific section below explains the processing currently associated with that app. Third-party providers may also process information under their own privacy policies.
Information We Process
Depending on the application and the features you use, information processed may include:
- Information you send us, such as your email address and the contents of a message when you contact support or send feedback.
- App and device information, such as device or installation identifiers, device type, operating system and version, app version, language, and diagnostic information.
- Usage events, such as app sessions, screens or features used, playback actions, downloads, favorites, and errors. The events collected differ by application.
- Advertising information, which may be processed by advertising providers to deliver, measure, and, where permitted by your settings and applicable law, personalize ads.
- Information needed to provide online content, such as requests for songs, story content, or images. Our servers and hosting providers may receive technical information associated with these requests, such as an IP address, request time, and basic browser or app connection details.
Some applications store settings, favorites, downloaded media, or reading progress locally on your device. This locally stored information is generally removed if you clear the app's data or uninstall the app, unless your device backs it up separately.
Advertising and Third-Party Services
Some of our applications are ad-supported and use Google AdMob. AdMob and Google Play services may process device and advertising information to provide and measure advertising, prevent fraud, and operate their services. Your advertising and privacy settings, as well as applicable regional consent requirements, may affect how information is used.
Some applications may use crash reporting or other diagnostic services. When enabled, these services may receive app version, device and operating system details, crash reports, and related diagnostic data.
Third-party services operate under their own terms and privacy policies. For Google services, see:
We do not control the information practices of third-party providers. Please review their policies and use the privacy controls offered by your device, Google account, and the relevant service.
How We Use Information
We may use information processed by an application to:
- provide the app's features and requested content;
- remember app preferences or locally stored progress;
- maintain and improve app performance;
- understand feature usage where usage analytics are enabled;
- diagnose crashes, errors, abuse, and technical problems;
- display and measure advertisements where the app is ad-supported; and
- respond to support requests.
We do not sell personal information. Reading in Kisah Nyata does not require Google sign-in. Some optional account-based features, such as Daily Check-in rewards, do require sign-in.
Sharing and Retention
Information may be processed by service providers that help us host content, deliver advertising, process app events, or diagnose technical problems. They may process information as needed to provide their services and as described in their own privacy policies.
Information is retained only for as long as reasonably needed for the purposes described in this policy, to maintain the service, or to meet legal requirements. Locally stored information can generally be removed by clearing the app's data or uninstalling the app. Server-side retention periods depend on the data and service involved.
Security
We use reasonable measures to protect information handled by our services. However, no method of transmission or electronic storage is completely secure, and we cannot guarantee absolute security.
Children's Privacy
Our applications are not intended for children under 13, and we do not knowingly collect personal information directly from children under 13. If you believe a child has provided personal information to us, contact us so we can review and take appropriate action. Where an app or platform has additional age-related requirements, those requirements also apply.
Your Choices and Requests
You can stop using an application's optional features, adjust available advertising or privacy settings on your device or Google account, and remove locally stored app data by clearing the app's data or uninstalling it.
To ask a question or make a privacy-related request about information handled by Duanestrastudio, contact us at duanestrastudio@gmail.com. Some information processed directly by Google or another third-party provider must be managed through that provider.
Changes to This Policy
We may update this Privacy Policy when our applications, services, or legal requirements change. We will post the revised policy on this page and update the date above. Changes take effect when posted.
Contact Us
If you have questions or requests about this Privacy Policy, contact us at duanestrastudio@gmail.com.
Application-Specific Information
Tebak Lagu Nostalgia
Tebak Lagu Nostalgia is an ad-supported game. The game may store game progress or preferences on your device. The game uses Google Play services, AdMob, and Firebase Crashlytics. These providers may process advertising, device, and diagnostic information as described in their respective privacy policies.
Music Player
Music Player displays ads using Google AdMob. The app stores certain playback and library information on the device so its music-player features can work.
The app also sends usage events to a Duanestrastudio analytics service. The events can include a device identifier, operating system and version, app version and build, session information, and actions such as starting or stopping playback, selecting artists or songs, downloading songs, changing favorites, and playback errors. Events may be queued on the device while it is offline and sent when a connection is available.
Peterpan Noah
Peterpan Noah displays ads using Google AdMob and retrieves music content from Duanestrastudio services. The app also sends usage events to a Duanestrastudio analytics service. Those events can include a device identifier, operating system and version, app version and build, session information, and actions such as playback, downloads, favorites, and playback errors. Events may be queued on the device while it is offline and sent when a connection is available.
Didi Kempot
Didi Kempot displays ads using Google AdMob and retrieves music content from Duanestrastudio services. Downloaded music, where available, may be stored locally on your device. Requests for online music and ads may be processed by the relevant hosting or advertising providers, which may receive technical connection information such as an IP address.
Jet Rabbit
Jet Rabbit is a game. Game progress or preferences, where applicable, may be stored on your device. Information processed by the app store or any third-party SDK included in a particular release is subject to that provider's privacy policy. No account is required to play.
Kisah Nyata
Kisah Nyata retrieves story text, covers, and related content from Duanestrastudio services. The app stores favorites, the last-read story, reading position, display preferences, and story filter preferences locally on your device.
To help prevent direct browser access to story APIs, Kisah Nyata uses Google Play Integrity when establishing or renewing an anonymous app session. No Google sign-in is required to read. The app sends an encrypted integrity token to Duanestrastudio's server, which asks Google Play to verify that the request comes from a recognized, Play-licensed installation of Kisah Nyata. The token is used for verification and is not stored as a user account. The server issues a temporary session for story requests; it does not contain your name or Google account identifier. Google and our hosting provider may process technical request information, such as IP address and request time, to provide and protect this feature. Google processes Play Integrity information under its own privacy policies.
When you use story filters, the selected category and region may be included in requests to our server so the app can retrieve matching stories. Filter preferences are not included in the Google sign-in backup described below.
The app records qualifying story-read events to update public story readership counts. These records include a story identifier, an event identifier, and the time the event was recorded; they are not currently linked to a Google account in the app's database. Requests to retrieve content or submit read events may also be processed by our hosting provider.
Google sign-in is optional. If you choose to sign in, the app receives basic Google profile information, including your name and email address, to show which account is signed in. While signed in, the app also backs up your favorite stories, reading progress (last read story and scroll positions), and reader preferences (font size, dark mode, auto-scroll speed) to Duanestrastudio's server over HTTPS so they can be restored on another device.
The app sends a Google ID token with each sync; the server verifies it with Google, stores your Google email address with the backup so the backup can be identified, and keys the backup by a one-way SHA-256 hash of the Google account identifier. Your name and profile photo are not stored in the backup. The backup contains only story summaries, such as title, category, cover, and reading time, not story text.
Daily Check-in is optional and requires Google sign-in. The app sends a Google ID token to our server, which verifies it and identifies the account using a one-way SHA-256 hash. The server stores the verified Google email address alongside that hash, as well as check-in dates, consecutive-day progress and any Premium reward expiry; it does not store the raw Google account identifier. The server uses the Jakarta calendar date and grants Premium after the number of consecutive daily check-ins and for the duration configured by the administrator (default: seven days and 24 hours). The app caches the expiry on the device so the reward works offline only until that time.
The in-app "Hapus data tersimpan" action deletes both the Google backup and Daily Check-in progress/reward for that account, then signs you out; data on your device is kept except the local check-in cache. You can also request deletion by contacting duanestrastudio@gmail.com. Google processes sign-in information under its own privacy policy.
The app displays ads using Google AdMob. Google and its services may process advertising and device information as described in Google's privacy policies.
Premium subscriptions are purchased through Google Play and are associated with the Play Store account, not the optional Google sign-in inside the app. To verify, restore, and grant a subscription, the app sends the purchase token to Duanestrastudio's server over HTTPS. The server verifies the token with Google Play and does not retain the raw token. The app caches the verified subscription expiry on the device so Premium features remain available offline until that expiry.
An administrator may provide a reusable Premium access code independently of Google Play. If you enter one, the app stores the code in its private local storage and sends it to our server over HTTPS to check access. The server stores new codes and a one-way hash; authorized administrators can view the codes in the CRM. Older codes may be stored only as hashes. The app caches code-based access for up to 24 hours after verification for offline use. A code may be disabled by an administrator.
Users may submit a Saran & Masukan message when the feature is available to them. The app does not request a name or email for this feature, although you may include personal information in the message itself. Authorized CRM administrators can read and update the status of these messages.
When Premium is required, the server verifies the purchase token or Premium code and stores a one-way SHA-256 hash derived from it with the message to enforce submission limits. The raw purchase token is not stored with the message, and the message is not linked to a Google profile.
When Saran & Masukan is available without Premium, the app generates a random identifier for that installation and sends it with free feedback. The server stores a SHA-256 hash derived from that identifier with the message and the last submission time to enforce a configurable limit on free submissions per installation in 24 hours. It is not a hardware identifier or Google account. Clearing app data or reinstalling may reset it, although device backup may restore it.