LEGAL & COMPLIANCE APP STORE & PLAY CONSOLE AUDITED

Privacy Policy

Official policy for NeoFilm iOS and Android applications.

Original Effective Date August 3, 2026
Last Updated September 23, 2026
Developer / Operator ZEROdev
Direct Contact simpelkode@gmail.com
Privacy Summary: NeoFilm is designed with a strict on-device architecture. Your photos, RAW DNG files, camera streams, and custom film recipes are processed 100% locally on your smartphone. We do not operate photo-hosting servers, we do not upload your images, and we do not sell or monetize personal data.

1. Introduction & Operator Identity

This Privacy Policy governs the mobile applications known as NeoFilm - Vintage Film Camera (including iOS application package com.zerodev.neofilm and Android application package com.zerodev.neofilm), collectively referred to as "NeoFilm", "the App", "we", "us", or "our".

The data controller and publisher responsible for the NeoFilm applications is ZEROdev (represented by Ahmad Sufyan). For any privacy concerns, data subject requests, or regulatory inquiries, contact us directly at simpelkode@gmail.com.

2. 100% On-Device Photo & Image Processing

The core philosophy of NeoFilm is complete photographic privacy:

  • Zero Image Uploads: When you photograph with NeoFilm, apply film stock simulations, develop RAW DNG negatives, or export photos, all color transformations, grain rendering, and optical halation kernels run entirely on your device’s local graphics processor (Apple MetalKit and CoreImage on iOS; OpenGL ES and CameraX on Android).
  • No Cloud Storage: We do not operate cloud servers that receive, process, store, or inspect your pictures or live camera feeds.
  • Local Darkroom Studio: Re-development, cropping, straightening, border application, and contact-sheet synthesis occur entirely within the local sandbox of the application.

3. Device Permissions & Data Access

To operate as a camera and darkroom, NeoFilm requests access to specific device capabilities. Each permission is limited strictly to its stated operational purpose:

A. Camera Permission (NSCameraUsageDescription / android.permission.CAMERA)

Purpose: Required to display the real-time optical viewfinder, adjust manual exposure (ISO and shutter speed), perform manual focus with live peaking, and capture photographs.
Behavior: Camera sensor buffers are streamed directly to on-device memory for real-time shader rendering. Video buffers are never transmitted over the internet.

B. Photo Library & Storage Access (NSPhotoLibraryUsageDescription / NSPhotoLibraryAddUsageDescription / Scoped Storage)

Purpose: Required to save your final processed photos, RAW DNG digital negatives, and exported contact sheets to your device gallery, and to allow you to import existing images into the Mobile Darkroom for reprocessing.
Behavior: On iOS, NeoFilm adds photos to your Photos library and creates a designated "NeoFilm" album. On Android (Android 10+), NeoFilm uses system Scoped Storage (MediaStore.Images), requiring zero broad storage permissions. For legacy Android 8 and 9 devices (API 26–28), WRITE_EXTERNAL_STORAGE is requested solely to write image files to the shared DCIM directory.

C. Location Permission (NSLocationWhenInUseUsageDescription / ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION)

Purpose: Entirely optional. Used exclusively to look up the approximate city name on-device and optionally stamp it onto your film frame borders, as well as embedding standard geographic coordinates into the photo’s local EXIF metadata.
Behavior: Reverse geocoding occurs locally using operating-system location services. Geographic coordinates are never transmitted to our servers or third-party marketing services.

D. Microphone

Status: NeoFilm does not request microphone access and does not record audio. Mechanical shutter sounds are synthesized locally using pre-packaged audio files.

4. Custom Film Recipes & QR Code Sharing

NeoFilm enables photographers to create, save, and share custom analog recipe settings (color curves, HSL channel shifts, grain intensity, halation bloom, and vignette):

  • Local Storage: Custom recipes are stored locally in your device app data store (SwiftData/UserDefaults on iOS; Jetpack DataStore on Android).
  • QR Code Generation & Scanning: When you share a recipe, NeoFilm encodes the parameter values into a visual QR code image. When you scan a recipe, the camera reads the code locally using Apple Vision or Google ML Kit. No external recipe servers or user accounts are involved.

5. In-App Purchases, Subscriptions & Billing

NeoFilm offers optional NeoFilm Pro upgrades (Annual Subscriptions, Monthly Subscriptions, and Lifetime non-consumable unlocks). All transactions are processed through official mobile storefront billing systems:

  • Apple App Store (StoreKit): On iOS devices, purchases are processed by Apple Inc. under Apple’s standard terms.
  • Google Play In-App Billing: On Android devices, purchases are processed by Google LLC under Google Play terms.
  • Payment Card Information: We never collect, see, or store your credit card, debit card, or bank account details. All financial transactions are secured by Apple or Google.
  • RevenueCat (Receipt & Entitlement Management): We use RevenueCat (RevenueCat, Inc.) to validate subscription status, verify promotional trial eligibility, and facilitate cross-device "Restore Purchases" operations. RevenueCat receives an anonymous, randomly generated App User ID and cryptographically signed purchase receipts from Apple or Google. RevenueCat does not receive your name, email address, photos, or location. For more details, consult RevenueCat's Privacy Policy.

6. Diagnostics & Crash Reporting (Android Only)

To maintain stability across thousands of Android device models, the Android version of NeoFilm integrates Firebase Crashlytics (provided by Google LLC):

  • Information Collected: In the event of an abnormal application crash, Crashlytics collects anonymous technical diagnostic data including operating system version, device model, memory state, and technical stack traces.
  • No PII or Photos: Crash reports contain strictly technical stack information. Photos, camera buffers, location coordinates, and personal user identifiers are never included in crash reports.
  • iOS Platform Status: The iOS application contains zero third-party crash reporting SDKs and relies exclusively on Apple’s native, opt-in Crash Diagnostics managed in iOS Settings.

7. Third-Party Analytics, Advertising & Tracking

Zero Commercial Trackers: NeoFilm contains NO advertising networks, NO marketing analytics SDKs (such as Facebook SDK, Google Analytics for Firebase, or AppsFlyer), NO tracking pixels, and NO commercial behavioral data brokers.

We do not sell, rent, or trade your personal information or photographs to any third party for monetary or other valuable consideration under California Consumer Privacy Act (CCPA/CPRA) or any other privacy framework.

8. Data Retention & User Deletion Rights

Because NeoFilm operates without user accounts and without remote photo databases:

  • Photos & Negatives: Your photographs remain on your device. You can delete individual photos, developed rolls, or RAW DNG files at any time via the NeoFilm Studio or your device Photos app.
  • Local Settings & Recipes: Uninstalling the NeoFilm application from your device immediately deletes all locally stored preferences, user presets, and custom recipes.
  • Purchase Records: Purchase tokens and subscription receipts are retained by Apple, Google, and RevenueCat in accordance with statutory accounting requirements and store policies.
  • Rights Requests: If you have questions regarding data access or deletion requests under GDPR, UK GDPR, or CCPA, contact simpelkode@gmail.com.

9. Children’s Privacy

NeoFilm does not knowingly collect, solicit, or maintain personal information from children under the age of 13 (or under 16 in the European Economic Area). Because our application does not require registration and processes photos locally, it does not collect identifying personal data from any user. If you believe that a child has provided us with personal information through support correspondence, please contact us at simpelkode@gmail.com so we can delete the correspondence immediately.

10. App Store Privacy & Google Play Data Safety Alignment

This policy is structured to match the disclosures published on our store product pages:

  • Apple App Privacy (iOS): "Data Not Linked to You" — Purchase history and diagnostics managed through RevenueCat and Apple StoreKit. Zero photos or contact information collected.
  • Google Play Data Safety (Android): "Data Shared" is limited to anonymous crash diagnostics (Firebase Crashlytics) and anonymous purchase tokens (RevenueCat / Google Play Billing). No photos, videos, location, or personal documents are shared or uploaded.

11. Changes to This Privacy Policy

We may periodically update this Privacy Policy to reflect application updates, regulatory changes, or new platform features. Any modifications will be posted directly to this URL with an updated "Last Updated" timestamp. Material changes affecting data handling will be highlighted in the application update release notes.

12. Contact Information

If you have any questions, comments, or concerns regarding this Privacy Policy or our privacy practices, please contact our privacy representative:

Questions Regarding Our Policies?

For privacy inquiries, rights requests (data access, deletion, or portability), or licensing questions, contact our support team at simpelkode@gmail.com.