Chalka

Privacy policy

Effective

The short version

Who we are

Chalka is made by LVL Digital Ventures Ltd, a company registered in England and Wales with company number 17436151. Our registered office is 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. In this policy, “we” and “us” mean LVL Digital Ventures Ltd.

Under UK data protection law, we are the controller of the small amount of personal data described below.

Questions about privacy go to privacy@chalka.app.

What stays on your iPhone

Chalka saves the following in its own storage on your iPhone:

None of this is sent to us or to anyone else. We cannot see it.

Chalka also keeps the random ID it created for your purchase record and usage data (see Subscriptions and Usage data).

Chalka keeps your last 500 sessions and drops older ones. Your daily totals and XP are kept.

If you back up your iPhone to iCloud or a computer, the backup may include this data. That backup is held by you and Apple, not by us.

The camera

Chalka asks for camera access the first time you start a set. It uses the camera only while a set is on screen.

Apple's body pose detection, which is part of iOS, finds the positions of your joints in each frame, such as your shoulders, hips and knees. It runs on your iPhone. Chalka uses those positions in the moment to count reps, time a hold and draw the skeleton on screen. Then it discards them.

No photo, video or joint data is saved, uploaded or seen by us. Only the result is saved: the exercise, the number of reps or seconds, and the XP.

You can turn camera access off at any time in Settings > Apps > Chalka. Without it, Chalka can't count your reps.

Alarms and notifications

If you allow alarms, the morning alarm rings through iOS's alarm system, which sounds even in silent mode, only at the times you set. If you don't allow it, it arrives as a notification instead.

Chalka also sends a reminder two days before a free trial turns into a paid subscription. If you use the app lock, tapping Earn minutes on the lock screen can send a notification that opens your set.

All of these are scheduled by the app on your iPhone. They don't come from a server, and we don't use a push notification service. You can turn notifications off in Settings > Notifications > Chalka, and switch the alarm off in Chalka.

The app lock

The app lock is optional. It uses Apple's Screen Time framework, and the first time you set it up, iOS asks whether Chalka may use Screen Time. You can say no, and you can take the permission back in Settings > Screen Time.

You choose the apps, categories or websites to lock in Apple's own picker. iOS gives Chalka a coded reference for each one, which it can use to lock it, and the number you chose. Chalka never learns which apps or websites they are, can't see what you do in them and doesn't read anything from them.

To keep a daily limit, iOS tells Chalka when you have spent a number of minutes in the locked apps, all of them together. Chalka keeps your lock settings, the minutes you have earned and used, your emergency passes and a daily total of minutes in the locked apps on your iPhone. The lock screen shows your pet, from a picture saved on your iPhone. None of this is sent to us or anyone else.

The usage events about the lock say only that it was set up (its rules and how many apps you picked), that a pass was used, that a set was opened from the lock's notification, or that an app was taken off the lock (see Usage data). If Chalka Pro ends, every lock lifts.

Sounds

Chalka's alarms ring with iOS's own alarm sound, and its notifications with the default sound. Chalka doesn't use the microphone and never records you.

Saving pictures

When you save a badge or a dare picture from the share sheet, iOS adds it to your photo library. Chalka asks only for permission to add photos. It can't see the photos you already have.

Sharing

When you share a dare, an invite, a result or a badge, iOS opens its share sheet with a short message or a picture. Dares and invites include your invite code. You choose where it goes. We don't see the message or who receives it.

Chalka doesn't read anything from other apps. The app lock closes the apps you pick without learning which they are (see The app lock). If you set up Chalka before version 1.1, the apps you said you scroll most are only an answer you gave. Chalka doesn't check them or see what you do in them.

Subscriptions

Apple handles every payment for Chalka Pro. We never see your card details, your Apple Account or your name. Apple's own privacy policy covers what Apple does with that data.

We use RevenueCat, Inc., based in the United States, to manage subscriptions. When you open Chalka, RevenueCat's software inside the app checks whether you have Pro. RevenueCat receives:

Like any internet service, RevenueCat's servers also see the IP address of your connection.

We use this data to turn on Pro, restore it on a new iPhone, prevent fraud, see totals such as how many people subscribe, see which Apple Ads bring people who subscribe, and see why people cancel.

RevenueCat is our data processor. It handles this data on our instructions. It does not receive your workouts, your settings or anything from the camera. RevenueCat also tells PostHog when your subscription changes, as described under Usage data. You can read RevenueCat's privacy policy.

App updates

We use Expo's update service, run by 650 Industries, Inc. in the United States, to send small fixes to the app without a new App Store release. When you open Chalka, the app asks Expo whether a newer version of its code is ready. Each request includes:

Expo's servers also see the IP address of your connection. Expo uses these requests to deliver updates and to show us totals, such as how many installs have an update and how often it crashes. It receives nothing from your workouts, your settings or the camera. You can read Expo's privacy policy.

Usage data

To see which parts of Chalka work and which get in people's way, the app sends short usage events to PostHog, our analytics service, run by PostHog, Inc. Each event says that something happened in the app. The events are:

Each event also carries whether you have Pro, whether it came from a test build, and details PostHog's software reads from your iPhone: the app's version and build, the iPhone model, iOS version, screen size, language and time zone settings.

The events are kept under the random ID Chalka created on your iPhone, the same ID as your purchase record at RevenueCat. PostHog keeps a profile under that ID with one detail: your App Store country (the country of your App Store account, not where your iPhone is). RevenueCat also tells PostHog when your subscription changes: a free trial starting, becoming a paid subscription or being cancelled, a renewal, a refund or an expiry, with the plan, its price and the details of your purchase record listed under Subscriptions, including your invite code.

That lets us see, for example, which countries and which parts of setup lead to people who keep training and subscribe. The ID doesn't say who you are: there is no account, and we can't connect it to your name or Apple Account unless you tell us, for example by sending us your Apple order ID.

Usage events never include your name, your other answers from setup, your reps, seconds or XP, anything you type, or anything from the camera.

PostHog's servers see the IP address of your connection when the app sends events. We have set PostHog not to store it and not to look up a location from it.

We use the events as totals and trends: how many people finish setup, which exercises get finished or closed, whether the alarms get used, and which countries lead to subscriptions. Not for advertising, not to change what the app shows you, and not to make decisions about anyone.

You can object to usage events at any time by writing to privacy@chalka.app (see Your rights). If you installed Chalka before usage data was added, the app sends nothing until it has told you, on the What's New screen of version 1.1. RevenueCat still keeps your purchase record and still tells PostHog when your subscription changes, because that's how we count subscriptions.

PostHog is our data processor. It handles these events on our instructions. You can read PostHog's privacy policy.

Apple

Apple runs the App Store and processes payments under Apple's privacy policy. If you have chosen to share analytics with app developers in your iPhone's settings, Apple may send us crash reports and usage statistics. These don't identify you.

This website

chalka.app is a set of plain pages. It sets no cookies, and its fonts and pictures come from chalka.app itself.

To count visits, the site uses Cloudflare Web Analytics, which may add a small script from Cloudflare to the page. It records the page, the site that linked to it, your country, your browser, operating system and device type, and how fast the page loaded. It uses no cookies or other storage on your device and doesn't fingerprint you. We see only totals.

Cloudflare, Inc. hosts the site. Like any web host, Cloudflare processes your IP address and the details of each request, such as the page and your browser, to deliver the pages and protect the site from attacks. You can read Cloudflare's privacy policy.

Email

If you write to us, our email provider, Zoho Corporation, stores your message and your email address for us. We use them only to answer you. You can read Zoho's privacy policy.

What we don't do

Children

Chalka is for anyone who wants to train a little every day. It is built so that nobody has to share personal details to use it.

Under 13 in the United States (COPPA). We don't knowingly collect personal information from children under 13. The app doesn't ask for any.

In the UK. We design Chalka with the Age Appropriate Design Code in mind: no location, no profiling for ads or to personalise the app, analytics under a random ID with no name or contact details, and only the data the app needs to work and to get better.

Parents and guardians. If you have a question, or want us to delete any data linked to your child, write to privacy@chalka.app.

UK data protection law requires a reason, called a lawful basis, for each use of personal data. The personal data we handle is the RevenueCat record and the subscription events it sends to PostHog, the update requests Expo receives, the usage events PostHog receives, the requests this website receives, and emails you send us. Our reasons are:

How long we keep it

Where it is stored

RevenueCat and Expo store data on servers in the United States. PostHog stores usage and subscription events in its EU cloud, in the European Union. Cloudflare serves the website from data centres around the world, close to whoever opens it. Zoho stores our email in its own data centres, which may be outside the UK. When data leaves the UK, we rely on the safeguards UK law requires for international transfers: the UK's adequacy regulations for the European Union, and for other countries the UK International Data Transfer Agreement or the UK Addendum to the European Commission's Standard Contractual Clauses.

Your rights

You have the right to ask for a copy of your personal data, to have it corrected or deleted, to object to or limit how we use it, and to receive it in a form you can take elsewhere.

Data on your iPhone is already in your hands. You can see it in the app, and delete it by deleting the app.

Usage events carry only a random ID. If you subscribed, include the order ID from Apple's purchase receipt email when you write: we find your RevenueCat record by it, and your usage and subscription events by the record's ID, and can copy or delete them. If you never subscribed, we can't tell which events are yours. Either way, they are deleted after one year.

For the RevenueCat record, write to privacy@chalka.app. Because the ID is random, please include the order ID from Apple's purchase receipt email. You can also find it at reportaproblem.apple.com. We reply within one month.

You can complain to the UK Information Commissioner's Office at ico.org.uk. Please contact us first so we can try to put things right.

Security

Data on your iPhone is protected by iOS, including encryption while your iPhone is locked with a passcode. Data sent to RevenueCat, Expo and PostHog is encrypted in transit, and this website is served only over HTTPS.

Changes

If we change this policy, we'll update this page and the effective date. If a change affects what data leaves your iPhone, we'll tell you in the app before it applies.

Contact

LVL Digital Ventures Ltd
71–75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom
privacy@chalka.app