Refund Policy

Last Updated: May 2026

Due to the digital nature of the services, access privileges, and architectural configurations assigned to profiles upon framework activation, Floy enforces a strict operational performance refund protocol.

Core Condition: Refunds are strictly restricted and only issued if the Floy Toolkit encounters an internal functional system failure or asset delivery error, and our technical engineering department cannot correct the malfunction.

1. Scope of Coverage

This policy uniquely covers the structural functions of the Floy Toolkit, which consists of the Bulk Email Sender Domain Reputation tracking array, the Email Verifier processing architecture, and the Spam Score Checker engine. Disagreement with software layout variations or adjustments in internal business criteria do not constitute valid grounds for refund generation.

2. Mitigation Requirement

Before any credit processing execution can open, users must submit detailed log logs of the failure to our node network support pipeline. Our team maintains a baseline period of seven (7) business days to repair, patch, or work around the reported code asset breakdown.

3. Non-Eligibility Parameters

No returns are granted under conditions involving profile restrictions due to system security protection triggers, intentional honeypot abuse, or external IP blockages stemming from high-volume cold outreach setups configured outside our target boundaries.