Dharmarth Ads is operated within Dharmarth Traders (OPC) Private Limited. This service remains independent from third-party advertising platforms unless a written agreement says otherwise.
What the public workflows collect
The media planner collects business contact details, organisation, objective, budget, timing, category, destination, geography, language and channel preferences. Publisher intake collects business contact details, property URL and type, languages, formats, self-reported inventory scale, supply declarations and consent. Partnership intake collects role, business context and any planning reference you choose to link. Do not submit passwords, payment credentials, special-category personal data or customer lists.
How contact and analytical records are separated
Contact details needed for follow-up are encrypted in a separate authenticated vault with an independent key. Authenticated operator retrieval is access-logged. The business ledger stores pseudonymous contact and company identifiers plus bounded planning or readiness facts; it does not store raw names or email addresses.
Why we use the information
We use the information to create an on-screen planning receipt, assess a property or request, queue human follow-up, enforce policy, prevent duplicate submissions, maintain business evidence and protect the service. The current product does not use these submissions to train a cross-customer outcome model or sell personal data as a standalone product.
Retention
Operational contact records use a default 90-day follow-up period and expired records are excluded and pruned by the vault workflow, unless a legal or documented business obligation requires a different period. Pseudonymous business receipts and access evidence may be retained longer for integrity, security, dispute and legal purposes. Commercial records will follow the signed agreement and applicable law.
Website and future advertising data
Normal edge and application logs may process network and route metadata for availability and abuse prevention. Edge access logs redact query-string values, and the public delivery tag does not collect a page title or full page URL. Media connectors, cross-site profiles, conversion measurement, automated bidding and publisher delivery are not enabled by the current public planning workflows.
RTB Intelligence, live aggregates and identity providers
The public RTB Intelligence demo uses synthetic observations calculated in the browser and is labelled as a demo. The protected live workspace reports minute-level counters observed by the Dharmarth Ads gateway from authenticated, permissioned sources. Its aggregate store excludes raw bid requests, page URLs, IP addresses, user or device identifiers, creative markup and advertising-account credentials. Bid, win, spend, invalid-traffic and viewability fields remain unavailable until a contracted source supplies them under an approved measurement definition. Live telemetry does not itself authorize media spend.
Google, Meta and X identity options remain inactive until registered applications, server-side callbacks and a purpose-specific notice are deployed. Arattai is not represented as an active identity provider without a verified official integration contract. Identity sign-in and permission to access an advertising account will remain separate consent steps.
Your choices
Use the privacy rights request form to request access, correction, deletion or withdrawal. Include the application reference if known and avoid unrelated personal data. We will verify the requester before disclosing or changing a record.
Changes
We version this notice when material data flows, retention rules, operators or legal responsibilities change.