Privacy Policy
DuoCam — published on Google Play as DuoCam: Dual Camera Recorder, package app.filmode.duocam — is a dual camera recorder for Android published by FightTech VN. In short: your videos and photos are recorded and saved on your phone, they are never uploaded, and there is no account. The app sends usage counts and crash reports, plus anonymous daily counts of which film looks are used to our own server, all of which you can switch off in Settings. The free version shows ads from Google AdMob, which uses your device's advertising ID subject to your consent choices; DuoCam Pro removes the ads. We do not sell your data.
What the app does
DuoCam shows your phone's front and back cameras at the same time and records both into one video file, in a picture-in-picture or split layout, with an optional film look. It can also take a dual photo with both cameras in one JPEG, and show a scrolling teleprompter script on screen while you record. On phones that cannot run two cameras at once, it records with one camera. All recording and composing happens on the phone. Nothing you film is sent to us, to Google or to anyone else.
Permissions the app declares
These are the permissions in the app's final manifest, including the ones added by Google's and the ad network's libraries. Android asks you for the runtime ones (camera, microphone and, on old Android versions, storage) when each is first needed, and you can revoke them later in Settings → Apps → DuoCam → Permissions.
- Camera (
CAMERA) — DuoCam is a camera, so it asks for this when it first opens. The camera pictures are shown on screen and written into the videos and photos you take. They are never streamed or uploaded. - Microphone (
RECORD_AUDIO) — used only to record sound into a video. The sound is written into your video file on the phone and never transmitted. Deny it, or turn the microphone off on the record screen, and videos record without sound. - Storage, on Android 9 and older only (
WRITE_EXTERNAL_STORAGE, declared withmaxSdkVersion="28") — to save videos and photos into the sharedMovies/DuoCamandPictures/DuoCamfolders. On Android 10 and newer the app saves through the system MediaStore and does not request this permission. - Internet and network state (
INTERNET,ACCESS_NETWORK_STATE) — used to load ads in the free version, to send usage and crash reports, to send the anonymous daily look counts to our server, to send a Contact us message when you tap Send, and by Google Play Billing for purchases. Network state lets the app and its libraries check whether the phone is online first. Neither is a runtime permission. - Advertising ID (
com.google.android.gms.permission.AD_ID) — added by the Google Mobile Ads SDK. It lets the ads in the free version read your device's resettable advertising ID, used for ad delivery, frequency capping, measurement and, where you consent, personalised ads. You can reset or delete the advertising ID in Android's Settings → Google → Ads (or Settings → Privacy → Ads). - Android Ad Services (
ACCESS_ADSERVICES_AD_ID,ACCESS_ADSERVICES_ATTRIBUTION,ACCESS_ADSERVICES_TOPICS) — added by the Google Mobile Ads SDK so that, on Android versions that have the Privacy Sandbox, ads can use Android's on-device ad ID, attribution and topics APIs instead of cross-app identifiers. Android lets you control these under Settings → Security & privacy → Privacy → Ads. - Google Play billing (
com.android.vending.BILLING) — added by Google's Play Billing library for the optional DuoCam Pro purchase. - Keep awake (
WAKE_LOCK) — added by the Firebase and ad SDKs so that a report or ad request already in progress can finish if the screen turns off. - Install referrer (
com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE) — lets the analytics and ads SDKs read once which Google Play listing or campaign the app was installed from, for aggregate install counts and ad attribution. - Foreground service (
FOREGROUND_SERVICE) — declared by the ad SDKs for their own internal work. DuoCam does not record in the background: leaving the app stops the recording.
No GPS location, no gallery browsing. The app declares no location permission and writes no location into your files. In the free version, the ad networks below may estimate an approximate location (city or region) from your IP address to choose and measure ads; DuoCam itself never reads it. It does not request access to read your whole gallery; it shows only the videos and photos it recorded itself. It declares no contacts, phone, calendar, SMS or "all files access" permission.
The camera and microphone are used only while the camera screen is open, to show the preview and to record. Nothing they capture is uploaded.
Your videos and photos
Videos are saved as MP4 files to Movies/DuoCam and dual photos as JPEG files to Pictures/DuoCam in your phone's shared storage, through Android's MediaStore, where your gallery and other apps can see them. They are yours: the app never uploads, copies or shares them. Sharing happens only when you tap Share and pick an app in Android's share sheet.
So the in-app gallery can list what DuoCam recorded, the app keeps a small index in its private preferences: for each item, its MediaStore link, whether it is a video or a photo, the date, the length, the file size, the layout and the picture size. It holds the most recent 500 items. This index is never uploaded by the app; see Android backup for how Android treats it. Teleprompter scripts, favourite looks and your settings (layout, format, picture-in-picture position) are also kept in the app's private storage on the phone and are never sent anywhere.
Deleting an item in the in-app gallery deletes the file from your phone after you confirm. Uninstalling DuoCam does not delete the videos and photos in Movies/DuoCam and Pictures/DuoCam.
Analytics and crash reporting
The app uses Google Analytics for Firebase and Firebase Crashlytics, both provided by Google, to learn which features are used and to fix crashes. Both are on by default, and both stop collecting when you switch off Settings → Share usage and crash reports; the choice is remembered across launches. The same switch also stops the look counts.
- Usage counts — the events listed below, plus what the Firebase SDK records by itself: first open, sessions and their length, the screen shown, the app version, the phone model, Android version, language and country, and a random app-instance ID that Firebase creates on install. Google Analytics also records completed Google Play purchases automatically, with product ID, price and currency. Country is derived by Google from the connection; Google Analytics does not log or store IP addresses.
- Crash reports — when the app crashes or hits an error it recovers from, the stack trace, the phone model, Android version, free memory and disk space, orientation, a random Crashlytics installation ID, and the recent app events that led up to it.
Labels on every report. Usage counts carry the user properties app_variant = duocam, is_pro (true or false) and ads_network (which ad network served the free version). Crash reports carry the custom keys app = duocam, screen (the screen that was open) and where (the part of the app where the error happened), so DuoCam can be told apart from our other apps in the same Firebase project.
What is never sent: your videos, photos or any frame of them, the camera pictures, sound, teleprompter script text, file names, your precise location, your name, email or any account identifier.
This data is processed by Google on our behalf, under the Firebase privacy and security terms. We use it only to improve the app, never combine it with other data to identify you, and never sell it.
Every event the app sends
This is the complete list of DuoCam's own analytics events and the values each one carries. None of them includes the content of what you record.
Recording and photos
| Event | When | Values |
|---|---|---|
record_start | A recording starts | layout, quality, fps, orientation, cameras (one or two), codec, audio (on or off) |
record_stop | A recording ends | duration_s, size_mb, ok (whether it was saved), layout |
export | A video or photo is written to your storage | format (mp4 or jpg), duration_s |
photo_capture | You take a photo | layout, cameras, ok |
timelapse_start | A time-lapse recording starts | none |
dual_unsupported | The phone cannot run both cameras at once | reason, model (the phone model) |
Layout and features
| Event | When | Values |
|---|---|---|
layout_change | You change the layout, also while recording | layout (new), from (previous), recording (whether a recording was running) |
pip_move | You move or resize the picture-in-picture window | corner, size, pinch (whether it was resized) |
swap_cameras | You swap the cameras, also while recording | mode (dual or single), recording |
teleprompter_open | You open the teleprompter | scripts (how many scripts you have, a count only) |
feature_use | You use a control | feature: one of torch, tap_focus, ae_af_lock (a long-press that holds focus and exposure), exposure (the exposure slider; its EV value), pip_shape, pip_border, mirror_front, a format setting, timer, grid, mic, script_add, script_delete, teleprompter, delete, open_in_photos, analytics, import_inset and import_remove (a clip or photo from your gallery used as the inset; only its kind, never the file), volume_shutter, shortcut (a home-screen shortcut), review_flow, rate_store, contact_mailto, or a Settings row (restore, manage, share_app, rate, help, privacy, terms, ad_privacy, whats_new); plus where it applies state, count, kind, on, ok, from, camera or in_app (the setting chosen, front or back camera, a number of items, the kind of item, on/off, whether it worked, where it was opened from, whether Google Play showed its review card) |
onboarding_step | You move through the first-run introduction | step, via (button or swipe), page |
share | You share a video or photo | kind (video or photo), layout — not the file or the app you shared to |
rating_prompt | You answer the app's "Enjoying DuoCam?" card | choice (yes, no or later), from, saves (how many items you have saved) |
settings_change | You change a setting | key (which setting, for example theme or language), state (the option chosen) |
whats_new | The "What's new" card is shown or closed | action (shown or dismissed), version (the app version) |
contact_opened | You open the contact form | from (the screen you opened it from) |
contact_sent | You send the contact form | ok, paid (whether you have Pro), topic, screenshot (whether one was attached), from — never the message itself |
thermal | The phone gets hot enough that the app warns you or stops a recording | level (warn, stop, or ok once it cools), status (Android's thermal status) |
record_recovered | A recording cut short by a crash is found on the next start | kept (whether the clip could be kept), duration_s |
Screens
screen_view, with the screen's name: camera, camera_permission, contact, dual_unsupported, format, gallery, licences, paywall, pip_style, settings, teleprompter or viewer.
DuoCam Pro
| Event | When | Values |
|---|---|---|
pro_gate | You tap a Pro feature without Pro | source, detail (the feature) |
paywall_open | The Pro screen is shown | source, detail, type (promo, none or no_plans) |
paywall_dismiss | You close the Pro screen | source, seconds it was open, product_id, offer_id |
paywall_plan_select | You pick a plan | product_id, offer_id, source |
purchase_start | You start a purchase | product_id, offer_id, source |
purchase | A purchase completes | product_id, offer_id, source |
purchase_cancel | You cancel the Google Play purchase sheet | product_id, offer_id, source |
purchase_fail | A purchase cannot complete | reason: billing_unavailable, a Google Play error code, or bad_signature |
purchase_restore | You restore purchases | state (the result) |
purchase_pending | A purchase waits for payment | product_id, source |
pro_state | Pro turns on or off after the app checks with Google Play | state (gained or lost), is_pro, product_id |
Ads (free version)
| Event | When | Values |
|---|---|---|
ad_init | The ads SDK starts | ok, reason (why it did not start, if so) |
ad_consent | The consent step finishes | enabled (whether ads may be requested) |
ad_shown, ad_load_fail, ad_clicked, ad_dismiss | An ad is shown, fails to load, is tapped or is closed | format (banner or interstitial), network, placement |
ad_break | The app reaches a point where a full-screen ad may show | placement |
ad_impression_value | An ad earns revenue | the estimated ad revenue value and currency reported by AdMob |
Error reports
Crashlytics non-fatal reports, each carrying only the error and where it happened, under these keys: clip_insert, clip_provider, clip_publish (a video or photo could not be added to or released in your storage), gallery_delete, gallery_delete_confirm, photo_save, purchase_signature (a purchase could not be verified), record_refused, record_start, self_test, viewer_open, viewer_play and viewer_share.
Favourites and look popularity counts
You can long-press a film look in the look sheet to keep it in the Favourites row. The favourites list is kept in the app's private storage on your phone and is never sent anywhere.
So that we can tell which looks people actually use, the app also keeps an anonymous count for each day: which built-in looks you picked that day, and which you added to or removed from favourites. Each look is noted at most once a day, however often you use it.
Once a day is over, the app sends it in one HTTPS POST to our own server, https://fighttech.vn/api/v1/looks/usage (FightTech VN). If the phone is offline it tries again later, and several finished days may then travel in the same request, each with its own token; a day still unsent after 7 days is deleted from the phone. The request holds only:
- the app's package name and the date;
- a random token for that day, used only to refuse the same day if it is sent twice; the server stores only a hash of it and deletes that after 9 days;
- for each look, its built-in ID (for example
vint-neg-1) and whether you picked, favourited or unfavourited it.
It holds no installation ID, advertising ID, account, device model, video, photo, file name or location, so two days cannot be linked to each other or to your phone. The server keeps only totals: for each app, day and look, how many installs picked, favourited or unfavourited it. These totals are kept for 400 days, then deleted.
This endpoint stores nothing about the request itself: not your IP address, which, like any web request, the network and the server see while it is handled, and not the standard header Android adds to web requests, which names the Android version and phone model. The totals are visible only to FightTech VN, in an internal report that hides any look used by fewer than 5 installs. They are never sold or shared.
The counts stop when you switch off Settings → Share usage and crash reports, the same switch as the analytics. Switching it off also deletes the days not yet sent.
Data we collect
Only the usage counts and crash reports described above, which we see as totals and individual crash reports in the Firebase console, the anonymous look totals on our own server, and aggregate ad reports from AdMob. We — FightTech VN — hold no database of users, and we never see your videos, photos, scripts or settings. There is no account system and no newsletter. If you email us or use the in-app contact form, we receive what you choose to write, and use it only to answer you.
The in-app contact form
Settings → Contact us opens a form. Nothing is sent until you tap Send. When you do, the app sends over HTTPS to our support server at fighttech.vn:
- the topic you picked and your message (10 to 4000 characters);
- your email address, only if you type one, so we can reply;
- a screenshot, only if you attach one (scaled down to 700 KB at most);
- app and device details: app version, phone maker and model, Android version, language, time zone, screen size, dark mode, memory, which store installed the app, and camera support (how many cameras the phone has, whether it can run two at once, the last camera error);
- if you have Pro: the plan and the Google Play order number, so we can find your purchase.
The form shows a short summary of this before you send. It sends no videos, photos, scripts, advertising ID or location. We use messages only to answer you and fix the problems you report, and keep them for up to 12 months after the conversation ends, then delete them. To have yours deleted sooner, email us (see Contact). If sending fails, the app offers to try again or to open your email app instead.
Purchases
DuoCam Pro is sold as a monthly or annual subscription or a one-time lifetime purchase through Google Play Billing. Google processes the payment under the Google Privacy Policy; your card details and billing address are never given to us or to the app. Google Play Console shows us the order record for each purchase (order ID, product, date, price and country), which we use only for refunds, tax and support. The app verifies the purchase on your phone against Google's signature and remembers the result locally.
Third parties and ads
We do not sell your data. These companies process data on behalf of, or alongside, the app:
- Google AdMob (Google Mobile Ads SDK) — shows ads in the free version: a banner in the gallery and settings screens, and occasionally a full-screen ad between actions. A full-screen ad never appears while you are recording or during the countdown. To serve and measure ads, the SDK collects device information, IP address and the approximate location derived from it, the advertising ID and ad interactions, under How Google uses information from sites or apps that use its services.
- Unity Ads — an ad network AdMob may use through mediation to fill an ad slot. When it does, Unity receives similar device and ad-interaction data under the Unity privacy policy.
- Google User Messaging Platform (UMP) — if you are in the European Economic Area, the UK or another region where consent is required, DuoCam shows Google's consent form before ads are requested. You can change your choice at any time under Settings → Privacy options. Settings → Remove ads opens DuoCam Pro, which turns ads off completely.
- Firebase Analytics and Firebase Crashlytics (Google) — usage counts and crash reports, as our processor, as described above. Switch them off under Settings → Share usage and crash reports.
- FightTech VN (us) — our own server at
fighttech.vnreceives the messages you send from the contact form and the anonymous daily look counts. - Google Play Billing — purchases, as described above.
No ad network or analytics service ever receives your videos, photos, sound or teleprompter scripts. With DuoCam Pro no ads are requested and the ad SDK makes no ad requests.
Android backup
If you use Android's backup or move to a new phone with Android's transfer tool, Android may include DuoCam's private preferences — your settings, teleprompter scripts and the gallery index — in a backup stored in your Google account or copied to your new phone. That is done by Android and Google under your account and its settings; we have no access to it. The app's on-device history folder and thumbnails are excluded from backup and transfer, and a restored gallery index only lists items whose files are present on the new phone. Your videos and photos in Movies/DuoCam and Pictures/DuoCam are backed up, or not, like any other media on your phone.
Data retention and deletion
Your settings, scripts and gallery index live on your device and are removed when you uninstall the app or clear its storage. Videos and photos you recorded stay in Movies/DuoCam and Pictures/DuoCam until you delete them.
Google Analytics keeps user-level event data for the retention period set in our project, at most 14 months, after which only aggregated totals remain. Firebase Crashlytics keeps crash reports for 90 days. AdMob and Unity Ads keep ad data under their own policies linked above. Google Play keeps purchase records under the Google Privacy Policy. Clearing the app's data or reinstalling it creates a new random app-instance ID, so earlier reports can no longer be linked to your phone. Look counts not yet sent stay on the phone for at most 7 days; on our server, the per-day look totals are kept for 400 days, then deleted.
To delete your DuoCam data:
- In DuoCam, open Settings and switch off Share usage and crash reports, so nothing new is sent. This also stops the look counts and deletes the days not yet sent.
- To delete videos or photos, delete them in the DuoCam gallery or in your phone's gallery app (folders
Movies/DuoCamandPictures/DuoCam). Skip this step to keep them. - Uninstall DuoCam, or clear its storage in Android's Settings → Apps → DuoCam → Storage → Clear storage. This deletes your settings, scripts and gallery index, and resets the app-instance ID.
- To reset the advertising ID used by ads, open Android's Settings → Google → Ads (or Settings → Privacy → Ads) and reset or delete it.
- To have the usage counts and crash reports already sent deleted, email trunghieu4121993@gmail.com with the subject "DuoCam data deletion". We will delete them from Firebase within 30 days and reply to confirm. Otherwise they are removed automatically after the retention periods above. Look counts already sent are anonymous totals that cannot be traced back to you, so they cannot be deleted for one person.
To cancel a subscription, open the Google Play app → Payments & subscriptions → Subscriptions.
Security
Your settings, scripts and gallery index sit in the app's private storage, which Android keeps out of reach of other apps. Reports to Firebase, look counts, contact messages and ad requests are sent over HTTPS. Purchases are verified with Google's signature on the device. No system is perfectly secure, but because your videos never leave your phone, there is no copy of them on any server of ours.
Children
The app is not directed at children under 13 and does not knowingly collect personal information from children. Ads are not personalised for users the ad SDK identifies as children.
Your responsibility
DuoCam records two cameras at once, including whoever is in front of the selfie camera. You are responsible for what you record and share, including the consent of the people you record and the laws of the place you record in.
Changes to this policy
If the app's data practices change, this page will be updated and the date above revised before the new version is released. A new permission, event or SDK will be listed here first. The October 31, 2026 update adds favourite looks and the anonymous daily look counts, and corrects the name of the usage switch.
Contact
FightTech VN, Vietnam. Questions about this policy, or a request about your data? Email trunghieu4121993@gmail.com.