Privacy Policy

Effective date: September 6, 2026 · Last revised for version 1.0.1

FilCam — published on Google Play as FilCam: Pro Manual RAW Camera, package app.filmode.filcam — is a manual camera app for Android published by FightTech. This policy describes exactly what the app accesses on your device and what leaves it. In short: your photos are captured, processed and stored on your phone, they are never uploaded, and there is no account. From version 1.0.1 the app does send anonymous usage and crash reports, so that a camera that fails on your phone can be fixed for your phone; the section below lists exactly what those contain, and one switch in Settings turns them off. We do not sell any data.

What the app does

The app operates your phone's camera, applies the settings and film look you choose, and writes the resulting image file to your own storage. Everything — exposure, colour, LUTs, RAW conversion and the built-in photo editor — runs on your device's own CPU and GPU. There is no cloud processing of your images, no user account and no sign-in. The only thing the app ever sends over the network is the anonymous usage and crash reporting described below — never an image, and never any part of one.

Permissions the app declares

These are the only permissions in the app's manifest. Android asks you for the first three at the moment each is first needed, and you can revoke any of those later in Settings → Apps → FilCam → Permissions; the last group is granted at install time and is what the reporting switch controls.

Camera (CAMERA) — required. It is what runs the viewfinder and takes the photo. Without it the app cannot function. The camera feed is rendered on screen and written to the file you capture; it is never streamed anywhere.
Location, optional (ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION) — used for one purpose only: writing GPS coordinates into the EXIF metadata of the photos you take, on the device. It is requested only if you switch on Save location in photos in the app's settings, which is off by default. The coordinates are stored inside your own image files and are not transmitted to us or to any third party. Leave the setting off and the app never asks for the permission and never reads your location. GPS hardware is declared as optional, so the app installs on phones without it.
Storage, on older Android only (WRITE_EXTERNAL_STORAGE, declared with maxSdkVersion="28") — needed on Android 9 and earlier to save your photos into the shared Pictures library. On Android 10 and newer the app writes through the system MediaStore and this permission is neither declared nor requested. The app does not ask for broad access to read your existing photo library.
Network (INTERNET, ACCESS_NETWORK_STATE, WAKE_LOCK) — these are not permissions Android asks you about; they are granted at install time, and they come from the reporting libraries described in the next section. They are used to deliver a usage or crash report, and to notice whether the phone is online before trying. The same libraries add one Play Store permission, com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE, which lets Google Play tell the app which listing the install came from. Nothing else in the app uses the network: there is no update check, no ad request, no remote configuration and no upload of anything you shot.

The app declares no contacts, microphone, phone, calendar, SMS or background-location permission, and no "all files access". It also declares no advertising permission: AD_ID and the Android Ad Services permissions are explicitly removed from the build, so the app cannot read your advertising identifier.

Your photos and where they go

Photos are written into a folder inside your device's public Pictures directory — Pictures/Filmode by default, or whichever folder name you set — and registered with your media library so Gallery and other apps can see them. You choose the file format (JPEG, HEIF or PNG, plus RAW DNG on devices that support it), the quality and the filename pattern. Photos you take belong to you and stay on your device until you move or delete them; uninstalling the app does not delete them.

The image files carry standard EXIF metadata written by the app — exposure time, ISO, aperture, focal length, white balance, orientation, the date and time from your device, and GPS coordinates if and only if you enabled geotagging. That metadata travels inside the file, so bear it in mind before sharing a photo publicly. It is written locally; we never see it.

Analytics and crash reporting

From version 1.0.1 FilCam includes two Google libraries: Firebase Analytics (Google Analytics for Firebase) and Firebase Crashlytics. They exist for one reason. Manual camera control on Android depends on what each manufacturer exposes through the Camera2 API, and it differs from phone to phone; without a crash report we cannot know that RAW capture fails on some particular model, and cannot fix it.

What is sent.

Which features you used, as plain counters with no content — that a photo was captured, saved or shared, that a LUT or a preset was applied or imported, that a recipe was saved, that a long exposure was taken, and which of the two screens (camera, photo editor) you were on. Never the photo, never the file, never the name of the LUT file you imported.
Crash and error reports — the stack trace when the app crashes or when a camera operation fails (opening the camera, taking a picture, writing a DNG), the name of the operation that failed, and the recent in-app steps that led up to it. Reports are attributed to the app with an app key so we can tell FilCam's reports from our other apps'.
Device and app context collected automatically by those libraries: your phone's model and manufacturer, the Android version, the app version, the language and country setting, the screen size, and a randomly generated installation identifier that Google's SDK creates. That identifier is not your advertising ID — the app cannot read your advertising ID at all — and it is reset if you clear the app's data or reinstall.

What is never sent: your photographs or any part of one, thumbnails, file names, folder names, your GPS location or geotags, the location or contents of your imported LUT files, the contents of your media library, your advertising identifier, your name, your email or any account identifier. There is no account, so there is nothing to attach a report to a person by.

The switch. Open Settings in the app and turn off Send usage and crash reports. It is on when you install the app; switching it off stops collection in both libraries immediately, for as long as it stays off, and no further report leaves the device. Uninstalling the app has the same effect.

Who processes it. Google, as our processor, under the Firebase privacy documentation and Google's Privacy Policy. The data lands in our Firebase project and is visible only to us, in aggregate; we do not attempt to identify anyone from it, and we do not sell it, share it or use it for advertising. Retention follows Firebase's own settings: user-level analytics data is kept for 2 months, Google's default, which we have not extended, and Crashlytics reports are kept for 90 days.

No advertising. The app contains no ads and no ad SDK. The AD_ID permission is not declared, so the app cannot read your advertising identifier, and no data from the app is used for advertising or ad targeting.

Data we collect

We — FightTech — operate no server of our own for this app and hold no database of its users. What reaches us is only the anonymous usage and crash reporting described above, through Google's Firebase, and only while you leave that switch on. We never see your photos, your files or your location. There is no account system, no newsletter and no in-app purchase.

Data shared with third parties

The only third parties that receive anything are Google's Firebase Analytics and Crashlytics, acting as our processor for the reporting described above. No data is sold, and none of it is shared with anyone else or used for advertising or ad targeting. Nothing else leaves your device.

Data retention and deletion

All app data — your settings, imported LUTs, saved presets and recipes — lives on your device and is removed when you uninstall the app. Photos you have taken are yours and stay in Pictures until you delete them.

Usage reports are kept for 2 months and crash reports for 90 days, then deleted by Google automatically. Nothing else about you is retained anywhere: we run no server and hold no account, profile or database for FilCam.

How to request deletion of your FilCam data

Stop new reports. Open FilCam, go to Settings → Send usage and crash reports and switch it off. From that moment the app sends nothing.
Clear what is on your phone. Uninstalling FilCam — or Settings → Apps → FilCam → Storage → Clear data — removes every setting, preset and LUT the app has stored, and resets its random installation identifier, so any later report cannot be linked to an earlier one. Your photographs are not touched: they stay in Pictures until you delete them yourself.
Ask us to delete reports already sent. Email trunghieu4121993@gmail.com with the subject FilCam data deletion request. Tell us your phone model and roughly when you used the app; we hold no name, email or account that could otherwise point us to you. We reply within 30 days and have the matching Firebase Analytics and Crashlytics records deleted.

What gets deleted: the anonymous usage counters, crash and error reports, the device and app context sent with them, and the app's random installation identifier. What is kept: nothing about you — and, on your own phone, your photographs, which are yours and which we never receive. Anything not deleted on request expires by itself on the schedule above: 2 months for usage data, 90 days for crash reports.

Children

The app is not directed at children under 13 and does not knowingly collect personal information from children.

Your responsibility

You are responsible for the photographs you take and how you use them, including consent of the people you photograph and the law of the place you are shooting 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. If a future version adds a permission or an SDK, it will be listed here first. Revised on September 6, 2026 for version 1.0.1, which adds Firebase Analytics and Crashlytics, the network permissions they need, and the Send usage and crash reports switch that turns them off. Version 1.0.0 had none of these and no network access at all.

Contact

Questions about this policy, or a request about your data? Email trunghieu4121993@gmail.com.

← Back to FilCam · Terms · Support