Privacy policy
Last updated November 17, 2026
Worklog ("we") runs worklog.pro.et, a work log that collects what you worked on from you, your AI assistants and the tools you connect. This policy explains what we collect, why, who processes it and how to delete it. The short version: we keep a record of your work so you can use it, we don't sell it, and you can delete it at any time.
What we collect
- Account: your name, email address, a hashed password, timezone and the role you picked at sign-up.
- Your work log: entries you or your connected tools create: titles, summaries, categories, durations, projects, tags, status and ticket keys.
- AI assistants (MCP and the Claude Code plugin): whatever your assistant sends to Worklog's tools when you ask it to log or look up work. If you turn on automatic session capture, once per session: the project folder name, the first line of your first request (up to 300 characters), the start of the final answer (up to 2,000 characters), start and end time and number of turns. We do not receive code, file contents, branch names, commit hashes or repository URLs from the hook.
- Browser extension (optional): the names of websites you use (for example figma.com) and when. Never page titles, full addresses, page content, keystrokes, screenshots or private windows.
- Connected tools (optional): calendar feed links, Telegram chat id and username, and personal tokens for Jira, Tempo, Linear or Notion. Tokens are encrypted at rest (AES-256-GCM). From these tools we read only your own activity (for example meetings, issues you moved or created) and write only what you send (for example Tempo worklogs, Notion rows).
- API keys: stored only as one-way hashes.
- Usage analytics: anonymous page-view statistics through Vercel Web Analytics (no cookies, no cross-site tracking).
What we remove automatically
Before anything is stored, Worklog removes links, code blocks, file paths, passwords, API keys and other credentials, email addresses, phone numbers, IP addresses and card numbers from titles and summaries. Meeting attendee lists and locations from calendars are not stored.
How we use it
- To show you your log, calendar, focus score, reports, timesheets and recaps, and to let your AI assistant answer questions about your work.
- To send what you ask us to send: Telegram check-ins and recaps, budget alerts, Tempo worklogs, Notion rows.
- To keep the service secure and working. We do not sell your data, use it for advertising, or use it to train AI models.
Who processes it
- Vercel (hosting and anonymous analytics) and Prisma Postgres (database), as our infrastructure providers.
- Anthropic, only if AI categorization is enabled on the server: site names (never anything else) are sent to categorize websites the built-in list doesn't know.
- Telegram, Jira, Tempo, Linear, Notion, your calendar provider: only when you connect them, and only to do what you set up.
- Your AI assistant's provider (for example Anthropic for Claude) receives tool results when your assistant uses Worklog, under that provider's own terms.
Retention and deletion
We keep your data until you delete it. You can delete any entry, delete tracked browser activity, revoke API keys, disconnect any tool, or delete your whole account under Settings → Delete account, which permanently removes your account, log, activity, keys and connections. Backups held by our database provider expire on their normal schedule.
Security
Data travels over HTTPS. Passwords are hashed with bcrypt; sessions and API keys are stored as hashes; connector tokens are encrypted. Access to production data is limited to operating the service.
Children
Worklog is meant for people at work and is not directed at children under 16.
Contact
Questions or requests about your data: worklog.pro.et/support. We'll update this page when our practices change and show the date at the top.