Privacy Policy

Effective July 7, 2026 · Written by humans, in plain English.

The short version: Snailsy accounts are pseudonymous (your username is your only public identity), the extension never reads the content of the pages you visit, never captures payment details, never sells data, and can delete everything you've contributed with one click.

What changed on July 7, 2026: trails can now anchor to a specific page, not just a whole site. To show you a page's trails, the extension now sends the page's normalized web address (tracking and session codes stripped) instead of only the domain. A settings toggle ("Check individual pages") returns it to domain-only, and everything below describes both modes honestly.

What Snailsy is

Snailsy is honest insight from people you trust, built on Snail Trails: short thoughts members anchor to websites, or to a single page of one. Members follow each other, see their network's trails in a feed, comment on them, and give ❤️ loves. The extension never reads, scans, or modifies the content of the pages you visit - it looks only at the tab's own web address, so it can show that page's (and site's) trails and let you know when there are some.

The "heads-up" feature

So you don't have to click the snail on every page, the extension can badge its toolbar icon, show an on-page banner, and notify you when a member - or a hashtag - you follow has trails where you are. To do that it checks your current tab's address against the trail map:

With "Check individual pages" on (the default): the page's normalized address is sent - the domain plus the page's path, with fragments, tracking parameters (utm_*, click IDs) and session/token-like codes stripped first. Links that look personal or temporary are reduced to the domain automatically.
With it off: only the domain name (e.g. ticketmaster.com) is sent - exactly how Snailsy worked before page trails.
Signed in: the check includes your membership solely so Snailsy can tell you when members you follow - or hashtags you follow - have trails there. Signed out, checks are anonymous.
Never: page contents. And lookups are answered and forgotten - they are not stored as a browsing history.

The badge, notifications, banner, and page-level checks each have their own switch in the extension's Settings; turning them all off disables checking entirely.

What we collect (and why)

Your account. An email address (login + password resets only - never shown to other members, never used for marketing) and your chosen username, which is your only public identity.
Trails you choose to leave. The text you write, its tag, and the site - or the specific page - it's about. Trails are public by design and appear under your username. Emails, card numbers, and long ID numbers are scrubbed from trail text automatically - on your device and again on the server - and page addresses are stripped of tracking and session codes before they're saved.
Comments you write. Public, under your username, on the trail they reply to - with the same automatic PII scrubbing as trails.
Loves, follows, and reports. Which trails and comments you ❤️, which members and hashtags you follow, and anything you report - all tied to your account so you can undo them or delete everything at once. Loves you give are publicly visible; your follower and following lists are public by default but one profile switch hides them from everyone but you; reports are never public.
Your avatar. An emoji you pick from a fixed set - no photo uploads, so there's nothing to trace back to you.
@mentions and #hashtags you write. Mentioning a member notifies them; hashtags in your trails are indexed so members who follow that topic can find them. Both are parsed from the public trail text you already chose to publish.
An anti-spam stamp. Leaving a trail includes a proof-of-work stamp - a small math puzzle your browser solves invisibly. It contains no personal data; it's compute, not identity. Submissions are also rate-limited per device and per network (network addresses are checked as one-way hashes and never stored raw).
Waitlist email (only if you sign up on this website). Used solely to email you about Snailsy launches. The list is write-only from the web - no client can read it back.

What we never collect

No page content, ever - the extension never reads the pages you browse, only their addresses.
No browsing history. Your current tab's normalized address (or, with page checks off, just its domain) is used to look up trails and then forgotten - lookups are not logged against you, and nothing is stored unless you leave a trail.
No tracking or session parameters - they're stripped from addresses before any lookup, and personal-looking links are reduced to the domain.
No real names or addresses - membership is a username, an email, and a password.
No payment data of any kind.
No ad identifiers, no fingerprinting, no third-party trackers - including on this website.

Trails, comments, loves, and follows are public

Anything you write in a trail or comment is visible to everyone - in the extension and on this website - under your username, as are the loves you give and the members you follow. Don't put personal information in trails or comments; our scrubbers try to catch it, but the best protection is not writing it.

We never sell data

Not raw, not "anonymized," not aggregated for marketers. We also take no money from the websites trails describe - no affiliate fees, no ads - because that conflict of interest would defeat the point of Snailsy.

Deleting your data

Extension Settings → "Delete all my data" removes every trail, comment, love, follow, and report you've made from the map. To delete the account itself (email + username), write to hello@snailsy.app - we process deletions within 30 days.

Where data lives

Trails, comments, loves, follows, and the waitlist are stored with Supabase (Postgres, US region). Clients can only reach the data through narrow, rate-limited functions - the underlying tables are not readable or writable directly by any client.

Changes

If this policy changes materially, we'll say so prominently on this page and in the extension before the change takes effect.

Contact

Questions, concerns, deletions: hello@snailsy.app. The full source code is on GitHub.