This Privacy Policy explains how QZAR handles personal data when you use the official Telegram bot, Telegram Mini App, web application (including its installable progressive web app, or PWA, mode), qzar.io, related documentation, accounts, Privy-backed Wallet services, trading tools, public profiles, rankings, tournaments and reward features (the Services). It applies to individuals who use the Services and, where appropriate, people whose public Wallet activity is displayed or analysed through supported research tools.
This Policy is a notice about data processing. Using the Services or accepting the Terms of Use is not by itself consent to optional cookies, marketing, or other processing for which separate consent is required. Where the law requires your consent, we request it separately and explain how to withdraw it.
If you choose Sign in with Google, the Google Sign-In section explains the Google information we receive through Privy, its use, sharing and retention, and how to revoke access or request deletion.
1. Who controls your data
In this Policy, QZAR, we, us and our refer to the provider of the Services operating under the QZAR name. We are responsible as a data controller for personal-data processing whose purposes and means we determine. Where two or more parties jointly determine the purposes and means of processing, we will explain their respective responsibilities as required by applicable law. Contact [email protected] about this Policy, your privacy rights or the contact details of a data-protection officer or local representative, where applicable.
Other parties, including Telegram, blockchain participants, Wallet providers or third-party protocols, may be independent controllers for activities they determine. Some vendors process data for us under contract. Being described as a third party does not remove obligations we have for processing we control.
2. Scope and data minimisation
We process information necessary to provide requested account, Wallet, trading, analysis and reward features, to secure the Services and to comply with applicable law. Features differ by platform, country and account configuration. References to a conditional feature below do not mean every user or interface currently uses that feature. Accessing an interface does not, by itself, mean that we request identity documents. A particular feature, eligibility review or applicable legal requirement may require additional identity information or make a service unavailable. Any such request must be limited to information reasonably needed for its stated purpose and supported by an applicable lawful basis.
We seek not to collect more information than is reasonably needed. Do not send passwords, private keys or recovery phrases to a support agent. When the official Wallet import function requests recovery material, see Section 5 for its particular risks.
3. Categories of personal data
Depending on your actual use, we may process:
Account, profile and authentication data. Internal account and Privy user identifiers; Telegram user/chat identifier, username, display name, language and relevant bot or Mini App information; email address and Google or Telegram sign-in attributes when you choose those methods; linked identity references; account status, referral code and permissions; public username and nickname (including initially assigned values), biography, avatar and banner. We also process session and refresh-token records, authentication and linking events, encrypted authenticator setup secrets where two-factor authentication is enabled, and security audit records such as login, key-export and withdrawal events with available IP address and browser information. Some identity and token references are stored as hashes or encrypted values; this does not make them anonymous.
Wallet and credential data. Public Wallet addresses, Privy wallet identifiers, account-to-Wallet associations, labels and groups, default Wallet selection, PIN or other security settings, and information needed to request transaction signatures. Privy provides the Wallet key infrastructure. QZAR receives recovery material submitted through its supported import flow and private keys returned through an authorised export flow; see Section 5. A public Wallet address or Privy wallet identifier may be personal data when linked to an identifiable individual.
Trading and transaction data. Selected tokens, amounts and routes; balances; current and historical orders; price triggers, expiry, slippage and fee settings; portfolio and cost-basis estimates; transaction signatures/hashes; execution results and failure records; copied or monitored public Wallet addresses; and other data needed to display or execute the user-requested function.
Rewards, referrals and competition data. Referral codes and attribution/deep-link parameters, inviter/invitee associations, eligible completed trading volume, points, cashback tiers, earned and pending rewards, claim Wallets, payout records, tournament entries, eligibility inputs (such as registration date, referrer or qualifying Wallet balance), qualifying trades, scores, ranks, estimated prizes, investigation flags and related support correspondence.
Preferences and notifications. Watchlists, selected or monitored public Wallets, saved trading presets, notification preferences, browser push-subscription endpoints and encryption keys where you enable notifications. Push messages can identify a token, trade direction or order fill and link to the relevant application page; device notification settings determine whether others can see them.
Device, usage and connection data. IP address, approximate region inferred from a connection, timestamps, browser and operating-system information, app version, page and feature events, crash or diagnostic events, error logs, device/session identifiers and security events, to the extent generated or collected in the applicable interface. We do not claim to collect precise geolocation, phone contacts, camera content, biometrics or device advertising identifiers unless such a feature is separately implemented and disclosed.
Communications and legal data. Support messages, reports, disputes, security investigations, communications preferences, and information required to respond to lawfully binding requests, verify eligibility, prevent fraud or address legal claims.
4. Where the information comes from
Data comes from (i) what you submit or configure; (ii) actions in the Telegram bot, Mini App or web application, including its installed mode; (iii) Telegram or a sign-in provider when you choose that authentication method; (iv) devices, browsers and our infrastructure; (v) public blockchains, DEXs and associated market-data infrastructure; and (vi) support or compliance sources where justified and lawful.
We may observe publicly available trading activity of Wallets belonging to people who have never opened a QZAR Account, because a user requests research, monitoring or copy-trading information. We process that information in accordance with applicable law and the purpose explained in Section 6. Blockchain accessibility does not automatically mean such data is anonymous or excluded from privacy law.
5. Telegram, Mini App, web app, PWA and Wallet credentials
Telegram bot. When you interact with our official bot, it can receive messages and information you send to it, plus identifiers and other information Telegram makes available to the bot. Bots are services operated by developers through Telegram's Bot API. Messages with a bot are not equivalent to Telegram Secret Chats or guaranteed to be end-to-end encrypted between you and QZAR. The import of recovery material through a bot may expose it to the platforms and systems involved in delivering and processing that message. Follow only the verified import flow and consider using a newly created, dedicated Wallet for trading.
Telegram Mini App. If you open QZAR inside Telegram, the Mini App may receive launch, identity and session information supplied by Telegram, including signed launch data used to verify the user. We use the information required to authenticate and provide the requested Services. Telegram separately controls its application and certain platform data under its own terms and privacy notice. We do not obtain general access to your Telegram conversations, phone contacts or phone number merely because you use our Mini App.
Web application and authentication. QZAR uses Privy to verify email-code, Google and Telegram sign-in proofs where offered, then establishes its own application session. Telegram Mini App launch verification can establish a session separately from a Privy browser login. Linking an additional sign-in method associates its verified identity with the existing QZAR Account; unlinking a method is not account deletion. Privy authentication and Privy Wallet signing are separate functions: signing out does not cancel server-side orders. The website and terminal use cookies or similar storage as described in Section 10. A sign-in provider does not give QZAR general access to your email inbox or conversations.
Installed web application. Installing the web application in PWA mode provides another way to use the same service. Application files, sign-in information and preferences may remain on your device after you close it. Removing a home-screen icon or uninstalling the application does not necessarily clear browser data, close your QZAR account, delete Wallet credentials held through Privy or cancel active orders. Clear relevant browser/site data and use the account/order controls separately. Installation does not enable offline trading; automated orders may continue under your standing instructions as described in the Terms of Use.
Privy-backed Wallets and signing. QZAR creates and imports Solana Wallets through Privy. Its Wallet records contain public addresses and Privy wallet identifiers. QZAR's server authorisation is configured to request signatures and private-key exports through Privy. Wallet signing can therefore take place without your device being online, and an authorised key-export flow can make a private key available to QZAR's systems. Import and export flows can bring plaintext recovery or key material through the QZAR systems and interface involved, even though ordinary transaction signing uses Privy. We use these capabilities for your permitted Wallet functions and Automated Instructions, security and applicable legal requirements. Exporting a key does not delete the Privy wallet or revoke QZAR's signing capability. See the Terms of Use, Sections 5 and 19, for authority, cancellation and exit.
Google Sign-In
Access and information received. Google Sign-In is an optional way to create, access or link a QZAR Account. When you choose it, Google authenticates you and Privy provides QZAR with your Google Account identifier, email address, name where supplied, and confirmation of the verified sign-in. We associate that identity with your QZAR Account and the relevant Privy user record. QZAR does not receive your Google password. The current Google Sign-In feature uses basic identity and profile information; it does not access your Gmail messages, Google Drive files, contacts, calendars or Google Photos. If we introduce a feature requiring other Google data, we will explain its purpose and request the necessary additional permission before accessing that data.
How we use Google information. We use this information to verify that you control the selected Google Account, create or identify your QZAR Account, link a sign-in method you request, maintain account access, populate account name and contact information, verify supported sensitive account actions, prevent account misuse and resolve account-related support requests. Google authorisation is for sign-in; authority to create Wallets or execute trades comes from your separate QZAR instructions under the Terms of Use. Signing in with Google does not authorise us to publish your Google email address or Google Account identifier. Public QZAR profile and trading information is described separately in Section 9.
Sharing and access. Google and Privy process information needed to complete the sign-in and account-linking flow. Privy also maintains the associated authentication record for QZAR. Necessary account information may be processed by our hosting, security and support providers for those functions, subject to access restrictions and appropriate safeguards. We may disclose information where required by applicable law or necessary to investigate abuse or protect account security. Access by personnel is limited to what is necessary for these purposes. We do not sell Google user data or transfer it to data brokers, use it for advertising or credit decisions, or use it to train general-purpose AI models. The general recipient and analytics descriptions elsewhere in this Policy do not authorise unrelated use or sharing of Google sign-in information.
Storage and retention. We keep the identity reference and necessary name, email and account-linking information in our account and authentication records; Privy holds the associated provider record. Some matching identifiers are stored as hashes, which does not make the linked account anonymous. We apply the safeguards described in Section 13. We retain Google sign-in information while needed for the account and sign-in functions you use. After unlinking or account closure, we delete or anonymise information no longer needed, subject to specific legal retention duties, proportionate security needs or unresolved claims as described in Section 12. Unlinking a sign-in method does not itself erase contact information still needed for an account you continue to use. You may request access, a copy or deletion of your Google-related account information at [email protected]; we verify the request proportionately and explain any justified retention.
Revoking Google access and deleting data. You can review or remove the QZAR connection through your Google Account connections. You can also unlink Google using an available QZAR account control or contact [email protected] for assistance. Keep another verified sign-in method before removing the method you rely on. Removing a Google connection does not automatically delete data already held by QZAR or Privy, close your QZAR Account, end existing QZAR sessions or cancel trading instructions. To request deletion of Google-related account data, write to [email protected]; we address records held by QZAR and relevant provider-side records through the applicable deletion process. Account closure, session controls and cancellation of trading instructions are separate actions described in Section 15 and the Terms of Use. Google also explains how to manage connections and what removal does.
Google user-data commitments. We use and transfer information received from Google APIs in accordance with the Google API Services User Data Policy, including its Limited Use requirements where applicable. These Google-specific restrictions take precedence over any more general permission in this Policy, including provisions about analytics or a transfer of the Services. Where Google's rules require prior consent for a transfer, including to a successor, we will obtain it. We will notify you and obtain the required consent before using Google user data for a new purpose not previously disclosed.
6. Purposes and lawful bases
Where the EU GDPR, UK GDPR or a similar legal-basis framework applies, the relevant purposes and bases are:
| Purpose | Typical personal data | Lawful basis, where applicable |
|---|---|---|
| Create an account, validate login and provide connected bot/Mini App/web/PWA sessions | Account, authentication and session information | Performance of the contract where necessary; legitimate interests in account security for additional protective processing |
| Create/import Wallets and carry out your authorised trades, orders and automation | Public addresses, necessary signing credentials, order parameters and transaction records | Performance of the contract to provide the specific Wallet or execution function |
| Display balances, research, public Wallet histories and portfolio analytics | Public-chain records, selected monitored addresses, activity and settings | Performance of the contract for your requested functions; legitimate interests in supplying relevant public-chain analytics for records concerning others, after a balancing assessment |
| Calculate and deliver referrals, cashback, points and payment corrections | Account/referral associations, trading-fee and reward records | Performance of disclosed program terms, and legitimate interests in fraud prevention and correct accounting |
| Provide public profiles, portfolios, search, leaderboards and requested tournament participation | Profile fields, account-to-Wallet associations, balances, positions, trade histories, points, eligible volume, ranks and tournament records | Performance of the contract for requested profile and competition functions; legitimate interests for associated public discovery and rankings, subject to balancing and applicable objection rights |
| Save watchlists/presets and send requested trade or order notifications | Preferences, relevant trading events and push subscriptions | Performance of the contract for the requested feature; device permission or separate consent where required |
| Measure product use and diagnose performance | Pseudonymous account/session references, feature and execution events, referral attribution and technical metadata | Legitimate interests where lawfully available following a balancing assessment; consent for non-essential device access or other processing requiring it |
| Detect abuse, secure sessions and systems, prevent account takeovers, investigate scams and defend claims | Logs, risk signals, relevant transaction and communication records | Legitimate interests in security, integrity and protection of users and legal claims, balanced against individual rights; legal obligation where a binding requirement applies |
| Satisfy a binding legal, tax, sanctions or regulatory requirement applicable to us | Necessary account, transaction and compliance records | Compliance with legal obligations; another lawful basis where expressly permitted and appropriate |
| Respond to support requests and issue essential notices | Support and contact information, account status | Performance of the contract and/or legitimate interests in resolving issues and providing operational notices |
| Send optional marketing or use non-essential tracking | Contact identifiers, preferences or cookies when implemented | Consent where required, with an effective way to withdraw it |
We do not use consent as the default basis merely because a user accepted our Terms. If the law does not require a GDPR-style basis, we still handle information according to the local rules applicable to QZAR and the individual. We will notify you of materially new processing purposes and obtain consent if required.
7. Automated processing and user controls
QZAR's trading automation compares user-selected order conditions with market or on-chain information and may initiate authorised transactions without real-time interaction. Its financial outcome results from your prior instructions and market execution; it is not a promise of personal financial advice or a guarantee of execution. You can use supported controls to modify or cancel future instructions, subject to transactions already submitted.
Reward calculations and security controls may use automated rules to determine balances, flag suspicious patterns or temporarily restrict actions. You may contact us to seek a review of errors or adverse reward and access decisions. If we use solely automated processing to make a decision about a person that produces legal or similarly significant effects and Article 22 GDPR or equivalent law applies, we will provide the additional information, lawful conditions and meaningful human-review or other safeguards that law requires.
8. Disclosure and recipient categories
We share personal data only where relevant and lawful, including with:
- Operational processors, such as software development and maintenance, hosting, infrastructure, monitoring, security and support providers, where they need access to personal data to perform functions on our behalf and act under appropriate contractual safeguards;
- Privy, for authentication proofs, Wallet provisioning, import/export and signature requests, and Telegram/Google, for the selected platform or sign-in method;
- Analytics and notification infrastructure, including PostHog where configured and the browser/device push service associated with an enabled subscription;
- Other users and the public, for public profile fields and leaderboard information described in Section 9;
- Blockchain and transaction infrastructure, including nodes, RPC services, validators, block engines, DEXs, liquidity pools and smart contracts receiving a transaction or fetching public-chain data;
- Professional advisers, when necessary and subject to appropriate confidentiality; and
- Competent public authorities or counterparties to a legitimate corporate transaction, where disclosure is legally required or otherwise has a valid basis and safeguards.
A blockchain transaction ordinarily publishes addresses, signatures, instructions, amounts and other protocol-required data; it does not require broadcasting your private key. Participants on a public network may process and retain transaction information independently of us. We do not represent that all third parties are our processors or that their practices are controlled by this Policy.
Service providers. QZAR uses Privy, Telegram, Google sign-in, PostHog and browser Web Push for the functions described in this Policy, together with blockchain/RPC, routing and transaction-submission services. See Privy's privacy notice for its own processing. Providers' roles depend on the particular activity; not every provider acts solely on QZAR's instructions. Contact [email protected] for information about the recipients relevant to your use. If another company becomes a joint controller for an operation, we will provide the information required by applicable law.
9. Public blockchain data and data about non-users
Public blockchains are globally replicated and generally append-only. Wallet addresses, transaction hashes, instructions and token movements may be visible, analysed, copied or linked to an individual by QZAR and by independent third parties. Removing data from QZAR's interface cannot delete a transaction that other blockchain participants continue to store. We do not independently control chain finality, consensus records or third-party explorers.
Public profiles, portfolios and rankings. Profile and portfolio pages are accessible without requiring the viewer to sign in. A profile lookup, or a lookup of one associated Wallet address, can reveal the account association and the supported Wallets linked to that account, with balances, positions, trading history, profit-and-loss estimates and other public-portfolio statistics. This linkage is information QZAR supplies in addition to the underlying public-chain records. Profile identifiers and available profile fields can be visible even before you edit them; do not assume visibility requires a separate publication action. The interface also supports account search and leaderboards. Rankings may show username, nickname, avatar, points, rank and, for tournaments, eligible volume, trade counts and estimated prizes; callout rankings can show signal counts and outcomes. Do not place confidential information in public profile fields. Public-chain research, public portfolio/profile fields and private authentication or order-management records are different categories; displaying one does not make all account information public. Profile-edit controls do not guarantee removal of historical rankings or third-party copies. Contact [email protected] about correction, objection or deletion requests.
We remain responsible for personal data held in our own systems, including account-to-address associations, indexes and derived profiles, and for addressing rights requests as applicable. We will not assume a privacy request is impossible merely because some underlying information is public. For non-user public-Wallet information, we assess applicable transparency obligations and any exception, including whether individual notice would be impossible or involve disproportionate effort, without treating that exception as automatic.
10. Cookies, browser storage and notifications
We use cookies and similar browser storage for sign-in, security, requested features and analytics. You can manage stored data through your browser's site-data settings; clearing it may sign you out or reset preferences.
Sign-in and security. QZAR and its sign-in provider, Privy, use cookies and browser storage to authenticate you and maintain access to your account. QZAR sign-in cookies expire after 15 minutes or 7 days according to their purpose; they may be renewed during use, subject to a 30-day maximum session lifetime. Privy's sign-in storage is used during authentication, and remaining local data can be removed through browser settings.
Preferences and temporary information. Browser storage remembers interface and trading preferences, referral information, temporary navigation state and dismissal of informational notices. Temporary information generally lasts for the browser-tab session, subject to browser restoration settings. Preferences and notice-dismissal records may remain until replaced, updated or cleared through browser settings.
Application files. Your browser may keep copies of application files to improve loading and support the installed web application. These copies may be replaced when the application updates or removed through browser settings. This does not enable offline trade execution.
Analytics. We use product analytics, including the provider described in Section 8, to understand use of the Services and improve them. This may include account or session identifiers, referral information, and activity involving pages, features, Wallets, trades, orders and rewards. Analytics may use browser storage and information generated when you use the Services. Analytics storage remains until its configured expiry or removal through browser settings; contact us for details applicable to your visit.
Your choices. The informational notice in the documentation is not a consent control; dismissing it does not disable analytics. Neither dismissing that notice nor accepting the Terms is consent to non-essential tracking. Where applicable law requires prior consent, non-essential storage or access requires a separate valid choice and a way to refuse or withdraw it. You can clear browser storage and contact [email protected] about analytics processing and your applicable rights.
Notifications. If you enable browser notifications, we process subscription information to deliver updates through your browser's notification service. Messages may be visible on a locked device. You can revoke permission in browser or device settings; contact [email protected] to request subscription removal where a dedicated control is unavailable. Changing an in-app display preference does not necessarily remove the subscription. Enabling notifications does not give QZAR access to camera content or precise location.
11. International transfers and where we process information
QZAR uses infrastructure and service providers that may process information in countries other than your country of residence. Telegram and globally distributed blockchain services may also involve independent cross-border processing. Data-protection rules can differ between countries.
Where applicable law restricts international transfers, a transfer is subject to the relevant legal requirements, including a valid transfer mechanism and supplementary safeguards where required. The mechanism depends on the recipient and transfer and may include an adequacy decision or approved contractual safeguards. Contact [email protected] to request information about processing locations and the safeguards applicable to your data, including a copy where you are entitled to receive one, subject to necessary redactions.
12. How long we retain data
We keep personal data only as long as reasonably needed for its stated purpose, a valid legal claim or a binding retention obligation. We determine retention by the type of data, the requested feature, the account relationship, the need to resolve transactions or disputes, and applicable legal requirements.
| Category | Retention criteria |
|---|---|
| Account and profile data | While needed to maintain the account and requested features; after closure only where justified by a legal obligation, security need or unresolved claim |
| Privy wallet references, provider-held keys and import/export material | While needed for authorised Wallet functions and the applicable exit, deletion or legally required retention process; account closure and provider-side key-access handling are assessed separately |
| Orders, transaction, fee and reward records | While needed to execute or reconcile instructions, maintain accurate accounts, meet legal recordkeeping duties or resolve disputes |
| Security, access, error and application logs | For the period reasonably needed to identify failures, prevent abuse, investigate incidents and protect legal claims |
| Support correspondence | While needed to handle the request and any related complaint, dispute or legal obligation |
| Public profile, watchlist, preset, tournament and analytics records | While needed for the relevant feature, disclosed analytics purpose, result verification, recordkeeping or dispute resolution |
| Push subscriptions | While needed for the requested notification service; provider expiry responses and applicable removal requests inform deletion |
| Cookies, session data and local caches | According to Section 10 and the browser/device controls available to you |
When data is no longer needed, we delete it or irreversibly anonymise it, unless a lawful hold or retention duty applies. Restricted backup copies follow the backup lifecycle and cannot be used as a general reason to resume a deleted profile. QZAR cannot erase independent copies of public blockchain records. Contact [email protected] for retention information relevant to your request.
13. Security and incidents
We use Privy for Wallet key infrastructure and signature requests, together with QZAR account and session controls. Account protections include encrypted authenticator secrets, secure HttpOnly session cookies, additional checks for sensitive web actions and a bot PIN for key export. These controls differ by interface and do not prevent every unauthorised signature or disclosure. QZAR's server authorisation key permits Privy signing and key-export requests; its compromise or misuse is a material risk. No platform can guarantee absolute security. Protect your Telegram account, browser/device, authentication method, session and exported Wallet material. Do not send your seed phrase to customer support.
We will investigate personal-data incidents and provide notifications to authorities or affected individuals where required by applicable law. If you suspect a QZAR account or credential exposure, use our verified security contact immediately and consider moving Digital Assets to a fresh Wallet controlled by you.
14. Your privacy rights and contact process
Subject to applicable law and exceptions, you may request information about processing, access to data, correction, deletion, restriction, portability and, where applicable, object to processing based on legitimate interests or object unconditionally to direct marketing. Where processing relies on consent, you may withdraw it without affecting prior lawful processing. Applicable laws may also give rights relating to qualifying automated decisions.
Send requests to [email protected]. We may verify the request proportionately but will not ask you to disclose a private key, recovery phrase or account password. We respond within the deadlines required by law; under the GDPR this is normally one month, subject to lawful extensions. Where we cannot meet a request in full we explain the relevant reason unless prohibited. A pending trade, legal duty or public blockchain record may limit what can be erased, but will not automatically nullify your request.
You may complain to the relevant supervisory authority. For the EEA, see the European Data Protection Board supervisory authority directory; for the UK, see the Information Commissioner's Office. A privacy complaint to a competent authority is not subject to a contractual arbitration requirement.
15. Closing an account and data deletion
To request closure or deletion, use a supported account control, if available, or contact [email protected]. You should independently export or back up keys needed to retain access to assets and cancel active instructions before requesting account closure. Those precautionary steps do not remove statutory erasure rights.
QZAR will handle account access revocation, remaining authorised automated instructions, Privy wallet references and provider-held key access in accordance with the Terms of Use, applicable law and the relevant closure process. Signing out, ending browser sessions, unlinking a login method or removing a Wallet from a list does not by itself delete a Privy key or revoke signing authority. Where no dedicated closure control is available, send the request to [email protected]; we must assess relevant records and provider-side action separately. A closed account does not reverse a blockchain trade, remove public blockchain records or guarantee that locally stored browser/PWA files have been removed from your device. We will explain justified retention and restrictions when responding to the request.
16. Children and excluded services
The Services are for people aged 18 or older. If you believe someone under 18 has supplied personal data through QZAR, contact us and we will take the steps required by law. The public-profile, ranking and tournament features described above do not imply a general social network, user trading-thesis publishing, futures or prediction markets. Materially new functions involving different data types will require revised notices and, where appropriate, new choices before deployment.
17. Changes and contact details
We may update this Policy when the Services, legal requirements or actual processing changes. We will post the revised text and effective date and give additional notice for material changes when appropriate. If a changed activity requires consent, we will request it before carrying it out. Earlier processing is assessed under the law and notice applicable at the relevant time.
If responsibility for processing changes following a reorganisation or transfer of the Services, we will publish the new controller's details and the effective date in this section and provide affected individuals with the notice required by applicable law. Any related disclosure or international transfer of personal data requires an applicable lawful basis and the safeguards described in this Policy. A change of service provider or controller does not itself supply consent where consent is required, erase existing privacy obligations or remove your rights. A separate developer or technical provider is a controller or processor according to its actual role.
Privacy requests: [email protected].
Do not include a private key, seed phrase, PIN or other secret in a privacy or support request.