Changelog

The privacy notice now says what is kept when you answer the dashboard's training verdict. So far that verdict has been that it does not have enough to suggest anything, and such a day is recorded the same way. The record lists the verdict word for word, and the readings and sources it rested on. It lists your answer (one of three), how it felt (one of three), and the times. It also keeps your sport programme and the make of your watch. One person holding the server can read it. This is the first retention rule for what is kept about an account holder: kept until you ask by mail, removed by hand. Version 2.5.0 of the notice carries this, live since 2026-09-14. Measured on 2026-09-17, no answer has been recorded yet. With an account, you see the dashboard card that takes the answer.

On the night of 2026-09-14 the evening message said the connection needed reconnecting when it could not read the watch. That was a cause it had not measured. Since 2026-09-15 it says only what happened, by kind of failure, and names no cause it has not checked. A night older than last night is now named by its date instead of "last night". This is the same kind of correction as the entry from 2026-08-22 below: a verdict that was not measured is no longer given.

The entry from 2026-09-03 below says there are three cookies. Measured again on 2026-09-08, there are two. The third was not sent by any address checked, so its description is gone from the privacy notice. That entry stays as it was written, and this one replaces it.

The count was not the only wrong part. The privacy page and the home page set no cookie at all. The one-year cookie comes from addresses under /auth/ that do not exist, so a mistyped address is enough to leave you with it. The sign-in page did not set it in that check. Version 2.4.0 of the notice says all of this, in section 2.

The entry from 2026-08-23 below says the server sets PHPSESSID before you type anything at all. Measured again on 2026-09-08, that holds on the sign-in page and not on the home page or the privacy page. That entry stays as it was written, and this one replaces it.

Section 5 of the privacy notice said the benchmark is run. It is a draft protocol. No system has been run against it, and no result exists. Version 2.4.0 corrects that sentence.

The entry from 2026-09-03 below says the notice lists a transfer to the United States. It did not say what that transfer rests on. Section 7 now does. Postmark is run by AC PM, LLC. Its data processing addendum names the EU-U.S. Data Privacy Framework first, and standard contractual clauses as the alternative where the law requires them.

A first version of that paragraph, written on 2026-09-03, was wrong. It named a parent company neither source names, and it put the two the wrong way round. It was corrected on 2026-09-05, and neither version was on this site until today. Section 8, the change record, keeps the wrong step. Section 7 names what is still unchecked. Neither statement has been put against the official Data Privacy Framework registry, and ActiveCampaign's own page on that framework does not name Postmark.

The entry from 2026-08-31 below says the front page has a Sign in link in the top bar. It does not. The top bar holds a status chip, Benchmark, Build status and Changelog. That entry also says the link is what makes the rest of it reachable. It stays as it was written, and this one replaces it.

The same entry says the form to create an account is one click past that link. Further down it says there are two ways to ask, and names the form as one of them. Sign-ups were switched off on 2026-08-30. The page at /auth/registration still opens, so it looks open, but sending the form fails. Writing to info@vyren.life is the only way to ask now.

The privacy notice now says what is kept for someone who holds an account. Until now it said that part was not written. Section 7 lists 45 tables across three databases, 50 kinds of wearable measurement, health data, a stored phone number, stored mail bodies, and a transfer to the United States. Version 2.3.0 of the notice carries it.

A second copy of account passwords sat outside the sign-in system. On 2026-09-03 it was emptied out of the account table, and the page that wrote it is off this site. Section 7 says what that settles and what it does not.

Version 2.3.0 corrects three more things. Two pages the notice named no longer exist, and both are now described in the past. Section 4 stopped promising a separate opt-in process that does not exist. Section 2 said two cookies reach a reader, and there are three.

The paragraph at the top of this page said there was nothing to sign up for yet. It also said the dashboard entries ran on one person's data. Neither held after 2026-08-30, the day an account was created here, approved by hand and signed in. That paragraph has been replaced. The entry from 2026-08-23 below says registration is not open. It stays as it was written, and this one replaces it.

The front page now has a Sign in link in the top bar, and the form to create an account is one click past it. That link is what makes the rest of this entry reachable.

You can now ask for an account here. It gives you nothing on its own. Each one waits until one person approves it by hand. Nothing is sent when that happens, so if you have asked, come back and try to sign in. There are two ways to ask, and both end in the same place. Use the form, or write to info@vyren.life, which the entry from 2026-08-24 names.

Settings only worked for one account. Anyone else who signed in and opened it found a page that would not load. It now opens for whoever is signed in, on that account's own settings.

There was more than one sign-in page. There is one now. The older addresses no longer answer on their own; they send you to it.

Signing in now starts pulling what your device recorded. It used to wait for the next scheduled run. Measured once, on 2026-08-31: sixteen seconds from signing in to the data being in. The page opens before that finishes, so the new numbers show on the next load. No account has been created since these changes went in. Nothing has yet gone from the form to a working sign-in in the shape it stands in today.

The address to write to is now info@vyren.life. The entry below, from 2026-08-23, names the address that was live that day. It stays as it was written, and this one replaces it.

The privacy notice now names the two companies that carry your mail. One is a forwarding service called ImprovMX. The other is Google, whose Gmail mailbox it lands in. Google was always in the path. ImprovMX is new today. Version 2.2.0 of the notice says both, in section 3.

Two lines said that nothing here was running yet: a label in the top bar, and a line under the example decision. A sign-in page answers anyone who visits it, so both lines were false. They now say the narrower thing that is true. No recommendation has been made yet.

The privacy notice said this site sets no cookies. The server sets one, called PHPSESSID, before you type anything at all. Version 2.0.0 names it, and names the server log kept for seven days. The old text was written from the plan, not from the running site.

The not-found page said the site has three pages and that nothing is hidden. Both halves were wrong. Other addresses answer as well. That page now lists the pages written for the public, and says registration is not open.

An entry from 2026-08-18 counted the addresses that answer the public. It counted too few. Some of the ones it missed belong to the app, not to this page. The number stays exactly as it was measured that day, with a note above it saying what it missed.

There is now an address to write to: vyren.life@gmail.com. One person reads it, and answers can take days. Registration is still not open. The first testers are family, and when it opens each account is still approved one at a time.

The evening message used to tell you to eat more when the day's logged calories or protein fell under a fixed number. Neither number carried a cited source. In one case the message gave that instruction to one person. That person's own logged data did not support it. It now reports the day against your own goal: how much you logged, how much is left. It makes no recommendation.

The morning and evening messages both used to call a full rest day. That verdict came from four fixed numbers: two for sleep, two for stress. No published source could be found for any of them. They now compare last night with the median of your own recorded nights, and say what those numbers do not tell you.

The dashboard now charts steps, sleep and resting heart rate from your wearable data, each over the last 90 days. Thirty-one measures are collected and stored; three are shown, and the screen says which. Currently synced from a Garmin watch. A day that is still running is marked as unfinished, so a partial day does not read as a drop. Sending fewer measures to the browser also means less of your health data leaves the server at all.

Dates now carry the time as well, so you can see how fresh a number is. Your one-rep max reads the same everywhere on the dashboard.

The public page is open. It says what VYREN does, and what it deliberately does not.