Keirolabs / Privacy

Privacy Policy

This policy explains what data Keirolabs collects when you use our site, dashboard and web search API, why we collect it, and how you can access or delete it. It is written to be read.

Effective November 14, 2026Version 1.1Terms of Service
§ 01

Who this policy covers

This policy covers keirolabs.cloud, the Keiro dashboard and documentation at platform.keirolabs.cloud, the API at api.keirolabs.cloud, the MCP server, and the metered cloud browser service. Together these are the “Service”. By using the Service you accept this policy.

§ 02

What we collect

  • Account data. The email address you sign up with and a hashed password. A display name if you provide one.
  • API keys. The keys you create in the dashboard. Keys are stored in hashed or encrypted form and are shown in full only once, at creation.
  • Request metadata. When your code calls the API we log the endpoint called, timestamps, credit usage and rate-limit counters, so we can bill correctly and prevent abuse.
  • Content you submit. Queries, target URLs and extraction instructions you send to endpoints, and the URLs visited by the metered cloud browser when you use browser tools. Search queries are answered from our own index. Extraction and browser requests fetch the target websites you name; that is inherent to how the Service works. On every paid monthly plan, zero data retention (ZDR) applies: we do not store this content once the response is sent.
  • Billing data. Payments are processed by our payment processor. We keep invoices and subscription status, not card numbers.
  • Support messages. What you send us through the dashboard support form or by email.
§ 03

Analytics and cookies

Our marketing sites, keirolabs.cloud and browserfoundry.cloud, use PostHog for product analytics. It records which pages you visit, what you click and scroll to, page performance and errors, and a replay of the session so we can see where the site is confusing or broken. Text you type into form fields is masked in replays and is never collected.

The marketing sites set no cookies. PostHog keeps a random visitor ID in your browser's local storage so visits can be counted; clearing site data removes it, and content blockers that block analytics will stop it entirely. Analytics data is processed by PostHog on servers in the United States.

We do not run advertising networks, we do not sell or rent personal data, and we do not build advertising profiles. The dashboard uses a session cookie to keep you signed in. To have your analytics data deleted, email us (see Contact below).

§ 04

Why we process data

To operate the Service you asked for: authenticating your requests, metering credits, showing your usage, billing plans, answering support requests, and keeping the Service available and free of abuse. We rely on contract performance for operating the Service, and on legitimate interest for keeping it secure and for the site analytics described above.

§ 05

Who we share data with

  • Infrastructure providers. Cloud hosting, egress and browser-rendering providers that run the Service.
  • Payment processor. To collect subscription payments.
  • Analytics provider. PostHog, which processes the site analytics and session replays described above.
  • Legal process. We may disclose data when required by law or to protect the Service against abuse.

We do not sell your personal data, and we do not share it for third-party advertising.

§ 06

How long we keep it

Zero data retention. On every paid monthly plan, the content you submit (queries, target URLs, extraction instructions) and the results we return are not stored after the response is sent. Request metadata (endpoint, timestamps, credit usage) is still kept so we can bill you and enforce rate limits. On other plans, content you submit is kept only as long as needed to operate, debug and secure the Service, then deleted.

Request metadata is kept for the period needed for billing, rate-limit accounting, abuse prevention and legal obligations, then deleted or aggregated. Account data is kept until you ask us to delete it or your account is inactive for an extended period. Support messages are kept as long as needed to resolve your request and for our records.

§ 07

Your rights

You can ask us to access, export, correct or delete your personal data, and you can object to or restrict processing where the law allows. To exercise any of these rights, email team@keirolabs.cloud or open a support ticket from the dashboard. We respond within 30 days. Deleting your account removes your email address and keys from active systems.

§ 08

Security

Traffic to the Service is encrypted in transit with TLS. API keys are treated as credentials: hashed at rest and shown once at creation. Access to production systems is limited to the people who operate the Service. No system is perfectly secure, and we will notify affected users if a breach ever requires it.

§ 09

International transfers

Our servers and providers may process data outside your country. Where that happens, we use providers that offer comparable protections and transfer mechanisms.

§ 10

Children

The Service is not directed at children. If you are under 16, do not create an account.

§ 11

Changes to this policy

If we change this policy we update the effective date at the top. Material changes are announced on the site or by email to account holders.

§ 12

Contact

Questions about this policy: team@keirolabs.cloud or the support form in the dashboard. Related reading: Terms of Service.