Content Ratings, Policies, and Privacy

Why Content Ratings Matter

The Content Rating Questionnaire

// 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

// 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

// 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

// 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

// 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

// 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

// 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

// 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

// 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

// 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

Lesson Recap