Trust & Compliance — how ForexBrokerLead protects your business.

Every EU/EEA lead we deliver has documented opt-in consent for third-party broker contact. This means the prospect explicitly agreed to be contacted by a third-party broker about trading-related services — not just to receive marketing from the original source. Each lead record carries a consent timestamp, the source URL where consent was captured, the prospect's IP address at the time of consent, and a double opt-in confirmation where required by the source country's regulation. The consent metadata is included in the CSV we deliver, so your compliance team can verify each record independently.

A full Data Processing Agreement (DPA) is available at /data-processing-agreement.html. The DPA documents the controller/processor roles, sub-processor arrangements, data-subject rights handling, breach-notification timelines, cross-border transfer mechanisms, and audit obligations. We sign DPAs with enterprise customers on request and provide the standard template for self-service procurement teams who need it pre-signed.

Our data retention policy is GDPR-aligned: unused leads are retained in active inventory for a maximum of 30 days before being permanently purged, and active inventory is never held for more than 90 days from initial consent. We do not maintain "archives" of aged leads to resell later — once a lead passes its freshness window, it is purged from our systems. This is also why we can guarantee that no lead you receive from us is older than 30 days.

The right to erasure is honoured: any lead (data subject) can request deletion of their personal data at any time by emailing privacy@forexbrokerlead.com. We process erasure requests within 30 days, propagate the deletion across our active inventory and backups, and notify any broker who received that lead within the previous 30 days so they can also purge it from their system. This is a closed-loop erasure workflow, not just a "we deleted it from our database" answer.

Our web server returns 9 security headers on every response: Strict-Transport-Security (HSTS) with preload, Content-Security-Policy with restrictive default-src, X-Frame-Options: DENY, X-Content-Type-Options: nosniff, Referrer-Policy: strict-origin-when-cross-origin, Cross-Origin-Opener-Policy: same-origin, Cross-Origin-Resource-Policy: same-origin, Permissions-Policy with geolocation/camera/microphone disabled, and X-DNS-Prefetch-Control: off. These headers protect against clickjacking, MIME-sniffing attacks, CSRF-based information leakage, and cross-origin data exfiltration.

Our SSL certificate is a valid Domain Validation (DV) certificate issued by Sectigo, with HSTS preload enabled and a one-year renewable rotation cycle. All HTTP traffic is permanently redirected to HTTPS at the server level — there is no plaintext path to any ForexBrokerLead endpoint. We are working toward an Organization Validation (OV) certificate upgrade for 2027 to further strengthen identity verification on the certificate itself.

All form submissions on ForexBrokerLead are protected by four layered defenses: CSRF tokens validated server-side per session, a honeypot field invisible to humans but populated by bots, Google reCAPTCHA v2 (loaded via the official API on every form page), and IP-based rate-limiting that throttles repeat submissions from the same source. These defenses defeat automated spam, credential-stuffing, and brute-force lead-impersonation attacks.

Secrets are stored OUTSIDE the webroot. The Telegram bot token, the reCAPTCHA secret key, the CSRF HMAC key, and other operational secrets live in a /private/ directory above the public webroot with chmod 0600 permissions. They are never committed to version control, never appear in client-side JavaScript, and are loaded by PHP through a path traversal above public_html/. All operational logs — php-error.log, auto-ping.log, cache-manager.log, seo-health.log, indexnow-submission.log — are written to /private/logs/ (also above webroot) so they can never be downloaded by an attacker even if the public directory is fully exposed.

Every paid order is backed by our 95% deliverability guarantee: if more than 5% of leads in your order are invalid (bounced email, disconnected phone, wrong country, duplicate, or non-consenting), we replace the invalid leads free within 48 hours of you reporting them — no forms, no friction, no questions asked. Simply email your account manager with the list of invalid lead IDs and we send replacements.

If our deliverability falls below 95% across the entire order (not just individual leads), you receive a full refund for the shortfall — proportional to the gap below the 95% threshold. This is a contract-level commitment, not a marketing slogan. The full policy, including the definition of "invalid," the reporting window, the replacement workflow, and the refund calculation methodology, is documented at /refund-policy.html.

Invalid leads must be reported within 7 days of delivery to qualify for free replacement. This window exists because lead data decays over time — phone numbers disconnect, email addresses are abandoned, prospects revoke consent. Reporting within 7 days ensures the issue is attributable to our verification process, not to natural data decay, and keeps the guarantee fair to both parties.