Skip to content
For mobile-first MENA apps

Apple, Google, and SDAIA
all want the same thing.

Privacy Manifest. App Tracking Transparency. Play Data Safety. Saudi PDPL. Arabic + RTL banner. The four things every MENA app dev wires from scratch — landed in one SDK, $50/month per app. No five-figure CMP contract. No web subscription required.

Apple

Privacy Manifest + ATT

~40% of App Store rejections trace to a missing or wrong manifest. Ours ships valid.

Google

Play Data Safety + GCM v2

April 2025 tightening on Android ID classification baked in. Firebase mapping included.

MENA

PDPL · UAE · Egypt · GCC

Saudi PDPL is active (48 enforcement decisions confirmed by SDAIA). UAE Federal regs landing. Country-aware out of the box.

Users

Arabic + RTL native

SwiftUI + Compose. Two-step UX. EN + AR copy ships. RTL-aware. Not bolted on.

Five lines and you’re live

Configure once in your app entry point, drop the banner where it makes sense, and track events. Consent gating happens automatically.

iOS — Swift

ContentView.swift
import Arqam360

@main
struct MyApp: App {
    init() {
        Arqam360.shared.configure(apiKey: "ak_...")
    }

    var body: some Scene {
        WindowGroup {
            ContentView()
                .sheet(isPresented: $showBanner) {
                    ConsentBanner(language: .arabic) { _ in
                        showBanner = false
                    }
                }
        }
    }
}

// Track events. Auto-gated by analytics consent.
Arqam360.shared.track("cart_started", properties: ["sku": "ABC123"])

Android — Kotlin

MainActivity.kt
class MyApp : Application() {
    override fun onCreate() {
        super.onCreate()
        Arqam360.configure(this, apiKey = "ak_...")
    }
}

@Composable
fun MainScreen() {
    var showBanner by remember { mutableStateOf(Arqam360.shouldShowBanner) }
    Box {
        AppContent()
        if (showBanner) {
            ConsentBanner(language = BannerLanguage.AR) { _ ->
                showBanner = false
            }
        }
    }
}

// Track events. Auto-gated by analytics consent.
Arqam360.track("cart_started", mapOf("sku" to "ABC123"))

Install

Both SDKs ship as v0.1.0. Maven Central + CocoaPods Trunk publishing is in flight; until then, JitPack and SPM Git refs work today.

Swift Package Manager
// Package.swift
dependencies: [
    .package(url: "https://github.com/arqam360/ConsentIQ.git",
             from: "0.1.0"),
],
targets: [
    .target(
        name: "MyApp",
        dependencies: [
            .product(name: "Arqam360",
                     package: "ConsentIQ"),
        ]
    )
]
CocoaPods (after Trunk publish)
# Podfile
pod 'Arqam360', '~> 0.1.0'
Gradle + JitPack (works today)
// settings.gradle.kts
dependencyResolutionManagement {
    repositories {
        maven { url = uri("https://jitpack.io") }
    }
}

// app/build.gradle.kts
dependencies {
    implementation("com.github.arqam360:ConsentIQ:0.1.0")
}
Maven Central (after we publish)
// app/build.gradle.kts (after Maven Central publish)
dependencies {
    implementation("com.arqam360:arqam360-android:0.1.0")
}

Manual setup vs. Arqam360 SDK

Everything a MENA mobile team wires from scratch — and what the SDK gives you on day one.

Without a CMP SDK

  • Hand-roll Apple Privacy Manifest from your Podfile.lock
  • Fill the App Privacy Label form for every SDK you ship
  • Fill Play Data Safety across every Gradle dependency
  • Wire the App Tracking Transparency prompt and consent state
  • Implement Consent Mode v2 default + update signals yourself
  • Translate the banner into Arabic and handle RTL layout
  • Source PDPL templates for Saudi, UAE, Egypt, GCC separately
  • Maintain all of the above as platforms update their rules

With Arqam360

  • Privacy Manifest auto-generated from Podfile.lock
  • App Privacy Label assembled from your SDK declarations
  • Play Data Safety form built from Gradle dependencies
  • ATT prompt + consent state wired into one SDK call
  • Consent Mode v2 signals fire automatically on consent change
  • Arabic + RTL banner ships out of the box
  • MENA PDPL templates included, country-aware by default
  • SDK updates ship through SPM / Gradle when rules change

Same SDK call. Native UI on each platform.

One configure() call. iOS renders a SwiftUI sheet. Android renders a Material 3 dialog. Both bilingual. Both PDPL + GDPR + ATT compliant.

9:41
●●●▮▮▮

إعدادات الخصوصية

Privacy preferences

NecessaryON
Analytics
Marketing

Powered by Arqam360

iOS · SwiftUI
9:41
●●●▮▮▮

إعدادات الخصوصية

Privacy preferences

NecessaryON
Analytics
Marketing

Powered by Arqam360

Android · Material 3

What ships in v0.1

Six things you would otherwise wire from scratch — implemented, tested against Apple + Google review, ready to drop into your app.

Consent recording + storage

Stable per-install anonymous ID. SharedPreferences / UserDefaults persistence. Audit-trail every accept, reject, and category-level change.

Bilingual EN + AR banners

SwiftUI on iOS, Jetpack Compose on Android. RTL-aware. Two-step UX (summary → customize). The Powered-by-Arqam360 footer is locked — that pays for the price.

ATT + GCM v2 wired

App Tracking Transparency wrapper on iOS. Google Consent Mode v2 signal mapping for Firebase Analytics on both platforms. No more guesswork on signal naming.

Event tracking

track / screen / identify / reset — Segment-shaped API every mobile dev already knows. Consent-gated automatically; deny categories suppress at source.

Zero third-party deps

iOS: pure Foundation + SwiftUI, no CocoaPods bloat. Android: AndroidX + Compose only, no OkHttp, no Gson. SDK weight under 100KB compiled.

Open source under MIT

github.com/arqam360/ConsentIQ — both SDKs in the monorepo. Audit the code before you ship. Fork the banner. Patch what you need.

$50/month per app

Standalone subscription. One iOS or Android app. 14-day free trial.

Most-cited alternatives charge $10K+/year. Open the SDK source on GitHub before you commit.

Start your trial

Shipping more than one app? Bundle pricing kicks in from app #2 — adjust at any time from billing.

Questions developers ask before installing

Real questions from real iOS and Android teams.

Ship a compliant app this afternoon.

iOS + Android SDKs, four free generators, one dashboard for both surfaces.

Early access — first paying mobile customers get 50% off year one.

A note on v0.1.0

v0.1.0 is tagged and validated end-to-end on CI: real Xcode 16 builds the iOS SDK + runs unit tests on iOS Simulator, real Gradle 8.5 + AGP 8.2 builds the Android AAR + runs JVM tests. Both SDKs are open-source under MIT — audit before shipping. CocoaPods Trunk and Maven Central publish are in flight; today's working install paths are Swift Package Manager via the GitHub repo and JitPack from the same monorepo. First-customer support: founder is on call for any v0.1.x integration issue, with same-day v0.1.x patch turnaround. Email admin@arqam360.com if your team is integrating and you'd like priority support.