Skip to content

Draft — requires legal review before launch

This document is not in force. Bracketed items are placeholders, and the launch-review checklist at the end lists what must be done first.

Privacy policy

What VidarFit on vidar.fit stores, why, who else can receive it, how long it is kept, and your choices. Draft pending legal review.

Version 0.23 (draft) · Updated November 20, 2026

This draft describes how VidarFit’s website, vidar.fit, handles data during early access. It has not been reviewed by a lawyer and is not in force. The checklist at the end lists what must happen before launch.

Who is responsible

VidarFit is operated by VIDARFIT LLC, contact hello@vidar.fit.

The short version

  • VidarFit stores what it needs to run your account and your training, and nothing for advertising.
  • VidarFit is free during early access. It takes no payment and holds no payment details.
  • No ads. Your data is never sold or shared for advertising.
  • No third-party analytics, tracking pixels or data brokers.
  • Google sign-in is used only if you choose it, and an AI language model for the assistant only if it is switched on. This policy names what each receives.
  • Exporting your data and deleting your account will never require payment.

What VidarFit stores and why

What
Account
Examples
Email address, a name if your sign-in provider supplies one, and whether your email is verified
Why
To identify your account and contact you about it
How long
While your account exists
What
Terms accepted
Examples
Which version of the terms you accepted when you signed up, and when
Why
To show what you agreed to
How long
While your account exists
What
Bug reports you send
Examples
Your account, message and submission time. Only if you opt in: the screen path and workout reference, movement and set previewed in the report form. No automatic logs, screenshots or training history
Why
Staff investigate the problem in your existing support conversation; a report requests a person rather than an automated reply
How long
While your account exists; removed with account deletion. An unsent draft stays in memory on the current screen only and is cleared when you leave that screen or close the browser
What
Password
Examples
A one-way scrypt hash, never the password itself. An account moved from the earlier VidarFit keeps its earlier bcrypt hash until its first sign-in
Why
To check your password at sign-in
How long
While your account exists; accounts created with Google have none
What
Sign-in sessions
Examples
A session token in a cookie, the IP address and browser details at sign-in, and when it started and was last used
Why
To keep you signed in and list your devices so you can sign them out
How long
Until you sign out, or 30 days without use
What
Security counters
Examples
Short-lived counts of sign-in attempts by network and page; per-account counters stored as keyed hashes, not as addresses
Why
To stop password guessing without locking you out
How long
Minutes to hours
What
Reset links
Examples
A single-use token
Why
To let you choose a new password
How long
60 minutes or first use
What
Profile
Examples
Your 18+ confirmation, training goal, experience, schedule, session length, units, and the joints, muscles and movements you avoid; optionally birth year, height and bodyweight, the figure you pick for your recovery map, and your running preferences, including your maximum and resting heart rate if you enter them
Why
To plan your training, and to draw your recovery map on the figure you pick
How long
While your account exists; optional details can be cleared
What
Training records
Examples
Equipment, check-ins (including pain answers), workouts, sets, notes, corrections, recovery estimates and overrides, runs
Why
This is the product
How long
While your account exists
What
Optional nutrition, body and supplements
Examples
Food log, weigh-ins, body measurements and body-fat percentage, targets, the sex you choose for an energy estimate (which also picks your recovery map’s figure, unless you pick one yourself), meal plans, grocery lists, kitchen stock, supplement records (the dose as you typed it), your allergies, diet and foods you exclude, and your confirmation for meal planning that you are not pregnant or breastfeeding and don’t need a professionally managed diet for a medical condition or an eating disorder
Why
Only if you use them
How long
While your account exists
What
Progress photos
Examples
The pictures you add, saved again as new images without location or camera details, at most 1,024 pixels on the longest side, with the date, view and note you give
Why
Only if you use them
How long
A picture until you delete it; its date, view and note while your account exists
What
Coaching, groups and kitchens you share
Examples
Invitations, relationships and the permissions you granted, messages and check-in answers, group rooms and their chat, a name you chose for a room, and which exercises got a new personal record if you share records with a room
Why
To run the sharing you chose
How long
While your account exists; group chat, room names and other room events 30 days after the room ends
What
Assistant conversations
Examples
What you typed or said (as text) and the answers
Why
To keep the conversation going
How long
30 days, then deleted
What
Questions help could not answer
Examples
When Ask, voice or a connected agent finds no published help article for a question: the question with emails, links, handles and every digit removed (other words you typed, such as a name, stay), where it came from, when, and a link to your account
Why
So a person can write the missing article. Operations staff read these questions. Their review screen groups them and does not show who asked, but the stored record keeps the link to your account, and the database lets an operations admin read that link
How long
A year after it was noted if nobody reviews it; 180 days after it is reviewed; sooner if you delete your account. Not part of your data export
What
Connected agents
Examples
Each connection’s permissions and expiry, and a record of each call (which tool, when, allowed or not)
Why
So you can see and revoke what an agent does
How long
Calls 90 days; connections while your account exists
What
Imports and exports
Examples
Import previews, the records an import created, and export files
Why
To show a preview, remove an import, and let you download
How long
Previews 7 days; import details 30 days after import; export files 7 days
What
Plan
Examples
Your plan, which during early access is early access with everything included, and any plan included with your account. Never payment details
Why
To show your plan page
How long
While your account exists
What
Change records
Examples
Operation identifiers and version numbers; an audit trail that names which fields changed, not their values
Why
Safe retries, no duplicates, accountability
How long
While your account exists
What
Undo copies
Examples
The previous values of something you changed
Why
So you can undo
How long
24 hours, or until used
What
Pending approvals
Examples
A change proposed by the assistant or a connected agent, waiting for you
Why
So nothing changes without your approval, apart from what you let a connected agent save without review (below)
How long
30 minutes, or until you decide
What
Server logs
Examples
The service’s own lines hold operation identifiers and outcome codes; emails, passwords, tokens, entered values and request bodies are removed before anything is written. Cloudflare, which runs the service, also keeps its own record of each request in its logs. That record can hold the address asked for, the request’s headers, your IP address and your country, so it can hold sign-in, reset and confirmation tokens. A confirmation token holds your email address
Why
To diagnose failures
How long
Up to 7 days in Cloudflare’s logs

Most records also carry the time zone they were made in.

Check-ins, pain answers, the joints and muscles you avoid, bodyweight, measurements, heart rate, food logs, allergies, diet, supplement records and progress photos can be health information under some laws. VidarFit treats them as sensitive: they are never used for advertising and never shared except as described here.

Your recovery map’s figure. The recovery map is drawn on Vidar or on Astrid, and you can pick one in You, then Profile and goals. Until you do, it shows Astrid if you chose Female in your newest energy estimate, and Vidar if you chose Male or Skip or have no estimate. If your newest estimate was saved before the map offered two figures, the map shows Vidar. The figure changes only the picture, never your training or your targets. Coaches, groups, shared kitchens, connected agents and the assistant never receive it.

On your device

To let you train without a signal, VidarFit keeps some data in your browser’s storage (IndexedDB), in a separate database for each account that signs in on the device:

  • Changes not yet sent to your account, such as logged sets, until your account confirms it has them. Sent changes are kept for up to 24 hours as receipts, then removed.
  • Copies of records VidarFit is working with, such as your active workout.
  • Drafts you have not finished, such as a form you are part-way through.
  • Cached copies of account data VidarFit has fetched, so screens can open without a signal.

The browser also keeps a list of which accounts have data on the device (account identifiers only), and VidarFit’s offline cache holds its own files and the workout player’s screens, which contain no personal data.

Unsent changes belong to the account that made them and are never sent from a different account.

Signing out. If everything has reached your account, signing out deletes that account’s data from the device. If some changes have not been sent yet, signing out tells you how many, and that account’s data stays on the device so nothing you logged is lost. Those changes are sent the next time the same account signs in on this device. Anyone else using the device’s browser profile could find that data in the browser’s storage, so on a shared device, sign in again to send your changes, or clear the device.

Clearing the device. Clear this device, in You, then Data and privacy, deletes every VidarFit account’s data from the browser, including changes not yet sent, after showing how many would be lost. Clearing the browser’s site data for VidarFit does the same without the warning.

VidarFit uses only the cookies the service needs: your sign-in session, your time zone, so dates show in your own time, and short-lived ones while you sign in with Google or open an invitation. There are no advertising or analytics cookies.

Other services

These are used only as described, and only the information listed is shared.

Service
Google sign-in
When
Only if you choose Continue with Google
What it receives
Your sign-in request
What VidarFit receives or keeps
Your name, email, profile picture link and Google account identifier, plus the sign-in tokens Google returns. Nothing is posted to your Google account.
Service
Email delivery
When
Password resets, email confirmation and account notices
What it receives
Your email address and the message
What VidarFit receives or keeps
Resend sends these emails for VidarFit. VidarFit keeps only a log line of the outcome, and Resend keeps its own list of addresses that bounced or complained. In development, emails never leave the machine.
Service
Password check
When
When you choose a new password
What it receives
The first five characters of a one-way hash of the password, never the password or your email address
What VidarFit receives or keeps
Whether it’s on Have I Been Pwned’s public list of leaked passwords, from its Pwned Passwords service
Service
Assistant language model
When
Off unless switched on
What it receives
If switched on: an assistant message the built-in rules could not answer, to pick which of your records to read. Its conversational mode also receives your recent messages and Ask’s recent replies, the text of what it read for that answer (your own training, equipment, recovery estimates and strength trends) and help sections. It never receives ids, emails, names, check-in answers, food, bodyweight, supplements or another account’s data, and it never writes or approves anything
What VidarFit receives or keeps
The pick or the answer. The model runs on Cloudflare Workers AI, on the network that hosts VidarFit. [Workers AI’s data retention and training terms, to be confirmed and stated here before it is switched on.]
Service
Voice input
When
Only if you tap the microphone and agree
What it receives
Your browser’s own speech recognition does the listening; some browsers send the audio to their maker to turn it into text
What VidarFit receives or keeps
The text only. VidarFit never receives or keeps audio.
Service
Connected agents
When
Only agents you connect, for 7, 30 or 90 days
What it receives
Only what the permissions you granted allow
What VidarFit receives or keeps
A record of each call. Every change an agent proposes waits for your approval, unless you turn on Save without review for that agent: then the food entries or runs it sends (only those, and only the kinds you chose) are saved at once, marked in its activity, and can be undone for 24 hours. It is off unless you turn it on. Revoke any time.

VidarFit does not use your data to train AI models.

Other people you choose to share with

  • Coaches see only what you grant, one category at a time: nutrition only as daily totals, never your food diary, and for progress photos only the date of your latest one and how many, never a picture or its note. Revoking ends access immediately; your history stays yours.
  • Group workouts share the session structure, which exercise you are on and how many sets you have done, and chat if the host allows it. You appear as “Host”, or as “Member 1”, “Member 2” and so on in the order people joined, unless you choose a name for that room; never by your account name or email. If you turn on Share my personal records for a room, the room also sees which exercises got a new record when you finish, never the weight, reps or effort. Nothing else of your training history is shared, and never your loads, health details or body measurements.
  • Shared kitchens share stock and portions only, never your food log, goals or measurements. Members appear as “Owner” and “Member 1”, “Member 2”, never by account.

Your choices

  • Get a copy of your data as a JSON archive and CSV files, from You, then Data and privacy.
  • Correct anything you entered.
  • Delete your account and its data, from You, then Data and privacy, or, if you cannot sign in, by email to hello@vidar.fit from your account’s address. Deletion runs 7 days after you ask, and Keep my account stops it until then. What stays afterward: a record that a deletion happened, with no account id, email or content (a keyed fingerprint, outcome codes and counts). The cloud database’s own daily backups, and any copy of the whole database made before a database change, age out within 7 days of the deletion.
  • Sign out any device, and revoke coaches and connected agents.

None of these will ever require payment. Your rights under the law where you live may go further; the final policy will list them.

Where data is stored and how it is protected

The service runs on Cloudflare Workers and is reached over HTTPS only. Files you add (photos, imports, exports) are stored in Cloudflare R2, which encrypts them at rest. The database is a managed PostgreSQL database at Supabase in the United States, with row-level security, so each account’s rows are only reachable by that account, as a second layer behind the application’s own checks. It is backed up daily, and each backup is kept for 7 days. Before a database change, VidarFit also makes a copy of the whole database, kept for at most 7 days: an encrypted copy on GitHub, or a copy on VidarFit’s own computer.

Age

VidarFit is for adults 18 and over. An account found to belong to someone under 18 will be closed and its data deleted.

Changes to this policy

Before a material change takes effect, VidarFit will tell you on the website and by email.

Launch-review checklist

  • Not done yet: Working privacy contact verified for VIDARFIT LLC.
  • Not done yet: Legal review for the United States, including state privacy laws such as CCPA/CPRA and consumer health data laws such as Washington’s My Health My Data Act, and consent for health-related data, progress photos included.
  • Not done yet: Hosting provider, region, subprocessors and data processing agreements listed.
  • Not done yet: Email provider chosen and named; production email delivery configured.
  • Not done yet: Whether Resend’s list of addresses that bounced or complained belongs under what stays after a deletion.
  • Not done yet: Server log (7 days) and backup (daily, kept 7 days) retention confirmed in the Cloudflare and Supabase dashboards.
  • Not done yet: The copy of the whole database made before each database change, kept at most 7 days on GitHub or on VidarFit’s own computer: whether counsel is content with that.
  • Not done yet: What one Cloudflare log entry holds, read on a test deployment for a sign-in, a reset link and a confirmation link, and the server log row matched to it. Also whether loading a recovery map picture (/media/astrid/...) makes an entry at all, and if it does, what it holds.
  • Not done yet: Data export and account deletion re-tested on the production service, and the job sweep that runs due deletions confirmed running there.
  • Not done yet: Assistant language model: stays off, or Workers AI’s data retention and training terms are stated here before it is switched on.
  • Not done yet: Cookie position confirmed (essential cookies only, no consent banner), with the cookies listed above checked against the running site.
  • Not done yet: The “On your device” section re-checked against the offline client.
  • Not done yet: Voice: the browsers supported at launch listed with where their speech recognition sends audio.
  • Not done yet: Connected agents (MCP): what agents receive checked against the running service.
  • Not done yet: Questions help could not answer: confirm the retention (a year if never reviewed, 180 days after review), who among operations staff may read them, and whether they belong in the data export and in answers to access requests.
  • Not done yet: How long an account with no sign-in is kept, decided and stated here.
  • Not done yet: Before vidar.fit sells a plan: once it does, it shows the shared policy with its Buying on vidar.fit part instead of this page, so both are reviewed for the website first.
  • Not done yet: The recovery map’s figure: counsel’s view on letting the sex chosen for an energy estimate pick the figure, including whether that new use needs consent or notice. Also, if the log reading above finds recovery map pictures in Cloudflare’s request records, whether the server log row covers their addresses; and whether “On your device” covers the pictures VidarFit’s offline cache keeps after sign-out. Both can show which figure an account sees.
  • Not done yet: A way to tell people on the website about a material change to this policy, in place before the first one.
  • Not done yet: Every statement in this policy re-checked against the running product.