Privacy Policy

This Privacy Policy explains how Angela handles information when you use the Angela mobile application.

Last updated: October 17, 2026

Back to Angela · Terms and Conditions

1. Who We Are

Angela is a personal safety app that listens for a user-defined phrase on the device and can run user-selected safety actions such as local alerts, flashlight strobe, and trusted contact messaging.

Angela is developed and operated by Angela Technologies LTD, a company incorporated in Israel with company number 517414009 (“we,” “us,” or the “Company”). The Company is responsible for the personal information it processes as described in this policy.

Support email: [email protected]
Privacy email: [email protected]

2. Information Angela Uses

Angela may access the following categories of information:

  • Microphone and speech recognition data to detect your chosen phrase.
  • Contacts if you choose trusted contacts for alerts.
  • Location if you enable location sharing for alerts.
  • Notification permission if you enable local alerts.
  • Camera/flashlight access if you enable the flashlight strobe action.
  • App configuration data such as your phrase, alert settings, trusted contact phone numbers, and alert message.
  • Optional onboarding answers such as an age range, situations where Angela may be useful (including domestic violence), and relevant communities (including LGBTQ+, Arab society, disability, chronic health conditions, and economic hardship). These answers can reveal sensitive information.
  • Feedback you submit, including a rating, category, and any details you choose to write.
  • Usage information, technical diagnostics and crash reports through Google services, as described below.

Angela uses a random installation ID to connect the usage information, technical diagnostics and crash reports you choose to share. This helps us understand problems across app sessions. When you enable more than one sharing choice, it can also connect the corresponding data categories with one another. The ID is not a hardware ID and does not contain your name or contact details. Reports associated with it are not necessarily anonymous. Google services may also use their own identifiers.

Optional survey answers are kept separate from usage information, technical diagnostics, and crash reports. A separate private code stored on your device lets the survey service update your answers without an account. This code is not used as the installation ID for shared diagnostics. Feedback submissions contain neither this survey code nor Angela’s diagnostics installation ID.

3. How Angela Processes Audio

Angela processes live audio on your device to detect your configured phrase. Angela does not send microphone recordings or speech transcripts to Angela’s servers or Firebase for phrase detection. Temporary audio buffers and recognition results are used for detection and are not saved as recordings by Angela. Angela does not persist a history of detected speech or recognition transcripts. Your configured safety phrase is stored separately as part of your app configuration.

Angela requests microphone access only so it can listen for the phrase you configure. On supported devices, this may continue while the app is active or while a background listening session is running.

4. Contacts, Location, and Safety Actions

  • Contacts: Angela uses contact access so you can select trusted contacts. The app stores the trusted contact phone numbers you choose in local app configuration and does not store your full address book remotely.
  • Location: If you enable location sharing, Angela attempts to obtain your current location for an alert. Availability and accuracy depend on your phone, permissions, and surrounding conditions. The location may be approximate or the last known location available to your phone, which may no longer reflect where you are. Location sharing is optional. On Android, this can include accessing location during a background listening session when you enable location in alerts and grant the necessary permissions.
  • SMS alerts: If you enable trusted-contact messaging, Angela can send an SMS on supported Android devices and uses Apple Critical Messaging on supported iOS devices. An alert may include the message you configured and, if you enable location sharing, a map link containing the available location described above. Your operating system, carrier or messaging provider, and recipients process the message and its contents. If a recipient opens the map link, the map provider may process the location in that link.
  • Local notifications and flashlight: These actions run locally on the device when enabled by you.

Once a voice or manual trigger occurs, Angela attempts the safety actions you have enabled without asking for further confirmation for each action. Required permissions and platform restrictions still apply. An attempted action does not guarantee successful execution or message delivery.

5. Usage Information, Technical Diagnostics and Crash Reports

You can separately choose to share usage analytics, technical diagnostics, and crash reports to help improve Angela and fix failures. All three choices are off in a new installation. You can change them in Settings. Declining any choice does not prevent you from using Angela’s safety features.

  • Firebase Analytics: If you opt in, Angela sends app usage events such as when Angela is opened or returned to the foreground, screen names and time spent, permission request outcomes, onboarding completion, feature and settings choices, and safety workflow action types and outcomes. The app-open event is about Angela only. Angela does not track which other apps you open or which apps are installed on your device. Angela uses the diagnostics installation ID described in Section 2 when the disclosed correlation is enabled, so these events can be associated with the same app installation. Events do not include your configured phrase, contact names or phone numbers, alert text, message contents, or precise location. Firebase may also process technical app, device, and installation information as described in Google’s documentation.
  • Technical diagnostics in Google Cloud: If you enable technical diagnostics and a diagnostics destination is configured, Angela sends technical logs, traces, operation timings, and metrics to Google Cloud through an Angela-operated gateway. These help us investigate reliability and performance. They can include listening start and duration measurements, phrase-detection events indicating whether detection occurred during a phrase test, permission and operation outcomes, error types and stack traces, and app, device, operating-system, and language details. These are examples, not an exhaustive list. The app, operating system, and provider SDKs may generate other operational attributes as technical needs change. Diagnostics include information from the Flutter app and native Android or iOS components. Session and trace identifiers connect activity within a run; the diagnostics installation ID also connects app logs and traces across runs. Listening metrics do not automatically receive that persistent installation ID, but their session and device context can still be linkable.
  • Firebase Crashlytics: the app can send crash and diagnostic information to help identify failures. The app’s code is intended to limit custom crash metadata and not include audio, contacts, messages, phrase text, or live location in crash-report custom keys.

When you opt in to crash reporting, reports may contain crash details, stack traces, app version, device or installation diagnostics, technical breadcrumbs, and safety-action outcomes. Session and eligible trace identifiers can connect reported errors with technical diagnostics. The diagnostics installation ID can also connect crash reports across sessions. Angela does not intentionally add microphone audio, speech transcripts, phrase text, contacts, message contents, or precise location to usage events, technical diagnostics, or Crashlytics custom fields. Stack traces and native crash reports can contain additional technical information, such as file paths. These reports are not a record of what you said, and a phrase-detection event does not establish that an emergency occurred.

Firebase Analytics, Crashlytics, App Check and Google Cloud are Google services. App Check is also used to help validate requests to Angela’s services. App Check processes app and device attestation information independently of the optional usage, technical diagnostics, and crash choices to help protect service requests. Angela’s demographics and feedback services are hosted on Cloudflare Workers and store submissions in Cloudflare D1 databases. See Cloudflare’s privacy policy. Google’s privacy policy is at policies.google.com/privacy. We require providers that process information for Angela to protect it consistently with this policy and applicable privacy requirements. Their own policies also describe their practices.

6. Optional Answers and Feedback

If you choose to answer the optional onboarding questions, Angela sends your selected age range, useful situations, and relevant communities to an Angela-operated service supported by hosting providers. A separate private survey code authorizes your submission. The survey service stores a hash of that code as the reference for updating the same response if you submit answers again. The code and its reference are separate from the diagnostics installation ID. Survey answers are not joined to usage or crash reports. Skipping the questions sends no answers. We use these answers to understand the needs and situations of people who use Angela and to guide improvements to the app.

If you submit feedback in the app, Angela sends your chosen rating, category, written details, app language, platform, source screen to Angela’s feedback service. Feedback records are stored without Angela’s diagnostics installation ID or private survey code. We use feedback to understand reported problems and suggestions and improve Angela. Do not include information you do not want Angela to receive in feedback text. The text you write may identify you or another person even though the feedback record does not contain either of those identifiers. Hosting providers support the demographics and feedback services and may process request and network information to operate and protect those services.

Angela does not keep raw IP addresses or general network-activity logs in its demographics and feedback databases. To limit repeated submissions, these services process the request IP address and store a hash derived from it and a time window, together with request counts and timestamps. These abuse-prevention records are separate from submitted answers and feedback. This is distinct from any processing by hosting providers described above.

Answering these questions and submitting feedback are voluntary; you are not required by law to provide them. Skipping either does not prevent you from setting up or using Angela’s safety functions.

7. Where Information Is Stored

Angela stores app configuration data locally on the device.

This local data may include your configured phrase, trusted contact names and phone numbers, alert message and enabled safety actions. The diagnostics installation ID is stored separately in app-private storage excluded from backups. The private survey code uses separate storage: app-private storage excluded from backups on Android and a device-only, non-synchronizing Keychain item on iOS. An iOS Keychain item may survive uninstalling the app.

Angela may also keep pending safety-action status locally so it can show action results and let you acknowledge them after the app reconnects or restarts. This status does not include detected speech or recognition transcripts and is separate from your configuration. Angela does not keep a persistent detected-text incident history.

Optional onboarding answers and submitted feedback are stored by Angela’s demographics and feedback services using hosting providers. Usage and crash information are sent to Firebase; technical diagnostics are sent to Google Cloud as described in Section 5. Angela does not operate a user account system.

Angela uses HTTPS to protect information sent between the app and its online services. App configuration, the diagnostics ID and survey code are kept in the device storage described above. The protection of data stored on your device also depends on your device security settings and who can access the device.

8. When Information Leaves Your Device and Is Shared

Audio processing, your safe phrase, and trusted-contact settings stay on your device. Optional data sharing is explained separately in this policy. Contact details needed to deliver an alert are handled by the relevant delivery service as described in Section 4. We do not sell your personal information.

In normal use, the main times information leaves your device are:

  • Firebase Analytics and Crashlytics receive app analytics and crash diagnostics when you opt in to the respective service.
  • Angela’s services receive optional onboarding answers and feedback when you choose to submit them. Hosting providers support both services.
  • Google Cloud receives technical logs, traces, timings, and metrics through Angela’s gateway when you enable technical diagnostics and a destination is configured.
  • Service authentication uses Google App Check and its attestation providers to validate requests independently of optional usage analytics, technical diagnostics, and crash sharing.
  • Trusted-contact alerts are sent from your device when enabled and triggered by voice or manual activation, without a further confirmation prompt. Those messages are then handled by your operating system, mobile carrier, SMS provider, and recipients.

We may also share aggregate demographic statistics, such as combined counts and percentages, with third parties to help understand community needs and improve Angela. This sharing is limited to statistics that meet the conditions in Section 9; it does not include individual demographic records or app-installation identifiers. Processing of individual records by service providers on Angela’s behalf is described separately in Sections 5 through 7.

9. Data Retention and Deletion

Local settings remain on your device until you change or remove them. The separate survey code may survive uninstalling the app on iOS, as explained in Section 7.

We have not set a fixed automatic deletion deadline for optional onboarding answers. Turning sharing off or uninstalling Angela does not by itself delete information already received. This does not override earlier deletion commitments or the service-specific retention rules below.

We retain personal information while it remains necessary for the purposes explained in this policy or another applicable legal requirement. We review that need at least annually. Information that is no longer justified is deleted or made anonymous, subject to applicable legal requirements. No automatic expiry date does not mean that we keep every record forever.

We may keep and share combined demographic counts and percentages for longer if they cannot reasonably identify anyone or be linked back to an individual installation. Removing an identifier alone does not necessarily make information anonymous.

Submitted feedback is scheduled for deletion from active systems once it is at least 60 days old. Cleanup runs daily; a failed run can delay deletion until a subsequent successful run. Recovery copies and manual exports may have separate retention periods.

Google Cloud's current logging configuration retains ordinary logs for 30 days and required audit logs for 400 days. These periods describe the log buckets, not every diagnostic signal or possible exported copy. Traces and metrics have separate provider retention rules. See Cloud Trace retention and Cloud Monitoring retention.

Firebase Analytics and Crashlytics have their own retention controls. The absence of an Angela-set deadline does not override those controls. See Google Analytics retention documentation and Firebase privacy documentation.

If you supplied information under an earlier notice that promised a particular deletion period, this policy does not by itself extend that period. We will explain material changes and obtain any consent required before applying them to that information.

Subject to applicable law, you have the right to access personal information about you held by Angela and to request correction of information that is inaccurate, incomplete, unclear, or outdated. You can also request deletion of optional onboarding answers, feedback, or other personal information Angela controls. Send these requests to [email protected]. Describe the information and, if possible, when or how you submitted it so we can locate it. Do not send sensitive information unless needed to identify it. Because Angela does not have user accounts, we may need additional information to locate the relevant record and verify that you are entitled to access or change it. Survey access depends on the separate private code; losing that code can prevent us from verifying ownership of a particular response. Feedback is not stored against the diagnostics installation ID or survey code, so those identifiers alone cannot locate your feedback. We may be unable to act on a particular record if we cannot locate it or verify your connection to it. Requests involving Firebase data are handled using the controls available for those services. Uninstalling Angela does not by itself delete information already sent to Angela, Firebase or Google Cloud. The survey Keychain item on iOS may also survive uninstalling.

10. Your Choices

  • You can deny or revoke microphone, contacts, location, notification, camera, and SMS permissions in your device settings.
  • You can change or remove trusted contacts, alert text, and optional safety actions from within the app.
  • You can choose separately whether to share usage analytics, technical diagnostics, and crash reports, and turn each option off in Angela’s settings. Turning collection off does not by itself delete information already sent; the retention rules in Section 9 still apply. Turning all three sharing choices off resets Angela’s diagnostics installation ID for future collection. If you enable sharing again, Angela creates a fresh ID. Turning off only one choice does not reset the ID while another remains enabled. These controls do not promise to reset identifiers maintained by Google’s SDKs or to anonymize records already received.
  • You can skip the optional onboarding questions and choose whether to submit feedback.
  • You can exercise applicable access and correction rights and request deletion using the privacy contact above, as explained in Section 9.
  • You can stop using Angela and remove local data by uninstalling the app.

11. Children’s Privacy

Angela is intended for people aged 13 and older. People aged 13 to 17 may use Angela only with the consent and supervision of a parent or legal guardian, as described in the Terms of Use. The optional onboarding age-range choices include “Under 18,” but Angela does not ask for a birth date. Children under 13 should not use Angela or submit information through the app. If you believe a child under 13 has provided information through the app, contact us so we can review the issue and address deletion.

12. Processing Outside Israel

Angela’s service providers may store or process information outside Israel, including when you use the app in Israel. The location of processing depends on the service and its hosting arrangements. Those countries may have different data protection laws from Israel or your location. Applicable requirements for transferring and protecting personal information continue to apply.

13. Changes to This Policy

We may update this Privacy Policy from time to time. We will post the updated version on this page and update the “Last updated” date. Minor corrections, such as fixing typos or clarifying wording without changing our practices, will not require renewed acceptance. We will notify you of material changes through the app or another appropriate channel before they take effect. Before collecting new categories of optional data or using optional data for new purposes outside your existing consent, we will explain the change and ask for fresh consent. We will also seek renewed consent where required by applicable law.

14. Contact

For privacy questions or requests, contact: [email protected]