Pre-launch · Building openly

Personalization without profiling.

A user-owned context wallet for the agentic web. Save preferences once. Sites and AI agents request only the fields they need. You approve, get a receipt, revoke anytime.

Free for users Revoke anytime No tracking
Thanks — you're on the list.
sole-republic.com
Sites see today
0 data points
With ContextPass
0 approved fields
Difference 0 tracked
Built for the agentic web
One wallet across every store and AI agent

Web visits may fade.
Revenue doesn't have to.

As AI agents research and evaluate products for humans, it's critical that your brand is found and recommended — without surveilling the people they're shopping for.

How it works

Five steps. Zero creepy tracking.

The user is never silently identified. Sites ask for specific fields. The user decides. Personalization runs only on what was explicitly approved.

i.

Save preferences

Set up your wallet once: size, budget, colors, styles, interests.

ii.

Visit a store

You're not auto-identified. The site is generic by default.

iii.

Approve fields

The site requests specific fields. You decide what's shared, for how long.

iv.

See better results

Products reorder with reason labels: your size, under budget.

v.

Receipt & revoke

Audit what was shared, when, and why. Revoke access anytime.

The consent prompt

You see exactly what each site asks for.

No hidden tracking. No silent profiling. The site shows the user what fields it wants, what it'll use them for, and how long it can keep them. Anything not on the list is off-limits.

ContextPass
sole-republic.com

This store wants to use:

shopping.shoe_size
shopping.budget_range
shopping.preferred_colors
shopping.preferred_styles
Purpose
Personalize product ranking
Retention
24 hours
Not requested
name
email
exact age
full browsing history
For everyone

Built for two sides of the same problem.

Shoppers want personalization without surveillance. Stores want better signal without privacy landmines. ContextPass sits in the middle as a consent layer.

Users · Free

Carry your context. Approve who gets it.

Stop re-entering your preferences everywhere. Carry them once and share only what you choose.

  • One wallet across every store and AI agent
  • Approve specific fields, not your whole identity
  • See receipts of what was shared and why
  • Revoke any site's access in one click
  • Free forever for personal use
Merchants · Paid

Personalize using customer-approved preferences.

Personalize your store using customer-approved preferences, not creepy tracking.

  • Higher product relevance and add-to-cart rate
  • Reduce returns from off-spec purchases
  • Collect user-approved preferences cleanly
  • No ad-tech, no profiling, no GDPR landmines
  • Ready for AI agents shopping on behalf of users
The flip

The web today secretly guesses. We make sites ask.

Personalization shouldn't require surveillance. ContextPass inverts the flow so the user owns the context and approves it field-by-field.

Today

The web silently profiles you.

User visits website
Website guesses who they are
Website tracks behavior
Website personalizes secretly
User has little control
ContextPass

The user owns and approves the context.

User owns context
Website asks for specific fields
User approves or denies
Website personalizes only with approved fields
User gets a receipt and can revoke
The hard rules

Privacy isn't a feature. It's the contract.

These aren't aspirational. They're built into the protocol.

Never the whole wallet

Sites only get the specific fields the user explicitly approved for that origin. Nothing else, ever.

Pairwise IDs, not global

Same user, different ID per origin. No shared identifier links your activity across sites.

No personal data on-chain

No tradable token represents a person. Wallets stay private and revocable, not auctioned.

No inference, no minors

No age, gender, race, or income inference. No price discrimination. No data on minors.

No fingerprinting

No permanent cross-site tracking ID. No silent identification. The user controls every grant.

No selling raw user data

ContextPass is paid by merchants on a SaaS subscription. We never sell what's in the wallet.

Under the hood

Every grant is a scoped token. Every share is a receipt.

Sites receive short-lived tokens with explicit fields, purpose, and expiry. Users get an audit log of every grant — append-only, revocable, theirs.

context-token.jsonScoped
{
  "aud": "sole-republic.com",
  "sub": "pairwise_user_8f3d",
  "purpose": "personalize_product_ranking",
  "fields": {
    "shopping.shoe_size": "10.5",
    "shopping.budget_max": 150,
    "shopping.preferred_colors": ["black", "gray"],
    "shopping.preferred_styles": ["minimalist", "casual"]
  },
  "expires_at": "2026-04-28T23:59:59Z",
  "grant_id": "grant_123"
}
Audit receiptActive
Store
Sole Republic
Fields shared
  • shopping.shoe_size
  • shopping.budget_max
  • shopping.preferred_colors
Purpose
Personalize ranking
Retention
24 hours
Not shared
full name · email · exact age · browsing history
Lines we won't cross

What ContextPass is not.

Saying yes to privacy means saying no to a long list of common ad-tech and crypto patterns. Here's what we deliberately won't build.

  • A hidden identity graph
  • A data broker
  • A surveillance advertising tool
  • A system that secretly follows users everywhere
  • A permanent global ID for every person
  • A tradable token that represents a human being
  • A product that puts personal data on-chain
  • A system that guesses age, gender, race, or income
  • A system that sells raw user data
  • A system that fingerprints visitors
Roadmap

Shipping in this order.

A short, opinionated build path. The demo store and wallet ship first so the consent flow is provable end-to-end.

01

Landing page

This page. Email capture for early access.

02

Demo store

Real e-commerce surface to test the consent flow.

03

Wallet

Where users save and edit context fields.

04

Consent screen

The per-site approval prompt.

05

Personalization

Product ranking with reason labels.

06

Audit receipt

What was shared, when, why.

07

Revoke flow

One-click access cancellation.

08

Browser extension

Chrome MV3 reason badges on any site.

09

Shopify app

Drop-in install for any Shopify store.

10

Cloudflare gateway

Token exchange & receipt log at the edge.

Pricing

Free for users. Paid by merchants.

Personal wallets are free, forever. Merchants choose a tier that fits their store size — pilot with us at zero risk.

Free Pilot

For early stores helping us prove the model. Limited slots.

Starter

Indie and small Shopify stores. Full consent flow + audit log.

Growth

Mid-market brands with a real catalog and personalization needs.

Enterprise

High-volume retailers, custom integrations, dedicated support.

Frequent questions

Answers to the obvious ones.

How is this different from cookies or a customer data platform?+
Cookies and CDPs work by silently identifying and profiling users. ContextPass inverts the model — the user owns the context, the site has to ask for specific fields, and the user can deny or revoke. Sites never get "the whole person."
Is my data stored on a blockchain?+
No. There is no on-chain personal data and no tradable token that represents you. Wallets stay private. We use scoped, short-lived tokens for grants and an append-only audit log for receipts.
How does ContextPass make money?+
Merchants pay a SaaS subscription based on store size and feature tier. Users use ContextPass for free. We never sell raw user data or run an ad network.
What if I want to share less than the site asks for?+
You can deny any field. The site only personalizes with what you approved — if a field is missing, that part of personalization is just generic. There is no penalty for sharing less.
What happens when I revoke access?+
The grant is invalidated immediately. The site receives a revocation signal and is required to drop the cached context. The next time you visit, the experience returns to generic.
Does ContextPass work with AI agents?+
Yes — that's part of why we're building it. Agents shopping on your behalf can request scoped context the same way sites do, and you approve or deny per agent, per task, per field.
I'm a Shopify merchant. When can I install?+
The Shopify app is on the roadmap right after the wallet, consent screen, and demo store ship. Drop your email below to be first in line for the pilot program.
Get early access

Carry your context. Own who gets it.

Free for users Revoke anytime No tracking
Thanks — you're on the list.