A LITTLE TRANSPARENCY

Your photos.
Your choices.

Privacy policy for the Irisa Android app and website.

Updated 9 November 2026

Photo editing stays on your device. Android eye detection, makeup, layers and effect rendering run locally.

The website uses a sample portrait. Your theme choice stays in your browser; feedback is sent only when you submit it.

Third-party services are separate. Google’s advertising, Firebase crash reports and app statistics, ML Kit metrics and Play services have their own data handling.

1. What this policy covers

This policy covers the Irisa Android eye photo editor and this product website. Irisa is published by ModelX Apps Studio (“we”, “us”). The website’s sample previews are separate from the app’s photo-processing features.

Questions about your information can be emailed to tmukhtar.dev@gmail.com or sent through our feedback page, using the Privacy request category.

2. Photos, faces and eye detection

In the Android app, imported photos, detected face and eye positions, iris geometry and editing are processed on your device using ML Kit, MediaPipe and the app’s image engine. Hair color and background blur or replacement use an on-device MediaPipe segmentation model to separate hair, person and background. The app does not upload your photos, camera frames or edited results to an Irisa server for processing.

Detection estimates where to place an effect; it is not used by Irisa to identify a person or build a face-identity database. Eye positions, outlines and edit settings may be kept in a local draft so you can continue editing.

Google states that ML Kit processes input and outputs on-device, while its SDK can contact Google for model or compatibility updates and send API performance and usage metrics. See ML Kit’s privacy information.

3. Editing features and the information they use

All of these Android editing features use your chosen photo, camera capture, detected eye geometry and the adjustments you make. Their settings do not require an Irisa account.

  • Lenses and color: textured lenses, two-tone colors, independent eye colors, partial heterochromia, fantasy pupils and favorite looks.
  • Beauty and retouch: eyelashes, eyeliner, eyeshadow, eyebrows, iris/pupil proportions, subtle symmetry adjustments, flash red-eye correction, eye brightening, iris detail and under-eye correction.
  • Creative effects: laser, neon, galaxy, fire, ice, lightning, cyber, anime, horror, glitter and iris reflections.
  • Hair and background: hair color, background blur and background replacement, using the on-device segmentation described above.
  • Animated eyes: neon pulses, galaxy motion, fire flicker and laser motion, with GIF export.
  • Layer studio: up to eight ordered effects, with each layer’s settings, visibility and mask stored with the project.
  • Precision tools: manual eye placement, zoom, repositioning, iris radius/oval/rotation, soft erase/restore masks, original comparison and session undo/redo. Crop/rotate tools are available in the existing AI editor.
  • Batch and live tools: batch edits use selected photos; live try-on uses camera frames. Saving a frame or exporting a batch is an action you choose.

4. Camera and device permissions

Camera access is used for taking a photo and live try-on. Live frames are processed in memory; the app keeps a photo when you choose to capture one. The website does not request camera access.

The Android photo picker gives the app access to photos you select. The app copies an imported source into its private draft storage so an edit can be reopened even if picker access expires. You can manage camera and other permissions in Android settings.

5. Drafts, layers, settings and favorites

The app’s private storage may contain your imported source photo, edited creations, drafts, eye positions, mask strokes, layer order, lens pattern identifiers, selected colors, effect strengths, favorite looks, batch progress and preferences such as language, appearance and icon choice.

Drafts are saved locally to support resuming and Edit again. Undo/redo history is a session feature; the current edit is what the draft retains. Irisa does not provide cloud account synchronization for these projects.

6. Exporting and sharing

You choose when to create JPEG, PNG or animated GIF output, save a copy to Gallery or Files, or open Android’s share sheet. Image dimensions, compression quality and file names are used to create the requested output.

Without Irisa Pro, saved images carry a small Irisa mark in a corner unless you choose to watch an extra short video to save without it. The mark is drawn into the output on your device.

If you share a saved look, Irisa creates a small file holding the look’s name and lens settings, with no photo in it, and sends it with a link to the app to the place you choose. Whoever receives it can see that name. When you open a look or a photo sent from another app, Irisa uses it on your device only. A look file is checked before use and is added to your looks only if you tap Add.

Sharing sends a file to the app or location you select. Those recipients handle the copy under their own practices. Copies saved outside Irisa are independent of the in-app original, so deleting a creation inside Irisa does not delete copies you exported or shared.

7. Deleting app data and temporary files

Deleting a saved creation normally moves it to Recently deleted, where it can be restored. The app purges expired trash after seven days when cleanup runs, and you can empty trash yourself. Deleting a draft removes its editable source and settings from the app.

Temporary camera and cache files can be cleared through the app’s storage controls. Clearing Android app storage or uninstalling removes the app’s local data. Gallery exports, shared copies, backup archives and data restored by Android remain subject to the location or backup service where you placed them.

8. Backups and device transfer

Android backup can include preferences and favorite looks. The app’s backup rules exclude saved creations, drafts and batch progress from Android cloud backup. Android device-to-device transfer can move this app data to another phone.

If you choose to create a portable backup archive, it can include the photos, drafts, looks and settings selected by that feature. You choose the file destination and control who can access or share the archive. See Android’s backup documentation for platform behavior.

9. Advertising and consent

The free version of the Android app is supported by ads from Google AdMob, using Google’s Mobile Ads Next-Gen SDK. Ads can appear as banners (including a banner that opens larger once and can be collapsed), native ads within screens, full-screen ads after saving and when you return to the app, and optional reward videos. Without Irisa Pro, saving a creation, using a Pro effect (creative effects, animated eyes, hair and background) or removing the Irisa mark asks you to watch a short reward video, and complete eye looks show a reward ad after a countdown you can cancel. If no ad is available, the action goes ahead.

When ads are shown, Google’s SDK can collect and share IP addresses, approximate location derived from IP, advertising/device identifiers, ad and app interactions, and diagnostics for advertising, measurement and fraud prevention. Your photos are never passed to the ad SDK.

Where the law requires it, Google’s consent form asks for your choices before personalized ads are shown; Settings → Ad privacy choices lets you change them. Irisa Pro, bought through Google Play, removes all ads, reward videos and the Irisa mark. We do not sell your personal information. This website does not embed advertising scripts.

Provider details: Google Next-Gen advertising data disclosure and Google Privacy Policy.

10. Crash reports and app statistics (Firebase)

The Android app uses two Google Firebase services to find bugs and see which features are used. Neither receives your photos, file names or anything you type.

  • Firebase Crashlytics: if the app crashes, or an action such as saving a photo or making a backup fails, it sends Google a report: where in the app’s code the crash happened, your device model and Android version, the app version and a random installation ID.
  • Google Analytics for Firebase: records which screens you open, when you save a creation (only its format: JPEG, PNG or GIF), and once per install when you first open a photo (only whether a face with open eyes was found, never the photo itself) and first save one. It also records how you use features: which lens finish or looks you preview, apply and save, how long a preview takes, whether you chose to watch a video or go Pro for a paid effect, which effect that was, and whether a look was shared or added, or a photo was opened from another app. These are only feature names and choices. They are sent together with device and app information such as model, Android version, language and app version, and a random app-instance ID.

Where the law requires consent, Analytics follows the choices you make in Google’s consent form, which you can change in Settings → Ad privacy choices. Until you agree, it stores no identifiers on your device and its data isn’t used for advertising. If you use Irisa Pro and were never shown the form, Analytics keeps working that way. This website itself uses neither service. See how Firebase handles data.

11. Google Play and purchases

The Android app uses Google Play Billing for Irisa Pro. Purchase and entitlement information is used to determine whether Pro features and ad removal should be enabled. Payment processing and account billing are handled by Google Play; Irisa’s editor does not receive card details.

App update checks, store links and rating prompts can open or interact with Google Play when used. Google’s own policies apply to its services. This website does not take payments or sell a subscription.

12. Irisa account (optional)

An Irisa account is optional; the app works without one. You can create one with Sign in with Google on this website or in the Android app; both use the same account. Google confirms your identity and shares your Google account ID, name, email address and profile picture link with us; we never see your Google password. We use these only to run your account and to contact you about it.

When you sign in, the website sets one essential cookie, irisa_session, which keeps you signed in for up to 30 days and is removed when you sign out. In the app, signing in gives that phone a sign-in token valid for up to 180 days, removed when you sign out. Sessions and tokens are stored only as one-way hashes. Share links you create while signed in are linked to your account so you can list and delete them. Account records are kept in a private database hosted for us (Neon Postgres through Vercel) until you delete the account.

You can delete your account at any time at irisa-api.vercel.app/account/delete, or by emailing tmukhtar.dev@gmail.com. Deletion removes the account, every website session and app sign-in, and the share links linked to it immediately; email requests are completed within 30 days. Photos on your phone and Google Play purchases are not affected.

13. Website previews and theme preferences

The website uses an original sample portrait to illustrate color, makeup, layer visibility, intensity and before/after controls. It does not import or analyze visitor photos. Preview choices stay in the current page session.

The look tools (Shade finder, Describe your look and Ask Irisa) run entirely in your browser: what you choose or type is not sent to us. If you pick colors from a photo in the Shade finder, the photo is opened only in that browser tab and is never uploaded or stored.

The website stores the preference Light, Dark or System in your browser’s local storage under irisa-theme. System mode follows your device’s color scheme. This is a functional preference, not an advertising identifier. Clear site data to remove it.

The website currently includes no advertising, analytics scripts, tracking cookies or mailing list. Optional accounts are described in section 12; Google’s sign-in script loads only on the account pages. The hosting provider may process standard request information, such as network addresses and technical logs, to serve and protect the site.

14. Website feedback and privacy requests

When you submit the feedback form, this website receives the category, affected feature, message, optional email address, your privacy acknowledgement and the submission time, and gives it a reference number. No photo attachment is requested. The submission is sent by email to the Irisa team’s private inbox (tmukhtar.dev@gmail.com, provided by Google Gmail) so we can review suggestions, investigate bugs, handle privacy questions and, if you gave an email, reply to you. The website itself does not keep a copy.

Form drafts are not saved or sent while you type. We do not add your email to marketing lists or publish your message. We delete feedback emails once they are handled, and within 90 days. To request earlier deletion, use Privacy request and include your reference, or email us directly.

The service temporarily uses a hash of the request’s network address in memory to limit repeated submissions. This hash is not included in the email and expires after approximately 15 minutes.

Please do not include passwords, payment details, medical information or other sensitive information in feedback. A response or a particular feature change is not guaranteed.

15. Your choices and requests

You can manage device permissions, delete drafts and creations, empty Recently deleted, clear browser theme storage, avoid optional feedback email and manage Google consent or purchase choices through the relevant controls.

For any privacy request, email tmukhtar.dev@gmail.com. For feedback access or deletion requests, you can also send the reference through the feedback page. We may ask for enough information to verify that the request relates to you. Rights and available options may vary with the services you use and applicable rules.

16. Children, security and policy updates

Irisa is not designed specifically for children under 13. If you believe a child has sent personal information through this website, contact us using Privacy request without adding unnecessary information about the child.

The website is served over HTTPS, and feedback is delivered by email to a private inbox rather than stored on the website. No method of storage or transfer is completely secure, so please avoid sending sensitive information.

We will update this page when implemented features or data handling change. Last updated: .

Ask a privacy question →