Keep your own copy of your workspace, in storage you already own. Time Trakkr exports your data to Box on a schedule you choose, and tells you exactly what each archive holds.
Pick a cadence — daily, weekly or monthly — and Time Trakkr exports your workspace as a ZIP of CSVs, one per table, and uploads it to Box. Set a retention count and older archives are removed automatically after each successful upload, so the folder does not grow without limit.
You can run an export immediately with Run now, or pause a destination without losing its configuration or its history.
Alongside the CSVs is a manifest.json listing what was written and what was deliberately withheld, with a reason for each. An absence reads as a decision rather than as an empty workspace.
Connecting Box gives Time Trakkr read and write access to the whole account the connecting user can see — not only a backups folder — for as long as the connection stays active.
This is a constraint of Box’s self-serve authorisation flow rather than a corner we cut. That flow offers two scopes, root_readonly and root_readwrite, and neither is folder-scoped. Box does support genuinely folder-isolated access, but only through service-account authentication, which has no per-user Connect button at all.
Time Trakkr writes only its own backup archives. The warning appears again next to the Box connect button before you authorise anything. If you would rather grant less, our Google Drive and Dropbox connections are both scoped to what the app itself creates.
Box is connected from inside a Time Trakkr workspace, under Settings → Backups. Time Trakkr is currently invite-only, so if you do not have a workspace yet, start there.
Invite-only during beta. Free while we build together.
Request an invite