Privacy policy

1. Owner and contact

AgeSquare is owned by Andrey Makarenkov, an individual in the Russian Federation, who handles user requests. For privacy questions, contact mail@agesquare.app.

2. Demo and local application data

The homepage demo uses your entered birth date in browser memory. It does not save it in website storage or on the server. Opening Telegram passes the selected language, not your birth date.

You may provide a date of birth, interface language, preferences, weekly reflections, and intentions. The application processes this data in your browser and stores it in IndexedDB on your device.

In guest mode, your birth date and entries stay on your device. Signing in does not transfer your guest journal. When you separately enable sync, a copy of your birth date, settings, entries, and drafts is sent to the AgeSquare server over HTTPS. The server copy is encrypted with a key stored separately from the database. This is not end-to-end encryption: the server can decrypt the copy for sync.

3. Technical data

To deliver pages, the hosting provider processes network requests. These may include your IP address, request time, URL, response code, and browser and device information. This information supports delivery, error diagnosis, and security.

AgeSquare uses Beget infrastructure. It does not create a separate advertising profile or use third-party web analytics. When access logging is enabled, the hosting provider rotates access logs daily and keeps them for at least four days under its technical rules. The provider publishes its own data processing terms.

4. Email support

If you email AgeSquare, the owner receives your sender address, message, and any information you include. This is used to respond, provide support, maintain security, and protect legal rights.

Correspondence is kept until the request is resolved and afterward only as needed to comply with law or protect rights. Do not include birth dates, journal exports, passwords, or other information unnecessary for resolving your request.

5. Cookies and browser storage

AgeSquare does not set advertising or analytics cookies. Sign-in uses necessary secure HttpOnly session cookies lasting up to 30 days; Telegram sign-in uses a temporary state cookie lasting up to 10 minutes. The app uses IndexedDB and localStorage. Offline use relies on Cache Storage and a Service Worker. The app does not put private entries in the HTTP cache.

6. Retention and local deletion

Local data remains until you delete it in Settings, clear browser data, or remove the application. You can download a JSON backup first.

Deleting all local data cannot be undone and does not delete export files you have created separately.

7. Exports and security

A JSON export may contain your birth date and private entries. You choose where to store it and control access. Do not share exports with third parties or upload them to unverified services.

AgeSquare uses HTTPS and minimizes data transfer. The security of your device, browser, email account, and backups also depends on your actions and the relevant providers.

8. Your requests and controls

You may request information about processing, correction, restriction, or deletion of data held by the owner where there is no other lawful basis for processing. Email mail@agesquare.app with the subject “Personal data”.

Manage local data in Settings or through your browser. Delete your cloud copy and account separately in account settings. Pausing sync stops sending changes but retains an existing server copy until you delete it.

Accounts, Telegram, and reminders

Sign-in uses a verified email address or Telegram identifier. AgeSquare does not receive your Telegram password. Email addresses are encrypted; verification codes are single-use and expire after 10 minutes. Session and rate-limit data protect sign-in.

When a Mini App opens, Telegram supplies signed user data for server verification. Telegram and your regular browser have separate local storage. Data can be transferred through the same account and sync, or through a JSON export.

The independent AgeSquare Telegram bot stores your user and private chat identifiers, the birth date you provide, language, time zone, preferences, and reminder consent settings. Text entered while creating or editing an entry is temporarily stored as a draft. After confirmation, an entry is stored with its date and type. Ordinary messages outside an entry flow are not added to the journal. This data is held in a separate SQLite database on the bot server. File permissions restrict access, but the database is not encrypted at rest; it is not end-to-end encrypted. Telegram also processes messages under its own terms. The web app and bot use separate storage with no automatic synchronization between them.

The /export command sends saved entries and preferences as a JSON file to your private chat. The /stop command disables reminders without deleting your journal. The /delete confirm command deletes your profile, draft, and entries from the bot working database. It does not delete Telegram history, previously sent exports, or existing backups. Bot commands do not automatically delete those copies; contact the address above with questions about their processing.

Allowing web push stores a subscription endpoint and technical delivery keys. Notifications pass through your browser's push provider. You can revoke permission in your browser and disable notifications in AgeSquare. The email provider processes the address and sign-in email; Telegram processes sign-in data and bot messages.

The cloud journal remains until you delete it. Up to five previous server versions are retained for recovery. Sessions expire after 30 days; codes after 10 minutes. Technical notification history is cleared after 45 days. Infrastructure backups expire under the provider's schedule. After restoration, the operator must reapply deletion requests before reopening access.

Signing out does not remove the account's local copy from the device. On shared devices, export first, then delete local data or clear site data. Deleting an account does not delete exports or messages already delivered.

9. Changes

Updated policies are published here with an edition date. This version does not provide for payments, advertising analytics, or sending your journal to external AI services.