What we store, and what we do not

What BLOKZA stores

Two things, and it depends entirely on whether you have signed in: the document you are editing, and — only if you have an account — the email address you used to create it. There is no analytics script on this site and no advertising network. Nothing is sold or shared for marketing.

What stays in your browser

An account is required to open the editor, but the document you are editing still lives in your browser's own storage, under the key altask:builder:v3. That local copy is written on every edit and is what makes the editor work offline; it reaches our servers only when you save the site to your account.

Clearing your browser's site data removes it permanently. We cannot recover a document that was never sent to us, because we never had a copy.

Using BLOKZA with an account

Signing in creates an account holding an email address and a password. The password is hashed by our authentication provider; it is never stored or transmitted in a form we or anyone else can read.

Sites you save to your account are stored as a single JSON document per site. Access is enforced at the database level by row-level security, which compares the signed-in user on every request to the owner recorded on the row. A request without your session cannot read your rows, and neither can another account.

Your browser also keeps a session token so you stay signed in between visits. Signing out deletes it.

Third parties that see a request

Loading a page necessarily reveals your IP address to whoever serves it. The parties involved here are:

• Cloudflare — serves this site and the editor.
• Supabase — stores accounts and saved sites. Contacted only when you are signed in.
• Google Fonts — serves the two typefaces this site uses, from fonts.googleapis.com and fonts.gstatic.com.
• Formspree — receives whatever you type into the contact form, and only then. It is not contacted by simply loading a page.

Sites you publish

A site you publish is plain HTML and CSS. It contains no tracking, no runtime and no script from us, so visitors to your published site are not measured by BLOKZA in any way. If you add an analytics tag or embed of your own, that is between you and whoever provides it, and your site will need its own privacy notice.

Keeping and deleting your data

Saved sites are kept until you delete them. Deleting a site in the Cloud panel removes it from the server; a copy in your own browser is untouched and has to be cleared separately.

Ask us to delete your account and we remove the account and every site attached to it. Because sites are linked to the account, deleting the account deletes them too.

Your choices

You can export every site you own as files at any time, from Publish — the export is the complete site, so you are never locked in. You can ask for a copy of what we hold, ask us to correct it, or ask us to delete it.

Getting in touch

Write to privacy@blokza.com for anything on this page, including deletion requests. We answer people, not tickets.