Privacy policy.

Last updated May 2026

Build for One ships two Chrome extensions: PIKA (virtual fashion try-on) and Tab Finder (keyboard tab search). They have very different privacy footprints — both are covered below.

PIKA — Virtual Fashion Try-On

Short version: Your uploaded photo stays on your device. When you generate a try-on, your photo and the garment image are processed on our secure servers solely to render your result — they are not saved. The try-on result image is stored securely on our servers on a temporary basis, only for quality monitoring (verifying try-ons succeed) — never for training, learning, or marketing. We also collect minimal usage data — your first name, an anonymous ID, retailer sites, and basic event counts — to run the beta and improve the product. No account or email required (unless you join the waitlist).

What PIKA is

PIKA is a Chrome browser extension that lets you virtually try on clothing items while shopping online. It is part of Build for One — a small portfolio of products built for personal use and shared publicly.

What stays on your device only

The following never leaves your browser. It lives in IndexedDB and chrome.storage.local, and is wiped if you uninstall the extension or clear your browser storage.

Your uploaded photo — uploaded by you (or selected from sample models). This photo is stored locally in your browser only and never leaves your device. A temporary copy is sent to our servers only at the moment you trigger a try-on (see below), solely to render the result.
Your local try-on history — every result image you've generated, kept in your browser, alongside the product page URL it came from. (A copy of each result is also held temporarily on our servers for quality monitoring — see How try-ons are processed.)
Your preferences — sample-model choice, dev-mode flag, dismissed nudges.

What we collect on our backend

The minimum needed to run a fair, reliable beta and understand how the product is used.

Your first name — entered before your first try-on. Stored against your anonymous ID.
Anonymous ID — a random UUID generated when you install the extension. Not linked to any real-world identity.
Fingerprint hash — a one-way SHA-256 of your IP address, browser, and language settings. Used to recognise reinstalls and prevent abuse. The raw IP and user-agent are also stored, used only for the same purposes.
Country code — derived from edge geolocation (e.g. US, FR). Used for region availability and analytics.
Try-on events — per try-on we log: timestamp, duration, success/failure, error type, garment category, and the domain + URL of the page where you triggered the try-on.
UI interaction events — coarse signals like "panel opened", "photo uploaded", "history cleared". No mouse coordinates, no scroll behaviour, no hover paths.
Waitlist email — only if you choose to submit one when access is full or the beta has ended.

What we do not collect

Your uploaded photo or garment images as stored records — they are processed solely to generate your try-on result, then discarded
Your photos, garment images, or try-on results for AI training, machine learning, model retraining, advertising, or marketing purposes — ever
Browsing history beyond the specific page where you triggered a try-on
Payment, financial, or authentication data
Health, biometric, or facial-recognition data

How try-ons are processed

When you generate a try-on, your photo and the garment image are sent over an encrypted HTTPS connection to PIKA's secure servers. The servers render the try-on result and return it to your browser. Input images are processed solely to generate the result and are not stored.

The try-on result image is stored securely on our servers on a temporary basis, solely for quality monitoring and to verify whether a try-on succeeded or failed. We hold privacy as a core value. Your try-on result is never used for AI training, machine learning model improvement, or marketing purposes of any kind.

Why we collect what we collect

Name + anonymous ID — so the product can greet you and so we can run a fair beta with usage caps per user.
Fingerprint hash — so a user who clears their browser storage isn't accidentally treated as a brand-new beta seat.
Try-on events + domain — so we can see which retailers PIKA works on, and fix sites where it silently breaks.
UI interaction events — so we can understand the activation funnel and improve the parts users get stuck on.
Country — for region availability and per-country analytics.

None of this data is used for advertising or sold.

Tab Finder

Tab Finder is a separate Chrome extension that opens a keyboard-triggered overlay to search every open tab — and every recently closed one — across every Chrome window. It is also part of Build for One.

Short version: Tab Finder collects nothing. Every search, label, and result happens entirely inside your browser. No data is ever transmitted to any server. There is no Tab Finder backend. No analytics, no telemetry, no accounts, no email — ever.

What stays on your device only

Your tab list — read on demand each time the overlay opens, rendered locally inside a shadow-DOM overlay, never sent anywhere.
Your recently closed tabs — read from Chrome's own session list (up to Chrome's 25-session cap), rendered locally, never transmitted.
Your tab labels — saved via chrome.storage.sync, which syncs through your own Chrome profile only. Labels are short user-typed strings tied to a URL.

Permissions and why each is needed

tabs — to read titles, URLs, favicons, and window IDs of your open tabs so they can be searched and switched.
sessions — to read and restore your recently closed tabs.
storage — to persist your tab labels via chrome.storage.sync, scoped to your Chrome profile.

What Tab Finder does not do

Send any data to any server — there is no Tab Finder backend
Run analytics, telemetry, or tracking of any kind
Read page content, DOM, cookies, form data, or browsing history
Show ads, upsells, or paid tiers
Require an account, email, or sign-in
Transfer or sell user data to any third party — ever

Across both products

The sections below apply to both PIKA and Tab Finder.

Your rights (GDPR, CCPA)

Access the data we hold about you — email us; we'll respond within 30 days. (For Tab Finder this returns nothing: we don't hold anything.)
Delete your data — email us; fulfilled within 30 days. (For Tab Finder this returns nothing: we don't hold anything.)
Export your data in JSON format — email us. (PIKA only; Tab Finder has nothing to export.)
Opt out — uninstall the extension. For PIKA, also clear your browser's IndexedDB and localStorage. Tab Finder keeps no local browser storage other than your labels in your Chrome profile.

To exercise any of these rights, email privacy@buildforone.com.

Children

Build for One's extensions are not directed at users under 16. We do not knowingly collect data from children under 16.

Changes to this policy

If this policy materially changes, the next time you open a Build for One extension you'll see a one-time notice with a summary of changes. Continued use after that constitutes acceptance of the updated policy.

Contact

Questions or concerns: privacy@buildforone.com