Privacy

This page describes what My Time Counts does with your information. It describes the software as it actually works.

Who runs this

My Time Counts is operated by Code Repair Shop LLC. Questions about privacy: support@mytimecounts.com.

What is stored, and where

Your data lives in two places:

• A shared registry holds your account record — your email, display name, an internal user id, the identity your sign-in provider gives you — plus your device tokens and role assignments.
• Your own database holds your time entries and projects, and nothing belonging to anyone else.

Every request is handled against exactly one of these per-user files, chosen by the account that made it. No query reaches across users: one account's data cannot appear in another account's file or export.

Signing in

Sign-in is handled by an external identity provider — a service you already use to sign in elsewhere. We never see or store a password. The provider tells us your email address and a stable sign-in identity, which we store so your account is recognized the next time you sign in.

Your session is carried in a cookie that page scripts cannot read, sent only over HTTPS, and cryptographically signed. It expires after 14 days of inactivity. A service restart signs everyone out.

Device tokens (the mobile and API path)

A device signs in through the same identity provider and receives a long-lived access token, which it then uses for API requests. That token is never stored in a readable form: it is shown to the device once and cannot be recovered from our records. Where the device supports it, the token is bound to that device's own key, so a stolen copy is no use elsewhere. Tokens expire after 90 days; you can revoke any device at any time from the Devices page.

What is logged

We log operational events — that the service started, errors, and failed sign-in or token exchanges — so the service can be run and faults diagnosed. Logs do not contain the contents of your time entries. There are no third-party ads, no analytics, and no trackers: the pages load no external scripts, fonts or images, and the only outbound link on the site is the Code Repair Shop credit.

Getting your data out

When signed in, /export downloads your complete database as a single SQLite file — the same file the service uses, not a summary. The report page also offers a CSV of a date range. Today every account can export its data; there is no paid tier yet.

Deleting your data

You can delete your account yourself, without asking anyone. The Account page has a Delete this account button; signed in, it asks you to type a word to confirm, and then removes your account and the database behind it. It is immediate and it cannot be undone. If you cannot sign in, contact support@mytimecounts.com and we will remove the account for you.

What that removes, precisely — so nothing here is a surprise:

• Your time entries, your projects, and the database file that holds them. Deleted, not marked deleted; nothing is kept for a grace period.
• The account record itself — your email, display name and sign-in identity — and every device token issued for it, so every signed-in phone is signed out at once.
• Signing in again afterwards is allowed, and starts a new, empty account. The deleted account does not come back.

One related fact, about deleting an individual time entry or project rather than your whole account. Deleting one leaves a "deleted" marker rather than erasing it at once, kept only so a synced phone knows to drop its copy. Those rows are purged automatically 90 days later. Ninety days is long enough that a device offline for a season still learns the entry or project is gone, and it is the only reason a deleted row is kept at all.

Revoking a device immediately stops that token from working. Signing out ends the web session.

Who else is involved (subprocessors)

• Railway — hosts the service and its storage, in its iad (US East) region.
• Your identity provider — receives your sign-in request and holds the credentials; it sees your email and name at sign-in, not your timesheet.

No other third party receives your data. There is no advertising or analytics subprocessor, because there is no advertising or analytics.

Changes to this policy

Material changes will be reflected here with a new "last updated" date (2026-10-17).