Privacy Policy for CarryLogic

Record of processing

This document explains categories, not every internal class name. It is provided by Melati Kusuma.

Data Controller

Melati Kusuma
Indonesia

Categories we expect in a typical build

• User-created content: text, structured entries, flags, and files you add inside CarryLogic.
• 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.

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.
• Revoke optional OS permissions (notifications, photos, calendar, and similar) in system Settings; the app then degrades the matching feature instead of demanding the permission to launch.
• Use Apple ID purchase history and App Store refund tools for store commerce questions.

If a regional privacy law gives you a right to access or erasure for data we actually hold, contact the address in the contact block when that block is shown. For data that exists only on your device, the in-app delete path and uninstall are the practical mechanisms.

Changes

We may update this policy. Changes will be posted here with an updated date. If the contact block below is empty, use the App Store listing's support link once it is attached to the same public pages.

Contact