Privacy
Data used
The service processes account and authentication details, including your Telegram identifier if you use that login method, business information and uploads, a wallet device identifier, language, bookings and messages when those features are used. Public business information is visible to visitors; do not publish secrets or other people’s personal information.
Purposes and legal bases
Data is used to provide the service and perform the contract, for security and handling notices under legitimate interests, and to fulfil applicable legal duties. Where consent is required, it is requested separately. Accepting the rules is not consent to all processing or marketing.
Notices and logs
The form stores the URL, description, language, time and name/email only if supplied. Responses are available via private links; the list of links is stored locally on your device. Clearing device data may remove this list, so keep important links separately. Abuse prevention stores an IP hash using a server key, not the raw IP. The server and hosting provider may keep separate logs. Authorised administrators can access requests; do not include unnecessary sensitive data.
Retention and recipients
Data is stored by the hosting provider used by the operator. Telegram participates in authentication if you choose it. The operator must specify actual providers, international transfers and retention for other features. In this module, closed notices and moderation logs older than 365 days are deleted when an administrator runs cleanup, unless the operator separately retains them on a lawful basis for a dispute or legal duty. Open notices are kept until resolved.
Rights and local storage
Use “Support” to request access, correction, deletion, restriction, objection and portability where applicable; consent may be withdrawn. You may complain to Latvia’s Datu valsts inspekcija. The app uses session cookies and local storage for language and the wallet. Clearing device data may remove access to an unsynchronised wallet.
Blocking data
To prevent abuse, the service processes a Telegram, device or dashboard identifier or a notice sender’s network hash, the reason and date of a decision, and the administrator identifier. A notice author is linked to a verified session where available; for guests only a network hash is used, not a name or email as proof of identity. Active restrictions remain until lifted. Manual cleanup deletes logs and lifted restrictions older than 365 days, as well as author records for deleted notices.