Privacy Policy

Practice data should remain under the person's control

This policy describes what data is processed by the Attention OS site and the `you_stalker` app in the current version of the project. The document will be updated before any features related to accounts, synchronization, cloud storage, or remote analytics are launched.

Short version

  • The site is informational and does not require registration.
  • In the current version, the app stores user records locally on the device.
  • The project does not require sending practice records to an external server.
  • The project does not use remote analysis of user records.
  • If cloud features appear, this policy will be updated before launch.

Who operates the project

Attention OS is an author's project that develops through practice, the app, and public materials on the site. A contact address for privacy questions will be added after the domain is chosen and the site is published.

What data the site processes

The site itself does not require an account, does not ask you to enter personal data, and does not contain forms for sending practice records.

During ordinary visits, technical data may be processed by the hosting provider: IP address, browser type, requested pages, request time, and similar server logs. This data is usually needed for site delivery, security, error diagnostics, and protection from abuse.

At the current stage, the site does not use advertising trackers, retargeting pixels, or behavioral analytics. If analytics are added, this must be clearly reflected in the privacy policy.

What data the app processes

The `you_stalker` app is intended for recording practice episodes: attention captures, chosen focuses, delayed purchases, attention tails, and related notes.

According to the current project specification, these records are stored locally on the user's device. The app does not require external APIs, sending records to a server, or remote analysis of practice content.

User records may contain sensitive personal observations. For this reason, the project follows a principle of minimization: not to collect or transmit such data without a separate, clearly described reason and without updating this policy.

What the project does not do in the current version

  • It does not create user accounts.
  • It does not synchronize records between devices.
  • It does not store practice records in the cloud.
  • It does not sell user data.
  • It does not use practice records for advertising profiles.
  • It does not transfer practice records to third parties for analysis.

Third-party services

After publication, the site will be hosted by a selected hosting provider and may use a domain registrar, DNS provider, security certificates, and abuse-protection services. These providers may process technical data needed for the site to work.

If the app is distributed through app stores, those stores may process data under their own rules: for example information about downloads, updates, device, payments, or reviews.

Voluntary contact

If a user writes to the author of the project, sends feedback, reports a bug, or asks a question, the project may process the data the user voluntarily provided: name, email address, message text, and technical details needed to respond.

Security

The project aims to limit data collection and not move personal practice records into external infrastructure without necessity. However, no method of storage or transmission can be absolutely secure.

The user should remember that local records are protected only as well as the device itself: phone access, backups, screen lock settings, and system permissions matter.

Children and teenagers

The project is not designed specifically for children and does not seek to knowingly collect data from minors. If future features require registration, payment, cloud storage, or communication, age limits and data-processing rules must be clarified separately.

Changes to this policy

This privacy policy may be updated as the site, app, and infrastructure develop. It is especially important to update it before launching accounts, synchronization, cloud backups, remote analytics, payments, newsletters, or advertising tools.

Last updated

Last updated: June 3, 2026.