Terms of Use

Who you are agreeing with

SwimScript is operated by spinrag, LLC, a limited liability company registered in New York, USA. You can reach us at [email protected].

We are reachable at [email protected]. If you need a postal address — for a formal notice, or because your own obligations require one — ask and we will provide it.

Your practices are yours

You own everything you write in SwimScript. Your practices, your saved sets, your section headings and anything you import are your work, and putting them into this tool does not transfer them to us.

We claim no ownership of your content. We do not sell it, license it, publish it, or use it to train anything. The permission we need is narrow and purely operational: to store your practices, to show them back to you and to the workspace they belong to, and to keep the backups that running a service responsibly requires. That is all, and it ends when your content is deleted.

A coach handing over years of written practices is entitled to ask what happens to them. This is the answer, and it is meant to stay the answer.

Personal workspaces and teams

Every account gets a personal workspace of its own, created when you first sign in. What is in it is visible only to you.

A team workspace is shared. Everyone in a team can read everything in that team's workspace, and members with a coach or admin role can change it. If you write a practice in a team's workspace, you have written it somewhere your teammates can see — that is what the team workspace is for.

Moving a practice from your personal workspace into a team is designed but not yet built. When it is, it will copy the practice rather than move it: your original stays in your own workspace and stays yours.

When you leave a team, the practices you wrote there stay with the team, and your name is cleared from them so that you are no longer recorded as their author. A squad should not lose the sessions it is already running because a coach moved on, and a coach who has left should not still be named on a team's work. That is the intended behaviour and it is not built yet: today, leaving a team removes your membership and nothing else.

Using SwimScript

The rules are short, because SwimScript is a planning tool and not a place where anything is published.

Do not use SwimScript to break the law. Do not try to reach another workspace's data, or probe the application for a way to. Do not upload malware. Do not resell access to an account.

You must be 13 or over to have an account, and by creating one you confirm that you are. We do not verify it; if we learn otherwise we will close the account. Swimmers write their own sets, and plenty of assistant coaches are still in high school — there is no good reason to shut either of them out.

Separately, do not use SwimScript to store information about anyone else under 18 — not their name, not a note about them, not anywhere in a practice. That applies however old you are: it is about who a practice is about, not who wrote it. Writing about yourself is fine at any age this account is open to; the rule is there to protect people who did not sign up. Supporting age-group and school teams is intended, but the consent and parental-access machinery that would make it safe has not been built. The Privacy Policy explains what is missing.

Beyond that, what you write in your own practices is your business. There is no moderation, because there is no audience: nothing you write is public, and nothing is shown to anyone outside the workspace it lives in.

SwimScript is not coaching advice

SwimScript adds up yardage and estimates how long a practice will take, using a pace model and whatever pace settings a workspace has been given. These are arithmetic, not judgement.

The estimates are approximations from a model, and the model is calibrated against a small number of real practices. It does not know your swimmers, your pool, the water temperature, who is injured, who is fourteen, or who came in tired. It is a planning aid and nothing more.

Nothing in SwimScript is coaching, medical, safety or training advice. Every decision about what a swimmer actually does in the water remains yours. You are responsible for the safety and the suitability of the practices you write and run, exactly as you would be if you had written them on paper.

Availability

There is no uptime commitment. SwimScript can go down: for maintenance, for a deployment, or because something broke.

We will try to keep it running and to keep your data intact, but this is a service provided as it is, without a guarantee that it will be available when you want it.

Keep your own copies of anything you cannot afford to lose. SwimScript prints, and a printed practice works on a pool deck whether or not the site is up.

Getting your data out

There is no export button and no self-service account deletion yet. Both are open work. Until they exist you can print or copy a practice out of the editor, and anything more has to be asked for at [email protected] and done by hand.

This is stated here rather than left out, because a terms page that implies a way out that does not exist is worse than one that admits there is not one.

Ending it

You can stop using SwimScript at any time.

We may suspend or close an account that is being used to attack the service or other users, or where we are required to. Short of that, we will not close your account without telling you.

When you close your own account, Download my data gives you everything you wrote first — practices as markdown, plus a structured copy — and you should take it before you confirm, because the export goes with the account.

What then happens is set out in the privacy policy: your own workspace and its practices are held for thirty days and can be restored in that window by emailing [email protected]; practices you wrote in a team stay with the team, with your name taken off them. After thirty days there is nothing left to restore.

If we close an account, the same thirty days apply, and we will tell you before the window starts rather than after it ends.

Changes to these terms

The date at the top of this page is the date these terms last changed.

If we change something material we will email the address on your account, and the change takes effect a reasonable time after that so you can read it and decide. Small corrections get the new date and nothing more.

Account email is being set up as this is written, so until it works a material change will be announced on this page rather than sent to you.

Liability

We do not limit our liability here, because no such limitation has been written.

A limitation of liability is the part of a terms page that most needs a lawyer, that varies most by jurisdiction, and where a confident-sounding paragraph written by someone unqualified is actively harmful: it can be unenforceable, it can be unfair, and it can give a false sense of what is covered.

Rather than write one badly, there is none. The practical effect is that you get more protection here than a typical terms page offers, not less. If a limitation is added later it is a material change, and you will be told.

Governing law

These terms are governed by the law of the State of New York, USA, and any dispute about them or about SwimScript would be heard by the state or federal courts sitting in New York.

If you live somewhere whose law gives you rights that cannot be signed away, that law still applies to you and this section does not take those rights from you.

Privacy

How SwimScript handles your data is described in the Privacy Policy.