No analytics
The website does not include analytics, trackers, pixels, cookies, chat widgets, embedded schedulers, or third-party forms.
Privacy
Public-beta privacy notice.
This page describes the current public website, the first-party working-session form, and the product data topics quoted before onboarding.
Effective: 2026-08-08
Public-beta boundary: product terms are quoted before onboarding
Form fields
The working-session form asks for name, work email, company, revenue-team size, current system, primary problem, and optional notes.
Attribution and operations
The form also records source page, referrer, UTM parameters, IP address, user agent, validation status, and timestamps for routing and abuse prevention.
Product data
CRM records, prospect lists, outreach content, retention, deletion, export, subprocessors, and model-use terms are scoped before onboarding.
Current website behavior
Current website behavior
This public-beta website has no signup, login, payment flow, analytics script, tracking pixel, chat widget, heatmap, session recording, or third-party scheduler. Static pages load local CSS, local JavaScript for navigation and attribution fields, and a local social image.
Working-session collection
Working-session collection
When a visitor submits the form, Pursenda receives name, work email, company, revenue-team size, current system, primary problem, optional notes, source page, referrer, UTM source, UTM medium, UTM campaign, UTM term, UTM content, remote IP address, user agent, and received time.
Purpose and handling
Purpose and handling
The information is used to review the request, prevent spam, route the inquiry, send an internal notification, send a best-effort prospect confirmation email, and maintain a JSONL lead record and a separate JSONL conversion record.
Conversion record boundary
Conversion record boundary
The conversion record stores event name, lead ID, timestamp, source page, referrer, and UTM values. It does not store the visitor's name, email, company, problem description, optional notes, account evidence, CRM content, or prospect records.
Storage and recipients
Storage and recipients
Lead and conversion records are written to first-party server files used by Digital Disconnections to operate Pursenda. Form email notifications are sent through the server's local sendmail path to the internal team address and to the submitting prospect as confirmation.
Product data scope
Product data scope
Before customer onboarding, the customer scope names product data categories, sources, purposes, retention, deletion, export, subprocessors, DPA availability, correction route, suppression/opt-out route, and whether any data trains models.
Contact path
Contact path
Privacy questions can use the contact link on this page. Do not send customer records, prospect lists, credentials, or sensitive deal details through the public form.
Public-beta boundary
This page states current website behavior.
Commercial contracts and customer data processing should use counsel-reviewed language tied to the actual product scope.