Walka uploads nothing

Privacy

Walka runs on your computer and uploads nothing. This website has no cookies and no analytics, and an account on it only if you make one - the rest is below, in plain words.

Last updated:

The short version

  • Walka uploads nothing. What it records stays on your computer. A walk gets into an account only when you add it on this website yourself.
  • An account is opt-in. Walka needs none, and neither do these pages. Without one, the site holds no data about you.
  • Private until you say otherwise. Nothing in your account is shown to anyone until you switch your page to public.
  • Yours to take and to delete. You can save everything as a file, and delete the account with everything in it, at any time.
  • No cookies, no analytics, no advertising, and no selling of data.
  • GitHub hosts the site and the downloads; Supabase keeps the accounts. A page that is not an account page asks no other company for anything.

The rest of this page says the same at length, in three parts: Walka, the program, this website, and your account, if you make one.

Part one

Walka, the program

Walka runs on your computer, in two pieces: the program you download and open, and the addon in the game. The program listens to your walking pad over Bluetooth, and to a heart-rate sensor if you add one. Nothing is uploaded - not to Walka's maker, not to anyone else.

Walka is experimental, and you use it at your own risk. It is not a safety device or a medical device. That is the subject of the disclaimer, not of this page.

What it keeps, and where

Walka's own folder: %APPDATA%\Walka on Windows, ~/Library/Application Support/Walka on a Mac

Your settings, among them the weight and height you entered (your age and sex too, if you entered them), and which treadmill and heart-rate sensor are yours.

Your walks: when and how long, distance, steps, calories, speed, and heart rate if you use a sensor. A walk is recorded whenever the belt moves, with a game or without. Closing Walka ends the recording.

Your characters' journey numbers, with each character's name but not its realm.

walka.log, if your Walka has a window of its own: what it connected to, and what went wrong. It can hold your treadmill's name and Bluetooth address, and it stays on your computer unless you send it to somebody.

And a few small working files.

The game's folder

In the Walka addon's folder: the addon, and CompanionData.lua, a file the program writes so that the numbers in the game agree - your measured walks (with average and highest heart rate), your weight and height, the treadmill's name.

And what the addon itself records: its settings and history, each character's journey and its road. The game saves those with your other addon settings.

Walka's window, or your browser

Your choices on the dashboard's Share page, and whether Getting started is hidden - kept by what shows the dashboard: Walka's own window, or your browser, in its own storage for the dashboard's address.

Where you ran probe

The probe report, a small text file. The window says where it was saved.

Of the game's files the program touches only Walka's own: the addon folder, and the addon's saved file, which it only reads.

These are ordinary files on your own computer. So another program that runs on your computer, or someone with access to it, can read them: Walka cannot defend against that.

A walk can be deleted on the dashboard's History page: its file is removed from Walka's folder and it is left out of the file the game loads. That cannot be undone. The addon's own note of that session, in the game's saved settings, is not removed by this.

Walka puts none of this anywhere else, so there is nobody to ask for a copy or a deletion: the files are yours.

The dashboard

The dashboard is a page that Walka itself serves on your computer, at 127.0.0.1:8787, and shows in a window of its own (version 0.7.0: in your browser). It is only reachable from the computer itself: it shows your walks, weight and height and has no password, so it is not offered to other devices on your network.

The page loads nothing from anywhere else. In its own words: "Runs on this computer. Nothing is uploaded."

Walka's own window is drawn with what your system already has for showing pages inside programs: Microsoft Edge WebView2 on Windows, WebKit on a Mac. Nothing is downloaded for it.

What it looks at on your screen

To count a walk for your character, Walka reads a thin strip of black and white squares that the addon draws in the top-left corner of the game window. The long version is under What Walka looks at, exactly.

  • Normally it looks at that corner only: a picture about 700 pixels wide and 12 high, some fifteen times a second.
  • From when Walka is started until it first finds the game window, it also looks at the top-left corner of each monitor and, every five seconds, takes one picture of the whole screen to search it for the strip. Walka.exe beacon, the command that checks whether the strip can be read, does the same once. Once Walka has found the game, it looks nowhere else.
  • What happens to a picture: it is searched for the strip, in the computer's memory, and then dropped. No picture is saved or sent anywhere, and of what is on it nothing is kept but the strip's ten bytes.
  • What the strip says: whether a walking session is running or paused, how fast your character is going and how, whether you are AFK, and the numbers of its journey. Not whether it is fighting, dead or resting.

On a Mac, macOS asks before a program may look at the screen, and it asks about Walka by name (about Terminal, if your Walka runs in a Terminal window). You can change it later under System Settings → Privacy & Security → Screen & System Audio Recording.

The Share picture

The dashboard's Share page turns your journey into a picture you can post. It is private by default:

  • The picture is drawn on your computer, from numbers that are already on it. Nothing is uploaded and nothing is posted for you.
  • Your character's name, and the small line with your weight and average pace, are off until you tick them.
  • The road is read from a file on your computer and goes no further than the page that draws it. On the picture it is a line on a simplified map and the names of the continents (or of another land your road is on) - no zones, no place names, no coordinates.
  • The downloaded file is named after the date, never after the character.
  • The realm never leaves the game: the program is only sent a number that tells your characters apart. It finds a character's road in the game's saved file by that number, and neither the realm nor the folder names are passed on or logged.

The probe report

Walka.exe probe (on a Mac: Walka probe) listens to your treadmill and saves a small text report, for a treadmill that is not listed, or not behaving. The saved report is made to be posted in public. It lists fitness machines only - not the headphones, watches and televisions that are also in Bluetooth range, yours or a neighbour's - with their addresses cut short, and without the treadmill's serial number.

The window the probe runs in shows everything: that is for your eyes. Post the file, not a screenshot of the window.

What leaves your computer

Only what you take out yourself: a Share picture you post, a walk you download as a TCX file and import somewhere by hand, a walk you add to an account on this website, a probe report or a walka.log you attach to an issue (the log can hold your treadmill's name and Bluetooth address). From then on it is with the place you gave it to, under that place's rules.

If you find a way to read what Walka stores from outside the computer, or to make Walka send anything anywhere, that is a security problem. Please report it in private.

Part two

This website

This site is plain files. It has no comments, no cookies, no analytics, no advertising, no trackers and no social-media widgets. Its account pages are the only ones with forms, and the only ones that talk to a database: they are the subject of part three.

Everything a page needs - fonts, scripts, pictures - is served by the site itself. Opening a page that is not an account page asks no other company for anything.

Who hosts it, and what a host sees

The files are kept in a public repository on GitHub, built by a GitHub Actions workflow and served by GitHub Pages.

Like any web host, GitHub receives your IP address and your browser's details when a page is fetched, and may keep logs. The site's maker cannot see those logs and gets no visitor statistics from GitHub. What GitHub does with them is in GitHub's privacy statement.

The site's name, walka.dev, is registered at Cloudflare, whose name servers tell the internet where the site is. No page of this site is fetched through Cloudflare: your browser gets every page from GitHub directly. (The database behind the account pages is another matter: part three says who carries what is sent to it.)

The one count the site's maker can see is Google's, and it came with the name. To whoever has proved that a name is theirs, Google shows how often that name's pages were shown, and how often clicked, in Google's own search results. The maker of this site has proved it (Google asks for that before its sign-in screen may say "Walka"). Those are Google's counts of what happens on Google's search page. This site sends Google nothing for them, and they say nothing about what anybody does here.

What is kept in your browser

The site sets no cookies. On every page, one thing about you is kept in your own browser: your choice of light or dark, if you use the switch. It is in the browser's local storage under the name walka-theme, and it is never sent anywhere.

To remove it, use the switch again to go back to what your system uses, or clear this site's data in your browser's settings.

The downloads page also keeps GitHub's answer about the latest version (see below) in that tab's session storage, and uses it for an hour so that it does not have to ask again. That is a version number, a date, the address of the release page, file sizes and the time of asking - nothing about you - and the browser drops it when the tab is closed.

The site also keeps, in that tab's session storage, how far down each page you were, so that going back puts a page where you left it. That is never sent anywhere, and the browser drops it when the tab is closed.

The account pages keep more there, and only for those who use them. A walker's public page keeps your choice of miles or kilometres, under the name walka-units, in the same way as light or dark. A browser that is signed in keeps the sign-in, and the food diary a copy of your diary: see what a signed-in browser keeps.

The downloads page

One page talks to GitHub beyond fetching the page. The downloads page asks GitHub's public API which Walka version is the latest, to show its number, its date and the sizes of the files. GitHub sees that request as it sees any other.

The download buttons themselves are links to files on GitHub. When you use one you are on GitHub, and GitHub's privacy statement applies there.

This site links to other sites, GitHub first of all. When you follow a link, the site you arrive at sees your visit as it sees any other, and its own privacy rules apply. This site asks your browser to tell that site no more than this site's address - not the page you were on.

Part three

Your account, if you make one

An account is for sharing your walking progress and for the food diary. Walka itself needs none, and neither do the other pages of this site. An account exists only if you make one. It holds what you put into it, and the record of your signing in.

Walka, the program, still uploads nothing. A walk gets into an account when you add it on this website yourself. Later the desktop program may be able to send your walks itself; that will be a switch you turn on, and until it exists Walka uploads nothing.

The accounts are run by the site's owner: the one maintainer who makes Walka and this website. There is no company behind them. Only what the two features need is kept, there is no advertising, and no data is sold. This part names every company that has a hand in it.

What is kept

An account holds nothing until you tick I am 18 or older on its first page. Until then only the sign-in itself is kept (see Signing in), and No thanks: delete this sign-in on that page removes that too.

Your profile

The name in your page's address and the name shown on it, if you chose them. Whether your page is public, and which of its switches are on. Whether you want miles or kilometres.

When you ticked I am 18 or older, and when you agreed to your body numbers and your food diary being kept, if you did.

Your numbers

Weight, height, year of birth and sex: what the food diary makes its estimates from. All of them are optional, and none is kept unless you have agreed.

Your walks

For each walk: when it started and ended, and the calendar day it counts for. The time the belt was moving, the distance, the steps, the calories, and how many of those calories were on top of sitting.

Whether a walking session was running in the game. How each number was come by - measured by the treadmill, or estimated, and for the calories whether the estimate was made from your speed or from your heart rate (the word, not the heart rate itself). And how the walk got here - from one of Walka's files, from a TCX file or typed in - with the name that file has for it, such as 20261119-213000.

Each walk also carries how far your clock was from world time (UTC) when it started, where the file or your browser says so. A program that sends walks may add a random number that tells one installation from another.

Left on your computer, because nothing here needs them: the second-by-second samples, the heart rate, the top speed, the treadmill's name and your character.

Your foods

A food you picked from a search or a scan, or made yourself, kept so that you can pick it again: its name, its brand, its calories in 100 grams, the size of a serving if the source names one, and where it came from - Open Food Facts (with the barcode), USDA FoodData Central (with its number there) or you.

Only what you picked is kept, and only in your own account. There is no shared list of foods.

Your food diary

One entry for each thing you ate: the day, the meal if you say which, the name and the brand, the grams if they are known, and the calories.

Your goal

One number: calories eaten minus calories burned, for a day. It goes no further than 500 either way.

Reports you send

If you report somebody's public page: the name of that page, which of three reasons you gave, your note if you wrote one, and when.

Each of these also carries when it was made and when it was last changed.

Not kept: no password, no location, no contacts, no pictures, no payment details, no advertising identifiers. Nothing that is not on this page.

Who sees it

You. Nobody else: not a visitor, and not another person who is signed in. The database itself holds to that, with a rule on every table that lets a signed-in person read, add and change their own rows and nobody else's. A visitor who is not signed in can read no table at all.

Two things leave your account, and only if you send them: what your public page shows, once you switch it on, and a report about somebody else's page, which the site's owner reads.

The site's owner runs the database, and as its administrator can read everything in it: the rules above do not bind an administrator. The owner does not look into anyone's account, except to fix a fault or to act on a report. A public page can be taken down without opening the account behind it.

Supabase, the company whose computers the database is on, can reach it as any host can. What it may do with it is under Where it is kept.

If you find a way to read or change an account that is not yours, that is a security problem. Please say so in private, to simplelogin-newsletter.outreach886@simplelogin.com, and not in a public issue.

Your public page

Your account is private. If you switch your page to public, anyone who knows or guesses its name can see the name you show, and in all: how many walks, how long and how far. Nothing else, unless you switch more on. The switches are on your account page, and each is off at first:

  • My page is public. Anyone who knows or guesses the name can see it. Switch it off and it is gone at once, and the switches below go off with it.
  • Show the last twelve weeks, day by day. A reader sees on which days you walked, for how long and how far, and since when you walk.
  • Show steps. If Walka estimates your steps, it does so from your height, so a reader can work out roughly how tall you are.
  • Show my single walks. Your last 20 walks, one by one: the day, the time walked and the distance. Never the time of day.

Calories, your numbers and your food are never on your page, whatever is switched on. Neither is your e-mail address.

Public means public. The address of your page has its name in it, and anyone who knows or guesses that name can open the page: it is not a secret link. The site asks search engines not to list these pages, and leaves them out of its sitemap. That is a request, and no more.

Switch your page off and it is gone at once. What somebody already saw, saved or took a picture of is not: nothing can take that back.

The name in a page's address is one of a kind. So somebody who tries to take a name learns whether it is taken, also when the page behind it is private.

A signed-in person can report a public page - one that pretends to be somebody, or has an offensive name. The site's owner can then take the page down. That hides the page and changes nothing in the account. The reason is noted with the account, and the owner can put the page back.

Body numbers and the food diary

Your weight, height, year of birth and sex, and what you eat, are information about your health. They are kept only if you agree, in these words on your account page:

Keep my body numbers and my food diary in my account. This is information about my health. No visitor and no other walker can see it. The site's owner, who runs the database, can: the privacy page says when. I can take this back on this page at any time, and then all of it is deleted at once.

Until you agree, the database refuses them. When you agree, it notes the moment. Your walks need no such agreement, and an account works without it: it has no food diary, and that is all.

To take it back, use Take back my agreement... under Your numbers on your account page. That deletes your body numbers, your foods, your food diary and your goal, at once. Your walks stay. It cannot be undone.

Where it is kept

In a database at Supabase, the company that runs the database and the sign-in for this site. The database is in Oregon, United States. The website itself is still plain files on GitHub, which holds no account data.

Supabase keeps the data for the site's owner and on the owner's instructions. Its own words are its privacy notice and its data processing addendum; the companies it uses in turn to run its service are in its list of sub-processors.

An account is kept until you delete it, or until accounts end in the way the terms describe. Nothing deletes one for not being used.

Signing in

Nobody signs in with a password here, and no password is kept. Signing in is done by a service of Supabase's, called the sign-in below.

With Discord, GitHub or Google. You go to that site, say yes there, and come back signed in. That site hands the sign-in your e-mail address, and with it your name and user name there, the number that site knows your account by, and the address of the picture you have there. This website uses the e-mail address. It neither uses nor shows the rest; the sign-in keeps it until you delete your account. The other site, for its part, learns that you signed in here, and when.

What the sign-in keeps:

  • your e-mail address, when the account was made, and when you last signed in;
  • for each browser you are signed in on, a session: when it began, when it was last renewed, the IP address it came from and what the browser calls itself;
  • a log of what it did for you - a code sent, a sign-in, a session renewed - with your e-mail address and the time of each.

Of all that, this website reads your e-mail address, which it shows you on your account page, and the two dates, which go into the file you can save.

What a signed-in browser keeps. The sign-in is kept in the browser's local storage, under names that begin with walka-account: the keys that say this browser is signed in, what the sign-in keeps about you (your e-mail address and the dates above, and what another site handed over: name, user name, account number and picture address), and a one-time secret for each sign-in that was begun here.

It is not a cookie. The keys go to Supabase with each request and to nobody else (on the way they pass through the network Supabase uses: see below), and all of it stays until you sign out.

The food diary also keeps a copy of your diary in that browser, so that it opens and works without a connection. Signing out removes that as well. That copy holds what the diary shows: your entries, your foods, your body numbers, your goal, and the time and calories of your recent walks. Taking back your agreement, and deleting your account, remove it too. So that the diary opens without a connection, the browser also keeps the diary's own files - scripts, styles and icons, nothing about you - until the site's data is cleared in the browser's settings.

Other services your browser talks to

A page that is not an account page asks no other company for anything: part two holds for it as before. The account pages - your account, your walks, the food diary, and a walker's public page - talk to these, each only when there is a reason:

Supabase

Every account page asks the database, and so does a walker's public page. With each request Supabase receives your IP address and your browser's details, as any host does, and it keeps a log of requests for a time.

The site's owner can read that log in Supabase's dashboard for as long as Supabase keeps it, and does so only to find a fault.

Those requests do not go to Supabase directly. They reach it through the network of Cloudflare, a company Supabase uses for that and names in its list of sub-processors. So Cloudflare carries every request to the database and the sign-in, your IP address with it. On the way to another site's sign-in and back, your browser is at Supabase's own address for a moment; Cloudflare may set a short-lived cookie of its own there, which it uses to tell browsers from programs. It is kept under Supabase's address, not this site's: no page of this site can read it, and none uses it.

Open Food Facts world.openfoodfacts.org

When you search for a food or scan a barcode in the food diary, your browser asks Open Food Facts, an open database of food products. It receives the words you searched for or the barcode, and your IP address and your browser's details. Nothing about your account goes with them.

What it does with a request is in its privacy policy.

USDA FoodData Central

Where the food search shows foods from the U.S. Department of Agriculture's list, your browser does not ask USDA itself: a small function at Supabase passes your search words on. USDA receives those words, and not your IP address.

Discord if you sign in with it

For that step you are on its own site, and its privacy rules apply there. It learns that you signed in to this website, and when.

GitHub if you sign in with it

For that step you are on its own site, and its privacy rules apply there. It learns that you signed in to this website, and when.

Google if you sign in with it

For that step you are on its own site, and its privacy rules apply there. It learns that you signed in to this website, and when.

GitHub as the host

Serves these pages as it serves the rest of the site: see part two.

Once a day a small job on GitHub asks the database one question, so that the database is not put to sleep for lack of use. It carries nothing about anyone.

No advertising network, no analytics and no tracker is among them, on these pages as on the others.

Taking it out, and deleting it

Taking it out. Save everything as a file on your account page. Your own browser reads your rows and saves them as one file, named walka-account and the date, in a format other programs can read (JSON). Nothing is made ready on a server, and nothing is mailed.

In the file: what the sign-in keeps that the site can read - your e-mail address, when the account was made, when you last signed in and which ways you signed in - and everything listed under What is kept: your profile, your numbers, your walks, your foods, your diary, your goal and the reports you sent.

Deleting one walk, food or diary entry. It is emptied at once, and what is left is a marker: of a walk, when it started and ended, its day, how far the clock was from world time, and how it got here; of a diary entry, its day; of a food, where it came from and its number there. The marker is kept so that another device of yours hears of the deletion and does not bring the entry back. Markers are in the file you can save, and they go when the account goes.

Deleting the account. Delete my account... on your account page. At once, and for good, this deletes everything in your account - your page, your numbers, your walks here, your food diary, the markers - and the sign-in record with it: your e-mail address, your sessions and whatever the sign-in noted about you in the database. It cannot be undone, and there is nobody who could bring it back. The walks on your own computer, in Walka, are not touched.

What stays, and for how long:

  • The name of your public page, if you had one, is kept free for 90 days - the name and a date, with nothing else - so that a link you once passed on does not lead to a stranger at once. The same holds for a name you change.
  • A report somebody else sent about your page stays in that person's account. It names the page, not you.
  • What Supabase itself keeps for a time - its log of requests, and any copies it makes of the database for safekeeping - is not the site's to delete. It runs out by itself.

For adults only

Walka is for adults, and so is an account. It holds nothing until you tick I am 18 or older. The database notes when, and that is not taken back. A year of birth is optional, and one that could make you 17 is not taken.

Nobody's age is checked beyond that: the site has no means to, and asks for no papers. An account that turns out to be a child's is deleted when the site's owner learns of it: write to simplelogin-newsletter.outreach886@simplelogin.com.

Estimates, not advice

Every calorie figure in an account is an estimate, for interest only: what a walk burned, what a body burns at rest, what a food holds, what is left to walk off. None of it is medical advice - for food as for walks. Do not use it to decide anything about your health, your diet, your medication or your training.

The food numbers come from two public lists and from what you type in. A list can be wrong about a food, and the food diary is not a diet plan: it says nothing about what anyone should eat.

Children

Walka is for adults only. Its disclaimer says so, and the dashboard's body profile does not take an age under 18.

This website is not directed at children. An account on it is for adults only, and without an account the site itself collects nothing from anyone.

Your rights, and who to ask

Depending on where you live, the law may give you rights over data that is held about you: to see it, to have it corrected, to have it deleted, to take it with you, to take back an agreement you gave.

Without an account, the site's owner holds no data about you to show, correct or delete. Walka's files are on your own computer, and the pages of this website collect nothing.

With an account, you do most of it yourself, on your account page, at any time and without asking anybody:

  • See it, and take it with you: Save everything as a file.
  • Correct it: change it where you entered it.
  • Delete it: a single entry, or the whole account (Delete my account...).
  • Take back your agreement to your body numbers and your food diary being kept (Take back my agreement...).

How each of them works, and what is left afterwards, is under Taking it out, and deleting it.

Where the law gives you these rights, it also lets you complain to the data-protection authority of the place where you live. You do not have to write to the site first.

Who to ask:

Walka is a hobby project with one maintainer, who is also the owner of this site and answers for its accounts. There is no company behind it. An issue or a report is written with a GitHub account and kept by GitHub.

Walka sends nothing about you to its maker. What reaches the maker is what you put on GitHub yourself, what you write to the address above, and what you put into an account.

Changes to this page

This page describes Walka and this website as they are on the date below. Every change to it is in the website's public history on GitHub. Before anything about accounts changes - what is kept, who sees it, a company that is added - this page is changed first, and its date with it.

Last updated: .