SafetyCam Privacy Policy
Last Updated: September 10, 2026
1. Scope of This Policy
This Privacy Policy applies specifically to SafetyCam, a mobile application developed and published by Orixa Studio ("we", "our", or "us"). It describes what SafetyCam stores on your device, what limited diagnostic and analytics information leaves your device, and the choices available to you.
SafetyCam is a personal-safety recording app. Its core function is designed to work without an Orixa Studio account and without uploading your recordings to us.
This policy covers the SafetyCam app only. For our website, other Orixa Studio products, and general business practices, see the Orixa Studio Privacy Policy.
2. Content That Stays on Your Device
SafetyCam stores the following content locally on your device only:
- Video recordings you capture
- Audio recordings you capture
- Photo bursts you capture
- Optional incident-location information, when you enable that feature
This content is encrypted inside the app's private vault. It is not automatically uploaded to Orixa Studio, Firebase, Google, or any other cloud service. We cannot see, access, or retrieve it.
If you choose to export or share a recording using your device's share sheet, messaging apps, email, or a cloud storage app, that content leaves SafetyCam's vault and is then governed by the privacy policy of whichever service or recipient you selected. That is an action you initiate, not something SafetyCam does on its own.
3. Firebase Analytics
SafetyCam uses Google Firebase Analytics to understand general app usage and improve features. Firebase Analytics may collect:
- App interactions, such as which screens are opened and which features are used
- Session information, such as session start, duration, and app open events
- App and device information, such as app version, device model, and operating-system version
- Installation identifiers generated by Firebase for this app installation
- An approximate region derived from a masked IP address
Analytics events describe that a feature was used, not the contents of what you recorded.
4. Firebase Crashlytics
SafetyCam uses Google Firebase Crashlytics to identify crashes, application-not-responding (ANR) events, and stability problems. Crashlytics may collect:
- Crash logs and stack traces
- Relevant application state at the time of the failure
- Device model
- Operating-system and app versions
- Session information
- Installation identifiers generated by Firebase for this app installation
Crash reports describe the technical failure so we can fix it. They do not include your recordings or vault contents.
5. What SafetyCam Never Sends Off Your Device
SafetyCam does not send any of the following to Firebase, Google, Orixa Studio, or any other third party:
- Video recordings
- Captured audio
- Photos and photo bursts
- Saved incident coordinates
- Vault contents of any kind
- AccessibilityService key events
We also do not sell your data and do not use SafetyCam data for advertising.
6. How This Information Is Used
The diagnostic and analytics information described above is used only to:
- Understand general app usage patterns
- Investigate technical failures, crashes, and ANRs
- Improve SafetyCam's reliability, stability, and features
It is not used by Orixa Studio for advertising, is not sold to third parties, and is not used to build profiles about you.
7. Permissions SafetyCam Requests
SafetyCam declares the following permissions and system access in its Android manifest. Each is used only for the purpose stated below:
- Internet: to transmit the limited Firebase Analytics and Crashlytics data described in Sections 3 and 4 over encrypted connections; recordings and vault content are never transmitted
- Camera: to record video and capture photo bursts, saved only to the encrypted local vault
- Microphone: to record audio, saved only to the encrypted local vault
- Location: optional, to attach approximate or precise incident coordinates to a recording stored on your device
- Notifications and foreground service: to keep camera and microphone recording running reliably and to show an ongoing recording or ready-status notification
- Wake lock: to keep the device awake as needed while an active recording is in progress
- Vibration: to provide on-device haptic confirmation for recording actions or alerts
- Run at startup: to restore SafetyCam's ready-status notification after the device restarts or the app is updated
- Display over other apps: optional special access used to show SafetyCam recording controls or status over other apps when you enable that feature
- Battery optimisation exemption: optional special access that lets you exempt SafetyCam from battery restrictions so an active recording is less likely to be interrupted; Android requires you to approve this setting
- Accessibility: optional, to detect a hardware-key trigger so recording can be started quickly, as described in the next section
- Quick Settings tile: to let you start or control SafetyCam from an optional tile that you add to Android Quick Settings
SafetyCam does not request broad storage or media-library permission. Vault files remain in the app's private storage. When you explicitly export or share a file, Android's secure FileProvider grants the receiving app temporary access only to that selected file.
Depending on your Android version, sensitive permissions and special access require your approval. You may revoke them at any time in device settings. Revoking access disables the feature that depends on it but does not delete content already saved to your vault.
8. AccessibilityService Disclosure
If you enable SafetyCam's accessibility-based quick trigger, the app uses Android's AccessibilityService API for a single purpose: to detect a hardware-key press pattern so that recording can be started quickly in an emergency, including when the screen is locked or the app is not in the foreground.
Key events observed by this service are processed entirely on your device, in memory, only to recognise the trigger pattern. They are not logged, not stored, not included in analytics or crash reports, and never transmitted anywhere. The service is optional, is off unless you turn it on, and can be disabled at any time in your device's accessibility settings.
9. Sharing and Transfer of Data
Firebase Analytics and Crashlytics data is transmitted using encrypted connections and is processed by Google as our service provider for analytics and diagnostics. Google processes this data on our behalf under the Firebase and Google Cloud data processing terms.
Because Google operates a global infrastructure, this diagnostic and analytics information may be processed on servers outside your country of residence.
We may also disclose information if required to do so by law, regulation, legal process, or an enforceable governmental request. Note that we cannot produce your recordings, vault contents, or saved coordinates in response to such a request, because we never receive them.
10. Security
- Vault content is encrypted at rest in the app's private storage area on your device
- All Firebase transmissions use encrypted (HTTPS/TLS) connections
- Access to Firebase analytics and crash dashboards is limited to authorised Orixa Studio personnel
Device-level protections matter too: keeping a screen lock enabled and keeping your operating system up to date meaningfully protects your vault. No application or system can be guaranteed 100% secure.
11. Data Retention
- On-device content: retained until you delete it in the app, clear the app's data, or uninstall SafetyCam. You are in full control of it.
- Analytics data: retained according to the retention period configured in Google Analytics for Firebase.
- Crash data: retained according to the Firebase Crashlytics retention period.
Uninstalling SafetyCam removes the app's local vault and its contents from your device. Please export anything you need to keep before uninstalling, because deleted vault content cannot be recovered by us.
12. Your Rights and Choices
- Access or deletion: you may request information about, or deletion of, applicable analytics and diagnostic data by emailing [email protected]. We may ask for information reasonably needed to identify the applicable records.
- Permissions: you may revoke camera, microphone, location, notifications, accessibility, display-over-other-apps access, or the battery-optimisation exemption at any time in your device settings.
- Reset identifiers: clearing SafetyCam's app data or uninstalling and reinstalling the app resets the Firebase installation identifier associated with your install.
- Stop all collection: uninstalling SafetyCam ends all analytics and crash reporting from your device.
Depending on where you live, you may have additional rights under laws such as the GDPR or the DPDP Act, including the right to object to or restrict processing. Contact us at the address above and we will respond within the period required by applicable law.
13. Google Play Data Safety Summary
This section is published so it matches the Data Safety form declared for SafetyCam in the Google Play Console.
Data collected and transmitted off the device
- App activity — app interactions: collected automatically, not shared, and used for analytics
- App info and performance — crash logs and diagnostics: collected automatically when a crash, ANR, or related stability event occurs, not shared, and used for analytics and app functionality (stability)
- Device or other IDs — installation identifier: collected automatically, not shared, and used for analytics and diagnostics
Data handled only on the device
- Photos and videos: processed and stored on-device only, never transmitted
- Audio recordings: processed and stored on-device only, never transmitted
- Location: optional, processed and stored on-device only, never transmitted
Security practices
- Data is encrypted in transit
- Vault content is encrypted at rest on the device
- You can request deletion of applicable analytics and diagnostic data
SafetyCam does not share any of the above categories with third parties for advertising, and does not sell user data.
14. Children's Privacy
SafetyCam is designed for users aged 13 and older and is not directed to, or intended for use by, individuals under 13 years of age. We do not knowingly collect personal data from children under 13. Users aged 13 to 17 should use SafetyCam with the involvement of a parent or legal guardian where required by applicable law. If you believe a child under 13 has used SafetyCam and that diagnostic data was collected, contact us at [email protected] and we will delete the applicable records.
See also our Child Safety and CSAE Policy.
15. Changes to This Policy
We may update this Privacy Policy to reflect changes to SafetyCam, to the third-party services it uses, or to our legal obligations. The revised policy will be published on this page with an updated "Last Updated" date. Material changes affecting how data is collected or used will also be reflected in the app's Google Play Data Safety declaration.
