Namebeam, a Carter Enterprise property. Plain words on what we collect, who handles it, and the choices you have. Effective 2026-10-28.
This page covers namebeam.ai and markets.namebeam.ai, and, in the Receipts Index sections below, the Receipts Index API at api.receiptsindex.com and the receipts-index MCP server. All are run by Carter Enterprise LLC, a Wyoming limited liability company at 30 N Gould St, Ste 65270, Sheridan, WY 82801. You can reach us at terry@namebeam.ai.
Other sites in the Carter Enterprise network, apart from the Receipts Index API and MCP server named above, have their own practices and are not covered here.
We use PostHog, hosted in the United States, to see how these sites are used. The PostHog script is on many pages of both sites, not on every page. It collects:
Automatic capture of every click and form entry is off. Apart from the items above, we do not log individual clicks.
PostHog keeps an identifier in your browser so it can tell a repeat visit from a new one. It is stored in both localStorage and a cookie. We do not send your name or email address to PostHog.
We use PostHog session replay. A recording shows how a page was used: what was on the screen, clicks, mouse movement and scrolling. It also includes browser console messages and the timing of page requests. Text shown on a page appears in a recording as it appears on screen. Everything typed into a form field is masked, so we do not see it. Recordings are not made on order confirmation (thanks) pages. Recordings are kept for up to 30 days.
Cloudflare hosts both sites. To deliver a page, Cloudflare handles your IP address and the request you make. On namebeam.ai, most pages also load Cloudflare Web Analytics, a basic Cloudflare traffic and page performance counter.
Buy buttons take you to a checkout page hosted by Stripe (buy.stripe.com). You enter your card details on Stripe, not on our sites, and Stripe handles the card data. We receive your name, your email address, the payment status and the order details you enter. Stripe's own privacy policy applies to what it collects.
If you reach a Namebeam page through an affiliate's link, a script from Endorsely (assets.endorsely.com) keeps a referral identifier in your browser for up to 90 days. Our Stripe checkout links carry that identifier so the affiliate can be credited for a purchase. Endorsely reads the payment record from our Stripe account.
Some namebeam.ai pages have forms that ask for details such as your email address, a market and a business name. A form sends what you type to Web3Forms (api.web3forms.com), which passes it to our inbox. markets.namebeam.ai has no forms. If you email terry@namebeam.ai, we read your message and reply by email.
The Receipts Index API at api.receiptsindex.com and the receipts-index MCP server are run by Carter Enterprise LLC. They need no account, no sign-in and no API key. We do not ask for your name or email address to use them. We do not sell personal data from the API, the MCP server or payments. The sections below say what each part collects. Documentation is at namebeam.ai/developers/receipts-index/.
The API runs as a Cloudflare Worker. Cloudflare handles your IP address and the request you make, and Cloudflare Workers Logs is turned on for the Worker, so Cloudflare keeps request logs for it. The API sets no cookies and loads no analytics script.
The Worker's own code writes two log lines for a paid request, one after the payment is checked and one after it is settled. Each line holds the route name and the status the payment facilitator reports for the listing check. The lines do not hold the payment signature, a wallet address or an IP address.
The buy page at api.receiptsindex.com/buy runs in your browser. It reads your account address and the network from your wallet so it can build the payment. It has no analytics script, and your private key stays in your wallet.
Paid routes use the x402 protocol. You pay in USDC on Base, from your own wallet. We do not take card details on the API. Your client signs a USDC transfer authorization and sends it in a PAYMENT-SIGNATURE request header. The Worker passes it to the payment facilitator, PayAI (facilitator.payai.network), which checks it and settles it on Base. PayAI receives the payment details, including your wallet address, and its own policies apply to what it keeps. The Worker does not store the signature.
Payments go to a wallet of Carter Enterprise LLC. Transactions on Base are public: your wallet address, the amount and the transaction appear on the blockchain, and we cannot remove them.
The npm package receipts-index-mcp runs on your own computer and reads the free routes of the API above. From version 0.1.1, including 0.1.4, it sends anonymous usage events to PostHog, hosted in the United States, in the PostHog project of Carter Enterprise LLC. The events hold:
The events carry no name or email address, and no person profile is created from them. As with any request to a web service, PostHog receives the network address the request comes from.
Turn it off. Set RECEIPTS_INDEX_TELEMETRY=0 or DO_NOT_TRACK=1 in the environment of the server. With either set, no PostHog client is created and nothing is sent to PostHog.
The remote endpoint at https://api.receiptsindex.com/mcp is part of the API Worker. It needs no sign-in or key and sends no events to PostHog or to any other analytics service. Its three tools read the Worker's own free routes. Cloudflare request logs, described above, apply to it. The endpoint never pays and never signs anything.
Our pages link to other services, such as the booking page on Calendly, X and YouTube. Those services receive your data only if you click through, and their own policies apply once you do.
Turn analytics off. If your browser sends a Do Not Track or Global Privacy Control signal, our script does not load PostHog at all. Nothing is sent to PostHog: no page views, no heatmap data, no replay. You can switch these signals on in your browser settings. You can also block posthog.com in a content blocker; the sites work the same without it. The Do Not Track and Global Privacy Control signals apply to PostHog. The Cloudflare Web Analytics counter is a separate script that a content blocker stops.
Turn off MCP package telemetry. Set RECEIPTS_INDEX_TELEMETRY=0 or DO_NOT_TRACK=1 in the environment of the receipts-index-mcp server. The Do Not Track and Global Privacy Control browser signals above apply to the websites only.
Clear what is stored. Delete the site data and cookies for namebeam.ai or markets.namebeam.ai in your browser to remove the PostHog identifier.
Ask to see or delete your data. Email terry@namebeam.ai and say what you want. To find analytics data we may ask for details such as the date and the page you visited.
If this page changes, we update the effective date below.
Carter Enterprise LLC
30 N Gould St, Ste 65270, Sheridan, WY 82801
terry@namebeam.ai
Effective date: 2026-11-03.