Applies to mcpro24fps (lv.mcprotector.mcpro24fps), mcpro24fps Demo (lv.mcprotector.mcpro24fps.demo) and the Russian build distributed directly as an APK (lv.mcprotector.mcpro24fps.red), for Android. Distributed through Google Play, Huawei AppGallery, Samsung Galaxy Store and RuStore, and — for the Russian build — published in our Telegram channel. Sections that name a store apply only to the store your copy came from.
1. Who we are
Controller: CHANTAL PRO SIA. Address: Bebru iela 16–34, Jēkabpils, Jēkabpils nov., LV-5201, Latvia. Registration number: 40103332030. VAT number: LV40103332030. Contact: info@mcpro24fps.com. Website: https://mcpro24fps.com
Write to info@mcpro24fps.com with any question about this policy or your data.
2. The short version
Shooting with mcpro24fps needs no account. Everything you shoot — video, audio, RAW/DNG frames, snapshots, presets and LUTs — stays in your device storage, under a folder you choose. The camera itself never connects to any system operated by Chantal Pro SIA.
An account exists for one optional thing only: RAW Bundle, the in-app purchase that adds the RAW player and converter and .mcpro recording. If you start its free trial or buy it, you sign in with the account of the store your copy came from, and the app talks to our licence server (§3.11). If you never sign in and own no RAW Bundle purchase, the app sends nothing to our server.
Only these kinds of data can leave your device:
- crash and error diagnostics (§3.1);
- the automatic usage statistics of the analytics SDK that belongs to your store build — we log no events of our own (§3.2);
- your purchases and donations, processed end to end inside the store's own billing component; we never see your payment details (§3.4);
- for RAW Bundle only: the email address and account ID of your store account, a random installation ID and your RAW Bundle purchase token, sent to our licence server (§3.11).
We never collect: your recordings or any frame of them; your microphone audio; your contacts, SMS, calendar or call history; your phone number or IMEI; any file outside the app's own output folder; your location (§3.6 — coordinates go into your own files only, and only if you switch that on); an advertising identifier (§3.3).
3. What is collected, why, and how you control it
3.1 Crash and error diagnostics
Which builds: the Google Play build and the Russian direct-APK build use Google Crashlytics. The AppGallery, Galaxy Store, RuStore and generic sideload builds are compiled without it.
What a report contains: device manufacturer, model and hardware name, the Android build fingerprint, Android version, app version and build variant, and the camera-session context needed to reproduce the fault — internal camera id, resolution, frame rate, codec and MIME type, bitrate, and whether the build is a Demo or Russian one — plus a short breadcrumb log of the last actions inside the app. When a fault happens while a finished recording is being registered in the Android media database, the report also carries the path of that file, which includes the folder and file name you chose. The contents of your files are never read, opened or transmitted.
Identifier: a report carries a random installation identifier created by the SDK, not an account and not a device serial. Clearing the app's data or reinstalling creates a new one.
Why: to find and fix faults in an application where a fault can cost you a take. Legal basis: Art. 6(1)(f) GDPR, our legitimate interest in a stable product.
Plainly: crash reporting is always on. The Statistics switch described below does not turn it off. If you do not want it at all, use the AppGallery, Galaxy Store or RuStore build, which ships without the crash SDK.
3.2 Usage statistics
We log no events of our own. Nothing about your settings, your shots, your camera, your presets or how you use the app is sent by us. What applies is only what the analytics SDK collects by itself: app first open, session start, app update and removal, foreground time, device model, OS version, app version, coarse country or region derived from your IP address, language, and an identifier the SDK generates for the installation.
Analytics SDK by store build
| Build | Analytics | Provider |
|---|---|---|
| Google Play (full and Demo) | Google Analytics for Firebase | |
| Huawei AppGallery | HUAWEI Analytics Kit | Huawei |
| Samsung Galaxy Store | none configured | — |
| RuStore | none configured | — |
| Direct APK, Russian build | Google Analytics for Firebase |
How to switch it off: in the app, Menu → Statistics → Off. The switch controls whichever analytics SDK your build contains — Firebase or Huawei — and nothing is sent while it is off. One honest exception: in the Russian direct-APK build, collection is switched back on at every app start. In the store builds, collection is also switched off automatically for as long as the camera is recording, so that it cannot interfere with capture.
Legal basis: Art. 6(1)(f) GDPR, and, where your store or your jurisdiction requires it, the consent you give when you first run the app.
3.3 Advertising identifier — not collected
The app shows no advertising, contains no advertising SDK and builds no profile of anyone. The advertising identifier is not collected on any Android version: the AD_ID permission is removed from the application at build time, the Privacy Sandbox permissions that the analytics library would otherwise add (ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION) are removed as well, and collection is switched off inside the analytics SDK itself, which also covers Android versions where no permission is required. In the AppGallery build the collection of Huawei's own advertising identifier (OAID) is switched off explicitly, since the Huawei analytics SDK would otherwise collect it by default. We run no advertising attribution of any kind.
3.4 Purchases and donations
The full version is bought in your store. Inside the app you can additionally buy RAW Bundle (§3.11) and make an optional donation of a fixed amount, as many times as you like. Every transaction runs inside the store's billing component: we receive no card number, no bank details and no billing address — only the aggregated sales reports our developer console shows. A donation unlocks nothing and nothing about it is sent to us. A RAW Bundle purchase is confirmed by our licence server with the store, as described in §3.11. Refunds are handled by the store under the store's own rules.
3.5 Rating prompt
The Google Play build may show the Google Play In-App Review sheet. Anything you write there goes to Google Play, not to us; we see only the public rating and review text that Google publishes.
3.6 Location — optional, and only inside your own files
Off by default. If you enable GPS data in the app and grant the Android location permission, the app writes the coordinates of the shot into the file you produce: the location atom of the MP4 container, and the GPS tags of DNG or JPEG output. Those coordinates live inside your file on your device. We never receive them and we have nowhere to receive them. Remember that anyone you later send the file to can read them — strip the metadata before publishing if that matters to you.
Legal basis: consent, Art. 6(1)(a) GDPR, given by turning the feature on. Withdraw it at any time in the app or in Android settings; the app then simply stops writing coordinates.
3.7 Bluetooth
Bluetooth permissions are requested for one purpose: connecting an optional BLE remote control. Scanning is declared neverForLocation, so Android will not derive your position from scan results. Nothing about your Bluetooth environment leaves the device.
3.8 Camera and microphone
Used to produce your recording and nothing else. No frame and no audio sample is transmitted anywhere, at any time, in any build.
3.9 Storage, settings and backup
Output is written to a folder you choose under DCIM/. Settings, presets and LUTs are kept in the app's own storage. The app sets android:allowBackup="false": Android's cloud backup does not copy its settings off your device.
3.10 Notifications
Used for the recording and background-task notifications Android requires. We send no marketing notifications and operate no push service.
3.11 Account and licence server — RAW Bundle only
When: only if you tap “Sign in” to start the 7-day free trial of RAW Bundle or to buy it, or if your store account already holds a RAW Bundle purchase that the app can restore. The camera, recording and playback work without it.
How you sign in: with the account of the store your copy came from — a Google account in the Google Play build, a HUAWEI ID in the AppGallery build, VK ID in the RuStore build, a Samsung account in the Galaxy Store build. The sign-in itself runs in that provider's own window; we receive your email address and the provider's account identifier for our app, never your password. No sign-in token is sent to our server. An account without an email address cannot be used, because your licence is tied to the email address.
What a request to our server carries: your email address and the provider's account identifier (once you have signed in), the name of the store, the app's package name, a random installation ID that the app creates on first use, the store's purchase token and product ID of your RAW Bundle purchase if there is one, a freshly generated random value (so that a signed answer cannot be replayed on another device), and a header with the signing-certificate fingerprint of the installed app, which lets the server reject tampered copies. Nothing about your recordings, your settings or your device contents is sent.
What the server does with it: checks a new purchase with the store's own purchase-verification service — Google Play Developer API, HUAWEI IAP order service, Samsung IAP receipt service or RuStore Public API, only the one of your store — and answers with a signed statement of what you are entitled to. Once a day it re-checks active purchases with the same store, which is how a refunded purchase stops unlocking RAW Bundle. A purchase can be used on up to 10 installations; reinstalling the app creates a new installation ID and counts as a new installation, and we can free the places when you change phones — write to us.
Stored on: our server api.mcpro24fps.com, in a PostgreSQL database hosted in the European Union: your email address, the store and the provider's account identifier, the start and end of your free trial together with a one-way hash of your email address computed with a secret key of our server (it records that the free trial was used and survives account deletion, so that one address gets one free trial), your purchase records (order ID, store, product, state, timestamps and the purchase token itself — kept because the purchase has to be re-checked with the store), and the installation IDs that use each purchase with the dates they were first and last seen.
Verification log. The server records attempts to verify a licence or a purchase: time, email address, store, product, the outcome and the IP address the request came from. A raw purchase token is never written to this log.
Legal basis: performance of the contract, Art. 6(1)(b) GDPR — the licence for RAW Bundle cannot be delivered without identifying the account and the purchase; for the verification log and the installation limit, our legitimate interest in the security of the licence service, Art. 6(1)(f) GDPR.
4. Third parties, by store build
Only the row group for your own store is active in your copy of the app.
Processors and what reaches them
| Service | What reaches it | Purpose | Build |
|---|---|---|---|
| Google Play services / Billing | purchase and donation transaction | sell the app and RAW Bundle, verify entitlement | Google Play |
| Google Sign-In | your email address and Google account ID | sign in for RAW Bundle | Google Play |
| Google Play Developer API | RAW Bundle purchase token, from our server | verify the purchase, detect refunds | Google Play |
| Firebase Crashlytics | crash reports as described in 3.1 | diagnostics | Google Play, direct APK |
| Google Analytics for Firebase | SDK-automatic events | stability and adoption metrics | Google Play, direct APK |
| Google Play In-App Review | your rating and review | collect reviews | Google Play |
| Huawei IAP / AGConnect | purchase and donation transaction | sell the app and RAW Bundle | AppGallery |
| HUAWEI Account Kit | your email address and HUAWEI ID identifier | sign in for RAW Bundle | AppGallery |
| HUAWEI IAP order service | RAW Bundle purchase token, from our server | verify the purchase, detect refunds | AppGallery |
| HUAWEI Analytics Kit | SDK-automatic events | stability metrics | AppGallery |
| Samsung IAP | purchase and donation transaction | sell the app and RAW Bundle | Galaxy Store |
| Samsung account sign-in | your email address and Samsung account ID | sign in for RAW Bundle | Galaxy Store |
| Samsung IAP receipt service | RAW Bundle purchase ID, from our server | verify the purchase, detect refunds | Galaxy Store |
| RuStore Pay | purchase and donation transaction | sell the app and RAW Bundle | RuStore |
| VK ID | your email address and VK ID identifier | sign in for RAW Bundle | RuStore |
| RuStore Public API | RAW Bundle invoice ID, from our server | verify the purchase, detect refunds | RuStore |
Provider policies: Google Play Services and Firebase — policies.google.com/privacy and firebase.google.com/support/privacy; Huawei — consumer.huawei.com/en/privacy; Samsung — account.samsung.com privacy notice; RuStore — rustore.ru privacy policy; VK ID — id.vk.ru privacy policy.
5. Where the data goes
Diagnostics and statistics are processed on the provider's own infrastructure, under the provider's own safeguards for transfers outside the European Economic Area. We keep no copy of them. Our own licence server, api.mcpro24fps.com, is hosted in the European Union; the app contacts it only for RAW Bundle (§3.11), and your email address, purchase records, installation IDs and the verification log are stored there. It is shared with our photo application mcpro35mm, but a licence for one app does not unlock the other.
6. How long data is kept
For RAW Bundle (§3.11): your email address, account identifier and trial dates — until you ask us to delete them, or 3 years after the last request from the app, whichever comes first; the free-trial marker (a keyed hash of the address, see §3.11) — for as long as we offer the RAW Bundle free trial, because its only purpose is one free trial per address; purchase records — anonymised on your deletion request, then kept as pseudonymous accounting records for the statutory period (5 years under the Latvian Law on Accounting) and deleted automatically; installation IDs — for as long as the purchase they belong to; the verification log — while it is needed for support and abuse investigation, and deleted on request together with the rest of your data.
Without RAW Bundle we create no records of our own for this app. In the providers' consoles the providers' default retention applies — for Firebase Analytics, event-level data is kept for the default retention period configured in the console; crash reports are kept under Google's own schedule for Crashlytics. Aggregated figures that identify nobody — crash-free rate, app versions, device models — may be kept longer as engineering history.
7. Your rights
Under the GDPR you may request access to your personal data, its correction or erasure, restriction of processing, portability, and you may object to processing based on legitimate interest. You may also complain to the Latvian supervisory authority, Datu valsts inspekcija (dvi.gov.lv), or to the authority of your own country.
To see, correct, export or delete the RAW Bundle account data held on our server (§3.11), write to info@mcpro24fps.com from the email address you signed in with; we answer within 30 days. Signing out in the app removes the email address from your device but not from our server — ask us for that. How deletion works, and what happens to a RAW Bundle purchase, is explained on the page Account and Data Deletion — mcpro24fps (/account-deletion-mcpro24fps).
One practical caveat, stated plainly: diagnostics are not tied to your account, so a diagnostic report normally cannot be linked to a person at all — not by us and not by the provider. If you want a specific report removed, send us the date and time, your device model and the app version, and we will find and delete what can be identified. You can reset the SDK's installation identifier yourself by clearing the app's data, and you can avoid diagnostics entirely by using a build that ships without the crash SDK (§3.1).
8. Children
The app is a professional camera tool and is not directed at children under 13. We do not knowingly collect personal data from children under 13. If you believe a child has sent us personal data, write to us and we will delete it.
9. Security
All traffic leaves the device over TLS. We store no passwords: sign-in happens at the store's account provider. Our licence server keeps only what §3.11 lists, and its answers are signed so that the app can tell a genuine answer from a forged one. Payment instruments stay with the store operator.
10. Changes to this policy
Changes are published on this page with a new “last updated” date. Anything material is also mentioned in the app's release notes.
11. Contact
CHANTAL PRO SIA, registration number 40103332030, Bebru iela 16–34, Jēkabpils, Jēkabpils nov., LV-5201, Latvia · info@mcpro24fps.com