Privacy Policy for PO - Exit Timeline

Record of processing

This document explains categories, not every internal class name. It is provided by Renato Goulart.

Data Controller

Renato Goulart
Brazil

Categories we expect in a typical build

• User-created content: text, structured entries, flags, and files you add inside PO - Exit Timeline.
• Local preferences: theme, sorting, onboarding completion, and similar switches stored on device.
• Purchase entitlements: if paid features exist, a local flag that a product was unlocked, without card numbers.
• Diagnostics Apple may collect: crash or performance data only when you have opted into Apple's sharing mechanisms.

Connectivity

The app may make network requests to retrieve app content or configuration, communicate with Apple platform services, and open support or legal resources. A feature that sends user-entered information to an external service should identify that behavior in its interface. App Store privacy disclosures for the submitted version provide the applicable data categories.

Safeguards

PO - Exit Timeline relies on the OS sandbox, transport security for any HTTPS calls, and Apple's signing/distribution channel. You still need a device passcode or biometric lock to protect local records at rest as well as the OS allows.

Your controls

Use an available in-app deletion control to remove content created in the app. Uninstall the app to remove data stored only in its local container. If you believe a build is collecting more than this notice describes, include the build number from the app's about screen when you write to the contact address.

Closing

We may update this policy. Changes will be posted here with an updated date. This notice should be read with the Terms of Use and the in-app about screen.

Contact