Privacy policy
Updated 2026-09-23
This policy explains the information processed through the site, accounts and API, and how to control optional analytics.
Service operator
MANINGO TECHNOLOGY LTD
Information processed
We process account email, authentication state, device and IP security data, orders, balance, API key metadata, usage and call logs, and support tickets. API requests can include inputs, files, parameters and tool calls; responses can contain model output. Avoid unnecessary sensitive data or secrets.
Purposes and recipients
Information supports accounts, API routing to third-party model providers, billing, payment verification, security, troubleshooting and support. Third-party model providers, cloud infrastructure, payment processors and email services may process necessary information for their roles. Meta and Google receive the advertising measurement data described below. Cross-border routing may involve other jurisdictions.
Payment and retention
Stripe handles checkout. We retain order identifiers, amount, currency, status and necessary callback records, but not full card details. Service, security and accounting records are kept as operationally or legally required; deletion may be limited by unsettled orders, investigations or legal retention duties.
Browser storage and optional analytics
Necessary browser storage supports login, sessions and privacy preferences. Optional site analytics are on by default: site attribution (the first referring site, landing page and campaign parameters), conversion events (such as opening the sign-in dialog, starting a sign-in or a top-up), external-link clicks and first-party website-performance measurement. For this the browser keeps a random analytics identifier and the first-visit source, and these events carry the event name, page path and that identifier. You can turn them off below at any time: this stops future optional sends and clears the related browser identifiers and source record while necessary account, billing and security records continue. A previous refusal and a browser Global Privacy Control signal are respected and keep site analytics off. Separately, every page loads Cloudflare Web Analytics, which counts anonymous visits, pages viewed, referring sites, countries and page-load timing. It sets no cookies, stores nothing on your device, does not identify you or track you across sites, and reports to us only in aggregate; it is not controlled by the optional analytics choice.
Your choices and contact
Use account settings or a support ticket to request access, correction or deletion of applicable personal information or ask about processing. Requests are verified and handled under applicable law and necessary service-record requirements. Signing in or creating an account requires ticking the box to accept the Terms of Service and this policy; when you continue, we record the terms and policy version you accepted, the time, the sign-in method and the interface language. Changes to this policy will be reflected in its update date.
Advertising measurement
Browser tags: the Google Ads tag runs on every page of the site, including account and payment pages, and Meta Pixel runs on public marketing pages such as the home, subscriptions, pricing and models pages. Both receive page views and limited campaign parameters and use advertising cookies. When a new account is created through email-code or Google sign-in, the Google Ads tag also reports that sign-up with your account email, which the tag hashes before sending. Advertising measurement is separate from optional site analytics. Measurement starts by default in all regions, and you can turn it off below at any time. Previous refusals and browser Global Privacy Control signals are respected. A default is never recorded as your explicit consent. Turning browser tags off stops future sends: the Google tag withdraws its consent at once and is no longer loaded, and pages with Meta Pixel move to a fresh page to leave loaded scripts. Ad click visits: when you arrive from a Google ad (the link carries a Google click identifier), we set a first-party cookie named kv_vid holding a random visitor ID for about 400 days, and record that arrival on our servers: the click identifier, the experiment variant in the link, the page path with only campaign parameters, the referring page without its query, your browser user agent and a shortened IP address (the first three parts of an IPv4 address or the first 48 bits of an IPv6 address). If you later create an account in the same browser, these records are linked to it. We use them only to count how often the same visitor clicks our ads, so we can measure ad experiments correctly; they are not sent to Meta or Google. This follows the advertising measurement setting: if you turn it off, or your browser sends a Global Privacy Control signal, nothing is recorded and the cookie is removed. When you turn it off we store adv_denied=1 in a cookie so our servers can respect the choice. Like other service records, they are kept as operationally or legally required (see Payment and retention). Server-side conversion measurement: sign-up, the first successful positively charged API use for new accounts, first subscription and top-up payments are reported only when a recorded advertising state allows measurement and the account has not opted out or recorded a withdrawal. Depending on the recipient, an allowed event can include a SHA-256 hash of the account email or account ID, the browser user agent and IP, the referring page and advertising click identifiers captured during sign-up or checkout. Payment events include the paid amount and currency; API activation does not report credit consumption as purchase revenue. The advertising state records a policy default separately from an explicit choice. Changing the advertising preference while signed in also saves that choice to the account; a saved withdrawal blocks pending server deliveries. You can also turn measurement off in account settings. Google ad personalization signals remain denied. Turning measurement off stops future sends but does not automatically delete information already sent; Meta’s and Google’s use of data follows their policies and account settings.