Privacy Policy

1. What We Collect

a. Public Information

We aggregate publicly available data from platforms such as:

• Social media (LinkedIn, Twitter/X, GitHub, etc.)
• Publicly published content or mentions on the open web

b. User Uploads

When you:

• Upload an image for facial recognition search
• Create an account or sign in

c. Platform Usage Data

To operate, secure, and improve the service, we may process:

• Email address (used for login or access verification)
• Limited first-party product and conversion events, such as a photo being selected, a checkout being started, or a purchase being confirmed
• First-touch attribution limited to the landing-page pathname, referrer hostname, and named UTM values (source, medium, campaign, content, and term)
• If you separately allow advertising measurement: Google ad-click attribution and, after a live completed purchase, its value, currency, fixed query-free payment-measurement pathname, and a non-personal backend order confirmation number; older orders retain their one-way private-ledger reference so the same purchase is not counted twice
• Browser type, country, and session metadata
• If you explicitly opt in to product guidance and offers: your consent choice, consent date, consent-copy version, consent source, delivery status, unsubscribe status, and a keyed digest of your confirmed email address used to enforce suppression without storing that address in the lifecycle tables

First-party conversion analytics exclude uploaded images, search-result IDs, email addresses, full URLs, URL query strings, private communications, phone numbers, home addresses, and messenger IDs.

2. How We Use It

We use this information to:

• Display public profile summaries from search results
• Enable AI-powered facial recognition search
• Process payments and manage your account
• Improve product performance and personalization
• Measure first-party conversion steps using limited, non-sensitive events and attribution context
• Retain separately consented Google ad-click attribution and measure completed Google Ads purchases
• Send the limited product-guidance sequence only when you explicitly opt in, and stop it after withdrawal, a real search, a purchase, or permanent monthly-customer exclusion
• Prevent fraud and ensure security

3. Facial Search & AI

When you upload an image:

• It is processed by a specialist third-party facial-search processor to return candidate public sources
• The original uploaded image is processed for face-matching and is not written to persistent 221B application storage on our servers
• The current search processor states that submitted search images are not added to its public index and temporary search data is deleted within 24 hours
• A compressed thumbnail may remain in your private search history so you can identify past searches
• We do not add your upload to a public facial database or reuse it to train our models
• Search results are based on publicly available data sources

4. Data Sharing

We do not sell your personal information. We may share data with:

• Service Providers: Third-party services that help us operate, including Stripe for payments, a specialist facial-search processor for candidate retrieval, Supabase for account and application data, Resend for opted-in email delivery, and Google Ads for separately consented ad-click attribution and purchase measurement
• Legal Requirements: When required by law or to protect our rights

5. Your Rights

You may:

• Access your personal data
• Request deletion of your account and data
• Request deletion of any uploaded media
• Clear your saved search history yourself from the Search history page
• Opt out of promotional communications
• Withdraw marketing consent without signing in; the unsubscribe link does not ask for additional personal information
• Decline or withdraw optional advertising-measurement consent at any time using the controls below

Contact us at: admin@221b.world

6. Data Retention

• Original uploads: Not retained in persistent 221B application storage after search-task processing
• Third-party processing: Our current search processor states that temporary search data is deleted within 24 hours
• Optional local photo draft: Only if you enable it, your browser stores the selected original photo for a 30-minute continuation window. It is cleared when a search is accepted or you sign out. Expired drafts are removed when the feature next checks storage; you can remove them sooner or clear site data.
• Search history: Retained for your private reference until you delete a report, clear history, or request deletion. You can choose automatic deletion after 30, 90 or 365 days in Settings; scheduled cleanup removes expired reports after that window. The default does not enable automatic deletion. Clearing history removes the saved report, matches, result links, and compressed thumbnail from the active 221B application database. 221B does not keep a separate application copy.
• Private first-party conversion events: Bounded event, pseudonymous journey, page-path, referrer-hostname, UTM, deployment, and experiment records may be retained for product and conversion analysis; they exclude uploaded images, search-result IDs, email addresses, user IDs, IP addresses, and full URLs
• Report tools and requests: Private bookmarks, notes and report-review activity are linked to your account and report. Deleting a report removes these associated records from the active database. Support requests and task states help resolve issues. Account deletion is a reviewed request, not an immediate action; legally necessary payment records, processor systems and backup expiry are handled separately and are not represented as instantly erased.
• Performance diagnostics: First-party measurements contain a bounded page category, device category and page-load responsiveness values, without photos, source URLs, account identifiers or search IDs. Samples are removed after 35 days. Browser security reports are reduced to a directive category; raw URLs and script samples are not stored.
• Marketing consent and suppression: Consent, withdrawal, complaint, hard-bounce, and minimized suppression evidence may be retained for as long as reasonably necessary to prove consent, prevent another send, manage complaints, and meet legal obligations. A keyed email digest is not used to reconstruct the email address.

7. Security Practices

We use:

• Encryption in transit using HTTPS/TLS
• Secure authentication via Supabase
• Role-based access controls
• Secure cloud infrastructure

Despite best efforts, no system is 100% secure — always use discretion when uploading images.

8. Cookies

We use essential cookies and first-party browser storage to maintain your session and preferences. First-touch attribution uses a random journey reference held in this tab for up to 30 minutes and is limited to the landing-page pathname, referrer hostname, and named UTM values; the raw query string is not retained. Short hashed conversion-deduplication markers may use session storage. These references help connect page visits and checkout steps, including after a reload or same-tab sign-in. Sanitized attribution and the journey reference may accompany your Stripe checkout and our private payment record so we can understand completed purchases. Neither browser mechanism stores uploaded images, search-result IDs, email addresses, full URLs, or raw URL query strings.

Google's advertising tag is not requested or initialized unless you separately choose “Allow ad measurement.” After a grant, the base tag may retain Google auto-tag click attribution before checkout and send Google a sanitized tag and click-attribution request. That request uses the page origin and pathname without the URL query string, and it is not a purchase conversion. We allow ad storage only for this attribution and a live, paid, fulfilled purchase conversion. Analytics storage, ad user data, ad personalization, Google signals, remarketing, and enhanced conversions remain disabled. Only after a live, paid, fulfilled purchase does 221B send a purchase conversion containing value, currency, a fixed, query-free payment-measurement page address, and, for newer orders, a non-personal backend order confirmation number. Older orders retain their one-way private-ledger reference so the same purchase is not counted twice. The ordinary address is/payment/success; a short-lived, single-use, server-authorized repair may instead use the unlisted/payment/conversion-replay address after the same payment is re-verified, without a new charge or credit grant. The conversion excludes every payment-page query string, replay token, Stripe session ID, email, photo, user, search, result, and full URL. Google also receives ordinary connection metadata when its tag is loaded. An initial decline or missing choice loads no Google tag and sends no Google request. If you withdraw after a prior grant, the already loaded tag may receive a denial update to stop further measurement.

9. Updates to This Policy

We may revise this policy from time to time. If significant changes are made, we'll notify users through the platform or email where applicable.

10. Contact

For privacy-related inquiries, contact us:

Email: admin@221b.world

Operator: Singula Pty Ltd, ABN 95 694 945 401