Pigly Privacy Policy

Last updated: July 13, 2026

Pigly is a gambling-recovery and self-protection app for iOS and Android. This Privacy Policy explains what information Pigly collects and processes, why it is used, which information remains on your device, which service providers process information for us, and the choices available to you.

Pigly is the product and brand name. Pigly is operated by Yuval Nir, trading as Mehayom Digital, Israel. For privacy questions or requests, contact office@mehayom.info. Yuval Nir, trading as Mehayom Digital, is the data controller for the personal information described in this policy.

This policy applies to the Pigly mobile apps, our account and support services, and the Pigly website pages that link to it.

Information we collect and process

Account and sign-in information

Pigly uses Supabase for account authentication and backend services. Depending on how you sign in, Supabase processes your email address, your authentication provider (email, Apple, or Google), an internal account user ID, authentication provider identifiers and profile information made available by that provider, and authentication, identity, and session records needed to create, secure, and operate your account.

Recovery Backup

When you are signed in, Pigly backs up a defined set of recovery information to your Supabase account so that it can be restored after you reinstall Pigly or change devices. Recovery Backup is linked to your authenticated account user ID. It includes:

• your quit date and recovery start date;
• clean-day, streak, and recovery statistics;
• your daily gambling amount and currency;
• savings goals and personal promise;
• your nickname and avatar;
• gambling types and triggers you select;
• self-assessment answers, score, level, and assessment date;
• recovery-program track, start date, progress, completed lessons, and onboarding status;
• urge logs, including the time, intensity, trigger, coping strategy, emotion, location label, time of day, and whether the urge was resisted;
• relapse records, including date, amount, duration, method, and any note you write; and
• relapse reflections, including the trigger, emotion, situation, learning, support needed, next-step plan, compassion score, and any text you write.

This information can be sensitive. Pigly uses it to provide the recovery features, maintain your progress, and restore it when you sign in to the same account. Recovery Backup is not used for advertising and is not provided to AppsFlyer or Meta.

Recovery Backup records are stored with Supabase in the European Union and are restricted by account-based access controls to the authenticated user. The same-account restoration mechanism uses your authenticated Supabase user ID; it does not restore one account's backup into another account.

Pigly is a recovery-support and self-protection app. It is not a medical device, and it does not provide diagnosis, treatment, or clinical advice.

Information that remains on your device

The following Pigly information is not included in Recovery Backup:

• journal entries;
• debts and money-allocation records;
• reminders and notification settings;
• pet progression and daily reward state;
• gambling-protection configuration and state;
• loved-one sharing settings; and
• other settings and preferences not identified above as backed up.

This device-only information is not restored by Recovery Backup. Removing the app or clearing its app data removes information held only in that local app installation. Subscription status is not stored in Recovery Backup; it is obtained from RevenueCat and the applicable app store.

Purchases, subscriptions, and entitlements

Pigly Premium subscriptions are purchased through the Apple App Store or Google Play. Apple or Google processes your payment method and store account. Pigly does not receive your full payment-card or bank-account details. Subscriptions renew automatically unless canceled under the applicable store's subscription terms. You can manage or cancel a subscription in your Apple or Google account settings.

Pigly uses RevenueCat to offer products and trials, validate purchases, restore purchases, and manage subscription entitlements. RevenueCat and Pigly may process a RevenueCat app-user identifier, product and entitlement identifiers, store and environment, subscription status and lifecycle events, purchase and expiration dates, transaction and original-transaction identifiers, country, currency and price information, estimated store fees and taxes, and related purchase, refund, renewal, cancellation, billing-issue, and product-change information.

Pigly receives RevenueCat subscription lifecycle webhooks and stores the related subscription, transaction, entitlement, accounting, and event records in Supabase. These records are used to provide Premium access, support purchases and refunds, attribute creator codes, prevent fraud, reconcile revenue and creator commissions, and meet tax, accounting, legal, security, and app-store obligations.

Creator and referral codes

If you enter or apply a creator or referral code, Pigly processes the code, creator name or handle snapshots, the associated RevenueCat offering, your Supabase account user ID, and your RevenueCat app-user ID. Before a purchase, this lets Pigly display the applicable offer and associate the account with the creator. If a purchase occurs, related attribution, transaction, commission, refund, and payout records may be retained for accounting, fraud prevention, dispute resolution, and creator-payment administration.

Support and privacy requests

If you contact us, we process your email address and the information you choose to include in the message, such as account details, support questions, or attachments. We use this information to respond, verify account ownership when necessary, troubleshoot issues, protect the service, and handle privacy or deletion requests. Please do not send information that is not needed for your request.

Attribution, analytics, and advertising measurement

AppsFlyer

Pigly uses AppsFlyer to measure app installs, app launches, completed account registrations, and the performance of advertising campaigns. AppsFlyer also supports attribution fraud prevention, security, diagnostics, and service reliability.

Pigly sends one app-specific client event to AppsFlyer when a new account registration is completed. The event identifies only the registration method, such as email, Apple, or Google. Pigly does not include the user's name or email address in this event. Pigly does not send client-side purchase or subscription revenue events to AppsFlyer.

AppsFlyer may process an AppsFlyer installation identifier, IP address used to derive approximate location such as region or city, app and device information, app-launch and registration-event information, campaign and attribution data, and limited diagnostic or performance signals such as launch timing or battery level.

On Android, AppsFlyer may access the Google Advertising ID and uses the AppsFlyer installation identifier, IP-derived approximate location, app and device information, and limited diagnostics for attribution, measurement, fraud prevention, security, and reliability.

On iOS, Pigly uses Apple's App Tracking Transparency framework. Pigly requests permission before allowing access to the Identifier for Advertisers (IDFA), and the IDFA is available to AppsFlyer and RevenueCat only if the user grants that permission. If permission is not granted, Pigly does not provide access to the IDFA. AppsFlyer may still process non-IDFA information permitted by Apple, such as its installation identifier, IP-derived approximate location, app and device information, and limited diagnostics.

RevenueCat attribution and subscription events

To connect subscription results with AppsFlyer attribution, Pigly provides RevenueCat with the AppsFlyer installation identifier and asks RevenueCat to collect the device identifiers used by the integration. Depending on platform and permission, these identifiers can include the Google Advertising ID on Android; the IDFA on iOS only after ATT permission; Apple's Identifier for Vendor; and the device IP address.

The active RevenueCat-to-AppsFlyer server integration can send subscription lifecycle events including initial purchases, trial starts, trial conversions, trial cancellations, renewals, cancellations, non-subscription purchases, expirations, billing issues, and product changes. RevenueCat is Pigly's source of truth for subscription and purchase events. Pigly avoids sending duplicate client-side revenue events to AppsFlyer.

Meta campaign attribution

When Pigly's Meta advertising integration is active, AppsFlyer may provide Meta with install, campaign-attribution, and configured conversion information so we can measure the results of Pigly advertising campaigns. This processing is conditional on that integration being active and on the identifiers and permissions available for the device and platform.

Pigly does not display third-party advertising in the app. Pigly does not sell personal information.

Gambling-protection processing

Pigly offers optional gambling-website protection. You choose whether to turn it on. Protection is best-effort and is not guaranteed to block every website.

iOS Pigly DNS and NextDNS

On iOS, the current Pigly DNS feature configures Apple's encrypted DNS settings to use a Pigly-controlled NextDNS configuration. When Pigly DNS is enabled, DNS requests are processed by NextDNS so that domains can be checked against the configured blocking policy and blocked or resolved. This processing is not entirely local to the device.

NextDNS necessarily receives and processes DNS request and network information needed to answer each request. Logging is disabled for Pigly's NextDNS configuration. With logging disabled, NextDNS states that request and response data is discarded after the response is returned. Pigly does not receive or store a history of the domains requested through this configuration in Supabase, AppsFlyer, RevenueCat, or Meta.

Pigly stores only the local configuration and status information needed to enable, verify, and remove the iOS DNS protection on the device. Turning off the feature removes Pigly's DNS configuration from the device.

Android protection

On Android, Pigly's protection feature uses Android's VPN permission to run a local filtering service on the device. It is not a remote VPN operated by Pigly, and Pigly does not route general internet traffic through Pigly servers. Domain checks against Pigly's block list occur on the device. DNS requests that are allowed still need to be resolved through the device or network's DNS infrastructure.

Pigly does not send Android browsing history, requested domains, or blocked-site attempts to Supabase, AppsFlyer, RevenueCat, or Meta.

Camera

The Panic or urge-support screen can display a private live mirror using the front camera to help you pause during an urge. The image is displayed live on the device and is not recorded, stored, or uploaded by Pigly.

How we use information

We use the information described in this policy to:

• create, authenticate, secure, and support Pigly accounts;
• provide Pigly's recovery, backup, restore, subscription, and protection features;
• provide, validate, restore, and support purchases, trials, subscriptions, and Premium entitlements;
• apply creator codes and administer creator attribution and commissions;
• measure installs, launches, completed registrations, and advertising campaign performance;
• prevent fraud, abuse, and security incidents;
• diagnose technical problems and maintain service reliability;
• respond to support, access, correction, and deletion requests; and
• meet legal, tax, accounting, transaction, dispute, and app-store obligations.

Service providers and recipients

We use the following providers to operate Pigly:

• Supabase — account authentication, database hosting, Recovery Backup, account-linked creator attribution, subscription and transaction records, and backend functions.
• RevenueCat — subscription products, trials, purchase validation, restoration, entitlements, subscription lifecycle processing, and the AppsFlyer attribution integration.
• AppsFlyer — install attribution, app-launch and completed-registration measurement, advertising measurement, fraud prevention, and limited related diagnostics.
• Meta, when the integration is active — Pigly campaign attribution and conversion measurement received through AppsFlyer.
• NextDNS — processing DNS requests for the optional iOS Pigly DNS blocking feature, with provider logging disabled.
• Apple App Store — iOS purchases, subscription management, billing, refunds, and platform compliance.
• Google Play — Android purchases, subscription management, billing, refunds, and platform compliance.

These providers process information under their own terms and privacy policies and, where applicable, on our behalf and instructions. Information may also be disclosed when reasonably necessary to comply with law, protect users or the service, investigate fraud or abuse, enforce agreements, or complete a business reorganization subject to appropriate safeguards.

Retention

Recovery Backup is retained while your Pigly account exists. Deleting the Supabase account deletes the account-linked Recovery Backup records described in this policy.

Other information is retained only for as long as reasonably necessary for the purposes described here, including providing the app, responding to support or privacy requests, maintaining security, resolving disputes, preventing fraud, and satisfying legal, tax, accounting, transaction, creator-payment, and app-store requirements.

Deleting your Pigly account does not necessarily delete every transaction, subscription, refund, fraud-prevention, security, tax, accounting, platform, AppsFlyer, or RevenueCat record. Records that must be retained may continue to contain store transaction identifiers, RevenueCat identifiers, AppsFlyer installation identifiers, or other limited identifiers needed for those purposes. We do not describe such records as anonymous unless they have actually been anonymized.

Device-only information remains in that app installation until it is removed by the app, you clear the app's data, or you uninstall the app.

Security

Pigly uses technical and organizational measures intended to protect personal information. Network transfers to Pigly's service providers use encryption in transit. Supabase provides encryption at rest for the hosted database, and Recovery Backup tables use authenticated user access controls. Access to administrative systems is restricted to authorized purposes.

No storage or transmission method is completely secure. We cannot guarantee absolute security, and we encourage you to protect your sign-in credentials and device.

Account deletion and your choices

You can delete your Pigly account in the app through Profile → Delete account, or request deletion using the instructions at https://piggybankmoneyback.com/account-deletion/.

Deleting the account deletes the Supabase authentication account and the account-linked Recovery Backup records. It also deletes the account's pre-purchase creator-code attribution. Certain purchase, subscription, transaction, refund, commission, fraud-prevention, security, tax, accounting, and platform-compliance records may be retained as explained above.

Deleting your Pigly account does not cancel an Apple App Store or Google Play subscription. You must cancel an active subscription in the applicable store's subscription settings.

Depending on applicable law, you may have rights to request access, correction, deletion, restriction, or a copy of personal information, or to object to or withdraw consent for certain processing. To make a request, email office@mehayom.info. We may need to verify your identity before acting on a request. Some rights are subject to legal exceptions and required retention.

On iOS, you can review or change Pigly's tracking permission in iOS Settings. You can turn Pigly's optional protection feature on or off in the app, subject to the app's protection controls.

International processing

Supabase Recovery Backup is hosted in the European Union. Other service providers may process information in Israel, the European Economic Area, the United States, or other countries where they operate. Where required, we rely on the providers' contractual and legal safeguards for international processing.

Children

Pigly is intended for adults and is not directed to children. If you believe a child has provided personal information to Pigly, contact us so that we can review and address the request.

Changes to this policy

We may update this policy when Pigly's features, providers, or legal obligations change. We will post the updated policy at this URL and change the Last updated date. Material changes may also be communicated through the app or another appropriate channel.

Contact

Pigly is operated by Yuval Nir, trading as Mehayom Digital, Israel. For privacy questions or requests, contact office@mehayom.info.