Privacy Policy

1. Scope

This policy explains the processing of data relating to visitors to tokeniser.ru, account and API users, and people contacting support. Processing includes collection, recording, storage, use, transmission to perform a request, correction, restriction, deletion and other necessary operations.

Publication of this policy provides information; it does not constitute user consent to advertising or every possible transfer of data. Where separate consent is legally required, it must be given separately from accepting the Terms of Service.

2. Account, security and support

Account sign-in and servicing involve the email address, account identifier, sign-in confirmations, session information, preferences and records of accepted documents. Security involves technical information about requests, time, device, browser and network address to the extent necessary for protection and investigation of errors.

Support correspondence includes the message, voluntarily attached materials, reply details and resolution history. Do not supply unnecessary information, passwords, active keys or bank codes.

Purposes include account creation and servicing, authentication, responding to user requests, access protection, support and evidence of actions. Grounds include performance of the agreement or steps requested before it, legal obligations and protection of rights where permitted by law.

3. API and transactions

API use involves the selected model, request parameters and content, resulting output and technical execution metadata. Request data is transmitted to external model providers to the extent needed to provide the selected service. Do not submit material you are not entitled to transmit.

The service records the model, time, status, transaction identifier, usage quantity and charge. Request and response content is not intended for permanent storage in Tokeniser usage history and is not included in customer financial reports. Material separately sent to support is processed as support correspondence. External providers may have different retention conditions.

Payments and refunds involve the amount, currency, method, status and transaction identifiers. Full card details and bank codes are entered with the payment provider, not sent to Tokeniser support. Purposes include supplying services, settlement, refunds, accounting and dispute resolution.

4. Cookies and analytics

Essential cookies and local storage support sessions, security, language, theme and saved preferences. Blocking them in the browser may prevent sign-in or retention of settings.

Yandex Metrica, including Webvisor on public pages, is used to analyse website use. Analytics may process browser identifiers, device and connection information, visited pages and interactions, and information about main service-use stages and confirmed transactions, without request content or access secrets. Webvisor can replay interaction with a public page; recording of customer-account content is disabled.

In the current interface, analytics starts by default unless a refusal has previously been saved. It can be disabled under “Cookie settings” or “Analytics and cookies” by selecting “Without analytics”, and the choice can later be changed. Refusal does not disable core service features. Clearing local storage or using another browser may require a new choice. Signed-in users’ preferences are also saved to their account.

Refusal stops further browser analytics transmission; if offline, the account change is saved when connectivity returns. It does not undo prior processing or necessary payment, security and service records. Contact support about deletion of previously collected data.

Default technical activation does not replace separate consent where applicable law requires it. Yandex processing terms: https://yandex.ru/legal/confidential/. Metrica technology documentation: https://yandex.ru/support/metrica/en/.

5. Messages and user choice

Service emails about sign-in, security, payments and support replies are necessary for requested actions and account servicing. They are separate from advertising.

Advertising messages require separate prior consent where the law requires it. Registration, payment or an analytics choice does not itself give that consent. Marketing preferences may be changed in account settings or withdrawn through support. Refusal of advertising does not stop service notifications.

6. Recipients and external processing

Infrastructure and backup, email-delivery, payment, analytics and AI-model providers support the service. Data needed for the relevant function is shared subject to access restrictions and contractual processing conditions. A third-party payment interface is also governed by its own privacy policy.

An external model provider or other contractor may process data outside the user’s country. Localisation, international-transfer, notification and consent requirements apply independently of this policy. Regulated information may be transferred only with the necessary legal basis and confirmed conditions. This policy is not unrestricted permission to transfer any information to any country.

Information about relevant processing and recipients can be requested at support@tokeniser.ru. Disclosure to authorities is made in response to a valid legal requirement; selling user requests is not a purpose of supplying the service.

7. Retention and termination of processing

Account information is retained during account servicing; after closure, only information with a continuing legal basis is retained. Sign-in codes and sessions have limited validity; expired or revoked information does not grant access.

Accounting and payment records, evidence of accepted terms and claim-related information are retained for periods needed for mandatory accounting, legal compliance and protection of rights. Support correspondence is retained until resolution and for the necessary period for related claims. A specific lawful preservation requirement may extend retention of affected records.

Once a purpose and legal basis end, data is deleted or anonymised within applicable periods. Backups have a separate renewal cycle and restricted access; restoration must not override accepted processing restrictions. Yandex stores Webvisor recordings for 15 days, including the current day; other analytics retention depends on its purpose and the provider’s rules.

8. Security and rights

Measures include secure connections, access control, protection of credentials, action logs and backups. Access is granted on a need-to-know basis. Absolute security is not promised; incidents are investigated with necessary mitigation and legally required notification.

Users may obtain information about processing, request correction, restriction or deletion where legally available, withdraw consent, request export of their own data and request account closure. Withdrawal does not end processing supported by an independent continuing legal basis.

Submit requests through the account or support@tokeniser.ru. Minimal identity-verification information may be required to protect the account. Requests are handled within applicable statutory periods; any restriction on fulfilling a request is explained. Users may contact the relevant data-protection authority or court.

9. Revisions

Revisions are published with a date and version. Material changes to processing purposes or conditions receive the necessary notice, and any required new consent is requested separately. Questions may be sent to support@tokeniser.ru.