Privacy Policy
Last updated: 3 November 2026
Aakriti is an Android live-wallpaper app operated by KALAEEM TECHNOLOGIES LLP, India. Contact for support and privacy: contact@kalaeem.com.
1. Wallpaper features and data on your phone
Browsing, favourites, preview and wallpaper application do not require Google sign-in or optional analytics. Favourites and settings are stored locally; we do not currently sync them across devices. Downloaded wallpaper layers, thumbnails, cache metadata and temporary previews are stored on your phone. Clearing cache removes downloaded extras; clearing Android app storage or uninstalling removes local app data, subject to Android backup/restore behavior. An applied wallpaper may need to be replaced separately in Android settings.
Motion sensors drive the parallax effect locally. We do not send raw motion-sensor readings, touch recordings, screenshots or screen replays to analytics. Wallpaper screens use Android content-protection controls. Those controls do not make the home-screen wallpaper itself uncapturable.
2. Network delivery and Cloudflare
The app requests its catalog and wallpaper assets from assets.aakriti.app, using Cloudflare CDN/R2. Cloudflare necessarily processes network information such as IP addresses, request times and security metadata to deliver and protect the service. This essential asset delivery still occurs when optional analytics is off.
3. Optional analytics and approximate city
In builds with privacy controls, optional telemetry starts off until you choose Allow. The choice covers usage analytics, diagnostics and IP-estimated city. You may choose Not now and use the core app normally. Change your choice under Profile → Privacy & Analytics at any time. Advertising consent remains denied; we do not use these events for advertising.
When allowed, Google Analytics for Firebase receives events such as named app screens, wallpaper IDs/categories viewed, preview/picker outcomes, favourite changes, asset-loading results, setting changes and sign-in/sign-out status. Custom analytics events do not include your name, email or Firebase account UID. Analytics uses its own app-instance identifiers and device/app information, so these records are pseudonymous, not anonymous.
For audience measurement, the app also requests geo.aakriti.app while foregrounded. Cloudflare estimates city, region and country from the connection IP. Our Worker returns only those coarse fields and schema/source metadata; it does not return your IP or coordinates, or add them to application logs. Cloudflare infrastructure may retain operational/security metadata under its service terms. Google receives the coarse geography under the Analytics installation identity.
This is not GPS, precise location, residence, nationality or Play Store download location. VPNs, carrier routing and missing IP data can make it inaccurate or unknown. We store the first successful city in the current local data set and refresh the current estimate at most daily on foreground, with failure backoff. Revocation, clearing data or reinstalling can reset this first-city record. We do not currently use city for personalized recommendations.
4. Optional diagnostics
With permission, Firebase Crashlytics processes crash/ANR reports, stack traces, app state, device/app metadata and installation identifiers to help us diagnose failures. After a new opt-in, crash uploads begin on the next app restart, following cleanup of earlier unconsented reports. Loading durations are measured locally and sent as generation-checked Analytics events only when the operation remained opted-in; Firebase Performance Monitoring collection remains disabled.
5. Optional Google sign-in
If you choose Google sign-in, Google/Firebase Authentication processes the credentials needed to authenticate you and may process your name, email, profile photo, provider/account identifiers and connection/security metadata. The app displays and locally caches profile information and maintains an authenticated session. Google credentials/passwords are not sent in custom analytics. Signing out ends the app session; it does not delete the Aakriti account or Google account.
6. Turning telemetry off
Revocation immediately closes the app’s custom-analytics gate, disables optional SDK collection, cancels city work and removes local city/queued-observation data. It resets local Analytics data and requests removal of unsent crash reports. Historical records already sent to providers are not deleted by this local reset. Data already transmitted or in transit cannot be recalled instantly. A new opt-in starts a new local analytics/city data set.
7. Retention and deletion
Local data remains until cleared, evicted, reset or uninstalled. Firebase account records remain until the account is deleted, subject to provider security, backup and legal-retention processes. Optional event/user-level Analytics retention follows the property’s configured retention period; aggregated statistics may be retained longer. We provide the current configured period on request and review retention before public release. Crashlytics retains diagnostic data under its published service retention practices. Cloudflare may retain operational/security records under its terms.
You can request account/data deletion at contact@kalaeem.com, including if you have uninstalled the app. See account and data deletion instructions. Account deletion and installation-linked analytics deletion are separate: your email alone does not locate Analytics records. Where available, the in-app email request includes the current Analytics app-instance ID for you to review and send. Previously reset identifiers may be unavailable. We will explain what we can identify, what is deleted and any necessary retention; we do not promise instant remote erasure.
8. Providers, security and international processing
We use Google/Firebase for authentication and permitted telemetry, and Cloudflare for hosting, asset delivery and optional city estimation. These providers and their subprocessors may process data outside India. App service connections use HTTPS. We restrict operational access and do not sell personal data. A service provider’s processing is still off-device collection; absence of GPS permission does not make it anonymous.
9. This website, contact and changes
This website uses no analytics scripts, advertising, third-party fonts or data-collection forms. Cloudflare still processes request/security information to serve it. Emailing us sends your message and contact details through the email providers involved; we use them to respond, verify requests and document their handling, retaining them as needed for that purpose and applicable obligations.
The app is not designed specifically for children. If you believe a child’s personal data has been provided, contact us. We update this policy when practices change and date revisions here; material new optional uses will require appropriate disclosure and choice.