Frequently asked questions.

Intro Pro is €19.99 as a one-time unlock, available until December 1, 2026. After that it moves to the regular price of €29.99. There's no subscription and no recurring charge either way.

A full 45-day trial with nothing crippled: unlimited clients, projects, and entries, reports, and both CSV and Excel export. You're evaluating the real app, not a limited demo.

No. There's no required account and no login screen. Tracky opens straight into the app, and the only reason you'd ever hand over an email address is to join the launch list.

The plan is a single one-time unlock for the current app. If that changes for a future major version, existing Pro users will hear about it directly and won't be surprised by a paywall appearing on an update they already paid for.

Locally on your Mac, using Apple's SwiftData framework. There's no Tracky server involved at any point, so nothing about your clients, projects, or entries is sent anywhere unless you explicitly export it.

Export a backup from Settings → Data before you switch machines, then import that same file on the new Mac. It's a single JSON file with every client, project, entry, time log, and setting, so nothing is left behind.

It replaces it. Importing a backup is meant for restoring onto a clean or matching state, not merging two histories together, so Tracky asks for confirmation before an import overwrites whatever's currently in the app.

Yes. It's a plain, readable JSON file, not a proprietary binary blob. You can open it in a text editor to inspect what's in it, and that same readability is what makes it possible to convert data from another tool into it — see the import questions below.

Yes, once. The storage layer was rebuilt with a dedicated migration path that moved every existing user's data across automatically, without loss. The same care applies to any future migration.

Not directly yet, there's no built-in importer for other trackers. But Tracky's own restore feature accepts any file that matches its backup structure, and that structure is a plain, documented JSON shape, so you can get existing data in without waiting for us to add a specific integration.

Export your history from your current tool in whatever format it offers, usually CSV or JSON. Then hand that export to ChatGPT or Claude along with the Tracky backup shape below, and ask it to convert your export into a matching JSON file. Import that file from Settings → Data, and your history shows up as regular entries.

A single JSON object with five top-level fields: exportedAt (a date), and arrays for clients, projects, timeEntries, timerSegments, and settings. Projects reference a client, and time entries reference a project plus one or more timer segments that hold the actual start and end times. Export a small backup from your own Tracky first: it doubles as the exact template to hand the AI, complete with the real field names and ID format it expects.

Treat it the way you'd treat any tool you paste client information into: check what that AI provider does with submitted data, and strip or anonymize client names first if you'd rather not share them at all. Once you have a converted file, importing it happens entirely on your Mac, nothing about that step touches a server.

It's a reasonable request and one we're watching for demand on. If you'd want a specific tool supported directly, the launch list is the best place to say so.

If Tracky quit or the Mac restarted mid-timer, it offers to continue or stop that timer the next time you open the app, so a running session is never silently lost. Separately, idle detection can flag long stretches without input and let you trim them from the entry afterward.

Yes. Typing a duration that differs from the logged segments keeps both: the override is what's used everywhere, but the table still shows the raw tracked time underneath, so the correction never erases the original record.

Nothing changes for the historical entries. Archiving just hides that client or project from the active list; every entry already logged against it stays exactly as it was and still shows up in reports and exports.

Always, single or bulk, with a reminder that it can't be undone unless you have a backup. That's one more reason a periodic backup export is worth the habit.

No. Rounding to the nearest 5, 10, or 15 minutes only affects what's shown in the table, reports, and export. The underlying tracked time is never overwritten, so you can change the rounding rule later without losing precision.

Yes. Set a default rounding interval and direction app-wide in Settings, then override it per project, along with that project's default billable state, whenever one client's rules differ from another's.

Plain CSV or a native XLSX file, built without any dependency on Excel being installed. You choose which columns to include, the duration format (HH:MM:SS, minutes, or decimal hours), and whether billable and non-billable entries get split into separate sections with their own subtotals.

When billable groups are split out, XLSX exports use real =SUM(...) formulas for each subtotal rather than a static number, so the sheet recalculates itself if you tweak a row after opening it in Excel.

Select one or more entries and mark them invoiced in bulk, optionally attaching an invoice number at the same time. Reports then break totals into billable, invoiced, and uninvoiced, so it's always clear what's still owed.

Not yet. An iPhone companion is planned after iCloud sync ships, for quick entries and timer control away from your desk. It will require iCloud sync turned on, since that's what keeps the phone and Mac in step.

No. CloudKit sync is already built into the storage layer, waiting for a public toggle, and it runs entirely through your own Apple account. There's no Tracky server in between, on or off by default, now or after it ships.

No, and none is planned. Tracky is built natively for the Mac menu bar, and that focus is deliberate rather than a gap waiting to be filled.

It's on the roadmap after iPhone, for starting and stopping work from your wrist. No date yet, it follows the same iCloud-sync dependency as the phone app.