TYNVOPrivacy Policy
This summary reflects features in the current application. It is not a claim of end-to-end encryption or a legal compliance certification.
Information processed
- Website accounts store a username, password hash, language and plan fields, reward preference, and account timestamps.
- Private notes store note keys and text associated with the account.
- When the Telegram bot is configured and used, it processes Telegram user identifiers and messages needed for the implemented bot commands and inline calculator. Telegram also processes data under its own policies.
- Basic server and reverse-proxy operational logs may include request metadata; log retention depends on server configuration.
Bot permissions and chat data
The current bot handlers process commands and messages Telegram delivers to it, plus inline queries explicitly sent by users. The code does not crawl chat history. Telegram privacy mode and chat permissions control which group messages the bot receives. If a required channel is configured, the bot checks membership using Telegram's getChatMember operation.
Storage and protection
Passwords are stored as scrypt hashes. The application encrypts selected account fields and private note keys/text in the database using the configured Fernet data key. This is application-layer encryption; the service operator controls the running application and key. It is not end-to-end encryption. HTTPS protects connections when enabled by the deployment's reverse proxy.
Use and sharing
Account information supports login, preferences, and private notes. Note content is not returned in public inline results. The current code does not implement advertising or payment processing. Telegram handles its own bot and inline-query processing.
Retention and controls
There is no automatic retention schedule, self-service account export, or account deletion workflow in the current application. Users can manage preferences in the account dashboard; note listing, saving, searching, and deletion are exposed through account APIs, though the current dashboard does not provide a complete deletion interface. For data requests, contact the operator; no support address is configured on this installation.
Children and changes
The service does not publish an age-specific policy in the current version. This page should be reviewed and updated when data handling, operators, retention, or integrations change.