Privacy & cookies
This describes exactly what the app does — not a template, not legalese. If something below ever stops being true, that's a bug in the app, not in this page.
Cookies
None until you log inBrowsing the map, searching, and viewing profiles sets zero cookies. No account needed for any of that.
If you generate or log into an account, one first-party cookie is set — it holds your login session and nothing else. It's not readable by any other site, isn't used for advertising or analytics, and nothing is shared with a third party. There are no tracking cookies, no cross-site cookies, and no cookie banner because there's nothing to consent to beyond "stay logged in."
Bot verification
Two forms onlyTwo forms — creating an account, and submitting a new artist, studio, or event listing — run a Cloudflare Turnstile challenge plus a hidden honeypot field before they're accepted, to keep scripted spam out. Browsing, searching, and viewing profiles never touch this at all.
We picked Turnstile specifically because it doesn't plug in a third-party device-fingerprinting partner or do cross-site tracking. It's the one place a third party (Cloudflare) is involved anywhere in this app, and only on those two forms.
What's stored, and why
By feature- Account: a randomly generated username and a passphrase-derived login credential. No email required, ever.
- Recovery passphrase: a 16-word phrase generated for you at signup and shown exactly once — we store only a hash of it, never the words themselves. Entering it later resets your password and issues a brand-new recovery passphrase; the one you used stops working immediately. No email involved at any point.
- Starting map location: only stored if you explicitly set one in Account — used only to open the map there for you next time. Never inferred from your IP or device.
- Favorites: private. Never shown to anyone else, never used as a public signal or ranking factor.
- Listings you submit (artist/studio/event profiles, portfolio images, contact info) — whatever you explicitly typed in, reviewed by a human before it's public.
- Guest spots and travel dates: if you're an artist, a studio you request a guest spot at and the dates you enter, and any travel dates you post — same review model as any other listing, and auto-removed 7 days after they're over (see below).
- Favorite-based alerts: favorite an artist or studio and you're notified in-app when they book a guest spot, reopen for bookings, or post a new event — no location involved at all.
- Nearby event alerts: an off-by-default preference, only usable if you've set a starting location — we compare that location to a new event's to decide whether to notify you, nothing about your location is shared with anyone else.
- Review outcome alerts: you're notified in-app when your own submission is approved (goes live), rejected, or later suspended or removed by a moderator — reason included each time, no need to keep checking back manually.
- Request alerts: notified in-app when someone requests to join your studio or perform at your event, and again once you (or they) accept — the studio/event side always has to explicitly confirm before it's public.
- Studio address reports: if 3 or more people report a studio's address as wrong or no longer existing, we record when that threshold was hit and notify the owner — they get 7 days to confirm it's still accurate with one click before the listing is automatically unlisted, and can always confirm later to relist it.
- Reports you file — on a listing or on a single photo — are visible only to moderators and admins, never public.
Account lifetime & deletion
Self-service- You can delete a single listing without touching your account: from that listing's own page, confirmed by re-typing its exact name plus your passphrase. Immediate and permanent — there's no undo and no moderator involved.
- You can delete your whole account, any time: Account → Settings → Delete account, confirmed by re-entering your username and passphrase. It's immediate — no waiting, no support ticket.
- What happens to your listings when you delete your account (as opposed to deleting them yourself, above): an artist profile (and every image on it) is deleted outright — it's tied to one specific person, so there's no plausible new owner. A studio or an event you submitted stays live but loses its owner; a moderator can manually link a new account to it any time someone comes forward who can actually speak for that business (e.g. new staff). If nobody claims it within 14 days, it's deleted.
- Empty accounts auto-delete after 14 days: if an account never gets a starting location, a favorite, or a submitted listing, it's automatically removed two weeks after creation. Using it for anything at all stops that — this only clears out accounts nobody ever came back to.
- Past events, guest spots, and travel dates are deleted 7 days after they end — not just hidden from search, actually removed from the database, including any images attached to a past event. Data minimization: there's no reason to keep a record of where you were once it's no longer useful to anyone browsing the map.
Image uploads
Always strippedEvery image is re-encoded in your own browser before upload — this strips all EXIF metadata (GPS coordinates, camera/device info, timestamps) automatically, as a side effect of how the compression works, not an optional setting. The original file you picked never leaves your device; only the stripped, resized copy is uploaded.
What we don't do
Never- No analytics or tracking scripts of any kind (the bot-verification check on signup/listing forms above is the one exception, and it never tracks you across sites or visits).
- No advertising, no ad networks, no retargeting.
- No selling or sharing data with third parties.
- No public ratings, reviews, likes, or follower counts.
- No algorithmic ranking — results come only from your filters.
One thing outside our control
Infra-level onlyOur hosting (Vercel) and database (Supabase) providers keep the standard infrastructure-level server logs any web host keeps (things like request timing and IP addresses, for abuse prevention and uptime) — this is normal for any web service and happens below the application layer described above. Our own code never reads, stores, or builds any feature on top of those logs.