Bit2Me · Privacy & Data

Bit2Me privacy & data

Read from Bit2Me's own page on 2026-11-09. 21 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.

Role

The page states nothing on this.

Data categories

category: identifying
Name, surname, ID, contact address, home address, email, contact phone
Read from Bit2Me's own page on 2026-11-09
category: financial
bank and payment method data (account/card number, holder)
Read from Bit2Me's own page on 2026-11-09
category: biometric
including image and biometric data
Read from Bit2Me's own page on 2026-11-09
category: device
Navigation and technical data: User metadata produced during your navigation (browser, operating system, IP, among others)
Read from Bit2Me's own page on 2026-11-09
category: behavioral
Behavioral analysis for improving user experience and resolving technical issues.
Read from Bit2Me's own page on 2026-11-09

Purposes

purpose: Service provision
Management of registration, execution, and monitoring of services contracted by the user
Read from Bit2Me's own page on 2026-11-09
purpose: Identity verification
Formal customer identification (KYC), due diligence, and continuous monitoring for compliance with respective regulations.
Read from Bit2Me's own page on 2026-11-09
purpose: Promotional or newsletters
Registration for sending information, news, and promotions
Read from Bit2Me's own page on 2026-11-09

Retention

scope: Active processingperiod: 48 hours
The moment you request the deletion of your data, it stops being used for commercial, operational (service-specific), or marketing purposes within a maximum period of 48 hours.
Read from Bit2Me's own page on 2026-11-09
scope: Identity Verification (KYC), AML and Monitoringperiod: 10 years (Legal Hold)
Identity Verification (KYC), AML and Monitoring 10 years (Legal Hold)
Read from Bit2Me's own page on 2026-11-09
scope: Whistleblower Channel / Reporting Channelperiod: 3 months (Deletion)
Whistleblower Channel / Reporting Channel 3 months (Deletion)
Read from Bit2Me's own page on 2026-11-09
scope: CV and Selection Processesperiod: 1 year (Deletion)
CV and Selection Processes 1 year (Deletion)
Read from Bit2Me's own page on 2026-11-09

Residency

region: EEA
The processing of your data is primarily carried out within the European Economic Area (EEA).
Read from Bit2Me's own page on 2026-11-09

International transfers

mechanism: adequacy
Safe countries (Adequacy Decisions): We send data to countries that the European Commission has officially recognized as safe
Read from Bit2Me's own page on 2026-11-09
mechanism: SCC
we sign specific contracts approved by the European Commission (called Standard Contractual Clauses)
Read from Bit2Me's own page on 2026-11-09

Subprocessors

Other providers: We use external services for the operation of our App and Website
Read from Bit2Me's own page on 2026-11-09

Data processing agreement

Deletion

Data subject rights

right: Access
Right to Access Right to obtain confirmation as to whether or not we are processing your personal data and, if so, to obtain a copy of the data
Read from Bit2Me's own page on 2026-11-09
right: Rectification
Right to Rectification Right to obtain the correction of personal data that is inaccurate or to have incomplete data completed.
Read from Bit2Me's own page on 2026-11-09
right: Erasure
Right to Erasure (right to be forgotten) Right to obtain the erasure of your personal data in accordance with applicable regulations.
Read from Bit2Me's own page on 2026-11-09
right: Portability
Right to Data Portability Right to receive the personal data you have provided to us in a structured, commonly used, and machine-readable format
Read from Bit2Me's own page on 2026-11-09
right: Object
Right to object at any time to our processing of your personal data based on Bit2me's legitimate interest.
Read from Bit2Me's own page on 2026-11-09

Sale or sharing

The page states nothing on this.

Document

Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page