Fendo Privacy Policy

Last updated: September 7, 2026

Fendo is a personal companion for adults who want to stop using nicotine pouches. This policy covers the Fendo iOS app and its legal pages at /fendo/privacy and /fendo/terms. It does not cover the separate InfoDrizzle app.

Who is responsible

Fendo is provided by Marco Pérez (“we” or “us”). For privacy questions or requests, email infodrizzle.contact@gmail.com.

Local journey data and online services

Fendo stores and processes your journey in the app’s local storage. Confirmed onboarding answers and onboarding and subscription events are sent to PostHog as described below. Your ongoing diary, check-ins, craving history, and calculated health estimates remain local and are not sent to PostHog or RevenueCat. There is no Fendo account, cloud sync, or developer-operated backup. The “Account details” screen edits your local profile; it does not create an online account.

Depending on what you enter and use, local records include:

• Your preferred name, optional identity choice, reasons for quitting, personal messages, concerns, intended quit timing, age range when you started using pouches, and previous quit attempts and challenges.
• Your pouch brand, strength, typical use, pouches per can, price, currency, journey start time, and recorded pouch use.
• Diary text, mood check-ins, feelings, contexts and triggers, craving strength before and after an activity, coping activities, and personal strategies.
• Calculated progress and estimates, goals, Grove trees and rewards, game records, and reading progress.
• App preferences, locale and timezone, local record identifiers and timestamps, and an unfinished onboarding draft so you can resume it.

Some of this information can reveal sensitive health or wellbeing information. Fendo uses it locally to show your history, personalize support, calculate estimates, and maintain progress. Local identifiers connect your records; they are not advertising identifiers.

Permissions and services

Fendo uses local notifications for trial reminders when an eligible, verified trial is available. Notification permission is optional and can be changed in iOS Settings. Reminder scheduling happens on the device; Fendo does not register a remote push token or send your journey to a notification server. Notification delivery is controlled by iOS and is not guaranteed.

The current app does not include advertising or third-party crash-reporting SDKs, tracking across other companies’ apps or websites, HealthKit access, or access to your contacts, photos, camera, microphone, or precise location. It does not send your entries to an AI service. We do not sell or rent your personal information or share it for targeted advertising.

Apple may process App Store downloads, device diagnostics you choose to share, and device backups under its own settings and privacy policy. These platform services are distinct from Fendo’s local journey storage.

Onboarding and subscription analytics: PostHog

Fendo uses PostHog Cloud US, hosted in the United States, to understand onboarding completion, where people leave, and subscription conversion. Analytics is active automatically in release builds, without a separate opt-in prompt or an in-app analytics switch. Events are sent through our analytics endpoint at i.infodrizzle.com to Fendo’s separate PostHog project.

We send:

• Onboarding starts, resumes, steps viewed and completed, final paywall views, and journey activation, with event times and generated installation and onboarding identifiers.
• Confirmed onboarding answers: preferred name, gender identity where provided, main reason for quitting, concerns, intended quit timing, age band when you started using pouches (not your current age), previous quit attempts and applicable challenge, pouch product and strength, usage frequency and typical amount, and price per can and currency. A complete answer snapshot is also sent when you reach the final plan picker. Confirmed corrections update the analytics profile; this does not necessarily erase earlier events.
• Subscription interactions during onboarding, when returning to the app, and in Settings: selected plan, product identifier, recurring price and currency, trial availability, purchase attempts and outcomes, restore outcomes, and verified access. Events distinguish trials from paid subscription periods and include generated purchase-attempt identifiers and limited error codes. They do not include payment-card details, receipts, RevenueCat customer identifiers, or raw purchase-error messages.
• App version and build, operating system, and standard SDK and session metadata. Network delivery exposes your IP address to the services handling the request; geolocation enrichment is disabled.

The installation identifier persists across app sessions, and confirmed answers are associated with its analytics profile. Because these records include your name and other personal information, they are not anonymous. There is no Fendo-account-based linking across devices. Events can be queued locally and sent when connectivity returns.

Fendo does not enable automatic screen or tap capture, session recording, automatic crash capture, or geolocation enrichment in PostHog. Ongoing Diary entries, mood check-ins, craving sessions, personal strategy text, and health estimates are outside this analytics collection. We use these analytics to understand and improve onboarding and subscription flows, not for advertising.

Some onboarding answers reveal health or other sensitive personal information. This notice describes collection; accepting the Terms or using the app is not a substitute for any separate consent required by law. See PostHog’s privacy information. Privacy requests and the current controls are described below.

Subscriptions: Apple and RevenueCat

Fendo uses RevenueCat to manage monthly and yearly App Store subscriptions, verify purchases, determine access, restore eligible purchases, and obtain trial and renewal status. Apple processes payments; we do not receive your full payment-card details.

RevenueCat processes a generated app user identifier, purchase receipts or transaction information, purchased products, subscription and entitlement status, trial and renewal dates, and associated technical information such as app and device details and IP address. Fendo does not attach your name, onboarding answers, Diary entries, craving records, or health estimates as RevenueCat subscriber attributes. The RevenueCat identifier is separate from the PostHog installation identifier.

Subscription processing supports the purchase and access you request and applicable transaction-record obligations. Access is checked at launch, on returning to the app, during use, and when subscription status changes. Verified trial expiration is used on your device to schedule an eligible local reminder. Restoring a purchase restores eligible access, not your journey data on another device.

RevenueCat processes end-user information on our behalf. Its infrastructure stores data in the United States, and its providers may process information in other countries. See RevenueCat’s privacy policy and Apple’s privacy policy. Contact us for requests concerning information we control; Apple manages its own payment and transaction records.

When you contact us or visit these pages

If you email us, we receive your email address, message, and any attachments you choose to send. We use them to respond, troubleshoot, and handle privacy requests. Please avoid sending sensitive diary or health information that is unnecessary for your request. Our email provider processes these communications to deliver and store email. We retain correspondence only as needed to resolve your request, maintain necessary support records, or comply with legal obligations, and then delete it.

These Fendo legal pages do not load advertising, analytics, third-party fonts, or tracking scripts and do not set application cookies. Our website hosting provider may process ordinary request information, such as IP address, browser information, requested URL, and time, to deliver and secure the pages. Opening these pages does not transmit your Fendo journey. Other pages on the InfoDrizzle site have separate practices.

For information we receive, we rely, where applicable, on our legitimate interests in answering requests and operating a secure website, on steps needed to provide requested support, or on legal obligations. We may disclose that information to service providers supporting those purposes or when legally required. Providers may process it outside your country; where required, we use applicable transfer safeguards. We do not have a server copy of your local journey to disclose.

Retention, deletion, and backups

Local data remains on your device while the app retains it. Editing or deleting an entry in the Diary changes the visible history, but some records are marked as deleted rather than immediately erased from storage. Previously earned rewards and related progress records can remain. There is currently no complete in-app export or erase-all tool.

To remove Fendo’s local app data, use Delete App in iOS, rather than Offload App, which retains data. Device or iCloud backups may contain app data depending on your settings. Manage or delete those backups separately through Apple’s controls; restoring a backup may restore earlier records. We cannot remotely access, recover, export, or erase records held only on your device. Deleting the app does not cancel any App Store subscription.

Deleting the app or editing local records does not automatically delete information already sent to PostHog, RevenueCat, or support. We retain provider-held information as needed for the purposes described in this policy, including analytics, subscription administration, support, and applicable legal obligations. A fixed Fendo analytics retention period has not yet been established; this policy does not promise automatic deletion after a particular interval. You can request deletion of information we control using the contact above, subject to applicable legal exceptions. Apple’s independently held records follow Apple’s policies.

Fendo relies on iOS app storage and device protections; it does not provide a separate app passcode or its own encrypted vault. Protect access to your device and backups. No storage system can be guaranteed completely secure, and device loss, deletion, or a failed restore may result in lost history.

Your choices and privacy rights

You can choose what optional information to enter, edit supported profile and diary fields, manage notification permission, and delete the app and backups. The current app has no analytics opt-out or provider-data deletion control. Contact us to request access, correction, deletion, or to object to processing; removing the app stops future app-generated events but does not erase information already received. Depending on where you live and the applicable law, you may also have rights to access, correct, delete, or obtain a copy of personal information we hold, restrict or object to its use, withdraw consent where processing relies on consent, and complain to your local data protection authority. Contact us using the email above to exercise those rights. We will respond within the applicable legal timeframe and will not discriminate against you for making a request. We may need proportionate verification and information to locate the relevant installation or purchase records. Because there is no Fendo account, your email address alone may not identify those records. We will explain any identification limits and will not ask you to upload your journey merely to identify you.

Adults only

Fendo is intended for people aged 18 or older. We do not knowingly collect children’s information through the app, support, or our website. If you believe a child has sent us personal information, contact us so we can address it.

Changes

We will update this page and its date when our practices change. For material changes, we will provide additional notice in the app or another appropriate way, and obtain consent where required before introducing new processing.