Cookie Policy

1. Essential Cookies

These cookies are required for the platform to function. You cannot opt out of them without losing access to the service.

Authentication (Supabase)

When you sign in with Google, Discord, or Apple, Supabase sets a secure session cookie to keep you logged in.

• Name: sb-[project-ref]-auth-token
• Purpose: Maintains your authenticated session
• Duration: Session (clears when you log out)
• Provider: Supabase (supabase.com)

2. Analytics Cookies

We use web analytics to understand how visitors use AXION, which pages they visit, how long they stay, where they came from, and what actions they take. This helps us improve the product.

Depending on the analytics tool configured at launch, this may include cookies or local storage entries from providers such as Plausible, PostHog, or Google Analytics. This section will be updated with specific cookie names once the analytics provider is finalized. Analytics data is aggregated and used to improve the platform, it is not sold or used for advertising profiling independently of the advertising tools described below.

3. Advertising and Conversion Tracking

AXION runs paid advertising on Meta platforms (Facebook and Instagram). To measure whether our ads lead to purchases and to optimize who sees them, we use two complementary tools:

Meta Pixel (browser-side)

The Meta Pixel is a snippet of JavaScript that loads when you visit axionhq.cc. It tracks events such as:

• PageView every page you visit on AXION
• ViewContent when you view the card builder
• InitiateCheckout when you click to deploy your card
• Purchase when a payment is completed

This data is sent to Meta and used to: measure the return on our ad spend, retarget visitors who didn't complete a purchase, and build lookalike audiences of people similar to our customers.

• Cookies set: _fbp, _fbc
• Duration: _fbp persists for 90 days; _fbc is session-based
• Provider: Meta Platforms, Inc. (facebook.com)
• Data sent to Meta: Browser identifiers, IP address (anonymized), page URLs, event names, and purchase values

Meta Conversions API (CAPI server-side)

In addition to the browser-side Pixel, we use Meta's server-side Conversions API. When you complete a purchase, our server sends a conversion event directly to Meta's API. This event may include:

• A hashed (SHA-256) version of your email address
• Purchase value and currency
• Event name (Purchase)
• Your IP address and user agent (used for deduplication with the Pixel)

The purpose of CAPI is to ensure conversion events are accurately attributed even in browsers that block the Pixel (e.g., Safari with ITP, browsers with ad blockers). Email addresses are hashed before being sent and cannot be reversed by Meta to identify you directly. They are used only for matching and measurement purposes.

No cookies are set by CAPI, it operates entirely server-side.

4. Your Choices

Opt out of Meta advertising tracking

You can limit how Meta uses data collected about you for advertising:

• Visit facebook.com/adpreferences to manage your ad settings
• Use the DAA opt-out tool for broader interest-based ad opt-out
• In the EU/EEA, you can also use the Your Online Choices tool

Note: Because CAPI operates server-side, standard browser-based ad blockers do not prevent server-side conversion events from being sent after a purchase. If you would prefer your purchase event not be shared with Meta, contact privacy@axionhq.cc.

Manage cookies in your browser

You can delete or block cookies through your browser settings. Blocking essential cookies will prevent you from logging in. Instructions:

• Chrome
• Firefox
• Safari
• Edge

5. Changes

We will update this page if we add or change tracking tools. The "Last updated" date at the top of this page will always reflect the most recent version.

6. Contact

Questions about our tracking practices? Email privacy@axionhq.cc.