basecamp / policies

This project is no longer maintained. All of our policies can be found at 37signals.com/policies now. If you’d like to be notified when policy changes happen, please join the mailing list at 37signals.com/policies/updates.

37signals Policies, Terms, and Legal Stuff

The rough print and the fine print. We try to make all our policies as clear, fair, and readable as possible.

• Terms of Service
• Privacy policy
• California Resident Notice at Collection
• Cancellation policy
• Refund policy
• Use Restrictions policy
• Security overview
• Until the End of the Internet
• Taxes
• Account ownership information for Basecamp 2 and Basecamp 4
• Service Level Agreement (SLA) for Basecamp Big
• How to manage the HEY account of someone who is incapacitated or has died
• HEY for Domains Ownership and Management Policy

A Note About the Email Addresses

If you try to click on any of the Support links in this repository, you'll get a 404 page. Don't despair! You can always reach us at [email protected]. Highrise customers can also email [email protected] and HEY users can reach out to [email protected]. Your emails all go to our same friendly Support team.

So how come the links don't work in this repository? The short answer is: we made a technical tradeoff. The long answer is, we copy the policies in this repository to our product marketing sites. To make it easier to transfer, we are now using relative links, this Jekyll plugin to convert Markdown links to a valid web URL, and some Liquid variables.

Public Contributions Welcome

We welcome our customers—you!—to suggest changes to our policies and to offer feedback on the changes we have planned. Please do chime in on any open pull request, or even file a pull request yourself.

Steal These Policies

You're free to use these policies in your own organization under the Creative Commons Attribution license. Edit them. Adapt them to your needs. Share them. Put them to work.

An example of a brief, unobtrusive attribution for your own policies that you've based on ours:

Adapted from the Basecamp open-source policies / CC BY 4.0

Here's how you could re-share your own policies under a CC license with attribution:

MyCorp policies are open source, licensed under CC BY 4.0. Adapted from the Basecamp open-source policies / CC BY 4.0.

policies's Issues

what a bizarre statement to make...

"ideologies like white nationalism,"

Broken 'contact us' link

The contact us link on the what happens when you cancel? page is broken.

We do and will not

In policies/privacy/index.md,
under Your Rights With Respect to Your Information,
the first line of Right to Non-Discrimination reads
"This right stems from the CCPA. We do and will not charge you a different amount..."
I assume it should read "We do not and will not..."

BTW thanks for sharing this!

Broken researchers list

https://github.com/basecamp/policies/blob/master/security/vulnerability-response.md

List of researchers are not rendering correctly.

#HighKnowledg3

Open sourcing the Basecamp DPA in hellosign

It will be super duper great if you guys can add Basecamp DPA in hellosign, in github and open source it.

https://app.hellosign.com/s/c0908a3d

Security policy has missing links

The links to the security white paper and to the security incidenct response page are missing from the security policy.

Converting the whole thing to jekyll

Hi,

We are so happy that Basecamp did smth like this. So amazing. We will use it in Remoteteam.com

I started to copy-pasting , replacing basecamp with Remote Team. It sort of need some work :). Change email, company name, etc etc, links ( they are all like /security/overview.md)

will you guys be ok to make this totally a jekyll site and make company name, email as variables. ?

Suggestion: Attribution Example

Hey, thanks for this great repo! It'd be great if more companies had policies that users can actually understand (a friend recently suggested companies should require developers to read their company's privacy policy when they start and when it changes).

It'd be great to have an example of preferred attribution in the readme. Here's a minimal one I came up with based on the "pretty good attribution" example in the Creative Commons wiki:

Adapted from Basecamp / CC BY 4.0

Let me know what you think.

Edit: I imagine the ideal case for most companies is no attribution (to appear more professional), but the current license doesn't allow for that. I'm not sure if that's a possibility (as the current license is already generous), but wanted to throw it out there. For instance, GitHub's balanced employee IP agreement is CC0 (public domain).