Your training records, on your device

tensr stores your training in a local database you can export. This page explains the core features we commit to keeping free and the design for optional paid services.

Keeping a copy

A usable copy also lets you put your records to work. Your own agents can read them, compare training blocks and build reports. Seewhat open data lets you do for examples and a first question to try.

The app reads and writes a SQLite database on your device. Exporting it as a.tensr.db file gives you a copy you can open with a SQLite tool, independently of tensr. The data model guide explains how to inspect the tables and query your history.

Keep an exported copy somewhere separate from the device if you want it to survive a lost phone or cleared browser storage. A local database alone isn't a backup. Another training app may need an importer to use the file; an open format doesn't mean every app already supports it.

What stays free without an account

Our core feature policy covers:

• Recording sessions with a supported sensor, at full fidelity.
• Viewing your session history, goals and personal records.
• Creating and editing goals and routines locally.
• Exporting your database.
• Manually moving data between your devices using links, QR codes or files.

Signing up adds account features. It must leave these core features available without payment or sign-up. Features involving a public profile or other users can require an account.

Planned cloud services

We plan to offer paid services such as cloud backup, automatic background sync and coaching tools. These are plans, not a list of features available today. Manual transfers between your devices remain part of the free core.

The design keeps a working copy of your records on your device, with the cloud acting as another copy. Ending a subscription must leave your local records available to read and export. Paid services can stop; retrieving your existing local history must not require a payment or support request.

Who can read synced data?

The planned cloud service can read the training data you sync.It is not end-to-end encrypted. The design uses encryption in transit and at rest, but those protections do not prevent the service from reading the data.

This supports server-side features such as backup and access for a coach you authorize. Cloud sync is opt-in. The privacy information presented when you enable it needs to explain what is uploaded and who can access it, so you can decide whether to use the service.

Sharing and leaving

A data-carrying share link includes its payload in the URL. Reading that payload doesn't require retrieving a stored copy from a tensr account. Compatible software is still needed to decode it, and the website that opens a link must be available. See the link format guide for details. Use a database export to keep your whole history.

Exported records and documented formats make switching easier. They can't transfer every app feature or bring your training partners with you. Our commitment is to keep your records usable and free to take elsewhere.