Legal

Privacy Policy

This Privacy Policy explains what information the JCLiveCut Android app handles, and — just as importantly — what it does not collect. JCLiveCut is a screen recorder. Your recordings stay on your device unless you explicitly upload them to your own Google Drive.

Effective date: May 12, 2026
Last updated: May 12, 2026

1. Who we are

The "App" refers to the JCLiveCut Android application (package name com.clavelyapps.jclivecut), published by ClavelyApps ("we", "us", "our").

For any privacy question or request, contact us at support@jclivecut.app.

2. Scope of this policy

This policy applies to the JCLiveCut mobile application distributed through the Google Play Store. It does not apply to third-party services you may use through the App (Google Sign-In, Google Drive, Google Play Billing), which are governed by their own privacy policies.

3. What the App does

JCLiveCut is a screen-recording app. It captures the screen of your Android device, optionally with audio from your microphone, the system playback, or both. Recordings are saved to a local library on your device. You can preview, rename, organize them into folders, trim them, and either save them to your device gallery or upload them to your own Google Drive.

JCLiveCut does not have ads. It does not include any analytics, telemetry, or crash-reporting SDK. It does not share recordings with us or any third party.

4. What we do not collect

We do not collect, store, or transmit your recordings or their content. Recordings live on your device.

We do not run advertising SDKs, analytics SDKs (no Firebase Analytics, no Google Analytics, no Mixpanel, no Amplitude, no Segment), or crash-reporting SDKs (no Crashlytics, no Sentry).

We do not collect device advertising identifiers (no AD_ID usage).

We do not maintain a developer-owned backend that stores your data.

5. Information the App handles

The App handles the following limited categories of information:

5.1 Google account information (required)

Sign-in with Google is required to use the App. When you sign in, the App receives from Google an ID token containing your email address, and optionally your display name and profile picture URL. These values are stored locally on your device (in encrypted system credentials and in the App's private preferences) and are used to identify your account inside the App.

We do not send this account information to any developer-owned backend, because no such backend exists.

5.2 Your recordings (stored on device)

When you record, the App writes the video file (and any audio track you selected) to the App's private storage on your device. Metadata about each recording (file path, duration, file size, creation time, audio mode, capture quality, optional Drive upload status and Drive file ID) is stored in a local SQLite database (Room) inside the App's private storage.

When you choose "Save to Device", the recording is exported via the Android MediaStore to your public Movies folder so other apps can see it.

Recordings and their metadata are not transmitted to us. They remain on your device until you delete them, you uninstall the App, or you choose to upload them to your own Google Drive.

5.3 Subscription state (Google Play Billing)

The App offers an optional Pro plan (annual subscription with a 7-day free trial), processed through Google Play Billing. Google handles all payment data; we never see your card details.

The App stores locally the timestamp of your first qualifying purchase, used to compute trial expiration. Active purchase state is read from Google Play when the App starts.

5.4 Crash reports (via Google Play, opt-in by user)

If the App crashes, Google Play may collect a crash report from your device under your Play settings. These reports include technical details (device model, Android version, stack trace), are not linked to your identity, and are governed by Google's privacy policy. The App itself does not include any third-party crash-reporting SDK.

6. Permissions the App requests

Below is the complete list of permissions declared by the App and the exact reason each one is requested.

6.1 Microphone — android.permission.RECORD_AUDIO

Why we request it: this is the Android system permission required to capture audio. JCLiveCut uses it when you select "Microphone" or "Microphone + System" as the audio mode for a recording, and also when capturing system audio playback via MediaProjection on devices that route system audio through this permission.

When it is used: only while a recording is in progress and only with the audio mode you selected. The microphone is never accessed in the background. While recording, the Android microphone indicator is shown by the system.

Where the audio goes: the captured audio is encoded into the recording file inside the App's private storage on your device. It is not transmitted to our servers and is not shared with any third party. You can delete a recording at any time.

You can revoke this permission from the Android system settings: Settings → Apps → JCLiveCut → Permissions → Microphone. If the permission is denied, audio capture modes will be unavailable, but silent screen recording will continue to work.

6.2 Screen capture — MediaProjection (granted per session)

JCLiveCut captures the screen using the Android MediaProjection API. This is not a manifest permission — Android shows a system dialog every time you start a recording, and you must explicitly grant permission for that session. The system also shows a persistent recording indicator while capture is active.

JCLiveCut does not record the screen in the background and does not start recording without your explicit per-session approval.

6.3 System overlay — android.permission.SYSTEM_ALERT_WINDOW

Why we request it: when you choose "Region" capture, the App shows a draggable overlay on top of other apps so you can frame the part of the screen to record. The overlay is only visible while you are setting up a region recording.

You can revoke this permission from Settings → Apps → JCLiveCut → Display over other apps. Without it, full-screen recording still works; only region recording becomes unavailable.

6.4 Foreground services — FOREGROUND_SERVICE, FOREGROUND_SERVICE_MEDIA_PROJECTION, FOREGROUND_SERVICE_MICROPHONE, FOREGROUND_SERVICE_DATA_SYNC

These permissions allow the App to keep a recording or an upload running with a persistent notification while you are using other apps or the screen is off, as required by Android for media-projection, microphone, and background data-sync work.

6.5 Network — INTERNET, ACCESS_NETWORK_STATE

Used so the App can talk to Google Sign-In, Google Drive (only when you opt in to backup), and Google Play Billing. The App does not transmit your recordings over the network unless you explicitly request a Drive upload.

6.6 Legacy storage — READ_EXTERNAL_STORAGE (Android 12 and below), WRITE_EXTERNAL_STORAGE (Android 9 and below)

Required to read and write media on older Android versions that predate scoped storage. On Android 10+ the App uses MediaStore APIs, which do not require these permissions.

6.7 Background — WAKE_LOCK

Holds a partial wake lock while a recording is in progress so the CPU does not sleep mid-recording. Released as soon as recording stops.

6.8 Notifications — POST_NOTIFICATIONS

Required on Android 13+ to show the persistent recording notification and upload progress notifications. You can deny or revoke this permission at any time; it does not affect recording or upload functionality, only their visibility.

Sign-in is mandatory to use the App. JCLiveCut uses the Android Credential Manager and Google Identity Services. The Web OAuth client ID configured in the App is used only as the audience of the ID token returned by Google.

The App does not request any Google API scope at sign-in beyond the basic profile and email. Drive scope is requested separately and only if you opt in to Drive backup (see next section).

You can sign out of the App at any time from inside the App; doing so removes locally cached credentials.

8. Optional Google Drive backup

Drive backup is opt-in. When you enable it, the App asks for the Google Drive scope DRIVE_FILE. This scope restricts the App's access to files that the App itself creates — it cannot read or modify any other file in your Drive.

When backup is enabled, recordings are uploaded directly from your device to your own Google Drive account. We do not receive a copy; we do not act as an intermediary. You can disable Drive backup at any time from the App settings, which stops further uploads (existing uploads in your Drive remain under your control).

9. Google Play Billing

The optional Pro Annual subscription (with a 7-day free trial) is processed by Google Play. Google Play returns a purchase token to the App, which the App uses to grant access to Pro features. The App stores locally the timestamp of your first qualifying purchase to compute trial expiration. We do not receive your payment card details.

11. Data retention

Recordings, their metadata, and your app preferences remain on your device until you delete them, uninstall the App, or clear the App's data from Android settings.

Files you uploaded to your own Google Drive remain there until you delete them from Drive.

Active subscription state is held by Google Play; ending or cancelling a subscription is done through your Google Play account.

12. Your rights

Depending on where you live (for example, the EU under GDPR, the UK under UK-GDPR, California under CCPA/CPRA, Brazil under LGPD), you may have rights to access, correct, delete, restrict, or port your personal information, and to object to certain processing.

Because we do not maintain a developer-owned backend that holds your personal data, the most direct way to exercise deletion is to delete your recordings inside the App, sign out, and uninstall the App. Local data is removed when you uninstall.

To exercise other rights, or for any privacy question, contact us at support@jclivecut.app.

13. Security

Recordings and the App's local database are stored inside the App's private sandbox, accessible only to the App. Communication with Google services is performed over HTTPS. The App's manifest declares android:allowBackup="false", which excludes App data from the system's automatic backup. No security measure is perfect, but we follow current Android platform best practices.

14. Children

JCLiveCut is not directed to children under 13 and does not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, contact us at support@jclivecut.app so we can delete it.

15. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we update the "Last updated" date at the top of this page. Material changes are highlighted in the App or on this page.

16. Contact

For any question about this policy or about how the App handles your data, contact us at support@jclivecut.app.