Privacy.

RowTech is run by Caden Polk, based in Ohio, United States.

For anything on this page, write to polkcade27@sehs.net.

The form on the apply page asks for:

• your name, your email address, and your club, school or program;
• if you add them: whether you’re a coach, a club or program, an athlete or something else; the boats you row; where you row; and your message.

It also sends which link brought you here:

• which of this site’s beta links you used, or the from tag on a link to the form;
• if the link you first came to the site on had them, its utm_source, utm_medium, utm_campaign, utm_term and utm_content tags (a ref tag counts as utm_source);
• if another website linked you here, that website’s domain: not the page, just the domain.

All of it is stored with your application in RowTech’s database, on Supabase. We use this to talk to you about the beta, and we note which link brought you here.

Once an email address has applied, applying again with it doesn’t change or add to the application we have.

The dashboard is for beta crews. Typing an email address into the sign-in form never makes an account.

An account holds its email address. Sign-in runs on Supabase Auth, which keeps the account and sends the sign-in links. Signing in sets Supabase’s sign-in cookies on this site; they keep you signed in to the dashboard, and nothing else uses them.

From a Force node’s session files, the dashboard keeps:

• the files themselves (meta.json, strokes.csv, curves.bin and events.csv), in Supabase Storage;
• each stroke’s force and timing figures, in the Supabase database;
• the seat number, the node’s ID and the session’s ID, from meta.json;
• when the session was rowed, and the boat’s name and a name for the session if you give them;
• which side each seat rows, if you set it.

If you aren’t on a team yet, your first upload makes one, named “My crew”. Teams made earlier were named after the part of the owner’s email address before the @. Everyone on a team can see everything uploaded to it.

The dashboard also keeps which account uploaded each session, and who is on each team and in what role: owner, coach or member.

The dashboard has a place for a GPS track of each outing, which will come from Vieve, the RowTech cox box. Vieve is in development, and nothing uploads a track today.

Session data describes the rowers in each seat, who may never use the dashboard themselves. So upload only the node’s session files, and don’t put rowers’ names or other personal details in session or boat names (see the Terms). Before you upload a crew’s sessions, let the rowers know, and for rowers under 18, their parents or guardians too.

A rower, or a rower’s parent or guardian, can ask their coach to delete a session from the dashboard, or write to us and we’ll delete it.

Vercel hosts the site and the dashboard, so every visit to them goes through Vercel.

Every page, on the site and in the dashboard, also runs Vercel Web Analytics and Vercel Speed Insights, which send information about each page visit, including which page it was, to Vercel.

Vercel says neither uses cookies or identifies you. Web Analytics records the page’s address, the site that linked you there, your approximate location (country, region and city), and your browser, operating system and type of device. It tells visits apart with a code made from each request, and discards that after 24 hours. Speed Insights records the page, how fast it loaded, your network speed, browser, operating system, type of device and country. Vercel’s own pages on Web Analytics and Speed Insights have the details.

For the beta form, the site keeps two small notes in your browser:

• in this tab’s session storage (rt_attr): the utm tags of the link you came in on, and the domain of the website that sent you, if one did. It goes when the tab is closed.
• in local storage (rt_cta): which of this site’s beta links you last used. The apply page reads it and removes it when it opens, unless the link to it had a from tag of its own, and uses it only if it’s less than five minutes old. Until then it stays in your browser.

Neither note leaves your browser unless you send the beta form. The utm tags are also part of the address of the page you came in on, which goes through Vercel like any other visit.

• Supabase: the database, sign-in and file storage behind everything above.
• Vercel: hosting, Web Analytics and Speed Insights.

That’s the whole list. The site’s fonts come from this site, and the dashboard’s map draws only your outing’s track, with no map tiles from anyone else.

It’s all stored and processed in the United States: Supabase keeps it in its us-east-1 region (Northern Virginia), and Vercel runs the site in its Washington, D.C. region. If you’re outside the United States, your information goes there. Everything between your browser, Vercel and Supabase travels encrypted over HTTPS, and Supabase encrypts what it stores.

Nothing is deleted automatically. Beta applications, dashboard accounts and uploaded sessions are kept until they’re deleted: a team’s owners and coaches can delete sessions themselves, and we delete anything you ask us to (see Your requests). Vercel keeps its analytics under its own rules.

For people in the UK and the EU, the legal basis for each use is:

• your beta application: our legitimate interest, and yours, in replying to you and running the beta you asked to join;
• your dashboard account and what you upload: providing the dashboard you signed up to use;
• which link brought you here, and Vercel’s analytics: our legitimate interest in knowing how people find the site and how well it works, using information that doesn’t identify you;
• the sign-in cookies: they’re needed to keep you signed in.

A team’s owners and coaches can delete a session themselves, from the session’s page in the dashboard.

You can ask us to show you, correct, export or delete the information we hold about you, to withdraw your beta application, or to close your dashboard account. Write to polkcade27@sehs.net from the email address you used with us, so we know the request is yours. We’ll reply within 30 days.

If you’re in the UK or the EU, you can also complain to your data protection authority.

Rowers under 18 can apply for the beta. The site and the dashboard aren’t meant for children under 13, and we don’t knowingly collect personal information from them: a rower under 13 should ask their coach to apply instead. If you think we have information from a child under 13, write to us and we’ll delete it.

The terms for beta crews and for the dashboard are on the Terms page.