Apps · Introva · Privacy

Privacy Policy

Effective 11 September 2026

Introva (the "App") is a private journaling app published by Taoufik Jabbari ("we", "us"). Introva lets you log your day by text or voice and turns your entries into a weekly report. This policy explains what data the App collects, how it is collected, who receives it, and your choices. It applies to the iOS and Android versions of the App.

1. What we collect

This list matches the data types declared on the App's store listing. "Linked to you" means the data is stored together with your account. None of these data types is used for tracking.

• User ID (linked to you): the account identifier Firebase Auth assigns to you when you sign in. It is the key under which your entries, reports, settings and push tokens are stored on our server. Used for app functionality.
• Email address (linked to you): the address you sign in with, or the private relay address Apple gives us if you choose "Hide My Email". If you join the waitlist before you have an account, the email address you type in is stored on the waitlist. Used for app functionality: signing you in, and telling you when a waitlist spot opens.
• Name (linked to you): the full name Sign in with Apple or Google sign-in hands over, stored by Firebase Auth as the display name of your account. Our own server does not store it. Used for app functionality.
• Other user content (linked to you): your journal entries (typed or transcribed from voice), the mood you attach to them, the weekly reports generated from them, and the profile file the report builds on from week to week. Used for app functionality.
• Device ID (linked to you): the push notification token (APNs on iOS, Firebase Cloud Messaging on both platforms) stored on your account so the App can tell you that a report is ready, and, if you join the waitlist, that a spot has opened. Firebase Analytics also reads an app instance identifier and, on iOS, the identifier for vendor, and Firebase creates an installation identifier for the App on your device. Used for app functionality and analytics.
• Product interaction (not linked to you): the standard usage events Firebase Analytics records automatically, such as screens opened and sessions started. Used for analytics.
• Coarse location (not linked to you): Firebase Analytics derives an approximate location (country or city) from the IP address of the request. The App never uses Location Services, never asks for location permission and never collects a precise location. Used for analytics.
• Crash data (not linked to you): crash reports collected by Firebase Crashlytics, with the device model, operating system version and the state of the App at the moment of the crash. Used for app functionality.
• Other diagnostic data (not linked to you): technical metadata the Firebase SDKs send outside crash reports, such as device model, operating system version, App version, network type, SDK versions and session timing, and the App Check attestation (Apple App Attest on iOS, Play Integrity on Android) that proves requests to our server come from a genuine copy of the App. Used for app functionality and analytics.
• Other data types (linked to you): your time zone identifier and the hour you chose for the daily reminder, stored on your account so entries are dated in your local time and the report is generated at the right moment for you. The time zone is also given to the report generator. Used for app functionality and analytics.

2. How we collect it

• Sign-in: when you sign in with Apple or with an email address and password (iOS), or with Google (Android), Firebase Auth receives the credential and gives us your user ID, email address and, for Apple and Google sign-in, your name.
• Journaling: entries and moods are sent to our server over HTTPS when you save them and stored encrypted at rest with AES-GCM.
• Voice entries: when you record a voice entry, the microphone is used only while you hold the mic on, and the audio is transcribed by the speech recognition service of your device (Apple speech recognition on iOS, the device's speech service on Android, usually Google). Depending on the device and language, that service may process the audio on its own servers. We receive only the resulting text; we never receive or store the audio.
• Waitlist: if the App is full, the waitlist screen sends the email address you type in, together with a push token if you allow notifications, to our server before any account exists.
• Push notifications: if you allow notifications, the App registers with Apple (APNs) or Google (Firebase Cloud Messaging) and sends the resulting token to our server. The notifications themselves ("Your weekly report is ready", "Your spot is open") contain no journal content.
• Settings: your time zone and reminder hour are sent to our server when you finish onboarding and each time you sign in.
• Automatically: analytics events, crash reports and diagnostic metadata are collected by the Firebase SDKs while the App runs.
• App lock: the optional Face ID, Touch ID or biometric lock is checked by your device's operating system. We never receive biometric data.
• Payment: the App Store or Google Play charges the price of the App. Apple and Google never share your card details with us, and we receive nothing about the purchase.

3. Third parties

We share data only with the processors below, each for the purpose stated. We never sell your data.

• Apple (Sign in with Apple, App Store): receives your sign-in on iOS and hands us your name and email address or relay address. Apple speech recognition may process the audio of voice entries on iOS. Apple Push Notification service delivers notifications. Apple handles the purchase of the App and does not share card details with us.
• Google (Google sign-in, Google Play): on Android, Google sign-in hands us your name and email address, the device's speech service may process the audio of voice entries, and Google Play handles the purchase of the App without sharing card details with us.
• Google Firebase Auth: stores your user ID, email address, name and sign-in credential, and issues the token the App uses to talk to our server.
• Google Firebase Analytics: receives usage events, the app instance identifier (and the identifier for vendor on iOS), diagnostic metadata and the coarse location derived from the IP address. No precise location: the App never uses Location Services.
• Google Firebase Crashlytics: receives crash reports, device model and operating system version.
• Google Firebase Cloud Messaging and Apple APNs: receive the push token and deliver notifications.
• Google Firebase App Check: receives the Apple App Attest or Play Integrity attestation that proves requests come from a genuine copy of the App.
• Our own server (hosted in Germany): stores your user ID, email address, time zone, reminder hour, push tokens, waitlist entry, and your encrypted entries, moods, reports and profile file.
• Anthropic (Claude): receives, once a week, the journal entries of the week, your profile file and your time zone, and returns the report. It receives no name, no email address and no account identifier.

4. How the AI report is made

A computer we operate (the "report computer") connects to our server every hour and downloads the new entries, moods and profile file of every account, decrypted, so that the weekly report can be built. It keeps them as plain text until the report is made. Once a week, after Sunday 9:00 in your time zone, the entries of the week are sent to Anthropic (Claude) together with your profile file and your time zone, and the resulting report and updated profile file are stored encrypted on your account. Anthropic receives no name, no email address and no account identifier; the request is made from a Claude session with no tools and no access to files.

Once the report is stored on our server, the entries it was built from are deleted from the report computer; entries written after the cutoff are kept for the next report. If no report could be made that week (too few entries, or a report our checks rejected), the entries stay there until a later run succeeds. The profile file and past reports are kept on the report computer so the next report can build on them. Everything under your account on the report computer is deleted at the run that follows a "Delete my data" or "Delete my account" request.

5. Your choices and consent

• Notifications: the App asks once, during onboarding (or on the waitlist screen if the App is full). You can change your answer at any time in your device settings; without permission no push token is created.
• Microphone and speech recognition: asked only when you start your first voice entry. Typed entries work without them.
• App Tracking Transparency and advertising identifiers: the App shows no ads, does not use the advertising identifier on iOS or Android, and does not track you, so no tracking prompt is shown.
• Analytics: Firebase Analytics runs in the App without a separate opt-in; its events are not linked to your account and contain no journal content.

6. Retention and deletion

Your entries, moods, reports, profile file, settings and push tokens are kept for as long as your account exists. From the App's Settings you can, without contacting us:

• Download my data: exports your entries, reports, profile file and account settings (email address, time zone, reminder hour) as a file you can save or share.
• Delete my data: deletes every entry, report and profile file from our server and from the report computer, while keeping your account and sign-in.
• Delete my account: deletes everything above plus your push tokens, removes your email address from the account row and deletes your sign-in from Firebase Auth. Two things remain: the account row itself, marked deleted and reduced to your user ID, time zone, reminder hour and creation date (so that the same account can be recognised and reactivated if you sign in again), and a log line with a hashed form of your user ID and the date of the deletion. Neither contains your name, email address or any content.

Individual entries can be deleted at any time in the App. A deleted entry disappears from the App and is no longer sent to the report computer, but its encrypted row stays in our database until you delete your data or your account, and a copy that had already reached the report computer that hour may still be read by that week's report. "Delete my data" and "Delete my account" take effect on our server immediately; the copy on the report computer is removed at its next hourly run. A waitlist entry (email address and push token) is kept on the waitlist table until you ask us to remove it by email. Crash and analytics data are retained by Google under the Firebase retention settings and are not tied to your journal content. You can also email goloio32@gmail.com for any deletion or export request.

7. What we do not do

• We do not keep the audio of your voice entries; only the transcribed text is stored.
• We do not use Location Services or collect a precise location. The only location data is the approximate location Firebase Analytics derives from the IP address, and it is not linked to your account.
• We do not access your contacts, photos or calendar.
• We do not collect health data (no HealthKit, no Health Connect, no fitness or medical records).
• We do not show ads, do not use advertising identifiers, and do not track you across other companies' apps or websites.
• We do not sell your data.

8. Children

Introva is not directed at children under 13, and we do not knowingly collect data from them. If you believe a child has created an account, contact us and we will delete it.

9. Not therapy

Introva is a journaling and self-reflection tool. It is not therapy, not a medical device, and not a substitute for professional mental health care. If you are in crisis or need medical advice, please contact a qualified professional or your local emergency services.

10. Changes to this policy

When we change this policy we update the effective date at the top of this page. Continued use of the App after a change means the updated policy applies.

11. Contact

Questions or requests, including data deletion or export: goloio32@gmail.com.