Effective date: November 1, 2026
This Privacy Policy explains how Puggy (“we,” “us,” or “the app”) handles information when you use our iOS application. The developer responsible for Puggy can be contacted at tenor.hector@gmail.com.
Puggy stores your financial records, including income, expenses, budgets, categories, savings goals, recurring transactions, notes, and opening balance, locally on your device using Apple’s SwiftData framework. We do not operate a backend that stores or synchronizes these financial records.
Your profile name, onboarding amounts, and certain preferences are also stored locally. Device backups may include this information, depending on your Apple and device settings. If you export your records, you choose where to save or share the exported file; any service you choose may process that file under its own terms.
Local storage does not mean that the app collects no information. The analytics and subscription services described below receive separate usage, identifier, onboarding, and purchase information.
We use PostHog and Google Analytics for Firebase to understand how people use Puggy and improve the app.
Information collected may include:
App launches, sessions, app and operating system versions, device model, language, and other technical context.
Persistent user, device, installation, and session identifiers.
Onboarding steps viewed or completed, time spent on steps, selections, and whether a name was provided, a budget was saved, or a commitment was completed.
Coded answers about spending habits, whether you pay for subscriptions, your main financial objective, a spending category of interest, and a savings objective, such as building an emergency fund or reducing debt.
Paywall views, plan selections, purchase attempts, cancellations, purchase outcomes, subscription status, trial status, and the selected plan’s price and currency.
Notification permission and trial-reminder setup events.
Our current onboarding analytics does not intentionally send the name you enter, your transaction notes, your income or expense records, or the exact spending estimates and budget amounts you enter during onboarding. It does send the selected answer categories described above.
These records are pseudonymous, not necessarily anonymous: identifiers allow events to be associated with the same user or installation. PostHog can associate earlier onboarding events with the app’s user identifier. Purchase-related events can also be associated with that profile.
Our analytics providers may derive general location, such as country, region, or city, from your IP address. Puggy does not request GPS access for analytics. PostHog session replay and automatic screen-view capture are disabled in our current configuration; explicitly recorded events and application lifecycle events are still collected.
We use Firebase Crashlytics to receive crash reports and technical diagnostics. These may include crash traces, device and operating system information, app version, installation identifiers, and information about app activity preceding a crash. We use this information to investigate faults, maintain reliability, and improve Puggy.
We do not intentionally attach your financial records to crash reports.
Puggy can create a local user identifier without requiring you to register an external account. This identifier may be used to associate analytics events with the same user.
If you use Sign in with Apple, Apple may provide an account identifier and an email address, including a private relay address if you choose Hide My Email. Puggy stores the returned account information locally. The account identifier may be sent to PostHog to associate analytics with that account; our current implementation does not deliberately send your profile name or email address to PostHog.
If you email us for support, we receive your email address and any information you include in your message. Please avoid sending financial records or other sensitive information unless it is necessary for your request.
Apple’s App Store processes payments. We do not receive your payment card number or bank account details.
We use RevenueCat to validate purchases and manage subscription access. RevenueCat processes information such as an app user identifier, receipts or transaction information, product and transaction identifiers, purchase dates, trial status, renewal status, and entitlements. This supports subscription management and subscription analytics.
We also send purchase-related analytics events to PostHog and Firebase as described above. Subscription information is therefore used both to provide access and to understand purchase and trial conversion.
If you use voice entry, Puggy requests microphone and speech recognition permissions. It requests on-device speech recognition when supported. When on-device recognition is unavailable, Apple’s speech recognition service may process audio under Apple’s terms and privacy practices. The resulting transaction details are presented for your review before saving locally. We do not send voice recordings to PostHog, Firebase, or RevenueCat as part of our analytics implementation.
If you enable Face ID protection, authentication is handled by Apple’s device frameworks. Puggy does not receive your facial images or biometric templates.
Trial reminders use local notifications, subject to your permission and device settings. Permission and reminder setup outcomes may be recorded as analytics events. A reminder is not a guarantee that you will be notified before renewal; subscriptions can be managed through Apple.
We use information to provide app features, manage subscriptions, understand onboarding and feature usage, improve Puggy, diagnose technical problems, and respond to support requests.
Information is processed by the relevant service providers:
PostHog: product analytics, onboarding analysis, and purchase-conversion analysis. Privacy information (https://posthog.com/privacy).
Google/Firebase: usage analytics and crash diagnostics. Privacy information (https://firebase.google.com/support/privacy).
RevenueCat: purchase validation, subscription access, and subscription analytics. Privacy information (https://www.revenuecat.com/privacy).
Apple: App Store payments and applicable sign-in, speech recognition, biometric authentication, backup, and notification services. Privacy information (https://www.apple.com/legal/privacy/).
These providers may process information outside your country. Their applicable data-processing terms describe processing locations and international-transfer safeguards.
We do not sell your personal information or use the analytics described here to build cross-company advertising profiles. We may disclose information where necessary to comply with legal obligations or protect against fraud and abuse.
Local financial records remain on your device until you delete them or remove the app. Copies in backups, exported files, and other destinations you choose may remain until you delete them separately. Offloading the app can preserve local data.
Analytics, diagnostic, and subscription information is retained according to the purposes described in this policy, our providers’ configured retention settings, and applicable contractual or legal requirements. Uninstalling Puggy does not automatically delete information already received by these providers.
You can contact us to request information about retention or request deletion of personal information that we or our service providers can associate with you. We may need information to locate the relevant records. Some information may need to be retained to meet legal obligations or manage purchases.
You can edit or delete local records, export your data, manage device backups, and revoke microphone, speech recognition, or notification permissions in iOS Settings. Manage or cancel subscriptions through your Apple account; deleting the app does not cancel a subscription.
The current version does not provide an in-app analytics opt-out switch. Contact us with questions or requests concerning analytics data.
Depending on applicable law, you may have rights to access, correct, delete, or obtain a copy of your personal information, restrict or object to certain processing, or withdraw consent where processing is based on consent. You may also complain to your local data protection authority. Contact tenor.hector@gmail.com to exercise these rights.
Puggy is not designed specifically for children. We do not knowingly seek personal information from children where parental authorization is required by applicable law. Technical and usage information may nevertheless be collected when the app is used. If you believe a child has provided personal information that should be removed, contact us so we can investigate and respond.
We may update this policy to reflect changes to Puggy or its data practices. We will publish the updated policy and revise the effective date. Where required, we will provide additional notice or obtain consent before introducing relevant changes.
For privacy questions or requests, contact tenor.hector@gmail.com.