Example output #3 (Gumroad • generous • LUTs/presets ZIP) Policy Summary This product is delivered as a ZIP download. If you can’t access the files or they’re corrupted/incompatible with the listed requirements, we’ll troubleshoot and refund if needed within the refund window. Refund Policy (ready to paste) Eligibility Refund requests accepted within 7 days if: the ZIP is corrupted and a replacement doesn’t fix it, the files are incompatible with the stated software/version requirements, or you cannot access/download after troubleshooting. Not eligible Refunds are not available for: change of mind after successful import/use, preference (“not my style”), using unsupported software/versions not listed in requirements. Time window 7 days from purchase date. Required info from buyer Order ID, software name/version, and a screenshot (import error or download error). Access & Delivery Troubleshooting Flow Buyer checklist Re-download the ZIP; try another browser. Extract using a standard extractor (avoid mobile extractors if possible). Confirm software and version match the listed requirements. Try importing a single preset/LUT first to confirm path/format. Seller checklist Provide a fresh ZIP link + alternate mirror if needed. Provide “how to import” steps for supported apps. Provide a replacement file if corruption is suspected. Receipt Message Template (ready to paste) Download the ZIP and open README first (import steps + requirements). If you hit an import error, reply with your order ID + software/version + screenshot. FAQ (10) Q1: What do I get? A: A ZIP containing LUTs/presets + README import guide. Q2: What software is supported? A: Only what’s listed in the requirements section. Q3: I can’t import—what do I do? A: Confirm version, then follow README steps; email support with a screenshot. Q4: Can I use these commercially? A: Yes for your own projects; no redistribution/resale. Q5: Can I share with my team? A: Please purchase additional licenses for team use. Q6: Do you offer refunds? A: Yes for access/corruption/incompatibility within the policy window. Q7: I don’t like the look—refund? A: Style preference alone isn’t refundable after successful import/use. Q8: Will this work on mobile? A: Only if your app supports LUT/preset import per requirements. Q9: Are updates included? A: Minor fixes may be provided; new packs are separate. Q10: How fast is support? A: Email-only; replies within the stated support window. Support Reply Templates (10) Can’t download “Send your order ID + screenshot. Try another browser/incognito. If it fails, I’ll send a new link.” ZIP won’t extract “What device/OS are you using? Try extracting on desktop or with a standard extractor. I can provide a re-zipped file if needed.” Import error “Please share software + version + screenshot. I’ll confirm compatibility and provide the correct import path.” File seems missing “Tell me which file name you expected. I’ll confirm contents and send the missing file if it’s an error.” Refund request “Share order ID + reason. If it’s corruption/incompatibility/access within 7 days, I can refund.” “Not my style” “Understood—if you successfully imported and it matches the description, refunds may not apply. I can suggest settings to get closer to your target look.” Duplicate purchase “Send both order IDs; I’ll refund one or convert it to an extra license.” Pre-purchase question “Tell me your software + version and I’ll confirm compatibility.” Custom request “I can quote a custom pack separately—share examples + deadline + budget.” Hostile message “I can help once I have your order ID and a clear description of the issue.” Risk Notes + Mitigation Compatibility disputes → list supported versions clearly + require version in requests ZIP corruption claims → re-zip + mirror link + checksum note (optional) Preference refunds → clarify “style preference not refundable after import” Mobile extraction issues → recommend desktop extraction Disputes → calm template + fast reproduction steps Clarifying Questions (Only if needed) Which exact supported apps/versions should be named in the requirements?