Privacy policy
Effective
The short version
- There is no account. We never ask for your email address, age or phone number.
- The camera counts your reps on your iPhone. No photo or video is saved, sent or seen by anyone.
- Your workout history, streak, XP and settings stay on your iPhone.
- The app lock works through Apple's Screen Time. You pick the apps in Apple's own picker, and Chalka never learns which apps they are or what you do in them.
- There are no ads and no tracking across other apps or websites.
- Chalka creates one random ID on your iPhone. Your purchase record and your usage events are kept under it, so we can see, for example, how many people who finish setup start a free trial. It holds no name, email address or Apple Account.
- The app sends usage events to our analytics service, PostHog: which screens open and which features get used, such as a set finished or an alarm saved, plus your App Store country. Never your name, your reps or anything from the camera. You can object by writing to us.
- Apple takes payment for Chalka Pro. Our subscription service, RevenueCat, keeps the purchase record, with your invite code. If you installed Chalka from an ad in the App Store, Apple tells RevenueCat which ad, without tracking you.
- Fixes reach the app through Expo's update service, which sees a random install ID and, after a crash, the error message.
- This website sets no cookies. It counts visits with Cloudflare Web Analytics, which doesn't identify you.
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:
- your first name, if you gave one, so the app can greet you
- your pet, Chalk or Mica, its name, and the promise you made in setup
- your answers from setup: what usually gets in the way, what you want from training, how often you train and your level, and your result if you took the camera test. If you set up Chalka before version 1.1, also the apps you said you scroll most and your estimate of daily screen time.
- your main exercise, daily goal, set size and figure
- your morning alarm (time, days and morning set)
- your app lock settings, the minutes you have earned and used, your emergency passes, and your minutes in the locked apps for each of the last two weeks (see The app lock)
- your sessions: when each one happened, the exercise, the number of reps or seconds, and the XP; and a total for each day you trained
- your XP, level, badges and streak
- the challenge you are doing, and the ones you have finished
- your dare settings, your invite code, and a friend's code if you entered one
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:
- a random ID that Chalka creates on your iPhone. It isn't linked to your name, email address or Apple Account. Chalka uses the same ID for usage data.
- if you installed Chalka after tapping an Apple Ads ad in the App Store, Apple's note of that ad, such as its campaign. Apple gives this through its AdServices framework, without your advertising identifier and without tracking you across apps. Chalka doesn't ask for permission to track you and doesn't need it.
- your invite code, and the code of the friend who invited you if you entered one. We use them to count how many people each code brings. Your friends know your code, so this record can be connected to you by people who know it.
- your purchase and subscription history in Chalka, including Apple's receipt for it
- your device type, iOS version, app version, and your language, region and currency settings
- when you last opened the app
- if you cancel from Manage subscription in Chalka's Settings tab and choose to say why, the reason you pick
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:
- a random ID that Expo's software creates on your iPhone when the app is installed. It isn't linked to your name, email address, Apple Account or the RevenueCat ID.
- the app's version and update details, and that it runs on iOS
- if the last update made the app crash, the error message, so the app can go back to a version that works
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:
- opening the app, each setup screen as it opens, your answer to the lock question in setup (when your apps should lock, or Not now), and on the setup screen after a purchase, whether you allowed alarms and Screen Time or skipped them
- the paywall opening, whether its prices loaded and whether Apple offers you the free trial, the plan you tap, the one-time Lifetime offer being shown, and how a purchase or restore ended: the plan, whether it had a free trial, and whether it went through. Never your payment details.
- each set ending: the exercise; whether it was a set, the morning set, a dare, a workout or free mode; whether it was done in full, stopped early or closed with nothing counted; and whether the camera was counting. Never the number of reps or seconds, or your XP.
- reaching your daily goal, and earning a badge (which one)
- saving the morning alarm: whether it's on, how many days a week it rings, whether it rings with a workout, and its exercise. Never the time it rings.
- an alarm or its notification opening the app, and switching the scroll limit on Home on or off (with its minutes)
- starting, leaving or finishing a challenge (which one), opening the share sheet for a dare, an invite or a badge, Chalka asking iOS for its rating prompt, and opening Rate or Send feedback
- with the app lock: turning it on (its rules and how many apps are picked, never which: Apple doesn't tell Chalka), using an emergency pass from the Lock tab, opening a set from the lock's notification, and taking an app off the lock (how many stay locked)
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.
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
- We don't have accounts or sign-in.
- We don't show ads and we don't use advertising networks, in the app or on this website. The one detail about ads we receive is Apple's note of whether an Apple Ads ad led to your install (see Subscriptions). This website counts visits with Cloudflare Web Analytics (see This website), and the app's usage events are described under Usage data.
- We don't track you across other companies' apps or websites, and we don't access your iPhone's advertising identifier.
- We don't sell or rent personal data, or share it for advertising.
- We don't use your location, contacts, microphone or health data, and we can't see your photos.
- We don't build a profile to target or personalise anything. PostHog's profile under the random ID holds only your App Store country.
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.
- Chalka never asks for your age, email address, phone number or a photo of you.
- There is no public profile, no chat, and no way for other people to find you in the app.
- Your workout history stays on your iPhone.
- The only data that leaves your iPhone is the random IDs, invite codes and purchase record described under Subscriptions, the update requests described under App updates, and the usage events described under Usage data. They are used to make Pro, invites and updates work, and to improve the app. They are never used for advertising or to contact anyone.
- Usage events carry no name or contact details. There are no settings to share more, and we don't ask you to.
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.
Why we may use data
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:
- To provide Pro. Turning on and restoring a subscription you bought is needed to perform our contract with you.
- To check for Pro, prevent fraud and see subscription totals. This is in our legitimate interest in running a secure, working app. The record doesn't identify you, which keeps the effect on your privacy small.
- To see which Apple Ads bring people who subscribe. This is in our legitimate interest in spending on what works. Apple's ad note comes without your advertising identifier.
- To count invites. This is in our legitimate interest in growing the app through people who use it. The codes are random and hold no name or contact details.
- To deliver fixes and undo a faulty update. This is in our legitimate interest in keeping the app working. The install ID is random, and nothing in the request says who you are.
- To improve the app with usage events. This is in our legitimate interest in finding out which parts of Chalka work and which don't. The events carry a random ID and no name, and you can object at any time by writing to us.
- To see subscription changes beside usage. This is in our legitimate interest in knowing whether the app is worth paying for. RevenueCat sends them under the same random ID, with no name or contact details.
- To deliver and protect this website, and count its visits. This is in our legitimate interest in running a website that works, stays safe and reaches the people it's for. The visit counts don't identify anyone.
- To answer your email. This is in our legitimate interest in helping the people who use Chalka, or needed for our contract with you when you write about a purchase.
How long we keep it
- On your iPhone: until you delete the app.
- With RevenueCat: for as long as we need it to provide Pro, handle refunds and disputes, and meet our legal obligations. Then it is deleted.
- With PostHog: usage events and subscription events are kept for one year, then deleted.
- With Expo: update requests are kept under Expo's retention rules, for delivering updates and counting installs and crashes.
- With Cloudflare: request details and visit counts are kept under Cloudflare's retention rules, for delivering and protecting the site and counting visits.
- Email: for as long as we need it to help you and keep a record of what we agreed. Then we delete 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