Measure discovery without building a surveillance profile.

Browsing

No consumer account is required

Normal browsing, search, discovery pages, and app pages do not require a CurioBeam consumer account. Restricted Admin authentication is a separate system for CurioBeam editors. Maker accounts are used only for the gated developer claim workflow and do not create a general consumer profile.

Analytics

A small first-party discovery funnel

Public Alpha analytics measure a limited set of product events: searches, filter use, no-result searches, result opens, app views, and clicks to active official app destinations. Keystrokes, hovers, scrolling, clipboard contents, session replay, and full form payloads are not analytics events.

Accepted analytics events use a random first-party cookie named cb_session for up to 30 minutes so CurioBeam can connect a short search → app → outbound journey. The cookie is HttpOnly, SameSite=Lax, and Secure on HTTPS. It is not derived from an email address, login, IP address, device fingerprint, or user-agent string.

Network data

What product analytics does not store

The analytics database does not store raw IP addresses, hashed IP addresses, user-agent strings, browser or device fingerprints, cross-site identifiers, external tracking IDs, or permanent anonymous visitor profiles.

Request addresses can be transformed with a process-random salt and held briefly in process memory for abuse rate limiting; that value is not inserted into the analytics database. EdgeOne Makers maintains separate infrastructure observability outside the product analytics system. Production Log Analysis has been verified to record runtime request data such as timestamp, request ID, requested host/path, HTTP status, execution duration, memory usage, and runtime information. CurioBeam does not treat those platform logs as product analytics or use them to build visitor profiles. The selected Makers log console uses the platform's default 24-hour retention window.

Search text

Bounded, reduced, and automatically expired

Retained search text is bounded to 256 Unicode code points. Obvious email-address patterns and long numeric sequences are replaced with redaction markers before storage. Structured filters are allow-listed and bounded.

Retained raw search text receives a 30-day expiry timestamp. The production database runs a daily scheduled purge that removes query text after it expires while preserving non-query event metrics. The scheduled operation has been verified with an actual expired-row run. Because the purge runs daily, this notice does not promise deletion at an exact second after the 30-day expiry point.

Submissions

The public submission form asks for an app URL

The public submission flow accepts an app URL without an account or payment. It also contains a hidden anti-bot honeypot field. The form does not ask for a submitter name, email address, or marketing profile. Submitted product URLs enter CurioBeam's review workflow and may be matched to an existing product to avoid duplicates.

Maker accounts

Passwordless identity is separate from app authority

When Maker authentication is enabled, CurioBeam uses passwordless email sign-in through Supabase Auth. Supabase Auth processes the email address and authentication/session data needed to send a Magic Link and maintain the signed-in session. CurioBeam does not use Maker login emails to create advertising profiles or sell contact lists.

Creating or authenticating an account does not establish ownership of an app and grants no editorial or app-scoped permission. App authority is represented separately by explicit CurioBeam authorization records.

Claims and proof

Private evidence stays inside the review workflow

An authenticated Maker can request a claim against a canonical app and submit bounded, non-secret proof references for review. Current proof references are limited to normalized website/DNS/work-email domains, an official GitHub organization/repository label, or a manual-review request. CurioBeam's claim form is not intended to receive passwords, API keys, OAuth tokens, DNS challenge secrets, full email inbox contents, or other account credentials.

Claim records, proof references, reviewer decisions, authorization grants, revocations, and Maker correction proposals are private workflow data. Competing claimants are not given another claimant's private evidence. Maker assertions do not directly overwrite CurioBeam's normalized public editorial facts.

Database and authentication

Supabase is hosted in Canada Central

CurioBeam's hosted production database and authentication foundation use Supabase in the Canada Central region (ca-central-1). Public application access is mediated through bounded server-side operations and database authorization rules rather than unrestricted public table access.

Admin and Maker authorization remain separate from authentication. Private Admin/Maker data is protected by CurioBeam-owned database authorization boundaries, and browser code is not designed to receive the Supabase service-role secret.

Authentication email

Delivery infrastructure is reviewed before public Maker rollout

Magic Link delivery is initiated through Supabase Auth. CurioBeam reviews the production sender, email template, rate limits, bot-abuse controls, and email-link security behavior before public Maker authentication is enabled. If CurioBeam adds a separate custom SMTP processor for production authentication email, this notice will be updated to identify the resulting material data-processing change.

Web hosting

EdgeOne Makers is the selected Alpha web runtime

CurioBeam uses Tencent EdgeOne Makers for the Public Alpha web hosting/CDN path. The public site is live on curiobeam.com, with the restricted Admin application isolated on admin.curiobeam.com.

EdgeOne Makers provides the web runtime, edge delivery, TLS for bound domains, and platform observability. Production Log Analysis has been verified live for CurioBeam SSR requests. CurioBeam has not enabled optional additional logging products merely for Public Alpha and does not imply that optional real-time or offline log-delivery features are active.

Retention and control

Different data has different operational lifetimes

Raw search-query text follows the 30-day expiry and operational daily purge described above. Other bounded Alpha analytics fields are retained for product measurement until a broader retention or aggregation policy replaces them.

Maker account identifiers and private claim, proof, proposal, authorization, abuse, and revocation records are retained while needed to operate the account/claim workflow and to preserve security, anti-abuse, revocation, dispute, and editorial audit history. A privacy request can ask CurioBeam to review, correct, or delete personal data; some limited records may need to be retained where deletion would undermine security, fraud/abuse prevention, a live authorization record, or the integrity of a review/audit history.

Contact

Privacy questions and requests

For privacy questions, access/correction/deletion requests, or concerns, email privacy@curiobeam.com. For general CurioBeam inquiries, email hello@curiobeam.com.