This policy is structured into three parts: Part A covers the privacy of individuals who visit our corporate website. Part B — the most critical section for enterprise due diligence — covers our product data practices, Zero-PII architecture, and the ethical framework governing our global clickstream panel. Part C details global compliance frameworks and your legal rights.
Lord Data operates at the intersection of behavioral intelligence and institutional finance. Our clients — hedge funds, quantitative research firms, AI laboratories, and enterprise data platforms — require not only exceptional data quality, but also unimpeachable data ethics. We believe these goals are perfectly compatible, and this policy is the technical and legal expression of that belief.
This Privacy & Data Ethics Policy applies to all Lord Data services, websites, APIs, and data products. It is reviewed and updated on a quarterly basis by our Data Protection Officer (DPO) and Legal team to reflect evolving regulations and best practices. The most current version is always available at lorddata.com/privacy.
Website Visitor Privacy
This section governs how Lord Data collects, processes, and protects the personal data of individuals who visit lorddata.com, interact with our web-based lead forms, subscribe to communications, or engage with our sales and support teams.
A.1 — Information We Collect from Website Visitors
We collect information through two primary channels: data you provide to us directly, and data that is automatically generated as you interact with our website. We are committed to collecting only the minimum information necessary to fulfill the stated purposes.
Directly Provided Information
When you complete a "Request Sample", "Book a Demo", or "Contact Us" form on our website, you provide us with:
Automatically Collected Technical Data
Our web infrastructure automatically records certain technical signals as part of standard server and analytics operations. This includes your IP address (retained for a maximum of 30 days before truncation to mask the last octet), browser type and version, operating system, referring URL, pages viewed, and time-on-page metrics. This data is used exclusively for site security, performance optimization, and aggregate traffic analysis. It is never used for individual profiling or sold to third parties.
A.2 — How We Use Website Visitor Data
We process website visitor data under the lawful bases of legitimate business interest and, where required, explicit consent. We use your information strictly for the following purposes and no others:
To deliver the customized data samples, proof-of-concept datasets, or live demonstrations you have specifically requested. This is the primary purpose of our lead forms.
To follow up with relevant information about our data products, pricing, API capabilities, and contractual terms. You can opt out of these communications at any time.
To inform existing clients and opted-in prospects about material changes to our data feeds, schema updates, coverage expansions, and compliance certifications.
To comply with applicable law, respond to lawful requests from public authorities, enforce our Terms of Service, and protect against fraudulent or malicious use of our systems.
We do not use your contact information for programmatic ad targeting, sale to data brokers, or any purpose outside the scope explicitly described above. Lord Data is an enterprise B2B company — your contact details are used to build a business relationship with you, not to monetize your personal identity.
A.3 — Data Sharing & Third-Party Service Providers
Lord Data does not sell, rent, or trade the personal contact information of website visitors or clients to any third party under any circumstances. We share data with a limited set of trusted service providers who are essential to our business operations, under strict contractual obligations that prohibit them from using your data for any purpose other than providing services to us.
These providers include: enterprise CRM and sales engagement platforms (e.g., for managing client relationships), cloud infrastructure providers (for hosting and data delivery), secure transactional email providers (for delivering data samples and correspondence), and legal and compliance advisors (under attorney-client privilege). All such providers are bound by Data Processing Agreements (DPAs) that impose GDPR-equivalent protections regardless of their jurisdiction.
We do not use social media tracking pixels or third-party behavioral advertising scripts on our website. Any analytics we employ are configured in privacy-preserving modes with IP anonymization enabled.
Product & Panel Data Privacy
This is the most critical section of this document for institutional due diligence teams. It describes, with technical precision, how Lord Data collects, anonymizes, aggregates, and delivers the behavioral clickstream data that constitutes our core intelligence product. Our architecture is built on a single non-negotiable principle: the individuals whose aggregate behavior generates our market signals must never be identifiable.
Lord Data's product data contains no personally identifiable information. Our clients — hedge funds, AI laboratories, and enterprise data platforms — receive behavioral market signals, not individual user profiles. The distinction is not semantic; it is enforced at the architectural level, before any data enters our processing pipeline.
B.1 — Zero-PII Architecture: Privacy-by-Design
Lord Data implements a Privacy-by-Design framework as defined by the Information and Privacy Commissioner of Ontario and adopted by the GDPR under Article 25. This is not a compliance checkbox — it is the core engineering philosophy of our data collection infrastructure.
Our collection endpoints are designed with hardware-level and software-level controls that automatically reject, drop, or cryptographically obfuscate any field that could constitute personal data before that data is written to any storage system. This occurs in real-time, at the point of collection, with no human in the loop and no intermediary storage of raw personal data.
Our SDK and browser agent maintain a regularly updated blocklist of known PII fields (email inputs, phone fields, name fields, government ID fields). These fields are dropped client-side before transmission.
Data collection is automatically suspended on pages classified as sensitive: banking portals, payment checkout flows, healthcare record systems, legal document platforms, and government services.
Raw IP addresses are never stored. Upon receipt, IPs are immediately subjected to a one-way cryptographic hash (SHA-256 with a rotating daily salt) and then truncated to remove host-level identifiability.
Geographic data is resolved from the hashed IP to city-level or country-level only. Precise GPS coordinates, ZIP codes, or sub-city granularity are never collected or stored in any form.
Our Zero-PII architecture has been independently reviewed by third-party privacy engineering consultants and found to be consistent with the technical requirements of GDPR Article 25 (Data Protection by Design and by Default) and the NIST Privacy Framework. Documentation of these reviews is available to enterprise clients under NDA upon request.
B.2 — Anonymous Behavioral Signals We Process
To generate market intelligence of institutional quality, we process the following categories of anonymous behavioral signals from our consented panel. All signals described below have been stripped of personal identifiers prior to any processing or storage:
Domain visits (e.g., amazon.com), subpage paths (e.g., /dp/B09X7), and referrer URLs. Subpage paths are truncated to remove query parameters that could contain personal session tokens, user IDs, or email addresses.
UTC-stamped event timestamps, enabling analysis of session duration, journey velocity (time between page transitions), and intra-day behavioral patterns at aggregate market level. Timestamps are stored at second-level precision; millisecond-level data is discarded to prevent fingerprinting via timing attacks.
General device category (desktop, mobile, tablet), operating system family (Windows, macOS, iOS, Android), and browser category (Chrome-based, Firefox, Safari). Specific version numbers and hardware configurations that could enable device fingerprinting are not collected. User Agent strings are parsed into categorical signals only and the raw string is discarded.
Search queries submitted to major search engines and e-commerce platforms, aggregated across the panel and analyzed for intent categorization (e.g., "purchase intent", "research intent", "price comparison"). Raw search queries are processed through a Natural Language Processing (NLP) pipeline that detects and removes queries containing apparent personal information (proper names in query context, email addresses, etc.) before aggregation.
Page-level signals indicating progression through commercial funnels: product page views, cart interaction events, checkout page visits, and order confirmation page visits. We do not collect transaction values, payment information, order IDs, product details beyond category classification, or any information entered into payment or shipping forms. Payment processor pages are classified as secure zones and collection is suspended.
B.3 — What We Categorically Do Not Collect
For the avoidance of any doubt, Lord Data's technology is engineered to never collect the following categories of information. These prohibitions are enforced at the collection layer and are not merely policy statements — they are technical constraints built into our data pipeline:
B.4 — Panelist Consent & Ethical Data Sourcing
The foundation of Lord Data's data supply chain is explicit, informed, and freely given consent. Every individual whose anonymized behavioral signals contribute to our panel has actively opted in through a transparent consent mechanism embedded in a participating application or browser extension. This is not passive implied consent or pre-checked boxes — it is affirmative opt-in.
Our consent collection meets or exceeds the GDPR standard of consent under Article 7: it is freely given (not bundled as a condition of service), specific (users are told exactly what behavioral signals will be collected), informed (plain-language explanations are required), and unambiguous (requiring a clear affirmative action). Users may withdraw consent at any time through in-application settings, triggering immediate cessation of data collection.
Sourcing Partner Requirements
All software partners and application developers who participate in our panel program are required to meet strict contractual standards before integration. These requirements include: displaying a clear and accessible privacy disclosure describing Lord Data's data collection; implementing a functional and prominent opt-out mechanism; obtaining consent before data transmission begins; and providing Lord Data with evidence of their own regulatory compliance (GDPR, CCPA, or equivalent). Partners who fail to maintain these standards are removed from the program.
Anonymization at the Point of Consent
Crucially, panelists consent to the collection of anonymous behavioral signals, not the collection of their personal data. The software running on their device performs the anonymization process locally — stripping identifying fields before transmission. Lord Data's servers never receive, and therefore cannot process, the personal identity of any panelist. This architectural choice is intentional: it makes it technically impossible for Lord Data to de-anonymize its own panel, not merely contractually prohibited.
B.5 — Data Anonymization & Aggregation Pipeline
Below is a high-level representation of our end-to-end data processing pipeline, illustrating the sequential anonymization steps that occur before any data enters our analytical systems:
Behavioral signals are captured on the user's device by our lightweight SDK. The SDK's field blocklist runs in real-time, discarding any detected PII before any network transmission occurs. Secure page detection suspends collection entirely on sensitive domains.
Pre-filtered signals are transmitted to Lord Data ingestion endpoints over TLS 1.3 with certificate pinning. All data in transit is encrypted. The transmitted payload contains no personal identifiers by design.
Upon receipt, the source IP address is immediately hashed with SHA-256 and a rotating 24-hour salt, then truncated. The hash is used for intra-session event grouping only and is discarded after session completion. The IP is resolved to city/country level, and the resolution result is retained; the IP itself is not.
Search query fields and URL parameters are processed through an NLP classifier trained to detect PII patterns (email formats, name-like tokens, phone number patterns) and redact or discard any flagged queries before they are written to the data warehouse.
Sanitized signals are aggregated into statistical market models. Individual event-level data is retained for a maximum of 90 days before aggregation; aggregate models are retained for up to 50+ months. Client-facing data products are delivered via secure S3 buckets or authenticated API endpoints with row-level access controls.
Regulatory Compliance & Your Rights
Lord Data is committed to full compliance with the world's most stringent data protection regulations. We do not adopt a "lowest common denominator" approach; instead, we apply the highest applicable standard globally across all our operations. The following frameworks govern our practices.
C.1 — GDPR Compliance (European Union)
Lord Data's product data practices are designed to be compatible with the General Data Protection Regulation (EU) 2016/679 (GDPR). Our primary compliance position is that our product clickstream data, having been anonymized at the point of collection, does not constitute "personal data" as defined under GDPR Article 4(1), and therefore GDPR's individual rights framework does not apply to it. This position is consistent with Recital 26 of the GDPR, which states that the principles of data protection "should therefore not apply to anonymous information."
For our corporate website operations, Lord Data acts as a Data Controller under GDPR. We have appointed a Data Protection Officer (DPO) accessible at [email protected]. For client data processing under contractual agreements, we act as a Data Processor and execute GDPR-compliant Data Processing Agreements (DPAs) with all enterprise clients in the European Economic Area.
Lawful Bases for Processing (Corporate Data)
We process corporate website visitor data under the following GDPR lawful bases: Article 6(1)(b) — processing necessary for the performance of a contract (delivering requested data samples); Article 6(1)(f) — legitimate interests (sales communication, site security, analytics); and Article 6(1)(a) — consent, where required for marketing communications.
Data Protection Impact Assessments
Lord Data conducts Data Protection Impact Assessments (DPIAs) as required by GDPR Article 35 for any new processing activity that may result in a high risk to individuals' rights and freedoms. DPIA records are maintained and made available to supervisory authorities upon request.
C.2 — CCPA Compliance (California)
Lord Data's practices comply with the California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA). California residents who interact with our corporate website have the following rights, which we honor unconditionally.
With respect to our product data: Because our clickstream data is thoroughly anonymized and aggregated, it does not meet the CCPA definition of "personal information" (information that identifies, relates to, or could reasonably be linked to a particular consumer or household). Therefore, individual opt-out and deletion rights under CCPA do not apply to our aggregate behavioral data products — not because we choose to exempt ourselves, but because the underlying technical architecture makes re-identification impossible.
Lord Data does not sell personal information. We are a B2B data company that sells anonymized market intelligence to institutional clients. Our business model does not involve selling or sharing consumer personal information for cross-context behavioral advertising.
C.3 — Your Rights & How to Exercise Them
The following rights apply to personal data we hold about you in our capacity as a corporate website operator and B2B service provider (i.e., your contact information, form submissions, and communication history). These rights do not extend to our anonymized product data, as that data is not personal data and cannot be linked to you.
Request a copy of all personal data we hold about you, including the categories of data, the purposes of processing, and recipients. We will respond within 30 days (GDPR) or 45 days (CCPA).
Request deletion of your personal data from our CRM, marketing lists, and communication records. We will process deletion requests within 30 days, subject to retention obligations imposed by applicable law.
Request correction of inaccurate personal data we hold about you. Contact us with the specific data that requires correction and the accurate information.
Receive your personal data in a structured, commonly used, machine-readable format (JSON or CSV), and transmit it to another controller where technically feasible.
Object to processing of your personal data for direct marketing purposes at any time. You may also object to processing based on legitimate interests, though we may demonstrate compelling legitimate grounds that override your objection.
Unsubscribe from all marketing communications at any time via the unsubscribe link in any of our emails, or by contacting [email protected]. Opt-out requests are processed within 10 business days.
Note regarding product data: Because our clickstream product data is rigorously anonymized and cannot be linked to any individual — including you — we are unable to process subject access, deletion, or portability requests with respect to it. We do not know who you are within our aggregate datasets, and this is by architectural design. If you were previously a panelist and wish to stop contributing behavioral data, please do so through the opt-out mechanism in the relevant application on your device.
C.4 — Security & Data Retention
Technical & Organizational Security Measures
Lord Data implements enterprise-grade security controls across all systems that handle data. Our security program includes: end-to-end encryption in transit (TLS 1.3 minimum) and at rest (AES-256); role-based access control with least-privilege principles enforced across all data warehouses; multi-factor authentication required for all internal system access; continuous intrusion detection and anomaly monitoring; regular third-party penetration testing; and a documented incident response plan with defined SLAs for breach notification to regulatory authorities (72 hours under GDPR Article 33).
Data Retention Schedule
C.5 — International Data Transfers
Lord Data operates globally and may transfer personal data (corporate contact information of leads and clients) across international borders as part of our normal business operations. All such transfers are conducted under appropriate legal safeguards in accordance with GDPR Chapter V.
Where we transfer data from the European Economic Area (EEA) to third countries, we rely on Standard Contractual Clauses (SCCs) as approved by the European Commission under Decision 2021/914, supplemented by transfer impact assessments where required. All data transfer agreements include data processing addenda that impose GDPR-equivalent protections on receiving parties, regardless of their domestic legal framework.
Our product clickstream data — being anonymized and therefore not constituting personal data — is not subject to international transfer restrictions under GDPR or equivalent regimes. However, we apply equivalent technical security standards to its storage and delivery regardless of geography.
Contact Our Data Protection Officer
If you have questions about this Privacy & Data Ethics Policy, wish to exercise any of your privacy rights, require a Data Processing Agreement (DPA) for enterprise procurement, or need documentation of our security and compliance posture for institutional due diligence, please contact our Data Protection Officer:
We aim to acknowledge all privacy inquiries within 48 business hours and provide substantive responses within 30 days.
For postal correspondence, DPA requests, and regulatory authority inquiries.
Hedge funds, asset managers, and enterprise procurement teams conducting privacy due diligence may request our full compliance documentation package, including: independent privacy engineering audit reports, DPA templates, SOC 2 Type II reports, DPIA summaries, and data flow diagrams. Please email [email protected] with subject line "Enterprise Privacy Due Diligence Request" and we will respond within 2 business days.