Velinoya analytics notice
Updated 22 September 2026. First-party product analytics is enabled for testing.
This supplements the Privacy Policy and describes enabled product analytics. Publication of this notice, reading the Policy or using core features does not by itself mean consent to optional analytics.
Purpose
To understand where users stop between entering the bot, viewing a palm result and obtaining compatibility, compare entry sources and measure return visits.
Planned data
Internal account ID; first observed entry-source code and server time; random event ID, an event type from a fixed list, interface language and time; first Mini App opening date. Events describe app opens, result views, invitation preparation and opening the share interface, pair views, forecasts and payment screens when available. Reports also use existing server records of processing jobs, created pairs and payments.
Excluded from events
Photos, palm lines, result content, names, raw initData, invitation tokens, invoice URLs and payment identifiers are not included in analytics events. Opening the share interface does not prove a message was sent. Campaign links can be forwarded, so a code does not verify an advertising source.
Storage and retention
The feature uses Velinoya's own backend at DigitalOcean Singapore (SGP1); no external advertising SDK is added. Raw records are linked to an account and are not anonymous. Administrative reports contain aggregates without account IDs. Events and source attribution are designed for 29-day retention with automatic cleanup. The first Mini App opening date is kept until account deletion, subject to the Policy's review of storage necessity. Backup periods are specified in the Policy.
Deletion and your choices
Account export and deletion cover analytics records. Questions about data, declining optional analytics and consent withdrawal can be sent to privacy@velinoya.com; the request process and applicable exceptions are described in the Policy. Consent to palm analysis is not consent to analytics. The operator and other terms are identified in the Policy.