Terms of service (draft)
Last changed with front v0.1.0.
1. Who provides the service
reach.rest is provided by legal entity TBD, at registered address TBD. The governing law and the venue for disputes are TBD. These are open items, not omissions.
2. What the service is
The service is a plugin that runs in your coding sessions and a hub at portal.reach.rest that stores what the plugin banks and shows it on a dashboard. It is described on how it works. Nothing described elsewhere on this site as not built or not ruled is part of the service today.
3. Accounts and access
Your identity is your email address: the same address receives your sign-in code and identifies you to the hub. You are responsible for the security of that mailbox, because whoever holds it can sign in as you. Your machines each hold a token, issued for 30 days and refreshed at the start of a session. Removing a member revokes that person's live tokens.
An org is a cohort or a team. Today one person belongs to one org, and only we create orgs and bind projects to them. The owner of an org decides who is a member of it.
4. Your content
You keep every right you have in your projects and your code. The plugin banks a record of your work — a map of each commit and a view of the build — to the hub so your org's dashboard can show it. We use that record to run the service for your org. We do not claim ownership of your work.
Members of your org with the right role can see your org's dashboard. That is the purpose of the product: a mentor checks a cohort's process and a manager checks a team's progress.
5. Acceptable use
Do not use the service to break the law, to attack it or anyone else through it, or to get at another org's records. Do not share your sign-in code or your machine token.
6. Payment
Payment is not available on this site yet and no price has been announced. When it is, this section will state the billing period, renewal, refunds and what happens when a subscription lapses. TBD
7. Availability and change
The service is under active development and parts of it change. We do not promise an uptime figure here; when we are prepared to commit to one it will be written here rather than implied. TBD
8. Ending it
You can stop using the service at any time and ask for your member record to be removed, which revokes your machine tokens. We may suspend an account that breaks section 5. What happens to banked records after an account ends is TBD and will be stated here and in the privacy notice before payment opens.
9. Liability
TBD — this section needs a lawyer, and a placeholder is more honest than a clause copied from somewhere else.
10. Changes to these terms
While this draft stands, it can change without notice. Once the reviewed version is in force, material changes will be announced to account holders before they take effect.