Privacy Policy
Last updated 10 November 2026
Logsheet (“we”) provides time tracking, approvals and billing software at logsheet.io. This policy explains what we collect, why, and the choices you have. If anything is unclear, use the request form on our home page.
What we collect
- Account details: your name, work email, role, time zone and sign-in security data (hashed password, authenticator secret stored encrypted).
- Work data you enter: clients, projects, tasks, time entries, notes, approvals, invoices and the audit trail of changes.
- Technical data: IP address, browser type and sign-in times, used for security and abuse prevention.
- Calendar data, only if you connect a calendar (described below).
Connecting Google and Microsoft calendars
Connecting a calendar is optional and needs your explicit consent on Google's or Microsoft's own sign-in screen. Your organisation's administrator must also have switched the feature on.
When you connect an account we receive:
- your account's email address, name and a stable account identifier, to show which account is linked;
- the list of your calendars (names and colours), so you can choose which ones to use;
- for the calendars you turn on, each event's title, start and end time, whether it is all-day, your response (accepted, declined and so on), whether it shows you as busy or free, the number of attendees, and the recurring series it belongs to.
We do not store event descriptions, attachments, meeting links or the email addresses of attendees. Events marked private or confidential at the source are stored with the title “Busy”.
We keep a rolling window of roughly the past 35 days and the next 60 days. Older events are deleted automatically.
How calendar data is used
- to show you your meetings next to your timesheet so you can turn them into time entries;
- to suggest a project based on how you logged the same meeting before;
- if your organisation and you choose to turn on writing: to create, update or remove calendar events that Logsheet itself created, such as time blocks or timesheet reminders. We never change or delete events we did not create.
Who can see it. Your calendar data is visible only to you. Your manager, your organisation's administrators and Logsheet staff do not have a screen or report that shows your calendar events. Managers and administrators see only the time entries you choose to save, as with any timesheet.
Limited Use. Logsheet's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the user-facing features described above. We do not transfer it to others except as needed to provide those features, to comply with law, or as part of a merger or sale with notice to you; we do not use it for advertising, for building or training generalised AI/ML models, or to determine creditworthiness; and no human reads it unless you ask us to for support, it is necessary for security or abuse investigation, or the law requires it.
How we protect it
- Calendar access and refresh tokens are encrypted at rest (AES-256-GCM) and used only on our servers.
- All traffic uses HTTPS. Passwords are hashed, and authenticator-app (TOTP) two-step sign-in is supported.
- Time changes are recorded in an append-only audit trail.
Sharing
We do not sell personal data and do not show advertising. We use a small number of service providers to run Logsheet, such as hosting and email delivery, who process data only on our instructions. We may disclose information if the law requires it.
Cookies
The signed-in app uses an essential session cookie to keep you logged in. On our public pages we also ask whether you accept one optional cookie, ls_attr, which remembers for 30 days which ad or page brought you to Logsheet (for example the campaign name). If you accept, we attach that to the account you create, so we can tell which campaigns work. If you choose “Essential only” we do not set it. We store your choice in a cookie and in your browser's local storage for 6 months. Our public pages load Google Tag Manager so we can measure visits and ad campaigns with Google Analytics. Loading it means Google receives your IP address and the page you request. Until you choose “Accept all”, it is told not to store anything on your device and to treat analytics and advertising storage as denied. If you accept, Google may set its own cookies (such as _ga) and record page activity for measurement. If you choose “Essential only”, those cookies are not set, and any set earlier are removed. You can change your choice at any time with the “Cookie choices” link in the footer. We do not load these tags in the signed-in app.
Your choices
- Disconnect any time under Calendars in Logsheet. This immediately deletes that account's tokens, calendar list and every cached event. Time entries you already created are kept because they are part of your timesheet.
- You can also revoke access from your Google account (Security → Third-party access) or Microsoft account (My Apps). Logsheet will then ask you to reconnect.
- Choose per calendar whether it is used at all; only your primary calendar is on by default.
- You can ask us to access, correct, export or delete your personal data by contacting us. Your organisation's administrator controls the organisation's work data, such as timesheets and invoices, and we act on their instructions for it.
Retention
Work data is kept while your organisation's account is active and for as long as the organisation needs it for records, then deleted or returned on request. Calendar data is kept as described above and removed when you disconnect. Security logs are kept for a limited period.
Children
Logsheet is a workplace product and is not directed at children.
Changes
If we change this policy in a meaningful way we will update the date above and, for changes that affect calendar data, tell connected users in the product.
Contact
For privacy questions or requests, use the request form on our home page.