Skip to content

Conversation

@unknwon
Copy link
Contributor

@unknwon unknwon commented Feb 12, 2025

@vercel
Copy link

vercel bot commented Feb 12, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sourcegraph-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 12, 2025 8:23pm


## Are there any refunds for the subscription?

We don't offer refunds, but if you have any queries regarding the Enterprise Starter, please write to [email protected], and we'll help resolve the issue.
Copy link
Member

Choose a reason for hiding this comment

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

This is not aligned with our terms IMO, see section 8.3 of https://sourcegraph.com/terms/cloud

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmm, these are the ~exact words copied from Cody Pro

image

Copy link
Contributor Author

Choose a reason for hiding this comment

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

God damn it, our dark background page design literally killed my eyes. I think it actually aligns?

All fees and charges are earned upon receipt by us and are nonrefundable unless negotiated otherwise

Contacting support is applicable for "negotiated otherwise"? BTW this repo and our comments here are public.

Copy link
Member

Choose a reason for hiding this comment

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

I think the "or (b) as required by applicable law." section is missing here for me.

Maybe we could link to terms? (deeplinking is sadly broken there)

Not a lawyer but this statement feels incomplete to me. Won't block here but I think it could use some wordsmithing haha

Copy link
Contributor Author

Choose a reason for hiding this comment

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

deeplinking is sadly broken there

Already asked for a fix! https://sourcegraph.slack.com/archives/CNC4YAL1E/p1739389461245829 so we can still do deep link and wait for it to be fixed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Let's wait for legal response first!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nudged again on the Legal thread for a suggested wording. If we couldn't get a effective response by tomorrow, I am gonna merge as-is first.

Copy link
Member

@eseliger eseliger left a comment

Choose a reason for hiding this comment

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

unblock

Copy link
Contributor

@MaedahBatool MaedahBatool left a comment

Choose a reason for hiding this comment

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

LGTM thanks

@MaedahBatool
Copy link
Contributor

@unknwon please merge if we are ready. :)

@unknwon
Copy link
Contributor Author

unknwon commented Feb 13, 2025

@unknwon please merge if we are ready. :)

We are waiting for Legal response for the exact wording to be used/updated here, will update and merge once we are ready.

@unknwon
Copy link
Contributor Author

unknwon commented Feb 18, 2025

Merging as-is and will follow up later once we get a firm response from Legal.

@unknwon unknwon merged commit fb70e21 into main Feb 18, 2025
5 checks passed
@unknwon unknwon deleted the jc/es-billing branch February 18, 2025 14:51
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.

4 participants