1. Introduction
Meridian Ads is a real-time ad serving product operated by Yelle Software ("we," "our," or "us"). This Privacy Policy explains how we collect, use, disclose, and safeguard information when you visit meridianads.tech, use the Meridian Ads console, call our control-plane or serve APIs, or integrate our SDKs.
By using Meridian Ads, you consent to the practices described in this policy. If you do not agree, please do not use the product.
2. Who This Policy Covers
Meridian Ads serves three audiences. The data we process depends on how you interact with the product:
- Console users (advertisers and publishers): people who sign in to create campaigns, manage apps and placements, buy credits, or request payouts.
- Publisher-supplied profiles: identifiers and trait data your app sends when it requests an ad. We process this on behalf of the publisher to match segments and serve creatives.
- People who see ads in a publisher product: Meridian Ads does not build a cross-site cookie graph. On a static site, the browser tag stores a random viewer id in a first-party cookie on that site for 400 days, and sends the browser language and a coarse device class. Server integrations pass a publisher user id and do not set that cookie. Matching uses that profile and the traits on the request.
3. Information We Collect
Console and account data
When you sign in through Logto, we receive identity and organization membership data needed to operate the console: name, email, org membership, and authentication tokens. We also store the records you create in the product, including apps, placements, campaigns, creatives, segments, API keys, billing history, and payout settings.
Billing and payouts
Prepaid credit purchases and publisher payouts are processed through Stripe. We receive transaction metadata, customer identifiers, and Connect account status. Card numbers are handled by Stripe, not stored on our servers.
Publisher profiles and serve requests
Each serve request may include a user_key (an opaque publisher identifier), a placement name, and an optional context trait map (for example plan, country, locale, or device class). We merge context into a profile keyed by (app_id, user_key). If a user_key looks like an email address, we hash it at rest. When a publisher uses the browser tag, the tag creates that id and stores it in a first-party cookie named meridian_uid. The publisher can override it with data-user-key. The id is not an account and is not added to advertiser links.
Impressions, clicks, and reporting
When a creative is shown, the browser tag or the SDK reports an impression with a signed token. Clicks pass through serve.meridianads.tech, are recorded, then redirect to the advertiser landing URL. Clicks do not include user_key on the destination. We store campaign, creative, placement, and timing data for reporting and billing.
Creative assets and landing pages
Advertisers upload banner images and native copy. We store images on Cloudflare R2 and fetch advertiser destination URLs during automated review. Object names do not contain user_key or org secrets.
Website analytics
We may collect anonymized usage data on the marketing site and console through privacy-respecting analytics (for example Umami). This may include pages visited, approximate region, device type, and referral source. Product feature flags may use Statsig. These tools are for product analytics, not for building an ad identity graph.
4. How We Use Information
We use the information we collect to:
- Operate the console, serve APIs, the browser tag, and SDK integrations
- Match campaigns to publisher profiles and deliver creatives
- Bill prepaid CPM credits on impressions and accrue publisher payouts
- Moderate creatives and recrawl landing pages for policy compliance
- Provide reporting, support, security, and fraud prevention
- Improve the product using aggregated analytics
- Comply with legal obligations and enforce our terms
5. We Do Not Sell Your Data
We do not sell, rent, or trade personal information to advertisers, data brokers, or other third parties. Advertisers receive aggregate reporting (impressions, clicks, spend). They do not receive publisher user_key values or end-user trait maps. Publishers do not receive raw advertiser landing URLs from our click path.
6. Ad Serving and Profiles
Meridian Ads does not use third-party tracking cookies to match ads across sites. Segment matching uses the merged profile for (app_id, user_key) and the traits in the current request. If a campaign requires a trait that is missing, it does not match.
Publishers can request deletion of a profile through the console. We remove the Redis and Postgres copies. Impression and click facts may remain in reporting stores for the retention period described below, without the deleted profile.
7. Creative Review
Before a creative can serve live, our worker fetches the destination URL, extracts page content, and sends copy (and banner images when present) to xAI grok-4-fast for automated policy review. We store fetch snapshots and model output. Landing pages are recrawled every 24 hours. If the moderator is unavailable, creatives remain pending and are not auto-approved.
9. Third-Party Services
We use service providers to operate Meridian Ads. They process data on our behalf under their own terms and, where applicable, data processing agreements. Current categories include:
- Logto for authentication
- Stripe for prepaid credits and publisher Connect payouts
- Cloudflare for CDN and creative image storage (R2)
- xAI for automated creative moderation
- Hosting, observability, email, and analytics providers used across Yelle Software products (for example Sentry, Statsig, Pusher, Mailgun, and Umami)
We do not share console contact data with third parties for their marketing purposes.
10. Data Retention
- Profiles: until GDPR or publisher delete
- Raw impression and click rows: 90 days
- Hourly rollups: kept for reporting
- Console and billing records: as long as needed for the account, payouts, tax, and legal obligations
- Landing fetch snapshots: retained for moderation audit and recrawl
11. Your Rights
Depending on your location, you may have the right to access, correct, delete, port, or restrict processing of your personal data, or to object to certain processing. Publishers can delete end-user profiles through the console. Console users can contact us directly.
To exercise these rights, email [email protected]. We will respond within a reasonable time and in accordance with applicable law. You may also have the right to lodge a complaint with a supervisory authority in your jurisdiction.
California residents: Under the California Consumer Privacy Act (CCPA), you have the right to know what personal information we collect, to delete it, to opt out of "sale" or "sharing" of personal information, and to non-discrimination. We do not sell or share your personal information as defined under the CCPA.
12. Children's Privacy
Meridian Ads is not directed at individuals under the age of 16. We do not knowingly collect personal information from children. Publishers must not send profiles for users they know are under 16. If you believe we have collected information from a child, contact [email protected] and we will take steps to delete it.
13. International Transfers
Your information may be processed in countries other than your own. We take steps to ensure that such transfers are subject to appropriate safeguards (for example standard contractual clauses or adequacy decisions) where required by law.
14. Changes to This Policy
We may update this Privacy Policy from time to time. The effective date at the top of this page will be revised when changes are made. Continued use of Meridian Ads after changes constitutes acceptance of the updated policy. Material changes may be communicated via email or a notice in the console where appropriate.
15. Contact Us
For privacy-related questions, requests, or complaints, contact Yelle Software at:
This Privacy Policy is effective as of September 2026 and applies to Meridian Ads operated by Yelle Software.