Who handles the data
Lateral Edge Ltd operates Domain Signals and is the contact for public-site, account and service privacy questions. Customer instructions may make Lateral Edge a processor for protected workspace content.
Legal LEG-003
Privacy notice
Privacy notice sets out the current invite-beta operating position for Data subject, customer. These operating terms explain the invite-beta service in direct language. They should be read with the product's technical and evidence boundaries, not as a substitute for them.
Bounded, non-exploitative Authorised external assessment.
Bounded evidence. Explicit responsibility. No hidden inference.
The useful answer
Privacy notice sets out the current invite-beta operating position for Data subject, customer.
Privacy notice sets out the current invite-beta operating position for Data subject, customer. Privacy notice sets out the current invite-beta operating position for Data subject, customer. These operating terms explain the invite-beta service in direct language. They should be read with the product's technical and evidence boundaries, not as a substitute for them.
Route-specific context
The decision this page is designed to support
- Who this governs
- Data subject, customer
- Operating effect
- Understand personal-data processing and rights. Privacy notice sets out the current invite-beta operating position for Data subject, customer.
- Evidence and precedence
- The public site does not send assessed domains, IPs, findings, report content or personal free text to product analytics. Evidence basis: Current route contract and invite-beta operating configuration.
01
02
03
Current operating document
Privacy notice
- Version
- Invite-beta v1.0
- Effective
- 24 August 2026
Data collected
The service records account identity, workspace membership, permission, submitted domains, bounded observations, reports, operations, billing references, support requests and security audit events.
Purposes and lawful basis
Data is used to provide the requested service, secure tenant access, meet contractual and legal duties, prevent misuse, support customers and improve governed capability. Public marketing analytics never include assessed targets or report evidence.
Sharing and transfers
Data is limited to the subprocessors and public authorities necessary for hosting, identity, billing, email, operations or legal compliance. Current providers and relevant transfer safeguards are described in the Trust Centre.
Retention
Retention follows the active plan, the data-retention policy, security needs and any legal hold. Short-lived raw collector payloads are separated from normalised evidence and removed on the shorter schedule.
Your rights
Applicable rights may include access, correction, erasure, restriction, objection, portability and complaint. Use the electronic privacy-complaint route so the request can be acknowledged and tracked.
This is the current founder-adopted invite-beta operating version. It does not claim external legal certification.
A deliberate path
From permission to retained evidence
- 01
Read who privacy notice governs and which version is in force.
- 02
Check the operating effect against your intended use: understand personal-data processing and rights.
- 03
Use the contact route before relying on an unclear term; the product interface does not silently broaden the document.
Evidence before assertion
What the product can support
The applicable record is the version displayed when an action is taken. Material changes are dated, retained and presented before they govern a future use of the service. The public site does not send assessed domains, IPs, findings, report content or personal free text to product analytics.
Operating position
Privacy notice sets out the current invite-beta operating position for Data subject, customer.
Route contract and current invite-beta configurationDirect answers
Questions a careful reader should ask
What does Privacy notice establish?
Privacy notice sets out the current invite-beta operating position for Data subject, customer. It establishes only what the governed evidence supports.
What does it not establish?
It does not prove complete organisational security, exploitability, breach likelihood or the absence of unobserved weaknesses.
How can I verify the conclusion?
Use the linked evidence or capability record to inspect source, observation time, target, responsibility and the condition required for closure.