Skip to content
antei
FeaturesDocsBlogSign in
Sign up
  1. Antei
  2. Privacy policy

Privacy policy

Last updated 17 November 2026

This policy explains what Antei (“we”, “us”) collects when you use antei.ai, the Antei console, our MCP server, onboarding booking service at book.antei.ai and our emails, why we collect it, and the choices you have. Questions go to hello@antei.ai.

  1. What we collect
  2. Onboarding calls and Google Calendar
  3. Google Analytics and cookies
  4. Meta Pixel
  5. X Pixel
  6. How we use it
  7. Who we share it with
  8. Where it is stored and for how long
  9. Your choices and rights
  10. Security
  11. Children and changes

What we collect

  • Account details. Your email address, first and last name, and how you signed up (email, Google or Apple). Google and Apple sign-in run through Privy, and we receive your email and, where the provider shares it, your name. If you use a password we keep only a bcrypt hash of it.
  • Waitlist. Your email address, your place in the queue, your referral code and who referred you, and how you found us: campaign tags such as utm_source, ad click IDs and the referring site. Your browser keeps those tags for up to 90 days so they can be attached when you join.
  • Trading. Your Hyperliquid wallet address and the API wallet you approve for Antei (its key is encrypted and never shown to strategy code), plus the strategies, code and settings you upload, backtests, deployments, orders, fills, positions and logs. Hyperliquid is a public blockchain, so activity on it is public by nature.
  • AI assistants. When you connect Claude, Codex or another assistant to our MCP server, we keep the OAuth client and the access you granted, and process the requests your assistant sends for you.
  • Email. When we email you (sign-in codes, account and waitlist messages), we record delivery and whether the message was opened (through a small image) or a link was clicked (links pass through antei.ai). Messages you send to an @antei.ai address are stored so we can read and answer them.
  • Usage and device data. Our servers log the IP address, browser (user agent), page requested and time of each request to run and protect the service. We also use Google Analytics, the Meta Pixel and the X Pixel, described below.
  • Error reports. When something fails on the site or on our servers, a report goes to Sentry so we can fix it: what failed, the page path (never the rest of the address), browser and device type, timing data, related warnings from our server logs, and a recording of the page for the minute before the error in which all text, form input and images are hidden. Passwords, keys, tokens, sign-in codes, email addresses and IP addresses are stripped before a report is sent. Reports from your browser pass through our servers, so Sentry never receives your IP address or cookies, and the admin panel, sign-in return and MCP approval pages are never recorded.
  • Visit recordings. We record how each visit unfolds (session replay): the pages you open, what they show, and your mouse moves, taps and scrolls, so we can see where the site is unclear. It is not video. What you type, email addresses, keys and the rest of each web address are left out; the pages above are never recorded, nor is a browser that sends Global Privacy Control. Recordings stay on our own servers, are linked to your account once you sign in, and are deleted after 30 days or with your account.

Onboarding calls and Google Calendar

Antei Onboarding uses our self-hosted Cal.diy service at book.antei.ai to arrange 30-minute calls with our sales team. When you book, we collect your name, email address, selected time and timezone, and any information you enter in the booking form. Customers do not need to connect their Google accounts or give us access to their calendars.

An authorized member of our team connects the organizer’s Google account. With permission, the scheduler reads the organizer’s calendar list and event availability to offer times that avoid conflicts. It creates, updates and cancels onboarding events on the selected calendar, adds attendees and creates Google Meet links. The integration can also read the organizer’s basic Google profile to display a profile photo. Private calendar event details are not shown to booking visitors.

Google receives the booking details needed to create the event and Meet link. The organizer and invited attendees receive the meeting details, including names, email addresses, time and joining link; Resend delivers booking emails. Booking records, calendar connection settings and access and refresh tokens are stored on our private scheduler servers in Singapore. The Antei account stores booking status and meeting references so it can recognize that you completed this onboarding step.

We use Google Calendar and profile data only to provide this scheduling service. We do not sell it, use it for advertising or use it to train AI models. Antei Onboarding’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

The organizer can disconnect Google Calendar in the scheduler and revoke access in Google Account connections. Disconnecting stops future access; it does not remove existing calendar invitations or booking records. Use your booking email to reschedule or cancel a call. To request deletion of booking records or a calendar connection, contact hello@antei.ai. We retain booking records to manage calls and related support until they are no longer needed or a deletion request is fulfilled, subject to legal retention requirements. Copies held by Google or other attendees remain under their control.

Google Analytics and cookies

We use Google Analytics 4 (measurement ID G-B685DB3XW2) to understand how people find and use antei.ai. It sets first-party cookies (_ga and _ga_B685DB3XW2) and sends Google the pages you view, the referring site, device and browser details, and an approximate location derived from your IP address. Before a page address is sent, our site strips everything except the path and campaign tags, so sign-in codes, invite codes and similar values never reach Google. The admin panel, the sign-in return page and the MCP approval page do not load Google’s tag at all.

We use Google signals, a Google Analytics Advertising Feature. For visitors signed in to a Google account with ad personalization turned on, Google associates this data with that account so we can see aggregated, anonymous reports on demographics, interests and use across devices. For these features Google and we use first-party cookies such as the Google Analytics cookie together with third-party cookies such as Google advertising cookies. We never receive your Google account details.

When you arrive from one of our Google ads, our servers tell Google Ads when your account signs up, when it starts its first paper strategy in Pine Script and in Python, and when it starts its first live strategy, identified only by that ad’s click ID (gclid), never by your email address or other account details.

You can opt out at any time:

  • install Google’s Analytics opt-out browser add-on;
  • turn off ad personalization in My Ad Center;
  • block or delete cookies in your browser settings.

How Google uses data from sites that use its services: policies.google.com/technologies/partner-sites.

The site also keeps your session token and a few preferences in your browser’s local storage, and sets a small cookie that only records that you are signed in, so pages can send you to the right place. For 90 days it also keeps where you first came from (the link’s campaign tags and ad click ID, the first page you saw and the referring site) and sends it with your sign-up, and in a cookie that goes only to our sign-in step for AI apps (/authorize), so an account made in an AI app’s chat is credited to the same link.

Meta Pixel

We use the Meta Pixel, from Meta Platforms, to measure our ads on Facebook and Instagram and the visits that come to antei.ai from Meta. It sets a first-party cookie, _fbp, which lasts 90 days, and after you click one of our ads also _fbc, which holds that ad’s click ID. With each page view it sends Meta the page address (its path and campaign tags only, Meta’s ad click ID included), the referring page, browser and device details, and your IP address. If you are signed in to Facebook or Instagram in the same browser, Meta can link the visit to your account.

The pixel sends a page view only when the page address holds nothing but its path and campaign tags, so on a page whose address carries a sign-in code, an invite or referral code or anything similar it sends nothing. It does not record what you click or type, and we never give Meta your email address or other account details. The admin panel, the sign-in return page, the MCP approval page and the wallet approval pages do not load it at all.

After you create an account, the pixel may send Meta a registration event to measure ads. The event contains no email, wallet, strategy or trading details; Meta also receives browser and device information and may associate it with your Meta account.

You can opt out at any time:

  • choose in Meta’s ad preferences whether your activity on other websites, such as ours, is used to show you ads;
  • block or delete cookies in your browser settings.

How Meta uses this data: facebook.com/privacy/policy.

X Pixel

We use the X Pixel, from X Corp., to measure our ads on X and the visits that come to antei.ai from X. It sets first-party cookies that last 390 days: _twpid for your browser, _twsid for your visit and, after you click one of our ads, _twclid for that ad’s click ID. With each page view it sends X the page address (its path and campaign tags only, X’s ad click ID included), the referring page, browser and device details, and your IP address. X can also recognize your browser by its own cookies, such as muc_ads, and link the visit to your X account.

As with the Meta Pixel, a page view is sent only when the page address holds nothing but its path and campaign tags, and the admin panel, the sign-in return page, the MCP approval page and the wallet approval pages do not load it at all. We turn off its automatic events, so it does not record what you click or type, read our forms or report when you leave a page.

When you arrive from one of our X ads, our servers tell X when your account signs up, when it starts its first paper strategy in Pine Script and in Python, and when it starts its first live strategy, identified only by that ad’s click ID, never by your email address or other account details.

You can opt out at any time:

  • choose in X’s personalization and data settings whether your visits to other websites, such as ours, are used to show you ads;
  • block or delete cookies in your browser settings.

How X uses this data: x.com/en/privacy.

How we use it

  • to run the service you ask for: accounts and sign-in, backtests, and the strategies, orders and deployments you start;
  • to email you sign-in codes, service messages and waitlist updates, each marketing email with an unsubscribe link;
  • to understand and improve the product, including through Google Analytics;
  • to measure our ads and the visits and sign-ups they bring, through Google Ads, the Meta Pixel and the X Pixel;
  • to find and fix errors and slow pages, through Sentry;
  • to keep the service secure and prevent abuse and fraud;
  • to meet legal obligations.

We do not sell your personal data.

Who we share it with

Service providers that process data for us, only for the purposes above:

  • Hetzner, which hosts our servers in Singapore;
  • Privy, which runs Google and Apple sign-in;
  • Resend, which delivers our email;
  • Google, for Google Analytics and the Google Ads conversions described above;
  • Meta Platforms, for the Meta Pixel;
  • X Corp., for the X Pixel and the ad conversions described above;
  • Sentry (Functional Software, Inc.), which receives our error reports and stores them in the European Union;
  • AI model providers, for the content you submit to an AI-assisted feature.

A partner whose link (?ref=) you signed up through within 30 days sees your masked email, sign-up date, country and setup progress, never your trades. Hyperliquid receives the orders you place through Antei. We may also disclose data when the law requires it, to protect people or the service, or as part of a merger or acquisition, in which case this policy continues to apply.

Where it is stored and for how long

Our servers are in Singapore. Our providers may process data in other countries, such as the United States, Japan and those of the European Union, under their own safeguards.

We keep account and trading data while your account is open, and afterwards only as long as needed for legal, accounting or dispute purposes. Waitlist data stays until you join or ask us to remove it. Server logs are kept for a short period. Google Analytics keeps user-level data for the retention period set on our property (currently two months); aggregated reports are kept longer. Sentry keeps error reports and page recordings for up to 90 days.

Your choices and rights

You can ask us to access, correct, export or delete your personal data, or to restrict or object to how we use it. Email hello@antei.ai from the address on your account and we will reply within 30 days. You can unsubscribe from marketing email with the link in any message, and opt out of analytics as described above. If you are in the EU or UK you can also complain to your data protection authority.

Security

Traffic to antei.ai is encrypted with HTTPS, stored exchange credentials are encrypted with AES-256-GCM, and access to production systems is restricted. No system is perfectly secure, so please tell us at hello@antei.ai if you find a problem.

Children and changes

Antei is not for anyone under 18.

If we change this policy we will update the date above, and for material changes we will tell you by email or on the site before they take effect.

antei

The Vercel for AI trading agents on Hyperliquid.
© 2026 Antei AI, LLC

FeaturesBlogPrivacyBack to top ↑