Privacy, in plain words.

Drizzl Privacy Policy · Updated 22 October 2026

Drizzl is provided by Pranav Garg. This policy explains how the app and the services it uses process information. For a privacy question or request, email pranavgarg@gmail.com.

Information and purposes

App activity and reliability

Firebase Analytics receives app events such as feature use, materials and tools selected, optional idea progress, purchases, ad interactions and notification opens. Reports can include app version, platform, language, device characteristics and coarse performance measurements. We use these reports to understand feature use and improve the app.

Our Google Analytics account also enables Google data sharing for improving Google products and services; modeling and business insights using aggregated, de-identified measurement data; technical support access when needed; and recommendations, insights and offers about using Analytics. These purposes are described in Google's Analytics data-sharing documentation. They are separate from the advertising choices managed by AdMob.

Firebase Crashlytics receives crash and failure information, such as stack traces, failure categories, device and app context, and limited app state around a problem. Firebase installation and transport services support delivery of these reports.

Drizzl creates or reuses a random installation identifier and provides it to Analytics and Crashlytics. On iOS, an update can retain the identifier from the previous Drizzl app. It is pseudonymous: it is not your name, but it allows activity from an installation to be linked over time. Service providers may also use their own identifiers.

The events written by Drizzl do not contain your canvas pixels, selected photo, purchase receipt, purchase token, signature, raw store transaction identifier or raw store error message. An app preference, progress count or purchase state may be included in app reports. This is different from information collected independently by a store or advertising service.

Advertising and consent

Drizzl uses Google Mobile Ads (AdMob) and Google's User Messaging Platform. These services may process device or advertising identifiers, ad requests and interactions, product interaction, IP address or coarse location, consent choices, performance information and diagnostics. This supports advertising, measurement, fraud prevention and consent management. Drizzl does not request precise GPS location for gameplay.

On iOS, the App Tracking Transparency permission controls access to tracking identifiers and tracking across other companies' apps and websites. On Android, Google Play services provides an advertising ID, which you can reset or delete in your device settings. Google requests advertising consent where its consent service requires it. Drizzl starts ad requests only after that service permits them. Declining tracking does not remove ads.

Some advertising disclosures or uses may fall within local definitions of sale, sharing or targeted advertising. The Google privacy options available in the app and your device permissions let you review applicable choices. Advertising choices do not automatically disable separate app analytics or crash reporting.

Purchases

The App Store or Google Play handles your store account, payment method and payment transaction. Drizzl receives verified product and ownership information to unlock features and restore purchases. App reports can include the product, purchase outcome, price and currency where available, and a one-way digest used to avoid duplicate purchase reporting. Drizzl does not receive your card details.

Notifications and support

Reminders are optional and scheduled locally. The app stores permission and scheduling state. Opening a reminder may send an Analytics event containing its type and time since scheduling.

If you email support, we receive your email address, message and any attachments you choose to send. We use them to answer your request and investigate the issue. Please do not include passwords, payment details or private artwork unless you choose to share it for support.

Artwork, photos and device storage

Your canvas, Rewind and recovery data, settings and selected Photo to Sand image are handled locally in normal use. Saving a snapshot, sharing an image or exporting a canvas sends the selected content to the operating-system feature or destination app you choose. Those destinations control their copies.

Eligible app data may be included in device backups or transfers according to your operating system and settings. Drizzl does not provide its own cloud canvas account or sync service. A device backup is separate from importing a previous canvas format: Drizzl 1.1 starts fresh and does not import canvases from the earlier native app.

Your choices

• Change notification and tracking permission in device Settings. On Android, reset or delete the advertising ID in device settings.
• Use Manage privacy choices in Drizzl Settings when Google's consent service makes that control available.
• Choose which photos, snapshots or files to import, save or share.
• Delete saved images or exported files from their destination, and manage backups through your device or backup provider.
• Contact us to make a privacy request.

Clearing the canvas is a play action, not a request to delete all app information. Rewind and recovery copies can remain. Uninstalling stops future collection by the app and normally removes its local container, but does not necessarily delete information already held by providers or in backups and exports.

How long information stays

Local canvas and settings remain until replaced, removed with app data, or changed by the operating system or a restore. Exported images, files and backups follow their destination's storage rules.

The Drizzl Google Analytics property is configured for 14-month event and user data retention, with user retention reset by new activity. Aggregated reports can follow different retention rules. Google's Analytics retention documentation explains these limits.

Firebase states that Crashlytics retains crash traces, associated installation identifiers and related information for 90 days before beginning removal from live and backup systems. Other Firebase services have separate retention and deletion rules; see Firebase privacy and security.

Advertising, consent and store records follow the relevant providers' retention rules and service settings. Support correspondence may be retained while responding to your request and handling follow-up, security or legal needs. Contact us to ask about a particular record or request deletion.

Service providers and disclosure

The following services process information under their applicable terms and privacy policies:

• Firebase Analytics, Crashlytics and related Firebase services
• Google AdMob and advertising privacy
• How Google uses information from apps that use its services
• Apple privacy policy
• Google privacy policy, including Google Play

We may disclose information where reasonably necessary to comply with law, respond to lawful requests, prevent fraud or protect rights and safety. Providers can process information outside your country under their applicable privacy and transfer arrangements. No method of transmission or storage is completely secure.

People under 13

Drizzl is intended for ages 13 and over and is not directed to children under 13. We do not knowingly solicit personal information from children under 13. If you are a parent or guardian and believe a child has provided information, contact us so we can investigate and take appropriate action with the relevant providers. The store's content rating describes app content and may differ from this intended audience.

Privacy requests

Depending on where you live, you may have rights to access, correct, delete or receive information; object to or restrict processing; withdraw consent; or opt out of certain advertising uses. You may also have a right to complain to your local data protection authority. Withdrawing consent does not change the lawfulness of processing before withdrawal.

Email pranavgarg@gmail.com with your request. We may need proportionate information to verify it and locate relevant records. Because Drizzl has no required user account, we may not be able to associate a pseudonymous installation record with you without further information. We will explain applicable limits rather than promise that uninstalling deletes provider records.

Changes and contact

We will update this page when the app's practices change and provide any additional notice required by applicable law. A policy update does not replace consent where consent is required.

Drizzl is provided by Pranav Garg. Privacy and support contact: pranavgarg@gmail.com.