# AI Coding Pricing final compliance recheck

> Date: 2026-05-21
> Reviewer: 墨盾 ⚖️
> Scope: production policy / trademark / privacy / deployment verification for https://aicodingpricing.com after policy remediation commit `2735ea6d40888977aeeb8407206dfb3e5d727232` and later SEO/content deployment commit `5d141b41e61f70d1f773de8b421b90b12592edfe`.
> Note: This is a business compliance and risk-control review, not formal legal advice. Consult a licensed attorney for material legal decisions, trademark disputes, paid partnerships, or regulated data processing.

## 1. Verdict

GO for public compliance gate, with one P1 operational caveat.

- Compliance verdict: GO_WITH_P1_CAVEAT
- P0 blockers: 0
- P1 issues: 1 — `support@aicodingpricing.com` is published, but no MX record was observed for `aicodingpricing.com` during this recheck.
- Trademark / no-affiliation gate: GO.
- Logo / third-party asset gate: GO.
- Pricing source freshness gate: GO for the current production snapshot.
- Cookie / analytics runtime gate: GO for the current implementation because no non-essential tracker script or `Set-Cookie` header was observed.
- Policy completeness gate: GO after `/privacy` and `/terms` remediation.
- Deployment source gate: GO. Cloudflare Pages Production shows latest Source `5d141b4`, matching the later SEO/content deployment commit `5d141b41e61f70d1f773de8b421b90b12592edfe`.

## 2. P0 blockers

None found in this recheck.

The stale prior NO_GO was tied to thin `/privacy` and `/terms` content. Production now includes the required operator, processor, retention, rights, cookies, data category, IP/trademark, affiliate/sponsorship, no-warranty/liability, no-private-account-data, and complaint/correction-route language.

## 3. P1 issues

### P1-1 Domain email deliverability is not proven

Observed public contact route:

- `/privacy` publishes `support@aicodingpricing.com` for privacy rights requests.
- `/terms` publishes `support@aicodingpricing.com` for correction, copyright, trademark, affiliation, and provider-reference requests.
- `/contact` publishes the same support route for source corrections, pricing updates, privacy requests, and newsletter issues.

DNS check:

```text
MX:
(no MX record returned)
A:
188.114.97.1
188.114.96.1
TXT:
(no TXT record returned)
```

Risk: users may not be able to reach the published route unless email receiving is configured elsewhere and verified. This is not a launch-blocking legal content defect, but it is an operational compliance weakness because the rights/complaint route must work.

Required follow-up:

- Configure and verify inbox delivery for `support@aicodingpricing.com`, or replace it with a verified working mailbox before broad launch / GSC / directory submissions.
- If using a domain mailbox, add MX/SPF/DKIM/DMARC records and send a test email.

## 4. Production availability

Checked with live HTTPS fetch on 2026-05-21 using a browser-like user agent.

- `/` 200
- `/privacy` 200
- `/terms` 200
- `/contact` 200
- `/about` 200
- `/claude-code-pricing` 200
- `/codex-pricing` 200
- `/cursor-pricing` 200
- `/github-copilot-pricing` 200
- `/pricing-changelog` 200
- `/claude-code-vs-codex` 200
- `/claude-code-vs-cursor` 200
- `/codex-vs-cursor` 200
- `/sitemap.xml` 200
- `/robots.txt` 200

Footer/legal navigation check:

- `/` links to `/privacy`, `/terms`, and `/contact`.
- `/privacy` links to `/privacy`, `/terms`, and `/contact`.
- `/terms` links to `/privacy`, `/terms`, and `/contact`.
- `/contact` links to `/privacy`, `/terms`, and `/contact`.
- `/about` links to `/privacy`, `/terms`, and `/contact`.
- `/claude-code-pricing` links to `/privacy`, `/terms`, and `/contact`.

## 5. Privacy Policy recheck

Observed page: https://aicodingpricing.com/privacy returned 200.

Now passed:

- Operator: names Nextfield Labs LLC, Wyoming, USA.
- Data categories: calculator scenario inputs, token estimates, model selections, result values, newsletter/pricing-alert data, contact/correction/support requests, technical logs, IP address, user agent, request path, timestamps, error logs, abuse-prevention signals, security events, aggregate analytics.
- No private account data: explicitly says the site does not ask for, collect, or store provider account credentials, API keys, billing exports, private usage dashboards, source-code access, or private account data.
- Processors: names Cloudflare as hosting/security processor; states Plausible is not installed and must be named before enablement; states newsletter/email provider must be named before storage or email delivery is enabled.
- Retention: newsletter/pricing-alert records until unsubscribe/deletion/list retirement; contact/correction/copyright/trademark/privacy-request emails normally 24 months; server/security/anti-abuse logs normally 30–90 days.
- Rights: access, correction, deletion, copy of personal data, unsubscribe, opt-out of future non-essential marketing/analytics tracking, no sale/share for cross-context behavioral advertising.
- Cookies: states no non-essential cookies are currently observed; Cloudflare may use strictly necessary mechanisms; no banner required for current implementation; GA/Clarity/ad pixels/affiliate trackers require consent gate and policy update before use.
- Contact route: `support@aicodingpricing.com`, with a caveat that `privacy@aicodingpricing.com` should only be used after MX/inbox delivery is verified.

Residual note: policy text is adequate for current low-risk static/comparison/calculator implementation. If newsletter storage, email delivery, analytics, affiliate tracking, payments, accounts, or user-uploaded content are enabled later, the policy must be updated before collection starts.

## 6. Terms of Use recheck

Observed page: https://aicodingpricing.com/terms returned 200.

Now passed:

- Operator/governing law: names Nextfield Labs LLC, Wyoming, USA; governing law is Wyoming, USA, subject to mandatory consumer/data-protection law.
- Independent status: states AI Coding Pricing is not affiliated with, sponsored by, endorsed by, or officially connected to Anthropic, OpenAI, Anysphere, GitHub, Microsoft, or other mentioned providers.
- Informational-only scope: not official billing guidance, procurement advice, legal advice, tax advice, financial advice, accounting advice, or a substitute for provider contracts/invoices/pricing pages/account dashboards.
- Pricing caveat: calculator outputs are estimates, not billing quotes; pricing, usage limits, promotions, availability, taxes, FX, overage rules, seat policies, and account-specific terms can change.
- Trademark/fair use: lists Claude/Anthropic, OpenAI/ChatGPT/Codex, Cursor/Anysphere, GitHub/GitHub Copilot/Microsoft; frames use as nominative identification, comparison, source citation, and factual commentary.
- Affiliate/sponsorship placeholder: states no current affiliate links or sponsored placements; future affiliate/sponsored/referral relationships must be disclosed near relevant links/placements and must not change factual tables, source links, methodology, caveats, or correction handling.
- No private account data/scraping: prohibits provider credentials, API keys, private billing exports, private account screenshots, personal account data, confidential company data, source-code repositories, private account scraping, bypassing access controls, unauthorized procurement automation, and representing estimates as official provider quotes.
- No warranty / liability: includes as-is/as-available disclaimer and limitation of liability for indirect, incidental, special, consequential, exemplary, punitive damages, lost profits/revenue/savings/goodwill/data/procurement outcomes/business decisions.
- Complaint/correction route: `support@aicodingpricing.com` for source corrections, copyright complaints, trademark complaints, affiliation concerns, or provider-reference updates.

## 7. Trademark / no-affiliation / assets

Passed.

Evidence:

- Production text uses negative no-affiliation language: not affiliated with, sponsored by, endorsed by, or officially connected to the named providers.
- Search terms such as `endorsed by` and `sponsored by` appear in negative no-affiliation disclaimers, not as positive claims.
- No positive `official pricing calculator`, `certified`, `approved`, `partner`, `powered by official data`, `100% accurate`, `guaranteed latest`, `unlimited usage`, or `official source of truth` claim was found in the scanned production pages.
- Production HTML scan found no provider `<img>` logo assets on the checked pages.
- Provider pages are source-linked and comparison-oriented, not official-looking brand landing pages.

Residual guardrail:

- Do not add third-party logos, screenshots, provider UI captures, official badges, or “partner / certified / approved / official” copy without separate IP/TOS review.

## 8. Runtime cookies / analytics / trackers

Passed for current runtime.

Evidence from live production pages:

- `Set-Cookie`: none observed on checked responses.
- Tracker script scan: no Plausible, Google Analytics, Google Tag Manager, Microsoft Clarity, Hotjar, Facebook Pixel, or ad-pixel scripts observed.
- Scripts observed: Next.js static chunks and Cloudflare email-decode script on pages with encoded email addresses.
- Policy match: `/privacy` says no non-essential cookies are currently observed and no banner is required for the current implementation.

Interpretation:

- Current implementation does not require a cookie banner.
- If Plausible is later added without cookies, Privacy must name Plausible and describe the data before/when enabled.
- If GA/Clarity/ad pixels/affiliate trackers are added, cookie banner + consent gating + Cookie Policy become P0 before use in EU/UK-facing traffic.

## 9. Pricing data / source freshness

Passed for current production snapshot.

Evidence:

- Pricing pages render source links and freshness/caveat language.
- Live text check confirms current pricing pages include `checked 2026-05-21` where applicable.
- Provider pages and changelog pages expose source-linked pricing/freshness context.
- Calculator and Terms both state outputs are estimates, not billing quotes.

Residual risk:

- AI coding tool pricing and limits are volatile. Weekly source review/changelog maintenance remains required after launch.
- Do not market the site as complete, official, guaranteed current, or account-specific.

## 10. Deployment evidence

Cloudflare Pages deployment list:

```text
Environment  Branch  Source   Deployment
Production   main    5d141b4  https://1bd9892c.aicodingpricing.pages.dev
Production   main    2735ea6  https://18e7f67f.aicodingpricing.pages.dev
Production   main    2d87d35  https://378de47d.aicodingpricing.pages.dev
```

Expected final source after later SEO/content deployment:

- Full commit: `5d141b41e61f70d1f773de8b421b90b12592edfe`
- Cloudflare Pages Production Source: `5d141b4`
- Result: matched.

Local source state during recheck:

```text
branch: main
HEAD: 5d141b41e61f70d1f773de8b421b90b12592edfe
git status: clean before report rewrite
```

Validation commands run from `/root/projects/aicodingpricing`:

```text
npm run lint        PASS
npm run verify      PASS { ok: true, routes_checked: 23, redirects_checked: 4, contract_routes: 21 }
npm run build       PASS
```

## 11. Final gate

compliance_verdict: GO_WITH_P1_CAVEAT

p0_issues: 0

p1_issues:

1. Published domain email route needs deliverability verification because no MX record was observed for `aicodingpricing.com`.

Launch interpretation:

- PM/QA can replace the stale policy-related NO_GO with GO_WITH_P1_CAVEAT.
- The site is acceptable for public compliance gate on policy completeness, trademark/no-logo/no-affiliation, pricing caveats, cookie/runtime tracker match, and production deployment source.
- Before broad distribution, verify `support@aicodingpricing.com` receives mail or replace it with a verified working mailbox.
