Dafonts · Android and iOS
Effective date: November 9, 2026
Dafonts helps people browse, preview, download, and use fonts. This policy explains what information the app and its service providers handle, why they handle it, and the choices available to you and your family.
It covers DaFont / Dafonts on Google Play (dafonts.dafonts.dafont) and DaFonts on the App Store (com.dafonts.dafonts), published by Gorantala Niharika. Privacy contact: gorantalaniharika8@gmail.com.
Dafonts is intended for a mixed audience, including children. The native Android and iOS implementations use different privacy controls.
The native Android update described here does not ask for or collect an age choice, and does not save new age choices. On startup, it attempts to remove the former local age-choice preference from older installations; if removal fails, any remaining value is ignored and deletion is retried on a later startup. The same conservative settings apply to everyone: contextual ad requests use Google's child treatment and G-rated content setting, while Google's consent eligibility still controls whether ads can be requested. Interstitial ads can appear at natural preview or download breaks, and app-open ads can appear on eligible launches or returns to the app under the safeguards described below. Rewarded ads for extra downloads are disabled; eligible users may explicitly choose an ad to unlock install tools for a selected font, as described below.
In native Android 2.0.4 (build 25), sanitized Sentry reporting for unhandled Java/Kotlin crashes and app-not-responding events (ANRs) is enabled for reliability. Firebase Crashlytics/Performance, product analytics, Session Replay, cross-promotions, font-request submissions, and purchases remain disabled. The Android crash-reporting scope and controls are described below.
The native iOS update described here does not ask for, collect, classify, or infer your age. It has no age-selection screen or age-based feature modes. Age choices saved by earlier versions are ignored, and the app attempts to delete the retired local age-choice file on startup. If cleanup cannot complete, it is retried on a later startup; any remaining value does not control advertising, diagnostics, purchases, or other features.
Version coverage. These descriptions apply to the native implementations described in this policy. Publishing this policy does not update apps already installed. The absence of an age-selection screen alone does not identify an older implementation; see Earlier app versions.
On native iOS, the same child-appropriate advertising settings apply to everyone: contextual ad requests use Google's child-directed treatment and G-rated content setting. There is no tracking-permission prompt. Inline ads, interstitials at natural preview or download breaks, app-open ads during eligible loading screens or returns, and explicitly chosen rewarded ads for extra downloads may be offered after the relevant consent, entitlement, and presentation checks. Purchases, restore, font requests, and cross-promotions are available without an age classification. Usage analytics is enabled automatically in production builds, as described below.
Browsing, previews, favorites, and ordinary downloads remain available. The ordinary daily download allowance still applies. Essential catalog, file-delivery, and advertising services may receive an IP address and technical request information to operate, secure, and deliver those services. Contextual advertising does not mean no information is processed.
Parents or guardians can contact us to ask about information associated with their child's use, request access or deletion where we can identify the information, or raise a concern about inappropriate collection. Do not include a child's full date of birth or other unnecessary sensitive information in a request.
You do not need a Dafonts account. Search terms and selected categories are sent to Google's Firebase Cloud Firestore to find matching fonts. Previews, images, and font files are retrieved from catalog file providers, including Google/Firebase storage and DaFont download servers. Those services receive the requested content, IP address, and technical connection information; Firestore also processes client and device metadata needed to provide its service. Update checks contact Google Play on Android or Apple's lookup service with the app identifier and storefront country on iOS.
Downloaded files, favorites, preview settings, language, onboarding choices, daily download counts, and any earned download credits are stored on your device. Native iOS does not collect or retain age choices for use by the app; it ignores any legacy value pending deletion. The native Android update does not save new age choices and ignores any legacy value pending deletion. The app also keeps limited local diagnostic and ad counters. Text you enter to preview a font is used to render the preview; we do not intentionally send that text to product analytics.
When you choose to share a file or image, install a font, or save to another location, your device passes it to the destination you choose. Exported files and operating-system backups can remain after you remove Dafonts. We do not receive your personal font files merely because you keep them on your device.
Dafonts uses Google AdMob. Depending on platform configuration, privacy choices, region, and platform permission, Google Mobile Ads may process IP-derived general location, device or app identifiers permitted by the platform-specific settings below, ad views and clicks, app interactions, and SDK diagnostic/performance information for advertising, measurement, analytics, security, and fraud prevention. Google and eligible advertising partners process information under their own policies.
On native Android, all users receive the contextual-ad treatment described above. Google's User Messaging Platform checks consent eligibility before ad requests; where required, its consent form is shown. Inline ads and interstitials at natural preview or download breaks can be requested when eligible. App-open ads may appear on eligible launches or returns to the app after consent and entitlement checks permit ads and the app's onboarding requirements are met. Premium status, pending entitlement checks, active dialogs or other modal screens, and device-safety restrictions can prevent presentation. Rewarded ads for extra downloads, and prompts to watch those ads, remain disabled.
Android has a separate, opt-in install reward: when offered, you may choose “Watch ad to unlock install tools” for a selected font. A rewarded ad is shown only after that choice and subject to consent eligibility, entitlement, foreground, and full-screen availability checks. The advertising SDK must confirm the stated viewing action to earn access; simply closing or clicking an ad does not earn it. Earned access is saved on your device for that font and manufacturer route when local storage succeeds; if saving fails, access is available for that visit only. This reward does not add download credits or guarantee that your phone can apply the font. Browsing, previews, and ordinary downloads do not require this install reward.
Native iOS applies Google's child-directed treatment and a G-rated ad content setting uniformly, without collecting or deciding any user's age. This configuration disables interest-based and remarketing ads and prevents the advertising identifier (IDFA) from being sent in Google AdMob requests. The app does not show Apple's tracking-permission prompt or use IDFA for tracking. Google's User Messaging Platform also receives a uniform under-age-of-consent setting and still updates consent information before ad requests; its eligibility result controls whether ads can be requested. Contextual ads can still involve IP addresses, app interactions, and other technical information described above.
Native iOS does not change ad treatment or available features using a collected, inferred, or saved age choice. The uniform child-appropriate ad configuration applies to every installation. Premium status, consent eligibility, pending entitlement checks, foreground state, and presentation safeguards still control whether an ad can load or appear. When offered, you may explicitly choose to watch a rewarded ad for the stated in-app download credits. The reward depends on completing the advertised viewing action, never on clicking an ad.
Native Android 2.0.4 (build 25) automatically sends sanitized reports of unhandled Java/Kotlin crashes and app-not-responding events (ANRs) to Sentry to diagnose failures and improve reliability. This crash reporting is enabled for all users, is not optional product analytics, and has no in-app opt-out. “Help improve Dafonts” is not offered on Android.
Reports can include the error type, sanitized stack traces, app version, and operating-system, device-model, and runtime context. Before sending a report, the app removes user details and user/device identifiers, request details, exception messages, custom tags and extra fields, interaction breadcrumbs, and attachments. It removes absolute stack paths, local variables, and surrounding source context, while retaining the method names and line numbers needed to diagnose failures. The app does not attach your font files, search or preview text, screenshots, or screen view hierarchies to these reports.
Handled errors and ordinary log messages are not sent through this crash-reporting path. Sentry Session Replay, performance tracing and profiling, automatic session tracking, behavioral logs and breadcrumbs, and native (NDK) crash reporting and memory dumps are disabled. Firebase Crashlytics/Performance and Google Analytics for Firebase remain disabled on Android.
Sending a report still makes a network connection: Sentry may receive an IP address and technical connection information to receive and secure reports. Removing identifiers from the report payload is not a promise that the service receives no network metadata. These crash-reporting restrictions do not disable the technical information processed by essential catalog, file-delivery, or advertising services described elsewhere in this policy.
On native iOS, Sentry and Firebase Crashlytics/Performance provide reliability diagnostics without an age-based eligibility gate. They may process crash reports, error information, stack traces, app and operating-system versions, device/runtime details, installation or session identifiers, and performance measurements so we can diagnose failures and improve reliability. These reports are separate from product usage analytics. We limit application-supplied metadata and do not intentionally attach your name or email address to diagnostic reports. App-reported handled failures use allow-listed diagnostic fields; raw request details, user context, and arbitrary extra fields are removed from those handled-error reports. Limited, allow-listed ad lifecycle information can accompany them.
Session Replay is disabled in both native implementations described here. They do not use Sentry to reconstruct recordings of your app sessions.
Google Analytics for Firebase is enabled automatically in native iOS production builds to measure app use and improve Dafonts. Selected events include app activity, previews, downloads, purchase outcomes, and ad/reward interactions, together with associated technical and app-instance information. Firebase Remote Config supplies app configuration and experiments. There is no “Share usage analytics” switch or “Help improve Dafonts” screen in this update, and the retired local analytics preference no longer controls collection. Development and sample-ad builds are excluded from this usage measurement. We do not intentionally send font names, search text, or preview text as product-analytics event parameters. Analytics advertising storage, advertising user data, and ad personalization remain disabled, and Firebase vendor-identifier (IDFV) collection is disabled. Usage analytics does not change your ad privacy choices. You can contact us about access or deletion as described below.
On native iOS, Apple processes payments and RevenueCat checks subscription or purchase status and restores entitlements. RevenueCat also checks existing access at startup so a paid user is not treated as a free user for advertising. Automatic device-identifier collection by RevenueCat is disabled in this native iOS update. RevenueCat may receive an anonymous app-user identifier, transaction/purchase history, receipt information, app/device information, and entitlement status. We do not receive your payment-card number. Android does not currently offer these in-app purchases.
Font-request submissions and cross-promotions are disabled in the native Android implementation described here. If you submit a font request on native iOS, Firebase stores the requested font name, optional note, app locale, platform, and submission time. Please do not put personal or sensitive information in the request. The app does not attach a Dafonts account, name, or email to it.
If you contact us by email, we receive your email address, message, and anything you choose to attach, and use them to respond. External websites, stores, email services, and sharing destinations apply their own privacy practices.
Ad privacy: open the app menu, then Privacy & legal → Ad privacy settings when this entry is available. Google's form lets you review the choices applicable to your location, including consent withdrawal or relevant opt-outs.
Product analytics: native iOS production builds collect the usage analytics described above automatically, without an in-app toggle. This is separate from ad consent and reliability diagnostics. Contact us for access or deletion requests. Product analytics is disabled for everyone in the native Android implementation described here.
Tracking: this native iOS update does not request tracking permission or use IDFA for ads. Your device's privacy settings may still show permissions granted to earlier versions. Android advertising-ID controls can be reviewed in your device's privacy settings.
Local information: remove downloaded files and favorites using the app or your device. Clearing app data or removing the app removes its local storage, subject to device backups and files exported elsewhere. A new installation may restore backed-up settings.
Questions or correction: contact us if you need help identifying or using the privacy controls your installed version provides.
The privacy policy bundled in the app can be read offline. The online policy (https://sites.google.com/view/fonts-privacy-policy9/home) contains the latest published text. The bundled policy contains no advertising or embedded analytics scripts. Google Sites hosts the online policy and may process connection information and cookies under Google’s privacy policy.
Local settings and app files remain until you change or remove them, clear app data, or uninstall, subject to backup and export behavior. Server-side font requests, support correspondence, diagnostics, analytics, and purchase records are retained while needed for their stated purposes, provider retention settings, security, and applicable legal obligations. Advertising providers retain their records under their own policies. We do not claim that uninstalling the app deletes records already held by a service provider.
To request access, correction, or deletion of information we can identify, email gorantalaniharika8@gmail.com. Tell us the platform and the relevant request, transaction, or approximate event time. We may need limited additional information to locate a record and verify that the request is yours or that you are the child's parent or guardian. We will address requests for records under our control, including deletion unless retention is needed for a legitimate security or legal obligation, and explain when a provider must handle a request directly. Without a named user account, some aggregate or pseudonymous records cannot be linked back to you.
We use encrypted connections and access controls for supported services. Providers may process information outside your country, including in the United States. No storage or transmission system is completely secure.
Some earlier app versions, released before the platform-specific controls described here, may initialize AdMob, diagnostics, and purchase services without those controls. Depending on the version, Sentry Session Replay may reconstruct sampled screen layouts and interactions for troubleshooting, including sessions with errors. Masking varies by version: images and user-input surfaces may be masked while some app labels remain visible. Technical, interaction, and session information can still be processed. Some earlier native iOS builds offered an optional “Help improve Dafonts” analytics switch. The controls and defaults in an older installed version continue to apply until it is updated.
The native Android and iOS updates described here have no age-selection screen. Android applies conservative settings to everyone. This native iOS update applies one child-appropriate advertising configuration to everyone; it does not collect, classify, or infer age and ignores retired age-choice values while removing them from local storage. Some earlier iOS versions retained saved age choices and applied different feature restrictions. Screen presence or absence alone therefore does not identify an earlier version. Check the installed version and its bundled policy, or contact us for help. Updated controls take effect through an app update; a website policy change alone does not change an older installed app.
Google Privacy Policy (https://policies.google.com/privacy) and how Google uses information from partner apps (https://policies.google.com/technologies/partner-sites)
Firebase privacy and security (https://firebase.google.com/support/privacy)
Sentry Privacy Policy (https://sentry.io/privacy/)
RevenueCat Privacy Policy (https://www.revenuecat.com/privacy/)
Apple Privacy Policy (https://www.apple.com/legal/privacy/)
DaFont Privacy Policy (https://www.dafont.com/privacy.php)
For privacy questions, child-privacy concerns, or information requests, contact gorantalaniharika8@gmail.com. This policy applies to the Dafonts app identities listed above; it does not replace the policies of unrelated apps.
We may revise this policy as the app or its services change. We will publish the revised text with a new effective date and provide additional notice or request consent where required.
Dafonts privacy policy online (https://sites.google.com/view/fonts-privacy-policy9/home) · Updated November 9, 2026