Short, because there is not much to describe. We are an advertising company that does not build audience profiles, which is unusual enough to be worth stating plainly.
What we collect
- Account data. Your email address, and whatever you choose to add: company name, website, Telegram handle.
- Campaign data. The briefs, creatives, budgets and flight dates you submit, plus the transaction hashes of deposits you make.
- Support tickets. The messages and screenshots you send us.
- Delivery data. Impression and click counts for ads we serve. This is aggregate: counts per placement per day, plus the coarse signals used to filter invalid traffic (IP, user agent, timing). It is not tied to an identity and it is not used to build a profile of anyone.
What we do not do
- We do not sell or rent data to anyone, in any form.
- The analytics and advertising tags on praxads.com (Google Analytics and the Meta pixel) load only under the answer described in the section below, which also names every cookie that can be set and what turns it on.
- We do not do cross-site behavioural targeting or wallet-level targeting. Campaign targeting is contextual: which site, which section, which geography.
To measure which of our own ads work, when you sign up, request a deposit or make one we send the advertising platforms we buy ads from (Meta, for example) your account id, a hashed copy of your email address, the amount and any transaction hash involved, any Meta browser and ad click identifiers stored with your account, and, when it happens in your browser, the IP address and browser details it sent us.
Visitors to this website (praxads.com)
We measure which pages work. Where the law says to ask first, we ask first, and until you press “Allow all” on the bar at the bottom of the page nothing loads: no Google script, no request to Google, no analytics cookie. Press “Essential only” and the same is true, permanently. That covers the EEA, the UK, Switzerland, Turkey, Brazil, Quebec, China, Saudi Arabia and Nigeria.
Everywhere else, where the rule is opt-out rather than opt-in, analytics runs and the control below turns it off in one press. We would rather say that plainly than show everybody a bar and imply a choice we were not required to offer. Either way your answer wins: refuse in a country where we did not have to ask and you stay refused, agree in a country where we did and you are not asked again.
This is the whole of it:
| Cookie | Set by | What it is for |
|---|---|---|
| praxads_consent | Us, first party | Your answer to the question, so we do not ask again. Set whichever way you answer, including when the answer is no, because it is the record of the decision. With praxads_consent_required, it is all “Essential only” leaves you with. Lasts 180 days. |
| praxads_consent_required | Us, first party | Whether the country your request arrived from is one where we have to ask before loading analytics. One character, y or n, written from the country our host already sees on every request. It is not a choice and it holds nothing that identifies you. Lasts 180 days. |
| praxads_utm | Us, first party, only after you allow it | The campaign that brought you here, when the link carried one (utm_source, utm_medium, utm_campaign, utm_content, utm_term, gclid), so a signup can be matched to the ad that led to it. Removed when you choose “Essential only”. Lasts 90 days. |
| praxads_ref | Us, first party, only after you allow it | When you arrive from a PraxAds ad on a PraxNet publisher's page: the signed id of the PraxNet page whose house ad you clicked, so the publisher can be credited if you open an advertiser account. Where we have to ask first, it is only kept after you allow it. Removed when you choose “Essential only”. Lasts 30 days. |
| _ga | Google Analytics 4, only after you allow it | Distinguishes one browser from another so a visit is not counted as several. |
| _ga_<property> | Google Analytics 4, only after you allow it | Keeps the state of the current session. |
| _fbp | The Meta pixel, only after you allow it | Distinguishes one browser from another for Meta, so it can tell us which of our ads led to a visit. |
| _fbc | The Meta pixel, only after you allow it | Set when you arrive from one of our ads on Facebook or Instagram: which ad click brought you here. |
Analytics reaches this site through Google Tag Manager, which loads GA4 and the Meta pixel. Google and Meta process that data under their own terms as well as ours, which is exactly why we ask before loading it rather than after. We use GA4 to see which pages work, without advertising features on the property, and the Meta pixel to see which of our own ads work. We do not sell what either collects.
Changing your mind. Use the control below at any time. Turning it off stops the container loading and expires the _ga, _fbp and _fbc cookies this browser is already carrying, and the kept praxads_utm and praxads_ref, as far as a website can: they were set on our domain by Google's and Meta's scripts, and expiring somebody else's cookie is best effort rather than a guarantee. Clearing site data for praxads.com in your browser is the version that always works.
Your choice is kept in a cookie in this browser. The control here needs JavaScript. Without it, clearing the cookies for praxads.com resets the choice.
The sign-in and sign-up pages load Google Analytics directly rather than through Tag Manager, and they follow the same answer and the same country rule as this site: refuse and nothing loads there; where we have to ask, nothing loads there until you allow it here. They do not ask a second time, because the question belongs here rather than in the middle of signing up.
The logged-in dashboard at app.praxads.com is a separate case and is not covered by the control above. It measures the product for the account holder who signed up to use it, and it is being reviewed separately.
Who processes it
We are a small operation and we use standard infrastructure rather than running our own. These providers process data on our behalf:
| Provider | What it handles |
|---|---|
| Vercel | Hosting and request logs for praxads.com |
| Supabase | Account records, campaigns, transactions, uploaded creatives, and support tickets with their screenshots |
| Resend | The emails we send you: sign-in, confirmation and password links, and the notice that a support ticket has an answer (your address and the ticket subject) |
| Google (Tag Manager and Analytics 4) | Page and session counts for praxads.com, only after you allow it |
| OpenRouter | Routes our automated review of ad creatives, ad text and public landing page content to AI models |
| Google (Web Risk) | Checks landing page addresses against its unsafe-site lists |
| Cloudflare | Runs the browser that opens landing pages for review and stores its screenshots |
| Sanity | Published articles, no personal data |
| Telegram | Operational alerts to our own team |
| Public blockchains | Deposit and payout transactions. These are public by design and permanent. We cannot delete them and neither can anyone else |
To review campaigns, we send your ad creatives, your ad text and the public content of your landing page to automated checks, including AI models run by third parties through OpenRouter, and Google Web Risk. We never send them your name, email, wallet or account details.
How long we keep it
Account and campaign records stay while your account is open and for as long after as we need them for financial records. Delivery data is kept in aggregate. Ask us to delete your account and we delete the account data. On-chain transactions are outside anyone's control, including ours.
Your requests
Email contact@praxads.com to see what we hold, correct it, export it or delete it. No form to fill in. A person reads it and replies.
Advertisers get support inside the dashboard. Everything else: contact@praxads.com.