Privacy policy
Your recordings stay on your device. Apple and RevenueCat handle purchases. Standard app usage uses PostHog and Firebase Analytics; campaign and purchase reporting also uses RevenueCat. Crash diagnostics use Firebase Crashlytics with a separate setting. Additional Pro offer and purchase-screen events are optional.
DrivoCam is provided by Semih Karakaya. This policy describes the iOS app’s camera, recording and purchase features and this support website.
Recordings and telemetry
Videos you record, import or download are stored in the app’s local storage. DrivoCam does not automatically upload your video, microphone audio or precise location to the developer or RevenueCat.
Depending on the features and settings you use, recordings may include microphone audio, timestamps, speed, location, direction and motion data. Telemetry may be stored beside a recording or permanently embedded in an exported video. Review recordings before sharing them.
Permissions
- Camera and microphone access support video recording and optional audio.
- Location supports speed, coordinates and direction. On supported systems it may also be used to read the camera’s Wi-Fi network name. Recording without location remains available if you decline that permission.
- Motion data supports G-force information and automatic recording protection.
- Local Network access supports camera discovery, live viewing and transfers you request.
- Photo library access lets you save selected recordings to your library.
You can change permissions in iOS Settings. Disabling a permission can limit the related feature. DrivoCam does not promise continuous recording while the app is in the background or the phone is locked.
Camera connections and local preferences
The app connects to the camera or stream address you choose. If you choose an internet-hosted stream, its operator receives your connection and may process ordinary network information under its own policies. Camera pairing and session information is used during that connection. Successfully authorized 70mai pairing tokens can be retained in iOS Keychain or Android Keystore-backed encrypted storage. Other local preferences and recordings are not erased by this storage change; re-pairing can be required after reinstall or device transfer.
Recording preferences, the last camera address, your analytics choice and the amount of your free recording allowance already used can be stored on your device. The recording allowance is shared by phone recording and connected cameras. These local preferences are separate from purchase verification; usage events do not include camera addresses.
10 minutes of free recording shared by your phone and connected cameras. After the allowance is used, starting a new recording session requires the one-time Lifetime Pro purchase. Existing recordings remain accessible.
Purchases
Apple processes App Store payments. DrivoCam does not receive your card details. RevenueCat verifies transactions, restores purchases and tells the app whether Pro access is active. This uses purchase and transaction history, product and entitlement information and a randomly generated app user identifier. RevenueCat also receives technical device information, such as device type and operating system, and service activity information such as when the app was last seen. The app does not ask you to create a DrivoCam account or supply an email address for purchases.
Purchase information is used for access, purchase support, fraud prevention and purchase reporting. A RevenueCat identifier is not a guarantee that the underlying store records cannot be associated with your store account. Essential purchase verification and restoration work independently of your optional analytics choice.
RevenueCat processes end-user purchase information on our behalf. For information about these providers and their practices, see Apple’s privacy policy and RevenueCat’s privacy policy.
Standard usage and campaign measurement
When analytics is configured for your app version, PostHog receives standard app usage events automatically: app opens, onboarding completion, successful camera connections by camera family, and recording starts and stops with source types and duration. The detailed purchase analytics switch does not disable these events.
Standard events use a randomly generated installation identifier, the app environment and acquisition status. For iOS campaign measurement, the app can request an Apple AdServices attribution token and send it to Apple to resolve campaign information. Available results can include campaign, ad group, keyword, ad and organization identifiers, country or region, and conversion or claim type. Unavailable attribution stays unknown. The token itself is not included in PostHog events or RevenueCat customer attributes.
The same app-generated installation identifier used for PostHog events and available campaign information can be associated with the RevenueCat customer used for purchase verification and reporting. This helps relate acquisition and app use to purchases. These identifiers are pseudonymous; linking them to purchase information does not guarantee anonymity. PostHog, RevenueCat and Apple also process ordinary network information, such as an IP address, when receiving requests.
The app does not add recordings, microphone audio, precise coordinates, camera addresses, camera credentials, purchase receipts, an account email address or free-form user input to its analytics events. Session replay and automatic screen capture are disabled in this integration. See PostHog’s privacy policy, RevenueCat’s privacy policy and Apple’s privacy policy for provider information.
Firebase Analytics and crash diagnostics
When enabled for a release version, Firebase Analytics receives standard SDK app events and the app’s limited onboarding, camera-family and recording-state events. It can process app and device information, an app-instance identifier, SDK-supported purchase events and approximate location derived from network information. We do not set an account email, PostHog identifier or RevenueCat customer identifier as a Firebase user ID. Advertising-ID collection and ad-personalization consent are disabled.
Firebase Crashlytics receives crash and error diagnostics, app/build and device/OS information, and SDK-generated installation/session identifiers. Application-supplied Dart diagnostics use filtered error categories and code-stack information. Native crash reports also contain SDK-generated exception and execution information. The app does not attach footage, audio, precise GPS, camera addresses, credentials, receipts or free-form input to its custom Firebase events or diagnostic messages.
Crash reporting starts on in release builds and can be disabled independently using “Crash reports” in Settings. Disabling it stops new app-supplied crash reports, disables SDK crash collection and asks the SDK to discard unsent crash reports. Already transmitted reports are not automatically deleted by that switch. This choice does not disable standard analytics, recording, camera connections or verified Pro access. Debug/profile application entry points do not activate Firebase reporting; dedicated developer setup tests use synthetic data.
Firebase SDKs may keep events or diagnostic reports on the device for later transmission when a connection becomes available. Recordings and camera connections do not wait for those transmissions. Google processes Firebase information under its Firebase privacy documentation. Provider retention, regional processing and deletion requests are separate from local app-file deletion.
Optional detailed purchase analytics
The “Detailed purchase analytics” switch in Settings starts off. If you turn it on, PostHog and Firebase Analytics also receive Pro offer requests and purchase-screen outcomes using the same installation identifier and available campaign context. A client purchase-flow outcome is not itself proof of a purchase.
You can decline these additional events or turn the switch off at any time. The app saves this choice locally. If it cannot save a change, it shows an error; retry so the choice is retained after restarting. Turning the switch off cancels pending app-owned optional PostHog requests and prevents new detailed purchase-event calls to either provider. Firebase events already accepted by its SDK while this choice was enabled can remain in its SDK queue for later transmission. It does not stop standard usage or campaign measurement, remove the installation identifier or RevenueCat association, clear campaign data, reset an ongoing recording interval, sign you out of purchases or remove verified Pro access.
The app-owned PostHog transport sends events directly without a persistent offline queue; failed or busy PostHog requests may be dropped. Firebase SDK queues are described separately above. The native PostHog event queue is not started. Previously delivered data is not erased by changing the optional switch, and a request already received by a provider cannot be recalled.
For access, objection or deletion requests concerning standard or optional analytics and campaign information, contact semih@ilysia.app. We may need enough information to locate the relevant installation or purchase record; a support email address alone may not identify pseudonymous records. Do not send passwords, payment-card details or an Apple attribution token.
Sharing, backup and deletion
When you choose to share or export a recording, the selected recipient, service or photo library receives that copy and any embedded information. Copying telemetry to the clipboard places it on the system clipboard. Those copies are governed by your choices and the receiving service.
Delete local recordings from the app. Storage management may remove old, unprotected phone recordings when your selected storage limit is reached. Marking a recording as protected does not encrypt it. Removing the app may remove its local data; exported files, Photos copies and system backups must be managed separately. iOS device backups depend on your system settings.
Deleting the app does not by itself erase Apple or RevenueCat transaction records. Purchase records may be retained as needed to verify and restore access, handle refunds and meet applicable recordkeeping obligations. Contact us with purchase-data requests; do not send your Apple password or payment-card details.
Local recordings and preferences remain until you remove them, storage management removes eligible unprotected recordings, or the app’s local data is removed. The saved analytics choice and recording-allowance usage are separate local records. Changing the detailed purchase analytics choice does not reset the recording allowance or delete your footage.
Analytics and campaign information already received by PostHog, Firebase/Google, RevenueCat or Apple is subject to the applicable project settings, provider policies and any recordkeeping obligations. This policy does not promise a fixed retention period or automatic historical deletion when you change the optional switch or uninstall. Contact us for an access or deletion request, including information retained in provider records; we will explain any limits that apply to your request.
Support and this website
If you contact us, we use the email address and information you choose to send to respond to your request. The in-app support action pre-fills a draft with existing PostHog and RevenueCat identifiers, available app/device information and app language. You can review and edit the draft before sending it. Share only recordings or diagnostic details that you want us to review. We retain support correspondence while needed to handle the request and related obligations.
This website has no analytics or advertising scripts added by us. Its hosting service processes the network information needed to deliver pages and operate the service.
Your requests and policy updates
Depending on applicable law, you may have rights to access, correct, delete or object to processing of information held about you. Contact semih@ilysia.app for privacy requests. We may need enough information to locate a purchase or verify a request, and some store records are controlled by the store provider.
We update this page when the app’s data practices change. The date above identifies the latest version.