A printed yearly security note
This is a future plan. A printed yearly security note is not available in the mailbox today. Nothing on this page is that note. The note, if it exists later, would describe changes that had already happened. It would not name a future date.
What it is
Once a year, Turkeuro would publish a note that says what changed in the security of the mailbox, in language a person can read, and that note could be printed. It would look backward. A control that was added, a control that is still not on, a limit that still stands: those are the kinds of sentences the note would be for. It would not be a launch announcement, and it would not pick a day for work that has not happened.
It is for a person who wants to read what changed without learning a new dialect, and for a business admin who wants to print the same note and keep the paper. Printable means a normal page a person can print, with the sentences in the page, not a picture of a certificate. A seal with no sentences would be the opposite of the plan.
The security page is the living description of what is on and what is not. The yearly note would be a point-in-time reading of changes, published when Turkeuro actually publishes it. This roadmap is not the note. A roadmap lists plans. The note would list changes that already happened. Using one as the other would confuse a plan with a fact.
How the logic would work
Turkeuro would write the note after the year it describes, about that year's changes, and publish it where a person can open it without a special request. The sentences would be checkable against the product. If a paragraph said the password exists, the password would exist. If a paragraph said a VPN is not on, a VPN would not be on. A note that drifted into advertising would fail its own test.
The note would say what is not on, not only what sounds strong. SMS sends nothing, unless that fact has changed and the note is describing the change that already happened. Second-factor choices are saved and are not asked again at sign-in, unless a change that already happened is what the note is reporting. The note would not smooth those limits out. A yearly note that hides a limit is worse than no note.
Print would be the reader's print. The page would be readable on paper: real text, the company named, the subject named. It would not require a special viewer. It would not be a PDF of one mailbox letter. Saving a message as PDF is a different plan. This note is Turkeuro writing about the service, not a person exporting a letter.
The note would not name a date that has not happened, and it would not name a release. If a change has not happened, it is not in the note. Plans stay on the roadmap, in the language of plans. The note stays in the past tense of work that shipped. This page, today, is still a plan, so there is no note to print.
What you would see
A person would see a single note, written in ordinary sentences, saying what changed in the security of the mailbox. They would see that it can be printed. They would see the limits as clearly as the additions. An admin would see the same note, not a private edition with extra claims.
They would not see a schedule of future work. They would not see a customer count. They would not see a seal that stands in for the sentences. They would not see a reward, a score, or a comparison with another company invented for the occasion.
Today they see the security page, which is the current description, and they see this roadmap, which is the list of plans. They do not see the yearly note. There is nothing to print under that title.
What it would not do
It would not announce future work. It would not name a date that has not happened. It would not claim a private network path, video calls, office tools, an assistant, or payments exist, unless those things had in fact been added and the note was describing the addition after the fact. They have not been added. A note published now would have to say they are not on. This page is not publishing that note.
It would not claim the mailbox is sealed so that only the account holder can read stored mail. The connection uses TLS. The note would not upgrade that fact into a larger promise. It would not claim a secret codebase. The mailbox is Postfix, Dovecot, and SnappyMail, and a yearly note would keep naming the programs it actually runs.
It would not replace the security page, the audit log, or responsible disclosure. Those are different pages and different plans. It is not published today.
What is available today instead
Read the security page for what is on now: the password, the 41-character Turkeuro account code that starts with turkeuro, a two-factor choice, an authenticator, email as a verification choice, TLS, and Login settings. The second-factor choices are saved and are not asked again at sign-in. Unlock does not lock the screen. SMS sends nothing.
The Windows desktop app is the desktop client for that mailbox. Business plans are at the business page. None of those is a printed yearly security note. The note remains a plan.
What you can use today is a mailbox on Postfix, Dovecot, and SnappyMail. You sign in with a password. The account can hold a 41-character Turkeuro account code that starts with turkeuro, a two-factor choice, an authenticator, and email as a verification choice. Those second-factor choices are saved with the account. They are not asked again at sign-in. The connection uses TLS. Login settings hold the sign-in controls for the mailbox you have open. There is a Windows desktop app. Business plans are listed at https://turkeuro.com/business.
SMS sends nothing. A mobile number saved on the account does not produce a text message from Turkeuro. The unlock choice in Login settings does not lock the screen. Those are limits of the mailbox as it is. They are not a quiet version of the plan on this page.
