PRIVACY
Privacy Policy
EFFECTIVE SEPTEMBER 8, 2026 · UPDATED SEPTEMBER 30, 2026
NamedFirst works on what the public can already see about your business: what AI assistants say, what your website says, what reviews say. That keeps the personal data we hold small. This page says exactly what it is.
THE SHORT VERSION
- We collect what it takes to bill you and to do the work: your name, your email, your business name, and your website. Your payment details go to Stripe, and Stripe keeps them.
- We never ask for a password, whether for your website, your Google profile or your social accounts. The off-site work is drafted by us and posted by you.
- The audit data we gather about your business is public information, and we keep it so we can show you what changed.
- Our site uses no advertising trackers. The only cookie it ever sets is the one that keeps you signed in to your account, and only after you sign in. Page counts are measured without identifying you.
- We do not sell data. We do not add you to a mailing list.
- 01 · WHO WE ARE
- 02 · WHAT WE COLLECT, AND WHY
- 03 · WHAT WE NEVER COLLECT
- 04 · THE AUDIT DATA
- 05 · THE COMPANIES WE RELY ON
- 06 · COOKIES AND BROWSER STORAGE
- 07 · HOW LONG WE KEEP THINGS
- 08 · YOUR CHOICES
- 09 · HOW WE PROTECT IT
- 10 · CHILDREN
- 11 · CHANGES TO THIS POLICY
- 12 · CONTACT
Who we are
NamedFirst is made and run by Command Module, a product line of AIgent, LLC, in Texas. We are the controller of the personal data described here. Reach us at hello@commandmodule.com or (817) 409-6700.
What we collect, and why
When you subscribe
Checkout runs on Stripe’s own pages. Stripe collects your name, your email address, and your payment details. Stripe keeps them. We receive your name, your email, and a customer record so we can bill you and reach you. Stripe’s checkout page also asks two questions of ours: your business name as customers know it and your website. Those are the two facts the baseline starts from, and we store them on your customer record.
When you finish checkout
The page that confirms your payment asks our server whether Stripe recorded it. That request carries the checkout session id Stripe issued to your browser and nothing else. The answer carries your own name, email, and business name, so the page can say them back to you.
When we email you
When you subscribe we send a welcome email and an onboarding note. After that we send the emails the work needs: your question list to review before we measure, your baseline report, a short note every morning, with one task on Monday, Wednesday and Friday and where you stand on the other days (one click pauses it), and billing notices. We keep copies of what we sent and what you replied so we can remember what we said.
When you write to us
That is an email from you to us. We keep it in our mailbox so we can answer it and remember what we said. Writing to us does not put you on a list.
When you run the free machine sample
The Baseline Kit can put one of its generated questions to seven AI engines for you, once a day. That run costs us seven API calls, so it asks for your website and an email address. The website tells a link to you from a link to anyone else and limits runs per site; the email is where the result goes and limits runs per person. The run also carries your business name and the competitors you typed into the Kit, because each answer is scored for those names. We keep the website, the email and the business name, with the question you chose and what each engine said, as a record that you asked. The question — and nothing that identifies you — goes to the engines named on the page under their own terms: OpenAI, Anthropic, Perplexity, Google, xAI, and a search-results provider for the two Google surfaces. Over the two weeks after the run we send four short emails to that address about what the result means and about the paid baseline — on days one, three, seven and fourteen — then we stop. Every one carries a link that stops the rest at once, and buying the baseline stops them too. We keep the address, the site, and the note that you asked us to stop, so a later run never starts them again.
When you run the Readability Check
The Readability Check sends one thing to our server: the web address you type. The server reads that page twice as a browser and once under each of six crawlers’ published user agents (OpenAI’s, Anthropic’s, Perplexity’s and Google’s), fetches the site’s robots.txt and llms.txt, and sends what it found straight back to your browser. It keeps neither the address nor the page. To stop one source hammering it, the server counts checks per IP address in its own memory, ten a minute; the count lapses when the minute is up and is never written to disk or a database. The site you check sees those requests arrive from our server.
In the normal course of serving pages
Our hosting provider sees your IP address and browser type when it serves a page or an API request, the way every website’s host does. We use the IP address only to stop abuse, such as one address hammering the checkout button. We do not build profiles from it.
What we never collect
- Your passwords. We never ask for the login to your website, your Google Business Profile, your review platforms, or your social accounts. If a fix needs a change only you can make, we send you the change and you make it.
- Your payment details. They live with Stripe. For a card we see the last four digits on our Stripe dashboard, the same as any merchant, and nothing more.
- Your customers. The review requests we draft are for you to send. We never receive your customer list.
- Anything from your visitors. We do not put scripts on your website. Nothing about the people who visit your site comes to us.
The audit data
To do the work, we gather public information about your business and your market: what AI assistants answer when asked the questions your buyers ask, the public pages of your website, public reviews and mentions, and the public presence of competitors named in those answers. All of it is information about businesses, and it is already public. We keep it dated and locked, because the whole product is showing you the before and after honestly. It may include names of people that appear in public reviews or on public pages. We use those only as they appear and never build anything about those individuals.
The companies we rely on
| Company | What they do for us | What they see |
|---|---|---|
| Stripe | Checkout, billing, invoices, your billing page | Your name, email, card, business name, website |
| Vercel | Hosts this site and its small API; counts page views without cookies | Your IP address and browser type while serving a page |
| Resend | Delivers our email to you | Your email address and the messages we send |
| OpenAI, Anthropic, Perplexity, Google, xAI, and a search-results provider | Answer the free machine sample and the paid baseline | The question text only. Some questions name your business, the way a buyer would; none carries your own name, your email, or your web address |
| Google Fonts | Serves the typefaces on this site | Your IP address when your browser fetches a font file |
| AI platforms | ChatGPT, Claude, Gemini, Perplexity, and Google’s AI Overviews answer the questions we test | The questions we ask. They name your business and your market; none names you personally |
Each of these companies has its own privacy policy. We chose them because they hold the least they can and say what they hold.
Cookies and browser storage
This site sets one cookie, and only if you sign in: a session cookie that keeps you signed in to your account page for up to 30 days. It identifies your subscription to us and nothing to anyone else — it is not readable by scripts, is never used for advertising or analytics, and disappears when you sign out. Browsing the site, the free tools, and everything else here sets no cookies at all. The free tools keep what you type and score in your browser’s local storage, on your device; none of it reaches us unless you run the machine sample, which sends the one question you chose. Page views are counted by Vercel Web Analytics, which works without cookies and without identifying you. Stripe’s checkout and billing pages set the cookies Stripe needs to run them; those pages are Stripe’s. There is no consent banner because strictly functional cookies need no consent and we use nothing else.
How long we keep things
- Your customer record stays for as long as you subscribe, and then for as long as tax and accounting rules require us to keep billing records.
- The audit data stays for as long as you subscribe, so every delta report can point at the baseline. Ask, and we delete it when you leave.
- Email stays in our mailbox so we can remember what we told you.
- Hosting logs are kept by our hosting provider for a short period and then discarded.
Your choices
- See or correct your data. Email us. Your name, email, and card are also editable on your billing page.
- Cancel. From the billing page, any time. Your access runs to the end of the period you paid for.
- Delete. Email us and we delete your customer record and audit data, apart from the billing records the law makes us keep.
- Stop the emails. Every email we send about your account is part of the service, so the way to stop them is to cancel. We never send marketing email.
How we protect it
Everything travels over HTTPS. Our server talks to Stripe with a secret key that lives in our hosting provider’s protected settings, never in code. Stripe signs every message it sends us and we check the signature before acting on it. Only the people who run NamedFirst can reach the customer records, and there are very few of us.
Children
NamedFirst is a service for businesses and is not directed at anyone under 18. We do not knowingly collect data from children.
Changes to this policy
When this page changes in a way that matters, we email subscribers before it takes effect and update the date at the top. Small wording fixes just get the new date.
Contact
Command Module · AIgent, LLC
1107 South Airport Circle, Bldg C, Euless, TX 76040
hello@commandmodule.com · (817) 409-6700