Stickering.com Cookie Policy and Preferences
Version 1.0 · Updated 11 November 2026.
1. Operator and scope
NOMADE - S.R.L., Via Luigi Salvatore Cherubini 10, 50121 Florence (FI), Italy, VAT / tax code 07505480488, operates Stickering.com. Contact: help@nomadesrl.it; PEC: info@pec.nomadesrl.it.
This policy covers cookies, localStorage, sessionStorage and browser identifiers used by the website. It distinguishes functional participation data from optional PostHog analytics. The privacy policy explains photographs, public locations, AI processing, Telegram submissions, recipients and your rights.
2. Your analytics choice
The banner offers equally prominent Reject analytics and Accept analytics buttons, plus Cookie preferences. The X rejects analytics. Scrolling, browsing or closing the preferences without saving is not acceptance. Optional statistics are off until you accept.
Use Cookie preferences in the footer or open the preferences to change or withdraw your choice. Reject analytics withdraws consent; Save preferences applies the selected checkbox. The choice is valid for six months in that browser when storage is available. An expired, missing or invalid choice causes the banner to return. Choices propagate to other open tabs on the same origin. Clearing storage or using a different browser may require choosing again.
Refusing analytics does not prevent browsing, uploads, voting or account use. It does not remove functional identifiers, an account, published images or previously stored contributions. The preferences apply to this website, not Telegram's own application or the separate services of an identity provider.
3. Website storage inventory
| Item | Purpose and category | Lifetime / removal |
|---|---|---|
stickering_consent, localStorage |
Necessary record of the analytics choice, notice version, update date and expiry; contains no additional visitor identifier | Choice valid for six months; localStorage itself has no automatic expiry. The application checks validity and replaces the record after a new choice. |
_preferred-theme, cookie |
Requested light/dark appearance, also read during server rendering | Set without an explicit persistent expiry; a session cookie, subject to browser session restoration behaviour. |
stickering_fp, localStorage |
Functional fingerprint used for votes, submissions/status, reports, attribution and association of prior browser history with an account | Cached for 24 hours and refreshed when needed. Cache expiry is not deletion of database contributions and does not guarantee a new identifier. |
last_location, sessionStorage |
Remembers the map location selected for a submission | For the tab's session, subject to browser restoration/clearing. |
| Clerk session cookies and related authentication storage | Sign-in state, authentication and session security | Managed by Clerk according to session type and configuration; signing out ends the active session. Exact cookie names and expiry can vary. See Clerk's cookie information. |
| Mapbox browser storage, where used by its SDK | Map delivery, map session/accounting and technical operation | Managed by the map SDK and browser; names and expiry depend on SDK configuration. See Mapbox's privacy policy. |
stickering:sign-up-completed:v1:<user-id>, localStorage |
Optional analytics guard preventing duplicate sign-up conversion events, written only when analytics are enabled | Until browser storage is cleared; it is not the analytics consent record. |
ph_<project-key>* and PostHog session identifiers, localStorage / SDK storage |
Optional pseudonymous analytics identifiers, session state and event properties | LocalStorage has no native expiry; this application removes project analytics identifiers on withdrawal or missing/expired consent. |
__ph_opt_in_out_<project-key>, SDK consent storage where created |
Technical PostHog opt-in state | Removed with this project's analytics identifiers on rejection; the necessary choice remains in stickering_consent. |
Cookies and storage from external sign-in providers depend on the method you choose. This inventory describes the application's own keys and integrations, not a claim that every browser or provider always sets the same items. Browser settings let you inspect actual stored items and their expiry. Blocking necessary storage can affect sign-in, recognition of votes, preferences or submission recovery.
4. Functional fingerprint and maps
Stickering uses the locally bundled FingerprintJS library to derive a pseudonymous browser identifier from browser/device characteristics. It is used when participation and account features request it, independently of PostHog consent. Votes, submissions and reports can be associated with it on the server; signing in can link earlier anonymous contributions to your verified account. It is not an advertising identifier, but it can identify recurring activity and must not be described as anonymous.
Deleting stickering_fp clears only the local cache; the same browser may generate the same identifier again. To request deletion or unlinking of associated personal records, contact the controller. The analytics checkbox does not control this participation identifier.
Maps and location search connect your browser to Mapbox, which receives request information and map/search inputs. Browser geolocation is used only after browser permission and can be declined in favour of manually choosing the work's location. The selected coordinates can become public when the submission is approved. Browser permission is separate from the analytics checkbox. Nominatim receives sticker coordinates from the server for reverse geocoding.
5. Optional analytics and withdrawal
PostHog measures page navigation, selected interactions, sign-ups, accepted submissions and technical errors using pseudonymous browser identifiers and device information. After sign-in, consented events can be associated with your Clerk account identifier; the identity integration does not send your email, name or profile fields. The current application disables click autocapture and session recording. It does not initialise the PostHog SDK before analytics acceptance and checks the current consent before sending events. No optional advertising category is enabled by this implementation.
Rejecting or withdrawing analytics opts the SDK out, stops session recording if active, resets its identifiers and removes this project's analytics storage, including best-effort cleanup of legacy cookies on applicable domains. No new analytics event is authorised after withdrawal. Previously received events are not automatically erased: use the privacy contact to exercise applicable rights. Local cleanup cannot recall information already transmitted to a provider.
The six-month consent duration does not specify how long PostHog holds received events. Fixed server analytics retention has not yet been defined; the operator must retain such data only for as long as needed for usage analysis and diagnostics. Processing locations, recipients and transfer information are addressed in the privacy policy; this policy does not assert an audited PostHog region or account retention setting.
6. More information
See the privacy policy for rights, retention criteria, controller contacts and international processing, and the terms for contribution rules. The Italian data protection authority provides guidance on cookies and other tracking technologies.