Privacy

screens.guide sets no cookie and writes nothing to your browser's local or session storage. Its pages load scripts and styles from screens.guide only.

Usage events

The pages send the events below to PostHog, which stores them in its EU region (https://eu.i.posthog.com). They are sent only from screens.guide itself, in PostHog's cookieless mode: PostHog's servers compute a hash in place of a visitor id, and nothing is stored in your browser. No event carries text you type.

EventSent whenCarries
$pageviewa page loadsthe page's address
explorer_changeda picker in a device page's explorer changesthe device id, screen, orientation and runtime build
compare_changedthe comparison's device list changesthe device ids
playground_useda playground's first input on a page; for "this device", when it has read the screenthe playground's name; for "this device", the id of the closest measured device
data_link_clickeda click on a link to a data file, llms.txt or a Markdown copythe link's path

With each event, PostHog's library adds the page's address and the referring page, the browser's user agent, name and version, the operating system, the device type, the screen and window sizes, the language and the time zone. PostHog's servers receive each request's IP address; PostHog's privacy policy covers what they keep. The site's code that sends the events is src/lib/analytics.ts in the source.

Events from the server

The server that answers the MCP server's address /mcp, the pages and the data files sends the events below to the same PostHog project, only for requests to screens.guide itself. It sends them from Cloudflare, so PostHog receives Cloudflare's address and not yours, and each event asks PostHog to skip its location lookup. Each event has a new random id, so PostHog cannot link two requests, and stores no person profile. No event carries your IP address, the frames you send to check_layout or other text you send; a path is recorded only for a page or file that exists. The code is worker/analytics.ts.

EventSent whenCarries
mcp_requesteach message to the MCP server at /mcp, and each request its rate limit refusesthe method; for initialize, the client's name and version and the protocol version; for a tool call, the tool, the device ids, screen, orientation, rotation and runtime it names, the number of frames, and whether it failed; a JSON-RPC error code; which rate limit refused it; the HTTP status; the request's User-Agent and Accept headers
page_servedeach request for a page, as HTML or as Markdownthe page's path, when the page exists; whether the answer was HTML or Markdown; the HTTP status; the request's User-Agent and Accept headers
file_servedeach request for a data file, llms.txt, llms-full.txt, a Markdown copy by its own address, or a file of the skillthe file's path, when the file exists; the HTTP status; the request's User-Agent and Accept headers

To keep the MCP server's limit of 1,000 requests a UTC day per address, a Cloudflare Durable Object named by the SHA-256 hash of your IP address stores the current UTC date and the number of requests from that address on it. The first request on a new date replaces both. The address itself is not stored. Cloudflare's rate limiting counts the limit of 100 a minute, keyed by the address. The code is worker/ratelimit.ts.

Hosting

Cloudflare serves the site and keeps its own logs of the requests it serves, under Cloudflare's privacy policy.