Pre-launch · Building openly

Personalization without profiling.

The identity layer for the agentic web. Save your size, taste, and boundaries once — sites and AI agents read only the fields you approve, only for as long as you allow, and you can revoke anytime.

Free for users Revoke anytime No tracking

Or see the live demo

Thanks — you're on the list.

sole-republic.com

<!DOCTYPE html>
<html lang="en">
  <head>
    <title>Sole Republic</title>
    <meta shoe.size="10.5"/>
    <meta budget.max="150"/>
    <meta styles="minimal"/>
    <meta colors="black,gray"/>
  </head>
  <body>
    <h1>Picked for you</h1>
    <div>products...

Personalization context

Sites see today

312 fields

With ContextPass

4 approved

Field difference −308

{
  "wallet": "cp_w_jeff7277",
  "fields": 12,
  "active_grants": 7,
  "size": "M",
  "shoe.size": "10.5",
  "budget.max": 150,
  "styles": ["minimal"],
  "colors": ["black", "gray"],
  "last_revoke": "2d ago"
}

Your wallet

Sites authorized

Active grants

Last revoke 2d ago

// Your AI agent acts on your behalf
const ctx = await ContextPass
  .read(['size', 'budget'], {
    purpose: 'shopping',
    retention: 'temporary'
  });

const items = await store
  .pickFor(ctx.fields);

await user.review(items);

Agent context request

Fields requested

Auto-approved

trusted

Receipt logged

By design

Six things ContextPass refuses to do.

Track you across sites

Sell your data

Use fingerprinting

Store PII server-side

Lock you to one browser

Hide grants from you

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.

For the agentic web

When AI agents act on your behalf, they need to know who you are.

A new generation of protocols defines what agents can do — call tools, talk to each other, coordinate work. None of them solve the harder question: who is the agent acting like? Your size. Your taste. Your boundaries. That data has to live somewhere the agent can read and you can control. ContextPass is that wallet — the identity layer for the agentic web, with consent built into every read.

User → Wallet → Agent → Merchant. Receipts flow back. Nothing happens without explicit consent.

MCP

Anthropic · Tool-use protocol

Lets AI agents call tools and external APIs. Solves "how does the agent do things?"

No user consent layer

A2A

Google · Agent-to-agent

Lets AI agents talk to each other and coordinate. Solves "how do agents collaborate?"

No user data layer

ContextPass
Identity + consent for users
The wallet your agent reads to act like you. Every field is user-owned, scoped, time-limited, and revocable per merchant.
User-owned identity

MCP is plumbing for tools. A2A is plumbing for agents. ContextPass is the identity layer for users — the wallet your agent reads to act like you, with consent built into every share.

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.

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.

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.

Live demo · 30 seconds

See it work in your browser.

A real storefront with the real ContextPass SDK. Click Personalize. Share your size and budget. Watch the products re-rank in front of you. No signup, no installs — just the full loop.

Try the live demo

No signup required Works in any browser Restart anytime

your size

your color

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.

Landing page

This page. Email capture for early access.

Demo store

Real e-commerce surface to test the consent flow.

Wallet

Where users save and edit context fields.

Consent screen

The per-site approval prompt.

Personalization

Product ranking with reason labels.

Audit receipt

What was shared, when, why.

Revoke flow

One-click access cancellation.

Browser extension

Chrome MV3 reason badges on any site.

Shopify app

Drop-in install for any Shopify store.

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

$0first 5 stores

90-day pilot program. We'll help you integrate.

Full consent flow + audit log
White-glove onboarding
Direct line to the founder
Email support

Apply

Starter

$79/ month

Indie and small Shopify stores.

Up to 5,000 grants / month
Field-level analytics
Webhooks for grant events
Slack support

Start pilot

Growth

$299/ month

Mid-market brands with serious catalogs.

Up to 50,000 grants / month
Pairwise ID API + SDK access
Custom retention policies
Priority support

Start pilot

Enterprise

Custom

High-volume retailers and platforms.

Unlimited grants + SLA
Forward-deployed engineering
Custom integration + dedicated CSM
Procurement-ready paperwork

Talk to sales

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."

What's the difference between "Approve for 24 hours" and "Always allow"?+

Approve for 24 hours grants the site access to your approved fields for one day, then expires automatically — you'll be re-prompted next time. Always allow creates a persistent grant for that one site, for those specific fields, until you revoke it. Both are scoped to the same fields and the same origin — "Always allow" doesn't give the site more data, just longer access. Sites you trust and use frequently are good candidates for "Always allow"; sites you're trying once should use 24 hours. You can revoke either at any time from your wallet.

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.