Your footage is nobody's business.

OpenInstaCine is an open-source field monitor for the Insta360 Luna Ultra, for iPhone, iPad and Android. It talks to your camera over Bluetooth and the camera's own Wi-Fi. The app has no account. Automatic error reports are optional and off by default. OpenCapture is the data controller for the processing described here. Contact support@opencapture.org privately about privacy or deletion. This page is the canonical privacy text; the Privacy screen in the app is a summary of it.

What the app does with data

• Live view and camera control happen entirely over Bluetooth and the camera's own Wi-Fi between your device and your camera. Video frames and raw camera packets stay on that local link.
• Saved camera names and last SSID are stored only in app-local storage on your device. The camera Wi-Fi password is stored in the iOS Keychain (on Android, the Android Keystore) on that phone only.
• Operator preferences such as Keep Screen Awake and the last LUT look stay on the device, along with any .cube files you import.
• Clips you open from the camera are copied into a local cache on the phone so they can play back. Favorites are stored on the phone too. You can clear the cache in Settings at any time.

What never leaves the phone

Live HEVC, camera telemetry, and pairing traffic stay on the local link. We do not operate a footage cloud. We do not sell data or use advertising SDKs. Optional reliability reporting sends technical measurements, never camera footage or raw camera packets.

Third parties

• Apple (or Google). Permission prompts and OS diagnostics are processed under their own policies. If you install a TestFlight or Google Play beta, Apple or Google may provide crash reports to the developer under their terms.
• Sentry (optional reliability reports). In builds configured for this service, you can enable Automatic error reports in Operator Setup. Reports include crash, hang and live-feed diagnostics, app, build, OS and device versions, random incident and session identifiers, and session health counts. They exclude all images, footage, screenshots, raw camera packets, camera Wi-Fi passwords and personal device names. We do not collect GPS location; stored event IP addresses and IP-derived geography are removed. Sentry necessarily receives your IP address while accepting the network connection. Uploads wait while a camera session or the camera Wi-Fi path is active. Turning the option off stops reporting and clears the pending reporting cache on this phone; it does not retract reports already received by the service. Local diagnostic reports remain available to share or delete. Sentry explains its privacy practices in its privacy policy; submitted reports are handled under the configured project's service agreement. Builds without a configured service cannot enable uploads.
• Frame.io (optional, iPhone and iPad). If this build is configured and you sign in, the app talks directly to Adobe IMS and Frame.io to upload clips you pick. The sign-in token stays in the on-device Keychain. Uploads go from your device to Frame.io, never through us. Adobe's privacy policy applies. The Android app does not offer Frame.io upload yet.
• Photos and system share. Saving a clip or using the share sheet is something you start. Apple, Google or the app you pick then handles that file.
• On-device face boxes. AF-C face boxes are computed on the phone from the live preview, with Apple Vision on iPhone and iPad and Google ML Kit on Android. Face geometry is not uploaded. Google describes the usage and performance information ML Kit may send to Google in its ML Kit data disclosure.
• AirPods head tracking (iPhone and iPad). If you use it, the app reads headphone motion on the phone to aim the gimbal. Motion data is not uploaded.
• Sharing the live picture (iPhone and iPad). If you choose to share the live picture with nearby OpenInstaCine phones, it is sent over the local Wi-Fi directly to those devices, not through us. Sharing is off until you turn it on.
• Location permission. iOS and Android tie Wi-Fi network names and Bluetooth scanning to location permission, so the system may ask for it while the app joins the camera's Wi-Fi or scans for it. OpenInstaCine does not use that permission for maps, ads, or a location history, and does not store or share your location.
• GitHub. If you open an issue or discussion, that is public and governed by GitHub's policies. Never post camera Wi-Fi passwords, captures, or private media.

What the app does not do

• No automatic reliability uploads without opt-in and a configured reporting service.
• No advertising or tracking across apps or websites.
• No account with us: the app has no sign-up.
• No sale of personal data.

Reporting a problem yourself

Report a problem opens a native form. When you tap Send report, your description, any optional reply email, selected images and technical details you choose are sent to OpenCapture through Sentry to help investigate and improve the app. Technical details are off by default and can be reviewed first. You may choose up to three photos or screenshots, preview them and remove them before sending. We resize and re-encode selected images without their original filenames or location metadata. The images themselves may contain personal or confidential information: only share images you have permission to send. No images are captured or attached automatically. Please do not include passwords or other sensitive information in your message. This one-off submission does not enable automatic reports. Unsent reports are stored privately on your phone and expire after seven days (removed the next time the app runs). They wait until you leave camera Wi-Fi and can be removed before delivery. Once received, the Sentry retention and deletion arrangements below apply. We use an optional email only to follow up about your report.

Your choice and legal basis

Optional reliability reporting relies on your consent (GDPR Article 6(1)(a)). The first-launch prompt offers Enable automatic reports and Not now. Declining leaves all features and manual reporting available; you can opt in later in System. Reporting helps OpenCapture diagnose crashes, hangs and live-feed interruptions and measure recovery. It is off by default. You can use every camera feature without consenting. Withdraw consent at any time by turning off Automatic error reports in Operator Setup. This stops further reporting and clears pending SDK uploads; withdrawal does not change the lawfulness of processing before withdrawal. Reports already received can be the subject of a deletion request.

Reports use random incident and session identifiers rather than an account or advertising identifier. Technical reports can still be personal data; we do not promise that removing names makes them anonymous. We do not use reports to make automated decisions about you or to profile you for advertising.

Where reports are processed

Sentry (Functional Software, Inc., United States) processes optional reports for OpenCapture. Our Sentry organization, opencapture, uses the Germany (EU) region for event storage. Some account, integration and organization metadata may be processed in the United States, and international access or transfers may occur. Sentry describes its available transfer safeguards, including standard contractual clauses, in its Data Processing Addendum, and publishes its subprocessors and EU storage details.

How long data is kept

Sentry event and attachment retention depends on the plan in effect when a report arrives: normally 30 days on Developer or 90 days on Team and Business plans. Issue summaries may remain after individual events expire. Sentry rotates backups separately, within 30 or 90 days depending on data type. See Sentry retention periods. Deletion requests also cover any identifiable copies we have exported for support.

On-device diagnostic storage is bounded and older reports are rotated. You can delete saved reports in Operator Setup. Turning off reporting clears pending SDK uploads; it does not clear separately saved local diagnostics. Preferences, saved cameras and cached clips remain until you change or clear them or remove the app, subject to platform backup and secure-storage behavior.

Private support correspondence is kept while needed to resolve the request and follow up. We review these records and remove information no longer needed; legal obligations may require specific records to be retained longer.

Your privacy rights

Depending on the circumstances, you may request access, correction, erasure, restriction or portability of your personal data, object to processing based on legitimate interests, and withdraw consent. You may complain to your local data protection authority. Email support@opencapture.org privately. We normally respond within one month; if a lawful extension is needed, we explain it.

We do not attach a name or email address to reliability reports. If available, include an incident identifier from a saved report, the approximate time and app build to help locate your data. We may need limited additional information to locate a report or verify a request. Do not post personal details or diagnostic attachments in public GitHub issues or discussions.

Visiting this website

Vercel hosts this website and receives technical connection information, including your IP address, to deliver and secure it. Pages that load Google Fonts also make a connection to Google. These providers process connection data under their own policies. This website sets no cookies and runs no analytics or advertising scripts. Optional external services receive data when you use them. Necessary site delivery and handling support requests are based on our legitimate interests in operating and supporting OpenInstaCine; you may object where this basis applies.

Changes and contact

Changes to this policy are published on this page and in the project's public repository. Bugs: GitHub Issues. Privacy and private support: support@opencapture.org.