Privacy Policy

1. Scope

This policy covers the SerpResult API, the dashboard, the documentation and this marketing site. It does not cover the third-party search engines whose results the API returns, or the sites those results link to.

2. What we collect

Account data

Your email address, your name if you give one, and the profile details your identity provider returns when you sign in with Google. Passwords are stored only as a hash.

API keys

A label, the key type, and a hash of the secret. The secret itself is shown once at creation and is never stored in a form we can read back.

Query logs

For every call: the query text, the target, the country, the locale, the paging and result parameters, whether the answer came from cache, the latency, the credits charged, the HTTP status, and any error code. These rows are how usage and billing are accounted for.

Cached results

The organic results returned for a query, so a repeated search does not repeat the work upstream. The cache is keyed on the search parameters, not on who asked.

Website usage

The demo search on the home page sends your query to the API the same way a customer call does, and it is rate limited per IP address. Your theme preference is stored in your own browser and is never sent to us.

3. How we use it

• To answer your API calls and show them back to you in the dashboard.
• To meter credits and enforce rate limits.
• To debug failures, which is why each response carries a request id.
• To send service email you cannot opt out of, such as email verification.

We do not sell your data, and we do not use your queries to build a profile of you or your organisation.

4. How long we keep it

Account data is kept while the account exists. Query logs are kept for a bounded retention window and then deleted by a scheduled job. Cached results expire on their own freshness window. Deleting your account removes the account row and the keys and logs that hang off it.

5. Who else sees it

We share data only with the processors needed to run the service:

• our hosting and edge platform, which runs the API and stores the database;
• the fetch node that retrieves results from the target search engine;
• a transactional email provider, for verification and account email;
• an API marketplace, where you reached us through one, so your usage there can be billed.

A query you send is passed to the target search engine to be answered. Do not put personal or confidential information in a search query.

6. Your rights

Depending on where you live you may have the right to access, correct, export or delete the personal data we hold about you, and to object to some processing. Write to [email protected] and we will action it.

7. Security

Traffic is served over TLS. API key secrets and passwords are stored only as hashes. Access to production data is limited to the people who need it to operate the service. No system is perfectly secure, and we will tell affected users promptly if a breach reaches their data.

8. Changes

This policy will change as the product does. The date at the top of the page reflects the last revision, and material changes will be announced before they take effect.

9. Contact

Privacy questions and requests go to [email protected].