etrobeads
  • Gallery
  • Prism
  • Tutorials

Privacy

Local-first, with clear account boundaries.

Effective date: 2026-09-26

Local browser use stays private by default. Account, Prism cloud, and paid features add server-backed data only when you choose to use them.

In one paragraph

RetroBeads is local-first by default. Images are processed in your browser, and local projects stay on your device unless you explicitly choose a Prism project backup. A backup can include project data and, when available, a normalized working image; the original full-resolution upload stays local. My Beads sync and public pattern publication are separate, explicit account features. When you make an account, we store what that account needs. And so we can tell whether the site and app are working for people, we use a simple visitor counter on both the website and the app. It counts visits — it stores no cookies, and it can't tell who you are. We don't sell your data, we don't run ad trackers, and we don't record your screen.

What stays in your browser

  • Local source images, conversion work, projects, and preferences by default; explicit Prism project backups, My Beads sync, and public pattern publication are separate choices.
  • Local backups, local imports, and client-side PDF exports.
  • Your theme choice on this site, stored in localStorage.

What account and cloud features may store

When you use account or Prism features, they may store:

  • Your account identifier, email address, session data, and provider metadata through Supabase Auth.
  • Privacy, Terms, and account-age acknowledgement versions with acceptance time.
  • Project metadata, derived pattern data, and an optional normalized working image when you explicitly choose Back up project or Update backup in Prism. The original full-resolution upload stays local; My Beads sync and public pattern publication are separate features.
  • Security, rate-limit, and operational logs needed to run the service and reduce abuse.
  • Billing and entitlement records if you buy a paid feature. Paddle is our Merchant of Record: it sells and invoices paid subscriptions. To create and manage a purchase, RetroBeads shares the buyer details needed for that purpose, including your account reference, email address, selected price, and language. Paddle processes payment details; RetroBeads does not receive or store your card number.

What we avoid

  • No sale of personal data.
  • No ad pixels, heatmaps, fingerprinting, or session replay.
  • No server-side conversion of your images in the planned account flow.
  • No retention of original full-resolution uploads as cloud originals.

How we count visits

So we can tell whether the site and app are actually working for people, we use a simple, privacy-friendly visitor counter on both the website and the app.

What it does: counts visits to the app's start page and all pages on the marketing site. It stores no cookies and can't link a visit to a person.

What it never sees: This visit counter does not receive your images, patterns, projects, file names, or anything you make. Optional project backups, My Beads sync, and public pattern publication are disclosed separately.

Being straight with you: like every website, the counter works over the internet, so rough things like your country can be estimated from your connection. That's why we call it privacy-friendly, not invisible. We don't try to identify you, and we don't keep a record of who you are.

Providers we use

RetroBeads uses Cloudflare for hosting and private cloud file storage, and Turnstile for bot checks. Account data is handled with Supabase. Paddle is our Merchant of Record: it sells and invoices paid subscriptions and handles checkout, payment processing, tax, receipts, and subscription management. To set up and manage a purchase, we share the buyer's email, selected price, language, and account reference with Paddle.

Paddle buyer terms · Paddle privacy notice

Your choices and rights

You can use RetroBeads locally without an account. Account controls provide a machine-readable export and a way to request account deletion. If Prism access ends, existing cloud projects enter a 90-day lockbox where you can read, restore, export, or delete them but cannot add new cloud writes; remaining cloud data is deleted when that window ends. Account deletion removes cloud objects and public output RetroBeads controls; local projects on your device are unaffected. Use the Paddle portal linked from your account to view invoices, update payment details, or cancel a renewal. For refund or withdrawal requests, follow the buyer-support route in your Paddle receipt or terms, or contact RetroBeads support. Deleting your RetroBeads account does not delete Paddle's financial records; Paddle retains them under its own obligations.

Preference cookies

The rb_www_locale and rb_billing_country cookies remember your language and billing-country preferences in this browser across retrobeads.app subdomains for up to one year. They are set only when you choose a preference and contain only a language or country code, with no tracking or personal data. SameSite=Lax and Secure. Until you choose a country, this browser may also keep an approximate country code in local storage to show local prices; checkout confirms the final billing country.

Questions

For privacy questions, account-data requests, or deletion help, email support@retrobeads.app.

etrobeads© 2026 RetroBeads · A small tool for makers.
ChangelogPrismPrivacyTermsContact
EnglishSvenska