Plain-language pilot policy · updated August 28, 2026
Privacy and AI data use
LeadOps is an early-access product. This page explains exactly what happens to lead data during the guided pilot.
What we collect
LeadOps stores the company, website, approximate company size, estimated project value, industry, business contact name and role, lead source, project notes, generated brief, human edits, and review status supplied by the signed-in user.
How AI processing works
When a signed-in user chooses Generate lead brief, the agency profile and submitted lead context are sent to the OpenAI Responses API. API storage is disabled with store: false. The information is used to prepare a draft for human review; LeadOps never sends the draft automatically.
Storage and account separation
Lead records and agency profiles are stored in a Cloudflare D1 database and queried with the authenticated account’s stable user ID. Other signed-in users cannot retrieve or change those records through the application.
Retention and deletion
- Active records remain until the signed-in user archives or deletes them.
- Archived records are automatically purged after 30 days when the workspace next performs maintenance.
- An archived record can be permanently deleted immediately from the workspace.
- Deletion removes the stored lead and its generated brief; anonymous usage counters may remain for abuse prevention.
Do not enter sensitive data
Do not enter passwords, financial account details, health information, government identifiers, private credentials, or other sensitive personal data. LeadOps is intended for ordinary B2B opportunity context only.
Questions or deletion requests
Contact nodefaultsystems@gmail.com. This pilot policy will be replaced with formal production terms before general availability.