Our Refund Policy
We are committed to fair and transparent refund practices to ensure your satisfaction and service reliability. This policy outlines the conditions under which refunds may be granted for our personal use plans.
Refund Eligibility Criteria
Monthly Service Downtime
You may be eligible for a refund if our services experience significant downtime within a 30-day period:
- Total service downtime exceeding 3 days within a 30-day period.
- Continuous, uninterrupted service downtime for 2 consecutive days.
Model Availability Issues
You are eligible for a refund under the following model availability conditions:
Refundable: Chat Completion Models
- If any state-of-the-art model designated in your plan (Basic or Pro) is not working for more than 2 consecutive days, you are eligible for a refund.
- This policy applies exclusively to chat completion models included in your subscription tier.
Non-Refundable: Additional Services
The following services are provided out of generosity and are not eligible for refunds:
- Image Generation - Creative AI image creation tools
- Text-to-Speech - Voice synthesis capabilities
- Embeddings - Text vectorization services
- Speech-to-Text - Audio transcription features
- Image Editing - AI-powered image modification
- Video Generation - AI video creation tools
API Compatibility Claims
Non-Refundable Cases:
- General tool or library incompatibility issues not directly related to A4F's API specification.
- Compatibility issues with individual third-party services that are not guaranteed by A4F (e.g., specific versions of OpenAI SDK if not claimed as fully compatible by A4F).
Refundable Cases (Subject to Verification):
- Proven non-compatibility with A4F's documented API standards for core functionalities.
- Demonstrated incompatibility with an API standard explicitly claimed as supported by A4F (e.g., specific versions of OpenAI API compatibility if advertised).
Credit Usage and Refund Eligibility
Refund eligibility is contingent upon proportional service usage relative to your subscription investment:
Usage-Based Refund Assessment
Principle: Refund eligibility is directly proportional to service utilization. Users with zero or minimal usage ($0-3) due to technical issues from the beginning have clear refund eligibility. However, when you pay very little and consume disproportionately massive amounts—consuming $1,000-3,000+ on a $15 plan or $2,000-6,000+ on a $25 plan—refund eligibility becomes logically and financially untenable.
Rationale: Extensive usage patterns fundamentally contradict claims of service instability. If our service were truly unreliable, logical users would discontinue usage rather than continue consuming thousands of dollars worth of resources. The mathematics of paying $15-25 while consuming $1,000-6,000+ worth of services, then requesting full refunds, creates an unsustainable business model that would compromise our ability to serve all customers.
Non-Refundable Usage Scenarios
$15 Basic Plan Examples:
- User consumes $1,000+ worth of API credits, then requests refund citing service instability
- User processes $2,000+ worth of requests over multiple sessions, then claims uptime issues
- User generates $3,000+ worth of content, then requests full refund for "unreliable service"
$25 Pro Plan Examples:
- User consumes $2,000+ worth of API credits, then requests refund citing service instability
- User processes $4,000+ worth of requests over multiple sessions, then claims uptime issues
- User generates $6,000+ worth of premium model outputs, then requests full refund for "poor performance"
Our Perspective as a Small Company:
We want to be transparent about the reality we face: when you consume $1,000-$2,000 worth of credits on a $25 subscription, those are real costs that we bear. As a growing company, we pay our AI providers for every token processed, every image generated, and every API call made. High-volume usage genuinely impacts our infrastructure and operational costs.
When someone uses our services extensively and then requests a full refund citing instability, it puts us in an incredibly difficult position. We've already incurred the real expenses of serving those requests, often at a significant loss, and a full refund would compound that financial impact on our small team.
Exceptional Cases - Partial Refund Consideration:
However, we believe in doing what's morally right. If you genuinely believe your situation is exceptional and you have a valid moral case despite high usage, we may consider a partial refund that reflects both your concerns and the real costs we've incurred. Each case will be evaluated individually with empathy and understanding of both perspectives.
Standard Assessment: Such usage patterns typically demonstrate that the service was sufficiently stable and functional to support extensive consumption. Full refund requests under these circumstances generally cannot be processed, as they would create unsustainable business conditions for our small company.
Legitimate Refund Scenarios
Logical Usage Pattern: User experiences genuine service issues early in their subscription period and discontinues usage, resulting in minimal credit consumption relative to their plan cost.
$15 Basic Plan Examples:
- User subscribes but cannot use service due to technical issues from the beginning, with zero or negligible usage
- User encounters immediate service problems and discontinues usage early in subscription period
- User experiences persistent API instability from start, attempts minimal usage before requesting refund
- User faces genuine uptime issues, processes limited requests before seeking refund (usage remains proportionally reasonable to subscription cost)
$25 Pro Plan Examples:
- User subscribes but cannot use service due to technical issues from the beginning, with zero or negligible usage
- User encounters immediate service problems and discontinues usage early in subscription period
- User experiences persistent API instability from start, attempts minimal usage before requesting refund
- User faces genuine uptime issues, processes limited requests before seeking refund (usage remains proportionally reasonable to subscription cost)
Assessment: These usage patterns are consistent with genuine service concerns and demonstrate responsible user behavior when encountering technical difficulties.
Important Clarification: Legitimate Service Issues vs. Fraudulent Claims
✅ We WILL Support You in Genuine Service Failures:
If you've been using our service successfully for 15-20 days and suddenly encounter legitimate technical issues, service outages, or performance degradation—that's clearly our responsibility. We will absolutely offer you a partial or full refund because that represents a genuine service failure on our part, regardless of your usage up to that point.
❌ We CANNOT Support Fraudulent Refund Attempts:
However, if everything has been working perfectly, you consume massive amounts of credits (sometimes 100-400x your subscription cost), and then suddenly claim the service is "unstable" or "unreliable"—this pattern suggests an attempt to receive services for free rather than reporting genuine technical issues.
🤝 Our Promise to Honest Users:
If you're not attempting to defraud us, if your concerns are genuine, and if you're acting in good faith—we will work with you to find a fair solution. We believe in treating honest customers with empathy and understanding, even when situations don't perfectly fit our written criteria.
The key question we ask ourselves: "Is this user genuinely experiencing issues, or are they trying to game the system after heavy usage?" Your usage patterns, timing of complaints, and communication style help us make this determination fairly.
Technical Evaluation: All refund requests undergo comprehensive usage analysis including credit consumption patterns, session frequency, API call distribution, and temporal usage correlation with reported issues.
Transparency Commitment: We maintain detailed usage analytics to ensure fair and evidence-based refund assessments. Users can request their usage reports for transparency during the refund review process.
This refund policy is designed to balance user protection with service sustainability. All refund requests are carefully reviewed on a case-by-case basis. We strive to maintain 99.99% uptime for our core services and will communicate proactively about any significant service disruptions.
Our Commitment: We Believe in Fair Treatment
At A4F, we understand that technology can sometimes be complex, and genuine concerns deserve genuine solutions.
Here's our promise: We don't engage in disputes over legitimate refund requests. Our experience shows that users who seek refunds typically have valid concerns, not fraudulent intentions.
Beyond the Policy: Human Understanding
Even if your situation doesn't perfectly match our formal criteria, we evaluate each case with empathy and understanding. If we believe your concern is genuine and reasonable, we will process your refund at no additional cost—because doing right by our customers is more important than rigid policy enforcement.
Refund Process
Contact Support & Submit Request
To request a refund, please reach out to our support team through the Help Center on our website or by contacting us via our official channels: Telegram, Instagram, Discord (@devsdocode), or Twitter/X. Provide your account details, the reason for the refund, and any supporting evidence (especially for API compatibility or downtime claims).
Review Process
Our team will acknowledge your request and begin a review process. This may involve verifying your claim and account history. We aim to complete this review within 1-2 days. However, for most cases, we resolve requests within 6 hours to ensure thorough evaluation.
Decision & Processing
Once a decision is made, we will notify you. If your refund is approved, it will be processed to your original payment method.
Confirmation
You will receive an email confirmation once the refund has been successfully processed from our end.
Frequently Asked Questions
Still have questions?
Our support team is here to help with any questions about our refund policy or to assist with processing your refund request. You can reach us via our official channels: Telegram, Instagram, Discord (@devsdocode), or Twitter/X.