No KYC — no ID, no selfie, no documents. Pay in crypto: BTC, USDT, USDC, ETH, SOL, LTC
Language: English
Get an API key

What we keep, why, and for how long

Privacy policy

A SERP API sees the questions you ask. This page lists every item we keep about you and your requests, the reason, and the date it is deleted.

Last updated: · 3 min read

Quick answer

What does SerpCrypto keep about me and my searches?

SerpCrypto keeps your account number, an optional email, your top-up and order records, and API request logs for 30 days. It does not request identity documents or card data, and it does not sell your queries. We log, for each request, the time, account, engine, query parameters, status and credits used, and keep these logs for 30 days to show your usage and settle billing disputes, then delete them. We do not sell or share your queries. We keep your account number, orders, top-up records and credit totals while your account is open, and afterwards only as long as accounting rules require. We disclose records to authorities only when the law requires it.

1. What do we collect, and for how long?

DataWhy we keep itHow long
Account numberIt is your loginWhile your account is open
Email address (optional)Account recovery and support repliesUntil you remove it or close the account
Top-up and order records: amount, coin, network, transaction ID, dateCrediting payments, accounting, refundsWhile your account is open, then as long as accounting rules require
API request logs: time, account, engine, query parameters, status, credits usedShowing your usage, settling billing disputes, handling abuse reports30 days, then deleted
API keys (stored so we can check them)Authenticating your requestsUntil you revoke the key or close the account
Support messagesAnswering youWhile your account is open

2. What do we never collect?

We do not ask for or store identity documents, selfies, company registration papers, a postal address or a phone number. There is no card payment, so we hold no card data. You do not need to give a name to open an account.

3. Do we sell or share your queries?

No. We do not sell, rent or publish your queries or your results, and we do not use them to build datasets for others.

To run a search, our policy is to send upstream only the search parameters: the query, engine, country, language, location, device and page. We do not send your account number, your email or your API key to the partners that help us collect results. Those partners may keep their own technical logs under their own policies.

4. What does the website store in my browser?

The public website sets no advertising or analytics cookies. It uses your browser's local storage for three small, optional items: the language you chose, the code language you picked in the docs, and the source of your visit (the referring site or a utm_source tag and the landing page, with no identifier) for 30 days, which is sent with an order so we know which pages bring customers.

The client area needs a session to keep you signed in. Blocking storage does not stop the public pages from working.

5. When do we disclose data?

Only when the law requires it, and only the records we actually hold, as listed in section 1. Because request logs are deleted after 30 days, older searches cannot be disclosed: they no longer exist on our side.

6. What choices do I have?

  • Add or remove your email at any time in the client area.
  • Revoke any API key; the key stops working at once.
  • Ask for a copy of the data we hold about your account, or for its deletion, by writing from the client area or to [email protected].
  • Close your account. Records that accounting rules require stay for the legal period; everything else is deleted.

We never ask for your account number or your API key by email or chat.

7. Who is responsible, and how do I contact you?

SerpGoat LLC is responsible for this data. Write to [email protected] for any privacy question. Email replies within 12 hours, 7 days a week, including help with API integration. We publish changes to this policy on this page with a new date and note them in the changelog.