Skip to content

Privacy and Personal Data Policy

Draft policy under Kazakhstan personal-data law. Operator details and retention periods require approval.

1. Data operator

Operator: [legal operator awaiting approval]. Full legal name, BIN, registered address and data-subject email are pending approval. Phone: +7 707 701 66 23.

This Policy was prepared with reference to Law No. 94-V of the Republic of Kazakhstan dated 21 May 2013, On Personal Data and Their Protection, in the version checked on 8 November 2026. Legal counsel must confirm how each requirement applies.

2. Categories of data

Bankemes processes Merchant account data: phone number, name, business name, optional email, password hash, verification, login and lock statuses.

Cashier and operation data may include profile and organisation identifiers, masked cashier phone, encrypted bank session and device identity, payment identifiers, amounts, statuses, descriptions and metadata.

A Buyer phone number may be processed for a remote invoice. A mask and irreversible digest are retained, while an encrypted value is held temporarily for creation and recovery of the operation. IP addresses, HTTP request details, security events, API/MCP/OAuth connections, approvals, webhook addresses and technical logs are also processed. Bankemes does not request or store Buyer card data.

Where the Merchant keeps a customer directory, Bankemes processes the customer’s name, encrypted phone number, email, Telegram chat ID, preferred channels, tags, external ID, notes, invoice schedules and history, and a notification log. For connected CRM and automation services, encrypted credentials and external event identifiers are stored.

3. Processing purposes

Data is used for registration and authentication, cashier connection, payment creation and reconciliation, webhook delivery, contract performance, support, security, fraud prevention, action logging and compliance with legal obligations.

4. Legal grounds

A legal ground may be the subject’s consent, entering into or performing a contract, compliance with an Operator obligation, or another ground allowed by Kazakhstan law. Consent must be specific and informed where required and does not replace all other grounds.

Using the website does not constitute consent to all processing. The backend does not currently record a consent version, so an audit trail is required before mandatory acceptance is introduced.

5. Buyer data

The Merchant supplies Buyer data to create an invoice or perform its own scenario and is responsible for lawful disclosure and Buyer notice. Depending on purpose and actual decisions, the Merchant may determine processing while Bankemes performs technical operations, or Bankemes may have independent security and logging duties.

The final allocation of data owner, operator and third-party roles under Kazakhstan law requires legal review and contractual documentation.

6. Recipients and disclosures

Where necessary, data may be disclosed to the connected bank, the server infrastructure provider, the Cascade OTP provider, webhook recipients chosen by the Merchant, and, where the Merchant enables these features, Telegram and CRM or automation services connected by the Merchant. Data is disclosed to public authorities only on a lawful basis.

The primary database and backups are hosted on a server in the Republic of Kazakhstan (Hoster.KZ data centre, Astana), in line with Article 12(2) of the Law requiring personal data to be stored in Kazakhstan. Backups are currently kept on the same server; no off-server copies were found.

A cross-border transfer may occur if the Merchant itself configures a webhook, CRM or other service outside Kazakhstan. In that case the Merchant is responsible for the lawfulness of that transfer. Other vendors are not named until confirmed.

7. Retention and deletion

No retention schedule has been approved. Periods must be approved for accounts, bank sessions, payments and audit, OTP and authentication challenges, IP and technical logs, webhook delivery, MCP/OAuth, backups and support requests.

The encrypted Buyer phone used for a remote invoice is deleted by the application after confirmed creation or final resolution. A mask and digest may remain for identification and duplicate protection.

Deletion may be limited by contract performance, dispute resolution, security, backup restoration and mandatory legal retention.

The code already implements some periods: login codes are valid for up to 15 minutes, password-reset grants for up to 30 minutes, sessions expire automatically, the encrypted Buyer phone for a remote invoice is deleted after the operation is resolved and by default within 7 days, payment-link analytics are kept for 180 days, completed customer notifications for 365 days, the integration event log for 180 days, and local backups for 14 days. These values are not an approved policy and are listed for the owner’s decision.

Deleting a customer in the cabinet currently archives the record, and there is no self-service account deletion. Both require separate development before this Policy is approved.

8. Security measures

Implemented measures include tenant isolation, encryption of bank sessions and sensitive credentials, password and API-token hashing, HMAC webhook signatures, rate limits, logging and service isolation. Secrets must not appear in public logs.

Bankemes does not claim ISO or PCI DSS certification, bank accreditation or an independent audit. No measure eliminates all risk.

9. Data-subject rights and requests

A data subject may obtain information on whether their data is held and on the purposes, methods, list and periods of processing; request correction or completion of data where supported by evidence; request blocking where processing conditions were breached; request deletion of data processed unlawfully or in other cases provided by law; and withdraw consent except where the law does not allow it.

There is no self-service account deletion button in the dashboard. A request is made through support by phone or WhatsApp at +7 707 701 66 23, and through the official email once approved. The request states the account phone number, what is requested and, where needed, supporting documents.

Before acting, the Operator verifies the requester’s identity: the request must come from the account phone number and be confirmed with a one-time code or from an active dashboard session. A representative provides a document confirming their authority. Without this verification, data is neither disclosed nor deleted.

A response is given within the periods set by Kazakhstan law, and a refusal is reasoned. If there is information that processing conditions were breached, the data is blocked within one working day. Deletion is refused or partial where data must be kept by law, to perform the contract and complete open operations, to resolve a dispute, to prevent fraud, or in the cases set out in Article 41(4) of the Digital Code. Access to one’s own data is free of charge.

10. Cookies and analytics

The service uses necessary session and CSRF cookies and localStorage for language and theme. No advertising cookies or external marketing analytics were found in the reviewed code. If introduced, this Policy and the consent mechanism must be updated first.

For payment-link statistics, an irreversible hash of the network block, browser family and day is stored together with a device category. This data is not shared with external analytics services.

11. Policy changes

The revision, approval date and effective date will be set only after owner decision and legal review. Material changes will be communicated clearly, and renewed consent obtained where required. This version remains a noindex draft.