Align current public copy with submitted Etsy appeal - #64
Merged
Conversation
Removes "AI optimization"/"AI credits"/"AI Listing Optimization" and
similar phrasing from the homepage hero, pricing preview, pricing page,
/features metadata and safety list, FAQ, and feature-registry public
copy, replacing it with neutral wording ("advanced workflows",
"suggestion credits", "saved workflows") so public marketing no longer
implies broader external AI processing than production currently
performs. No authenticated in-app AI functionality is removed or
renamed; backend fields (e.g. ai_credits_per_month) are unchanged —
only public-facing display strings.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RzUkp3csH7vBCA286nfaxL
…eguards Privacy §6 (AI features) now states that sending Etsy-derived listing data to an external AI provider is disabled by default in production pending Etsy's written confirmation, without claiming Etsy prohibited or approved AI use. Privacy §10 (retention) documents that backup snapshots and CSV job records are retained for a 30-day conservative default (not Etsy-mandated), the automated daily cleanup that enforces it, the first successful run on 2026-07-15, and corrects stale copy that claimed self-service account deletion doesn't exist — it does, gated behind password re-confirmation and an active-subscription check (see app/services/auth.py delete_account). Terms §6 adds the same external-AI-disabled safeguard and softens "AI-generated" to "AI-assisted" to match the review-required framing used elsewhere. Terms §8 documents that account deletion does not auto-cancel Stripe subscriptions, matching the billing gate already enforced server-side. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RzUkp3csH7vBCA286nfaxL
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The already-submitted Etsy appeal describes conservative AI handling and updated retention/account controls. Current source no longer exposes old founding-access or public AI Listing Optimizer / Listing Health Score cards, but a few public pages and metadata still contained overly broad AI wording or incomplete legal copy.
Changes
/pricingmetadata, the plan comparison table label, and the homepage plan-summary highlight/featuresmetadata description (dropped "AI optimization"/"listing health scoring") and the safety-list line ("AI suggestions are reviewed before acceptance" → "Suggestions are reviewed before acceptance")featurePages.tspublic copy: Safe Preview EnginehowItWorks, Scheduled Jobs ("AI sessions" → "saved workflows"), Social Promote ("AI-prepared captions" → "Prepared captions")/private-betametadata description ("or early access" removed — page body already only talks about a status update, not access tiers)app/services/auth.py::delete_account)Already clean (verified, not modified)
pre-launchword appears in an internal code comment on an admin-only/owner/userspage — not public copy)/features/features/ai-listing-optimizationand/features/listing-health-scoreare not inFEATURE_PAGESand hitnotFound()(404) via the dynamic[slug]routesitemap.tsis generated fromFEATURE_PAGES/BLOG_POSTS/COMPARISON_PAGES/FREE_TOOLS/a static public-route list, so the removed AI/health slugs were never includedNEXT_PUBLIC_LEGAL_ENTITY_NAMEwith a "Bulk Edit App" fallback (seeDECISIONS.md); production env value was not checked here (no DO secret access) — if it is set to "Bulk Edit App LLC" without confirmed registration, that's a pre-existing environment question for the owner, not a source issueValidation
npm run type-check— passednpm run lint— passed (only pre-existing warnings in unrelated authenticated-app files)npm run build— passed, all 82 routes generatedapp/,components/,lib/— clean (remaining hits are an explanatory source comment and one authenticated in-app AI label, both allowed categories)git diff --check— cleanSafety
Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01RzUkp3csH7vBCA286nfaxL