Back to sale

Privacy Policy

Last updated: 17 November 2026

This policy explains how Matrix handles information on matrix.app, its username guide and reservation website, and related services. The Cookie Policy explains browser storage and analytics. Contact us at contact@matrix.app.

Username reservations

To reserve a username, you provide a username and an email address. We send a one-time email code and check it before the server confirms a reservation. We process the email address, requested username, verification and reservation records, and request information needed to prevent abuse and handle errors.

A website reservation is not an on-chain username, a token purchase or proof of wallet ownership. Later account linking and public username resolution are separate steps. If you link a username to public wallet addresses, those mappings can be public. Do not put private information in a username.

The reservation page keeps email codes, CAPTCHA tokens and temporary claim credentials in its current flow memory. It does not save them as browser preferences. Reloading the page can discard an unfinished flow. The server retains the records needed to process and confirm the reservation.

Hosting, email and security

Cloudflare hosts the websites and provides network protection. The reservation backend runs on Google Cloud. These services can process IP addresses, request details and technical connection information to deliver the service, enforce limits and investigate problems. We use Resend to deliver verification emails. Resend processes the recipient address and verification message for that delivery. See Resend's Privacy Policy.

The reservation form uses Cloudflare Turnstile to check for automated requests. Google reCAPTCHA Enterprise is the fallback when Turnstile is unavailable. These providers process challenge and device or browser information under their own policies. See Cloudflare's Privacy Policy and Google's Privacy Policy and Terms.

Cloudflare Web Analytics can measure website use and performance through the existing website beacon. This is separate from the optional PostHog measurement described below. Hosting, security and provider requests can process connection information even when you decline optional PostHog analytics.

Optional website analytics

With your consent, we use PostHog to count visits and selected actions by consenting browsers on the main website, username guide and reservation flow. We use a pseudonymous browser identifier and fixed page, button and flow-step labels. A pseudonymous identifier distinguishes a browser without using your name. These counts do not represent all visitors or unique people. It is not a promise that all data is anonymous.

Our event payloads contain only the approved page and action measurements. We do not enable session replay, automatic interaction capture or form capture. We do not include email addresses, usernames, email codes, CAPTCHA tokens, claim credentials, wallet addresses, sale access codes, raw page URLs, query strings or referrers in those events. These website measurements do not run on the private-sale portal.

We use PostHog’s US region. The project discards client IP addresses from stored events, and our events disable location enrichment. Each optional event is sent directly from your browser to PostHog. PostHog receives your IP address and standard browser information with the request, such as the browser type, website origin and language headers. It processes this information under its project settings and privacy terms. We do not promise that PostHog discards it immediately or retains it for a particular period.

Optional PostHog measurement starts only after you accept it. You can decline it or change your choice through the website's cookie controls. Declining it does not prevent a username reservation. Your choice and, when analytics is accepted and configured, a random browser identifier are stored locally. Each website origin has its own choice and identifier; we do not share this identity across subdomains.

Rejection or a supported browser privacy signal removes the local identifier where the browser allows the storage change. If storage cannot be updated or cleared, the page reports the problem and keeps optional analytics disabled for that page. The old stored choice can remain, so you may need to clear browser storage before opening a later page. A choice change does not itself delete measurements already received. You can contact us about deletion requests. See PostHog's Privacy Policy.

Private-sale analytics

The website analytics described above do not apply to the private sale. The sale page has its own analytics, and it sends nothing until you select Allow analytics. With your permission, it sends visits, checkout steps and request data from your browser: a fixed request name, a random request reference, the result, the attempt number, timings, connection quality, and if the browser is online and the page is visible.

The sale analytics does not send your invitation code, wallet, amount, transaction, request content, error text or face check data. The last 100 request records stay only in the sale page's memory and are not saved. Select Turn off analytics at any time to stop.

Wallet connection diagnostics

When you choose a wallet on the sale page, the page sends short support diagnostics about that connection attempt to Matrix's sale service. They record fixed connection steps and their timing, the page version, the connection type, a broad browser category such as Safari on iOS, whether the browser is online and the tab is visible, whether the wallet relay is connected and a wallet session is present, and a broad result such as cancelled or timed out. Each attempt gets a new random connection reference, which the page shows so that support can find that attempt.

These diagnostics do not include wallet addresses, invitation codes, pairing links, session topics, signatures, biometric data or raw error text. They are necessary to support wallet connections and are separate from the optional analytics described above. They go only to Matrix, not to PostHog, and are sent even when optional analytics is off. They are sent without cookies, use no saved browser identifier and are not used to track you across sites. Like any request to the sale page, they reach our hosting provider with ordinary connection information, such as your IP address and standard browser information.

Wallet and private-sale services

Matrix's wallet features are self-custodial. The website does not need your private keys or recovery phrase to reserve a username. Do not send these secrets to us. Wallet connections can disclose public addresses and connection information to the wallet provider, WalletConnect and the application you connect to. A public address can be linked to activity on a public blockchain.

Where you choose the optional iCloud Keychain backup on a supported Apple device, recovery data is handled through Apple's Keychain and iCloud Keychain mechanisms. Keep your Apple account and device authentication secure. This is a native wallet feature, not a website reservation requirement.

If you use the private-sale portal, it processes the access code you submit, your connected public address, authentication records, purchase requests and transaction references. Necessary browser cookies support wallet authentication. Local purchase references support recovery from an interrupted checkout. The final deployed contract and the sale terms shown before purchase determine the purchase rules. This policy does not promise a particular vesting, lock-up or settlement schedule.

Private-sale purchases require the buyer to pay the applicable network fees. Mobile wallet sponsorship, where separately supported, does not mean that the private sale sponsors gas.

The private sale requires Didit face verification. During private testing, this is a liveness check only. Didit processes camera images and biometric face data to check that a live person is taking the check. It does not confirm that you are one unique person. Matching your face against earlier checks is temporarily off for private testing, so the face check does not stop the same person from buying with another wallet. Each wallet and each invitation code still allows one purchase. Read and accept the face-check notice before starting. The face check does not request an identity document.

Fingerprint device checks are disabled for new checkouts. The sale does not request new Fingerprint identifications or enforce a one-device purchase restriction while these checks are disabled. Earlier device-check records can remain for purchase history, security and support. The liveness-only Didit check also turns off Didit's IP address and device analysis. Didit still receives ordinary connection information, such as your IP address, when you use its check.

Matrix stores verification decisions and purchase records, not copies of the face images. Didit stores liveness images and results under its retention settings. Face comparison records from earlier checks remain until they are separately deleted. Contact us to request deletion of these images, results or records. Purchase history and device purchase restrictions remain separate.

Uses, sharing and retention

We use information to provide the requested service, verify requests, prevent abuse, maintain security, respond to support requests and meet applicable legal obligations. Optional website analytics follows the choice described above. We do not use this website measurement to build third-party advertising profiles or sell your personal information.

Information is shared with the hosting, security, email, analytics and wallet infrastructure needed for the feature you use. Each provider can also have its own privacy terms. We can disclose information when required by law, at your direction, or as part of a business transfer subject to applicable safeguards.

We keep off-chain information for the purposes for which it was collected, including service operation, security, dispute handling and legal obligations. Different records can have different retention periods. This notice does not promise a fixed deletion deadline for all logs or records. Clearing browser storage does not delete server records or public blockchain data.

Providers can process data outside your country. The applicable safeguards depend on the provider and processing involved. Contact us for information about the processing relevant to your request.

Your choices and rights

Depending on the law that applies to you, you can ask for access, correction, deletion, restriction or a copy of your information, object to some processing, or withdraw consent. Some records may need to remain for legal or security reasons. Public blockchain records cannot be erased by Matrix.

Send requests to contact@matrix.app. We may need to verify that a request relates to you. We will not ask for a private key, recovery phrase or wallet password. You can also raise a concern with the data protection authority available in your jurisdiction.

The Services are for adults who meet the eligibility rules in the Terms of Use. Do not submit a child's information. We may update this policy when the service or its processing changes. We will publish the updated date and provide further notice where required.