Developer Terms

Draft for legal review · Last updated [date]

These terms cover building and running an app on Wakeshift.

They have two parts: the General Terms, which apply to every app, and the Service Terms, which add rules for particular ways of running one. Our Data Processing Addendum ("DPA") is part of these terms, and so is the acceptable use section of our Terms of Service. Where they conflict, the DPA wins on personal data, and otherwise the Service Terms win over the General Terms.

Part 1: General Terms

1. Who these terms bind

These terms are between Clawvisor Inc. ("we", "us"), and you, the person or organization that registers an app ("you"). If you register an app for an organization, you agree on its behalf and confirm you're allowed to. You must be at least 18.

These terms bind you, not the people who use your app. You're responsible for your app's users and their use of Wakeshift through your app. Your own terms with them must be consistent with these terms and with our acceptable use rules.

2. Your app and its keys

• Describe your app accurately. Wakeshift writes the page where people approve your app from the description you give it (your app's manifest), so ask only for the access your app needs.
• Keep your app's key secret, and tell us at support@wakeshift.ai if it leaks. Wakeshift keeps only the public half of the key. You can replace the key or delete the app in the console.
• Test keys reach only people who use your app without a Wakeshift account. Live keys also reach people who sign in with Wakeshift. During the beta, ask us at support@wakeshift.ai and we'll turn on live keys for your app. We don't review apps first.
• We keep a log of what happens to your app (for example when it was created, when its key was replaced or first used, and when its description was published) and show it on the app's page in the console.

3. Your users

If anyone outside your own organization uses your app:

• Publish terms and a privacy policy, and link them from wherever people add your app to their agents. Your privacy policy must say what your app sends to people's agents through Wakeshift, why, who receives it, and how long it's kept.
• Give notice and get consent. Before people connect an agent, tell them your app uses Wakeshift to deliver messages to it, and get any consent the law requires for us to store and deliver those messages for you.
• Send only what your app needs. Don't send passwords, keys or other secrets to people's agents.
• Respect withdrawals. When someone withdraws their approval or removes your app, stop sending to them. Wakeshift stops delivering at once either way, and no agreement between you and your users can change that.
• Delete on request. When someone disconnects your app, asks you to delete their data, or stops being your user, delete what Wakeshift holds for them within 30 days by calling the app API's "forget user". Wakeshift keeps a user's data until you do, or until you delete the app.
• Handle their requests. You answer your users' requests about their data. If we receive one about your app, we'll forward it to you and may point the person to you.

4. Use of what you receive

Use the data and agent access your app gets only for what you described, and only while the person's approval lasts. Don't sell it, and don't use it to build profiles of people for advertising.

5. Suspension

We may limit, suspend or remove an app, or turn off its live key, if it breaks these terms or our acceptable use rules, or puts people or Wakeshift at risk. Where we can, we'll tell you first and give you a chance to fix the problem. If you think we got it wrong, write to support@wakeshift.ai and we'll look again.

6. Fees

Wakeshift is free for developers during the beta. If we start charging, we'll tell you at least 30 days in advance, and you decide whether to continue.

7. Ending

You can delete your app at any time. When you do, or when these terms end, we delete your app's data as the DPA says. We may end these terms with 30 days' notice, or at once for a serious breach. Sections 3, 4, 8 and 9 continue to apply after they end.

8. Disclaimers and liability

The disclaimers, the limitation of liability, and the disputes section of our Terms of Service apply to you as a developer. In addition, you're responsible for claims that arise from your app or from what it sends to people's agents, and you'll cover our reasonable costs of dealing with such a claim.

9. General

We post each version of these terms here with the date it takes effect, and tell you by email at least 30 days before a significant change. Contact: support@wakeshift.ai.

Part 2: Service Terms

A. Apps whose users don't sign up with Wakeshift

Your app can let people use it without a Wakeshift account. You give Wakeshift your own ID for each user, and Wakeshift keeps a record of that user's agents and the messages your app sends them, on your behalf.

• We handle this data as your processor, under the DPA. Its schedule lists what we keep and for how long.
• Wakeshift shows these users no approval page: adding your app to their agent is their approval, so your own sign-up or connect step must give the notice in section 3.
• Use a stable ID that doesn't reveal who the person is. Don't use an email address or a name.

B. Guest sign-in

Wakeshift's guest sign-in lets people use your app with no account at all, as our games do.

• Next to the step that connects an agent, show a line saying that continuing means agreeing to your app's terms and privacy policy, with links to both, and put the same line in the instructions your app gives the agent.
• Guests can't be identified, so say in your privacy policy how long you keep their data, and let them delete it with the link or name they used.

C. The wakeshift program and connectors

The wakeshift program and its connectors are open source: we publish their code at github.com/wakeshift/connectors under the Apache License 2.0. So are the SDKs for building apps, for TypeScript at github.com/wakeshift/wakeshift-node and for Go at github.com/wakeshift/wakeshift-go, and the code of our own apps, at github.com/wakeshift/apps. You may point your users to them, bundle them, or change them under that license. If you change them, don't present your version as ours: the license covers the code, not our names or logos, so an app you build from ours needs its own name.