Skip to content

Refund policy #2085

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Refund policy #2085

wants to merge 4 commits into from

Conversation

EVDOG4LIFE
Copy link
Contributor

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

…ranch to keep separate from SLA changes - Includes streamlined policy without internal review details - Updated navigation to include refund policy in policies section
@EVDOG4LIFE EVDOG4LIFE requested a review from stnguyen90 June 10, 2025 22:47
Copy link
Contributor

@stnguyen90 stnguyen90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work on the formatting.

Just a few comments.

Comment on lines +157 to +159
new: isNewUntil('31 July 2025'),
label: 'Refund Policy',
href: '/docs/advanced/platform/refund-policy'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this section is all about policies, we don't need to include "policy" here.

Suggested change
new: isNewUntil('31 July 2025'),
label: 'Refund Policy',
href: '/docs/advanced/platform/refund-policy'
new: isNewUntil('31 July 2025'),
label: 'Refund',
href: '/docs/advanced/platform/refund'

Make sure to update the file name too.

- **Incorrect setup or inactivity:** Customer misconfiguration, failure to complete onboarding, or lack of usage
- **Expired refund window:** Requests submitted more than 30 days after the transaction date
- **Third-party limitations:** Issues caused by third-party tools, plugins, or unsupported integrations
- **Terms of service violations:** Any usage found to be in breach of Appwrite's Terms of Service or Acceptable Use Policy
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We call it Fair use rather than Acceptable use and let's link to these.


To request a refund, please follow these steps:

1. **Submit your request** in writing through our Support portal
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's match the Uptime SLA instructions:

Suggested change
1. **Submit your request** in writing through our Support portal
1. **Submit a ticket** via the Appwrite Console

Comment on lines +59 to +61
# Policy updates {% #policy-updates %}

Appwrite reserves the right to update this policy to reflect changes in our services or business practices.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's make this match the Support SLA that was approved (including the contact page part). Ideally, we should have a partial and re-use it on all policies that need it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants