Privacy

Swervely can send a small amount of anonymous usage data, like which pages and features get used and on how many laptops. It's on by default. The app tells you that the first time it opens, and you can turn it off with one click.

This page isn't about your robot's telemetry. Swervely doesn't send robot data anywhere itself. If you use an AI assistant, what it reads goes to that assistant's company.

What it sends

  • A random install ID. Your laptop makes it up the first time Swervely runs, and it isn't based on anything about you or the laptop. You can reset it in Settings, and then the laptop counts as a new one.
  • The app version, your operating system and its version, your language and region, like en-US, and your time zone as a number of minutes from UTC, so a team's evening counts as one day.
  • Which features get used, for example that a page opened, a deploy worked, a hardware check ended in a pass or an AI chat started with a certain assistant. These are only fixed words, true or false values, and counts like how many tuning values were saved.
  • Anonymous crash signatures. Each one is a short code, usually made from where in Swervely's own code something went wrong. When there's no location, it's made from the kind of error and its text with every number taken out. Only the code is sent, never the text.

When a batch of events arrives, the server notes which country it came from as a two letter code like US. It doesn't note anything more precise than that.

What it never sends

  • Names, team numbers, usernames or computer names.
  • Robot code, file paths, OpMode or class names.
  • Telemetry values, or which tuning values changed and to what.
  • Anything typed to an AI assistant, or what it answered.

Every value is a number, a true or false, or a word from a fixed list. The app checks this twice before anything leaves the laptop. The server doesn't store IP addresses.

How to turn it off

Usage data is on by default. The first time the app opens, it shows a small notice saying so, with a Turn off button. After that, any one of these turns it off:

  • In the app, open Settings, Privacy and switch off Send usage data.
  • In settings.json in the config folder, set "privacy": { "usageData": false }.
  • Set the environment variable SWERVELY_TELEMETRY=0 (false, off and no work too). This is handy for a whole school computer lab.

Once it's off, no more usage data is sent, and anything still waiting to go out is deleted from the laptop right away. Every feature works the same whether it's on or off. To see the last 50 events exactly as they were sent, open Settings, Privacy, What was sent.

Checking for new versions

Separate from usage data, the app asks GitHub for the newest version number once a day, with nothing sent except what any web request carries (like your IP address), and you can turn that off in Settings, Privacy, Check for new versions.

How long we keep it

We delete the events after 13 months. Two things stay longer, so we can count active laptops over time: a short list of which days each install ID opened the app and on which version, and one row per install ID with its first and last day seen, version, system, language, country and totals.

Who sees it

Nomadic Dragons, FTC team #25528, the team that makes Swervely. We use it to decide what to fix and what to build next. We don't sell it, and we don't share it with anyone else.

The full list of events

This is every event the app can send. Each one is sent along with the install ID, app version, operating system and language described above, plus the time it happened.

app_open
The app opens, and whether this is its first run.
app_close
The main window closes, and how many seconds it was open.
page_view
A page opens: Live, Tuning, Tests, Paths, Recordings, Hub or Settings.
settings_section
A Settings section opens, by its fixed name.
connect
The robot link comes up, and how: USB, Wi-Fi, simulator or other.
disconnect
The robot link goes down, how it was connected and for how many seconds.
opmode_start
An OpMode starts: TeleOp or autonomous, and whether it is one of the helper OpModes. Never its name.
drive_start
Laptop driving switches on, with the keyboard or a gamepad.
drive_test
A drive test starts, by its fixed name, like diagonals or spin in place.
recording_start
A recording starts.
replay_start
A replay starts.
deploy
A deploy finishes: whether it worked and how many seconds it took.
check_run
A hardware or odometry check finishes, with its worst verdict: pass, warn or fail.
path_run
A path is sent to the path runner, and whether that worked.
tuning_change
Tuning values are saved to the robot. Only how many, never which or to what.
saved_to_code
Tuning values are saved to your robot code. Only how many, never which or to what.
setup_step
A setup step happens, once per laptop, by its fixed name: robot code folder picked, library added, a deploy worked after that, a real robot has the library, path runner added, simulator tour started or finished.
ask_ai
An Ask AI button is pressed: on the robot log, the build output or the robot error. Never the log or the question.
ai_chat_start
An AI chat starts, and with which assistant.
ai_prompt
An AI turn ends, and how many tools it ran.
ai_permission
An AI permission question is answered with allow or reject.
terminal_start
An AI terminal tab opens, and for which assistant.
mcp_install
The AI tools are installed into an app from the AI tools list.
mcp_remove
The AI tools are removed from an app.
theme
At launch and on change: the built in theme or a custom one.
units
At launch and on change: inches or centimetres.
keybinds_custom
At launch, how many keys were moved, if any.
workspace
A workspace is picked on the Live page: built in or custom.
config_import
The config folder is imported.
config_export
The config folder is exported.
error
Something failed: which part of the app and a short fixed code like connect_failed, or no_device when a connection can't find the robot. Never the error text.
crash
An unexpected error: whether it was in the window or the core, and an 8 digit code made from where in the app it happened, or from the error with its numbers taken out.

This website

This website counts page views with Vercel Web Analytics. It sees which page was opened, the site that linked to it, the country, and what kind of browser and device you're on. It doesn't set cookies or keep anything that identifies you, and it's separate from the app's usage data.

The download pages ask GitHub for the newest version, straight from your browser.

There's no cookie banner because there are no cookies to agree to.

Questions

Email swentze@proton.me and someone on the team will answer. If you send us your install ID (it's in Settings, Privacy), we'll delete everything tied to it.