Privacy
Kalkas has no released hosted service, so there is no customer dataset on this side to describe. What follows is this site itself: what it keeps in your browser, what a server sees while it serves a page, and what changes when a released service exists. It is written to be read against the pages it describes.
ScopeThis page describes the site, not a service
There is no account to create, no hosted decision surface, and no customer data behind these pages, because the hosted service is not released. The only thing this site can store is a theme choice, and — where sign-in is configured — the session described below.
Not here
These are absences rather than settings: there is nothing on this site that collects, measures, or passes on what you read.
In your browser
The first is the theme you choose; the second is an operator session, and it exists only when this deployment is configured for sign-in.
The theme choice
The theme control remembers whether you chose system, dark, or light, under one local-storage entry, so a reload does not flash. Set it back to system, or clear this site’s data, and the entry is gone.
With no stored choice, the pages follow your operating system’s setting and store nothing at all.
The operator session
Signing in hands off to the Sylphx Identity Account Portal. What comes back is the session Identity issued, sealed into a host-only, HttpOnly, Secure cookie that lasts at most eight hours. This site keeps no user record, no password, and no refresh token, and it mints no credential of its own.
A deployment with no identity configuration never sets the cookie, and the operator surfaces that need a session stay closed rather than pretending.
The cookie is sealed so its contents cannot be read or altered by the browser. It is sent only to this site, and it is the whole of what this site holds about a signed-in operator.
On the server
Serving a page requires a web server to see the request. That much is unavoidable, and it is worth stating precisely rather than in a phrase about logs.
A request carries the network address it came from, the path that was asked for, the time, and the browser’s own user agent string. A platform hosting an instance of this site may keep those ordinary request records. This page does not state a retention period or a location for them, because the platform that would hold them is not operated from here and no period could be evidenced.
What this site adds to a request is nothing: no copy of what you typed, no page-view record, no identifier placed in the request, and no third-party logging. When a page fails, what is recorded is a digest of the failure, not the content of your request.
Stated plainlyNo policy is invented here
We do not publish a retention period, a sub-processor list, or a data location for a platform we do not operate. Publishing a number we cannot evidence would be worse than saying what is true: the platform may hold ordinary request records, and that is the limit of what this page can claim.
Customer data
Nothing is being held for customers on this side of the product, and no hosted surface exists that could hold it.
Accounts, where they exist, belong to Sylphx Identity. This site holds no user record to read back, correct, or export.
When you run the product locally, it writes the history file you name, on your machine. Nothing about a local run reaches this site.
There is no corpus, no receipt store, and no payment detail held behind these pages, because there is no released service to hold them.
Ending a session
Signing out is the whole deletion step, because there is nothing on the server to delete.
The account page holds the sign-out control. Signing out expires the session cookie in your browser; no server-side session table is left behind, because none was ever written. To remove the theme choice, set the theme control back to system or clear this site’s data.
If you want to ask what a session carries, or ask for it to be ended for you, write to [email protected]. The sign-in page says when this deployment can sign anyone in at all.
AccountsIdentity owns the account
Where an account exists it is held by Sylphx Identity, which owns the credentials and can act on the account itself. This site can end the session it holds and nothing more, which is why the answer to a deletion request here is short.
What changes
This section is an intention, not a description of anything that exists today. It is written down now so the change is visible when it comes.
What is collected, why it is collected, where it is processed, and who to write to — published before anything is hosted for customers, not after.
How long each kind of record is kept, stated as a period rather than as a principle, and revisited when the record changes.
Ways to ask for a copy, a correction, or a deletion, with a route that does not depend on a support desk existing.
The statement you are reading will be replaced rather than amended in place, so the difference between today and a released service stays visible.
The site collects nothing beyond what serving a page requires, and says so on every page it serves. The trust surface lists the controls; the contact page says how to reach a person about any of it.