01
Who is responsible
Lerp (lerp.gallery) is operated by an independent developer based in Hong Kong, responsible for the personal data described here. Contact support@lerp.gallery with privacy questions.
02
Accounts and sign-in
We store your email, account creation date, passkey public keys and credential identifiers, hashed session tokens, sign-in challenge hashes, session expiry, and limited device information for your session list. We do not receive your passkey’s private key or biometric data. Essential HttpOnly cookies keep you signed in; localStorage may hold legacy browser saves until your next sign-in, plus recently viewed sites and interface preferences. Recently viewed shows at most 24 site identities and visit times from the last 30 days, on this browser when signed out or privately in your account when signed in. Older visits are discarded when you next use history. Clear it any time from Saved; it never appears on shared boards.
03
Saved references and connected agents
We store boards you save to an account or share, their items and sharing identifiers. Anyone with a shared link can read its board. API keys are stored as hashes with a prefix, label, scope, expiry and last use. OAuth grants, registered client details and hashed tokens live in our token store. MCP call records keep account, credential, tool, time and usage information to enforce quotas and show account activity.
04
Payments
Our payment processor handles checkout, subscriptions and the billing portal. We keep customer and subscription identifiers, plan status, billing periods and webhook event identifiers. We do not store full card details. The payment processor holds payment and invoice information under its own privacy policy.
05
Messages, launch list and delivery logs
We keep what you submit: contact details, suggestions, claims, removal requests and their decisions. Joining the launch list stores your email and signup time for a launch announcement, not unrelated marketing. Email delivery logs include the recipient, subject, plain text and HTML body, link, expiry and provider delivery identifier or failure. An owner can view these logs, including short-lived sign-in codes. Ask by email to leave the launch list.
06
Security and analytics
Our hosting and infrastructure provider runs the service, database, object storage, token storage, email delivery and owner-only sign-in. A bot check protects public forms from abuse. Rate limits use short-lived hashes of network address, action and time window; raw addresses are not stored in that table. The provider may process request addresses, browser information and operational logs for security. Cookie-free visit counts measure aggregate traffic and performance without advertising cookies or a tracking pixel in email.
07
Analytics
We also count how the library is used, so we can see which references, searches and plans help. This is cookieless: we do not set an analytics cookie, and a signed-out visit does not get a profile. We honour Do Not Track and Global Privacy Control. We do not sell this information or use it for advertising. We record page views, control clicks, heatmap positions, clicks with no response, rapid repeated clicks, browser performance and errors (error type, a shortened message with emails, keys and query text removed, and code locations, not entered text), and a few actions: a search (how long the query was, where it ran and how many results came back, not the words), a filter, opening a site, a save, choosing a layout, playing a clip (which capture size, not the frames), choosing Pro, copying a prompt, pack, code or connection detail, and account changes such as creating or revoking a key, disconnecting an app, opening the billing portal, signing out other sessions, removing a passkey or deleting the account. A signed-in visit is tied only to an internal account number, never to an email address or a name. Addresses, sign-in codes and keys are removed before anything is sent. A network address may be used briefly to tell visits apart and estimate region; we do not store it in our database. Connected agents are counted the same way: when a client first connects, which tool it calls, the plan, how many results, how long it took and whether it failed — not the request text or the key. A completed purchase is recorded from the payment notification so we know a subscription started. We may ask signed-in members one optional question about whether a reference helped.
08
Reference content and AI
We store public-site recordings, stills, extracted design tokens, measurements and editorial notes. AI model providers process selected public-site material for classification and prompt generation. Suggestions and credit claims may be analysed for triage. Do not submit secrets or sensitive personal information in these fields. We do not sell personal data or use sign-in emails as model prompts.
09
Retention, deletion and access
You can delete an account from Account, which cancels billing and removes account records and connected access. Delivery logs, support requests, security logs and necessary accounting records may remain separately; email support@lerp.gallery to request access, correction or deletion. We retain opt-out domains to avoid recapturing removed sites. Expired rate-limit windows are cleaned after a day when forms are used. Account deletion does not erase every separately retained record immediately.
10
Your choices and questions
Email support@lerp.gallery for privacy requests or launch-list removal. Depending on where you live, you may have rights to access, correct, export, erase or restrict processing and complain to a regulator. Our providers may process data internationally.
A person, not a maze. support@lerp.gallery