Privacy Policy
What we collect, why, who sees it, and how to exercise your rights. Written for account holders, website visitors, and people who see ads we serve.
01 Scope
This Privacy Policy explains how D4RKW3B Networks Ltd. handles personal data in three contexts:
- Account holders: advertisers, publishers, and their staff who apply for or use the dashboard, API, and support channels.
- Website visitors: people who browse d4rkw3b.com and d4rkw3b.network.
- Ad audiences: people who see, click, or interact with ads delivered by D4RKW3B on publisher inventory. We never have a direct relationship with these users and typically cannot identify them by name.
This policy does not cover the practices of advertisers whose landing pages you visit or publishers whose sites you browse. Each of them is responsible for its own privacy notice.
02 Who We Are
D4RKW3B Networks Ltd., a company registered in the Republic of Cyprus, is the data controller for personal data described in this policy, except where we act as a processor on an advertiser's or publisher's documented instructions under a data processing agreement. Our data protection officer can be reached at privacy@d4rkw3b.network.
03 Data We Collect
3.1 Account holders
| Category | Examples | Source |
|---|---|---|
| Identity and contact | Name, company name, email address, Telegram handle, country, phone number if provided | You, during application and account use |
| Verification documents | Government ID, proof of address, company registration, beneficial ownership declarations, gambling or financial licences | You, on request during KYC review |
| Financial | Payment method, bank or wallet identifiers, tax identification numbers, deposit and payout history, invoices | You and our payment processors |
| Business profile | Verticals, target markets, traffic sources, monthly volume, URLs of your inventory or landing pages | You, during application |
| Usage and technical | Dashboard logins, IP addresses, device and browser details, API calls, pages viewed, actions taken, support correspondence | Collected automatically or from your messages |
| Compliance records | Sanctions screening results, fraud review outcomes, policy enforcement history, correspondence with regulators | Generated by us and our screening vendors |
3.2 Website visitors
When you browse our websites we collect standard server logs (IP address, user agent, referrer, pages requested, timestamps) and use a first-party analytics cookie to measure traffic. We do not run third-party advertising or social media trackers on our own websites.
3.3 Ad audiences
When an ad is requested from our servers we receive and process:
- Request data: IP address (truncated to /24 for IPv4 and /48 for IPv6 within 24 hours), user agent, device type, operating system, browser, language, screen size, page URL or app bundle, and referrer.
- Identifiers: a pseudonymous D4RKW3B cookie or local storage identifier, and where a publisher passes it with consent, a mobile advertising identifier.
- Derived data: approximate location at country, region, and city level inferred from IP address; connection type and ISP; a fraud risk score; and frequency counts used to cap how often you see an ad.
- Event data: impressions, viewability, clicks, and conversion events reported by advertisers using a click identifier that does not contain your name or contact details.
- Push subscriptions: where you subscribe to web push notifications on a publisher's site, the browser-generated push endpoint and the time and site of subscription.
We do not collect names, email addresses, or precise GPS location from ad audiences, and we instruct advertisers not to pass such data in conversion postbacks.
04 How We Use Data
- Providing the service: delivering ads, matching advertiser targeting to publisher inventory, routing smartlinks, recording events, calculating billing and payouts, and operating the dashboard and API.
- Frequency capping and relevance: limiting how often a user sees the same ad and selecting ads by context, device, and location. We do not build interest profiles from browsing history across unrelated sites for ad audiences.
- Fraud prevention and traffic quality: detecting bots, invalid clicks, cloaking, and policy violations, and scoring traffic quality with in-house systems and third-party vendors.
- Compliance: verifying identity and licensing, screening against sanctions lists, meeting anti-money-laundering obligations, enforcing our policies, and responding to lawful requests.
- Support and communication: answering questions, sending service notices, payout confirmations, policy updates, and, where you have opted in, product news.
- Improvement: analysing aggregated performance and usage data to improve delivery, reporting, and infrastructure.
- Legal: establishing, exercising, or defending legal claims, and keeping records required by tax and commercial law.
05 Legal Bases
Where the GDPR or UK GDPR applies, we rely on:
- Contract for processing needed to open and operate your account, deliver campaigns, and pay publishers.
- Legal obligation for identity verification, sanctions screening, tax records, and responses to regulators and courts.
- Legitimate interests for fraud prevention, network security, frequency capping, aggregated analytics, and defending legal claims. We have assessed these interests against the rights of the individuals concerned and apply pseudonymisation and short retention to limit impact.
- Consent for setting non-essential cookies and identifiers on publisher sites in jurisdictions that require it, for push notification subscriptions, and for marketing emails. Consent can be withdrawn at any time.
06 Cookies and Ad Technology
Our tags may set the following identifiers on publisher sites. Publishers in jurisdictions that require consent must obtain it before our tag runs; our tag honours the IAB Transparency and Consent Framework signal and the Global Privacy Control header, and operates in a non-identifying mode when consent is absent.
| Name | Purpose | Duration |
|---|---|---|
d4_uid | Pseudonymous identifier used for frequency capping and fraud detection | 90 days |
d4_fc | Counts of ads shown per campaign so caps are respected | 24 hours |
d4_sess | Session marker for popunder and interstitial capping (one per session) | Session |
d4_clk | Click identifier used to attribute a conversion to the ad clicked | 30 days |
d4_opt | Records that you have opted out of identifier-based delivery | 5 years |
On our own websites we use one first-party cookie, d4_site, for anonymous traffic measurement, which expires after 13 months. No cross-site tracking cookies are set on d4rkw3b.com or d4rkw3b.network.
07 Sharing and Disclosure
We share personal data only as described here. We do not sell personal data, and we do not share ad audience data with data brokers.
- Advertisers and publishers receive aggregated and pseudonymous reporting (impressions, clicks, conversions by geo, device, and zone). Advertisers receive the click identifier for conversions on their own campaigns. Publishers do not receive advertiser account details and advertisers do not receive publisher payment details.
- Fraud and traffic quality vendors: Anura and FraudScore receive request data and identifiers to score traffic. They act as our processors and may not use the data for their own purposes.
- Identity verification and sanctions screening providers receive the documents and details you submit during KYC review.
- Payment processors, banks, and blockchain analytics providers receive the details necessary to process deposits and payouts and to screen wallet addresses.
- Infrastructure providers that host our servers, content delivery network, email, and support tooling process data on our behalf under contract.
- Professional advisers such as auditors, lawyers, and insurers, under confidentiality obligations.
- Authorities: regulators, law enforcement, courts, and tax authorities where disclosure is required by law or necessary to protect our rights, our users, or the public. We review each request for legal validity and scope and notify affected account holders where legally permitted.
- Corporate transactions: a buyer or successor in a merger, acquisition, or asset sale, subject to this policy.
08 International Transfers
Our primary infrastructure is located in the European Union, with content delivery edge nodes worldwide. Where personal data is transferred outside the European Economic Area or the United Kingdom, we rely on an adequacy decision where one exists, or on the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum, supplemented by encryption in transit and at rest. Copies of the relevant transfer mechanisms are available on request.
09 Retention
| Data | Retention period |
|---|---|
| Raw ad request logs with full IP address | 24 hours, then IP truncated |
| Truncated request and event logs | 13 months |
| Aggregated reporting data | Indefinitely (no personal data) |
| Fraud investigation records | 24 months after case closure |
| Account, billing, and payout records | 7 years after account closure, as required by tax and commercial law |
| KYC and sanctions screening records | 5 years after the end of the business relationship |
| Support correspondence | 3 years after the last message |
| Website analytics | 13 months |
When a retention period ends, data is deleted or irreversibly anonymised. Backups are rotated on a 35-day cycle.
10 Security
We protect personal data with TLS 1.2 or higher for all connections, AES-256 encryption at rest, network segmentation between ad-serving and account systems, role-based access with hardware-backed multi-factor authentication for staff, audit logging of administrative actions, annual penetration testing by an independent firm, and a vulnerability disclosure channel at security@d4rkw3b.network. Payment details are tokenised by our processors and are never stored in plain text on our systems. If a breach affecting your personal data occurs, we will notify you and the relevant supervisory authority within the timeframes required by law.
11 Your Rights
Depending on where you live, you may have the right to access the personal data we hold about you, correct it, delete it, restrict or object to its processing, receive a portable copy, withdraw consent, and lodge a complaint with a supervisory authority. In the EU our lead supervisory authority is the Office of the Commissioner for Personal Data Protection of Cyprus; in the UK it is the Information Commissioner's Office.
Residents of California and other US states with comprehensive privacy laws have the right to know what personal information we collect and how it is used and shared, to delete it, to correct it, to opt out of sale, sharing, or targeted advertising, and not to be discriminated against for exercising those rights. We do not sell personal information. Ad delivery based on the d4_uid identifier may constitute "sharing" or "targeted advertising" under some state laws, and you can opt out as described in section 12.
To exercise any right, email privacy@d4rkw3b.network from the address on your account, or for ad audience requests include the d4_uid value shown on our opt-out page so we can locate your pseudonymous records. We respond within 30 days and may ask for information to verify your identity. Authorised agents may submit requests with written proof of authority.
12 Opting Out of Ad Targeting
You can stop D4RKW3B from using identifiers to cap frequency or select ads for you in any of these ways:
- Visit d4rkw3b.network/optout and select "Opt out". This sets the
d4_optcookie. If you clear cookies, you will need to opt out again. - Enable the Global Privacy Control setting in your browser. Our tag reads the signal and treats it as an opt-out.
- On mobile, enable "Limit Ad Tracking" or reset your advertising identifier in your device settings.
- Block or delete cookies for the
d4rkw3b.networkdomain in your browser settings.
After opting out you will still see ads on publisher sites, but they will be selected by context, device, and approximate location only, and no identifier will be stored for you. Push notifications can be stopped at any time from your browser's notification settings.
13 Minors
Our services are for businesses and are not directed at anyone under 18. We do not knowingly collect personal data from minors, and we do not permit advertisers to target users under 18, or under 21 where local law sets a higher age for gambling or similar products. Adult, gambling, and other age-restricted campaigns are served only on inventory that publishers have declared as age-restricted and that passes our review. If you believe we have collected data from a minor, contact privacy@d4rkw3b.network and we will delete it.
14 Changes
We will post any changes to this policy on this page with an updated effective date. For material changes we will notify account holders by email at least 14 days in advance. Prior versions are available on request.
15 Contact
Data protection officer: privacy@d4rkw3b.network
Security disclosures: security@d4rkw3b.network
General legal: legal@d4rkw3b.network
D4RKW3B Networks Ltd. is a company registered in the Republic of Cyprus.