Proposed update: 30 September 2026. Publisher: Nityatna, Padubidri, Nadsal, Udupi, Karnataka 574111, India. Contact: deiaitycollab@gmail.com.
deiAIty is an India-focused devotional wallpaper app intended for people aged 13 and older. It offers public wallpaper browsing, optional sign-in and synchronized Collections, notifications, and Auto Wallpaper. We do not ask for date of birth or identity documents merely to confirm age.
Firebase Authentication processes account email, display name, provider and user ID when you sign in. Guest use can create a pseudonymous Firebase identity to reach protected services. Account Collections store your selected wallpaper release IDs with your account ID in Firebase Realtime Database; local copies and pending edits are stored on your device. Public images and catalog metadata are downloaded and cached. The app sends network requests and App Check/Play Integrity signals to operate the service and reduce abuse. We do not upload your personal photos.
Usage analytics and crash/performance diagnostics are enabled by default when the app starts. After onboarding, the app shows a notice explaining both settings. Firebase Analytics receives coarse feature and screen events, app-interaction counts and a pseudonymous app-instance identifier. We exclude wallpaper release IDs, deity and category keys, names, search text, account IDs and email from the event contract. Our Analytics data can be exported to BigQuery for aggregate operational analysis. Crashlytics and Firebase Performance Monitoring can process crash stacks, performance traces, device/runtime information, network metadata and installation/session identifiers. You can turn either setting off in the notice or later in Profile > Diagnostics; Profile also has a Usage Analytics switch. A choice you previously turned off stays off after this update. Turning a setting off stops future collection; prior records follow the service's configured retention and deletion process.
A trusted service records one wallpaper view per pseudonymous Firebase user per release per UTC day, subject to abuse limits. It keeps short-lived per-user receipts and aggregates public view totals. Signed-in favorites can contribute to aggregate popularity. Your private Collections are not public. Notifications are generated from public release metadata and your device settings; permission is optional.
Google Firebase and Google Cloud process service data for authentication, database, storage, analytics, diagnostics and app integrity. Information travels over HTTPS; local refresh credentials use Android Keystore-backed encryption. We do not export advertising identifiers to BigQuery or sell personal data.
Account details and private Collections remain while your account is active and are removed from the active service through verified account deletion. The planned view-receipt and quota records expire after approximately two days; completed deletion markers after 90 days. These application-level periods must be confirmed after the matching backend is deployed. Aggregate popularity and daily product counts without account identifiers may remain for long-term reporting.
In the linked Google Analytics property, event-level data is set to two months and user-level data to 14 months; new user activity resets the user-data period. These settings do not govern BigQuery exports or standard aggregate Analytics reports. Raw Analytics, Crashlytics, Performance Monitoring and Firebase sessions exports in BigQuery are configured for 90-day retention. The daily product aggregate is retained without a set expiration. Newly created export tables will be checked after the next export.
Firebase's own service periods differ from the BigQuery copies: Crashlytics retains relevant crash data for 90 days before removal begins; Performance Monitoring retains IP-associated events for 30 days and installation-associated or de-identified data for 60 days before removal begins. Firebase Authentication may take up to 180 days after account-deletion initiation to remove associated information from its live and backup systems. Our Cloud Logging default bucket retains operational logs for 30 days; its locked required audit bucket retains required audit logs for 400 days. The project's Realtime Database and Firestore databases have no scheduled backups enabled. Deleted Cloud Storage objects can remain recoverable for seven days through Soft Delete; live catalog files have no automatic age-based expiration.
Proposed support-mail practice: we acknowledge requests within three business days, handle verified account-deletion requests within 30 calendar days, and manually remove support and deletion-request correspondence within 12 months after the case closes, unless a specific legal or security reason requires longer. Gmail may keep a message in Trash for up to 30 more days after we delete it. This practice is proposed and must be adopted before this notice is published.
You may turn off usage analytics and diagnostics, turn off notifications, remove favorites, clear the app's image cache, or request account deletion from Profile. The planned in-app deletion flow stops account writes, removes cloud Collections and the Firebase Authentication account, and removes account-bound local Collections and rotation queues. Applied wallpapers and files you exported to your device are under your control. Some aggregate data, required audit logs, service records and provider backup copies follow the periods above. To request deletion without the app, use the account deletion instructions. Contact us about access, correction or deletion questions at deiaitycollab@gmail.com.
We will update this dated notice when data practices change and provide additional notice where required.