Data handling
The service handles the data needed to assemble disclosures, issue records, support reprints, and deliver the resulting documents. It is not designed as a general-purpose account platform or long-term publishing workspace.
Data handling in this service is operational: it exists to make disclosure issuance possible.
What the service stores
- Draft input during the drafting process.
- Issued disclosure data needed for record continuity and reprints.
- Delivery-related information such as email where needed for fulfillment.
What the service is not doing
The service does not create long-term user profiles as the core product model, and it does not treat email as a persistent account identity. Email is primarily a fulfillment and communication channel.
Why this matters
Understanding data handling helps users interpret the service correctly. The system is designed to create and deliver a formal record, not to become the user's permanent collaboration environment.
Related pages
See Retention for how data availability differs by state, and Privacy policy for the public policy statement.