Privacy Policy

Last updated: 9 October 2026

This Privacy Policy explains how LLM7.io (“we”, “us”, “our”) collects and processes your personal data when you use our educational and research-oriented website and API, including dash.llm7.io. We operate from the United Kingdom and comply with the UK GDPR and, where applicable, the EU GDPR. Access to the API requires an API token issued via dash.llm7.io.

1. Controller contact

Controller: LLM7.io (operated by an individual) Email: support@llm7.io

2. Data we collect

Account & authentication

Tokens, subscriptions & usage (service operation)

Network & security

Referral Programme

We do not intentionally collect special category data. We do not sell personal data.

Optional product analytics

If you enable “Product analytics” in “Analytics preferences”, we use PostHog's EU service to understand page visits and selected feature actions across LLM7.io and dash.llm7.io. We send query-free page routes, enumerated action outcomes, model/language choices, and timing ranges. In the dashboard's Add balance flow we also collect opening sources, button actions, grouped amount-edit validation states, exact valid selected USD top-up amounts, displayed crypto bonus/credit amounts, quote and checkout outcomes, and dismissal reasons. Random, in-memory flow IDs link these actions within a modal opening; raw typed text is not sent. We do not observe activity inside hosted payment-provider pages or infer completed payments from a checkout handoff. Landing visitors are initially anonymous; after dashboard sign-in we associate consented activity with an opaque account ID and subscription tier. Shared first-party PostHog cookies support this attribution. We do not include email, passwords, API keys, prompt or generated text, referral codes, payment identifiers, exact account balance, or raw API errors in these events. Autocapture and session replay are disabled.

The necessary preference cookie llm7_analytics_consent remembers your product-analytics choice across both sites for 180 days. PostHog is not loaded before permission. You can withdraw PostHog permission using “Analytics preferences” in the footer on either site; this stops new PostHog collection but does not delete events already received. Contact support@llm7.io regarding deletion of previously collected account data.

Optional OpenAI ad measurement

The “Google & OpenAI ad measurement” choice enables OpenAI Pixel page views, model-catalogue expansion, Add balance and payment-provider choices, and successful checkout-start events. Our server also sends eligible new registrations, successful checkout starts, and verified paid top-ups after base credit is delivered. Checkboxes are initially selected, but measurement requires saving preferences; “No thanks” declines both. You can change these choices in the footer at any time.

For signed-in customers, we normalize and SHA-256 hash the email address and stable internal customer ID before sending them to OpenAI for conversion matching. We do not send raw email addresses or account IDs to OpenAI. Anonymous visitors have no email identifier. Where available and permitted by your ad-measurement choice, matching also uses your real client IP address and browser user agent captured when you authenticate or start checkout. Events may include checkout or paid top-up amounts in USD cents, a shared event ID to prevent double counting, the site origin, and OpenAI click/browser references. Promotional credits do not increase the paid value. No payment-card data, API tokens, prompts, or model responses are included.

With permission, the Pixel stores __oppref (up to 30 days) and __obref (up to 365 days) in first-party cookies. Revoking ad measurement stops new OpenAI events, clears these cookies, and requests cancellation of pending server deliveries for that consent receipt. A connection is needed to notify the server; failed requests are retried through the consent-revocation mechanism described below. Matching data for pending server delivery is removed after acceptance, suppression, or expiry. Data already sent or being transmitted cannot be recalled by changing browser preferences. See OpenAI’s privacy policy.

Optional Google Ads measurement

Google and OpenAI ad measurement share a choice in “Analytics preferences”. Existing product-analytics permission does not authorize advertising measurement. If enabled, we keep a Google ad click identifier (gclid, gbraid or wbraid) and click time in the first-party llm7_ads_attribution cookie for up to 30 days, shared by LLM7.io and dash.llm7.io. The llm7_ads_consent preference cookie stores your choice, time and random consent receipt for 180 days. Without permission, the Ads integration does not persist the identifier or send it to our payment API. The identifier may be held in the current page's memory while you decide.

When you start a top-up with Ads measurement enabled, the dashboard includes the consented click and receipt in the payment request. After the payment provider confirms payment and your paid balance credit succeeds, our server can send Google the click identifier, paid amount, currency, completion time, and a unique payment reference to count the purchase once. Promotional bonus credits do not increase this value. This integration does not send Google your email, account identifier, API keys, prompts, raw page URLs or card details. It does not use a Google Ads browser tag or record a purchase from a return-page URL alone.

You can withdraw Ads measurement using the same footer preferences. This stops new attribution immediately in the current page, removes the click cookie and requests cancellation of uploads for that consent receipt. If the request fails, the llm7_ads_revocations preference cookie holds up to 32 random receipt IDs for 180 days so later visits can retry. A connection is needed to notify the server; if cookies are blocked, a retry can only be retained while that page is open. Withdrawal cannot recall data already sent to Google. Contact support@llm7.io about previously collected data. Clearing cookies alone does not notify our server about a previous payment. See Google's privacy policy.

Google Analytics on the landing site

Google Analytics loads on the landing homepage independently of the PostHog choice, including before a choice is made and after “No thanks”. It uses Google's analytics service and cookies to measure visits and usage. The PostHog preference does not disable Google Analytics. Our explicit pageview events omit query strings and referrers. See Google's privacy policy for information about Google's data processing.

Consent copy, analytics retention, processor agreements and jurisdiction-specific requirements should be reviewed before this analytics configuration is deployed.

3. Purposes and legal bases

Legal basis: Contract (Art. 6(1)(b)).

Legal basis: Legitimate interests (Art. 6(1)(f)).

Legal basis: Legitimate interests (Art. 6(1)(f)) and, where applicable, Legal obligation (Art. 6(1)(c)).

Legal basis: Consent for browser storage and legitimate interests for the server-side programme record and fraud prevention. You can refuse the attribution prompt or clear the browser storage before registration; a recorded referral relationship cannot be reassigned to another referrer.

Legal basis: Consent. The choices are independent and can be withdrawn in the footer preferences.

Legal basis: Legal obligation (Art. 6(1)(c)).

Legal basis: Contract (Art. 6(1)(b)).

Legal basis: Contract (transactional/service emails) and Consent (optional updates), or Legitimate interests where permitted with a clear opt-out.

4. Storage, processors, and international transfers

We use Cloudflare for hosting, storage, networking, and security and act as the data controller while Cloudflare acts as our processor under its DPA and GDPR programme:

Data may be transferred internationally. We rely on appropriate safeguards (e.g., Standard Contractual Clauses and the UK Addendum) as implemented by Cloudflare.

5. Sharing

We share personal data only with:

6. Communications

We send:

We do not sell personal data.

7. Retention

8. Your rights

Depending on your location (UK/EEA), you may have rights to access, rectify, erase, restrict, portability, object (for legitimate interests), and to withdraw consent (for consent-based processing). To exercise your rights, contact support@llm7.io. You may lodge a complaint with your local authority. In the UK: ICO — https://ico.org.uk/.

9. Cookies and similar technologies

We use strictly necessary cookies/edge storage for authentication, security, and core operation. Google OAuth and Cloudflare may set cookies required for sign-in and security. The optional Ads integration uses the first-party attribution and preference cookies described above; it does not add a Google Ads browser tag or third-party advertising cookies. The existing Google Analytics behavior is described separately above.

Where you open a referral link, we ask for your consent before storing the referral code in local storage and a first-party .llm7.io cookie for 30 days. Refusing consent does not affect ordinary access to the Service, but we cannot apply the referral attribution. You can withdraw consent by clearing the relevant browser storage; this does not remove an attribution already recorded at account creation.

10. Automated decision-making

We use automated rate-limiting, fraud-prevention, and abuse-prevention systems. These systems may temporarily or permanently restrict requests, tokens, accounts, payment profiles, or API access where they detect suspected fraud, unauthorised payment activity, account farming, limit evasion, abuse, or security risks. We may also review these decisions manually where appropriate.

11. Children

The service is not directed to children. If you are under 13 (or the minimum age in your country), please do not use the service. If we learn we have collected data from a child, we will delete it.

12. Changes to this Policy

We may update this Policy. The latest version will be posted here with a new “Last updated” date. Material changes will be communicated reasonably (e.g., site notice). Continued use after updates means you accept the revised Policy.

13. Related documents

14. Contact

Questions or requests: support@llm7.io