Guide for mobile-specific consent management covering Apple ATT framework for iOS, Android permission model, in-app consent flows, SDK consent propagation to third-party libraries, and IDFA/GAID…
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-mobile-app-consent -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills managing-mobile-app-consent --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/managing-mobile-app-consent .claude/skills/managing-mobile-app-consent && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "managing-mobile-app-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-mobile-app-consent into .claude/skills/managing-mobile-app-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-mobile-app-consent", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-mobile-app-consentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-mobile-app-consent -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills managing-mobile-app-consent --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/managing-mobile-app-consent .agents/skills/managing-mobile-app-consent && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "managing-mobile-app-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-mobile-app-consent into .agents/skills/managing-mobile-app-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-mobile-app-consent", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-mobile-app-consent -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills managing-mobile-app-consent --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/managing-mobile-app-consent .cursor/skills/managing-mobile-app-consent && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "managing-mobile-app-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-mobile-app-consent into .cursor/skills/managing-mobile-app-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-mobile-app-consent", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/managing-mobile-app-consent--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-mobile-app-consent -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills managing-mobile-app-consent --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/managing-mobile-app-consent .gemini/skills/managing-mobile-app-consent && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "managing-mobile-app-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-mobile-app-consent into .gemini/skills/managing-mobile-app-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-mobile-app-consent", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mukul975/Privacy-Data-Protection-Skills managing-mobile-app-consentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-mobile-app-consent -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/managing-mobile-app-consent .github/skills/managing-mobile-app-consent && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "managing-mobile-app-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-mobile-app-consent into .github/skills/managing-mobile-app-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-mobile-app-consent", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-mobile-app-consent -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills managing-mobile-app-consent --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/managing-mobile-app-consent .opencode/skills/managing-mobile-app-consent && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "managing-mobile-app-consent" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-mobile-app-consent into .opencode/skills/managing-mobile-app-consent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-mobile-app-consent", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
managing-mobile-app-consentGuide for mobile-specific consent management covering Apple ATT framework for iOS, Android permission model, in-app consent flows, SDK consent propagation to third-party libraries, and IDFA/GAID…
Managing Mobile App Consent is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guide for mobile-specific consent management covering Apple ATT framework for iOS, Android permission model, in-app consent flows, SDK consent propagation to third-party libraries, and IDFA/GAID handling. Addresses platform-specific requirements alongside GDPR and ePrivacy compliance for mobile applications.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).
It sits in Legal & Compliance, covering Privacy and GDPR and Authorization and RBAC. It works with Android and iOS. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Managing Mobile App Consent loads about 1.9k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 658 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 658 words, ~1,924 tokens.
.claude/skills/managing-mobile-app-consent/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Mobile applications present unique consent challenges: platform-level permission systems (Apple ATT, Android runtime permissions), advertising identifiers (IDFA/GAID), SDK-level data collection by third-party libraries, and limited screen real estate for consent interfaces. Compliance requires coordination between GDPR/ePrivacy requirements and platform-specific privacy frameworks.
Apple's ATT framework requires apps to request user permission before tracking across apps and websites owned by other companies. Key aspects:
Purpose String (NSUserTrackingUsageDescription): "CloudVault uses this identifier to measure the effectiveness of our advertising campaigns and provide relevant ads. You can change this in Settings at any time."
Pre-Permission Prompt (shown before ATT dialog): CloudVault SaaS Inc. displays a custom pre-permission screen explaining the value exchange before triggering the system ATT dialog:
"Help us improve CloudVault by allowing measurement of our advertising. This helps us understand which ads brought you here and improve our marketing spend. Your data is never sold. You can change this choice in iOS Settings at any time."
[Continue] → triggers ATTrackingManager.requestTrackingAuthorization()
| ATT Status | Meaning | CloudVault Action |
|---|---|---|
| .notDetermined | User hasn't been asked yet | Show pre-permission screen, then request |
| .authorized | User allowed tracking | Enable IDFA access, attribution SDKs |
| .denied | User denied tracking | Disable IDFA, use SKAdNetwork for attribution |
| .restricted | Tracking restricted by parental controls/MDM | Do not request, use SKAdNetwork |
com.google.android.gms.permission.AD_ID in AndroidManifest.xml to access Google Advertising ID (GAID).Google's Privacy Sandbox for Android introduces:
<!-- AndroidManifest.xml -->
<uses-permission android:name="com.google.android.gms.permission.AD_ID"/>GAID is only accessed if the user has granted consent for advertising purposes through the in-app consent flow. If consent is not granted, GAID is not read.
App First Launch
│
├─► Step 1: Welcome screen with privacy summary
│ "Welcome to CloudVault. Before you get started,
│ let's set up your privacy preferences."
│ [Set Up Privacy]
│
├─► Step 2: Layered consent screen
│ ├─ Purpose 1: Analytics [Toggle, OFF by default]
│ │ "Help us improve CloudVault by sharing anonymous usage data"
│ │ [Learn More] → detailed Art. 13 information
│ │
│ ├─ Purpose 2: Advertising Measurement [Toggle, OFF by default]
│ │ "Measure which ads brought you to CloudVault"
│ │ [Learn More] → detailed information + ATT context
│ │
│ ├─ Purpose 3: Crash Reporting [Toggle, OFF by default]
│ │ "Share crash reports to help us fix bugs faster"
│ │ [Learn More] → data types, retention
│ │
│ └─ "You can change these at any time in Settings > Privacy"
│
├─► Step 3: Record consent decisions
│ ├─ Per-purpose consent records (standard fields)
│ ├─ Platform: iOS/Android
│ ├─ OS version, app version, device model
│ └─ SDK consent propagation (see below)
│
├─► Step 4: Platform-specific follow-up
│ ├─ iOS: If advertising consent granted → trigger ATT dialog
│ └─ Android: If advertising consent granted → access GAID
│
└─► Step 5: Proceed to app
└─ SDKs initialized based on consent stateThird-party SDKs in the CloudVault mobile app must respect user consent:
| SDK | Purpose | Data Collected | Consent Required | Propagation Method |
|---|---|---|---|---|
| Firebase Analytics | Usage analytics | Events, screen views, device info | pur_analytics_001 | FirebaseAnalytics.setAnalyticsCollectionEnabled(granted) |
| Crashlytics | Crash reporting | Stack traces, device state | pur_crash_003 | FirebaseCrashlytics.setCrashlyticsCollectionEnabled(granted) |
| AppsFlyer | Attribution | IDFA/GAID, install referrer | pur_advertising_002 | AppsFlyerLib.start() only if consented |
| Google AdMob | Advertising | IDFA/GAID, device info | pur_advertising_002 | MobileAds.setRequestConfiguration() with consent |
SDKs must not be initialized before consent is obtained. CloudVault SaaS Inc. implements a "consent gate":
| Identifier | Platform | When to Access | When NOT to Access |
|---|---|---|---|
| IDFA | iOS | ATT status = .authorized AND pur_advertising_002 consented | ATT denied/restricted OR advertising consent not granted |
| GAID | Android | pur_advertising_002 consented AND AD_ID permission declared | Advertising consent not granted OR app targets children |
© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/managing-mobile-app-consent of mukul975/Privacy-Data-Protection-Skills.
Open the folder on GitHubat commit 9b2ef9e
Managing Mobile App Consent next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Managing Mobile App Consent this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Cis ControlsSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Tos Clause Scannerzebbern/claude-code-guide | 4.7k | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Healthcare Phi Complianceaffaan-m/ECC | 276k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Policy OpaAgentSecOps/SecOpsAgentKit | 220 | 1 repos | ~3.5k | Automated safety check: Pass | Custom licence | |
| Consent Flowgustavscirulis/snapgrid | 116 | 1 repos | ~2.6k | Automated safety check: Notes | Custom licence |
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert CIS Controls v8 (CIS Top 18) advisor — implementation group scoping (IG1/IG2/IG3), control gap assessments, safeguard-level guidance, asset inventory, software inventory, data protection…
zebbern/claude-code-guide
Audit Terms of Service, user agreements, and privacy policies for consumer risks, producing a structured report that flags unfair clauses, data traps, and liability issues.
affaan-m/ECC
Protected Health Information (PHI) and PII compliance patterns for healthcare applications: data classification, row-level access control, tamper-proof audit trails, schema tagging, and common leak…
AgentSecOps/SecOpsAgentKit
Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA).
gustavscirulis/snapgrid
Generates GDPR/CCPA/DPDP privacy consent flows with granular category preferences, consent state persistence, audit logging, and ATT (App Tracking Transparency) integration.
vinayaklatthe/microsoft-security-skills
Guidance for Microsoft Intune device management — enrollment, configuration, compliance, and security baselines across Windows, macOS, iOS/iPadOS, and Android.
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
mukul975/Privacy-Data-Protection-Skills
Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.
mukul975/Privacy-Data-Protection-Skills
Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.
Categories
Guide for mobile-specific consent management covering Apple ATT framework for iOS, Android permission model, in-app consent flows, SDK consent propagation to third-party libraries, and IDFA/GAID…. Managing Mobile App Consent is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guide for mobile-specific consent management covering Apple ATT framework for iOS, Android permission model, in-app consent flows, SDK consent propagation to third-party libraries, and IDFA/GAID handling.
Managing Mobile App Consent fits situations like: tasks that involve Privacy and GDPR; tasks that involve Authorization and RBAC.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-mobile-app-consent -a claude-code`. Or copy the skill folder (skills/privacy/managing-mobile-app-consent in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/managing-mobile-app-consent in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-mobile-app-consent -a codex`. Or copy the skill folder (skills/privacy/managing-mobile-app-consent in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/managing-mobile-app-consent in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-mobile-app-consent -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managing-mobile-app-consent, .gemini/skills/managing-mobile-app-consent, .github/skills/managing-mobile-app-consent and .opencode/skills/managing-mobile-app-consent in your project.
Going by SKILL.md and its folder, Managing Mobile App Consent needs Python for the scripts in its folder. Our summary lists: Python 3.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Managing Mobile App Consent is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Managing Mobile App Consent: Cis Controls (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), Tos Clause Scanner (zebbern/claude-code-guide, 4.7k stars), Healthcare Phi Compliance (affaan-m/ECC, 276k stars) and Policy Opa (AgentSecOps/SecOpsAgentKit, 220 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 301 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.
Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
