stickerPop
Privacy Policy
Updated October 3, 2026
Developer and scope
stickerPop is developed by Eric Augusto Ito. For privacy requests, contact contato.stickerpop@outlook.com. This revision also describes measurement added in iOS version 1.0.3. Earlier versions and other platforms may not include these integrations.
Content on your device
Photos, videos, text, cutouts, projects, favorites, imported fonts and brand kit materials are processed and stored on your device. There is no proprietary account system or cloud sync for creations. Recognition uses ML Kit and, for object cutouts on compatible iOS devices, Apple Vision. Content recognition runs locally. We do not send your creations, entered text or file names as analytics or advertising events.
Purchases and subscriptions
Google Play or the App Store processes payments. RevenueCat processes an SDK-generated identifier, products, transactions, purchases and subscription status to validate and restore access and analyze subscriptions. The app does not receive your full card number. On iOS, attribution also updates RevenueCat with tracking permission status and available technical identifiers, such as IDFV, IP and, when authorized, IDFA and a Meta identifier.
Usage analytics on iOS
We use Google Analytics for Firebase to understand app opens and return visits, onboarding completion, paywall views, checkout attempts, exports, saving and opening sharing. Events may include export format, media type, operation duration and access status. The SDK uses an app installation identifier, app and device information and approximate location derived from IP, without GPS. It may record store purchase and subscription events. We do not provide a name, email or proprietary account ID to Firebase. Firebase advertising consents are disabled in app configuration. Usage analytics is independent of Apple tracking permission.
Meta advertising measurement
On iOS, we request Apple tracking permission to associate Sticker Pop ads with activations and subscriptions. When authorized, we send activation events through the Meta SDK and may share free-trial, purchase and renewal events through RevenueCat. Data includes available installation, technical user and device identifiers, app information, product, transaction, value and currency. Meta may associate this data with information from its services to measure our ads. We do not send photos, videos or text from your creations for this purpose.
Your choices
You can refuse or revoke tracking in iOS Settings → Privacy & Security → Tracking. Refusal does not prevent editing or subscribing. The app checks your choice when returning to the foreground and before purchase; updating RevenueCat requires communication with the service. Current configuration requires ATT authorization to send subscription events to Meta. Revocation does not automatically delete previously sent data or disable Firebase usage analytics. The app does not yet offer a separate switch for that analytics; data requests can be sent to the contact in this policy. SDKs may make technical configuration requests even without authorized advertising events.
Technical services and recipients
ML Kit may download models and updates and send Google technical usage and performance metrics. Google Fonts downloads transmit request information such as IP. Depending on platform and functionality, recipients include Google/Firebase, Meta, RevenueCat, Apple and Google Play. See the Google Privacy Policy, ML Kit terms, Meta Privacy Policy, RevenueCat Privacy Policy and Apple Privacy Policy. These providers may process data using infrastructure outside Brazil.
Permissions and sharing
Camera and media permissions let you capture or select content to edit. Manage permissions in your system settings. When exporting, copying or sharing, you provide your creation to the destination you choose. Copies in your gallery, clipboard and other apps follow those destinations’ controls. The app has no public feed or social login.
Purposes and rights
We process data to provide requested features, manage subscriptions, understand usage, measure campaigns and provide support. If you email us, we receive your address and message. Use the contact above to request information, access, correction or deletion of data under our responsibility and exercise other applicable rights. We request only information needed to locate and handle your request. Do not send passwords or complete card information.
Retention and deletion
Creations remain in app storage until removed or local data is erased. Backups may retain or restore copies according to your settings. Delete exported files at their destinations. Measurement and purchase records are processed according to service settings, the purposes described and applicable legal retention requirements. Deleting the app does not automatically remove records already sent to Firebase, Meta, RevenueCat or stores. Deletion requests depend on identifying the records and applicable retention obligations; we do not promise deletion of records stores must retain. See how to delete data (Portuguese). Deleting the app does not cancel your subscription.
Updates
We will update this policy when relevant changes occur. The date on this page identifies the revision.