Privacy Policy
Klado is a self-hosted web application. It runs on infrastructure chosen by the organisation that operates it, and that organisation is the controller of the data described below. This page describes what the application itself does with data; the operator's own identity and contact details appear at the end.
What Klado Is
Klado is a working space with six areas: a Data Center for the files you upload and the datasets built from them, an Inbox for activity addressed to you, a Workspace for reports and documents, a Knowledge base for reference material, a Calendar, and Settings. You sign in with an account; what you upload, write, and publish is yours to manage and, unless you share it explicitly, visible only to you.
Information Processed
- Account records — the email address you sign in with, an optional display name, an optional role, and a password hash. Klado stores only a salted password hash, never the password itself.
- Files you upload — their contents, filename, size, and the object key under which they are stored.
- Datasets derived from those files — the parsed rows, and any derived columns computed by the cleaning rules you or your agent apply.
- Content you create or an agent creates for you — reports, knowledge pages, calendar events, and the notes colleagues leave on documents.
- Inbox messages — the sender, the target document, and the event that produced the message.
- Operational records — an access log of requests, and, when you send or receive a message, the SMTP conversation metadata needed to deliver it.
Isolation and Access Control
- Data Center datasets are stamped with the account that created them and are filtered by that account on every read and write. Another signed-in account cannot list, read, or delete them, and an administrator sees them only in an explicit administrative view.
- The built-in query tool can only reference datasets visible to the signed-in account. Queries naming anything else are refused before they run.
- Documents you publish can be shared with named colleagues, or with anyone holding a share link. Sharing is always an explicit action, never a default.
- Request paths that load a document on its own resolve the caller's identity, so an unrecognised caller receives a 404 rather than a page.
Automated Agents
Klado can issue an access code so that a script or an automated assistant can act on your behalf. Such a code carries your own permissions: it reads what you can read, and it does not receive the account password. Codes can be revoked at any time from Settings, which takes effect on the next request, and a revoked code can then be deleted outright. Every request made with a code is attributed to you.
Storage
Structured records live in the PostgreSQL database the operator configures. Uploaded files and generated images live in an object store the operator configures — Alibaba Cloud OSS or any S3-compatible service. Neither location is determined by Klado; both are set by the deployment.
Sharing
The application shares data with third parties only where the operator has configured it, and only for the purpose it was configured for:
- Email delivery — verification codes, access codes, and report notifications are sent through the SMTP server the operator configures. The message content is what the page you triggered says it is.
- Share links — a link you choose to distribute lets its holder read that document without signing in. Treat it as public.
Klado itself contains no advertising, no analytics, and no third-party tracking.
Retention and Deletion
- You can delete the datasets and files you uploaded, and the content you created, from within the application.
- An administrator can remove an account. Removing an account removes what the application holds for it.
- Records needed to keep the application consistent — the access log, for example — may be retained for a period the operator chooses.
Security
- Sessions use an HTTP-only cookie; the session secret is held in the deployment configuration and never in the source tree.
- Passwords are stored as salted hashes and compared in constant time.
- Content rendered from other users' text is inserted as text, not as markup.
- The application serves its own assets; user-supplied file names are never used to build a path.
Your Responsibilities
Do not enter personal, confidential, or third-party information that you are not entitled to place here. You are responsible for the access codes issued on your account, and for sharing documents only with recipients who may read them.
Contact
For access, privacy, or security questions, contact the operator of this Klado deployment — listed in your deployment's configuration and reachable through the in-app administrator. If this page is being read on a deployment whose operator details are missing, treat the deployment as unverified and do not upload sensitive material to it.