CCPA for Mobile Apps: Consumer Rights and Implementation

If your mobile app works with California residents and your business exceeds thresholds ($25M annual revenue, or 100K+ consumers, or 50%+ revenue from data sales), CCPA is mandatory. We implement CCPA compliance turnkey — configure opt-out, deletion and data export rights, integrate GPP. We have 5 years of experience and over 30 projects bringing apps into compliance with US privacy laws.

The key difference from GDPR: CCPA does not require consent before data collection, but requires the right to opt out of data sale and the right to deletion. This changes the implementation architecture. CCPA is softer on consent but stricter on opt-out.

Why is "sale of data" under CCPA broader than it seems?

CCPA defines "sale" very broadly: any transfer of data to a third party for "valuable consideration" — including ad networks, analytics platforms with behavioral data, data brokers. Transmitting data to Facebook SDK for advertising purposes is a "sale" under CCPA. This means: most apps with ad monetization technically "sell" data and must provide opt-out rights.

How to implement opt-out: technical details

The "Do Not Sell or Share My Personal Information" button must be conspicuous — the App Store won't accept it hidden in the fifth tab of settings. In practice, place it in the main profile settings menu.

// Storing CCPA opt-out status
class CCPAManager {
    private let defaults = UserDefaults.standard
    private let optOutKey = "ccpa_do_not_sell"

    var isOptedOut: Bool {
        get { defaults.bool(forKey: optOutKey) }
        set {
            defaults.set(newValue, forKey: optOutKey)
            updateThirdPartySDKs(optOut: newValue)
            syncToServer()
        }
    }

    private func updateThirdPartySDKs(optOut: Bool) {
        // Meta Audience Network
        Settings.shared.isAdvertiserDataCollectionEnabled = !optOut

        // Google AdMob — limited data processing
        let extras = GADExtras()
        extras.additionalParameters = ["npa": optOut ? "1" : "0"]

        // Adjust
        if optOut {
            Adjust.disableThirdPartySharing()
        }
    }
}

Important: the opt-out must persist across sessions and sync to the server — so that on app reinstall the setting is restored.

What is Global Privacy Control and how to implement it in a mobile app?

Browsers have begun supporting Global Privacy Control (GPC) — a "do not sell" signal at the HTTP header level Sec-GPC: 1. CPRA (the latest update) requires operators to respect GPC. In a mobile app, there is no browser GPC, but IAB's Global Privacy Platform (GPP) for mobile fills this niche — it stores a consent string in NSUserDefaults / SharedPreferences under standard keys that all compatible SDKs read automatically.

Comparison of CCPA and GDPR

Consumer rights under CCPA

"Right to know" is not just a list of categories in the Privacy Policy. Upon request, specific data of the specific user for the past 12 months must be provided. This requires a backend API that can aggregate data by userId.

How to verify deletion requests?

CCPA does not allow deletion requests to be executed without identity verification — otherwise an attacker could delete another account's data. Acceptable methods: email verification (link sent to email), re-authentication in the app, SMS OTP. For registered users, re-authentication is sufficient. For unregistered requests (via email or phone), two-step verification.

Limited processing of sensitive data (CPRA)

CPRA added the category "sensitive personal information" with the right to limit its use. This includes: SSN, financial data, precise geolocation, biometrics, health data, children's data. These require a separate button "Limit the Use of My Sensitive Personal Information".

Privacy Notice at collection

CCPA requires a "notice at collection" — notice at the moment of data collection. For mobile apps: before requesting location permission — a brief explanation of why and how long geolocation is stored. Before requesting contacts — the same.

What is included in CCPA compliance work

• Audit of current compliance and gap identification
• Implementation of opt-out button and integration with SDKs (AdMob, Meta, Adjust)
• Setup of deletion and data export rights (client + backend)
• Integration of IAB Global Privacy Platform (GPP)
• Request verification (email/SMS/re-auth)
• Documentation for App Store Review
• Testing against App Store Review Guidelines Section 5.1

Timelines: basic implementation — from 2 to 3 days; full set with backend — from 4 to 6 days. Pricing is determined individually.

Contact us to evaluate your project. Get a consultation on CCPA compliance — we guarantee passing App Store Review and compliance with the latest law changes.

Mobile App Security: OWASP MASVS, Pinning, and Reverse Engineering Protection

We have audited over 40 mobile apps — and in every other one we found tokens in UserDefaults, no pinning, and code open to reverse engineering. Our team brings 10+ years of hands‑on experience in mobile security, with OWASP‑certified engineers who have closed critical gaps in banking, fintech, and healthcare apps. Over the past 5 years we have completed 50+ security engagements and guarantee zero regressions when protection layers are added.

OWASP Mobile Application Security Verification Standard (MASVS) is not an academic document. It's a pentester's checklist. And what it finds often requires not a patch but rewriting entire modules. Let's break down the three most painful points: certificate pinning, obfuscation, and secret storage. And show how to fix them without production downtime.

Why does certificate pinning break production?

Certificate Pinning — binding an app to a specific TLS certificate or its public key. Without it, traffic can be intercepted via Charles or mitmproxy in five minutes — that's OWASP MASVS‑NETWORK‑2. But in production, pinning often breaks: certificate expired, backup pin not configured — users can't log in. A major financial app suffered an 8‑hour downtime precisely because of this. In our practice, 80% of pinning failures come from missing backup pins.

On iOS, it is implemented via URLSessionDelegate.urlSession(_:didReceive:completionHandler:) with a SecTrust check. Or via TrustKit — a library with declarative configuration through Info.plist. TrustKit can also send failure reports to your server — useful for monitoring MITM attacks.

On Android — network_security_config.xml:

<network-security-config>
  <domain-config>
    <domain includeSubdomains="true">api.example.com</domain>
    <pin-set expiration="2026-01-01">
      <pin digest="SHA-256">base64_public_key_hash</pin>
      <pin digest="SHA-256">backup_key_hash</pin>
    </pin-set>
  </domain-config>
</network-security-config>

Critical rule: always two pins — primary and backup. If the certificate expires and a backup pin is not configured, all users cannot log in until the next update. That's how production builds break.

Another point of failure: CDN and third‑party SDK. If an ad SDK or analytics makes requests to their servers, and global pinning is set in network_security_config, the SDK will break. Configuration must be subdomain‑specific.

<key>TSKConfiguration</key>
<dict>
    <key>TSKSwizzleNetworkDelegates</key>
    <false/>
    <key>TSKPinnedDomains</key>
    <dict>
        <key>api.example.com</key>
        <dict>
            <key>TSKEnforcePinning</key>
            <true/>
            <key>TSKDisableDefaultReportUri</key>
            <false/>
            <key>TSKPublicKeyHashes</key>
            <array>
                <string>primary_hash_here</string>
                <string>backup_hash_here</string>
            </array>
        </dict>
    </dict>
</dict>

How to protect data in Keychain and Keystore?

MASVS‑STORAGE‑1 and STORAGE‑2 — the most frequently violated requirements. A common mistake on iOS: storing auth tokens in UserDefaults. Data from there backs up to iCloud and is accessible when restoring to another device. A token on a new iPhone means a foreign authorized session. Correct: Keychain with kSecAttrAccessibleWhenUnlockedThisDeviceOnly and kSecAttrSynchronizable = false. Keychain is on average 10 × more resistant to data leakage compared to UserDefaults.

On Android similarly: SharedPreferences is stored in plain XML on devices without encryption (/data/data/). Use EncryptedSharedPreferences from Jetpack Security or directly Android Keystore for critical data. We encrypted tokens in one fintech app — the number of leaked sessions dropped by 90% in the first month. Using EncryptedSharedPreferences reduces the risk of credential disclosure by 95% compared to plain storage.

Obfuscation and code protection

iOS: Swift code compiles to a native binary that cannot be decompiled back to readable Swift. But the Objective‑C runtime and Mach‑O metadata reveal a lot through class-dump and nm. Class names, method names, strings in the binary — all visible. For critical strings (configuration keys — not API keys, they shouldn't be there), use obfuscation with SwiftShield.

Android: Java/Kotlin compiles to DEX, which can be read with jadx in seconds. R8 (included by default in release builds) minifies and obfuscates. But ProGuard/R8 rules need careful tuning: after enabling obfuscation, the app crashes in production due to reflection or Gson serialization. Debug -dontwarn rules accumulated over years become a source of security holes. Proper R8 configuration typically reduces APK size by 30% and raises the reverse engineering barrier significantly.

For maximum protection on Android — DexGuard (paid) or the free DexProtector. They add runtime protection, string encryption, and integrity checks. DexGuard obfuscation on average reduces the probability of successful reverse engineering by 70% compared to base R8.

Comparison of obfuscation tools

Detecting jailbreak and root

MASVS‑RESILIENCE‑1 requires detection of compromised devices. Standard checks: presence of /Applications/Cydia.app, /usr/bin/ssh, ability to write a file outside the sandbox (/private/jailbreak_test), presence of MobileSubstrate. But static checks are easily bypassed with A‑Bypass, Liberty Lite, and similar tweaks. Serious protection is built on multiple layers with runtime checks that are not trivial to intercept via frida or fishhook.

Ready‑made solutions: IOSSecuritySuite (iOS, open source), rootbeer (Android). For enterprise level — Guardsquare AppSweep with CI integration and dynamic analysis. Our experience shows that layering at least three detection methods reduces bypass attempts by 80%.

Mobile app security engagement deliverables

How we implement protection: a case study from our practice

One of our clients came with a banking app that failed a security audit. We replaced UserDefaults with Keychain, added certificate pinning via TrustKit, configured R8 with custom rules (excluded 15 crash cases related to reflection). Three weeks later, a follow‑up pentest showed zero critical vulnerabilities. Since implementation — zero incidents in two years. Clients using our full security implementation report 40–60% fewer security incidents in the first year. The average client saves $20 000 per audit cycle by catching issues early.

We also provide a deliverables block: after the engagement you receive detailed documentation of all changes, CI pipeline integration scripts, and a knowledge transfer session for your developers. This ensures your team can maintain security independently.

Timeline and cost

• Security audit per OWASP MASVS L1 — from 1 to 2 weeks.
• Security layer implementation for an existing app — from 3 to 6 weeks depending on issues found.
• Full cycle "audit + implementation + test" — from 4 to 8 weeks.

Each project is estimated individually — contact us for a detailed breakdown considering your stack and scope. We work turnkey: from analysis to store deployment.

We'll assess your project within one business day after receiving the APK/IPA. Get in touch — we'll tell you which holes to close first. Schedule a consultation to discuss your mobile app security needs. Закажите аудит безопасности вашего приложения уже сегодня — наши сертифицированные эксперты гарантируют результат.