refund-page-generator
The refund-page-generator Claude Code skill helps create and optimize refund and return policy pages for SaaS products, digital goods, e-commerce, physical merchandise, and services. It assesses product category, jurisdiction-specific legal requirements (including EU withdrawal rights and FTC rules), refund models, and payment structures to generate compliant, clear policy content tailored to the business type and relevant regulations.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/refund-page-generator && cp -r /tmp/refund-page-generator/skills/pages/legal/refund ~/.claude/skills/refund-page-generatorSKILL.md
# Pages: Refund / Return Policy Guides refund and return policy page content for SaaS, digital products, e-commerce, and services. Covers jurisdiction-specific requirements including EU withdrawal rights. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment Identify: 1. **Product category**: See §Product Categories — refund logic is fundamentally different for SaaS vs digital downloads vs physical goods vs services 2. **Jurisdiction**: EU (14-day withdrawal right + mandatory withdrawal button), UK (DMCCA subscription rules), US (FTC clear-and-conspicuous), Australia (consumer guarantees), China (2026 platform rules) 3. **Refund model**: Full refund, partial/pro-rata, store credit only, no refund, or conditional 4. **Payment flow**: One-time, subscription/recurring, or tiered pricing --- ## Product Categories Refund policies differ radically by product type. Identify the category first: | Category | Default Refund Stance | Key Considerations | |---|---|---| | **SaaS / Subscription** | Pro-rata or conditional | EU withdrawal button required by Jun 2026; trial periods; auto-renewal cancellation; Sky Austria case may reclassify subscriptions as "digital services" with full-period withdrawal rights | | **Digital Downloads** | Typically non-refundable | "Once downloaded, all sales final"; exceptions for technical failure or duplicate purchase; must obtain explicit consent to waive EU withdrawal right before download | | **Physical Goods** | 30-day return window (standard) | Return shipping costs; restocking fees; original packaging; final-sale categories | | **Courses / Coaching** | Conditional | Pre-recorded: non-refundable once accessed; Live: partial refund before start, none after; rescheduling preferred over refunds | | **API / Usage-Based** | Prorated or non-refundable | Pay-as-you-go typically non-refundable; subscription components may be prorated | | **Marketplace** | Per-vendor or uniform | Who processes refunds; vendor return rates (>8% review, >15% suspend); uniform policy builds trust | | **Free Tools** | N/A | No payment = no refund policy needed; state "free, no purchase required" if asked | --- ## Jurisdiction Requirements ### EU — Consumer Rights Directive + 2026 Withdrawal Button **14-Day Cooling-Off Period**: - EU consumers have an unconditional 14-day right to withdraw from any distance contract (online purchase) - Applies to goods, services, AND digital products/SaaS - You must inform consumers of this right BEFORE purchase — failure extends the period by up to 12 months - For goods: withdrawal period starts on delivery - For services/digital: starts on contract conclusion **Mandatory Withdrawal Button — Deadline June 19, 2026** (Directive EU 2023/2673): This is the most urgent 2026 compliance item. Requirements: - A clearly labeled digital withdrawal function (e.g., "Withdraw from contract" button) on your website/app - **Two-step process**: (1) Withdrawal button → confirmation page → (2) "Confirm withdrawal" button - Automated confirmation sent to consumer on a **durable medium** (email) with timestamp - Button must be **permanently available** during the withdrawal period, prominently placed, not hidden behind logins or menus - Applies to **any business targeting EU consumers**, regardless of where the business is registered - Penalties: fines up to 4% of annual turnover in some member states; extended withdrawal periods until compliant **Digital Content vs Digital Services — Sky Austria Case (CJEU, pending 2026)**: This pending case may significantly change how SaaS refunds work: - Advocate General opined that streaming subscriptions (and by extension, SaaS) are **"digital services"** — not "digital content" - **Why it matters**: Digital content can waive withdrawal rights immediately upon access. Digital services only lose withdrawal rights once the service is **fully performed** — not when access begins - **Practical impact**: If the CJEU follows this opinion, SaaS providers may not be able to extinguish withdrawal rights at first login; the right would persist for the full subscription term - **Monitor this case** and be prepared to update refund terms **Exceptions** (Article 16 CRD — withdrawal right does NOT apply to): - Digital content where performance has begun AND consumer gave prior express consent AND acknowledged loss of withdrawal right (but note Sky Austria risk) - Fully performed services with consent and acknowledgment - Customized/personalized products - Services for specific dates (events, hotel bookings) **2-Year Conformity Guarantee**: Under Digital Content Directive (2019/770), consumers have a minimum 2-year guarantee for defective digital products and services. ### UK — DMCCA Subscription Rules (Spring 2027) - Pre-contract disclosure of key subscription terms (trial price, renewal date, cancellation method) - Two 14-day cooling-off periods (one at sign-up, one after auto-renewal of long-term contracts) - Mandatory renewal reminders with prescribed information - Cancellation must be "straightforward" — no unnecessary steps ### US — FTC Requirements - No federal right of withdrawal for online purchases - FTC requires refund policies to be "clear and conspicuous" - Some states have specific rules: California requires posting the refund policy if not offering full refund within 7 days - State AGs increasingly enforce against "dark patterns" that make cancellation difficult ### Australia — Consumer Guarantees (ACL) - Consumer guarantees **cannot be excluded** by store policy - Defective items entitled to refund, repair, or replacement regardless of what the policy says - No fixed return window — "reasonable time" applies ### China — 2026 Platform Rules (Effective February 1, 2026) - Platforms **cannot force merchants** to ac
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.