Legal
Privacy policy
Last updated 8 September 2026
What we collect
We collect only what the Service needs to run, bill correctly, and stay secure.
- Account data. Your email address, and any name or profile details you give our identity provider when you sign up. We never receive or store your password.
- Connection tokens. We store only a one-way hash of each token, plus the name you gave it, when it was created and when it was last used. The token itself is shown to you once and is not recoverable from our systems.
- Usage records. For each call your agent makes we record the operation name, the time, whether it succeeded, the amount charged, which token made it, how many rows came back, what serving the call cost us, and whether it was answered from cache. We do not store the arguments you send — a row count is how much came back, never what was in it.
- Cached answers. Data we buy from a source to answer a call is kept for up to 24 hours so the same question is not bought twice, and that cache is shared across customers. It is stored under a one-way digest of the operation and its arguments, never the arguments themselves, and it holds only what the source returned about the public web — never anything you supplied.
- Payment data. Payments are handled by our payment processor. We receive the amount, currency, status and a customer reference. We never see or store your full card number.
- Technical logs. Server logs record the request method, path, response status and timing, together with network metadata such as an IP address. Authorization headers and cookies are redacted before anything is written.
- Product analytics. On the website and dashboard we record which pages you open, which controls you use, and the outcome of the actions you take — signing up, creating a token, adding funds. Alongside each event we record your browser and device type, the referring page, and an approximate location derived from your IP address. On the API we record the operation, timing and outcome already described under usage records. Once you sign in, these are tied to your account.
- Session recordings. We record how pages are used — pointer movement, clicks, scrolling and navigation — so we can see where the interface fails people. Everything you type is masked before it leaves your browser, and the panel that shows a newly created token is excluded from recording entirely, so a recording never contains a credential.
- Query content in transit. The search terms, domains, company names and other inputs your agent sends are passed to the data suppliers needed to answer them, and the answers are passed back to you. This content is processed to serve your request; it is not written to our usage records.
How we use it
- To provide the Service. Authenticating your token, routing your calls, returning results, and keeping your balance correct.
- To bill you. Metering successful calls, applying credit, issuing receipts, and refunding calls that failed.
- To keep the Service secure. Detecting abuse, rate limiting, investigating a leaked token, and preventing fraud.
- To support you. Answering your questions and diagnosing a fault you report.
- To measure, analyse and improve the Service. We analyse how the Service is used — which operations are called, which fail, how long they take, where people get stuck — to fix defects, tune performance, price fairly, decide what to build next, and improve the quality of the tools and skills we ship. We may produce aggregated and de-identified statistics and derived insights from this analysis, and may use and publish those statistics, including in benchmarks and product materials.
- To meet legal obligations. Keeping tax and accounting records, and responding to lawful requests.
Aggregated and de-identified data is not personal data: it cannot reasonably be used to identify you or your business, and we do not re-identify it. We do not sell personal data, we do not share it with advertisers, and we do not use your query content to train machine-learning models.
Legal bases
Where the GDPR or a comparable law applies, we rely on: performance of our contract with you (providing and billing the Service); our legitimate interests (security, fraud prevention, measurement and product improvement, balanced against your rights); compliance with a legal obligation (tax and accounting records); and your consent where we ask for it, which you can withdraw at any time.
International transfers
Our providers operate in several countries, so your data may be processed outside the country you are in. Where data leaves a region with transfer restrictions, we rely on an adequacy decision or on standard contractual clauses with the provider concerned.
How long we keep it
- Account data: while your account exists, and up to 90 days after you close it.
- Token records: until the token is revoked, then up to 12 months so a disputed charge can be traced.
- Usage and billing records: up to 7 years, because tax and accounting law requires it.
- Technical logs: up to 30 days, unless a log is retained longer for a specific security investigation.
- Product analytics events: up to 12 months.
- Session recordings and error reports: up to 90 days.
- Query content: held only for as long as it takes to answer the request.
Your rights
Depending on where you live, you may have the right to access the personal data we hold about you, correct it, delete it, receive a portable copy, object to or restrict certain processing, and withdraw consent. You also have the right to complain to your data protection authority.
Exercise any of these by writing to support@wutheringai.com from the address on your account. We answer within 30 days. Some data has to be kept even after a deletion request — billing records, for example — and we will tell you when that applies and why.
Security
Traffic is encrypted in transit. Tokens are stored only as one-way hashes and compared in constant time. Credentials are held as environment secrets and are never passed to the components that fetch data on your behalf. Access to production data is limited to the people who need it to run the Service. No system is perfect: if a breach affects your data, we will tell you and the relevant authority as the law requires.
Children
The Service is for business use and is not directed at children. We do not knowingly collect data from anyone under 16. If you believe a child has given us data, write to support@wutheringai.com and we will delete it.
Changes to this policy
We update this policy when the Service changes. The date at the top always reflects the current version. If a change materially reduces your rights, we will tell account holders by email before it takes effect.
Contact
Questions about this policy, or about the data we hold on you, go to support@wutheringai.com. We are the controller of the personal data described here.