Answers, withoutthe breathlessness.

CurbPage, CurbPlace, CurbTube and CurbTime are the current CurbApps products. The maturity label on each product card tells you whether a store build is available. Password management now lives in CurbPage and CurbPlace, while shared viewing lives in CurbTube.

No. Each extension is local-first and useful the moment it is installed. A CurbApps account adds opt-in Premium sync across your devices, encrypted storage, and shared sessions.

You can sign in with Google or use an email address and password. Supabase handles authentication for CurbApps, while your encrypted product data stays in the separate sync data plane.

Chrome, Firefox and Edge, across the whole suite. Every extension targets the same three browsers, so the surface set on your second machine matches the first.

On the device, in the extension’s own browser storage. Bookmarks, notes, snippets, one-time passwords and settings never leave that storage unless you explicitly enable Premium sync. Uninstall the extension and the data goes with it.

Yes. Local-first means the core of each product opens without a server round-trip. Network features are the honest exception: CurbTube’s SponsorBlock data and shared sessions need a connection.

Bookmarks, notes, snippets, profiles, passwords, OTP accounts, clocks, and their linked metadata travel end-to-end encrypted to your other browsers and the companion app. The dashboard coordinates the account, while a separate data plane carries ciphertext.

Sync pauses, but every device keeps working from its local store. Cancelling removes the connection, not the local content. Re-subscribe and sync resumes.

Products that expose a local export let you download that data from the product itself. A single encrypted dashboard export is still under review. For an access or portability request, contact support. Local-only data stays in the browser profile where you created it.

Not today. The data plane is operated by us and only sees encrypted blobs. If self-hosting is a hard requirement, tell us. Demand shapes the roadmap.

The alpha is being built for iOS and Android. There is no public store or web release yet, and sign-in is required to use it.

Bookmarks, plain field notes, CurbTube watchlists, vault entries, OTP accounts, clocks, and CurbPlace tool preferences travel end-to-end encrypted. Sync runs only while the app is open. The Place tab shows the tool-preference shelf but does not run the tool catalog.

Yes. Native builds keep keyring material in SecureStore without biometric access control. Cloud sync requires a master password and its recovery material, and the workspace locks when the app moves out of the foreground.

Yes. The Page tab shows TOTP and HOTP codes after you unlock the workspace with your master password. There is no biometric unlock today.

No. Sync payloads are encrypted client-side with AES-GCM before they leave the device, and raw keys are never uploaded. The server stores and forwards ciphertext, nothing more.

No. Not aggregates, not anonymised sets, not ever. Website analytics are currently disabled, and there are no advertising pixels.

Deleting your CurbApps account removes your synced data from the data plane. On-device data is literally on-device: uninstall the extension or clear its storage, and it is gone.