Privacy, mapped clearly

1. The short version

Most of the pattern maker runs entirely in your browser. Image decoding, color matching, editing, bead counts, PNG export, and print/PDF preparation happen on your device.

The application code does not set cookies. Browser storage keeps language and progress settings, same-session link reuse, anonymous metric delivery markers, and share recovery data: pending pattern data only until confirmation, plus a completed share's SHA-256 content fingerprint, random share ID, and deletion credential until deletion or site data is cleared. You can clear this storage in your browser.

Before a new share request, the creating browser saves the pending pattern data, random share ID, and a separate deletion credential so a lost response can be retried safely. After confirmation, the pending pattern data is removed; the browser keeps the content fingerprint mapped to the random share ID, plus the separate deletion credential, so the same completed link can be recovered across tabs. The credential is not part of the public share link or QR code.

Anonymous product metrics count a small set of successful milestones, fixed error codes, and structured feedback. We do not create user identifiers, store event-level histories, or include your image, pattern contents, file name, title, or author.

We do not sell personal information or share it for cross-context behavioral advertising. Because there is no such sale or sharing, Global Privacy Control and Do Not Track signals do not change the site's behavior.

2. What information goes where

Browser storage is not sent to us merely because it exists. The page reads it locally to restore the feature you used.

3. Optional share links

Creating a share link is optional. If you do, we receive a random share ID and deletion credential, the data version, pattern dimensions, bead brand, compressed color-index grid, selected sheet layers, and any title or author label you enter. The credential is used only to derive a one-way hash and is not stored in plaintext.

We do not receive the source photo, source file name, complete bead inventory, device details, or undo history as part of a share.

Share data is stored in a private Vercel Blob. It is not listed in a public gallery and the Blob URL is not exposed. Anyone who has the unlisted mybeadpattern share URL can load the pattern, so treat that URL like a capability key.

Before a new share request, the browser stores the pending pattern data, a random ID, and a deletion credential, then sends them over HTTPS. The private record keeps only a one-way hash of the credential, and the response does not return it. The credential is not included in the share URL, QR code, public read response, or application logs.

After confirmation, the browser removes the pending pattern data and stores a minimal receipt whose key contains the pattern content's SHA-256 fingerprint and whose value contains only a version and random share ID. This receipt lets another tab recover the same completed link; it contains no pattern payload, deletion credential, QR code, title, or author, and remains until deletion or site data is cleared.

Shared patterns do not currently expire automatically. If this browser still holds the creator credential, use “Delete online copy” in Export. Clearing site data removes that credential, and older shares do not have one. Without the creator credential, neither self-service nor support may delete the online copy; a read-only share URL is not deletion authorization. Contact privacy support only for questions about this policy, and do not put personal information in optional fields.

Deletion replaces the stored pattern, title, and author with a minimal marker containing the random share ID and a one-way credential hash. We retain that marker only to prevent an old or delayed creation request from restoring the deleted share.

4. Technical requests and service providers

When you request a page or API, Vercel may process standard technical data such as IP address, user agent, requested URL, time, status, and security signals. The locale endpoint uses Vercel's two-letter country header only to suggest a language and returns a no-store response.

Our share API writes logs with a request ID, stable result code, HTTP status, request size, and pattern cell count. It is designed not to log pattern contents, titles, author labels, Blob URLs, full share URLs, deletion credentials, or credential hashes.

The metrics API accepts only documented event names and fixed enum values, then immediately increments daily aggregate counters in Upstash Redis. It rejects extra fields and does not log event payloads.

We use Vercel to host the site, API, and private share storage, and Upstash to keep anonymous aggregate counters. Support email is forwarded by Namecheap and then handled by the destination mailbox provider. These providers may process data in countries where they operate under their own terms.

We use information only to provide and improve requested features, keep the service secure and reliable, respond to messages, and meet legal obligations. We do not use automated decision-making or profiling.

Where applicable, we rely on legitimate interests to operate and secure the service, on your request or consent for optional sharing and support, and on legal obligations when required.

5. Children and families

The core editor can be used without an account and without transmitting a source photo. If you are under 13 or under the digital-consent age where you live, ask a parent or guardian before creating a share link or emailing support.

Children should not enter a real name, contact information, school, or other identifying details in optional fields. A parent or guardian can ask us to delete a shared pattern or support message by contacting us.

You never need to attach the image you uploaded. Source photos stay in your browser, and support requests should not contain them.

6. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or obtain a copy of personal information, and to complain to a local authority.

Send requests to support@mybeadpattern.com. A complete share URL helps us locate data but does not prove creation. New shares should be deleted with the creator credential held by the creating browser. We cannot delete older shares or shares whose credential was lost because they have no reliable creator proof; support will not bypass this credential or ask for your source photo.

You can clear language, build, and session information yourself through browser site-data settings. You can also use the site without creating a share link or sending email.

Clearing site data also removes creator deletion credentials from that browser; it does not delete the online share itself. Delete the online copy first if you still need to revoke its link and QR code.

7. Security, changes, and contact

We use data minimization, strict share validation, private storage, random unlisted IDs, same-origin checks, rate limiting, and logs that omit pattern contents. No online system is perfectly secure.

We may update this policy if features, providers, or legal requirements change. We will change the date above and provide additional notice if a change materially affects how information is handled.