Ghostline

Privacy Policy

Last updated: October 15, 2026

Ghostline is a Chrome extension that reviews Google Colab cells to help you find and fix silent mistakes. This policy explains what leaves your browser, what we store, and what we do not.

Who this covers

This policy applies to the Ghostline Chrome extension and the Ghostline review service (our Cloudflare Worker API).

What Ghostline sends when you run a cell

If reviews are turned on for that notebook, Ghostline sends to our review service:

That request is authenticated with a Google sign-in token so we can identify your Google account ID and apply per-account usage limits.

What Ghostline does not send

Where it goes

Our server receives that request, then sends the review payload to Anthropic’s Claude API to produce the suggestion. We choose the model and prompt on the server. We do not log your code, prompts, or model output. Operational logs may include your Google account ID, timestamps, token counts, and error codes only.

What is stored

What is never stored

Code content from your Colab cells is not stored on our server. It is used only to produce that review response, then discarded.

How to delete your data

Google sign-in

Ghostline uses Chrome Identity and Google OAuth to sign you in. We receive a token that lets us verify your Google account ID and, when available, your verified email address for account and usage display. We use that identity for authentication, daily limits, and optional admin grants — not for advertising. We do not sell personal data.

Third parties

Those providers process data under their own terms and privacy policies.

Children

Ghostline is not directed at children under 13. Do not use the service if you are under 13.

Changes

We may update this policy as the product changes. The “Last updated” date at the top will change when we do. Continued use after an update means you accept the revised policy.

Contact

Questions about privacy: use the support email listed on the Chrome Web Store listing for Ghostline, or the developer contact email on the Google OAuth consent screen.