Privacy
How Marbls and the Marbls browser extension handle your data.
Marbls (marbls.app)
When you create an account we store your email address, username, and — for password accounts — a hashed password. Your library, profile, ratings, and submissions are public by default; you can make your library or feed private in settings. We use a first-party analytics tool (Umami) that records anonymous, aggregate usage and does not track you across other sites. We do not sell your data or share it with advertisers.
Submitted product URLs may be checked against Google Safe Browsing to screen for malware and phishing. Questions or deletion requests: hello@marbls.app.
Marbls Library — New Tab (browser extension)
Last updated: 18 July 2026
What it stores
The only information the extension stores is the Marbls username you enter in its settings. It is saved with the browser's storage API (synced to your own browser profile) so the extension knows whose library to display. This value stays in your browser.
What it sends
To show your library, the extension makes read-only requests to marbls.app — to fetch your public library and the product logo images shown on the new tab page. Your username is included in these requests solely to identify which public library to load. No sign-in, cookies, or credentials are involved.
What it doesn't do
The extension does not collect analytics, does not track your browsing, does not run any remote code, and does not share or sell any data. It contacts no server other than marbls.app, and only to fulfil the function above.
Questions: hello@marbls.app.