Skip to content
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

The promised Core Values should be entrenched in the Terms of Service #28

Open
jimrhiz opened this issue Aug 25, 2012 · 2 comments
Open

Comments

@jimrhiz
Copy link

jimrhiz commented Aug 25, 2012

At the bottom of the TOS page we see

App.net has made a promise to its users and developers. Learn more

with a link to http://join.app.net , where the promise is stated as "Core Values", frequently using the words "never" and "always".

That promise was a vital part of what made Dalton's proposal attractive.

Shouldn't the promise not only appear in the TOS, but be entrenched there with a guarantee that what is promised will not be changed?

I see parts of the promise in the TOS and Privacy Policy, but they are certainly not entrenched ("We reserve the right to modify these Terms at any time."). Furthermore, the clear and plain language of the promise is not reflected in the quite legalistic language of the ToS. It's not that I don't have trust in the intentions of Dalton and the team, but circumstances and teams can change; the promise and the Core Values should not change.

For the record, I'm quoting the promise here. (As one example of the significance of this, issue #17 about deletion is just a special case of the "You own your content" section of the promise.)

APP.NET CORE VALUES

We are selling our product, NOT our users.
We will never sell your personal data, content, feed, interests, clicks, or anything else to advertisers. We promise.

You own your content.
App.net members will always have full control of their data. Members have the fundamental right to easily back-up, export, and delete ALL of their data, whenever they want.

We will align our financial incentives with members & developers.
In this paid model, the more people that value our service highly enough to pay for it, the more money we make. Our financial incentives are entirely tied to successfully delivering a service you can depend on, not on holding our ecosystem hostage.

App.net employees spend 100% of their time improving our services for you, not advertisers.
Rather than waste most of our engineering time coming up with new and exciting ways to sell your personal data to advertisers, 100% of our engineering and product team will be focused on building the most innovative and reliable service we can.

We will operate a sustainable, predictable business.
App.net will always have a clear business model. We know that depending on services that could go away or desperately squeeze users for more and more money is a toxic cycle.
We want our ecosystem to rest easy that App.net is built on a financially solid foundation.

We respect and value our developer community.
We believe that developers building on our platform are increasing the value and attractiveness of our service to paying members, and thus our financial interests are fundamentally aligned. We hope developers build large, robust businesses on top of our platform. Even if it means that we will likely forgo some huge future revenue streams, we will NEVER screw developers acting in good faith.

Our most valuable asset is your trust.
Many people have become so cynical about user-hostile, privacy-violating social services that they refuse to participate at all. We can understand why. Earning your trust is the most important thing we can do. It won't be easy, and we will make some mistakes, but we will do our best to be honest and transparent.

@mattflaschen
Copy link
Contributor

Excellent idea.

@katcaverly
Copy link

To codify (excuse the pun) the promise of App.net in the ToS explicitly, and to say what can never be changed, explicitly, would truly be ground breaking.

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

No branches or pull requests

3 participants