Privacy policy

Cyberpunk 2077 mission tracker · last updated 28 September 2026

The short version. Signing in stores your mission progress and nothing else. Your name is never written to the server. Your game save is read in your browser and never uploaded. There is no analytics, no advertising, and nothing is shared with anyone.

Who runs this

A personal, non-commercial hobby project by an individual, hosted on Cloudflare Workers at cp2077-tracker.ryanellis.dev. It is not affiliated with, endorsed by, or connected to CD Projekt Red.

What is collected when you sign in

Signing in with Google requests only the openid and profile scopes. From that the site receives:

An opaque account identifier — a meaningless string your provider uses to identify you. It is not your email address.
Your display name — used only to show who is signed in.

Your email address is never requested and never received. Signing in with GitHub, if it is enabled, works the same way using the read:user scope.

What is actually stored

On the server (Cloudflare Workers KV): your mission progress only — a list of mission identifiers such as the-heist, each marked complete or missed, plus a timestamp. It is filed under a key derived from your opaque account identifier.
Your display name is not stored on the server. It lives only inside the session cookie in your own browser.
In your browser: a copy of your progress in local storage so the site works offline and while signed out, and your view preferences.

Your game save is never uploaded

The import page reads sav.dat entirely inside your browser tab using the File API. No part of the file — not your character, inventory, position, or anything else — is sent to this server, to Cloudflare, or anywhere else. Only the resulting list of finished mission identifiers is saved, and only when you press the button to apply it. You can verify this by opening your browser's network tab while loading a save, or by reading savparse.js.

Cookies

One cookie, cp_session, set only after you sign in. It is HttpOnly, Secure, SameSite=Lax, signed with HMAC-SHA256, and expires after 90 days. It holds your provider, your opaque account identifier, your display name, and the expiry time. A second short-lived cookie, cp_flow, exists for ten minutes during sign-in to prevent request forgery. There are no advertising or analytics cookies.

Who else sees it

Cloudflare hosts the site and stores the progress data as the infrastructure provider.
Google (or GitHub) handles the sign-in itself and sees that you signed in to this app.
Google Fonts serves the page font, which means Google receives your IP address when the font loads.

Nothing is sold, shared for advertising, or passed to anyone else.

Deleting your data

Sign in, open the account menu in the top bar, and choose Delete my data. This removes your record from server storage entirely — it is not emptied and kept, it is deleted. Clearing your browser's site data removes the local copy and signs you out.

If you cannot sign in to do that, email ryancellis12@gmail.com and the record will be removed.

Keeping it safe, and its limits

Everything is served over HTTPS. Progress is filed per account, so no signed-in user can read or write anyone else's. That said, this is a hobby project with no warranty — please do not store anything here you would be upset to lose. Keep your own backup if it matters.

Children

This site is not directed at children under 13 and no age information is collected.

Changes

If this policy changes, the date at the top changes with it. Material changes will be noted on the tracker itself.