Privacy Policy

1. Scope and developer contact

This Privacy Policy applies to LumaEdit: Photo Editor, Android package com.lumaedit.photoeditor (the “App”). In this policy, “we”, “our” and “developer” refer to the LumaEdit development team.

For privacy or support questions, contact easygamedevs@gmail.com.

This policy describes the data practices of the current App release. LumaEdit does not require an account and does not operate a proprietary cloud service.

2. Privacy summary

3. Photos and on-device editing

You decide which images LumaEdit can access. You may:

• select a photo or a batch of photos through the Android system picker; or
• use the optional camera action to capture a new image.

The App decodes image content on the device to provide crop, rotate, flip, resize, canvas, portrait retouch, local brushes, light and color adjustments, filters, text, compression and export functions. Image pixels are held in memory while you edit and are not uploaded to a developer server or provided to the advertising SDK.

When you select multiple photos for batch processing, the App applies your selected edit recipe locally to a maximum of 20 images in that batch.

4. Projects and preferences stored locally

If you export a creation, LumaEdit may retain a project copy so that you can reopen it from “My creations”. A project contains an original working image, an edited preview and a creation timestamp. Projects are saved inside Android’s private storage for the App and are not accessible to other apps under normal Android protections.

The project library keeps up to 12 recent projects. When this limit is exceeded, the oldest project files are removed automatically.

The App also stores small preferences locally, including your selected language, color palette, default JPEG quality, haptic preference, export count and frequency-control timestamps used to avoid excessive ads. These preferences are not sent to the developer.

5. Export, metadata removal and user-directed sharing

When you export, LumaEdit creates a new JPEG file from the edited pixels. The App does not copy source EXIF fields such as GPS coordinates, camera or phone model into the exported image. Android may still add ordinary file-system information such as the filename and creation date.

Exports are saved to Pictures/LumaEdit through Android’s media storage. They remain there until you delete them through a gallery or file manager, including after the App is uninstalled.

If you tap Share, Android displays its system share sheet. The edited image is sent only to the app or service you choose. That recipient handles the file under its own privacy policy. We do not receive a copy and do not control the selected third party.

6. Android permissions and system access

You can deny or revoke camera and legacy storage permissions in Android Settings. Denying the camera does not prevent you from selecting existing images. Some export behavior on older Android devices may require legacy storage permission.

7. Advertising, optional diagnostics and third-party services

LumaEdit does not collect, upload, sell or share your photo files with the developer. The current release includes the Google Mobile Ads SDK to show anchored banner, interstitial and App Open advertisements. It also includes Google's User Messaging Platform (UMP) to obtain and manage advertising privacy choices where required.

According to Google’s SDK disclosure, Google Mobile Ads may automatically collect and share the device’s IP address, which may be used to estimate general location; product interactions such as app launches, taps and ad or video views; diagnostic information such as crash and performance data; and device or account identifiers such as the Android advertising ID, app set ID and related identifiers. Google states that this data is used for advertising, analytics and fraud prevention, and is encrypted in transit using HTTPS.

Depending on your region, age eligibility, consent choices and Google’s configuration, ads may be personalized, non-personalized or limited. The App requests an updated consent status at launch and does not request ads until UMP reports that ad requests are permitted. When UMP requires ongoing access to privacy choices, an Advertising privacy choices action appears in LumaEdit settings.

For more information, review Google Mobile Ads SDK data disclosure and the Google Privacy Policy. Google Play and Android may also independently process store, installation, security or diagnostic information under their terms.

Optional Firebase Analytics

Firebase Analytics collection and analytics storage are disabled by default. You may enable or disable them at any time through Settings → Usage analytics. If enabled, LumaEdit records low-cardinality product events such as the current screen, import source category, selected editor tool or filter, export preset, output count, quality, language and color palette. These events do not contain image pixels, filenames, file paths, URIs, captions, text-layer contents or account information.

Firebase Analytics may also process app and device information and an app-instance identifier needed to measure product usage. LumaEdit explicitly disables Analytics advertising-ID collection and advertising-personalization signals. Analytics data is used to understand feature adoption and improve reliability and usability, not to edit or analyze your photos.

Optional Firebase Crashlytics

Firebase Crashlytics reporting is disabled by default. You may enable or disable it separately through Settings → Crash reports. If enabled, Crashlytics may process stack traces, exception classes and messages, relevant app state, app version, crash timestamp, device model and operating-system information, memory/disk indicators, Crashlytics installation UUID, Firebase installation ID and session identifiers. LumaEdit adds only sanitized technical keys such as current screen, last editor tool, export preset, operation name and error class; it does not attach photos, user-entered text, filenames, paths or URIs.

Firebase states that Crashlytics keeps crash traces and associated identifiers for 90 days before starting removal from live and backup systems. Firebase encrypts data in transit and Crashlytics data at rest. See Firebase’s Android data-disclosure guide and Firebase privacy and security information.

8. Retention and deletion

• In-memory editing data: held while needed for the current editing session and released when the App closes or replaces the working image.
• Private projects: kept until automatically removed after the 12-project limit, until App storage is cleared, or until the App is uninstalled.
• Preferences and ad frequency controls: kept until App storage is cleared or the App is uninstalled.
• Exported images: kept in Pictures/LumaEdit until you delete them yourself. Clearing App storage or uninstalling does not normally remove those exported files.
• Advertising data: retained by Google according to Google’s privacy policy and retention practices. LumaEdit does not maintain a separate developer advertising profile or database.
• Analytics data: if you opt in, retained according to the Google Analytics retention configuration associated with the Firebase project.
• Crash diagnostics: if you opt in, crash traces and associated identifiers are kept by Firebase Crashlytics for 90 days before removal begins, according to Firebase.

To delete all private LumaEdit data, open Android Settings → Apps → LumaEdit → Storage → Clear storage, or uninstall the App. To delete exports, use your gallery or file manager. Because LumaEdit has no account or developer cloud database, there is no server-side LumaEdit profile to delete.

9. Security

Saved projects and preferences use Android app-private storage, and Android backup is disabled for LumaEdit. Exported photos use shared media storage so they can appear in your gallery and be opened by apps you authorize. Advertising and Firebase SDK communications use encrypted HTTPS connections; Firebase states that Crashlytics data is also encrypted at rest.

Protect your device with a PIN, password, pattern or biometric lock and keep Android updated. No local storage method can be guaranteed completely secure, especially on a rooted, compromised or unlocked device.

10. Children’s privacy

LumaEdit is a general-audience photo utility and is not directed to children under 13 or the minimum digital-consent age in their country. The App does not create user accounts or knowingly collect children’s photo files. The advertising consent request is configured for a general-audience app and not as an under-age-of-consent experience. Parents and guardians should supervise device use and any sharing of edited photos.

11. This website

This is a static product and support website. It has no advertising, analytics, tracking pixels, account registration or contact forms. The language selector on the home page stores only the chosen site language in your browser’s local storage. Sending an email or following a Google Play link is handled by the selected external service.

12. Changes to this policy

We may update this policy when LumaEdit’s functions, permissions, SDKs or legal obligations change. The revised version will be published on this page with a new effective date. The privacy policy and Google Play Data safety answers should always be reviewed when a new App release changes data handling.

Contact

Email: easygamedevs@gmail.com
App: LumaEdit: Photo Editor
Android package: com.lumaedit.photoeditor