Privacy Policy

Welcome to the Julython Privacy Policy — a document you are reading voluntarily, which already puts you in the top 1% of internet users. We'll keep this short, honest, and mercifully free of legalese.

Last updated: July 2025. We are not lawyers. This is not legal advice. If you need legal advice, we recommend finding a lawyer, not a coding challenge website.

What We Collect

Here is the terrifying list of data we hoard about you:

Your GitHub identity

When you sign in via GitHub, we receive your public GitHub profile — username, display name, and avatar. GitHub has a whole separate privacy policy for that part, and they are much larger than us.

Your GitHub OAuth token

We store a GitHub OAuth token so that you can register and manage webhooks on your repositories without having to re-authenticate every time. This token has three permissions: read:user, user:email, and — the big one — write:repo_hook (full control of repository hooks). We use it only to add webhooks on your behalf. We acknowledge this is a meaningful level of trust and we don't take that lightly.

You can revoke this token at any time by visiting github.com/settings/applications and removing Julython. Doing so will sign you out and disable webhook management until you re-authorize, but your account and points will remain intact.

Email addresses

We ask for the email address(es) you commit with. This is the only way we can match your commits to your account. We do not display this, sell this, rent this, or write it on a sticky note on our monitor.

Location (optional)

If you choose to add a city/region to your profile, we display it on the leaderboard so you can compete with your neighbors. You can leave this blank. We will not judge you. Much.

Commit metadata

When your webhook fires, we record the commit message, author email, timestamp, and repository name. That's it. We do not receive your code. We do not want your code. We have enough code of our own to be embarrassed by.

What We Don't Collect

This is the fun section.

🚫 Your actual code. We only support public, open source repositories. We never pull, clone, read, or judge your variable naming choices.

🚫 Private repositories. We don't have access and we don't want it. Keep your secrets.

🚫 Payment information. Julython is free. There is nothing to buy. There are no prizes. This is a labor of love and mild obsession.

🚫 Your browsing habits. We don't run ad trackers, analytics pixels, or any of that stuff. We can barely keep the server running.

🚫 Your soul. Unlike some platforms, we are not interested in maximizing engagement, time-on-site, or existential dread.

Who We Share It With

Nobody. We don't sell your data. We don't share it with advertisers because we don't have advertisers. We don't share it with "partners" — a word that in privacy policies usually means "strangers who gave us money."

The only third party involved is GitHub, who handles authentication. You can read their privacy policy at docs.github.com. It is significantly longer than this one.

Cookies

We use a session cookie to keep you logged in. That's the whole cookie story. No tracking cookies. No third-party cookies. No cookies that inexplicably follow you around the internet showing you ads for shoes you looked at once.

If you'd like to remove it, clear your cookies or sign out. The cookie will not be offended.

Data Retention

We keep your account data for as long as your account exists. If you'd like your data removed, email us at help@julython.org and we'll delete it. No questions asked, no dark patterns, no "are you sure? you'll lose all your points!" guilt trips.

Well — you will lose all your points. But we won't guilt trip you about it.

Security

We take reasonable precautions to protect your data. We use HTTPS, we don't store passwords (GitHub handles that), and we try not to do anything obviously foolish. That said, no system is perfectly secure, and we are a small open source project, not a bank.

Speaking of open source — if you find a security issue, please email help@julython.org rather than, say, posting it publicly or using it to give yourself a suspiciously round score.

Changes to This Policy

If we ever need to update this policy, we'll update the date at the top and try to communicate any meaningful changes. Since we're not planning to suddenly start harvesting your data, dramatic changes are unlikely.

Questions? Concerns? Unsolicited legal opinions? help@julython.org