Privacy Policy — Stash
THE POLICY

1. Who operates Stash

Stash is an open-source project maintained by Joaquin Terrasa (@espetro). For any privacy question or request, email josocjoq+dev@pm.me or open an issue in the GitHub repository.

2. Data we process

Website (stash.illo.fyi). Anonymous page views, clicks, and feature-usage event names via PostHog's cookieless mode. No cookies, no persistent identifiers, and URL fragments (which can carry shared stash content) are never captured.

Browser extension. Tab snapshots, names, tags, and preferences are stored in your browser's local storage and processed on your device. The only outbound calls are anonymous, aggregate usage counters — sent only when telemetry is enabled (on by default, switchable in the extension's settings).

Tab URLs and titles. Local by default. They leave your device only when you explicitly create a share link — and only in the form that link requires.

3. Share links and the relay

Stash offers two link types. Self-contained links carry the compressed payload inside the URL fragment (#p=…); nothing is stored on our servers and the fragment is never sent in HTTP requests. Short links store an entry on our Cloudflare-hosted relay under an unguessable random 6-character id. A stored entry contains only the payload — plaintext-encoded or client-encrypted ciphertext (zero-trust mode, where the key exists solely in the link's #<key> fragment and never reaches the server) — plus creation and expiry timestamps. No account, IP profile, or user identifier is attached.

4. Anonymous analytics

Both the website and the extension report anonymous aggregate event names (e.g. "stash saved", page views) to PostHog, hosted in the EU. We use these counters to understand feature usage. They contain no URLs, titles, notes, or identifiers. You can turn telemetry off in the extension's settings; the site's analytics use cookieless, memory-only persistence.

5. Google OAuth and the Chrome Web Store

The project operates a Google OAuth app named "Stash" that is used exclusively by the maintainer's release automation (GitHub Actions) to upload and publish extension packages via the Chrome Web Store API. This is maintainer-only automation: it never requests access to end-user Google data, and Stash never asks users to connect a Google account.

6. Local daemon and native messaging

The optional Stash daemon communicates with the browser extension over native messaging. All of that traffic stays on your machine; nothing is relayed to our servers.

7. Retention and deletion

Local data (saved stashes, preferences) stays on your device until you delete it. Short-link entries expire automatically at the link's chosen lifetime and are deleted on expiry; you can also revoke a short link early through the relay's deletion endpoint. We retain no personal data because we collect none.

8. No sale, no advertising

We do not sell data, share it with advertisers, or use it for advertising or profiling.

9. Your choices

Sharing is always explicit: nothing is transmitted until you create a link. You can use self-contained links to avoid server storage entirely, disable telemetry in the extension settings, and revoke short links before they expire.

10. Changes and contact

If this policy changes, the updated version is posted on this page. Effective date: October 7, 2026. Contact: josocjoq+dev@pm.me.

← Back to home Last updated: October 2026