Policy
Privacy Policy
LiftJot is designed so the developer does not automatically receive your workout history. The app stores training data locally and has no account, ads, analytics, tracking, developer-operated cloud service, or app-owned upload to the developer.
Important distinction: LiftJot does not send your workout log to a developer service. Apple or Google may separately transport a recovery copy that the app prepared, as part of operating-system-managed device backup or transfer. Data can also leave your device when you use a share sheet, send support email, open this website, or use operating-system notification surfaces.
1. Who is responsible
LiftJot is developed and published by Vitalii Vyrodov (“LiftJot”, “we”, or “us”). Privacy questions may be sent to liftjot@gmail.com.
2. Data kept by the app
The app stores workout dates, notes, exercises, categories, sets, pending targets, rest state, and app preferences in private storage on your device. LiftJot calculates progress from those records and processes supported import files locally.
LiftJot has no user account, sign-in, advertising, analytics, tracking SDK, developer-operated app server, or app-owned upload path for workout data. It does not automatically transmit your workout data to us.
We do not sell personal information, share it for cross-context behavioural advertising, disclose it to data brokers, or use it to train machine-learning models.
3. Operating-system backup and transfer
Depending on your platform, your settings, and your installed version, LiftJot may prepare a limited rotating set of recovery copies of your training log and mark them as eligible for operating-system-managed device backup or device-to-device transfer. Apple or Google—not a LiftJot developer service—decides whether to transport them and carries them out under their own terms.
A recovery copy holds the same portable record as a backup you make yourself: your workout history, day notes, exercises, categories, and the settings needed to restore them. The app's working data—its live storage, timer state, diagnostics, temporary files, and the safety copies described in section 4—stays outside that eligibility. App-controlled settings cannot describe every vendor tool or platform behaviour, and files you create yourself are a separate case explained in section 4.
These copies are best effort, not a guarantee. The operating system may never transport one, decides on its own whether and when transport happens, and LiftJot cannot confirm that it occurred. A copy that was transported may be out of date. Where the app reports that a recovery copy was prepared, that means only that LiftJot created and checked a local eligible file—not that it was backed up, and not that recovery will be possible. We recommend making your own backup rather than depending on this.
4. Files and actions you initiate
| Action | What LiftJot does | Copies and recipients |
|---|---|---|
| Create a backup | Prepares and checks a .workoutlog file in the app's own storage area, then opens the operating-system share sheet. | The file in the app's storage area remains. Another destination receives a copy only if you complete the share or save; LiftJot cannot verify that external copy. |
| Export CSV | Prepares a CSV file of performed sets and related workout fields in the app's own storage area, then opens the operating-system share sheet. It is not a complete restore record. | The file in the app's storage area remains. Each completed share or save may create another copy under that destination's terms. |
| Restore a backup | Prepares and checks a safety copy of your current training record before replacing it. | The safety copy may remain afterwards. The app offers a control to delete it directly after a successful restore; otherwise it stays. |
| Import a file | Reads a supported file you select without modifying it, and prepares a safety copy of your existing record before writing anything. | No LiftJot server receives the source file; the file provider you picked it from may handle access under its own terms. Recent safety copies remain, and clean-up of older ones is best effort. |
| Send feedback | Opens an editable email draft containing app version, platform, and app language, but no workout data and no automatic attachment. | Only if you send it, the message goes through your mail provider to our mailbox. |
| Open this policy | Makes a normal web request, such as IP address and browser/request information. | Cloudflare, which hosts these pages. |
Some of these files are replaced as newer ones are written, and LiftJot's clean-up of the older ones is best effort; others are never removed automatically. Treat anything LiftJot has written for you as still present unless you have deleted it yourself. The app does not provide a general in-app browser or deletion control for the files in its storage area, and clearing your workout history does not remove them.
On iOS, the backups and CSV exports LiftJot has written remain eligible for Apple-managed device backup. On Android, the app's own backup rules cover only the recovery copies described in section 3. Safety copies are configured to be excluded on both. Copies you saved or shared outside LiftJot must be deleted separately at every destination. LiftJot does not add its own encryption to the files it writes; that says nothing about encryption your device, an operating-system backup, or a destination may apply on top.
5. Notifications and Live Activities
With your permission, LiftJot uses local device notifications and, on supported iPhones, Live Activities to show generic rest-timer information. These are operating-system surfaces, not developer push messages. Your system settings may display or mirror them on other devices. The in-app timer still works if notification permission is denied.
6. Support correspondence
If you contact liftjot@gmail.com, we receive the name and email address supplied by your mail service, your message, any attachment you deliberately add, and later correspondence. We use it to answer requests, troubleshoot, prevent abuse, and meet legal obligations.
Please do not send workout records or other sensitive health information. We normally delete support correspondence from our active mailbox within 12 months after the last reply, unless it is still needed to resolve the request, prevent abuse, or satisfy a legal obligation. Gmail may retain deleted material temporarily or for security, backup, and legal purposes under Google’s Privacy Policy.
7. This website
This is a static Cloudflare Pages website. We do not add analytics, advertising, tracking pixels, contact forms, third-party fonts, or tracking cookies. When you open the site, Cloudflare processes ordinary web-request data—such as your IP address, HTTP request details, and traffic-routing and security information—to deliver and protect the pages under the Cloudflare Privacy Policy. Cloudflare Web Analytics is disabled, and we do not receive a visitor-level analytics dashboard from this site.
We may also use Google Search Console to understand how people find this website in Google Search, using aggregate search impressions and clicks. This does not add tracking code to the website.
8. App stores and operating-system services
Apple and Google independently process data when you browse, download, pay for, review, update, back up, or transfer apps. Their privacy policies govern that processing. They may provide us with aggregated store statistics, such as store-page visits, downloads and referral sources. We use these statistics to understand how people discover LiftJot. Where you allow sharing through your device or store settings, the platforms may also provide crash and performance reports, which we use to find and fix defects. These reports come through the platforms’ developer consoles, not from a LiftJot server. LiftJot has no in-app account to connect them to.
9. Retention and deletion
Local app data stays on your device until you use LiftJot's deletion controls or remove the app, subject to platform behaviour. Clearing your workout history permanently removes your performed history and the local recovery copies described in section 3, while keeping your exercises, categories, and preferences. It cannot retract a copy that Apple or Google already transported, and it does not remove the files covered by section 4.
Files you created yourself, and the safety copies described in section 4, are subject to the limits stated there. Apart from the control offered directly after a successful restore, LiftJot does not provide an in-app list or deletion control for them. Copies you saved or shared elsewhere must be deleted from each destination. Because LiftJot operates no developer recovery service, we cannot remotely view, correct, export, restore, or delete anything on your device or in platform backup. If you deliberately attach and send a workout file in support email, we receive that attachment as support correspondence under section 6.
For support correspondence held by us, you may request access, correction, or deletion by emailing the address above; applicable legal exceptions may apply.
10. Legal bases and your rights
Where European data-protection law applies, we rely on our legitimate interests in answering support requests, troubleshooting, securing our services, preventing abuse, and keeping necessary records. We may also process correspondence to take steps you request in connection with LiftJot or to comply with a legal obligation. We do not use support data for automated decision-making or profiling.
Subject to applicable law, you may request access, correction, deletion, restriction, or portability of personal data held by us, or object to processing based on legitimate interests. You may also complain to your local data-protection authority. Contact us at the address above. Google and Cloudflare may process email or website-request data in countries other than yours under their own policies and transfer mechanisms.
11. Security
LiftJot limits exposure by keeping training records in the app's private local storage, operating no developer cloud account, and keeping its operating-system backup eligibility narrowly scoped as described above. Device security, and the protection offered by an operating-system backup or by a destination you share a file with, are outside LiftJot's control.
LiftJot does not add its own encryption to the files it writes for you. No app, device, file, backup, or method of storage or transmission is completely secure. We cannot guarantee that data on your device, in a platform backup, or in files you have shared will never be accessed, altered, or lost. Keep and check independent backups of anything you cannot afford to lose.
12. Age
LiftJot is intended for users aged 16 and older and is not designed for children under 16. Users aged 16 or 17 should contact support only with a parent’s or guardian’s permission where local law requires it.
13. Changes and language
We will post revisions at this URL and update the date above. Material changes affecting app behaviour will also be reflected in the app and in store declarations as required.
English is the reference version to the extent permitted by applicable law. Non-English versions are provided for convenience and intended to convey the same meaning; mandatory rights under applicable law are not limited by a translation rule.
14. Contact
Vitalii Vyrodov
Email: liftjot@gmail.com