Privacy Policy

The short version

• Ads served through Leedas use no cookies, no tracking pixels, and no visitor identifiers. We do not know who sees an ad, and we do not try to find out.
• We do not build profiles of anyone's browsing, do not sell data, and do not share data for anyone else's advertising.
• If you hold a publisher or advertiser account, we collect the minimum needed to run your account and pay you: your email, your business name, and payment references. Card and bank details go directly to our payment providers and never touch our servers.
• Our automated systems read the public content of enrolled websites to decide which ads fit which pages. They classify pages, not people.

1. If you just see a Leedas ad on a website

This is the part that matters to most people, so it comes first.

When a page requests an ad, our servers pick one based on what the page is about — not who you are. The ad request is processed and answered; we keep a record that an ad was shown (which placement, which campaign, which image, and when) and, if you click it, that a click happened. Those records contain no name, no account, no cookie ID, no device fingerprint, and no browsing history — because we never collected any.

We set no cookies and store nothing in your browser when serving ads. There is nothing to opt out of, because there is no tracking to begin with.

Like nearly every service on the internet, our web servers and our network provider (Cloudflare) produce routine connection logs that can include IP addresses. We use these only for security, abuse prevention, and keeping the service running; they are kept briefly and are never used for ad targeting or joined to ad-serving records.

Ad delivery does not currently use your location at all. If we ever add geography to ad delivery, it will be coarse (city-level at most, never precise location), and we will update this policy before doing so.

2. Conversion measurement

Advertisers reasonably want to know whether their ads work. Leedas supports this with opaque, campaign-scoped tokens: when a click leads to a purchase or signup, the advertiser's server can report the conversion back to us using a token tied to that campaign. This tells the advertiser "a click from this campaign converted" — it does not identify the person, and it does not follow anyone across the web.

3. If you have a publisher or advertiser account

We collect:

• Account details — your email address and sign-in credentials. Passwords are stored only as salted cryptographic hashes; we cannot read them. If you sign in through Google, Microsoft, or GitHub, we receive your email address and an account identifier from that provider — never your provider password. Two-factor authentication secrets are stored encrypted and used only to verify your codes.
• Business details — your organization's name and the information needed to verify your website or run your campaigns.
• Payment references — records of deposits, earnings, and payouts. The sensitive parts (card numbers, bank accounts, identity verification) are collected and held by our payment providers, Stripe and PayPal, under their own privacy policies. Leedas stores only references and statuses, never the credentials themselves.
• Platform activity — the campaigns, sites, placements, and settings you create, and an append-only ledger of every financial event on your account. The ledger is deliberately permanent: it is what makes every balance on Leedas auditable and reconstructable.

We use this information to operate your account — including sending account emails such as password resets and payment notifications — calculate and pay earnings, prevent fraud, and meet our legal and tax obligations. Nothing else.

4. Single sign-on and Google user data

You can create or sign in to a Leedas account with single sign-on from Google, Microsoft, or GitHub instead of a password. When you do, the only data we request from the provider — and the only data we take from its response — is your email address and the provider's account identifier for you. We use that data solely to create your Leedas account, sign you in on later visits, and send you account email (such as password-reset and payment notifications). It is stored with your account record under the protections described in the Security section, and it is deleted or anonymized with the rest of your account data when you close your account.

Sign-in is all we ask for. We request no other scopes and gain no access to anything else in your Google, Microsoft, or GitHub account — no contacts, no files, no calendars, no repositories — and signing in never lets Leedas act on your behalf at the provider.

We do not sell this data, do not share it for advertising, do not use it to train AI or machine-learning models, and do not transfer it to anyone except the infrastructure service providers listed below (as needed to operate the service), when the law requires it, or as part of a merger or acquisition under this same policy. Leedas's use and transfer to any other app of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements.

5. Website content we process

When a publisher enrolls a website, our automated systems — including AI models — fetch and read that site's publicly available pages to classify what the content is about, check advertising suitability, and verify ad placements. The same review applies to advertisers' creatives and landing pages. Classification currently runs on servers Leedas operates; if we use a third-party AI provider for this in the future, it will process only this same public content, under contract.

Only publicly reachable pages participate in Leedas. We do not access private, password-protected, or paywalled content, and classification looks at pages, never at the people reading them.

6. What we share, and with whom

We do not sell personal information, and we do not share it for advertising. We share data only with:

• Service providers who run parts of our infrastructure — currently Cloudflare (networking, content delivery, account email delivery, and abuse protection), Stripe and PayPal (payments and payouts), and, if you use single sign-on, the identity provider you chose (Google, Microsoft, or GitHub) — each limited to what their function requires.
• Law enforcement or regulators, when a valid legal demand requires it, or when necessary to prevent fraud or protect the safety of the platform and its users.
• A successor entity, if Leedas is ever acquired or reorganized — in which case this policy continues to apply to data collected under it.

7. Security

All connections to Leedas are encrypted in transit. Passwords are hashed, every account is protected by two-factor authentication, access to production systems is restricted, financial records are append-only, and backups are encrypted. Some sensitive forms (such as password reset) are protected by Cloudflare Turnstile, which runs a browser check to block automated abuse; it does not identify you or follow you across sites. No system is perfectly secure, but the most effective protection on Leedas is structural: data we never collect cannot leak.

8. Retention and deletion

• Ad-serving records contain no personal information and are kept for reporting and fraud analysis.
• Connection logs are kept briefly for security, then discarded.
• Account data is kept while your account is active. When you close your account, we delete or anonymize your personal information, except financial and tax records we are legally required to keep — those are retained for the legally required period and no longer.

To request access to, correction of, or deletion of your personal information — including rights under state privacy laws such as the California Consumer Privacy Act — email us at the address below. We will respond to verified requests within the timeframe the applicable law requires. We do not discriminate against anyone for exercising a privacy right.

9. Children

Leedas accounts are for adults operating websites and advertising campaigns; you must be at least 18 to hold one. We do not knowingly collect personal information from children — and because ad serving collects no personal information from any visitor, that protection extends to every reader of every page carrying a Leedas ad.

10. Changes to this policy

If we change this policy, we will post the new version here with an updated date, and for material changes we will notify account holders before the change takes effect. We will never retroactively weaken the commitments above for data already collected.

11. Contact

Privacy questions and requests: hello@leedas.com