LeadUptimeLEAD JOURNEY MONITORING
PRIVACY & SECURITY
This operational overview describes the current private pilot. Monitoring checks use made-up values to verify configured form journeys.
Updated
WHAT LEADUPTIME CHECKS
The website uses bounded first-party, cookie-free page-view and active-session events. It stores the path, time, coarse browser and device family, referrer host, language, campaign labels, a masked network, and keyed pseudonymous daily values for at most 90 days. Global Privacy Control and Do Not Track disable this measurement.
A pilot application submits your work email, a public website and the form plugin. We keep these details encrypted for up to 30 days and notify our team by email. We use the request to review setup and contact you; it activates neither monitoring nor a paid plan. Separate first-party, cookie-free form events contain no contact fields and are retained for at most 30 days. Global Privacy Control and Do Not Track disable this measurement. An application counts as received only after durable storage; qualification and the first passing check are recorded separately. Encrypted backup copies rotate over a further seven-day window. Mailbox correspondence has its own retention lifecycle.
The app stores account, workspace, site, monitor, run, incident, alert, report, audit, and security records, plus uploaded profile media. Access is role-based and privileged accounts require MFA. Shared HTML reports use unlisted links: anyone with a report link can read it until expiry or revocation, without a recipient login.
Monitoring checks use made-up values and do not upload genuine WordPress form submissions. Evidence is redacted and expires under the active plan. Optional site-local recovery is off by default; if an administrator enables it, supported genuine submissions are kept briefly as encrypted records in the WordPress database. The site administrator controls recovery keys and cleanup; those contents are not uploaded to LeadUptime. The WordPress plugin connects outbound and cannot receive remote commands from LeadUptime.
Little Guardian is an AI assistant, not a person. AI replies can be wrong; contact hello@leaduptime.com for confirmation. When a visitor sends a question, the current message and up to five recent question-and-answer pairs are sent server-side to the OpenAI API using GPT-6 Luna. LeadUptime does not persist the chat history. Provider retention depends on the API account configuration; this is not a promise of zero retention or EU-only processing. Visitors must not enter personal or confidential information.
Little Guardian is a fictional brand mascot. Some illustrations were generated with AI, including the enquiry-inspector illustration. These illustrations are not photographs of real staff or customer events.
For access, correction, deletion, objection, restriction, portability, or privacy questions, email hello@leaduptime.com. The founders are Vlad-Andrei Cristea and Laila Holzmann. The legal provider details and complete privacy notice still need to be finalized before customer launch; this operational overview does not replace them.
LeadUptime does not claim SOC 2, ISO 27001, HIPAA, an uptime SLA, inbox-arrival guarantees, or server-side conversion monitoring.
FAQ
No advertising cookies or third-party advertising trackers are used on the public website.
Monitoring checks use made-up values and do not upload genuine WordPress form submissions.
No chat history is persisted by the LeadUptime website. Submitted messages are processed by OpenAI to produce the answer.
PRIVATE PILOT
