Legal
Privacy policy
LandingPagePrompts is a free prompt library. There is no account, no advertising and no data sales. This page describes the small amount of data the site does handle — including the product analytics it runs — in plain language, and what you can do about it.
The short version
- No account, no login, no email required to read or copy anything on this site.
- No advertising, no tracking pixels, no data sales, no cross-site tracking. The only analytics on the site is PostHog, used to understand which prompts are useful. It is not used for advertising, and it is never shared with an ad network.
- You can turn analytics off in one click — see Opting out. The site works identically with it off.
- One analytics cookie is set (
ph_…_posthog) plus onelocalStoragekey for your own votes. Both are described in Local storage and cookies. - Session recording and autocapture of form inputs are disabled. Nothing you type is recorded.
- The only personal data ever collected is what you type into the prompt-request form, and only if you choose to submit it.
What the server records
Like any website, the server sees the request you make. The site runs on Cloudflare Workers, and it records aggregate, non-identifying product events — never a profile of an individual. This is separate from the PostHog analytics described below: these events are counted server-side, carry no cookie and no visitor identifier, and are the numbers published on the stats page.
- Product events. A page view, a prompt copy, a search query, a vote, a verification request. Each event records the event kind, the prompt slug it relates to, and a coarse country code supplied by Cloudflare's edge. These are written to Cloudflare Analytics Engine and mirrored into a Cloudflare D1 database, and they are used only to show counts on the stats page and to decide which prompts to re-verify.
- Vote and copy tallies. Counts live in a per-prompt Durable Object. The tally is stored against the prompt, not against you — there is no record of which visitor voted which way.
- IP addresses, transiently. Your IP is used in memory to enforce rate limits on the write endpoints (so one client cannot flood the vote or verify endpoints) and is passed to Cloudflare Turnstile when the request form is enabled. It is not written to our database alongside your activity.
- Standard edge logs. Cloudflare, as the hosting provider, processes request metadata (IP, user agent, timestamp, path) as part of operating the CDN and Workers platform. That processing is governed by Cloudflare's own privacy policy.
If you submit the prompt-request form
The form asks for your name, your email address and a reference or description of the design you want a prompt for. If you submit it:
- Those three fields are stored in the site's D1 database, together with the submission timestamp and the country code the request came from.
- A separate analytics event records only the domain part of your email address (for example
example.com) so we can see roughly how many submissions come from agencies, studios or individuals. The full address is not written to analytics. - The submission is used to reply to you and to decide which prompts to write next. It is not added to a mailing list, not sold, and not shared with anyone other than the processors listed below.
- The form is protected by Cloudflare Turnstile, which means your IP address and the challenge token are sent to Cloudflare for verification.
To have a submission deleted, email privacy@landingpageprompts.com from the address you used and it will be removed.
Product analytics (PostHog)
The site runs PostHog to understand which prompts people actually use — which categories get opened, which get copied, and where the library loses people. It is product analytics, not advertising: there is no ad network, no data broker, no cross-site profile, and no sale or sharing of what it collects.
What PostHog receives when you load a page:
- A pageview and pageleave for each route you visit, with the referrer and your screen size.
- Interaction events — a prompt opened, a prompt copied, a filter or search used, a vote cast. These are the events the product decisions are made from.
- Your IP address, which PostHog uses to derive coarse location (country level) and then discards; it is not stored on the event. The analytics is served through a first-party
/ingestproxy on this domain, so the request is same-origin and is not visible to an ad blocker or a third-party network observer. - A pseudonymous identifier kept in a first-party cookie and in
localStorage, so a returning visit is recognised as the same anonymous visitor. It is not linked to a name, an email address or an account, because the site has none. - Structured log lines for the same interactions, so a copy that fails on one device can be traced. These carry the same fields as the events above — a prompt slug, a category, a model — and never the text of a search or a form.
- JavaScript errors — unhandled exceptions and unhandled promise rejections are reported so broken pages get noticed. The report contains the error message and stack, the page URL and the same pseudonymous identifier. It does not contain anything you typed.
Worth stating explicitly, because it is the thing people assume is collected: the text you type into the search box is not sent to PostHog. Only the number of results is recorded. The search itself runs on this site's own infrastructure.
What is deliberately switched off: session recording (no replay of your screen), autocapture of form inputs (nothing you type is captured), and any collection of the prompt-request form's contents. The form's fields are never sent to analytics — only the fact that a submission happened.
Opting out of analytics
You can turn analytics off, and the site behaves identically with it off. Three ways:
- From the browser console. Run
posthog.opt_out_capturing()on any page. The choice is stored on your device and no further events are sent.posthog.opt_in_capturing()reverses it. This audience is developers, so the console is the honest answer rather than a modal. - Block it technically. Blocking
/ingest/*, or clearing theph_…_posthogcookie and theph_…localStorage keys, removes it entirely. - Do Not Track. Where the browser sends DNT, PostHog can be configured to honour it — see PostHog's DNT documentation.
Because the analytics is first-party and pseudonymous, there is no name or email attached to it — but if you want your events erased anyway, email privacy@landingpageprompts.com and they will be.
Local storage and cookies
The library stores landingpageprompts:votes in your browser's localStorage. It holds the votes you have cast on prompts, so that reloading the page does not let you vote twice and so you can change or remove your vote later. It never leaves your device except as the anonymous toggle instruction sent to the vote endpoint, and clearing your browser storage erases it.
PostHog adds its own first-party entries: a cookie named ph_<project>_posthog (the pseudonymous visitor id) and matching localStorage keys. These are first-party, set by this domain, and used only for the analytics described above.
No sessionStorage is used. There are no advertising cookies, no third-party cookies and nothing that identifies you across other sites.
Who else is involved
These are the only third parties the site talks to, and what each of them sees:
- Cloudflare — hosting, CDN, D1 database, KV, R2 object storage, Durable Objects, Queues, Workflows, Analytics Engine, Workers AI (used only to turn a semantic-search query into an embedding), Vectorize, Turnstile and Browser Rendering. Cloudflare processes requests on our behalf.
- PostHog — product analytics, as described in Product analytics. Events are sent to PostHog Cloud, either directly or through the first-party
/ingestproxy on this domain. PostHog is a data processor for this site and does not receive the contents of any form. - Google Fonts — the pages load Inter and Instrument Serif from
fonts.googleapis.com. That request discloses your IP address and user agent to Google. If you would rather not make it, block the request; the site falls back to your system fonts. - AI model providers — used by the build pipeline, off the public site, to generate the prompts and the demo pages. No visitor data is sent to them at request time.
There is no advertising network, no social embed, no session recorder and no cross-site tracker on any page.
How long it is kept
Aggregate server-side product events and prompt tallies are kept indefinitely, because they are the evidence behind the library's published numbers and they contain nothing that identifies a person. PostHog event data is retained on PostHog Cloud under the retention period configured for the project. Prompt-request submissions are kept until they have been answered and the prompt they inspired has been written, or until you ask for deletion — whichever comes first.
Your rights
Depending on where you live, you may have the right to access, correct, export or delete personal data held about you, to object to processing, and to lodge a complaint with a supervisory authority. Because the site holds so little, most of these are easy to satisfy:
- Access, correction, deletion, portability: email privacy@landingpageprompts.com and state what you want. Requests are answered within 30 days.
- Objection: the only processing that touches personal data is the request form, and you can simply not submit it. Everything else on the site works without it.
- No sale or sharing: personal information is never sold or shared for cross-context behavioural advertising, so there is nothing to opt out of.
Children
This site is a developer and designer tool and is not directed at children. No personal data is knowingly collected from anyone under 13 (or the equivalent minimum age where you live). If you believe a child has submitted the request form, email privacy@landingpageprompts.com and it will be deleted.
Security
The site is served over HTTPS only. The public write endpoints are rate limited and validated server-side, and the request form is protected by Turnstile. Secrets are held as Cloudflare Worker secrets and are never bundled into the client. No system is perfect; if you find a problem, please report it to hello@landingpageprompts.com rather than disclosing it publicly first.
Changes to this policy
If this policy changes in a way that affects what is collected, the date at the top of the page changes with it. Material changes will be noted on the how it works page as well.
Contact
Privacy questions and data requests: privacy@landingpageprompts.com
Anything else: hello@landingpageprompts.com