BBlanket

PRIVACY BY DESIGN

Your screenshot stays
in your browser.

Blanket’s current editor is designed to process screenshots on the device you are using. The image does not need to be uploaded to an application server.

⌾
Current private-preview architecture

Text recognition, cover placement, color sampling, editing, and PNG export happen in your browser session.

01

Local screenshot processing

The editor reads your selected image inside the browser. Blanket does not currently transmit that screenshot to a hosted image-processing service.

02

No screenshot library

The free preview does not create a cloud gallery or retain uploaded screenshots after the browser session ends.

03

Export stays under your control

When you export, the browser creates the PNG and downloads it directly to your device.

04

Accounts are separate from screenshots

Supabase securely stores account identity and plan information. Screenshots remain local unless a future saved-project feature is explicitly enabled.

PLAIN-LANGUAGE POLICY

What this preview does—and does not do.

Information processed

Screenshot pixels are temporarily read by your browser to detect text, sample nearby colors, display editable covers, and create an exported image.

Account information stored

Supabase Auth stores your email, encrypted password credentials, confirmation status, account profile, and Free or Pro plan assignment. Blanket never receives your plain-text password.

Third-party model files

The browser may download the text-recognition components needed to run detection. Your screenshot itself is not sent with that download.

Before commercial launch

Blanket will publish complete terms, a formal privacy policy, retention periods, subprocessors, and enterprise security documentation.