Privacy

Effective 23 September 2026. This notice describes the current website, released products, support channels, telemetry, and public feedback.

The servers process code and runtime artifacts locally. Your MCP client can send returned content to its model provider.

Website operator and controller

Bogdan Novosad, a Spanish sole trader trading as GliderMCP, controls the personal data described here. NIF: Y8622372P.

Business address: Samaniego-Campoamor 22, 7º A, 03189 Orihuela, Alicante, Spain.

Email [email protected] for privacy requests. See the legal notice for supplier details.

Website requests, storage, and cookies

Cloudflare receives website requests and delivers the site. Request data includes IP addresses, requested URLs, headers, timestamps, and security or network diagnostics.

Cloudflare also creates aggregate zone analytics from edge requests. We use this processing to operate, secure, and understand the website.

We rely on our legitimate interests in providing a reliable and secure website.

Cloudflare may set essential security or rate-limit cookies when its services require them.

The site code sets no cookies. It stores your theme choice, optional game high score, and playground request history in your browser only.

Playground history can contain up to 100 tool names, parameters, outcomes, errors, durations, and timestamps. You can clear it in the playground or browser settings.

The playground uses a local server by default. You can enter another URL or supply one through the server query parameter.

The server you select receives connection checks and tool parameters. Review that server’s privacy terms before you use a remote URL.

This build does not load Google Analytics. It serves JetBrains Mono from this website and sends no font requests to Google.

Contact and correspondence

Email [email protected] for privacy requests or [email protected] for general enquiries.

Cloudflare routes domain email to a Gmail mailbox and sends our replies. Cloudflare and Google process message content, contact details, and delivery information.

We use this information to answer requests, take requested pre-contract steps, meet legal duties, and manage related support.

The legal basis depends on the request. It can be contract steps, a legal obligation, or our legitimate interest in answering enquiries.

We keep correspondence while we need it for the request, related follow-up, legal duties, or legal claims.

Do not send passwords, payment card details, or confidential source code.

Local code and runtime evidence

The servers read workspace files and return results through MCP. GliderTrace can also execute commands and store runtime artifacts.

Product telemetry excludes source code and runtime artifacts. Review your client’s data policy for content it forwards or retains.

Product telemetry

Telemetry is on by default. It includes installation identifiers, product and platform facts, tool outcomes, and documented health or workspace metrics.

Installation identifiers can link events from the same installation. We do not treat those identifiers as proof that the records are anonymous.

We use telemetry to measure product use, compatibility, reliability, and failures. Cloudflare validates events and sends the filtered records to Grafana Cloud.

Use --no-telemetry or DO_NOT_TRACK=1 to disable telemetry and agent feedback. See the full field list and controls.

Feedback your agent sends

All four products include send_feedback. It sends agent-authored text and product facts, then publishes a public GitHub issue. Glider development builds can add abstract reproduction evidence.

Glider development builds also let an agent preview an invented, small code example for public feedback. The agent must show you the complete issue and duplicate comment, obtain approval, and send the same content. The server does not store previews or verify approval. Your MCP client controls tool approval.

The example, run instructions, and evidence become public GitHub content. Ordinary feedback still rejects code. Filters for either route cannot prove that a report contains no sensitive information.

We process a report to publish, group, investigate, and answer it. We rely on our legitimate interest in receiving and responding to product feedback.

Set GLIDER_FEEDBACK=0 to disable feedback separately. See feedback fields, retention, and controls.

Website analytics

Google Analytics is disabled on this website. Product telemetry is separate and follows the controls described above.

Planned accounts, trials, and payments

Commercial accounts, trial activation, and paid checkout are not available on this website yet.

The planned service will use verified account identities, team memberships, license records, and payment references. Trial eligibility must persist across reinstalls.

Paddle is the selected payment provider and merchant of record. Its privacy notice describes its processing.

Before these features launch, we will publish their purposes, legal bases, recipients, retention periods, and applicable rights.

Recipients and international transfers

Cloudflare processes website requests, product ingest traffic, and email delivery. Its customer DPA describes its Data Privacy Framework and contractual safeguards.

Grafana Labs stores filtered product telemetry. Its data processing agreement describes its transfer safeguards.

Google stores support correspondence. Its transfer-framework notice describes its Data Privacy Framework and contractual safeguards.

GitHub stores public feedback issues. Its privacy statement describes its Data Privacy Framework and contractual safeguards.

These providers can process data outside the European Economic Area. Their notices identify locations, subprocessors, and applicable safeguards.

Your privacy rights

Where applicable, you can request access, correction, deletion, restriction, or portability of your personal data, and object to processing.

Where processing relies on consent, you can withdraw that consent. Contact [email protected].

You can complain to the Spanish Data Protection Agency (AEPD) or your competent data protection authority.

Retention

Local files, runtime artifacts, and client transcripts follow the retention settings of their respective tools.

We keep telemetry while needed to compare product versions, investigate reliability, and measure feature use. The active Grafana Cloud policy retains product logs for 14 days. Cloudflare request logs are separate and follow provider-controlled retention. We have not verified their retention period; the Grafana period does not apply to them.

Scheduled cleanup deletes filed, duplicate, and failed feedback database records once their last status update is more than 30 days old.

We keep reports available if they require publication or a retry. This deletion schedule covers the active database; provider backups follow separate retention.

Public GitHub issues follow GitHub retention. Closing or archiving an issue does not delete it.