Privacy policy

When your employer uses ActivityPulse, they are the data controller: they decide what is captured, why, and for how long. Kronosense Technologies L.L.C-FZ is the processor, acting on their documented instructions. Questions about why you are being monitored are for your employer; questions about how the software works are for us.

When you visit this website or contact us directly, Kronosense Technologies L.L.C-FZ is the controller for that limited processing.

Captured activity. The identity of the application and window in the foreground on a monitored device, the times and durations involved, whether the device was idle, and the project or task the time is attributed to. For browsers, the site-level identity of the active tab.

Device and account data. The device the agent runs on and its enrolment credentials, your email address and name, your role, and the organisation and teams you belong to.

Sign-in records. When you first signed in and when you last signed in. On your first sign-in only, we also record the approximate location Cloudflare resolves for the request — country, region and city — along with your browser and operating system family (for example “Chrome on Windows, desktop”), and how you reached us, meaning the referring website’s domain and any campaign tags on the link you followed. These are written once and never revised.

We do not store your IP address, and we do not store the full browser user-agent string. Cloudflare resolves the address to a place at the network edge; we receive the place and never the address. We keep only the referring site’s domain — never the page or search terms you came from. All of it is erased with your account.

Operational data. Standard request logs and error diagnostics needed to run and secure the service.

Website analytics. Our public marketing pages use Google Analytics to measure aggregate traffic — page views, approximate location, device and referrer. For visitors in the EEA, the UK and Switzerland, analytics and advertising storage default to denied under Google Consent Mode, so no analytics cookie is set unless consent is given. Analytics is not loaded in the signed-in application at all, so no captured activity — and no organisation, team, user or project identifier — is ever sent to Google. You can change or withdraw that choice at any time using Cookie settings in the footer.

Billing data. On a paid plan, the email address of the administrator who subscribes, together with the plan and seat count. Checkout, payment and invoicing are handled by Stripe, which is where any billing address and payment details are entered and held — we do not see or store card details. No captured activity is sent to Stripe.

Optional, off by default. Screenshots, and input-activity capture — counts of key and mouse events over an interval, never what you type. Both are off unless your organisation deliberately enables them, and the status of each is listed on your own data page in the console. Screenshots additionally require the Enterprise plan; input-activity capture is available to an organisation on any plan that chooses to switch it on.

To provide the service your employer has contracted us for: attributing working time to projects, producing timesheets and reports, and exporting data for billing or payroll. To keep the service secure and available. To meet our own legal obligations.

We do not sell personal data, and we do not use captured activity to train machine learning models.

Retention is set by your organisation within the bounds of its plan, from seven days on the Free plan up to twenty-four months or more on Enterprise. When a retention window passes, the underlying records are deleted rather than hidden. Account data is kept while the account exists.

The most detailed layer is shorter than that window, always. The record of each individual switch between applications — one row every time the focused window changes — is deleted after thirty days, or sooner if your organisation set a shorter period. Before it goes it is summarised into fifteen-minute totals, so the hours, projects and applications behind a timesheet stay available for as long as your organisation keeps data while the minute-by-minute trail does not. This is not a setting anyone can turn off.

Under the GDPR and comparable laws you can request access to your personal data, correction of it, erasure, restriction of processing, portability, and you can object to processing. Because your employer is the controller for captured activity, raise these with them — and the product gives you somewhere to do it. Signed in, the page My data shows what your organisation’s agents are set to record and lets you take your copy; administrators have the same controls under Settings → Data & privacy:

• Access. Download everything held about you, in one file, yourself, from My data — your account record, devices, memberships, timesheets, captured activity and your own audit trail. No administrator has to act for you, and the file lists what is not in it, and why.
• Correction. An administrator can amend your name and account details; timesheet corrections go through the adjustment record, which keeps both the original and the change.
• Restriction and objection. File a request with your grounds. It is recorded, your employer has one month to answer it, and they must give you reasons if they refuse. These two are decided by a person: nothing is granted or denied automatically.

Erasure. Ask your employer, and where they act on it ActivityPulse deletes the captured activity and the raw archive it was derived from — and then the account itself: your name, your email address, your devices, your team memberships and any invitation or sign-in code are destroyed, leaving a record that identifies nobody. Two things survive on purpose. The audit trail keeps the entry showing the erasure happened, because an erasure that erases its own evidence cannot be demonstrated to anyone. And your employer may keep your approved timesheets as evidence of hours paid, which Article 17(3) permits where they have a legal duty to hold them; that is their setting to make, it is shown to them at the point they erase you, and those hours are attached to the anonymised record rather than to you.

You can also contact us at contact@activitypulse.ai, and you have the right to complain to your local supervisory authority.

Only the sub-processors we publish, each for a stated purpose. The current list, what each one processes and where, is at /sub-processors. Each organisation's captured activity is stored in its own database rather than pooled with other customers'.

Kronosense Technologies L.L.C-FZ (Formation No. 2529704 · Licence No. 2529704.01), Meydan Grandstand, 6th Floor, Meydan Road, Nad Al Sheba, Dubai, U.A.E. Data protection enquiries: contact@activitypulse.ai. Security reports: /security.

If we change this policy materially we will update the effective date above and notify organisation administrators.