ExitLine Privacy Policy
ExitLine is built around on-device scheduling and simulated call-style presentation. This policy explains what the app stores locally, how Android delivery features work, and how advertising, crash diagnostics, and privacy controls fit into the experience.
Information ExitLine uses
- Caller profiles, custom scripts, app preferences, scheduled-call details, and recent session history created inside the app.
- Notification, alarm, and delivery state needed to schedule incoming-call alerts, present call-style screens, and restore pending scheduled calls after device restart.
- Standard device and app information needed to deliver the service, such as app version, device type, and diagnostics generated by the operating system or advertising SDKs.
- Crash and stability diagnostics that may be processed by Firebase Crashlytics, such as stack traces, app version, Android version, device model, and crash session identifiers when the app crashes or encounters serious runtime errors.
- Advertising-related data that may be processed by Google AdMob, such as advertising identifiers, approximate location, performance data, and interaction signals, subject to your region and privacy choices.
How information is used
- To save your caller setup, timing preferences, and recent activity on the device.
- To schedule and present incoming-call alerts, call-style screens, and optional cue cards when a session is triggered.
- To restore pending scheduled calls after device restart when Android restart handling is available.
- To monitor crashes, ANRs, and stability issues so the app can be diagnosed and improved on affected devices and Android versions.
- To support advertising, ad measurement, fraud prevention, and platform compliance when ads are enabled.
Data stored on your device
ExitLine stores caller profiles, settings, scheduled events, and recent activity locally using on-device app storage. ExitLine does not require account creation and does not ask for contacts, microphone, call log, SMS, or phone-state permissions to provide its core experience.
If you schedule a call, the pending event and related delivery state may remain on your device until the event is completed, canceled, app data is cleared, or the app is uninstalled.
Android permissions and delivery features
On Android, ExitLine may request notification permission so scheduled incoming-call alerts can appear when the app is not on screen.
- Notification permission supports background incoming-call alerts on Android 13 and higher.
- Exact alarm access improves timing precision for scheduled calls.
- Full-screen incoming-call presentation improves lock-screen delivery on supported Android devices.
- Boot-completed handling restores pending scheduled calls after device restart.
Advertising, crash diagnostics, and third parties
ExitLine uses Google Mobile Ads (AdMob) to request and display ads. Google may process data under its own privacy terms in order to serve, limit, and measure advertising.
ExitLine also uses Firebase Crashlytics to receive crash reports, non-fatal error reports, and Android ANR diagnostics. These reports help identify device-specific failures, operating-system issues, and stability regressions.
Where required by law or policy, ExitLine requests consent before personalized advertising is used and provides a privacy-options entry point when Google requires one.