Privacy, in plain language.

Updated October 12, 2026

Hablobi is a Qur'an companion, a recitation-grown garden and a place to give cards and flowers. This policy describes information used by the app and our website.

Your Garden microphone

Reading progress and levels

Hablobi saves reading progress to your Hablobi account so XP, levels and level unlocks can stay in sync. Records include the surah, ayah, counted word positions, reading pass, reading date and award time. These are activity records, not voice recordings or uploaded recognition transcripts. Accepted friends can see your level on your profile card; that view does not expose your detailed reading history. Shared-garden members can see their garden’s shared progress and turns.

Grow with Friends

Shared gardens use the same on-device recitation processing as your solo Garden. We store the garden name, invitations, membership and join order, turn assignments, accepted ayah, who accepted it and when, completion and collection records, and the bouquet and its growers. Members see shared progress and whose turn is next. No live audio, recording or recognition transcript is sent to other members or uploaded for this feature.

Older app versions may still offer the separate LiveKit voice-room feature: enabling its microphone transmits your voice to other participants and uses your account identity and room information to connect you. Existing account and room records are covered by the retention and deletion provisions below.

Account and what you share

Account: your email address, sign-in provider identifier, display name, handle and account ID. Apple or Google supplies the information you authorize when you use its sign-in option. Your profile can include your chosen Blobi appearance and its generated portrait.

Cards, flowers and companions: we store the content you send, card composition and written message, sender and recipient details, gift status, relationships, and delivery or opening records so gifts, conversations, flower history and keepsakes work. Recipients receive what you choose to share. Reports and blocks are processed for safety and support.

Religious activity: the app's content and records, such as Qur'an references you share or flowers grown from particular surahs, can reveal information about religious practice. We use these records to provide the features you chose, not to rank your faith.

Purchases, notifications and downloads

Apple handles payments. We receive subscription status and transaction information to provide Plus access, restore purchases and reconcile purchases. We do not receive your payment-card details.

To measure our Apple Ads campaigns, supported app versions request an attribution token from Apple after sign-in. Our server exchanges it with Apple for available campaign, ad group, keyword, country or region, and ad interaction information. We associate the result with your Hablobi account and verified purchase records to understand which campaigns lead to subscriptions. We do not collect IDFA, precise location, contacts or recitation content for this purpose. The raw attribution token is not retained. Attribution records are deleted with your account.

We store Garden openings, surah and generation, completion status, opening time and early-opening credits. Invitation-reward records include the account identifier and a unique completed-share event to prevent duplicate awards. These records are not voice recordings.

Optional rewarded ads

In versions that offer rewarded ads, you can choose to watch an ad to open another Garden instead of waiting. Plus members do not need these ads. We use Google AdMob and request non-personalized ads. Non-personalized does not mean no data is processed: Google's advertising SDK may process your IP address and approximate location, app or device identifiers, ad views and interactions, and diagnostic and performance information to deliver, measure and secure ads. We do not supply your Garden audio, recognized words, surah history, religious-interest profile or Hablobi account identifier to advertisers. See how Google uses information from apps that use its services.

Before requesting ads, we use Google's consent tools to present applicable choices. Where required, you can revisit them through Ad privacy choices in Settings. We do not request permission to access your iPhone advertising identifier for this feature. Availability can vary by region, consent choice and ad supply.

To prevent duplicate or forged rewards, our server creates a random one-use ticket linked to your account and sends only that ticket to Google with the ad. Google returns a signed reward confirmation containing the ticket, transaction identifier, ad unit, reward and time. We store the ticket and confirmation to credit your account once. Account-linked tickets are deleted when your account is deleted.

Invitation links go to the App Store. We do not read your clipboard, fingerprint devices or use an advertising-attribution SDK for invitations. The app uses the sharing service’s completion result; that result does not prove delivery or identify a unique recipient.

If you allow notifications, we store your device's push token and notification preferences to deliver relevant messages, gifts and shared-garden invitations, turns and completion notices. Delivery records, retry status, device-token hashes and seen/read receipts help avoid duplicate or stale notices. These records are separate from recitation audio. You can change notifications in the app and in iPhone Settings.

Card artwork, backgrounds and flower models download from our Supabase storage as needed and are cached on your device. Recitation playback also requires requests to audio providers. Hosting and delivery services process network information such as your IP address and request details to deliver and secure these services.

Usage and diagnostics

We collect account-linked usage events, including sessions, screens used, recitation playback, garden completion, gifting and subscription events. We also receive diagnostic and performance information, such as crashes, hangs, app version, operating-system version and device model. These help us understand which features work and fix failures. These events do not include Garden voice recordings or its recognition transcript.

Permissions and choices

You can revoke microphone or notification permission in iPhone Settings. Listening and reading the Qur'an do not need microphone access. Saving a card film to Photos uses the permission you grant for that action. The invitation flow uses contacts on your device; the address book is not uploaded by that flow.

The Garden update removes the Heart Scan and its reflection experience. It does not use face analysis to select an ayah or send Garden speech to OpenAI. Older app versions may have different features; contact us if you have questions about data from a previous version.

Service providers and sharing

We use Supabase for accounts, database records, functions and media delivery; Apple for purchases, platform diagnostics and push delivery; and Apple or Google when you choose their sign-in option. Older app versions use LiveKit for live voice-room audio; Grow with Friends does not. Our website is hosted on Vercel. These services process information needed to operate their part of Hablobi.

If you choose to share a card or film to another app, that service receives the content you select and its own privacy policy applies. We do not sell personal data or use it for cross-app advertising tracking. Information may also be disclosed where required by law or to investigate abuse and protect users.

Website measurement

Some App Store links include a campaign label, such as the flower guide or a Pinterest visit, and our public Apple provider token. Apple reports campaign results in aggregate subject to its privacy thresholds. We do not put your email address, app account identifier, or recitation activity in these links. An App Store link click does not itself mean that you installed the app.

We use Vercel Web Analytics on public marketing pages to count page views and clicks toward the App Store. We send page categories and a fixed set of campaign labels, not form entries, voice recordings, or app account data. Query strings and fragments are removed from analytics page URLs. Analytics is not loaded on admin or invitation pages, in local previews, or when your browser sends Do Not Track or Global Privacy Control. This integration does not set analytics cookies or store campaign information in your browser.

Keeping and deleting information

We retain account and feature records while needed to provide the service. Open Locker → Settings → Delete account to request deletion, or contact us for help. Account-linked analytics and diagnostics are included in the deletion flow.

Gifts already delivered to someone else can remain with their recipient, including the sender name and generated Blobi portrait preserved with that gift. Purchase and operational records may remain where needed for accounting, security or legal obligations; the account-deletion flow removes or anonymizes account links where applicable. Deleting Hablobi or your account does not cancel an Apple subscription: cancel it separately in Apple Subscriptions.

Depending on where you live, you may have rights to request access, correction, deletion or a copy of your information, or to raise a privacy concern with your local authority. Contact us to make a request. Our providers may process data outside your country.

Children and changes

Hablobi is not directed at children under 13. If you believe a child provided personal information, please contact us. We update this page when practices change and provide additional notice where required.

Talk to us

Privacy questions or requests: support@hablobi.com.