Marketplace votes
If you vote for the next marketplace, we store your work email, company and answers to follow up about eComm Pipes. Results only ever show totals. One vote per email. Ask us through the contact form to delete your vote.
Your data and access
What eComm Pipes receives, what it keeps, and how you can remove access.
eComm Pipes receives connector requests and returns results. It does not receive your full Claude or Codex conversation. Redacted request and result details support restricted operator inspection.
API keys stay in Google Secret Manager. Credentials, customer contact information, payment details, and signed download links are excluded from inspection records.
Google sign-in requests identity and email information only. It does not request access to Gmail or Google Drive. eComm Pipes stores your verified email and Google’s stable account identifier to match later sign-ins to your account. Account deletion removes this Google sign-in link.
Google access and refresh tokens are not retained. Signing in does not expand Walmart permissions or authorize a client to use seller data.
If you vote for the next marketplace, we store your work email, company and answers to follow up about eComm Pipes. Results only ever show totals. One vote per email. Ask us through the contact form to delete your vote.
eComm Pipes stores the notes you ask your client to save for the selected account and connection. Other authorized clients of that account and connection can read them. Notes are planning information, not verified Walmart facts or approvals.
Ask your client to clear the notes when you no longer need them. Disconnect and account deletion also erase saved context. Do not include customer personal data or secrets.
Configured pilot capture can store seller data for history and derived views. Connecting keys does not start capture or backfill earlier data. Stored results identify their freshness and coverage; missing history is not zero activity.
Captured history uses a rolling three-year retention window with scheduled cleanup. Disconnect and account deletion schedule removal of the connection’s captured data. Cleanup status can remain pending.
eComm Pipes uses PostHog (US Cloud) to understand how people find and use the product. On our pages, a first-party script sends page views, page exits, clicks and a sample of session replays (about 1 in 4 browser sessions). Replays and click records mask all text, inputs and attributes. Sign-in codes, Walmart API key forms, consent details, deletion forms and seller data are excluded from replays and click records.
Our server also sends product events: sign-in steps, connection status, client authorization, change milestones and connector tool calls. Tool call events contain the tool name, outcome, timing and error code only, never the request arguments or results. Votes send the chosen marketplace and the advertising answer, never your email or company. Contact messages send the topic only.
Events use a random identifier and, after sign-in, your internal account ID. We do not send your email address, your IP address or location to PostHog. Web addresses are sent without query strings, except campaign tags (utm) and ad click IDs.
If your browser sends Do Not Track or Global Privacy Control, eComm Pipes loads no analytics script, sets none of these cookies and sends no analytics events for your requests. To delete your analytics data, use the contact form; we delete the PostHog person and its events.
From your account, revoke a client, disconnect a Walmart Marketplace account, or review account deletion. Disconnect stops client access and schedules key deletion after active requests end.
Account deletion removes retained details and aggregates after required operation reconciliation. The deletion review identifies unresolved changes and required audit retention. The status page reports pending cleanup instead of claiming deletion is complete.