TrackTime
HomeProductPricingAboutBlog
Sign inStart trial

Privacy Policy

Last updated: September 25, 2026

TrackTime is a time-tracking service for professionals who bill by the hour. This policy explains what we collect, why, and what we never collect. The short version: we capture metadata, never content.

Using TrackTime Lite from the Play Store? Lite has a narrower set of permissions and no auto-detection. See the Lite privacy policy for the version that applies to that app.

Operator

TrackTime is operated by TripleDot LLC. References to “we,” “us,” or “TrackTime” in this policy refer to TripleDot LLC. Contact us through our contact form.

1. What we collect

To deliver TrackTime, we collect:

  • Account data — your name, email, password (stored as a salted argon2id hash), and organization details if you sign up as part of a firm.
  • Activity metadata — for calls, SMS, RCS, emails, and travel that the app captures: timestamps, durations, contact identifiers (phone number or email address), and the originating app or activity type. On Android, this metadata is obtained through the platform's Accessibility Service (for outgoing-message detection) and Notification Listener Service (for incoming-message detection); see section 10 for the full permissions map. We do not capture call recordings, message bodies, email subjects/contents, photos, or location traces. For transparency: when the app shows its on-device confirmation popup, it may briefly display the subject of an email you just sent or the first few words of a message you just received (SMS, RCS, WhatsApp, Signal, or Telegram), so you can tell which conversation the entry belongs to. That text is held in memory only while the popup is visible; it is never written to the device database and never transmitted to our servers.
  • Time entries you create or confirm — including any notes you choose to add and the client or project you assign the entry to.
  • Billing data — if you subscribe to a paid plan, Stripe handles your payment information and shares only a customer ID and subscription status with us.
  • Operational logs — IP address, user-agent, and timestamps of authentication and admin actions, retained for security auditing. Your sign-in sessions (device, IP address, time) are shown to you under Account → Sessions, where you can end any of them; session history is kept for 90 days.
  • App health report — with each sync the Android app reports its version, whether monitoring and its required Android permissions are enabled, and the time of its last automatic capture. This is metadata about the app itself (no call, message, or email data) and is used to help you keep tracking working.

2. What we never collect

  • Audio or video from your calls.
  • The body of your SMS, RCS, or messaging-app threads.
  • Email subject lines, bodies, attachments, or contact lists beyond the addresses you have communicated with.
  • Your precise GPS trail. Travel detection runs locally on the device; the server only sees start/end timestamps and a derived duration.
  • Photos, contacts, or files outside of what you explicitly attach to a time entry or invoice.

3. How we use your data

We use your data to provide the service: showing you your time entries, generating invoices, syncing across your devices, sending receipts and security notifications. We do not sell your data, and we do not use your data to train AI models.

4. Storage and security

  • All data in transit is protected with TLS (HTTPS).
  • Server-side databases run on dedicated servers we control, reachable only over a private network and never from the internet; passwords are hashed with argon2id; API keys and refresh tokens are stored as cryptographic hashes only.
  • The Android app stores its local database with SQLCipher (AES-256), with the encryption key protected by the device's Android Keystore. The app opts out of Android cloud backup, and its connections to our servers are pinned to our certificate authority's root keys.
  • We follow OWASP Top 10 hardening for the API surface and run regular security reviews.
  • Documents we sign, such as customer agreements and operator attestations, carry an OpenPGP detached signature from the TrackTime operator key. Its fingerprint is 38AA B7D0 0D13 E4C2 378E 2B4A DA51 1391 662B 70DD. Before relying on a signed document, verify its signature against this fingerprint as published here, not against a copy sent alongside the document.

5. Sharing and third parties

We share data only with vendors required to run the service:

  • Stripe for payment processing.
  • Postmark for transactional email delivery (verification, password reset, and account notices).
  • WebNX (Ogden, Utah, USA) for dedicated server hosting.

We do not share your data with advertisers or data brokers under any circumstances.

6. Your rights

You can export every time entry, client, and invoice you've created. You can delete your account at any time; access ends immediately and all account data is permanently deleted from our systems 30 days later. Individual time entries you delete are permanently removed within 30 days. Backups are encrypted and destroyed after 90 days. To request export or deletion, use our contact form.

7. Cookies and analytics

We use first-party, HTTP-only session cookies for authentication (an access token, a refresh token, and a CSRF token). We do not use third-party advertising or behavioral analytics cookies. Aggregate usage telemetry (page views, feature usage counts) is collected only to size capacity; no individual user is identified in those aggregates.

8. Children

TrackTime is a professional product and is not directed at children under 16. We do not knowingly collect data from minors.

9. International transfers

Our infrastructure is located in the United States. If you sign up from outside the US, your data is transferred to the US for processing. We rely on Standard Contractual Clauses where required by GDPR.

10. Android permissions

The TrackTime Android app requests the following permissions. Each one maps to a specific feature; we do not request a permission “just in case.”

  • Phone & Call Log (READ_PHONE_STATE, READ_CALL_LOG) — detect that a call started/ended and read its duration and contact identifier, so we can suggest a draft time entry. We never record audio.
  • SMS (READ_SMS) — count SMS messages sent/received per contact for time-entry suggestions. Message bodies are never stored or transmitted. As described in section 1, the first few words of an incoming message may appear briefly on the on-device confirmation popup, held in memory only.
  • Contacts (READ_CONTACTS, optional) — match captured phone numbers and email addresses to a client name you've saved. If you decline this, captures still work; they just show the raw number/address instead of the contact name.
  • Notification Listener (BIND_NOTIFICATION_LISTENER_SERVICE) — detect sent-mail confirmations from Gmail and Outlook, incoming RCS messages via Google Messages, and incoming WhatsApp, Signal, and Telegram messages. Notifications from any other app are ignored without being inspected. Replies sent from the notification's quick-reply action are also detected. We keep only the sender identifier, originating app, and time; message body content is never stored or transmitted, though the first few words may appear briefly on the on-device confirmation popup as described in section 1.
  • Accessibility Service (BIND_ACCESSIBILITY_SERVICE) — detect outgoing email sends. Outgoing email events are not exposed via the notification system on Android, so the Accessibility framework is the only API surface that allows the app to detect them. The service is restricted at the operating-system level to Gmail, Outlook, and Google Messages and receives nothing from any other app. Within those apps it reads only the recipient and subject fields of an email being composed and the conversation title in Google Messages; the recipient becomes the client match, and the subject is used only for the on-device popup and is never stored or transmitted. It does not read message or email bodies, capture keystrokes, or perform any action on screen, and it persists nothing beyond the timestamp, counterparty identifier, and originating app.
  • Foreground Service (FOREGROUND_SERVICE) — keep the capture service alive while the app is in the background, with a persistent system notification visible to you at all times.
  • Battery Optimization Exclusion (REQUEST_IGNORE_BATTERY_OPTIMIZATIONS) — prevent Android Doze from killing the capture service. Without this, captures stop a few hours after the screen turns off.

Before requesting any of the restricted permissions above (Accessibility, Notification Listener, SMS, Call Log), TrackTime shows an in-app disclosure explaining what the permission enables and what is and is not accessed. You may revoke any permission at any time from Android Settings; the app degrades gracefully and continues to function with reduced capture coverage.

11. Changes to this policy

We'll email all account holders at least 30 days before any material change to this policy. Non-material changes (clarifications, typo fixes) may be made without notice but are reflected in the “Last updated” date above.

12. Contact

Questions or requests: send a note via our contact form.