The components
How they connect
The client talks only to the backend and to the update hosts. It never talks to the dashboard, and the dashboard never connects to a client. There is no agent-to-agent traffic and no peer discovery.Separation between customers
Each organisation’s data lives in a backend application. Larger customers are given a dedicated application with its own credentials, separate from the application that serves other customers. Those are different backends, not different rows in one database. We will tell you which arrangement applies to you. Within an application, one organisation’s data is separated by an organisation reference on each record, and the dashboard scopes every query by the signed-in user’s role and organisation. An enterprise admin sees their own organisation; a supervisor sees their assigned groups.What each part stores
The client keeps activity that has not been uploaded yet, and its own configuration. When the machine is offline, sessions accumulate there and are sent when the connection returns. It holds no credentials that a person types, because nobody types any. The backend holds the accounts, groups, organisation settings, corporate list, and the activity rows themselves. This is the system of record. The fields are listed in full on Data collected and not collected. The dashboard stores almost nothing. It reads and writes the backend for everything a page shows. Its own local database holds only what it needs to run: session state, and a record of dashboard sign-ins, which is what the access log on the profile page shows. Activity data is not copied into it.The consequence worth knowing for an assessment: activity data exists in exactly two places, the machine that produced it until it is uploaded, and the backend application. It is not duplicated into the web tier.
Authentication
There is no dashboard single sign-on against a customer identity provider today. Passwords are set by an administrator and can be forced to change on next sign-in. Dashboard single sign-on through a customer’s own identity provider is on the roadmap and is not built.
Transport security
Every connection listed above is HTTPS. The client makes no plain HTTP requests, and the installers and version files are served over HTTPS too. Installers are additionally code signed and timestamped, so their integrity can be verified independently of how they were fetched. See Code signing and tamper resistance.Formal security reviews
If you are running a security assessment, procurement review or works council process, contact us at support@reclaimtime.com and we will respond in writing for your organisation. That covers hosting providers and data residency, encryption, backups, subprocessors, testing, access controls, and retention. Those answers depend on which backend your organisation is on and on your contract, so they are given per customer rather than published. Ask early rather than late. A questionnaire answered in week one is a formality; the same questionnaire answered the week before a renewal decision is not.Checked against ReclaimTime client 8.0.0.9 and dashboard V3 on 5 September 2026.