Privacy Policy

In brief

This notice describes processing identified in the BELOOK website and mobile application. Push notifications, optional technical diagnostics, usage statistics, promotions and release announcements have separate choices in Profile → Privacy & rights. They remain off without recorded explicit consent. Refusing them does not block financial operations.

Information required before final publication: the controller’s legal identity, address, establishment and operating countries, official privacy contact and any appointed DPO. This notice is not a compliance certification.

1. Controller and contact

The organisation determining purposes and means must be identified. Its legal particulars and official privacy contact remain to be confirmed; no DPO identity or specialist address is presented as verified.

To record a request, use the app privacy center or the form above with your support account. The support channel does not replace publication of the controller’s contact details.

2. Scope and data

The public site and application process account identifiers, profile details, contact information, preferences and security data. Financial services process accounts, amounts, beneficiaries and transaction references. Support processes the messages and tickets you submit. Business, point-of-sale, identity and partner services may require additional information and contracts.

Optional mobile diagnostics contain minimized technical events and selected fields, such as platform, error status and duration. They do not upload forms, payment request bodies, card numbers or message content. Never include sensitive material in a support ticket or rights request.

4. Identity information and permissions

4.1 Identity and verification data (KYC)

Verification may require identity documents, declarations, face capture or a presence check. The lawful basis, providers and conditions for biometric processing require validation for each relevant country. Device camera permission alone is not consent to biometric processing.

Camera, contacts and microphone permissions are requested for the functions that need them. You can manage them in device settings. Refusal may prevent that function and must not automatically activate another optional use.

5. Purposes and lawful bases

Providing the requested account and services requires an appropriate lawful basis, including contract performance where applicable. Financial checks and mandatory retention require identification of the legal obligations actually applicable; no universal retention period is claimed here. Security and fraud prevention also require documented justification.

The privacy center requests separate explicit choices for push, diagnostics, usage statistics, promotions and Android release emails. Release email consent is not marketing consent. OS permission does not replace this choice. Notice version and immutable choice history record grants and withdrawals.

6. Recipients and international transfers

Depending on the feature, necessary data is handled by BELOOK services, Supabase for storage and authentication, financial and identity partners, communication providers and support. If you enable push, OneSignal receives a pseudonymous account identifier and a device subscription; the mobile integration does not add your email address and disables OneSignal location sharing.

Support may use automated assistance for messages you submit. Do not send secrets, card data or identity documents. The complete recipient inventory and processor agreements require validation.

Actual hosting and access countries and transfer safeguards must be verified for each provider. This notice does not assume an adequacy decision, signed standard contractual clauses or a particular safeguard’s effectiveness.

8. Retention

Retention must follow documented purposes and applicable obligations, with an approved category-specific schedule. Legal periods for KYC, the ledger, disputes and backups remain to be confirmed for each jurisdiction. An erasure request does not authorise destruction of accounting entries or evidence subject to retention.

Browser support identifiers are limited to the current tab’s session. Display preferences and the public site cache may remain until removed. The mobile export’s temporary cache file is deleted after sharing; copies you choose to keep or share are then your and the recipient’s responsibility.

9. Choices and rights

You can record access, portability, rectification, erasure, restriction or objection requests linked to your account, with a tracking number. Receipt is not completion. Proportionate identity verification and review of exceptions may be necessary.

The initial response deadline is one calendar month. Any extension and its reasons must be communicated as required by applicable law; requesting more information does not automatically restart the clock.

The immediate export is partial: profile, preferences and recent operations, capped at 100 rows per collection. KYC documents, full history and partner records require a full access request.

Recording an erasure, restriction or objection request withdraws all four optional uses on the server. Local withdrawal may precede network confirmation, which the app identifies as pending. Withdrawal does not automatically erase records already held by a provider.

10. Security and automated decisions

Access controls, minimization, encryption and logging require assessment for the relevant processing. This notice does not claim an invulnerable system or formal certification.

Payment orchestration and risk checks may use automated rules. Legal classification, effects on individuals and challenge or human review procedures require dedicated assessment. Contact support to request review of a restriction.

11. Browser storage, complaints and updates

The Cookie and local storage policy describes browser storage and removal. The examined code contains no public advertising or audience measurement tool. Introducing one requires updated information and prior choice where required.

You may contact the competent data protection authority, including the CNIL where applicable. The notice version appears above. Final legal particulars and deployed practices must remain consistent with this notice.