BrickZoid

Privacy Policy

Your photograph is processed on your own device and never uploaded. There is no server to upload it to.

Images

Decoding, cropping, resampling, colour reduction and colour matching all run in your browser. The picture lives in memory for as long as the tab is open and goes away when you close or reload it. We never receive it and never see it.

A saved mosaic file is written to your device by your browser, and contains the grid, the palette and the settings — not the source photograph.

Cookies and local storage

BrickZoid sets no cookies at all, and by default writes nothing to local storage, session storage or IndexedDB. That covers the advertising script described below as well as the pattern tools themselves: unless you ask it to, it stores nothing on your device, and it is sent no cookies when it fetches an advert. There is no sign-in, no account and no profile, so there is nothing about you for us to store.

The one exception is a switch you turn on yourself: Keep this draft on this device, on the pattern screen. While it is on, your browser keeps a copy of the pattern in its IndexedDB storage — the chart, the palette, the settings and the pattern's name, the same things a saved pattern file holds — so a refresh or a closed tab doesn't lose your work. It never holds the photograph, and it never leaves your device. Turning the switch off, or choosing Discard when BrickZoid offers the draft back, deletes it; so does clearing this site's data in your browser.

Analytics

There is no analytics package and no tag manager. Nothing here measures or reports what you do with the site — not which photograph you chose, which settings you picked, or whether you exported anything. The one thing reported off the page is whether the advert was actually on screen, described next.

Hosting logs

Cloudflare Pages hosts the site and keeps ordinary web server records — IP address, time, user agent — in order to deliver pages and resist abuse. We do not enrich those records or use them to identify individuals.

Advertising

BrickZoid carries one advert, served by AppRing. It sits beside the legend on the pattern screen, in a fixed place chosen by us, and it is the only one: nothing is injected automatically, and the upload and setup screens carry no advertising at all. Nothing is requested from the advertising network until you reach the pattern screen, so simply visiting the site contacts nobody. Google AdSense is no longer loaded here.

The advert is plain text — an emoji, a headline, a line or two, and a link. There is no image, no iframe and no tag of its own inside it, so it cannot load anything further or watch the page around it.

To fill the slot, the page asks api.appr.ing for an advert. That request carries no cookies and nothing identifying; like any request to any server, it does reveal your IP address, your browser’s user agent and the page you were on. Once the advert has been at least half on screen for a second, the page sends AppRing a short note saying so, so that an advertiser is billed for adverts people actually saw. That note says only which advert was shown. It is the only thing this site sends anywhere about your visit.

The advert is not personalised. Nothing about you is sent, nothing is stored on your device, and nothing here builds a profile of you.

Block it with any content blocker if you would rather not have it — or if the network is simply unreachable, which comes to the same thing. The slot collapses to nothing and the pattern tools work identically, because they never depended on it.

Children

BrickZoid is not aimed at children under 13, and collects no personal information from any visitor regardless of age.

Updates

Revisions appear on this page. Ask anything at contact@sbsys.com.

Last updated October 2026.