Kilo Privacy Policy

Last updated: July 13, 2026

Kilo is a workout and body-weight tracking app provided by Ben Pronin, an individual ("we," "us," or "our"). For the purposes of the GDPR and UK GDPR, Ben Pronin is the data controller responsible for the personal information described in this policy. Questions about this policy can be sent to bpronin90@gmail.com.

Information Kilo handles

You can use Kilo locally without creating an account. Creating an account and enabling cloud sync are optional. If you do, Kilo collects and stores the following information to provide account and sync features:

• your account email address and Kilo account user ID;
• the profile name you choose to save (display_name);
• body-weight entries, weight goals and archived goals;
• workout content, including workout notes and related deload/fatigue history; and
• selected profile preferences and feature toggles, such as units, tracked lifts, workout-display state, and fatigue/deload settings.

We do not collect the template categories previously listed here, such as demographic characteristics, education, employment history, financial information, purchase history, or advertising/browsing profiles.

Device-local information and notifications

Your training history and app settings can be stored on your device. When you enable cloud sync, the selected preferences and feature toggles described above are also synced with your account. A stable per-install sync identifier stays on your device and is not uploaded. Local reminders are scheduled on your device only after you enable them. Kilo does not obtain, store, or transmit a push-notification token.

Diagnostics and service security

If a production build is configured with Sentry, Kilo sends crash and error diagnostics to Sentry to help us identify and fix problems. Sentry diagnostics are not sent when that service is not configured. Kilo also uses Expo Updates to deliver app updates.

To protect the account-export and account-deletion services from abuse, we temporarily retain the requesting IP address and authenticated user-ID rate-limit record. Export records are eligible for deletion after 10 minutes and deletion records after 1 hour; a scheduled cleanup runs every 30 minutes.

How we use information

We use information to provide optional account authentication and cloud sync, display and manage your training data, provide local reminders you request, secure export and deletion services, diagnose faults when diagnostics are configured, and deliver app updates.

Service providers and optional social sign-in

We use Supabase for account authentication, cloud storage, and related infrastructure. If you use email/password sign-up, sign-in, or password reset, your password credential is submitted to Supabase Auth for that purpose; Kilo does not store a plaintext password in its app data. You may optionally sign in with GitHub OAuth on web or Android. GitHub acts only as an identity provider for that sign-in; it does not host your Kilo account or synced training data. If enabled, Sentry processes diagnostics. Expo Updates provides update-delivery services. Termly provides the external data-subject-access/deletion-request form linked below.

We use these providers to operate Kilo, not to sell your personal information or to provide targeted advertising.

Legal basis for processing (GDPR/UK GDPR)

If the GDPR or UK GDPR applies to you, this section describes how we process your information and the basis on which we do so.

• Account and cloud sync — Art. 6(1)(b): Creating an account and enabling cloud sync are optional. Where you choose to do so, we process your account email, user ID, profile name, and synced preferences and feature toggles as necessary to provide the account and cloud-sync features you have requested.
• Health data — special category (Art. 9(2)(a) explicit consent): Body-weight entries; current and archived weight goals; tracked lifts and workout notes; deload notes and history, and fatigue-tracking data are data concerning health, a special category of personal data under Article 9 of the GDPR. Kilo does not process this health data in the cloud based on account creation or on enabling Cloud Sync alone. Instead, when you enable Cloud Sync, Kilo presents a dedicated, specific in-app consent step — separate from the account and sync toggle — in which you affirmatively state: "I explicitly consent to Kilo storing the health and fitness data listed above in its United States cloud database for cross-device sync." That affirmative statement is your explicit consent under Art. 9(2)(a), and it is the lawful basis for cloud processing of this health data. Our processor for this data, Supabase, is US-hosted and processes it under the EU Standard Contractual Clauses. Kilo keeps a minimal pseudonymized record of your consent choices for six years after account deletion to demonstrate compliance with Art. 7(1); that record contains no health entries, notes, or measurements. You can withdraw your consent at any time by turning off Cloud Sync; Kilo then stops cloud processing of this health data and deletes its cloud copy, without affecting the lawfulness of processing carried out before withdrawal. Turning off Cloud Sync does not erase device-local training history, which you continue to control on your device.

Exports and sharing you initiate

When you request an export, Kilo returns the export directly to you and does not retain a server-side export artifact. You may choose to send that export through your operating system's share sheet to an app or recipient you select. That transfer is initiated by you.

Security and retention

Kilo uses HTTPS/TLS for its network services. No method of transmission or storage is completely secure, but we use reasonable measures designed to protect information.

Cloud account and synced training data are retained while your account is active, unless we need to retain limited information for a legitimate purpose such as security, abuse prevention, or legal compliance. The specific short retention windows for rate-limit records are described above.

Delete your Kilo account or data

You can delete your account in Kilo. In-app account deletion deletes your Kilo account and its cloud copy of synced data. It intentionally does not erase device-local training history; you control that locally stored history on your device.

If you cannot access the app, you may request account or data deletion through the Kilo data deletion request form or by emailing bpronin90@gmail.com. We may need to verify your identity before acting on a request. We may retain the limited records described in this policy where necessary for security, fraud prevention, or legal compliance.

Your rights (GDPR/UK GDPR)

If the GDPR or UK GDPR applies to you, you have the right to:

• access the personal information we hold about you;
• request rectification of inaccurate or incomplete information;
• request erasure of your information;
• receive a portable copy of the information you provided to us, in a structured, commonly used, machine-readable format (see "Exports and sharing you initiate" above);
• withdraw any consent you have given, at any time, without affecting the lawfulness of processing carried out before withdrawal (Art. 7(3)) — for the health data described under "Legal basis for processing" above, you withdraw your explicit consent by turning off Cloud Sync at any time, which stops Kilo's cloud processing of that health data and deletes its cloud copy; and
• lodge a complaint with your local data protection supervisory authority.

You can exercise these rights using Kilo's in-app export and account-deletion features, the Kilo data deletion request form, or by emailing bpronin90@gmail.com. We may need to verify your identity before acting on a request.

Changes and contact

We may update this policy as Kilo changes. The current version is posted on this page. For privacy questions or requests, contact Ben Pronin at bpronin90@gmail.com.