Last updated: August 24, 2026
OutLoud does not collect, sell, share, or use personal data for tracking.
OutLoud stores the user’s settings, chosen phrases, protection state, automatic return mappings, and temporary challenge state in an on-device App Group container shared only by OutLoud and its Screen Time extensions.
Apps and websites selected through Apple’s Family Controls picker are represented by opaque system tokens. OutLoud does not receive their names and does not transmit those tokens off the device.
OutLoud requests Microphone and Speech Recognition access only while a spoken pause is active. Audio and recognized text are not stored by OutLoud, sent to the developer, or used for analytics or advertising. Speech processing is provided by Apple’s operating-system frameworks and is subject to Apple’s software and privacy terms. OutLoud requires on-device recognition and does not fall back to server speech processing. Own words acknowledgment matching uses a Core ML classifier and vocabulary bundled with OutLoud. Classification requires no language-asset download; spoken text remains on the device and OutLoud does not call an external AI service.
On iOS versions before 26.5, OutLoud may request notification access to provide a user-initiated bridge from Apple’s Screen Time shield to the app. On newer releases, the shield can open OutLoud directly. If you choose a usage-reminder interval, OutLoud also uses local, time-sensitive notifications at each matching milestone in a selected app’s cumulative foreground time for the current day. The total continues across visits and resets daily. These reminders operate independently of protection until you turn them off, and their timing is processed on device. The optional Shortcuts automation invokes an on-device action that re-applies protection; it does not contact a server.
OutLoud contains no analytics SDK, advertising SDK, account system, backend service, or third-party tracking technology.
If OutLoud’s data practices change, this policy and the App Store privacy disclosure will be updated before the affected version is released.
For privacy questions, open an issue in the OutLoud support repository.