CiteLens privacy policy (draft)
Effective date: To be set at publication.
Last updated: 17 November 2026 (Asia/Jerusalem).
Operator: Born Bots. The formal legal entity name is TBD.
Contact: [email protected]
1. Who we are
Born Bots operates CiteLens, including the ChatGPT plugin, the website at https://citelens.pages.dev, and the CiteLens Monitor workspace at https://citelens-workspace.bornbots.workers.dev. Until a legal entity is formed, the operator of record is Born Bots, reachable at [email protected].
2. What CiteLens does
When you ask for an audit, CiteLens makes read-only HTTP requests to the public URL you provide and to related public discovery files (for example robots.txt, llms.txt, and sitemaps). It parses the responses to produce a citation-readiness report. It does not log in to the target site, does not fill forms, and does not change the site.
3. Categories of personal data
We collect only what we need to run an audit, operate the service, and respond to you.
Information you give us
- The URL (and any other audit options) you submit.
- If you email us: your email address and the content of the message.
- If you join the workspace waitlist on our website: your email address, the fact that you ticked the consent box, the date and time you signed up, and which site the form was on. We do not store your IP address, browser details, or cookies with a waitlist entry.
- If you join the waitlist on the Monitor workspace: your email address, an optional URL, the date and time you signed up, and the source “workspace”. To rate-limit sign-ups we also store a hashed form of your IP address and a timestamp. We do not store the raw IP address with the waitlist entry.
- If you create a CiteLens Monitor account: an optional email, passkey public keys and credential IDs, sessions, saved URLs, audit history, and plan or subscription status. Details are in section 10. Account sign-up is not required for a one-off public audit.
Information we collect automatically
- Technical logs: timestamp, requested host or URL path as needed to debug, HTTP status, duration, and a coarse client identifier used for rate limiting (such as IP address). We do not log full HTML bodies, cookies from the target site, or passwords.
- Standard server and security logs from our infrastructure provider (for example request metadata needed to operate a host and reject abusive traffic).
- Bot checks from Cloudflare Turnstile on the website's free-audit and waitlist forms and the Monitor workspace's sign-up, sign-in and waitlist. Turnstile runs in your browser and sends Cloudflare signals about the browser and connection to tell people from automated traffic. We receive only a pass or fail result, which we check once and do not store. Cloudflare's Turnstile privacy addendum is at https://www.cloudflare.com/turnstile-privacy-policy/.
- Website visit statistics from Cloudflare Web Analytics: pages viewed, referrer, country, browser and device type, and page-load performance. It does not use cookies or local storage and does not track you across sites. We use it only to count visits and see which pages help people. Cloudflare's own policy is at https://www.cloudflare.com/web-analytics/.
Information we do not collect
We do not ask for payment-card data, government identifiers, passwords for third-party sites, or health information. We never receive payment-card details. Once payments are enabled, Polar will collect payment details on its own checkout pages (see section 10). Do not put secrets or credentials in a URL you submit. We do not use the plugin as a surveillance tool, and we do not profile third-party sites beyond the audit you requested.
If a page you ask us to fetch happens to contain personal data that is already public, we process that content only to produce the audit result.
4. Purposes of use
- To perform the audit you requested and return results.
- To prevent abuse (rate limits, SSRF protections, security investigation).
- To debug failures (timeouts, blocked destinations, WAF or captcha responses).
- To respond to support requests.
- To email waitlist members about the launch of the CiteLens web workspace. We do not use waitlist emails for anything else, and we do not add them to other mailing lists.
- To operate a CiteLens Monitor account if you create one: keep you signed in, save the URLs you choose, run audits, and show what changed.
- To process payments through Polar once payments are enabled. Until then, a plan choice only records that you expressed interest.
- To meet legal obligations if we are required to do so.
We do not use audit contents to train our own models. We do not sell personal data.
5. Categories of recipients
- Service providers that host or operate the product (compute, DNS, email delivery, and error or uptime monitoring, once those vendors are in production). They process data only to provide their service to us.
- Cloudflare, which hosts this website and the Monitor workspace, and is our processor for that hosting. The website stores waitlist entries in Cloudflare Workers KV, a store in our own Cloudflare account. The workspace stores accounts and audit history in Cloudflare D1, a database in our own Cloudflare account, and runs on Cloudflare Workers. Only Born Bots can read those stores.
- Polar, once payments are enabled. Polar will be our payment processor and merchant of record for CiteLens Monitor. We never receive your card details. Polar's privacy policy is at https://polar.sh/legal/privacy-policy. Until payments are enabled, choosing a plan only records your interest in our database.
- OpenAI, if you use CiteLens inside ChatGPT or Codex. Your conversation with ChatGPT is also processed by OpenAI under OpenAI’s own terms and privacy policy. We do not control ChatGPT’s logging.
- Authorities, if a lawful request requires it.
We do not sell, rent, or trade personal data, and we do not share it with third parties for their own marketing.
6. Retention
- Unauthenticated audit results: a short-lived result id, intended for follow-up tools in the same session, is kept for about 24 hours, then deleted.
- Technical logs (host, status, duration, rate-limit identifiers): kept only as long as needed for security and debugging, targeted at 30 days or less unless an investigation requires a longer hold.
- Website waitlist entries: kept until the workspace launches and we have sent the launch email, or until you ask us to remove you, whichever comes first. If the workspace does not launch, we will delete the list. Workspace waitlist entries are described in section 10.
- Support email: kept as long as needed to resolve the request and maintain a basic support record.
- CiteLens Monitor account data: kept until you delete the account, as described in section 10.
Fetched HTML is processed to produce the result and is not kept as a permanent copy of the target site.
7. User controls
- You choose which URL is audited. You may stop using the plugin or website at any time.
- To leave the waitlist, reply to any waitlist email or write to [email protected] from the address you signed up with, and we will delete your entry.
- If you have a CiteLens Monitor account, you can delete it yourself at
/app/account. That removes the account and the data listed in section 10. To leave the workspace waitlist, or to ask a question, correct information, or request deletion of support mail, email [email protected]. We will need enough detail to find the record (for example the URL, approximate time, and the email you used). - You may have additional rights under the law that applies to you (access, deletion, objection, and similar). Because our legal entity and primary establishment are TBD, we will state the formal process and any required local contacts before publication. In the meantime, write to [email protected] and we will handle the request in good faith.
We do not currently use non-essential marketing cookies or sell or share personal data as those terms are used in U.S. state privacy laws. If that changes, this policy will be updated first.
8. Children
CiteLens is not directed at children under 13, and we do not knowingly collect personal data from them.
9. International processing
Infrastructure may be located outside your country. Until the legal entity and hosting region are confirmed, assume processing may occur in the United States and other countries where our providers operate. We will update this section when those details are fixed.
10. CiteLens Monitor workspace
CiteLens Monitor is the signed-in workspace at https://citelens-workspace.bornbots.workers.dev. It lets invited accounts save public URLs, re-run audits, and see what changed. Payments are not live yet. This section describes what the workspace itself stores.
Where it is stored
Workspace data is stored in Cloudflare D1, a database in our Cloudflare account, and processed on Cloudflare Workers. Cloudflare is our processor for this hosting. Only Born Bots can read the database.
What we store and why
- Account. A unique account id, the email you choose to give us (you can create an account without an email), whether the account has been invited to early access, and when the account was created. We use this to operate your account and to gate early access.
- Passkeys. The passkey credential ID, the public key, a signature counter, optional authenticator transports, and when the passkey was created and last used. We use these to sign you in. We never receive biometric data, fingerprints, face data, or the passkey private key. Those stay on your device or password manager.
- Sessions. When you sign in we set a session cookie and store a hashed copy of the session token, a CSRF token, and an expiry time in the database. On HTTPS the cookie is named
__Host-citelens_sessionand is markedSecure; on HTTP it is namedcitelens_session. It isHttpOnlyandSameSite=Lax, and it lasts 14 days. We use it to keep you signed in and to protect form submissions. A new sign-in replaces previous sessions. After 14 days the session can no longer be used. - Guest form cookie. If you are not signed in, we set a
citelens_csrfcookie for 24 hours so waitlist and other guest forms can be protected against cross-site requests. It isSameSite=LaxandSecureon HTTPS. It is notHttpOnly. We do not store this value in the database. - Pending URL cookie. If you arrive from a free audit with a URL to save, we may set a
citelens_pending_urlcookie for 24 hours (HttpOnly,SameSite=Lax, andSecureon HTTPS). We use it only to offer to save that public URL after you sign in. We do not store this cookie value in the database unless you later save the URL to your account. - Saved URLs. The public URLs you choose to monitor, and when they were added and last checked. We use these to run audits for you.
- Audit runs and diffs. For each run we store when it started and finished, its status, score, grade, a short summary, the engine version, the final URL after redirects, and the structured check results we need to show a diff. We use these to show history and what changed. As with the rest of CiteLens, we fetch the audited URL and related public discovery files from our servers. We process the fetched page to produce the result and do not keep a permanent copy of the full HTML.
- Changes feed. When a score or check result changes, we store a change event (old and new scores and grades, which checks changed, and whether you have opened it) so you can see what changed.
- Invites and waitlist. Early access is an invite flag on your account, set by us after the account exists. If you join the workspace waitlist, we store your email, an optional URL, the sign-up time, and the source “workspace”. To rate-limit those sign-ups we also store a hashed form of your IP address and a timestamp. We do not store the raw IP address in the database.
- Plan and payment interest. Until payments are live, choosing a plan only records a stubbed interest record (which plan and when) in our database. No card details are collected. Once payments are enabled, we will store your plan, subscription status, period end, and Polar customer and subscription ids, so we can apply the correct plan. Polar will process the payment and act as merchant of record. We never receive card details. At checkout we will send Polar your account id, the plan, your account email if you have one, and your IP address (so tax and country can be determined). Polar's privacy policy is at https://polar.sh/legal/privacy-policy.
- Audit-run rate-limit records. When you run an audit from the workspace, we store a timestamp so we can enforce a per-user rate limit.
Retention
- Sessions are kept until they expire (14 days). The session cookie is also set to last 14 days. Signing in again replaces previous sessions. Sessions are also removed when you delete your account.
- WebAuthn sign-in challenges used during sign-up and sign-in are kept for 5 minutes.
- Waitlist anti-abuse attempt records (the hashed IP address and timestamp stored to rate-limit workspace waitlist sign-ups) are kept for 24 hours.
- Audit-run rate-limit records (the timestamps stored when you run an audit from the workspace) are kept for 1 hour.
- Expired sessions, challenges, waitlist anti-abuse attempts, and audit-run rate-limit records are deleted on the next write.
- Account data — your email if you gave one, passkeys, saved URLs, audit runs and diffs, changes, invite status, stubbed payment interest, and, once payments are enabled, plan and Polar subscription status — is kept until you delete your account.
- Workspace waitlist entries are kept until you ask us to remove you. Email [email protected] from the address you signed up with. Deleting a Monitor account removes the waitlist entry for the same email, if there is one.
- Self-service deletion is at
/app/accounton the workspace. You type DELETE to confirm. This removes the user record, passkeys, sessions, saved URLs, audit runs, changes, audit-run rate-limit records, stubbed payment interest, plan or subscription status, and the waitlist entry for the same email, if there is one. It cannot be undone. Once payments are live, an active paid subscription must be cancelled first. - Webhook delivery ids from Polar (a unique message id and the time we received it, with no email or other personal data) are kept so we can ignore duplicate payment events. They are not removed when you delete your account, because they contain no personal data.
11. Changes
We will post updates to this policy with a new “last updated” date. Material changes will be highlighted on the policy page.
12. Contact
Born Bots
Email: [email protected]
Legal entity, postal address, and data-protection contact: TBD