This translation is provided for convenience. In case of discrepancy, the Spanish version prevails.
1. Cookies actually used by the service
| Cookie | Category | Purpose | Duration | First-party |
|---|---|---|---|---|
joincomu_visitor_id | Analytics | Distinguish consented visitors to deduplicate views; only its HMAC is stored in events. | 180 days | Yes |
joincomu_cookie_consent | Necessary | Remember the choice and policy version. It contains no UUID, history or browsing identifier. | 180 days | Yes |
joincomu_submitter_id | Necessary | Prevent abuse and spam in community submissions. | 30 days | Yes |
joincomu_management_session | Necessary | Maintain an email-validated management session; restricted to /gestionar. | 60 minutes | Yes |
Only after analytics are accepted and only while the metrics system is enabled.
2. Choosing and changing preferences
JoinComu asks for a prior choice. No choice or rejection means necessary cookies only. Continuing to browse, scrolling or closing the notice does not constitute acceptance.
You can accept, reject or change your choice through “Cookie preferences” in the footer. Choosing “Necessary only” stops future metric events and deletes the analytics visitor cookie.
You can also delete cookies in your browser settings. Rejecting analytics metrics does not prevent browsing the directory, publishing, managing publications or opening links.
Strictly necessary features may use technical cookies when appropriate. localStorage, sessionStorage and IndexedDB are not used to store the analytics choice.
3. Analytics status
The integration is prepared, but analytics remain inactive while the metrics configuration is not ready. After analytics are accepted, the server creates a random first-party identifier and transforms only its value with HMAC; a separate pseudonymous network quota limits abuse.
For information about personal data, review Privacy. privacidad@joincomu.com