devprofile.dev

Privacy

Last updated 17 October 2026

Who is responsible

The operator named in the imprint is the controller for the data described here (Art. 13 GDPR). You can ask for a copy of your data, its correction or deletion, and you can complain to a data protection authority.

Visitors

devprofile.dev sets no cookies for people who look at a profile, runs no third-party scripts and loads nothing from other services except GitHub avatars. When a profile is viewed or one of its links is clicked, a counter for that profile and day goes up by one. The IP address, user agent and referrer are not stored. Requests from obvious bots are not counted.

People with a profile

Signing in with GitHub gives devprofile your GitHub user id, login and avatar URL. No access to your repositories is requested. A session cookie keeps you signed in for 30 days; only a hash of it is stored on the server.

Everything you write in the editor is public on your page unless you set the page to draft. You can download all of it as JSON from the editor and delete your account there; deletion removes the profile, links, projects and counters immediately.

Data from other services

Profiles show public data from GitHub, npm and the feed you choose. It is fetched by the server, cached for a few hours and never sent to anyone else.

Where it runs

devprofile.dev runs on a single server in Germany. The database and its backups stay on that server.

Contact

Questions about your data: privacy@devprofile.dev.