Privacy

Loopy Privacy Policy

Effective date: July 7, 2026

Loopy helps users complete guided CBT-style thought reframing exercises. This policy explains what information the app collects, how it is collected, every way it is used, which third parties receive it, and how to contact us with privacy questions.

Information stored on your device

Completed cards, onboarding state, and basic app state are stored locally on your device so you can continue using the app and revisit past thought shifts.

Information sent to our backend and AI provider (DeepSeek)

Nothing you write is sent anywhere until you explicitly allow AI processing inside the app. Loopy asks for this permission before your first guided session, and again at the moment you start a session if you previously declined. If you decline, the text you type stays on your device.

If you allow AI processing, the following data is sent when you use the guided coaching flow:

We do not design the service to keep a long-term archive of completed conversation bodies on the backend after processing. Standard hosting and operational logs may still exist for reliability and security purposes.

Optional research sharing

If you explicitly opt in inside the app, Loopy may upload partial or completed thought-reframe sessions to our database so we can review what people use the product for, where they get stuck, and how well the CBT flow is working.

These research uploads are linked to a random app-generated identifier instead of an account. They can include the session text, reframe fields, completion state, timestamps, and product-plan status. If you leave research sharing off, this database storage does not happen.

Analytics and diagnostics

When analytics is configured for a production build, Loopy may send basic product-usage events such as screen views, button taps, session progress, paywall interactions, and subscription-tier status to Google Firebase Analytics so we can understand feature usage. Firebase Analytics uses a pseudonymous app-generated instance identifier together with general device and usage data (such as device model, operating system version, and coarse region). These analytics events do not include the text of your thoughts or reframes.

To find and fix crashes, errors, and reliability problems, Loopy may also send crash reports, error reports, and diagnostic or performance context — such as the device model, operating system version, app version, and the technical details of a crash — to Sentry. Sentry is configured not to attach personal data, screenshots, or your written content.

Notifications

If you allow notifications, Loopy can schedule a local daily reminder on your device. You can change this permission later in iOS Settings.

Purchases and subscriptions

Subscriptions and purchase state are handled through Apple and RevenueCat. RevenueCat may process identifiers and subscription-related data needed to validate purchases, restore access, and manage entitlements.

How we use information

What we do not do

Your choices

You can delete locally stored cards by removing them inside the app, and you can remove app data from your device by uninstalling the app. If you opt in to research sharing, you can turn future uploads off inside the app at any time. Subscription management is handled through your Apple account settings.

Contact

For privacy questions or research-data deletion requests, email hakangun@icloud.com.

View Terms of Use