1. In short
Skill Forge uses a single cookie, technical and necessary: it keeps you signed in after the GitHub login. We do not use profiling, advertising or tracking cookies. That is why we do not show a cookie banner: there is nothing to consent to.
2. The cookie we use
| Name | Type | Purpose | Duration |
|---|---|---|---|
next-auth.session-token | Technical, necessary | Keeps the session after the GitHub login | Up to 30 days, or until sign-out |
next-auth.csrf-token | Technical, necessary | Protects forms from forged requests (CSRF) | Session |
next-auth.callback-url | Technical, necessary | Remembers where to return after login | Session |
The session cookie is signed and encrypted; it contains the GitHub token that lets us read your profile.
3. Why no banner
The rules (ePrivacy directive and the Italian Data Protection Authority's guidelines) require consent only for cookies other than the necessary technical ones. Since the only cookie we set is strictly necessary for the service to work, no prior consent is needed.
4. What we do not do
- No third-party cookies for advertising or analytics.
- No tracking across different sites.
- No profiling.
5. How to manage them
You can delete or block cookies from your browser settings. If you block the session cookie, however, you will not be able to stay signed in and the service will not work correctly.
6. Contact
For questions about cookies, write to ciao22king@gmail.com. See also the privacy policy.