Privacy

What Tempro records, and what it never does.

A time tracker that works by itself has to watch everything you do at the computer. So the rules are strict and simple: as little as needed, encrypted, and only on your machine.

Recorded

Active window
The program and its title, through Windows events. Titles are what projects are made from.
Browser tabs
With the extension: the address without its query string, and whether a video plays. Private windows are ignored.
Claude Code sessions
Which folder an agent works in, so its time lands on the right project.
Audio and microphone
Only on or off: enough to tell a video or a call from time away.
Lock and sleep
When the computer is locked or asleep, so those hours never count.

Counted, never kept

Keys
How many per minute. Never which ones, never what you typed.
Clicks and scrolls
How many per minute, to tell work from watching.

Never

Screenshots
None. Screen text recognition exists for programs whose title never changes; it is off by default, and even then keeps only the text.
Query strings
Stripped from every address before it is stored.
The cloud
There is no account and no server of ours. The app listens on 127.0.0.1 only.

Where it lives

Database
SQLCipher, AES-256. The key is kept in Windows Credential Manager and tied to your Windows account.
Password
Optional, for the log or the whole window. It locks again when the window hides or Windows locks.
Recovery key
Save it from Settings, Data in your password manager: it opens the database after a Windows reinstall and clears a forgotten password.
Retention
After 30 days (you choose) titles and addresses are wiped. Hours per project stay.
AI
Off by default. When on, it sends window titles and minutes to Claude, or keeps them on your computer with a local Ollama model.

Questions people ask

Do I need the AI?

No. Recording, sorting by rules, every report and the CSV export work without it. The AI names sessions, suggests projects for unsorted time and writes summaries.

Can I export my data?

Yes. CSV for Excel with sessions, hours by day and project, and rates, from the week, month, 3 month, year and project screens.

macOS or Linux?

Not at the moment: the sensors use Windows APIs directly. The engine and the interface are platform independent, so a port is possible.