Private people stay out of the public site.
pokedex.life has two different surfaces: a public project homepage and an access-controlled personal workspace. This notice explains what each surface processes, where information can go, and which safeguards prevent private relationship material from becoming public content.
Public homepage and analytics
The public homepage does not require an account and the application does not set its private-access cookie there. Vercel hosts the site and processes ordinary request and security logs. Vercel Web Analytics runs only on the public homepage and reports aggregated page-view information such as page path, referrer, approximate geography, browser, operating system, and device type without third-party analytics cookies or a personally identifiable visitor profile.
Vercel documents its Web Analytics privacy design and data points in its official privacy and compliance guide. pokedex.life does not configure custom analytics events, advertising trackers, session replay, or analytics on protected relationship routes. Automated scanners may request the public page, robots.txt, sitemap.xml, or llms.txt like any other visitor.
Google Fonts supplies the Departure Mono typeface used for labels and card data, so the browser requests a stylesheet and font files from Google when that font is available. Those requests can include ordinary connection metadata such as an IP address and user agent. pokedex.life does not send relationship fields or private-route content with the font request.
Private access and cookies
The protected workspace has no public signup flow. An access token is checked on the server, and a successful check creates a Secure, HttpOnly, SameSite=Strict cookie containing a one-way digest rather than the submitted token. The cookie lasts up to 30 days unless it is cleared earlier. Protected responses are private, no-store, noindex, and no-referrer by default.
Social profile and relationship data
Authorized Farcaster lookups can retrieve a public handle, display name, avatar, bio, public posts, follower counts, verified public handles, and a location the account chose to publish. The private classifier derives Trust readings, behavior stats, types, a tagline, and evidence notes from that material. Classified records may be cached in server memory for one hour and may be persisted in the project's private Supabase database when it is configured.
X and Instagram are not connected from the public homepage. The private workspace can use operator-provided exports or snapshots for private review, but those source graphs, relationship labels, and recommendations are not placed in public pages, metadata, robots guidance, or the sitemap. Social-platform exports remain subject to the source platform's own terms and privacy controls.
AI and service providers
Neynar supplies the Farcaster profile and post data requested by an authorized lookup. Anthropic receives the selected public profile evidence and up to 50 recent public casts to generate a structured card. Supabase can store private classified records and relationship data, while Vercel runs the application. These providers process information under their own service terms; pokedex.life does not sell private relationship data.
Private notes, drafts, and retention
The workspace may store a future-self profile, private people lists, trust overrides, and touchpoint metadata in access-controlled server storage. A tending-message draft stays in the operator's browser localStorage, and completing the ritual records only a private touchpoint rather than the message body. Browser drafts remain until cleared; other private records remain until the operator removes them or the relevant service's retention policy applies.
Payments and contact
pokedex.life has no active public paid plan, checkout, free trial, guarantee, or quote process. No payment-card details are collected by this site. Privacy questions can use the public contact route, but private access tokens, relationship notes, social exports, and another person's sensitive information should never be placed in a public message.