Recognition without an account.

What the public sees

The public map shows aggregate recognition counts and an approximate city-level location. It does not publish names, email addresses, IP addresses, browser tokens, device fingerprints or precise GPS coordinates.

Location

The site does not request device GPS. On the deployed service, the hosting provider supplies an approximate location derived from the network request, such as city, region and country. When approximate latitude and longitude are available, they are rounded to a coarse grid before storage and display.

Duplicate and abuse prevention

Your browser creates a random local token. The server also receives coarse technical characteristics such as operating-system family, screen characteristics, processor concurrency, time zone, touch capability and a normalized graphics description. A network address is processed while the request is handled. The server converts these values into keyed cryptographic hashes for duplicate and abuse prevention. Raw device characteristics and raw IP addresses are not stored in the participant database.

These hashes are pseudonymous technical identifiers. They are not displayed publicly and are not intended to identify a person by name.

Referral links and private impact

If you arrive through a referral link, the browser can keep that referral code locally for up to 30 days so the first stored referral can be credited if you later complete a recognition. The project does not need to store a database record for a link click.

After recognition, the site may provide a public referral code and a separate private impact token. The public code can be shared. The private token is the credential for your impact dashboard and is placed in the URL fragment so it is not sent as part of a normal page request or referrer. The database stores only a cryptographic hash of that private token.

The impact dashboard shows aggregate counts and places for recognitions attributed to your link. It does not reveal participant names, IP addresses, browser identifiers, device hashes or precise locations.

Cloudflare Turnstile

The recognition form uses Cloudflare Turnstile to distinguish legitimate interaction from automated abuse. Cloudflare processes technical request and browser information necessary to provide that security service. A Turnstile verification token is checked by the 1915.world server before a recognition can be recorded.

Stored participant record

A successful recognition stores the approximate public location, creation time, recognition status and privacy-preserving anti-duplicate hashes. The project is meant to be a persistent public record, so active recognition records are retained unless they are removed for abuse, legal reasons or a valid deletion request that can be matched to the record.

Service providers

The site currently relies on Vercel for application hosting, Supabase for the database, Cloudflare Turnstile for anti-abuse verification and OpenFreeMap for map tiles. Those providers may process network and operational data under their own privacy terms when delivering their services.

Sale and advertising

1915.world does not sell participant data and does not use recognition records for targeted advertising.

Questions or requests

For privacy questions or requests, contact contact@1915.world. Because the project does not require an account or identity, we may need enough information to safely locate the relevant record without exposing another participant's data.