Skip to content
mergio

Privacy

Last updated 19 November 2026

Draft. This is written in plain language and has not yet been checked by a lawyer. It will be before the pilot opens.

The short version

We keep what Mergio needs to teach you and to show what you have learned. We do not sell your data, the site has no advertising trackers, and your profile is private until you choose to share it. You can ask us to delete everything at any time.

The waitlist

When you join the waitlist we keep only what the form asks for:

  • your name and email address
  • why you are here: learning, hiring or teaching
  • the track you are interested in and how long you have been coding
  • for employers and schools, the name of your organisation
  • whether and when we invited you to a pilot wave

We use it to invite you to a pilot wave and to tell you about Mergio. Nothing else.

Signing in with Google

When you sign in, Google tells us your email address and name (and a link to your profile picture). We keep them with your account. During onboarding you add a username and choose a track. We also record which pilot wave you are in.

Connecting GitHub

To work on tasks you connect GitHub. We keep:

  • your GitHub username and GitHub's number for your account
  • the number of the Mergio Checks app installation on your account
  • the name and number of your copy (fork) of the course codebase

We do not keep any GitHub password or key. When the Mergio command-line tool needs to send your work to GitHub, it gets a key that works only on your copy and only for one hour.

Your copy of the course codebase lives on your GitHub account and is public, like the course codebase it comes from. The changes you send and the pull requests Mergio opens there can be seen by anyone on GitHub. Commits carry the name and email set in git on your computer; if none is set, the tool uses your GitHub username and GitHub's private “noreply” address instead of your real email.

The command-line tool

When you link the mergio tool to your account, we keep a scrambled copy of its login key (never the key itself), your computer's name and system (for example “my-laptop (win32)”) so you can tell your logins apart, and when it was last used. Each login stops working after 90 days, or straight away when you run mergio logout.

Your learning

As you learn we keep:

  • how far you are through each tour, and your quiz answers and scores
  • each task you start, and each piece of work you submit: the commit, its pull request and the result of the official check
  • each time you agree to the honour pledge when you submit (which task and commit)

The official check runs your code on GitHub's computers, in Mergio's private grading project, never on Mergio's own server. Only the results come back to us.

The AI coach and AI grading

As these parts of Mergio open, this is how they work. When you ask the coach for a hint, we keep your messages and its replies, so you can read them again and so we can check it never writes code for you. For every AI request we also log which model answered, how much text it handled and what it cost, so we stay within our budget. Your messages, and later the explanations you write about your changes, are sent to the AI provider that answers them, which processes them for us.

Stopping spam and abuse

When someone sends the waitlist form or links the command-line tool, we keep a scrambled copy of their internet address (or, for linking, their account) to limit how often it can happen. It cannot be turned back into the address, and we delete it after a day.

Counting visits

We count page visits with Vercel Web Analytics. It uses no cookies and does not identify you.

Who handles it for us

  • Supabase stores our database and runs sign-in.
  • Vercel serves the website.
  • Google handles signing in with Google.
  • GitHub holds your copy of the codebase and runs the official checks.
  • AI providers answer coach messages and help grade explanations, once those parts open.

How long we keep it

Scrambled internet addresses are deleted after a day, and unused sign-in codes for the command-line tool soon after they expire. Everything else is kept while you use Mergio, until you ask us to delete it. Your profile is private by default and never shows failed checks, attempts or how many hints you used.

Your choices

In Settings you can correct your name and username, download everything we hold about you as a file, and delete your account. You can also reply to any email we send you and we will do it for you. Deleting your account removes your profile, progress, submissions, coach messages, explanations, GitHub connection and waitlist sign-up from Mergio. Your copy of the codebase on GitHub is yours: delete it on GitHub, and uninstall the Mergio Checks app there, if you want those gone too. We aim to follow Ghana's Data Protection Act, 2012 (Act 843).

← Back to Mergio