Legal

Privacy Policy

Version 1.0. Effective August 17, 2026. Last updated September 30, 2026.

This policy covers Log Cam: RAW 4K Video Camera, an iPhone app that records log video, and this website. Mehmet Ali Kısacık operates both. He is an individual based in Istanbul, Turkey, and he is responsible for the decisions this policy describes. The app has no account, so it never asks for your name, your email address, or your phone number.

At a glance

  • No account. There is nothing here to sign up for. The app works without a name, an email address, or a phone number.
  • Your files stay yours. Footage, audio, gyro data, imported LUTs, and take metadata stay on your device or in an external folder you choose. None of it reaches us.
  • Limited data goes to a few services. Firebase Analytics, Firebase Crashlytics, and RevenueCat receive usage, device, and purchase information. By design, none of them receives the contents of a recording.
  • No advertising and no sale. The app carries no third-party advertising, sells no personal data, and collects no advertising identifier.

Your footage

The app writes footage either to its own storage on your iPhone or directly to an external folder you select. The in-app gallery reads takes from the selected location. The app does not upload your footage to us: there is no footage library on our side to hold it. You can also export or share a separate copy.

Recording and image processing happen on the device. Finished takes and their companion files go to the app’s own Documents/Clips folder, or to an external folder you select. The app does not analyze a recording to identify a person, infer a sensitive trait, recognize a face, or build a biometric template. It never uses your footage to train a machine-learning model.

A recording can hold personal data about you or about someone else. When you record another person, the notice, consent, privacy, and recording laws of your place apply to you.

Removing the app removes takes in its local container. It does not remove takes recorded directly to an external folder, exported copies, or copies held by a file provider or backup. We have no copy to restore. Keep your own copy of any take you need before you remove the app.

Permissions and what a take leaves behind

The app requests camera access to show a preview and to record. It requests microphone access when you enable audio, and Motion & Fitness access when you enable gyro logging. iOS supplies the answer, and iOS Settings is where you change it. A feature stops working when you refuse the permission it needs. The app can also list the camera lenses and audio inputs on your device, and it stores the identifier and display name of a microphone you select.

With gyro logging on, the app records rotation-rate samples and writes a Gyroflow-compatible GCSV sidecar and JSON metadata beside the take.

Each take can also produce a thumbnail, a capture ledger, and technical sidecars. Those files hold the filename, the time and duration, the file size, the codec and format, and the dimensions and frame rate. They also hold the log and LUT settings, camera and lens information, exposure and white balance, the device model, the audio route, gyroscope timing, thermal and storage state, memory and pipeline measurements, error codes, session events, integrity checks, and app-generated recording identifiers.

Those records let the gallery show take details, confirm that a recording finished correctly, recover from an interruption, diagnose a capture failure, and support Gyroflow. They stay with the take or in local cache storage on your device.

What the app keeps on your device

The app stores your capture settings: codec, frame rate, bitrate, log curve, crop, lens, LUT selection and use mode, monitoring tools, audio configuration, gyro setting, and stabilization. It also stores whether onboarding is complete, together with the onboarding answers you gave about your shooting priorities and your editing plans.

An imported .cube LUT is read, validated, and copied into the app’s Documents/_LUTs folder. When you choose an external recording folder, the app stores a security-scoped bookmark, a random local source identifier, and the folder’s display name, so it can ask for access again. A file provider such as iCloud Drive processes the source file or folder under its own terms.

The Documents folder is visible through the Files app, and it can be reachable through Finder or device file sharing. Your iPhone backup, your iCloud settings, and your external storage configuration can cause local files to be backed up, synchronized, or made available on another device. Apple and any file provider you select control that under their own notices.

The start date of the local trial sits in the iOS Keychain. That entry does not synchronize through iCloud Keychain, but it can travel in an encrypted device backup. It is designed to survive deletion and reinstallation of the app, so one installation cannot restart the trial.

What an export does

An export makes a separate copy of a take at a destination you choose, such as an external drive connected to the phone or a location in the Files app. The original remains in its recording location until you delete it. You can also choose an external folder as the recording destination, so a take can be written there without an export.

The Files app can expose iCloud Drive and other storage providers on your device. Recording or exporting into one of those locations gives that provider access to the files under its own terms and privacy policy. A copy exported to a drive attached to the phone does not involve a cloud provider by itself.

Sharing runs through the iOS share sheet. The person or the app you pick receives the files and processes them under its own terms, and we receive no copy of what you send.

Export Take Package is the wider of the two exports. It can include the technical ledgers and sidecars described above, and those files can reveal device and audio-route diagnostics. The app warns you for that reason. Review a take package before you send it to anyone, support included.

What the app sends elsewhere

None of the services below receives your footage. No call to Firebase or to RevenueCat carries a recording, a photograph, a LUT file, audio, gyro samples, a filename, or a precise location. What follows is about how the app is used and how a purchase is processed, not about what you shot.

  • Firebase Analytics, from Google LLC. Pseudonymous product analytics. It receives automatic and custom events: first open, sessions, screens viewed, feature controls used, purchase funnel events, and errors. Alongside them it receives an app-instance identifier, the Identifier for Vendors (IDFV), the app version, device model, OS version, language, and a coarse region inferred from the IP address your request arrives on. It is configured without the capability to collect the advertising identifier, and advertising personalization signals are turned off. Recording contents, audio, gyro samples, LUT contents, filenames, onboarding free text, contact details, and precise location are never sent as event parameters. Firebase Privacy and Security.
  • Firebase Crashlytics, from Google LLC. Crash diagnostics. When the app crashes it sends an installation UUID, a Firebase installation ID, a session ID, the time of the crash, the app bundle identifier and version, OS and device details, CPU architecture, memory and disk information, jailbreak status, stack traces, exception or signal details, and limited app state, logs, custom keys, and breadcrumbs. Recordings, audio tracks, Gyroflow files, LUT contents, external folder contents, and take ledgers are never attached to a crash report. Firebase Privacy and Security.
  • RevenueCat, Inc. Purchase and entitlement status. It runs in observer mode alongside StoreKit 2 and receives an automatically generated anonymous App User ID, technical data about the app and the device, and App Store transaction, product, entitlement and revenue information. It may also obtain an Apple AdServices attribution token and store Apple Ads campaign, ad group and keyword data, which is used to measure our own campaigns. It does not receive your name, your email address, your recordings, or your payment card number. RevenueCat Privacy Policy.
  • Apple Inc. StoreKit 2 handles the purchase itself, so your Apple Account, payment method, billing, authentication and any refund are Apple’s side of the transaction. The app receives the product information and the App Store-signed transaction and entitlement status it needs to unlock and restore a purchase. It never receives your payment card number. Apple also provides iOS permissions, Files integration, Apple Ads attribution, and backup. Apple Privacy Policy.
  • Microsoft Corporation. Privacy-request email. The address this policy designates for privacy requests runs on Outlook, so Microsoft handles your email address, your message, and anything you attach when you write to that address. Microsoft Privacy Statement.

Every one of those calls carries ordinary network data. The provider receives your IP address, the time of the request, the app and OS version, the response status, a project or authentication token, and any error. Serving and securing a request takes that much.

When you write to us for support, we process your email address, your message, and whatever you attach, so that we can investigate and answer. Do not send a recording, a ledger, or other sensitive content unless your request needs it and you are comfortable sharing it.

What none of this is. The app carries no third-party advertising. No personal data is sold, and none is shared for cross-context behavioral advertising. The advertising identifier (IDFA) is not collected, and nothing here tracks you across other apps or other websites. There is no account database, and your recordings never train a machine-learning model.

This is separate from anything the app does. When you turn on sharing with app developers in your iOS settings, Apple can share standard, aggregated crash and diagnostic reports with developers. That setting is yours and lives in iOS, not in this app.

Why the app processes it

  • To run the app. Camera preview, recording, audio capture, gyro logging, imported LUTs, gallery playback, take verification, file sharing, and access to an external folder.
  • To keep your setup. Remember settings, onboarding state, and preferences, manage the local trial, and return the app to a usable state after an interruption.
  • To process a purchase. Complete and confirm entitlements, restore purchases, and measure the performance of our own Apple Ads campaigns. For a web purchase, provide the access bought, prevent fraud, and handle refunds and revocations.
  • To keep the app working. Understand which features are used, measure performance, find crashes, diagnose failures, improve reliability, and protect the app and its services.
  • To answer you. Respond to support and privacy requests, meet legal obligations, and establish, exercise, or defend legal rights.

Legal bases

Where the data protection law of your country asks for a legal basis, one or more of these applies.

  • Your request, or our agreement with you. Providing the features of the app, processing and restoring a purchase, and answering your support message.
  • Consent, where the law requires it. Optional device permissions, analytics, and anything else your local law treats as consent-based. You can withdraw consent for future processing, and that withdrawal leaves lawful past processing intact.
  • Legitimate interests. Securing, maintaining, troubleshooting and improving the app, preventing abuse, measuring our own advertising, and protecting legal rights, as long as those interests do not override your rights and freedoms.
  • Legal obligations and legal claims. Valid government requests, tax and accounting requirements, and the establishment, exercise or defense of legal rights.

Where Türkiye’s Law No. 6698 on the Protection of Personal Data, the KVKK, applies, processing rests on the conditions that law permits, including explicit consent where the law requires it.

How long things are kept

On your device, everything stays until you delete it, replace it, use a control in the app, or remove the app. Deleting a recording moves its own files into a Recently Deleted area in the same storage location. They stay there for up to 30 days and are then deleted permanently, unless you restore or purge them first.

Removing the app removes its local container. It does not remove what you exported, what sits in an external folder, what a recipient already holds, or what a device or cloud backup already copied. The Keychain trial entry survives on purpose. We cannot read or delete anything that exists only on your device.

Off the device, the periods are these. Analytics event-level and user-level data is retained for up to 14 months, and standard aggregated reports can remain available longer, because the retention setting does not reach them. Crashlytics crash traces and their identifiers are kept for 90 days before removal begins. If you write to us for support, that email is kept for up to 24 months after the question is resolved, and longer where the law requires it or a legal claim needs it.

Apple, RevenueCat and, for web purchases, Paddle keep purchase, transaction, entitlement and attribution records under their own terms and their own legal obligations. When a period ends, the information is deleted or de-identified where that is reasonably possible.

When information is disclosed

Disclosure happens only in the ways this policy describes.

  • Service providers. Apple, Google, RevenueCat and Microsoft process the limited data their service needs, as described above. Paddle handles web purchases, and Resend handles any activation email we send, as described under This website.
  • At your direction. A sharing destination, an external drive, a file provider, or a recipient receives your files only when you select or authorize it.
  • Legal and safety. Information reasonably necessary to comply with the law or valid legal process, to protect users or the public, to investigate abuse or fraud, or to establish, exercise or defend a legal claim.
  • Business transfer. If the app or its assets are reorganized, acquired, financed or transferred, the relevant information transfers under this policy, or with advance notice of materially different treatment.

Personal data is not sold, not shared for cross-context behavioral advertising, not rented as a mailing list, and not disclosed to a data broker. Apple Ads attribution through AdServices uses no advertising identifier.

Where it is processed

Operations are based in Istanbul, Turkey. Apple, Google, Microsoft, RevenueCat, Paddle, Resend and their subprocessors can process information in the United States, the United Kingdom, the European Economic Area, Türkiye, or another country where they operate. Privacy law in those countries differs from the law where you live.

Where the law requires one, a transfer uses a lawful mechanism: an adequacy decision, standard contractual clauses or standard contracts, another recognized safeguard, or explicit consent. Ask us which one applies to your request and we will tell you.

Security

The protections match the nature of the information: iOS sandboxing and operating-system data protection, permission controls, security-scoped folder access, Keychain storage for the trial date, encrypted HTTPS transport for every service call, StoreKit-signed transaction verification, data minimization, and hard limits on what reaches Analytics and Crashlytics.

No method of storage or transmission is completely secure. Your device, your Apple Account, your passcode, your backups, your external drives, your exported files and your sharing destinations are yours to protect. If a breach requires notice, we investigate it and notify the people and the authorities that the law names.

This website

This site has no account, no sign-up, and no comment box. The web purchase page opens Paddle's checkout for payment and calls our entitlement service to create a transaction and check its status. The site sets no cookies of its own and runs no analytics or advertising scripts. To resume after you close the tab, the purchase page stores a pending activation secret, checkout environment, creation time, and browser-only completion flag in your browser's local storage. Our service checks payment status separately.

  • Web fonts. Pages load their typefaces from Google’s font servers. Your browser requests those files directly. So Google receives your IP address and browser details when it serves them.
  • Server logs. A hosting provider serves this site. It keeps ordinary request logs of the kind every web server keeps. Those logs hold IP addresses and the pages requested.
  • Web purchases. If you use the web-purchase option offered to some customers as a fallback, Paddle.com acts as our Merchant of Record and processes the information that purchase requires, under its own privacy notice. Paddle, not us, processes your payment card information. We can receive limited transaction and customer information from Paddle. We use it to provide the access you bought, give customer support, prevent fraud, and handle refunds and revocations. Paddle emails your receipt. When activation email is available, we send the link through Resend, which processes your email address and the message to deliver it. Our entitlement service reads the address from Paddle when sending that email and does not keep its own copy. Paddle Privacy Notice.

Your controls in the app

  • Permissions. Change Camera, Microphone and Motion & Fitness access in iOS Settings. Audio and gyro logging also have their own switches in the app.
  • Storage. Choose internal storage or a specific external folder, and remove or replace that folder selection in the app’s settings.
  • Recordings. Delete a recording, restore it from Recently Deleted during the recovery window, or purge it permanently. Delete an imported LUT through the app or through Files.
  • Exports. Share a recording on its own, or export a take package that includes the technical files. Check the destination before you send either.
  • Purchases. Restore purchases in the app. Apple’s own account and support tools cover App Store purchase history, refunds and payment questions. Paddle Buyer Support covers the same questions for a web purchase.
  • Removal. Remove the app to delete its local container, subject to the Keychain trial entry, backups, external files and exported copies described above.

Children

Neither Log Cam: RAW 4K Video Camera nor this site is directed at children under 13. It is a general-audience camera utility, and it is not designed or marketed for them. We do not knowingly collect personal information from a child under 13 in a way that requires parental consent.

If you believe a child sent information through analytics, crash reports, RevenueCat or support in a way the law does not allow, write to us. We will investigate and delete what is under our control, where that is possible.

Your rights

Where the data protection law of your country gives you rights over information about you, you can exercise them. Those rights can include learning whether your personal data is processed, and asking about its purposes, its legal basis, its recipients and its transfers. They can also include access to a copy, correction of inaccurate data, deletion, destruction, restriction, portability, objection to certain processing, withdrawal of consent, and a complaint to your data protection authority.

Footage on your own device does not need a release from anyone else. You already hold it, and you can delete it yourself.

Residents of Türkiye hold the rights in Article 11 of the KVKK, and a KVKK request is answered in the shortest time the law allows and never later than 30 days. Residents of California and other United States states hold the rights their own law gives them. We do not sell or share personal information for cross-context behavioral advertising, so there is no sale or share opt-out to offer.

Write from an address that can receive our answer, and describe the data and the right involved. Because there is no account and most data exists only on your device, we often hold nothing to identify. We can ask for a limited detail, such as an anonymous service identifier or a purchase reference, to verify and scope a request. We explain any lawful refusal, and we answer within the period the law sets.

Privacy requests

Mehmet Ali Kısacık is the data controller for the app and this website, and he is an individual based in Istanbul, Turkey. Türkiye’s Law No. 6698 on the Protection of Personal Data, the KVKK, applies to that processing, alongside whatever your own country gives you. Send a privacy or data-subject request to mehmetali.kisacik@outlook.com, which is the address this policy designates for it. Where the law sets a deadline, a request is answered within 30 days.

Changes to this policy

This policy changes when the app, a service provider, a legal requirement, or a data practice changes. When it changes in a way that matters, the date at the top of the page changes with it. A material change is made here rather than announced somewhere else.

Where the law requires it, a notice appears in the app or in another prominent place before a material change takes effect. If a change requires your consent, we ask for it before the processing begins.

Contact

Questions about this policy go to Mehmet Ali Kısacık through the contact page. Email: supportlogcam@gmail.com.