-
Notifications
You must be signed in to change notification settings - Fork 8
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
update t&cs #578
base: main
Are you sure you want to change the base?
update t&cs #578
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -7,7 +7,7 @@ slug: /terms-of-service | |||
|
|||
# Terms of Service | |||
|
|||
Last updated: February 06, 2024 | |||
Last updated: Feb 06, 2025 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How's that a year later to the day
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a few comments
|
||
No Refunds: All payments are non-refundable. We do not provide refunds or credits for any unused service, partial subscription periods, downgrades, or cancellations. | ||
|
||
Pricing Changes: We reserve the right to modify our pricing at any time. Any changes will be communicated in advance and will take effect at the start of the next billing cycle. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add an exact time, for example, "two weeks before the next billing cycle"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer not to create arbitrary commitments, I think in this case we'd likely update with more than two weeks but the above wording affords more flexibility.
docs/HyperIndex/terms-of-service.md
Outdated
Our products are currently provided on a free-to-use basis. We reserve the right to introduce charges for these services at our discretion. Any pricing changes will be communicated to users in advance. | ||
Our services are provided on a paid basis. By subscribing or making a payment, you agree to the applicable fees and billing terms. | ||
|
||
Billing & Payment: Fees are charged upfront based on the selected plan. Any additional unit fees exceeding the included base usage will be billed separately at the end of the calendar month. Payments must be made via the payment methods we support. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might decide to start sending an invoice earlier if the extra hours bill exceeds X amount. We need to decide how we want to implement this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know we spoke about this, will lean over and double check if we're happy with 2.5x
docs/HyperIndex/terms-of-service.md
Outdated
|
||
Pricing Changes: We reserve the right to modify our pricing at any time. Any changes will be communicated in advance and will take effect at the start of the next billing cycle. | ||
|
||
Cancellation: Subscriptions can be canceled at any time, but cancellations take effect at the end of the current calendar month for monthly subscriptions. For annual subscriptions, cancellations will take effect at the end of the current annual billing cycle. Previously paid fees will not be refunded. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"but cancellations take effect at the end of the current calendar month for monthly subscriptions". I think it's the same as for annual subscriptions - at the end of the billing cycle.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. I think either would be acceptable, the current is more verbose, but I'm not sure a change is necessary.
f60860c
to
7627d1d
Compare
: