Privacy Policy
Version 1.3 · Effective 12 August 2026 · Last updated 9 September 2026
The short version. ProCut edits video on your device. Your clips are not uploaded, we do not require an account, we do not track you across other apps, and we do not sell personal data. Two things do leave the device: anonymous usage and crash diagnostics, which you can switch off in the Me tab; and one reward video you have to tap to play, served without personalisation. This policy explains exactly what each of them sends.
1. Who we are
ProCut is developed and published by FightTech ("we", "us"). For the purposes of the EU and UK General Data Protection Regulation, FightTech is the data controller for the limited personal data described below.
Postal address and company registration details are listed in section 16.
2. What this policy covers
This policy covers the ProCut mobile and desktop applications for Android, iOS, iPadOS, macOS and Windows, and the ProCut website at procut.filmode.app.
It does not cover the app stores themselves. When you download ProCut or buy a subscription, Apple or Google acts as the merchant and applies its own privacy policy to that transaction.
3. What we collect — and what we don't
3.1 Your video, photos and audio
Media you import stays on your device. Import, preview, effects, transitions, text rendering and export all run locally through your device's own hardware codecs. ProCut does not upload your media, does not scan it, and does not send thumbnails, frames or audio anywhere — not for ordinary editing, and not for the diagnostics described in 3.4. You can verify this by putting the device in airplane mode: the editor keeps working, end to end, including 4K export.
3.2 Your projects
Project files (the list of clips, cuts, effects and settings) are stored in the app's private storage on your device. They are removed when you delete the project or uninstall the app.
3.3 What we do not collect
- No account, name, email address or phone number is required to use ProCut.
- No tracking of you across other apps or websites. ProCut does show one opt-in reward video (see 3.5), but it is served without personalisation, so the app never joins a cross-app advertising profile and never asks for App Tracking Transparency permission.
- No contacts, calendar, location or health data.
- No copy of your media, your captions or your project names. Analytics events describe the shape of your work — how many clips, how long the timeline is, which transition you picked — never its content. Project names are reduced to an eight-character hash before they leave the device, and text events carry a character count instead of the text.
3.4 Usage and crash diagnostics
ProCut includes Google Firebase Analytics and Firebase Crashlytics so we can see which features people actually use and get a stack trace when the app crashes. This is the only reason ProCut opens a network connection during ordinary editing.
You can turn it off. Open the Me tab and switch off Share anonymous usage and crash data. Collection stops immediately and nothing further is sent. Everything else in the app keeps working exactly the same — the editor has never needed the network.
When it is on, we receive: the name of the feature you used and its numeric parameters (clip counts, durations in seconds, export resolution, catalog IDs of the filters and transitions you chose), your device model, OS version, language, app version, a coarse device tier (low/mid/high), and crash stack traces. Firebase also assigns a random app-instance identifier so repeat sessions can be counted as one device; it is not your advertising ID, it is not linked to any account, and it is destroyed when you uninstall the app.
3.5 The reward video
ProCut has no banners and no pop-up ads. There is exactly one ad in the app: a reward video you can tap on the store screen to unlock every Pro filter for 24 hours, capped at five a day. It never plays on its own, never interrupts editing or export, and is not offered at all to Pro or Lifetime customers — on those devices the ad SDK is never even started. It is not present in the macOS desktop build.
The videos are served by Unity Ads (Unity Technologies). When you tap the card, Unity receives your device's advertising ID, device model, OS version and coarse country so it can pick a video, count the view and stop you being shown the same clip over and over. ProCut sets Unity's non-behavioural flag on every request, which means ads are chosen from the context alone: your ad ID is not used to build an interest profile, and nothing about your projects, media or usage of ProCut is sent to Unity.
How to switch it off. Simply never tap the card — no ad ever loads. You can also reset or delete your advertising ID in your device settings (Android: Settings → Google → Ads; iOS: Settings → Privacy & Security → Tracking), or remove the ad entirely by buying any paid tier. Unity's own privacy policy is at unity.com/legal/game-player-and-app-user-privacy-policy.
The table below is the same information we declare in the Google Play Data safety form and Apple's App Privacy questionnaire. If the two ever disagree, treat the store declaration as the one we are bound by and please tell us so we can fix the mismatch.
| Data | Collected? | Why | Leaves device? |
|---|---|---|---|
| Photos and videos | Used on device | To edit them | No |
| Audio you import | Used on device | Music and sound in your project | No |
| Project files | Stored on device | To reopen your work | No |
| Purchase status | Yes | To unlock what you paid for | Handled by Apple / Google |
| Crash diagnostics | Yes, unless you switch it off | To fix crashes | Yes — to Firebase Crashlytics |
| Feature usage counts | Yes, unless you switch it off | To see what to improve | Yes — to Firebase Analytics |
| App-instance identifier | Yes, unless you switch it off | To count devices, not people | Yes — to Firebase Analytics |
| Support emails | Yes, if you write to us | To answer you | Yes, to our mail provider |
| Advertising ID | Only if you tap the reward video | To serve and frequency-cap that one video | Yes — to Unity Ads, non-personalised |
| Location | No | — | — |
| Contacts | No | — | — |
4. Device permissions
ProCut asks for very little, and only at the moment a feature needs it. The app stays usable if you decline — you lose that one step, not the editor. This is the complete list; there is nothing else behind it.
4.1 iPhone and iPad
| Permission | Asked when | Used for |
|---|---|---|
| Add to Photos | You tap Save Video on the share sheet after an export | Writing that one finished video into your photo library. This is add-only — ProCut cannot read your library with it. |
| Speech recognition | You start auto-captions | Reading the speech in your own clips to write caption text. Recognition runs on the device; see section 5. |
ProCut does not ask for the camera, the microphone, read access to your photo library, or notifications, because it does not use them. Importing media goes through the system photo picker, which runs outside the app and hands back only the clips you tapped — no permission is involved, and no prompt appears.
4.2 Android
| Permission | Asked when | Used for |
|---|---|---|
| Storage (write) — Android 7–9 only | You save an export, on Android 7, 8 or 9 | Putting the finished video somewhere your Gallery can find it. Decline and the export still happens — the file just stays in the app's own folder, where uninstalling loses it. |
That is the only permission prompt ProCut shows on Android, and only on those older releases. On Android 10 and later the same save needs no permission at all, so nothing is asked. Importing media uses the system photo picker; auto-captions run on the device. Neither needs a permission.
The Play listing also shows permissions that are granted at install time and never prompt you: internet and network state (for the crash and usage reporting you can switch off, and for the opt-in reward video), advertising ID (frequency capping for that video — see 3.5), and a handful — wake lock, boot completed, foreground service, install referrer, Ad Services — that the Google and Unity libraries declare for their own scheduling. ProCut itself calls none of them.
You can revoke anything you granted at any time in your device's system settings.
5. AI features run on your device
Every AI feature in ProCut runs on your own hardware. There is no server-side AI, no queue, and nothing to upload — not optionally, not on request, not at all.
- Automatic captions — the speech in your clip is recognised by your phone's own speech engine, offline, and turned into ordinary text clips on the timeline. The audio never leaves the device and we never receive it.
- Background separation, beat detection, Ken Burns motion — the same rule: computed locally from media that is already on your device.
- No credits, no AI subscription. We do not sell credits or any pay-per-use AI. Because these features cost us nothing to run, they are free on every plan, with no usage limit.
- Language packs. Some on-device engines need a language model, which the app downloads once from the platform vendor when you first ask for that language. That download is a file coming down; nothing about your project goes up with it.
No media, no audio and no project data ever leaves your device. The whole app, AI included, works in airplane mode.
6. Purchases and subscriptions
All payments are processed by Apple or Google. We never see or store your card number, billing address or bank details. We receive only an anonymous receipt confirming that a purchase is valid, which is what unlocks paid features and lets you restore purchases on a new device.
7. If you contact support
When you email us we receive your email address, your message, and anything you choose to attach (for example a log file or a screen recording). We use it only to answer you. Please do not attach footage you are not comfortable sharing — we do not need your video to fix most problems.
8. Legal bases (EEA/UK)
| Processing | Legal basis |
|---|---|
| Validating a purchase | Performance of a contract (Art. 6(1)(b)) |
| Answering a support request | Legitimate interests (Art. 6(1)(f)) — supporting our users |
| Crash reports and feature-usage analytics | Legitimate interests (Art. 6(1)(f)) — app stability and deciding what to build next. The switch in the Me tab is how you exercise your right to object under Art. 21; we act on it immediately and ask for no reason. |
| Serving the reward video you tapped | Consent (Art. 6(1)(a)) — the tap is the consent, and there is no other way for the ad to load. Withdraw it by not tapping again. |
| Keeping records required by tax or consumer law | Legal obligation (Art. 6(1)(c)) |
9. How long we keep things
- Your media and projects — on your device, for as long as you keep them. We hold no copy.
- Usage analytics — retained by Firebase for 14 months, then deleted automatically.
- Crash reports — retained for 90 days.
- Reward-video ad requests — retained by Unity under its own policy; we receive only an aggregate count of views and revenue, with no per-device detail.
- Support correspondence — up to 24 months, then deleted.
- Purchase records — as long as accounting and tax law requires.
10. Who we share data with
We do not sell personal data, and we do not "share" it for cross-context behavioural advertising as those terms are defined under California law. We disclose data only to:
- Apple and Google, for app distribution and payment;
- Google Firebase (Analytics and Crashlytics), for the diagnostics described in 3.4 — unless you have switched them off;
- Unity Ads, and only at the moment you tap the reward video described in 3.5. Because we set the non-behavioural flag, this is a disclosure for serving a contextual ad, not a sale or a cross-context behavioural share;
- our email provider, to receive and answer your support messages;
- authorities, where we are legally required to and after checking that the request is valid and proportionate.
11. International transfers
Our processors may operate outside your country, including outside the EEA and the UK. Where that happens we rely on the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum, or an adequacy decision, as applicable.
12. Your rights and choices
Depending on where you live you may have the right to access, correct, delete, port, restrict or object to the processing of your personal data, and to withdraw consent. Because ProCut holds almost nothing about you, most requests are answered quickly.
- Delete everything locally — uninstalling the app removes your projects and its cache. See Delete my data for step-by-step instructions per platform.
- Ask us to delete server-side data — email [email protected]. We answer within 30 days.
- Complain — you may lodge a complaint with your local data protection authority. We would appreciate the chance to fix it first.
We do not charge for these requests and we do not discriminate against you for making one.
13. Children's privacy
ProCut is not directed at children under 13 (or under 16 where local law sets a higher age), and we do not knowingly collect personal data from them. The app is rated accordingly on both stores. If you believe a child has provided us with personal data, contact us and we will delete it.
14. Security
The diagnostics and ad requests described above travel over TLS. Project files sit in the app's private, sandboxed storage, protected by your device's own encryption. No system is perfectly secure, but keeping editing and AI local means there is very little about you for anyone to breach in the first place.
15. Changes to this policy
If we make a material change we will update the date at the top, and — for anything that meaningfully changes what leaves your device — show a notice in the app before the change takes effect. Previous versions are available on request.
16. Contact us
Privacy enquiries: [email protected]
General support: [email protected]
Postal: FightTech — [registered address]
We aim to reply within 5 working days, and within 30 days for formal data rights requests.