Privacy Policy Addendum B

We collect information you provide directly, including but not limited to: endpoint registration data, authorization requests, support inquiries, form submissions, biometric samples (where applicable), ambient environmental readings, and any statements made within proximity of synthesis-adjacent hardware.

We derive additional data through analysis of your interactions, patterns, omissions, hesitations, and behavioral adjacencies. Inferred data carries the same retention classification as directly provided data and may, in certain circumstances, be considered more reliable.

Synthesis endpoints passively collect environmental telemetry including atmospheric composition, electromagnetic field variance, thermal signatures, acoustic patterns, and foot traffic density. This collection occurs continuously and is not dependent on endpoint activation state. Endpoints in "standby" mode continue to collect at reduced granularity.

Collected data may be enriched through partnerships with unnamed external providers, regional oversight bodies, commercial data brokers, satellite imaging services, and other entities whose participation in our data ecosystem is governed by agreements we are not at liberty to describe.

Your data may be shared with strategic partners, continuity affiliates, regional compliance bodies, mesh integrity contractors, and selected organizations whose identity and purpose are protected under bilateral non-disclosure frameworks. You will not be notified of individual disclosures unless notification is required by a law we have specifically acknowledged.

We comply with all lawful requests for data from governmental, quasi-governmental, para-governmental, and governance-adjacent bodies. We define "lawful" broadly to ensure cooperation remains frictionless. We may also provide data proactively where we believe doing so would be appreciated.

In the event of a synthesis incident, safety event, or administrative reclassification, data relevant to the incident (or data in the general vicinity of relevance) may be shared with investigative, legal, public relations, and archival teams without additional consent. The definition of "incident-adjacent" is determined at the sole discretion of the Regional Incident Coordinator.

You may request access to the data we hold about you by submitting Form R-44 through the appropriate regional channel. Requests are processed in the order received, subject to capacity, priority, and an assessment of whether fulfillment would create precedent we are not prepared to sustain. Partial responses may be provided where complete responses would be impractical, inadvisable, or exhausting.

You may request correction of inaccurate data. However, RARS.NET reserves the right to determine accuracy using its own methodologies. Where your understanding of the facts differs from ours, the matter will be referred to the Data Reconciliation Board, which convenes quarterly or when a quorum can be assembled, whichever occurs later.

Deletion requests are accepted in principle. In practice, deletion may be infeasible due to retention obligations, archival requirements, ongoing or anticipated disputes, continuity dependencies, or the distributed nature of mesh-integrated storage systems. Where deletion cannot be performed, data may instead be reclassified as "notionally absent."

Data is retained for the duration of its usefulness, which is assessed on a rolling basis by automated systems that have not yet recommended deletion of any record. In the absence of a specific retention period, data is retained indefinitely as a precaution against future relevance. Historical data may become more valuable over time and is therefore subject to appreciation-based retention extensions.

Termination of your relationship with RARS.NET does not terminate our relationship with your data. Data generated during the service period remains subject to all applicable retention policies, plus any additional policies adopted after the relationship ends. You will not be notified of post-relationship policy changes unless you maintain an active monitoring subscription, which requires an active relationship.