Duminov DesignNudge Me

Nudge Me · pre-release

App privacy draft

This is a public-policy structure for development and Play Console preparation. It is not submission-ready until it matches the released code, every SDK, the Data safety form and the final operator details.

Draft for private design review · not approved for launch

1. App and developer

App: Nudge Me, a recurring habit-reminder app developed under the Duminov Design brand in Moldova. The legal developer name, address and privacy contact are pending. Product support is available at support@trynudgeme.app.

2. Current product model

Nudge Me is designed around reminders, schedules, active times and completion or snooze actions. The release data model must be verified in code. Earlier marketing statements about no tracking must not be reused unless the final build, SDK inventory and network testing support them.

3. Data-practice register to complete

AreaStatus before releaseRequired disclosure work
Reminder dataConfirm device-only storage and backup behavior.Purpose, retention, deletion and any OS/cloud access.
AdvertisingAds are planned inside the app, not on the studio website.Name the ad SDK, data collected, recipients and controls.
Analytics / diagnosticsFinal SDK choice and configuration pending.List events, identifiers, crash data, legal basis and retention.
AccountsConfirm whether the release permits account creation.If yes, provide in-app and web account-deletion routes.
ChildrenTarget audience and age treatment pending.Align store declarations, ads configuration and policy.

4. Ads, consent and third parties

If Google Mobile Ads / AdMob is included, the final policy must describe the SDK and link to relevant provider information. For users in the EEA, UK and Switzerland where applicable, in-app consent must be implemented through the app experience, such as Google's User Messaging Platform and Privacy & messaging configuration. The studio website banner does not provide consent for in-app advertising.

See Google's current European regulations message guidance.

5. Security, retention and deletion

The released policy must explain reasonable security measures, concrete or criteria-based retention periods, and how app data can be deleted. Uninstall behavior, backups, advertising identifiers, diagnostic records and provider-side retention should be tested rather than assumed.

6. Rights, requests and complaints

Rights depend on the law and facts that apply. The final notice should explain how to request access, correction, deletion, restriction, portability or objection, how consent may be withdrawn, and how to complain to the competent Moldovan or other applicable authority.

7. Google Play alignment

Google Play requires the privacy policy and Data safety answers to match the app's actual behavior, including third-party SDKs. The final policy URL must be public, active, non-geofenced and HTML, and linked in both the Play listing and the app. See the Google Play User Data policy.

Before publication

Items the operator must confirm

  • Inventory every permission, SDK, endpoint, identifier, event and recipient from the release build.
  • Complete operator identity, public privacy contact, retention and deletion procedures.
  • Configure and test in-app consent for AdMob where required; do not rely on this website banner.
  • Make Play Data safety answers, store copy, consent messages and this policy consistent.
  • Publish the final policy at a stable public HTML URL and link it in the app and Play listing.
  • Arrange Moldova-focused legal review and assess any additional GDPR application.

Need help with the product? Open Nudge Me support.