React Native Academy · 课时

内容分级、政策与隐私

完成内容分级问卷，在“数据安全”部分声明数据安全实践，并确认遵守 Google Play 政策以避免审核被拒。

第 3 / 4 课13 个步骤

内容分级、政策与隐私 是 CoddyKit 上的免费 React Native Academy 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 React Native Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 React Native Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Why Content Ratings Matter

Content ratings tell users (and parents) what kind of content an app contains and what age group it is appropriate for. Google Play requires you to complete a content rating questionnaire for every app. The rating is computed automatically based on your answers — you cannot choose it manually. An incorrect rating (e.g., marking a violent game as 'Everyone') risks policy violation and removal from the store.

The Content Rating Questionnaire

The questionnaire is found in Play Console under Policy > App content > Ratings. It asks about: violence, sexual content, profanity, controlled substances, gambling, user-generated content (UGC), and whether the app targets children. Your honest answers generate an IARC rating (International Age Rating Coalition) which is converted to regional equivalents (ESRB in the US, PEGI in Europe, USK in Germany, etc.).

// Common questionnaire categories:
// Violence:
//   - Does it depict violence? Cartoonish or realistic?
//   - Is there graphic injury or gore?
// Sexual content:
//   - Is there nudity or sexual themes?
// Profanity:
//   - Does the app contain crude language?
// Substances:
//   - References to alcohol, tobacco, drugs?
// Gambling:
//   - Real-money gambling? Simulated gambling?
// User content:
//   - Does the app allow user-generated content?
//   - Can users share content publicly?

Rating Results and Regional Equivalents

After completing the questionnaire, Play Console shows your IARC rating and regional equivalents. A typical productivity app gets Everyone (ESRB) / 3+ (PEGI). An app with mild cartoon violence might get Everyone 10+. Understanding regional equivalents matters for global launches — some regions restrict certain ratings to adult devices or require parental consent flows. Ratings expire only if you significantly change the app's content.

// Rating equivalents for a typical clean productivity app:
// ESRB (USA):         Everyone (E)
// PEGI (Europe):      3+
// USK (Germany):      0+
// CERO (Japan):       A (All Ages)
// ClassInd (Brazil):  Livre
// OFLC (Australia):   G

// A game with combat might get:
// ESRB:  Teen (T)
// PEGI:  12
// USK:   12

Target Audience and Apps for Children

The Target Audience section (Policy > App content > Target audience and content) determines if your app is designed for children. If you select an age range that includes children under 13, Google applies the Families Policy automatically: no behavioral advertising, no third-party trackers (unless COPPA-certified), no deceptive design patterns, and the app must use child-safe APIs only. Neutral apps (not specifically for children) should select 13+ as the minimum target age.

// Target audience options:
// Ages 5 and under
// Ages 6-8
// Ages 9-12
// Ages 13-15  <- no Families Policy applies
// Ages 16-17
// Ages 18+

// If you select any age under 13 AND your app
// is designed for children:
// - Families Policy applies
// - No behavioral ads (AdMob Families mode)
// - No IDFA/AAID collection
// - No in-app purchases without parental consent
// - Must pass Families Policy review

Google Play Policies Overview

The Google Play Developer Program Policies cover a wide range of content and behavior rules. Key areas include: Intellectual property (no fake celebrity apps, no icon/name copying), Deceptive behavior (no fake reviews, no misleading functionality claims), Malware (no apps that collect data without disclosure), User data (the Data Safety section must accurately reflect your data practices), and Monetization (no unauthorized subscription manipulations).

// Common policy violations that cause removal:
// 1. App impersonates another brand
//    (similar name/icon to popular app)
// 2. App requests unnecessary permissions
//    (CONTACTS for a calculator)
// 3. App uses deceptive ad placement
//    (close button too small, ads placed near buttons)
// 4. App uses undisclosed data collection
//    (sending device ID to server without disclosure)
// 5. Subscription cancellation made deliberately hard
//    (dark patterns in billing flows)

Data Safety Section

The Data Safety section (Policy > App content > Data safety) is Google's equivalent to Apple's Privacy Nutrition Label. You declare what data your app collects (name, email, location, etc.), whether it is shared with third parties, whether it is encrypted, and whether users can request deletion. This information appears on your Play Store listing. The declaration must match your actual app behavior — inaccurate declarations can cause policy violations.

// Data Safety categories to declare:

// Location:
//   Approximate location (GPS at city level)
//   Precise location (GPS coordinates)
//   Whether location is shared with third parties

// Personal info:
//   Name, Email, Phone number
//   User IDs, Address

// Device or other IDs:
//   Device or other IDs (Firebase installation ID, advertising ID)

// App activity:
//   App interactions, In-app search history, Installed apps

// For each data type:
//   - Is it collected?
//   - Is it shared with third parties?
//   - Is it required or optional?

GDPR and CCPA Compliance

If your app is available in the EU or California, you must comply with GDPR (EU) and CCPA (California). Key requirements: obtain explicit consent before collecting personal data, provide a way to delete user data on request, disclose what data is collected and why, and have a privacy policy. For apps using advertising, implement a consent management platform (CMP) that shows a GDPR consent dialog to EU users before loading ads.

// GDPR compliance checklist for React Native apps:

// 1. Privacy policy: Live URL, in user's language
// 2. Consent: Collect BEFORE any data collection
//    Use UMP SDK (Google) or a CMP for ads
// 3. Right to deletion: In-app 'Delete my account' option
//    (Google Play requires this from 2024)
// 4. Data minimization: Only collect what you need
// 5. Storage limitation: Delete data when no longer needed

// Account deletion requirement (from Dec 2023):
// All apps must offer in-app account deletion
// Accessible from Settings or Profile screen

Permission Best Practices

Google's policies require that permissions are necessary and proportional to the app's function. Request only the permissions you actually use. Never request READ_CONTACTS for an app that doesn't use contacts. Request permissions contextually — only when the feature requiring them is first used, not at app launch. Never ask again after a user declines twice — show a graceful message explaining the limitation instead.

// Permission best practice in React Native:
import { PermissionsAndroid } from 'react-native';

async function requestCameraIfNeeded() {
  // Only request when user taps 'Open Camera'
  const granted = await PermissionsAndroid.request(
    PermissionsAndroid.PERMISSIONS.CAMERA,
    {
      title: 'Camera Permission',
      message: 'This app needs your camera to scan QR codes.',
      buttonNeutral: 'Ask Me Later',
      buttonNegative: 'Cancel',
      buttonPositive: 'OK',
    }
  );

  if (granted === PermissionsAndroid.RESULTS.GRANTED) {
    openCamera();
  } else {
    showCameraUnavailableMessage();
  }
}

Advertising ID and Behavioral Ads

If your app uses the Advertising ID (AAID) for behavioral advertising, you must: declare this in the Data Safety section, provide a privacy policy that explains ad targeting, and respect the user's Opt out of Ads Personalization setting (accessible in Android system settings). Apps targeting children must not use AAID at all. Violating advertising ID policies can result in app removal or developer account suspension.

// Check if user has opted out of ad personalization
import { NativeModules } from 'react-native';

// If using Google Mobile Ads SDK:
import MobileAds from 'react-native-google-mobile-ads';

async function initAds() {
  const adapterStatuses = await MobileAds().initialize();

  // Check consent status before showing personalized ads
  // Use Google's User Messaging Platform (UMP) SDK:
  // https://developers.google.com/admob/react-native/privacy
  const consentInfo = await ConsentInformation.requestConsentInfoUpdate();
  if (consentInfo.isConsentFormAvailable) {
    await ConsentForm.loadAndShowConsentFormIfRequired();
  }
}

Responding to Policy Violations

If Google detects a policy violation, you receive an email and a notification in Play Console with a warning (fix within a deadline) or an app removal. Repeated violations can result in developer account termination. To respond: read the policy cited, fix the violation, and submit an appeal explaining your changes. For account appeals, the Google Play Policy Help Center has a formal appeals process. Act quickly — warnings expire and unresolved issues become permanent strikes.

// Policy violation response workflow:
// 1. Read the violation notice (specific guideline cited)
// 2. Fix the violation in code or metadata
// 3. Build and submit a new version
// 4. Submit an appeal in Play Console:
//    Policy status > Appeal
//    Explain: 'We removed the feature X that caused the
//    violation. The updated version (1.2.1) no longer
//    collects location data without user consent.'
// 5. Update your privacy policy if data practices changed
// 6. Update the Data Safety section to match

Pre-launch Reports and Security Testing

Play Console's Pre-launch report automatically tests your app on real Google devices when you upload to internal testing. It checks for crashes, ANRs, security vulnerabilities (SSL issues, exposed debug APIs), accessibility issues (small touch targets, missing content descriptions), and performance metrics. Review this report before promoting to production — it catches issues that manual testing might miss and reflects Google's automated policy checks.

// Pre-launch report sections (found in Play Console):
// Testing > Pre-launch report

// Security:
//   - SSL certificate validation errors
//   - Exposed debug endpoints
//   - Cleartext HTTP traffic (must use HTTPS)

// Accessibility:
//   - Touch targets < 48dp
//   - Missing contentDescription on images
//   - Text too small to read

// Performance:
//   - CPU usage during key flows
//   - Memory consumption
//   - Render frame rate

// Crashes:
//   - Automated test suite crash report
//   - Stack traces for any crashes found

Quick Check

Test your understanding of React Native Mobile Development concepts from this lesson.

在交互式课程中回答

Lesson Recap

In this lesson you learned: how to complete the content rating questionnaire and understand IARC regional ratings, how to fill out the Data Safety section accurately to match your app's actual data practices, and how GDPR, CCPA, and Google's permission policies affect your app. You also saw how the Pre-launch report helps catch issues before production. Next up we cover internal testing, staged rollout, and promoting to production.

免费开始

用 AI 导师学习 JavaScript — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 30
课程: 120

免费开始学习查看完整课程

常见问题解答

「内容分级、政策与隐私」课时是免费的吗？

是的 — 「内容分级、政策与隐私」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 React Native Academy 课程的其余内容，请升级到 CoddyKit PRO。 React Native Academy 课程共包含 4 节课。

「内容分级、政策与隐私」这节课中我会学到什么？

完成内容分级问卷，在“数据安全”部分声明数据安全实践，并确认遵守 Google Play 政策以避免审核被拒。你通过在浏览器中直接运行的动手代码来练习 React Native Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 React Native Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 React Native Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「内容分级、政策与隐私」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 React Native Academy 课中编写并运行代码吗？

能。每节 React Native Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 React Native Academy