1. Scope
This document describes information handling on the UviPay website, in KYC/KYB applications and in related interactions with the UviPay Telegram bot. Operator and privacy contact details will be completed before this policy takes effect.
2. Information you provide
Individual applications may include name, date of birth, nationality, address, contact details, identity documents and a selfie. Business applications may include company registration, representatives, owners, directors and supporting documents. Depending on verification needs, you may also provide source of funds, intended use, wallet or bank details and a linked Telegram account. The system also processes IP addresses to limit requests and stores application-related information, submission times, processing status and administrative audit events. Depending on enabled features, an application may include a signature, contact verification records, live photos and head-turn frames. The system may read ID photo information and generate face, movement, list or wallet comparison results to assist human reviewers.
3. Processing purposes
Information is used to link accounts, review applications, request clarification and support service requests. Answers about business activity, source of funds and beneficial ownership help the team assess an application. Information use must remain limited to disclosed purposes and applicable obligations.
4. Telegram and third parties
Telegram is an independent platform with its own policies. When interacting with a bot, some account information and the content you send are shared with its operator. Specific hosting, processing and payment providers, processing locations and sharing conditions must be confirmed and added before this policy takes effect.
Telegram Privacy Policy ↗5. Protection and retention
The current verification system encrypts application data and uploaded files at rest. Do not send passwords, private keys or wallet recovery phrases through forms or the bot. Retention periods, deletion schedules, access recipients and incident handling procedures have not been specified in this draft.
6. Website preferences
The website remembers language using a cookie and light/dark appearance using browser storage. Form answers are saved in the tab session to restore progress after a reload. You can clear this local data in your browser settings; doing so may remove unsubmitted progress.
7. Data requests
You may request information about your data, ask for correction or deletion and raise questions about processing. Fulfilment depends on requester verification and applicable retention obligations. The contact point, request process and response timelines will be published with the completed policy.
8. Business deck requests
To view the business deck, you provide an email and consent to storing the request to manage document access. Email is encrypted at rest; only administrators with data export permission can view the list. A signed access cookie contains no email and expires after 24 hours. This does not subscribe you to marketing or verify inbox ownership. Records older than 90 days after the latest request are deleted on the next lead save or list access. Backup copies follow the system’s separate backup retention schedule.