Privacy and AI data use

What we collect

LeadOps stores the company, website, approximate company size, estimated project value, industry, business contact name and role, lead source, project notes, public website research snapshot, generated brief, human edits, and review status supplied or confirmed by the signed-in user.

The public pilot application stores the applicant’s name, work email, agency, website, team and lead-volume ranges, current process, desired outcome, selected starting plan, internal review status, and owner notes.

Public website research

When a signed-in user explicitly chooses Research website, LeadOps reads the submitted public website homepage and, when available, one relevant same-site page. Requests are bounded, private or local addresses are rejected, and source URLs remain visible for human verification. Public page text may be sent to the OpenAI Responses API with storage disabled to extract a concise, source-linked snapshot.

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. Pilot applications are stored in a separate owner-only sales table.

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. Account-linked usage events may remain for abuse prevention; these are not anonymous.
• Application abuse checks use a daily hash of the visitor IP and request timestamps. The application does not store the raw IP in its usage table; hosting security logs are separate.
• Pilot applications are retained while the commercial conversation is active or as needed for ordinary business records; applicants may request deletion by email.

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.