ArbiBlast Privacy Policy

Last updated: 17 October 2026

This Privacy Policy explains how ArbiBlast.fun processes information when you use ArbiBlast, arbiblast.fun, and related ArbiBlast websites, interfaces, APIs, applications, and services (collectively, the “Services”).

For purposes of this Privacy Policy, “ArbiBlast.fun,” “ArbiBlast,” “we,” “us,” and “our” refer to ArbiBlast.fun, which operates the Services. For privacy questions or requests, contact [email protected].

This Privacy Policy does not apply to public blockchains or independent third-party services that process information under their own terms.

1. Important Blockchain Privacy Notice

Public blockchains are public by design.

Your wallet address, transactions, token balances, token holdings, approvals, smart-contract interactions, transaction timestamps, counterparties, and other on-chain activity may be permanently visible to anyone.

Blockchain data generally cannot be deleted or altered by ArbiBlast.

Connecting a wallet to the Services may allow wallet activity to be associated with technical information such as an IP address, device information, account identifier, or session information.

You should not assume that a blockchain wallet is anonymous.

2. Data Controller

For purposes of applicable data-protection law, ArbiBlast.fun acts as the controller of Personal Data processed in connection with the Services, except where a third party acts as an independent controller.

Privacy contact: [email protected]

3. Who This Policy Applies To

This Policy applies to visitors, connected-wallet users, token creators, API users, support contacts, and other persons who interact with the Services.

The Services are not directed to persons under 18.

4. Information We May Collect

The information collected depends on the features you use.

4.1 Wallet and blockchain information

We may collect or process:

• wallet addresses;
• ENS or other blockchain names;
• token balances;
• transaction hashes;
• transfers;
• approvals;
• smart-contract interactions;
• token creation activity;
• liquidity activity;
• trading activity;
• creator-fee activity;
• public blockchain history; and
• other information available on public blockchains.

Much of this information is public and may be obtained from public blockchain records.

4.2 Wallet connection and preferences

We may process your connected wallet address, risk acknowledgement, referral attribution, and the settings and preferences you choose to save. Connecting a wallet does not give ArbiBlast access to your private key.

When you acknowledge policies with your wallet, we store the wallet address, signature, signed message, exact document versions, eligibility declaration, detected country, network, verification block and acknowledgement timestamps. These records document acceptance and help enforce interface access. They are stored by ArbiBlast and are not published onchain by this signing flow. This acknowledgement record does not include your raw IP address.

4.3 Device and usage information

We may automatically collect:

• IP address;
• approximate location inferred from IP;
• browser type and version;
• operating system;
• device type;
• language;
• time zone;
• referring pages;
• pages viewed;
• buttons or features used;
• timestamps;
• error logs;
• performance data;
• session identifiers; and
• similar technical information.

4.4 Transaction-preparation information

When you use transaction-building or simulation features, we may process:

• wallet address;
• selected token or pair;
• transaction amount;
• slippage settings;
• contract address;
• network;
• gas estimates;
• unsigned transaction data;
• simulation results; and
• related request metadata.

A signed transaction may be submitted by your wallet. ArbiBlast does not require access to your private key.

4.5 Communications

If you contact ArbiBlast, we may process your:

• email address or social handle;
• wallet address;
• support request;
• attachments;
• correspondence; and
• information reasonably necessary to resolve the request.

4.6 User Content

If the Services permit content submission, we may process token metadata, names, symbols, images, descriptions, links, comments, profiles, posts, and related moderation records.

4.7 Compliance and risk information

We may process:

• sanctions-screening results;
• wallet-risk indicators;
• fraud signals;
• geographic eligibility signals;
• IP-risk or proxy indicators;
• blockchain analytics;
• restricted-person indicators;
• identity or eligibility documentation where required; and
• records relating to compliance decisions.

4.8 Local storage and similar technologies

Token pages use the open-source FingerprintJS library to derive a browser identifier locally and deduplicate page views. We receive the derived identifier, not the underlying browser fingerprint components. When a wallet has a verified signed session, we link its address to that identifier so repeated visits and visits from another browser do not count again. FingerprintJS usage monitoring is disabled. These identifiers are used for view deduplication, not targeted advertising.

We use browser storage for essential functionality, including risk acknowledgement, referral attribution, preferences, and the selected coin, amount, payment token, and slippage for an unfinished trade. Trade drafts stay in this browser tab and are not sent to an analytics provider.

When optional product analytics is configured, we use PostHog only after you select “Allow analytics.” You can decline or withdraw permission through “Analytics preferences” in the footer. We respect browser Do Not Track and Global Privacy Control signals. Browsing, quoting, and trading do not require analytics consent.

For consenting visitors, we measure visits, page views, internal navigation, search usage, discovery controls, portfolio tab selections, coin views, estimated quote views, wallet-connection status, submitted transactions, successful purchases verified from transaction receipts, and coarse failure categories. Page views and navigation use route templates without addresses, query strings, or URL fragments. Search and discovery events use fixed action names without search text or form values. Events include a pseudonymous browser identifier, network and production/test status, device category, a coarse traffic source or sanitized campaign source, new/returning browser status, the public coin contract and ticker, pair type, payment-token symbol, amount range, and slippage. Repeat-purchase counts and deduplication records are stored locally per network. We do not send wallet addresses, transaction hashes, wallet balances, exact entered amounts, full page/referrer URLs, or RPC/wallet error text to PostHog. Automatic interaction capture, screen/session recording, and person profiles are disabled; outbound events request that PostHog skip IP-based geolocation enrichment. PostHog and network infrastructure may process request metadata to deliver the service. Server-side retention and regional hosting depend on the operator’s PostHog project configuration.

Analytics represents only visitors who opt in and purchases observed by an open browser; it is not a complete record of onchain activity. Privacy contact: [email protected].

We also use an essential, secure, HTTP-only wallet-verification cookie, valid for up to 30 days, to associate a browser session with a verified policy acknowledgement. Geographic eligibility is checked separately and may require confirmation sooner. The browser cookie does not replace the server-side acknowledgement record.

5. Information We Do Not Need

ArbiBlast does not need your seed phrase or private key.

Do not provide either to ArbiBlast, support personnel, token creators, or anyone claiming to represent ArbiBlast.

6. Sources of Information

We may obtain information:

• directly from you;
• from your browser or device;
• from your wallet;
• from public blockchains;
• from services you choose to connect;
• from compliance, fraud, and security checks;
• from public sources; and
• from services you choose to use with ArbiBlast.

7. How We Use Information

We may use information to:

1. provide and operate the Services;
2. display blockchain information;
3. prepare, simulate, or facilitate user-authorized blockchain interactions;
4. authenticate users and wallets;
5. remember preferences;
6. provide support;
7. detect abuse, bots, manipulation, fraud, phishing, hacking, and security threats;
8. screen wallets or users for sanctions, eligibility, and other compliance purposes;
9. enforce the Terms of Use and other policies;
10. moderate User Content;
11. investigate suspicious activity;
12. improve reliability, performance, and user experience;
13. conduct analytics and product research;
14. measure referral or marketing performance where permitted;
15. communicate administrative, security, legal, or service notices;
16. comply with legal obligations and lawful requests;
17. establish, exercise, or defend legal claims; and
18. protect ArbiBlast, users, and third parties.

8. Legal Bases for Processing

Where the GDPR, UK GDPR, Swiss data-protection law, or similar laws require a legal basis, ArbiBlast may rely on:

• contractual necessity where processing is necessary to provide a requested Service;
• legitimate interests, including security, fraud prevention, service improvement, analytics, enforcement, and protection of users;
• legal obligation, including sanctions, court orders, regulatory requirements, tax, and lawful government requests;
• consent, where required for cookies, marketing, or another specific activity; and
• legal claims or substantial public interest, where permitted by applicable law.

Where processing is based on consent, you may withdraw consent prospectively.

9. Browser Storage and Controls

9.1 Current use

ArbiBlast uses browser storage for essential product functions, including remembering risk acknowledgement, referral attribution, and user preferences.

9.2 Controls

You may clear browser storage through your browser settings.

Disabling certain technologies may cause features to stop working.

9.3 Advertising

ArbiBlast does not use Personal Data for targeted advertising and does not knowingly sell or share Personal Data for cross-context behavioural advertising.

10. How We Share Information

We may disclose information to the following categories of recipients:

10.1 Companies supporting the Services

Providers that assist with operating, securing, supporting, and improving the Services may process limited information on ArbiBlast's behalf.

10.2 Compliance and security checks

Information such as wallet addresses, IP-derived information, or transaction data may be assessed for sanctions, fraud, abuse, and security risks.

10.3 Public blockchain networks

Information you choose to submit in a transaction may be transmitted to a public blockchain and become publicly and permanently accessible.

10.4 Third-party protocols

Where you choose to interact with a third-party protocol through the Interface, that protocol may receive or independently observe blockchain or technical data.

10.5 Professional advisers

Information may be disclosed to legal, accounting, audit, security, insurance, or other professional advisers where reasonably necessary.

10.6 Authorities and legal process

Information may be disclosed where ArbiBlast reasonably believes disclosure is required or permitted by law, court order, legal process, sanctions obligations, or to protect rights, safety, or security.

10.7 Business transfers

Information may be transferred as part of a merger, restructuring, financing, acquisition, sale of assets, or transfer of the Services, subject to applicable law.

11. International Transfers

Personal Data may be processed in countries other than the country where you live.

Where required, ArbiBlast may use recognized transfer mechanisms such as adequacy decisions, standard contractual clauses, contractual safeguards, or other lawful mechanisms.

Public blockchain data may be replicated globally and cannot be geographically restricted by ArbiBlast.

12. Data Retention

ArbiBlast retains Personal Data only for as long as reasonably necessary for the purposes described in this Policy, including security, fraud prevention, legal compliance, dispute resolution, and enforcement.

Retention periods depend on the type of information.

Examples:

• essential security records may be kept for a limited period unless required for investigation;
• support communications may be retained while necessary to resolve issues and maintain records;
• compliance records may be retained for legally required periods;
• account information may be retained while an account remains active and for a reasonable period afterward; and
• public blockchain data may remain permanently available independently of ArbiBlast.

Backups may persist for a limited period after deletion.

13. Security

ArbiBlast uses reasonable technical and organizational measures intended to protect Personal Data.

No internet, wallet, blockchain, or storage system is completely secure.

ArbiBlast cannot guarantee absolute security.

You are responsible for securing your wallet, device, credentials, and authentication factors.

14. Your Privacy Rights

Depending on where you live, you may have rights to:

• request access to Personal Data;
• request correction;
• request deletion;
• restrict processing;
• object to processing;
• receive certain data in portable form;
• withdraw consent;
• appeal certain privacy decisions;
• complain to a competent data-protection authority; and
• opt out of certain forms of sale, sharing, targeted advertising, or profiling where applicable.

Rights are subject to legal limitations and exceptions.

ArbiBlast may need to verify your identity before acting on a request.

A blockchain wallet signature may be used to verify control of a wallet where appropriate, but control of a wallet does not necessarily prove the identity of an individual.

Requests may be sent to [email protected].

15. Blockchain Data and Deletion Requests

ArbiBlast cannot delete or change information recorded on a public blockchain.

If a valid deletion request applies to off-chain Personal Data controlled by ArbiBlast, ArbiBlast will address that off-chain data as required by applicable law.

De-indexing or hiding blockchain content in the Interface does not erase the underlying blockchain record.

16. Children

The Services are not intended for anyone under 18.

ArbiBlast does not knowingly seek to collect Personal Data from children.

If you believe a person under 18 has provided Personal Data through an off-chain ArbiBlast feature, contact [email protected].

17. Third-Party Links and Services

The Services may link to third-party websites, wallets, protocols, social networks, block explorers, or other services.

Those third parties have their own privacy practices.

ArbiBlast is not responsible for their privacy or security practices.

18. Automated Risk and Eligibility Signals

ArbiBlast may use automated tools to identify suspected fraud, sanctions risk, geographic restrictions, bot behavior, wallet risk, or violations of the Terms.

Such tools can produce false positives or incomplete results.

Where applicable law grants rights concerning solely automated decisions that produce legal or similarly significant effects, ArbiBlast will provide those rights as required.

19. Do Not Track and Universal Opt-Out Signals

ArbiBlast respects browser Do Not Track and Global Privacy Control signals by disabling optional product analytics when either signal is active, including when you previously allowed analytics. You can also decline or withdraw analytics consent through Analytics preferences in the footer. These choices do not prevent you from browsing, requesting quotes or trading.

20. Changes to This Policy

ArbiBlast may update this Privacy Policy to reflect changes in law, technology, or the Services.

The updated version will show a revised “Last updated” date.

Where required, material changes will be communicated through reasonable notice.

21. Contact

Privacy questions and requests:

ArbiBlast.fun
Privacy contact: [email protected]

Do not send seed phrases, private keys, or authentication secrets.