Logmy.Work Privacy Policy

Overview

Logmy.Work is a workforce time, attendance, and productivity product operated by Vlemon LLP ("Vlemon", "we", "us"), available via browser at logmy.work, a Windows desktop app, and (planned) Android and iOS apps. This policy describes what Logmy.Work collects, why, and how it's protected. It supplements our main Privacy Policy and should be read alongside our Location Tracking Policy and GDPR page. Legal terms governing your use of Logmy.Work are at Logmy.Work Terms & Conditions.

Logmy.Work is a transparent workplace tool, not surveillance software. It records that work happened, on which task, for how long, and — only where your organization enables it — where a clock-in occurred. See What we don't collect below.

Who controls your data

Your employer or workspace administrator (your "organization") is the data controller for the work records described below — they decide what Logmy.Work features are enabled and who can see what within their workspace. Vlemon acts as the platform operator / processor: we host, secure, and process that data to provide the service, and we don't use it for purposes your organization hasn't authorized. Accounts and sign-in are handled by Vlemon Origin (origin.vlemon.com) — name, email, password or one-time code, and a session token. Logmy.Work itself never issues its own login tokens.

What we collect

Account and workspace

Full name, email, profile photo (if uploaded), your role in the workspace (admin or member), workspace/tenant membership and plan, authentication sessions (login time, session id, sign-out/revoke events), and device identifiers used to recognize a trusted client (platform — web, Windows, Android, iOS — device id, device/hostname, last-seen heartbeat, app version).

Time, attendance, and timesheets

Clock-in/clock-out, pause, resume, stop, and task-switch times; the active task, project, and sprint; session and pause durations; your organization's configured workday window; periodic in-session checkpoints (e.g. "still working on this task?"); daily attendance and holidays; timesheet submissions and approvals; leave requests; and — where your organization uses it — payroll allocation of time to projects and overtime signals derived from recorded hours.

Location (GPS / geofencing)

Only if your organization enables location policy and you grant your device's location permission: GPS coordinates at clock-in, clock-out, and site arrival/departure, and whether you're inside or outside an employer-defined job-site boundary. Full detail — including exactly what's collected, Android/iOS permission behavior, and how to control it — is in our dedicated Location Tracking Policy. Location is collected for work-site verification only; it is never sold or used for advertising.

Desktop activity (Windows app)

While a time session is running on the Windows desktop app, we may record: how long since your last keyboard/mouse input (used to pause a session or prompt you to assign idle time to a task), and the foreground application's process name and window title, sampled locally to decide when to show a timesheet checkpoint after a large context switch. This is not a keystroke log and does not record what you typed. If your organization has activity/productivity trend reporting enabled, it reflects aggregate time-per-application-category for coaching purposes, not individual screenshots or continuous surveillance.

Android and iOS (planned apps)

In addition to the account, time-tracking, and location data above, native mobile apps may use: precise or approximate GPS (see Location above); background location only if your organization has enabled geofenced arrival/departure tracking and you've granted that permission; push/local notifications (e.g. idle-while-timer-running reminders, checkpoint prompts); device id, OS version, and app version for compatibility and support; foreground/background app state (to pause or remind you during a running timer); the photo/file picker when you choose to attach a receipt or file (not camera access we initiate); and network access limited to Logmy.Work's own API — no third-party advertising SDKs.

Work content your organization stores

Projects, tasks, comments, status, assignees, due dates, and board/Gantt data; files and attachments you or your team upload; project expenses and receipts you submit; calendar events and, if your organization opts in, a public calendar by handle; and, if your organization connects Jira or a similar tool, the site URL, integration credentials, imported issues, and worklogs synced from Logmy.Work time sessions. Your organization may also record directory fields such as employee code, department, job title, and employment status.

Technical, security, and support logs

IP address, browser/app user-agent, request timestamps, and rate-limiting/abuse-prevention signals; audit records of who created, updated, or deleted a task, file, or similar record and when; and crash/diagnostic data limited to keeping the app working. If you contact us through a marketing or support form, we keep your name, email, and message. None of this is used for employee monitoring — it's platform operations and security.

What we don't collect

• Keystrokes, or passwords you type in other applications — no keylogging
• Clipboard contents, except what you actively paste into Logmy.Work
• Microphone or webcam access, or continuous camera capture
• Your personal contacts, SMS, call history, or photos other than ones you choose to attach
• Other applications' private data or your general browsing history
• Location after you clock out, after you deny the permission, or when your organization hasn't enabled geofencing
• Children's data — Logmy.Work is a workforce tool used by adults through their employer, not a consumer app directed at children

Who can see your data

You can see your own time, attendance, leave, and (if enabled) your own activity trends. Your organization's admins and managers can see team time, attendance, timesheet approvals, overtime, on-site vs. remote status (only if geofencing is on), payroll allocation, and project cost — scoped to their own workspace. Vlemon staff access data only to operate, secure, and support the platform, or as required by law. Your data stays within your organization's Logmy.Work workspace database and is never used to train public AI models.

Retention

We retain workspace data for the life of your organization's Logmy.Work contract plus a reasonable backup and legal-retention period. Ask your organization about its own HR record-retention rules, since some records may be ones your employer is legally required to keep. Deleting your Vlemon Origin account is handled per our main Account & data deletion policy, subject to any records your employer must legally retain.

International data transfers

Where data is processed on infrastructure outside your country — for example, in India — we rely on appropriate safeguards to keep it protected, consistent with our GDPR page.

Cookies

Logmy.Work uses cookies/tokens for session authentication only — no third-party advertising cookies.

No sale of data

We do not sell your personal data, and Logmy.Work carries no advertising.

Your rights

For work records your organization controls, start with your workspace administrator — they're best placed to action access, correction, or deletion requests within your organization's records. Vlemon supports those requests as the processor. For anything you deal with directly with Vlemon (such as your Origin account or a marketing inquiry), contact privacy@vlemon.com. See our GDPR page for the full list of rights available to EEA/UK individuals.

Changes to this policy

We'll update the effective date above when this policy changes and, for material changes, notify workspace administrators.

Contact

Questions about this policy can be sent to privacy@vlemon.com or legal@vlemon.com.