Stickering.com Privacy Policy
Version 1.0 · Updated 11 November 2026.
1. Controller and contacts
Stickering.com is operated by NOMADE - S.R.L. (“NoMaDe”), Via Luigi Salvatore Cherubini 10, 50121 Florence (FI), Italy, VAT / tax code 07505480488. For privacy requests, account deletion, corrections or complaints, email help@nomadesrl.it. Certified email (PEC): info@pec.nomadesrl.it.
This notice covers the website, its API and submissions to the Stickering Telegram bot. Telegram and external sign-in providers also process information under their own notices. The service is intended for people aged 18 or over.
2. What Stickering does
Stickering is a public archive of photographed street stickers and street art. Visitors can browse and search images, see locations on maps, vote, submit photographs from the website or Telegram, create profiles, suggest artist attributions, claim artwork and report content. Points, badges and leaderboards recognise participation.
Submissions leave your device. Photographs are uploaded to server storage and processed by automated services. Approved images, titles, artist names, descriptions, sticker coordinates and associated public profile information can be seen by anyone, indexed by search engines and copied by others. Sticker coordinates describe the photographed work, but can also reveal where you have been. Do not submit a home location, identifiable people, private communications or sensitive information that should not be public.
3. Data, purposes and legal bases
| Activity | Data processed | Purpose and legal basis |
|---|---|---|
| Browsing, security and abuse prevention | Network requests, IP addresses and technical logs; rate-limit counters; identifiers associated with requests | Deliver and protect the service; legitimate interests in availability, security and preventing abuse (Article 6(1)(f) GDPR). |
| Accounts and requested features | Clerk account identifier and sign-in data handled by Clerk; username, display name, avatar, optional biography and website; contributions, votes, points, badges and artist status | Provide account, contribution and community features requested by the user; performance of the service agreement (Article 6(1)(b)). Optional public profile fields are supplied at the user's choice. |
| Anonymous participation and account linking | Browser fingerprint, votes, submission records and timestamps; after sign-in, association with the verified account | Recognise contributions, apply vote limits, retrieve submission status and associate prior anonymous history with the signed-in account; performance of requested participation features and legitimate interests in integrity and abuse prevention, according to the operation. See the separate explanation below. |
| Website and Telegram submissions | Photographs and derived crops; title, artist and category; location from EXIF, a map or location sharing; source, status and identifiers. Telegram submissions also include Telegram user ID, username and available first/last names | Receive, process and publish the requested contribution; performance of the service agreement. Protect third-party rights and apply publication rules; legitimate interests in maintaining a safe, relevant archive. |
| Image analysis and search | Images, visible text, generated descriptions, numerical image/text representations (“embeddings”), image hashes, search text, classifier results and moderation records | Identify street art, detect duplicates, extract stickers, describe and search the archive; provide the requested service and maintain archive integrity. Images and search text are sent to the AI services described below. |
| Reports, attribution and rights requests | Sticker reference, reason, notes, account or fingerprint identifier; evidence and correspondence; moderator decisions | Investigate reports, correct attribution, protect rights and resolve disputes; legitimate interests, or compliance with legal obligations where applicable (Article 6(1)(c)). |
| Optional analytics | Page navigation, interaction events such as votes or submission/Telegram buttons, browser and device information, pseudonymous identifiers, signed-in account identifier, sign-up/submission events and technical exceptions | Measure usage and diagnose errors with PostHog, only with consent (Article 6(1)(a)). Refusal does not block the service. |
A browser fingerprint is derived from browser/device characteristics using the FingerprintJS library and cached locally. It is a pseudonymous identifier, not anonymous data and not the same identifier as PostHog analytics. The application may associate prior votes and uploads with your account automatically after sign-in. Rejecting PostHog does not disable this functional identifier or undo account linking. Its local cache lasts 24 hours; that does not mean the identifier changes every day or that linked database records expire after 24 hours. See the cookie policy for storage details.
Location may be extracted from photo metadata, selected manually, supplied through Telegram or obtained after your browser grants location permission. You can select a sticker's location manually instead of granting browser location access. The publication pipeline normalises images and strips embedded metadata from its canonical JPEG output; the selected coordinates are separately stored and published. Uploaded originals and source photographs used for crops can also be held in storage. Do not rely on metadata stripping to protect information visible within a photograph.
4. Automated analysis and human review
Automated classifiers and image/text models assess relevance and safety, read visible text, detect duplicate images, produce descriptions and generate search representations. A submission may be approved, rejected, held for human review or fail for technical reasons. Results can be wrong, including descriptions, artist attribution and location data. Moderators can review submissions and community reports. Contact us with the sticker or submission reference to contest a moderation result, request human review or correct an error. These tools concern archive publication; they are not used to make credit, employment or similar decisions about you.
5. Recipients and external services
Access is limited to authorised people and service providers for their respective tasks. Public content is also disclosed to visitors and search engines.
- Vercel: website/API hosting, execution, technical infrastructure and the AI Gateway through which AI requests are routed.
- Cloudflare R2 and, where enabled, Cloudflare Images: uploaded image storage, delivery and image processing.
- Clerk: registration, authentication and session management. Sign-in details may be processed by an external identity provider you select.
- AI providers through Vercel AI Gateway: the current pipeline uses Google Gemini models for image understanding and embeddings, and a Typesafe AI safety classifier with a Google fallback. Image bytes, visible text, descriptions or search queries are sent as required by the task. This notice does not promise that provider retention is zero or that their services run only in Europe.
- Mapbox: map rendering and location search. Your browser connects to Mapbox and sends technical request information, map views and search text; browser location may be used when you permit it.
- OpenStreetMap Foundation's Nominatim service: reverse geocoding of sticker coordinates into place/address information.
- Upstash Redis: API and Telegram bot rate limiting and abuse prevention.
- PostHog: optional browser analytics and diagnostics, subject to your analytics choice.
- Telegram: messaging and delivery of submissions made through the bot. The operator also stores conversation state needed to handle the submission flow.
- Database, bot hosting, backup and support infrastructure providers, authorised advisers and authorities where required for their functions or by law.
Providers processing personal data on our behalf must be covered by appropriate processing arrangements. Some providers, including messaging or sign-in services, may also act as independent controllers for their own purposes. Public image links should not be treated as private storage, even when an image is not listed in the gallery.
6. International transfers
Services may process data outside the European Economic Area. An EU-only processing region is not promised by this notice. Where a restricted transfer takes place, an applicable adequacy decision or appropriate safeguards, such as the European Commission's standard contractual clauses and necessary supplementary measures, are required. Contact us for information about recipients, processing locations and applicable safeguards, or to request a copy of the relevant safeguards.
7. Retention
We use the following purpose-based criteria; we have not adopted uniform fixed periods for accounts, operational logs, backups or analytics. A browser preference expiry is not the retention period for server-side personal data.
- Accounts and participation records: for as long as needed to operate the account and its requested features. On a deletion request we assess removal or anonymisation, including linked votes, attributions and contributions, subject to legal duties and necessary protection of rights.
- Published archive material: while it remains part of the archive and its publication remains justified. An account deletion request and an image removal request are assessed together where relevant, but removing an account does not necessarily remove every work that can lawfully remain in the archive without identifying the account holder.
- Pending/reviewed submissions, reports and moderation records: for handling review, correction, repeat abuse, disputes and accountability. Rejected material is not treated as a permanent public archive.
- Temporary uploads: the current cleanup code makes unreferenced temporary uploads and unused source images eligible for deletion after 24 hours. It also cleans unreferenced upload files attached to rejected or failed submissions after 24 hours. Cleanup is scheduled and bounded; retries or outages may delay deletion. Referenced source photos, database submission records and moderation logs have separate retention criteria.
- Bot conversation state: while needed to complete or recover the submission flow and handle operational issues. Telegram's own message retention is separate.
- Technical logs, rate-limit records and backups: for troubleshooting, security, recovery and legal needs; backups follow their rotation and are not a substitute for active account records. Necessary restrictions must be applied if data awaiting removal are restored.
- Analytics: only for usage analysis and diagnostics for as long as needed for those purposes; consent withdrawal stops future consent-based collection but does not automatically erase previously received events. Contact us to request erasure where applicable.
- Rights requests and disputes: for handling the request and any applicable legal duties or limitation periods.
8. Choices, required data and rights
Browsing does not require an account. Some features require sign-in, a photograph, a location or a functional identifier; without the necessary input we may not be able to provide that feature. Optional profile fields and PostHog analytics are not required. Avoid placing personal or sensitive information in image descriptions, search queries, reports or profile fields unless necessary for the request.
You can request access, correction, erasure, restriction and, where applicable, portability of your data. You can object to processing based on legitimate interests on grounds relating to your situation. You can withdraw analytics consent at any time through Cookie preferences, without affecting the lawfulness of earlier processing. A browser location permission can be revoked in browser settings; this does not remove coordinates already submitted.
Email help@nomadesrl.it and identify the relevant account, Telegram submission, sticker or browser contribution as far as possible. Do not send passwords or authentication tokens. We may request proportionate evidence to verify your identity or rights. You may lodge a complaint with the Italian data protection authority or your competent supervisory authority. Public copies held by search engines or other people may require separate removal requests.
9. Changes
We update this notice when the service or its processing changes and identify the revised version. A notice update alone does not authorise new optional tracking or reset an existing analytics rejection.