DaysWork

Privacy Policy

Effective date: September 2, 2026

Version: 1.0.0

This Privacy Policy explains how the DaysWork mobile application (“DaysWork” or the “App”), provided by Sebastian Salas-Vaca, handles information.

In short

DaysWork does not collect your data. It has no servers, no accounts, and no internet connection.

The rest of this policy explains the detail.

1. How your camera is used

DaysWork asks for camera access the first time you start a workout. It needs the camera to see your movement; without it the App cannot count reps.

While a workout is running, the App receives a live stream of camera frames. Each frame is analysed immediately, in memory, on your device, and is then discarded. Frames are never written to storage and never leave your device.

DaysWork does not record video or take photographs. There is no recording feature in the App, no photo capture, and no access to your photo library. An earlier version of DaysWork could record sessions to your Photos library; that feature has been removed entirely, along with its permission.

DaysWork does not use your microphone. No audio input is ever requested, captured, or processed.

The live camera image you see on screen is a preview drawn directly by your device. It is not stored.

2. How pose detection works

To count reps, DaysWork uses Google’s MediaPipe Tasks Vision library together with a BlazePose model file. Both are bundled inside the App and run entirely on your device. The model is never downloaded, and the analysis never leaves your phone.

Because this is Google software, it is worth being precise about what it is. MediaPipe here is a library compiled into the App, not a cloud service the App calls. It does its work locally and sends nothing to Google. MediaPipe is open-source software published under the Apache License 2.0, so this is a property of the code that anyone can inspect — not something you have to take on trust. Section 6 sets out who does and does not receive your information.

For each frame, the model estimates the position of 33 points on a human body. Most are limb and torso joints — shoulders, elbows, wrists, hips, knees, ankles. A few are points on the head: the nose, eyes, ears, and mouth.

We want to be explicit about those head points, because “the app tracks my face” is a reasonable thing to worry about:

The App uses these points to work out joint angles and whether you are in position to begin an exercise. Once a rep is counted, the only thing kept is the count itself — a number.

3. What DaysWork saves on your device

DaysWork stores a small amount of information locally, in your device’s app storage. It is not encrypted beyond the protection iOS applies to app data, and it is not synced to iCloud or anywhere else.

That is the complete list. There is nothing else.

DaysWork does not ask for, collect, or infer your name, email address, phone number, date of birth, age, sex, gender, height, weight, body-fat percentage, heart rate, calories, location, contacts, or any other personal or biometric information. There is no sign-up, no login, and no user profile.

One note about workout names. The name you give a saved workout is the only free text in the App. It is stored exactly as you type it. Please do not put personal information in a workout name.

4. Data we do not collect

DaysWork contains no analytics, telemetry, crash reporting, advertising, attribution, or tracking software of any kind. Specifically, there is no Google Analytics or Firebase, no Meta or TikTok SDK, no Sentry or Crashlytics, no ad network, and no advertising identifier (IDFA) usage.

DaysWork does not track you across apps or websites, and does not share any information with data brokers. On the App Store, DaysWork is declared as “Data Not Collected.”

5. DaysWork does not connect to the internet

The App contains no networking code. It does not have a server, a backend, or an API. It does not upload, download, sync, or back up anything. DaysWork works fully in airplane mode.

Because nothing is transmitted, there is no server-side copy of your information for anyone — including us — to access, read, sell, or hand over. We cannot see your data, because we never receive it.

One point of precision, so this section is not overstated. DaysWork’s own code contains no networking of any kind. The MediaPipe library it embeds is third-party code that we compile in rather than write — it is open source under the Apache License 2.0, its analysis runs locally against a model file bundled in the App, and it is not built to make network requests. We have created no mechanism by which your information could be transmitted, and we are aware of no path by which it could be.

6. Third-party components, and who else sees your information

The short answer is: no one. DaysWork does not disclose, share, sell, rent, or trade your information with anybody, because it never transmits your information in the first place.

Because “no one” is easy to write and hard to trust, here is each party people usually ask about:

We do not sell your personal information, and we do not share it for cross-context behavioural advertising, as those terms are used in the California Consumer Privacy Act. We have not done so in the preceding twelve months, and we have no mechanism that would allow us to.

MediaPipe is used under the Apache License 2.0.

7. Your choices and control

Because DaysWork holds no information about you outside your own device, requests to access, correct, port, or erase remote data cannot apply here — there is no remote data. Deleting the App is the complete erasure mechanism.

8. Health information

DaysWork is listed in the Health & Fitness category, and rep counts are health-adjacent information. We want to be clear about what that does and does not mean:

9. Children

DaysWork is not directed at children under 13, and we do not knowingly collect information from anyone, including children. Because the App collects no information at all and has no accounts, there is no children’s data for us to hold or delete. A parent or guardian with questions can contact us at the address below.

10. Security

Your information stays within the App’s sandbox on your device, protected by iOS’s standard app-data protections and by your device passcode or biometric lock. Since nothing is transmitted or stored remotely, there is no server for an attacker to breach.

Anyone with unlocked access to your device can open DaysWork and see your saved workouts and history. If that matters to you, use a device passcode.

11. Changes to this policy

We may update this policy. When we make a material change, we will increase the version number of this document, and DaysWork will present the updated policy to you and ask you to accept it again before you continue using the App.

You can review the current documents, and the date and versions you accepted, at any time from the Legal screen in the App.

12. Contact

Questions about this policy or about privacy in DaysWork:

daysworksupport@gmail.com Sebastian Salas-Vaca