Who handles your data, the information used by account and financial services, lawful purposes, sharing, retention and your rights.
Version 2.0Updated 15 Jan 202610 sections
In this documentexpand_more
1. Controller and contact
Benzig Jwelsg Digital Solutions N.V., registration number 548658, registered address Zuikertuintjeweg Z/N, Willemstad, Curaçao is the stated operator and controller for the investor platform’s account and service processing. Use Support or [email protected] for privacy enquiries, identify the account or request concerned and do not send passwords, private keys or authentication secrets. A product provider acting independently may have separate responsibilities; we must identify a material independent recipient or applicable notice rather than treating every recipient as our processor.
2. Data categories
We process registration identifiers, email, a password hash, profile details you provide, session and authentication status, security records and relevant activity logs. Financial records include balances, wallet addresses, network and transaction references, orders, share holdings and distributions, loan eligibility inputs, schedules and repayment history, liquidity operations and referrals. Support includes messages and attachments you choose to provide. Verification documents or source-of-funds information may be requested where justified; this notice does not claim that every account has undergone a completed identity check.
3. Purposes and legal grounds
Processing supports requested account access, custody, instructions, accounting, loans, distributions, liquidity, communication and complaint handling. Where applicable, grounds include steps toward or performance of a valid contract, a specified legal obligation, and legitimate interests such as preventing abuse subject to the required balancing and safeguards. Consent is used where required, including applicable optional marketing or tracking. Accepting commercial terms is not blanket consent to every unrelated use of personal data.
4. Sources, browser connections and blockchain data
Data comes from you, your account activity, payment and blockchain records and service infrastructure. The website requests Google Fonts; your browser can therefore connect to Google and transmit connection information such as IP address and request metadata. Email delivery can include open-tracking records in supported campaigns. Browser storage holds session, language, display and referral state described in the Cookie & Storage Policy. Public blockchain records can expose addresses and amounts independently of our private account database.
5. Recipients and access
Access is limited to personnel and providers who need information for the relevant service, support, infrastructure, security, communications or applicable compliance duties. A transfer to a blockchain recipient or network exposes necessary transaction data. Competent authorities may receive information under a valid legal requirement; professional advisers may receive information where necessary for a dispute or obligation. We do not describe public disclosure of private account balances as an ordinary platform feature. Do not assume that an external provider’s processing is anonymous.
6. International processing
The stated operator is based in Curaçao and infrastructure or providers can involve other countries. Where a transfer is subject to a law requiring an adequacy decision, contractual safeguards or another lawful mechanism, the applicable mechanism and required information must be addressed. This notice does not assert universal EU-only hosting, a particular transfer certification or signed safeguards that have not been identified. Ask Support about a relevant processing location and applicable protection.
7. Retention and closure
Account, transaction, verification, security and complaint records are retained according to the operational purpose, outstanding obligations, applicable statutory duties, limitation periods and necessary dispute or security investigation. Retention must be justified by category and not become indefinite merely because data is convenient. Signing out removes current access but does not erase financial records or public blockchain history. Closure and deletion requests require review of lawful retention and remaining claims; data no longer needed should be deleted or appropriately de-identified.
8. Security and minimisation
We must use appropriate access, authentication, operational and organisational safeguards proportionate to the processing. Password hashing, available two-factor authentication and private account access are safeguards, not guarantees that incidents are impossible. Share only information reasonably needed for your request, and use the authorised support route. We should not request your private blockchain key, full authentication secret or password to process a complaint or data-rights request.
9. Rights, consent and requests
Depending on applicable law, you may have rights to information, access, correction, erasure, restriction, portability, objection and withdrawal of consent, as well as a complaint to a competent data-protection authority. Rights can have lawful exceptions and must not be made dependent on waiving an unrelated financial claim. Contact Support with the right requested and sufficient identity information; we may proportionately verify authority. Applicable statutory response periods govern; where GDPR applies, its response and extension rules apply rather than an invented universal deadline.
10. Calculations, children and updates
The platform calculates valuations, borrowing capacity and an internal repayment-related score from service records. A displayed score is not described as a report from an external credit bureau. Where a solely automated decision with legally significant effects triggers explanation, contest or human-review rights under applicable law, those rights must be addressed. Services are not intended for minors. Material purpose or policy changes require appropriate notice and, where needed, a fresh lawful basis or consent; a new publication date is not blanket authorisation for unrelated processing.
