PRIVACY POLICY

Secure Charging Animations

Last updated: August 23, 2026

Secure Charging Animations ("the App", "we", "us") is built to work great without asking much of you. This page explains, in plain language, what data the App and the services it relies on can access, what we do with it, and what stays entirely on your device.

01 The short version

  • No account, no sign-up. You can use the App without ever giving us your name, email, or phone number.
  • Face ID / PIN data never leaves your device. Biometric authentication is handled entirely by Apple's on-device Face ID system — the App only ever receives a yes/no result, never your face data. Your PIN is stored locally in the device Keychain.
  • We don't run our own tracking servers. Any data collection described below comes from well-known third-party services (ads, subscriptions, crash/config tooling), not a backend we operate ourselves.
  • You control ad tracking. On first launch, the App asks for App Tracking Transparency (ATT) permission and shows a consent form (required for users in the EEA/UK). You can decline both and continue using the App normally.

02 Information we collect

Information you provide

The App does not require registration. The only information you actively provide is stored locally on your device and never transmitted to us:

Information collected automatically

Some third-party services the App relies on may automatically collect standard technical data — device type, OS version, general (non-precise) region, advertising identifiers (IDFA, where permitted), and app usage/crash diagnostics — to serve ads, process purchases, and keep the App stable. See the table below for exactly which services and why.

03 Third-party services we use

We rely on the following services to run the free, ad-supported version of the App and to process optional Pro subscriptions:

ServicePurposeData involved
Google AdMob (with mediation)Shows banner, interstitial, rewarded, and native adsAdvertising identifier (IDFA, with your ATT consent), general device info, ad interaction data
Mediated ad networks: AppLovin, Meta Audience Network, Pangle, Mintegral, InMobi, DT ExchangeCompete to fill ad space via AdMob mediationSame as above, only when ATT/consent is granted
Google User Messaging Platform (UMP)Shows the required consent form to EEA/UK users and forwards your choice to ad partnersConsent status only
Firebase Remote ConfigLets us adjust app behavior (e.g. ad timing) without shipping an updateAnonymous app/device configuration signals
RevenueCatManages Pro subscription purchases and ad removalAnonymous purchase/subscription status, App Store transaction data
Apple App StoreProcesses all paymentsHandled entirely by Apple under its own privacy policy — we never see your payment details

Each of these providers processes data under its own privacy policy. We only enable ad personalization and tracking-based features after you've responded to the ATT prompt and, where applicable, the UMP consent form.

04 How we use information

We do not sell your personal information. We do not build cross-app profiles of you ourselves — any advertising profile is built and controlled by the ad networks listed above, per their own policies and your consent choices.

05 Your choices & controls

06 Children's privacy

The App is not directed at children under 13 (or the relevant age of digital consent in your region), and we do not knowingly collect personal information from children. The App's ad configuration flags non-child-directed treatment to our ad partners.

07 Data retention

Locally stored data (PIN, logs, preferences) stays on your device until you delete it or uninstall the App. Data held by third-party services (ad networks, RevenueCat, Firebase) is retained per their own policies — see the links below.

08 International users

If you're in the EEA, UK, or another region with its own data protection law, you may have rights to access, correct, or delete data held about you by the third-party processors above. Requests about App-level local data can be resolved simply by adjusting Settings or uninstalling the App; requests about third-party processor data should go directly to that provider, or to us and we'll help route it.

09 Changes to this policy

We'll update this page if what we collect or how we use it changes, and update the "Last updated" date above. Material changes will also be reflected in the App's "What's New" release notes.

10 Third-party privacy policies

Questions about this policy?

Contact us at alihaidar679@gmail.com