This guide is here to help you understand the Privacy Policy in plainer language. It is not the binding legal policy. If this guide and the Privacy Policy ever differ, the Privacy Policy controls.

Privacy Policy Guide

Binding policy: binding Privacy Policy

The Short Version

Axiom Charts may collect personal information when you use the website, create an account, buy something, use paid access, contact support, or interact with related tools.

That does not mean every kind of data is collected from every person. It means different parts of the service may involve different records.

Some records are simple, like your name, email address, account ID, or support message. Some are more operational, like purchase history, subscription state, refund-related metadata, discount use, affiliate or referral metadata, TradingView fulfillment information, and access history for paid products.

Axiom also uses outside providers to run parts of the service. That is not the same thing as selling personal information. It does mean some providers may process information for their own role, and their own policies may also apply.

What This Guide Is For

This guide explains the Privacy Policy in plain language. It is meant to help you understand what may be collected, where it can come from, why it may be used, which providers may process it, and how privacy requests work.

This guide does not give legal advice. It does not create new privacy rights. It does not replace the Privacy Policy.

The binding Privacy Policy is the legal source.

What Information Axiom May Collect

Axiom may collect different kinds of information depending on how you use the service.

That can include:

• Contact and account details, such as your name, email address, account identifiers, and message content.

• Account and profile data, such as login events, authentication metadata, optional profile details, TradingView usernames, and fulfillment information.

• Commerce and entitlement data, such as purchases, product packages, subscription state, transaction metadata, affiliate or referral metadata tied to checkout, refund-related metadata, discount use, and access history needed to run paid access.

• Support, feedback, and operational data, such as support messages, attachments, help-center use, error records, and feature or changelog interactions.

• Device, browser, log, and security data, such as IP address, user agent, session metadata, abuse-prevention data, and debugging information.

Cloudflare Turnstile is also used in managed mode on selected forms and account, support, and checkout workflows. It helps check for automated abuse. On protected workflows, Turnstile may process device, browser, interaction, and network signals.

This is broader than "name and email." Paid access, checkout, support, security, fulfillment, refunds, discounts, and affiliate tracking can all create records.

Where The Information Comes From

Information can come from three main places.

First, it can come from you. That may happen when you create an account, make a purchase, contact support, submit a form, or use the service.

Second, it can come from providers that help Axiom run the service. These may include tools for authentication, hosting, support, affiliate attribution, analytics, and payment processing.

Third, some information can be collected automatically through browser, device, logging, and storage technologies while you use the website or account areas.

Automatic collection is not only cookies. It can also involve logs, device data, browser data, session state, and similar technology.

Why Axiom Uses Information

Axiom uses personal information to run the service and keep account, access, checkout, and support records lined up with what actually happened.

That can include:

• Creating and managing accounts.

• Delivering products and packages.

• Keeping entitlement and fulfillment records accurate.

• Processing purchases.

• Reconciling billing events.

• Handling subscriptions.

• Responding to support requests.

• Sending transactional or operational updates.

• Looking into service issues.

• Protecting the platform from abuse.

• Monitoring reliability.

• Improving the user experience.

• Meeting legal, tax, accounting, and recordkeeping duties.

For example, if you buy a product, the system needs enough purchase and access history to know what you bought and whether access should still be active. If a product needs a TradingView username, that username may become part of fulfillment data. If you send a support message or attachment, that material may become part of the support record.

Some tools have extra consent limits. Where required by law, optional analytics, support tooling, and affiliate-attribution processing start only after the relevant consent choice has been made.

Consent is not the only reason information may be processed. The binding policy also lists contract needs, legal duties, legitimate business interests, security, fraud prevention, and similar reasons, subject to applicable law.

Providers Who May Process Information

Axiom uses outside providers to run parts of the website, account system, checkout, support, analytics, affiliate attribution, and security workflows.

Provider processing does not mean Axiom sells personal information. It also does not mean Axiom never shares information.

The Privacy Policy names these providers and roles:

• Paddle handles merchant-of-record payment processing, billing, tax handling, transaction administration, and checkout metadata for referred purchases.

• Cloudflare Turnstile helps with managed bot protection, fraud prevention, and abuse-prevention checks on protected website workflows.

• Affonso supports optional affiliate attribution, referral continuity, and user-id-based signup tracking when marketing consent is enabled.

• Featurebase supports optional support, help-center, feedback, changelog, messenger, and chat workflows when a user enables support tools or requests chat support.

• Vercel Analytics supports optional traffic and product analytics after analytics consent is granted.

Axiom may also share information with authentication, infrastructure, database, storage, and related technical providers that help operate the business and service.

Professional advisers, auditors, legal counsel, or authorities may also receive information where disclosure is reasonably necessary or legally required.

Some providers may independently control information for their own legal or operational reasons. When that happens, the provider's own policy also applies. Paddle is an important example because it acts as merchant of record for checkout and payment processing.

Cookies, Storage, And Consent-Sensitive Tools

Privacy and cookies overlap. The Cookie Policy explains cookies and browser storage in more detail.

Some browser storage or similar technology may be needed for requested services. That technology can help with login, cart state, checkout return state, subscription updates, security checks, and billing actions.

Optional tools are different. Where required by law, optional analytics, support tools, and affiliate attribution are turned on only after the relevant consent choice has been made.

Affonso has one detail that is easy to mix up. Before marketing consent, the Affonso script may detect referral parameters and keep referral continuity in the URL. The Privacy Policy separates that from enabling marketing cookies or lead tracking. When marketing consent exists, Axiom may share an internal account identifier with Affonso so referred signups and purchases can be attributed correctly.

This does not mean optional support, analytics, or marketing processing is the same as necessary account, checkout, security, or product-access processing.

Sale And Cross-Context Advertising

The current Privacy Policy says Axiom does not sell personal information.

It also says Axiom does not share personal information for cross-context behavioral advertising as those concepts are commonly used in privacy law.

That is an important limit. It is not a promise that Axiom never shares information with service providers.

If Axiom materially changes that posture in the future, the Privacy Policy and any required user controls will be updated before the new activity is enabled.

Where Information May Be Processed

Axiom and its providers may process information outside the place where you live.

Where required, Axiom relies on contractual, organizational, or technical safeguards intended to support lawful international transfers.

This does not mean information always stays in your country. It also does not mean safeguards make every risk disappear.

How Long Information May Be Kept

Axiom keeps personal information only as long as reasonably necessary for the purposes in the Privacy Policy.

Those purposes can include operations, legal duties, accounting, tax records, security, and dispute resolution.

How long a record is kept may vary. It can depend on account status, transaction history, support history, security investigations, and legal obligations.

This means there is not one single deletion date for every record. It also means a deletion request does not always remove every record right away.

Security

Axiom uses administrative, technical, and organizational safeguards designed to protect personal information.

Those safeguards are meant to help protect against unauthorized access, misuse, loss, alteration, or disclosure.

But no system can be guaranteed perfectly secure. No transmission or storage method is immune from failure or attack.

Both parts matter: Axiom uses safeguards, and those safeguards are not a perfect shield.

Privacy Rights And Requests

Depending on your jurisdiction, you may have privacy rights.

Those rights may include access, correction, deletion, restriction, objection, portability, or withdrawal of consent.

Not every right applies to every person in every place. Axiom may need to verify your identity before fulfilling certain requests. Axiom may also decline a request where an exemption or legal basis to retain information applies.

To make a privacy-related request, use contact support.

That contact path does not promise a specific result, deadline, deletion, correction, or legal right.

Children

Axiom's services are not directed to children under 18.

Axiom does not knowingly collect personal information from children under 18.

If you believe a child has provided personal information to Axiom, use contact support so Axiom can review and address the matter appropriately.

That review step matters. This guide does not promise an automatic result before Axiom reviews the concern.

What This Does Not Mean

This guide does not mean Axiom sells personal information.

It does not mean Axiom never shares information with service providers.

It does not mean every customer has every privacy right listed.

It does not mean every privacy request will be granted.

It does not mean a deletion request always removes every record.

It does not mean optional support, analytics, or marketing processing is the same thing as necessary security, checkout, account, or access processing.

It does not mean data is guaranteed safe from every failure or attack.

It does not mean this guide replaces the binding Privacy Policy.

Changes And Contact

Axiom may update the Privacy Policy to reflect product, operational, legal, or regulatory changes.

The Last updated date in the Privacy Policy shows the latest revision. The current binding policy lists June 4, 2026.

Questions about the Privacy Policy can be sent through contact support.

That contact path does not mean Axiom gives legal advice or promises a specific support outcome.