Privacy & Cookie Information
Last updated: 8 September 2026
This is a privately operated Forgejo service at git.endalee.ie. It is used to host and distribute Git repositories.
Cookies
The service uses first-party cookies required for authentication, security and user-interface preferences. It does not use advertising or analytics cookies.
| Name / type | Purpose | Typical lifetime |
|---|---|---|
session |
Maintains the Forgejo login/session. | Up to 1 day under the current Forgejo configuration. |
persistent |
Used when persistent/remembered authentication is selected. | Up to 31 days under the Forgejo default. |
| Security and interface preference cookies | CSRF protection and preferences such as interface settings. | Depends on the feature; security values are generally session-related. |
forgejo-notice-dismissed |
Set only after you select “Dismiss” on the privacy notice, so the notice does not need to be shown repeatedly. | 1 year. |
These cookies are used to provide functionality requested by the user. No advertising, behavioural profiling or analytics cookies are intentionally set by this service.
Information processed
The service may process and store:
- account information such as username, email address, password hash and configured authentication keys or tokens;
- repository data, commits, issues, comments and other content submitted to the service;
- technical request and security information such as IP address, time, requested resource and browser/client information.
Why this information is used
Information is processed to provide the Git/Forgejo service, authenticate users, serve repositories, troubleshoot faults and protect the server against abuse or attacks.
Security monitoring
Traefik access logs are analysed by CrowdSec for abuse detection. CrowdSec may share security-signal metadata with its Central API when a configured security scenario is triggered. That metadata can include the offending IP address, the scenario that triggered, a timestamp and machine/scenario metadata. Repository contents are not part of the CrowdSec signal metadata described by CrowdSec.
Third-party services
This service does not use advertising or analytics providers. Infrastructure and security components may communicate with external services required for functions such as TLS certificate management and CrowdSec community security intelligence.
Retention
Repository and account information is retained while required for operation of the service. Security and request logs are retained for operational and security purposes and should be periodically rotated or deleted by the server administrator.
Your choices
You can delete site cookies using your browser controls. Doing so may sign you out or reset interface preferences. The privacy-notice dismissal cookie has no effect on authentication or repository access.
Contact
Questions about this service or its handling of personal data should be directed to the site administrator.