Privacy
This Privacy Policy explains how LP1 collects, uses, stores, and shares information for the LP1 marketing site, the Page Owner app, hosted Pages, Page Assets, Form Submissions, AI features, and External AI Client connections.
Launch draft effective July 28, 2026
This launch-stage legal page is provided for product transparency and is not legal advice. It should be reviewed by counsel before LP1 relies on it as a final legal document.
LP1 is built for Page Owners who create, edit, preview, publish, and collect responses from landing Pages. It also covers Visitors who view hosted Pages or submit forms on Pages published through LP1.
Page Owners are responsible for the Page HTML, Page Assets, copy, forms, notices, and visitor-facing promises they publish. Visitors should also review any privacy terms supplied by the Page Owner on the hosted Page.
When a Page Owner signs up or signs in, LP1 processes account information such as name, email address, authentication records, session data, and product usage needed to operate the app.
LP1 stores Page HTML, Drafts, Page Metadata, Page settings, Page Assets, Versions, Preview URLs, Published URLs, Publish Jobs, and editor activity needed to create, preview, publish, troubleshoot, and support Pages.
When LP1 hosts a published Page, it may process Visitor request data such as IP address, user agent, hostname, route, timestamps, referrer, and basic security or delivery metadata. This data is used to serve the Page, protect the service, diagnose issues, and understand product reliability.
Page Assets uploaded by a Page Owner may be publicly accessible when referenced by a published Page. Page Owners should avoid uploading sensitive assets unless they intend those files to be served publicly.
Published Pages can record first-party Marketing Events such as Page views, managed Form impressions, managed Form conversions, and named custom conversions. Those records can include a pseudonymous first-party Visitor identifier, the exact Page and Page Version, hostname, route, referrer, campaign parameters, event metadata, and the time of the event.
When a Page Owner runs an Experiment, LP1 uses first-party cookies to keep a Visitor assigned to the same Experiment Arm. LP1 uses Marketing Events to calculate Page Set metrics, identify statistically supported outliers after a minimum sample, enforce stop-loss rules, and keep an audit record of automation recommendations and actions.
If a Page Owner enables platform-managed Form capture, LP1 stores accepted Form Submissions for that Page. A Form Submission can include the Submission Payload entered by the Visitor and Submission Attribution such as hostname, path, campaign parameters, referrer, timestamps, and validation or spam-protection metadata.
LP1 stores Form Submissions for the Page Owner to view, export, or delete. LP1 does not decide what a Page Owner asks Visitors to submit, so Page Owners must only collect information they have a lawful basis to collect and must provide any required visitor notice.
LP1 uses AI features to generate and edit Page HTML from Page Owner instructions, Page context, uploaded or referenced content, and Chat history. Those requests may be processed by third-party model providers configured through the Page Owner's saved AI settings.
Page Owners may approve External AI Clients through External Client Connections. Those clients use capability-scoped Owner API Tokens to manage Pages and marketing operations on the Page Owner's behalf. Page access, publishing, marketing data, Experiment and Destination changes, automation runs, and automated publishing can be granted separately. LP1 records External Client Activities for account control, support, and abuse prevention.
A Page Owner can configure a public HTTPS Destination to receive signed Marketing Events. LP1 encrypts the Destination signing secret, creates a separate Delivery record after an event is accepted, and stores attempt status, response status, retry timing, and error information for owner review and replay.
Destination operators receive the event and attribution data selected by the Page Owner's LP1 configuration. Page Owners are responsible for choosing lawful recipients, protecting signing secrets, and ensuring their external systems handle Visitor data appropriately.
LP1 runs on Cloudflare services, including Workers and related hosting infrastructure, to serve the marketing site, app, Page runtime, assets, and custom-domain traffic. Cloudflare may process request, security, and network metadata as a service provider.
The marketing site can use Cloudflare Web Analytics when enabled in LP1 configuration. The current launch configuration keeps the analytics token empty unless LP1 turns that beacon on.
LP1 uses information to provide the service, authenticate Page Owners, operate hosted Pages, measure Page Sets, run Experiments, identify outliers, enforce automation guardrails, deliver signed webhooks, capture and show Form Submissions, support AI editing, issue and revoke Owner API Tokens, prevent abuse, debug errors, improve reliability, and communicate service-related updates.
LP1 does not sell personal information. LP1 may share information with infrastructure, authentication, analytics, AI model, security, and support providers when needed to operate the service.
LP1 keeps account, Page, Page Asset, Version, Marketing Event, Experiment, Automation Run, Destination Delivery, activity, and Form Submission records for as long as needed to provide the service, preserve owner-controlled history, comply with obligations, resolve disputes, and prevent abuse. Page Owners can delete Pages and Form Submissions through the product as those controls are available.
For privacy questions, requests, or launch-stage corrections, contact support@lp1.ai.
Questions about this page can be sent to support@lp1.ai .