01Public website measurement.
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.
02LeadUptime accounts and operations.
The app stores account, workspace, site, monitor, run, incident, alert, report, audit, and security records, plus uploaded profile media. Mail Studio stores connected mailbox messages, drafts, addresses, and delivery outcomes encrypted at rest. Access is role-based and privileged accounts require MFA.
03Synthetic checks and evidence.
Monitoring checks use made-up values and do not upload genuine WordPress form submissions. Evidence is redacted and expires under the active plan. The WordPress plugin connects outbound and cannot receive remote commands from LeadUptime.
04Little Guardian support bot.
The homepage clearly labels the assistant as automated. When a visitor sends a question, the current message and up to six recent question-and-answer pairs are sent server-side to the DeepSeek API for a reply and may be processed in China. LeadUptime does not persist the chat history. Visitors must not enter personal or confidential information.
05Contact and rights.
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.
06Claims LeadUptime does not make.
LeadUptime does not claim SOC 2, ISO 27001, HIPAA, an uptime SLA, inbox-arrival guarantees, or server-side conversion monitoring.