Refund & Cancellation Policy

Read this before paying.

If your account is suspended or terminated for violating SnapDeploy's Acceptable Use Policy, you forfeit all refund rights, in full, with no exceptions, including:

• The 3-day money-back guarantee on first-time Always-On purchases (section 2.1) — forfeited even if the violation is detected on day 1
• Any unused portion of a paid subscription period (monthly or yearly), including pro-rata refunds you would otherwise receive on cancellation
• Any unused GPU credit balance, regardless of when purchased
• Any unused add-on purchases (databases, custom domains, always-on subscriptions, any other paid feature)

Violations triggering full forfeiture include, but are not limited to: deploying tunneling tools (cloudflared, ngrok, frpc, sshx, bore, chisel, tmate, ttyd, etc.), VPN or proxy panels (V2Ray, Xray, Trojan, Shadowsocks, 3x-ui, x-ui, Hysteria, Sing-Box, gost, etc.), remote-shell / SSH server / VNC / RDP / web-shell pivots (openssh-server with public root login, shellinabox, dropbear, x11vnc, tigervnc, xrdp, guacd, code-server-as-pivot), web proxies designed to bypass network filters (Mercury Workshop / Scramjet, Rammerhead, Interstellar, unblocked-games frontends, generic open proxies), Telegram bot frameworks (Pyrogram, Telethon, telegraf, etc.), video piracy, torrent clients, or cloud-storage file-relay proxies (yt-dlp, qBittorrent, Sonarr/Radarr/Prowlarr, Alist, etc.), view-manipulation or credential-stuffing bots, game-server AFK bots (mineflayer, Aternos keep-alive, etc.), cryptocurrency miners (XMRig, T-Rex, NBMiner, lolMiner, etc.), and any attempt to circumvent platform security controls (binary obfuscation, base64 encoding, executable renaming, multi-stage hide layers, multi-account abuse to bypass resource caps).

Charge-back disputes: Payments made in connection with policy-violating deployments may be reported by us to the payment processor (Razorpay, the issuing bank, and the card network) as fraudulent or otherwise abusive use of the platform. Filing a charge-back dispute on a payment connected to a documented AUP violation is itself grounds for additional enforcement, including reporting to the credit-reporting infrastructure and pursuing collection of any outstanding infrastructure costs we incurred on your behalf.

Multi-account abuse: If a banned user signs up under a new email, payment method, or GitHub identity to evade enforcement, all payments made under the new account are also non-refundable upon detection of the evasion attempt.

If you are unsure whether what you intend to deploy is permitted, contact [email protected] BEFORE paying. We will tell you straightforwardly. We do not refund payments made by users who deploy a policy-violating workload first and then discover the policy after suspension.