CartRelay — Privacy for agent shopping

Humans brief. Agents discover.

The consumer website builds local shopping briefs, helps you connect a trusted agent and provides human review of that agent's signed intent. Four fixed homepage examples are a limited live discovery preview, not a direct browser catalog or manual shopping service. Copying a brief shares it only when you choose to paste it into your assistant; building it does not connect an agent or query a source.

For an explicit shopper need, an authenticated agent sends the product query and context (Canada, currency preference and optional postal code) to CartRelay's commerce service through hosted MCP or REST. CartRelay sends permitted queries to its outbound provider, Shopify Global Catalog, and resolves exact references for intent and handoff. Avoid sensitive personal information in briefs and queries. Your agent client may retain prompts, keys or responses under its own policy; choose a trusted client and follow source no-cache rules.

CartRelay runs on Manus-hosted infrastructure. The hero is original concept imagery. The four homepage product examples use fresh source listings and merchant-hosted photos, not generated branded lookalikes. Loading that section performs one fixed-reference source lookup without sending your brief, cookie or postal code. Your browser loads merchant images directly; their hosts can receive your IP address and browser information. Image requests suppress the referrer. The review page displays source facts as text. Agent clients may also display external source images. CartRelay does not copy or mirror merchant images.

Transient facts and signed-intent review

Source-result bodies, descriptions, image URLs, prices and offers are processed request-locally, not stored as a permanent catalog, database price snapshots or image copies. Catalog and credential responses use no-store. Only four fixed reference IDs and CartRelay-owned category labels are stored as showcase configuration, never returned titles, prices or images. This frontend does not put provider payloads, raw keys, CSRF or intent tokens in localStorage or sessionStorage.

Agents return an expiring review URL with the token in its fragment, not a query parameter. The review page reads it into memory and immediately removes the fragment from the address bar. It opens only for the originating shopper browser cookie, re-resolves current offers and uses the newly returned token for consent. Tokens are independently signed with a server-held secret; a guest cookie is not the signing key. A signed intent is not an inventory reservation.

Leaving the review page clears token/response memory and rendered source details and invalidates late requests. Reloading or restoring a cleared page needs a fresh agent-issued review link. Do not share review links or tokens with support. Explicit approval records only an opaque approval hash, owner session and expiry, not catalog payloads. The server rechecks current source fingerprints before releasing retailer links; changed or unresolved offers need renewed agent-originated review.

Sessions, keys and expiry

A guest session uses an opaque cookie with a 24-hour lifetime; the database stores its hash and expiry metadata, not the raw credential. Browser mutations use memory-held CSRF. These sessions support onboarding, key management, support and narrow owned-intent consent; cookies do not authorize commerce search, detail, offer, cart or handoff routes. Both MCP and REST commerce require delegated Bearer keys.

Delegated keys last two hours, can be revoked earlier and are revealed once. CartRelay stores hashes and metadata such as label, prefix, expiry, revocation, last use and calls. A key holder can act within its permitted scope until expiry or revocation. Losing the originating guest cookie can prevent key management and intent review; expiry still ends access.

Intent tokens last ten minutes. Expiry ends validity; expired credential and approval database state is removed by the next daily cleanup, not necessarily at the instant of expiry. Functional security/rate metadata and minimal operational outcomes are not provider-result payloads. Consult returned expiry timestamps.

Support records and notification copies

Submitting support sends your email, message, request type and reference to CartRelay for operator handling and attempts an owner notification. A stored request can remain if notification fails. Notification acceptance is not proof that a person read it or replied.

Application-database support requests and operational events are deleted after 30 days at the next daily cleanup, so retention can be up to 31 days. Native daily registration follows deployment. This cleanup applies only to the app database: email/message copies sent in owner notifications are not deleted by app cleanup. Copies in owner inboxes or Manus notification systems follow separate owner/Manus retention policies; no 30/31-day deletion promise applies to them. Ask the operator through a privacy request for help with those copies, subject to the relevant service and applicable obligations.

Raw catalog bodies, shopper-query payloads and briefs are not stored as operational logs. Support text is information you expressly submit, distinct from minimal operational metadata.

Retailers and operator access

CartRelay collects no retailer payment-card details and completes no purchase. After consent and recheck, following a source-returned retailer link takes you to the retailer, which handles final prices, payment, shipping, fulfillment and returns under its policies. A link may not set your quantity.

The private operator area uses real Manus identity and separate exact owner authorization. Being signed in is not operator access; guests are not automatically administrators.

Your questions and requests