Privacy Policy

Your footage

Footage you record with the app is stored on your device, in the app’s own storage. The in-app gallery reads it from there. It is not uploaded to us: there is no footage library on our side to hold it. What happens to a clip after that is your decision. You export it or you do not.

Because the footage lives on the device, the usual consequence applies. If you remove the app, you remove what is inside it. There is no copy here to restore it from. If you want to keep something, export it first.

What an export does

An export writes your footage to a destination you choose: an external SSD or a hard drive connected to the phone, or the Files app. You pick the destination. When the footage is there, that destination governs it, not this app.

That distinction matters if the place you pick is a cloud location. The Files app can expose iCloud Drive and any storage provider on your device. An export into one of those hands your footage to that provider. Its own terms and its own privacy policy then govern your footage. An export to a drive attached to the phone does not involve anyone else.

What the app sends elsewhere

Start with the part that does not change: 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.
• Firebase Crashlytics, from Google LLC. Crash diagnostics. When the app crashes it sends an installation UUID, a session ID, the time of the crash, the app version, OS and device details, stack traces, exception details, and limited app state and logs.
• RevenueCat, Inc. Subscription state. 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.
• Apple Inc. StoreKit 2 handles the purchase itself, so your Apple Account, payment method, billing and any refund are Apple’s side of the transaction. The app never receives your payment card number.

How long it is kept. Analytics event-level and user-level data is retained for up to 14 months. Crashlytics crash traces are kept for about 90 days. If you write to us for support, that email is kept for up to 24 months after the question is resolved.

What none of this is. The app carries no third-party advertising. No personal data is sold. The advertising identifier (IDFA) is not collected, and nothing here tracks you across other apps or other websites.

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.

This website

These pages are static. This site has no account, no sign-up, no comment box, and no form. So there is nothing here for you to submit information to. The site sets no cookies of its own and runs no analytics or advertising scripts.

• 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.

Children

Neither the app nor this site is directed at children under 13. We do not knowingly collect personal information from them.

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 the right to ask what is held, to ask for a correction, and to ask for a deletion. Footage on your own device does not need a release from anyone else. You already hold it, and you can delete it yourself. The next section says where a request goes.

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

When this policy 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.

Contact

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