Private by default. Optional by choice.
This policy is written for the Friction Atlas mobile/desktop app and its public website. It is intended to match the current local-first product design and can be used as the basis for future app-store disclosure.
1. Summary
Friction Atlas is designed as an offline-first habit and focus application. The core product does not require a Friction Atlas account or a custom Friction Atlas backend. Habit logs, friction reasons, experiments, settings and supported digital-friction summaries are stored locally on the user’s device unless the user deliberately exports a backup or a platform store processes a purchase.
2. Data stored locally by the app
Depending on which features you use, the app may store the following on your device:
- habit names, schedules and daily Done/Blocked outcomes;
- friction reasons, energy scores, notes and countermeasures;
- experiment history and intervention outcomes;
- app settings, selected companion and local entitlement cache;
- optional daily Digital Friction summaries such as foreground time, estimated app opens and observed short-form counts;
- correlation evidence created from those local summaries and habit outcomes.
No custom Friction Atlas server is required for this core data.
3. Optional Android permissions
| Permission / access | Purpose | Required? |
|---|---|---|
| Usage Access | Summarize per-app foreground time, estimated opens/sessions and top apps for Digital Friction. | No |
| Accessibility Service | Estimate short-form feed views in supported apps using a narrow observe-only event flow. | No |
| Display over other apps | Show the draggable Friction Bot over other Android apps. | No |
| Notifications | Local reminders and companion/foreground-service visibility where required. | No for core logging |
| Biometric/device auth | Optional local app lock. | No |
Accessibility Service disclosure
If Enhanced short-form tracking is enabled, the Accessibility Service is used to observe limited events and supported surface markers so Friction Atlas can estimate Reels/Shorts-style views. The service is not intended to perform clicks, gestures, navigation, automation or blocking. Friction Atlas does not intentionally persist messages, passwords, screenshots, images, typed content, raw accessibility trees or screen text from this feature.
Short-form counts are estimates because third-party interfaces can change and a scroll event is not equivalent to official platform analytics.
4. Purchases and app stores
Google Play, Microsoft Store or another distribution platform may process purchases for Pro Lifetime or separate robot products. Payment information is handled by the platform, not by a Friction Atlas custom payment server. The app may keep a local entitlement cache after a successful purchase or restore.
Store providers process data under their own privacy policies. Because the current product does not use a Friction Atlas account backend, cross-platform entitlement transfer is not promised.
5. Website
This static website does not intentionally set advertising cookies or embed third-party analytics in the supplied build. If hosted through GitHub Pages or another hosting provider, that provider may process standard network/request information such as IP address, user agent and request logs under its own terms.
External store or developer links take you to third-party services with their own privacy practices.
6. Retention, backup and deletion
Local data remains on the device until the user deletes it, clears app storage, uninstalls the app, or imports/replaces data through supported backup features. “Delete Everything” is designed to remove local app data, including saved Digital Friction evidence.
Exported backup files are controlled by the user and can remain wherever the user saves or shares them. Store purchase records are controlled by the relevant store and are not erased by deleting local habit data.
7. Security
Friction Atlas uses local storage and platform security capabilities appropriate to the app, including secure storage for selected sensitive local settings/entitlement cache and optional device/biometric authentication where available. No system can guarantee absolute security; users should protect device access and exported backup files.
8. Children
Friction Atlas is a general productivity/habit application and is not specifically directed to children. If the product is later offered to children in a regulated jurisdiction, the developer should update this policy and store disclosures before that distribution.
9. Changes to this policy
This policy may be updated when the app changes, new platform features are added, or legal/store requirements change. The effective date at the top of this page will be updated with material revisions.
10. Contact
For privacy or support inquiries, use the contact route published on baisalya.com. Before a public Play Store release, add the exact support/privacy contact email required by the store to this page and the listing.