Privacy policy · effective 29 September 2026

No account. Your browser work stays local.

Pebbleback saves browser work locally so you can close and resume developer and research tasks without losing your place. It does not require an account or operate a browser-work backend, and it does not automatically send your saved browser context anywhere. A separate minimal licence service handles optional Pro purchases without receiving browser-work data.

Data Pebbleback stores

Pebbleback stores this data locally in your browser:

Pebbleback does not capture page contents, passwords, form values, cookies, screenshots, or your full browser history. It does not index your general browsing activity, and it does not run analytics or telemetry on the URLs or notes you save.

Where data is stored

Pebbleback stores Trail history and checkpoints in local IndexedDB in your browser profile. Recovery data, preferences, and compact status values use local browser extension storage on your device.

Pebbleback's code stores this data using the browser's local, on-device storage APIs. It is not written to the browser's synced-storage area, so Pebbleback does not, on its own, copy your saved workspace data across your signed-in devices; whatever appears on another device is that device's own separate local copy. Pebbleback does not operate a browser-work backend, does not create a Pebbleback account, and does not send your saved browser context to Pebbleback or any Pebbleback-operated server.

Purchases and licence activation

Pebbleback offers an optional paid annual subscription: Pebbleback Pro (£29/year Founder pricing). All core work-memory, crash recovery, and data access features remain permanently free. Checkout is handled entirely by Stripe on Stripe's own secure hosted pages; Pebbleback opens that checkout only when you explicitly choose to upgrade, and a minimal licence service verifies the Stripe payment and issues a cryptographically signed licence file.

That licence service does not receive or store any of your browser-work data (your Trails, checkpoints, projects, notes, URLs, or Context Packs). Licence activation is an offline cryptographic signature check performed locally in your browser: it makes no network request and stores no personal identification. Your browsing history, URLs, titles, Trails, checkpoints, projects, notes, Context Packs, and search queries are never sent for licensing. Licence verification does not run in the background, and there is no recurring telemetry heartbeat.

Backups

Pebbleback can export local JSON backups that you control, and you can import a previously exported file to restore it. Current backups are local and manual only; Pebbleback does not upload a backup anywhere on your behalf.

Any future user-owned backup provider, such as Google Drive or GitHub, would need to be explicitly enabled by you. Pebbleback will disclose the destination and requested permissions before any such provider backup is used, and none is offered today.

Favicons

Pebbleback does not load remote favicon URLs in its own interface; favicon addresses may be retained as browser-provided tab metadata for backup fidelity, alongside the rest of a saved tab's details.

How Pebbleback uses your data

Pebbleback uses saved tab metadata and notes only to provide the extension's own user-facing features:

Pebbleback does not sell data, does not use data for advertising, and does not transfer data for purposes unrelated to these features.

Permissions

Pebbleback's browser permissions and why each is requested
Permission Type Why Pebbleback requests it
tabs Required Read tab metadata (title, URL, domain, pinned state), focus the correct destination tab or window, safely close individual tabs, and restore saved tabs.
storage Required Save projects, research sets, Trail status, tab metadata, notes, and local recovery data on your device.
sidePanel Required Show the Pebbleback workspace in the browser's side panel.
sessions Optional Only requested if you explicitly select "Allow enhanced recovery." Lets Pebbleback check Chrome's own recently closed sessions to restore a missing window more faithfully after a restart. Declining it leaves Pebbleback's existing whole-checkpoint restore fully available.

Pebbleback has no required host permissions and no optional host permissions, for its core features or for purchase and licensing.

Human access

Pebbleback developers cannot read your saved browser context because it is not sent to Pebbleback. If you choose to email an exported backup file to support, that file may contain the tab metadata and notes listed above, and whoever reads that email can see it.

Contact

Questions about this policy or requests concerning Pebbleback can be sent to nihal@cloudzzy.co.uk.