Privacy and data use

TeamLogger Privacy Policy

This policy explains what TeamLogger processes, why it is used, who can access it, and the choices available to account holders and workers.

Effective and last updated: September 13, 2026

1. Scope and roles

This policy applies to TeamLogger websites and services operated by Build80, including the TeamLogger web application, desktop timer, supported browser extensions, TeamLogger Mobile for Android and iOS, the TeamLogger Kiosk Android app, reporting services, support channels, and feature-request form.

A company or employer that creates a TeamLogger company account ordinarily decides why its workforce data is collected, which TeamLogger settings are enabled, which workers are invited, and which authorized users may view reports or screenshots. TeamLogger processes that data to provide the service. The exact legal roles of TeamLogger and the customer organization depend on the applicable law and the customer agreement.

This policy does not replace the customer organization's own employee notice, workplace policy, consent process, collective agreement, or legal obligations. Organizations using TeamLogger are responsible for lawful notice, authorization, access, retention, and use in each location where they operate.

2. Information we process

Account and contact information

• Name, username, email address, company membership, role, team or group assignment, and account status.
• Authentication and security information needed to sign in, protect the account, manage sessions, and prevent misuse.
• Support messages and contact information supplied when requesting assistance.

Work and organization information

• Projects, tasks, work-session start and stop times, work notes, manual time entries, approval decisions, approval remarks, and attendance-related records.
• Leave requests, leave balances and policy context, approval history, and files a user explicitly selects as leave attachments. Employer-configured leave types, notes, or upload slots can request health or sensitive leave information, such as a medical certificate.
• Company configuration, reporting permissions, manager relationships, workday boundaries, and time-zone settings.
• Device and synchronization metadata needed to associate, upload, secure, reconcile, and troubleshoot work records.

Screenshots and monitoring information

• Desktop or mobile screenshots captured during tracked work when the company has enabled that feature and the platform permits capture.
• Camera or webcam captures created by supported desktop features, and Sentinel captures where that company feature is enabled.
• Screenshot time, associated work session, project or task, capture type, upload status, and related activity values produced by the applicable tracker.
• The current mobile trackers can send protocol-compatibility activity-time tuples derived from elapsed tracked-time and capture intervals. These synthetic values are not observations of keyboard, pointer, touch, active-window, foreground-app, or idle behavior on the mobile device.
• Desktop application, website, active-window, keyboard, pointer, idle, or other desktop monitoring signals only when a supported desktop feature is configured to collect them. The current Android and iOS apps do not collect these signals from the mobile device.

Feedback and technical information

• Feature-request text submitted from the app, associated with the authenticated account and company so TeamLogger can evaluate and respond to the request.
• IP address, request timing, device or operating-system information, sync state, error information, and security events needed to operate, protect, and troubleshoot the service.
• Website analytics, cookies, browser information, requested pages, advertising-measurement events, and approximate country or language information used to understand and improve the public website. The TeamLogger public landing pages load Google Analytics and Google Ads measurement tags; Google can receive online identifiers, IP-derived information, browser/device details, referring pages, and interaction events under the applicable Google terms and settings. See Google's Privacy Policy. These website tags are separate from employee activity monitoring and are not embedded as analytics or advertising SDKs in the current TeamLogger mobile apps.

Information TeamLogger Mobile does not collect

The current TeamLogger Mobile apps for Android and iOS do not request or collect: data from Apple HealthKit or fitness/device sensors; precise or approximate device location; contacts; calendars; call logs; SMS; installed-app inventory; keyboard, touch, pointer, or idle-time signals; foreground-app or browser-tab names; or webcam images. They do not use the microphone to record audio, browse the photo library, or use the camera. This paragraph describes TeamLogger Mobile; the separate TeamLogger Kiosk camera and facial-attendance behavior is described below. A user may explicitly choose a supported file as a leave attachment through the platform file picker; depending on server and leave-policy support, that file can be a document, image, video, existing audio file, or another format and can contain health or sensitive information requested by an employer-configured leave process.

3. TeamLogger Kiosk facial attendance

TeamLogger Kiosk turns a dedicated Android phone or tablet into a shared workplace attendance device. A customer organization decides whether to enable facial attendance, which existing TeamLogger users are assigned to each kiosk, which authorized users may enroll them, the available non-biometric attendance process, and the workforce access and retention rules it applies.

Camera and face data

The Kiosk camera processes live frames on the Android device to detect a face, create or compare a mathematical face template, assess capture quality, and perform configured liveness checks. TeamLogger Kiosk does not send or retain those frames as photos or video. A mathematical face template is biometric information that can be used to identify an enrolled worker even though it is not a photograph. TeamLogger does not use Kiosk face templates for advertising, emotion analysis, or training a general-purpose face model.

Enrollment and attendance

Enrollment takes place through an activated Kiosk app. Before capture begins, a named authorized operator selects an existing assigned TeamLogger user and reviews the current employee notice. The app sends mathematical face templates, employee and operator account identifiers, the notice acknowledgement, model and policy identifiers, camera and capture-quality information, liveness results, and security and audit evidence to TeamLogger over HTTPS. Enrollment does not itself record attendance. An authorized employer or administrator can invalidate an enrollment from the TeamLogger web dashboard. TeamLogger erases the stored profile template during invalidation, and assigned kiosks erase their obsolete local copy after receiving a valid updated authorization.

For attendance, the kiosk sends the identified employee's name and account ID, Check in or Check out action and time, kiosk and installation identifiers, face-profile and model or policy identifiers, camera configuration, capture-quality and liveness results, offline and time-trust state, app version, and signed security evidence. Camera frames are not included in enrollment or attendance records.

Offline storage, retention, and choices

If internet service is temporarily unavailable, unresolved attendance records remain in encrypted app-private storage and upload when service returns. Accepted local synchronization receipts remain on the kiosk for 365 days. This local receipt period does not delete or set the retention period for server attendance, enrollment, security, or audit records; those records follow the general retention and verified-deletion terms in section 8.

The app protects local data with an encrypted database backed by Android Keystore, excludes app data from Android backup and device transfer, restricts network calls to TeamLogger's HTTPS kiosk API, and signs device requests and attendance records.

Facial attendance may be unsuitable or unavailable for some workers or situations. Customer organizations must provide lawful notice and any required choice or consent and make an appropriate non-biometric attendance process available. A worker can ask the organization controlling the workplace account, or contact TeamLogger, for access, correction, enrollment invalidation, deletion, or other privacy assistance. TeamLogger may need to verify identity and authority and may coordinate the request with that customer organization.

4. Mobile screen capture

If a company enables mobile screenshot tracking, TeamLogger presents a prominent explanation immediately before the platform screen-sharing flow. The explanation states what can be captured, why it is needed, that images are uploaded and stored, and that authorized company users may view them. The user can continue or decline.

Android

• Android capture uses the operating system's MediaProjection consent screen.
• On Android 13 and newer, TeamLogger requires notification permission before capture. App-wide notifications and the existing TeamLogger Screen sharing notification channel must remain enabled.
• While sharing is active, TeamLogger runs a visible foreground-service notification with a TeamLogger-specific icon and a Stop sharing action.
• If required notification visibility is denied or later disabled, capture stops or is blocked. If capture is mandatory for the company, the active work timer is reconciled instead of silently continuing without capture.

iOS

• iOS capture uses Apple's ReplayKit broadcast picker and the TeamLogger Broadcast extension.
• The user must start the broadcast through the system interface, and iOS displays its screen-capture indicator while broadcasting.
• ReplayKit frames are processed only while a valid TeamLogger work-session upload configuration is active. Transient App Group configuration and frame files are protected, excluded from backup, and cleared when the broadcast pauses or finishes, capture stops, or configuration is cleaned up.

Screenshot files awaiting a successful upload can remain temporarily in app-private storage so an interrupted upload can retry. They are removed after successful server acknowledgement, logout or authentication invalidation, or explicit queue cleanup. TeamLogger does not silently start mobile screen capture and does not request photo-library or storage permission to save or share viewed employee screenshots.

5. Authorized monitoring and screenshot viewing

Employers, administrators, and managers may be able to view recent monitoring cards and historical screenshots when their company role and TeamLogger permission settings allow it. The mobile Screenshots workspace is hidden when the signed-in account lacks the required permission. Server-held history may include screenshots and activity information uploaded by desktop or mobile trackers, including camera or Sentinel material if those existing company features are enabled.

TeamLogger limits the mobile viewer to the signed-in account's report and screenshot scope. Signed screenshot links are handled as sensitive, short-lived resources: the app does not attach TeamLogger authentication headers to external image hosts, does not save or share images, masks the viewer when the app is not active, and clears route-held image state when permissions, account context, or local capture status changes.

6. Why we use information

• Provide time tracking, synchronization, project and task assignment, facial enrollment and attendance, approvals, leave workflows, reports, screenshots, and permitted monitoring features.
• Authenticate users, apply company permissions, maintain account security, prevent fraud or misuse, and investigate incidents.
• Store and deliver records requested by the company account owner and make them available to authorized users.
• Provide support, respond to feature requests, communicate service information, and improve reliability and usability.
• Meet contractual, legal, accounting, dispute-resolution, and regulatory obligations.

7. Who can receive information

• Authorized company users. The company account owner and users granted applicable employer, administrator, manager, biometric-enrollment, approval, report, or screenshot permissions may access the relevant company data needed for those functions.
• Service providers. Hosting, storage, email, security, support, website analytics and advertising measurement, and other vendors may process information only for authorized services to TeamLogger. TeamLogger requires those providers, through applicable contracts and data-protection terms, to provide the same or equivalent protection described in this policy and to process information consistently with TeamLogger's instructions and applicable law.
• Legal and safety disclosures. Information may be disclosed when reasonably necessary to comply with law, legal process, enforce agreements, protect rights and safety, or investigate abuse.
• Business transactions. Information may be transferred as part of a merger, acquisition, financing, reorganization, or sale of assets, subject to appropriate notice and protection.

TeamLogger does not sell personal information for money and does not use employee work records or screenshots for third-party advertising.

8. Retention, deletion, and local copies

Retention depends on the type of record, lawful customer instructions, service-plan and contractual requirements, security and dispute-resolution needs, and applicable law. Company account owners may control or request deletion of many work records. Specific records may need to be retained for payroll, accounting, audit, fraud prevention, legal claims, or another lawful requirement.

Screenshot history is ordinarily available in TeamLogger for up to 120 days from recording. That product-access window does not by itself determine how long every customer-controlled storage object, backup copy, security record, or lawfully retained record remains; those copies and records follow the other retention criteria and verified-deletion process described in this section.

TeamLogger acknowledges a deletion request within 24 hours after receiving it. When a verified deletion request applies, TeamLogger completes the applicable account or requested-data deletion from active systems and backup copies within 24 hours after verification and confirms completion. If a company controls an employee record, TeamLogger may coordinate with that company during verification. If specific records must be retained under lawful customer instructions or another legal requirement, TeamLogger deletes all other applicable data within the same 24-hour period and, when permitted, identifies what was retained and why. Retained records remain protected, restricted from ordinary use where appropriate, and may be de-identified when appropriate for the retention purpose.

To request account or data deletion, follow the process on the TeamLogger account and data deletion page.

9. Security

TeamLogger uses encrypted network connections, access controls, authentication safeguards, scoped permissions, operational monitoring, and other administrative and technical measures designed to protect information. No method of storage or transmission is completely secure. Customers are responsible for limiting roles, reviewing permissions, protecting credentials, and promptly removing access that is no longer needed.

10. Choices and rights

• Employees can decline a mobile screen-sharing request. If the employer requires capture for tracked work, declining may prevent that work timer from starting or continuing.
• Users can stop active Android sharing from the TeamLogger notification or stop the iOS broadcast through the platform interface.
• Workers can ask their organization for its available non-biometric attendance process and can request access, correction, or invalidation of a TeamLogger Kiosk face enrollment.
• Users can contact their company administrator or TeamLogger support to request access, correction, restriction, objection, portability, or deletion where applicable.
• Website visitors can use browser controls to restrict cookies and can use Google's available analytics opt-out tools.

Rights vary by jurisdiction. TeamLogger may need to verify identity and authority before acting on a request. If the company is the relevant data controller, the request may be referred to or coordinated with that company.

11. International processing

TeamLogger and its service providers may process information in countries other than the user's country. Where required, TeamLogger uses contractual or other recognized safeguards for international transfers. Customers should evaluate their own transfer and localization obligations before enabling the service for a workforce.

12. Children

TeamLogger is a business workforce service and is not directed to children. Customers must not use TeamLogger to monitor children or to collect children's information unless they have independently confirmed that the use is lawful and suitable. The TeamLogger mobile store listings are intended for adult workplace users, not the Kids or Families categories.

13. Changes to this policy

We may update this policy when the service, legal requirements, or data practices change. The current effective date appears at the top. Material changes may also be communicated through the service or the contact information associated with the account.

14. Contact

For privacy questions, account assistance, or a deletion request, email customersuccess@teamlogger.com.

Postal contact: Build80, B2/B401, Lakeview Tower, Vastrapur Lake, Ahmedabad, Gujarat, India 380015.