CryptoFundsterPrivacy / Identity verification

Identity Verification Privacy Notice

Notice date: 30 September 2026
Version: CF-KYC-2026-09-30-EN-90D

90 days active evidence retentionSilent short camera checkHuman final review

1. Who is responsible

Bettaprop LLC operates CryptoFundster and is the controller for this identity-verification workflow. Address: 8206 Louisiana Blvd Ne, Ste A #4863, Albuquerque, New Mexico 87113, USA. For privacy requests, corrections or assistance, contact contact@fundedbankroll.com. Do not email identity documents or camera recordings; ask for the secure verification route.

This notice concerns identity evidence, local prechecks and the resulting review. It does not replace the product terms or describe all account, payment or website processing. Participation requires age 18 or older and the legal capacity required where you live.

2. Information processed

You provide your full legal name, date of birth, document issuing country and document type, and photographs of your passport, identity card or residence permit. A back image is requested where applicable. Images can contain a portrait, document number, nationality, expiry date, signature, address and other information printed on the document; original uploads may also contain file metadata.

The short camera check records a silent selfie video, normally approximately 35 seconds and limited to 60 seconds. It requests movements such as turning your head and blinking. The standard browser capture does not request microphone access. Sampled frames, a preview, a frame contact sheet, capture instructions and their timing support review.

We also process extracted document text and machine-readable or barcode fields, image-quality results, document-field comparisons, file hashes used to detect exact reuse, face-comparison results, verification case references, consent time and notice version, review notes, decisions, assistance requests and access/audit events.

3. Local checks and human review

The self-hosted worker reads document text, checks supported machine-readable checksums, compares supplied fields and document sides, and examines image quality and sampled camera movements. These checks can be incomplete or wrong; readable text and matching checksums do not prove a document is authentic.

The workflow includes local facial analysis and document-to-selfie face comparison. MediaPipe locates facial features; AuraFace computes numerical face representations to compare the document portrait with a camera frame. The worker uses these representations in processing memory, not as a stored searchable face-template database. A similarity score and review observations can be retained with the dossier. These are biometric processing, not a guarantee of identity or liveness.

Where a sufficiently recent local OFAC sanctions snapshot is available, name screening produces possible matches for a reviewer. Missing or stale data is marked unavailable. This is not comprehensive worldwide sanctions, politically exposed person or adverse-media screening. An apparent match is not a finding of wrongdoing.

An authorised human reviewer assesses the evidence and unresolved issues; final approval requires an independent super-admin. Local prechecks cannot approve identity. A face score is not a probability of identity, and the camera check is not certified proof against spoofing or deepfakes. There is no generative AI verification or automated guarantee of approval. You can ask for correction or human reconsideration.

4. Purpose, choice and legal basis

We use the evidence to establish that the trader is the person named on the document, assess eligibility, prevent identity misuse and fraud, and administer verification-dependent services such as payouts. We do not use this workflow to train models, advertise to you or sell your identity or biometric data.

Document and camera processing requires your agreement before preparation begins. Automatic facial analysis has a separate optional checkbox, unchecked by default. You may leave that checkbox unchecked and continue with assisted human review; we will not run facial landmarks or automated face comparison without that separate consent. Camera permission alone is not consent to facial analysis. If you do not agree to document and camera processing, do not upload evidence and contact us to discuss assistance. An alternative still needs sufficient identity evidence and is not a promise of approval. We cannot complete verification-dependent payouts without completing the applicable checks.

Where applicable, ordinary identity administration relies on necessity for the requested service; non-biometric fraud prevention and audit retention rely on legitimate interests in protecting accounts and resolving disputes. A legal obligation is relied on only where it actually applies. Facial comparison may require a separate special-category legal condition and explicit consent. A generic terms checkbox or this notice alone is not a substitute for any required specific consent.

Consent may be withdrawn without affecting the lawfulness of earlier processing. Contact us if you wish to withdraw or need assistance. Necessary records may remain on another applicable legal basis; mandatory privacy rights are not waived.

5. Access, hosting and security

Document and video evidence, derived images and sensitive dossier contents are encrypted at rest with AES-256-GCM in our self-hosted verification system on Hetzner infrastructure. Evidence is decrypted for local processing and authorised review. Separate case/status records and audit metadata are not all covered by the dossier-level encryption; encryption is not a claim of anonymity or zero risk.

The customer can access their permitted previews. Original evidence and camera contact sheets require authorised independent reviewer access, which is logged. Restricted operational access may also be needed for security, maintenance and recovery.

This workflow does not transmit customer documents, recordings or face data to OpenAI, ChatGPT, model-download sources or an external identity-verification/face-recognition API. Hosting and backup infrastructure still support storage; self-hosting does not mean no infrastructure provider is involved. Required disclosures to competent authorities remain possible under applicable law.

Bettaprop LLC is a US controller. Hosting, authorised access and a specifically arranged assistance session can involve locations outside your country. Contact us for the applicable recipient/location information and any required transfer safeguards. This notice does not assert a particular transfer agreement, local representative or worldwide legal clearance that has not been established.

6. Retention and deletion

Active-store retention: 90 days from the start of the verification preparation attempt. This covers original document images, camera recordings, previews/contact sheets and the sensitive preparation dossier, including extracted fields and local comparison results. Replacing a file, submitting for review or receiving a decision does not restart the clock.

At expiry, evidence access is blocked and the running service schedules removal of those active files and sensitive preparation contents. The sweep normally runs once per minute; downtime or processing failures can delay physical cleanup. Deletion is not a claim of forensic erasure from storage devices. Temporary video-processing files are normally removed when processing exits; abnormal termination requires operational cleanup.

The separate verification decision/status, case and attempt references, consent/notice records, audit history and any relevant appeal or payment records are not deleted by that raw-evidence sweep. Their retention is assessed separately for maintaining verification and payout records, resolving disputes, security and applicable recordkeeping duties. They do not currently have an automatic age-based deletion period in this workflow. The 90-day rule is not a promise that all account records disappear after 90 days.

Separate identity backups: recovery copies of raw documents, camera recordings, derived images and sensitive preparation dossiers are kept in encrypted identity-only archives for a maximum of seven days from each backup's capture. They can therefore remain for no more than seven additional days after removal from active storage. Expiry is scheduled earlier to allow retries; local working snapshots are temporary and are also cleaned up. Backups are for recovery, not routine verification access. Restoration must respect the original attempt expiry and subsequent withdrawals; it does not restart retention.

New general financial, account and authentication backups exclude the raw evidence vault, sensitive preparation-dossier contents and the vault key. The key needed to recover identity evidence is protected inside the encrypted identity-only backup instead. Separate decision/status, consent and audit records described above may remain in general backups; the identity-backup limit is not a promise to erase all financial or account records. Mandatory deletion rights continue to apply.

Before verification is approved, the preparation-withdrawal action removes active evidence when available. After approval, request withdrawal or erasure through our contact address; the self-service action does not automatically revoke a completed verification or erase associated records. We assess rights requests and any lawful retention exception individually.

7. Your rights and assistance

Subject to the law that applies, you may request access, correction, erasure, restriction, portability, or object to relevant processing, and withdraw consent. You may challenge a verification decision and request human review. Contact us using the address above; we may need proportionate information to establish that the request is yours.

You may complain to your competent privacy regulator, including the authority in your place of habitual residence, work or the alleged infringement where applicable. Rights, lawful exceptions and applicable response deadlines remain in force. Nothing here limits mandatory consumer or privacy protections.

8. Audio and other verification methods

This version covers the short silent camera route. Extended voice/video capture is separately disabled in the release configuration inspected for this notice. It is not authorised by the short-camera agreement. If a longer recorded session is offered later, its purpose, additional information, recipients and retention must be disclosed, with separate agreement before microphone access.

For an assisted meeting, ask about the proposed meeting service and whether recording is involved before participating. No external meeting provider, audio recording or automatic transcription is silently included by this notice.