PART 1: IN-APP DISCLAIMERS AND SAFETY NOTICES

1. GENERAL DISCLAIMERS FOR IN-APP DISPLAY

1.1 Service Disclaimer (Display on Registration/Settings)

"THE SERVICE IS PROVIDED 'AS IS' WITHOUT WARRANTIES. WE DO NOT GUARANTEE MATCHES, RELATIONSHIP SUCCESS, OR ANY SPECIFIC OUTCOMES. WE DO NOT CONDUCT BACKGROUND CHECKS BEYOND BASIC IDENTITY VERIFICATION. YOU USE THE SERVICE AT YOUR OWN RISK. SEE FULL TERMS AND CONDITIONS FOR DETAILS."

1.2 No Guarantee Disclaimer (Display on Onboarding)

"IMPORTANT: Jollof and Love facilitates connections but cannot guarantee you will meet compatible partners or form successful relationships. Success depends on many factors beyond our control including your profile, location, user base, compatibility, and communication skills. Results vary significantly among users."

1.3 Background Check Disclaimer (Display on Registration)

"NOTICE: We verify users' age and basic identity through government ID review but DO NOT conduct criminal background checks, sex offender registry searches, or comprehensive screening. You are responsible for your own safety. Always meet in public places and inform friends/family of your plans."

2. SAFETY WARNINGS AND GUIDELINES

2.1 First Meeting Safety Warning (Display Before Exchanging Contact Info)

"SAFETY FIRST: Meeting someone you met online involves risks. For your safety: (1) Meet in apublic, well-lit place; (2) Inform a friend or family member of your plans including time, location, and who you're meeting; (3) Maintain control of your own transportation; (4) Do not share your home address, workplace, or financial information; (5) Never send money to someone you met online; (6) Trust your instincts and leave if you feel uncomfortable; (7) Report suspicious behavior to us immediately. Jollof and Love is not responsible for user conduct or safety during in-person meetings."

2.2 Financial Safety Warning (Display in Messaging/Profile)

"SCAM ALERT: Never send money, gift cards, or financial assistance to someone you met on Jollof and Love. Requests for money are against our Terms and are often scams. Real users will not ask for financial help. If someone requests money, stop communication immediately and report them to us."

2.3 Personal Information Warning (Display in Profile Settings)

"PROTECT YOUR PRIVACY: Do not share your: full name (until you've met in person), home address, workplace address, phone number (until you've established trust), email address, financial information, Social Security number, or passwords. Share personal information gradually as trust is established."

3. LIMITATION OF LIABILITY STATEMENTS

3.1 Comprehensive Liability Disclaimer

"TO THE MAXIMUM EXTENT PERMITTED BY LAW, Jollof and Love AND ITS AFFILIATES ARE NOT LIABLE FOR ANY DAMAGES ARISING FROM: (a) your use of the Service; (b) interactions with other users (online or offline); (c) user content or profiles; (d) unauthorized access to your data; (e) service interruptions; (f) any other matter relating to the Service. OUR TOTAL LIABILITY SHALL NOT EXCEED THE FEES YOU PAID IN THE PAST 12 MONTHS OR $100, WHICHEVER IS GREATER. Some jurisdictions do not allow these limitations, so they may not apply to you."

3.2 Third-Party Conduct Disclaimer

"We are not responsible for other users' conduct, whether online or offline. Users may misrepresent themselves or act inappropriately. You interact with other users at your own risk.
We do not guarantee the accuracy of profiles or the safety of interactions. You release Jollof and Love from all liability related to your interactions with other users."

PART 2: APPLE APP STORE COMPLIANCE GUIDE

1. PRE-SUBMISSION REQUIREMENTS

1.1 Age Rating and Restrictions

Set age rating to 18+ in App Store Connect. Implement age gate during registration requiring users to confirm they are 18+. Complete identity verification requiring government ID upload.

Configure app metadata to indicate mature content. Ensure all marketing materials clearly state 18+ only. Do not market to minors.

1.2 App Privacy Details (Complete in App Store Connect)

Accurately complete the App Privacy questionnaire disclosing: Data Types Collected: Contact info (name, email, phone), identifiers (user ID, device ID), location (precise or approximate), user content (photos, messages, profile), usage data (app interactions), and other relevant data. Data Usage: App functionality, analytics, product personalization, advertising, fraud prevention. Data Linked to User: Profile data, location, messages, usage patterns. Tracking: Indicate if data is used for cross-app tracking (e.g., for advertising). Data Shared with Third Parties: Analytics providers, advertising networks, cloud hosting, payment processors, fraud prevention services.

CRITICAL DISCLOSURE FOR IDENTITY VERIFICATION: In the questionnaire, disclose that you collect government ID and selfie photos. In the privacy policy field, state: 'We collect government ID and selfie for age/identity verification through MANUAL HUMAN REVIEW. We DO NOT use facial recognition or extract biometric data. IDs and selfies are PERMANENTLY DELETED immediately after verification. We retain only verification status and timestamp.'

1.3 Privacy Policy Requirement

Provide publicly accessible Privacy Policy URL hosted on HTTPS domain (must be your own website, not third-party hosting). Link must be working and policy must be complete before submission. Privacy Policy must accurately reflect data collection practices disclosed in App Privacy Details. Include in-app link to Privacy Policy in Settings or Legal section.

2. SAFETY AND CONTENT MODERATION

2.1 Required Safety Features

Implement in-app reporting mechanism easily accessible from user profiles and messages.

Implement blocking functionality allowing users to block other users. Create and display Community Guidelines prohibiting harassment, hate speech, explicit content, illegal activity, and harmful behavior. Implement content moderation system for user photos and profiles (manual review, automated detection, or hybrid). Respond to abuse reports within 24-48 hours for serious violations. Display safety tips prominently during onboarding and accessible in-app. Provide safety resources (links to domestic violence hotlines, sexual assault resources, etc.).

2.2 Prohibited Content and Activities

Your app must not facilitate or contain: Sexually explicit content, pornography, or nudity (implement photo screening); Prostitution, escort services, or sexual services for compensation; Human trafficking or exploitation; Content involving minors (strict age verification required); Hate speech, discrimination, or harassment; Violence, gore, or harmful content; Illegal drugs, weapons, or contraband; Fraud, scams, or deceptive practices. Implement automated and manual moderation to detect and remove prohibited content. Train moderators on content policies. Document moderation processes and actions taken.

3. IN-APP PURCHASES AND SUBSCRIPTIONS

3.1 Apple IAP Integration

ALL digital goods must use Apple's In-App Purchase system. Integrate StoreKit framework for payment processing. Do NOT direct users to external payment methods or websites. Do NOT mention or link to non-Apple payment options. Clearly display subscription terms before purchase: price, duration, billing frequency, auto-renewal. Explain that subscriptions auto-renew unless canceled 24 hours before period end. Provide in-app link to manage subscriptions via Apple ID account settings (Settings > [Your Name] > Subscriptions). Clearly disclose free trial terms including trial duration and post-trial pricing.

3.2 Subscription Management and Transparency

Display all subscription tiers with clear feature comparisons. Include 'Restore Purchases' option for users who reinstall. Honor subscription status across devices via Apple ID. Provide clear path to cancel: App Settings > Manage Subscription > Link to Apple Settings. Disclose that payment is charged to Apple ID and auto-renews. For free trials, prominently state: 'Your subscription will automatically renew at [price]/[period] after the [X-day] free trial unless canceled.'

4. PERMISSION REQUESTS AND JUSTIFICATIONS

Location Permission: Request only when feature needs it (not on launch). Justification: 'Jollof and Love uses your location to show you matches near you and display distance in search results. Your precise location is never shared with other users without your consent.' Implement 'When in Use' permission (not 'Always'). Allow app functionality if permission denied (e.g., manual location entry).

Camera Permission: Request when user attempts to take photo. Justification: 'Jollof and Love needs camera access to take profile photos and selfies for identity verification.' Provide alternative to select from photo library if denied.

Photo Library Permission: Request when uploading photos. Justification: 'Jollof and Love needs access to your photos to upload profile pictures and share images with matches.' Support limited photo selection (iOS 14+).

Notifications Permission: Request after demonstrating value. Justification: 'Jollof and Love sends notifications when you receive messages, get new matches, or have important account updates.' Allow users to customize notification types in settings.

5. TECHNICAL REQUIREMENTS

App must be stable, complete, and fully functional at submission. No placeholder content, broken links, or incomplete features. All features advertised in description must work correctly. Test thoroughly on multiple iOS versions and devices (latest iOS and iOS minus 1 minimum).

Optimize performance: fast load times, minimal battery drain, efficient memory usage. Handle errors gracefully with user-friendly messages. Implement proper state restoration if app is terminated. Support all required device orientations (portrait minimum for dating apps). Include accessible labels and VoiceOver support for accessibility. Support Dark Mode if your app has custom UI.

6. APP STORE SUBMISSION CHECKLIST

Age rating set to 18+. App Privacy Details completed accurately and completely. Privacy Policy URL provided and working. Clear permission request explanations. Age verification implemented (18+ requirement). Identity verification with ID upload functional. ID/selfie deletion after verification confirmed. Reporting and blocking features implemented and tested. Community Guidelines created and displayed. Content moderation system active. Safety Tips section included. Apple IAP integrated for all digital purchases. Subscription terms clearly displayed. Manage subscription link implemented. App tested on multiple devices and iOS versions. All features functional and bug-free. Screenshots show actual app functionality (no mockups). App description accurate without exaggerated claims. Demo account prepared with sample profiles for reviewers. Special testing instructions documented if needed. Contact information and support resources provided. Terms and Conditionsaccessible in app.

PART 3: GOOGLE PLAY STORE COMPLIANCE GUIDE

1. PRE-SUBMISSION REQUIREMENTS

1.1 Content Rating

Complete IARC content rating questionnaire to receive 'Mature 18+' rating. Answer questions honestly about: sexual content (dating/romantic themes); violence (should be none or minimal); language (user-generated); controlled substances (should be none); gambling (should be none); user interaction features (yes - unfiltered user-generated content, ability to share location and personal information, unrestricted internet access). Rating determines app availability and age restrictions.

1.2 Data Safety Section (Complete in Play Console)

Accurately complete Data Safety disclosing: Data Collected: Personal info (name, email, phone, DOB, photos), location (precise or approximate), messages/communications, app activity, device identifiers, payment info (processed by third parties). Data Usage: App functionality, personalization, analytics, fraud prevention, advertising, communication. Data Sharing: Shared with service providers (hosting, payments, analytics), advertising partners, fraud prevention services. Security Practices: Data encrypted in transit (TLS/SSL), data encrypted at rest (AES 256), option to request data deletion, data handling follows industry best practices. CRITICAL: For ID verification, state: 'We collect government ID and selfie photos for manual age/identity verification. We do NOT use facial recognition or biometric technology. IDs and selfies are permanently deleted immediately after manual review. We retain only verification status and timestamp, not images or biometric data.'

1.3 Privacy Policy

Host Privacy Policy on secure website (HTTPS) that you control. Link Privacy Policy in: Play Console during app submission; App Store listing; In-app (Settings or About section). Privacy Policy must be easily accessible and match Data Safety disclosures. Update Privacy Policy before changing data practices.

2. USER-GENERATED CONTENT AND MODERATION

2.1 Moderation Requirements

Google requires apps with user-generated content to: Implement reporting system accessible from profiles, messages, and content. Implement blocking functionality. Create and enforce Community Guidelines prohibiting: sexual content and nudity; hate speech and discrimination; harassment and bullying; violence and dangerous content; illegal activity; spam and scams; impersonation; child endangerment. Implement content moderation combining: automated detection (AI/ML for explicit content, prohibited terms); manual review of flagged content; user reporting; proactive monitoring. Respond to reports promptly (24-48 hours for serious violations). Document moderation actions and maintain logs. Train moderators on policies and legal requirements.

2.2 Required Policies and Enforcement

Clearly communicate policies to users during onboarding. Enforce policies consistently with: warnings for minor first violations; temporary suspension for repeated or moderate violations; permanent ban for serious violations (illegal activity, severe harassment, child safety issues, fraud). Document enforcement decisions for potential appeals or legal requests. Cooperate with law enforcement when legally required.

3. PERMISSION DECLARATIONS AND JUSTIFICATIONS

In Play Console Permissions section, declare all permissions and provide justifications. Prominent Disclosure required for sensitive permissions:

ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION: Usage: 'Display matches near user, show distance in search results, location-based features.' Prominent Disclosure: 'Jollof and Love collects location data to show nearby matches and calculate distances even when the app is closed or not in use.' (Adjust based on when you collect.) Alternatives if denied: Manual location entry, broader geographic matching.

CAMERA: Usage: 'Take profile photos, capture selfies for identity verification.' Prominent Disclosure: 'Jollof and Love needs camera access to take photos for your profile and for identity verification purposes.' Alternative: Photo library selection.

READ_EXTERNAL_STORAGE / READ_MEDIA_IMAGES: Usage: 'Upload photos from device to profile, share images with matches.' Prominent Disclosure: 'Jollof and Love needs access to your photos to upload profile pictures.' Consider scoped storage (Android 10+) for better privacy.

INTERNET: No justification required (standard permission). ACCESS_NETWORK_STATE: No justification required (determines connection type).

4. MONETIZATION AND BILLING

Integrate Google Play Billing Library for all in-app purchases. ALL digital goods and subscriptions must use Google Play Billing. Do NOT direct users to external payment methods. Clearly display before purchase: subscription price, billing frequency, trial period duration (if applicable), auto-renewal terms, cancellation instructions. State: 'Subscription automatically renews unless canceled at least 24 hours before end of current period.' Provide in-app link to:

Google Play subscription management (Subscriptions section of Play Store). Honor subscription status across devices via Google account. Implement subscription features: upgrade/downgrade paths; grace period for failed payments; subscription hold/pause (optional but recommended); restore purchases functionality.

5. PROHIBITED CONTENT AND ACTIVITIES

Your app must not facilitate or promote: Sexual Content: pornography, explicit sexual acts, sexually suggestive content, escort services, prostitution. Child Safety: any content exploiting or endangering children, child sexual abuse material (CSAM). Dangerous Activities: human trafficking, drug trafficking, weapons sales, illegal services. Hate Speech: content promoting violence or discrimination based on protected characteristics. Harassment and Bullying: content that harasses, threatens, or abuses individuals. Impersonation and Deception: fake profiles, catfishing, scams, fraud. Spam: repetitive, unsolicited commercial messages. Implement policies prohibiting these activities and enforce them through moderation.

6. TECHNICAL AND QUALITY REQUIREMENTS

App must be stable and functional: No frequent crashes, freezes, or force closes. Proper error handling with user-friendly messages. Graceful degradation when network unavailable. Test on variety of: Android versions (latest and 2 previous versions minimum); device types (phones, tablets, various screen sizes); network conditions (Wi-Fi, cellular, offline). Performance optimization: Fast startup and load times; Minimal battery consumption; Efficient memory usage; Reasonable data consumption. Follow Android design guidelines: Material Design principles; Proper back button behavior; System notifications follow guidelines; Runtime permissions handled correctly. Accessibility: Content descriptions for images; Text readable without magnification; Interactive elements properly sized; Support for accessibility services (TalkBack).

7. GOOGLE PLAY SUBMISSION CHECKLIST

IARC content rating completed (Mature 18+). □ Data Safety section completed accurately. Privacy Policy URL provided (hosted on secure site). All permissions declared with justifications. Prominent disclosures for sensitive permissions included. Age verification implemented (18+ requirement). Identity verification with ID upload working. ID/selfie deletion after verification confirmed. Reporting and blocking features implemented. Community Guidelines created and accessible. Content moderation system active. Google Play Billing integrated. Subscription terms clearly displayed. Subscription management link implemented. App tested on multiple Android versions and devices. Stability verified (no crashes or major bugs). Screenshots show real app functionality. Store listing descriptionaccurate and compliant. Demo account available with sample profiles. Developer contact information complete. Terms and Conditions accessible in-app. Support and help resources provided.

8. POST-LAUNCH COMPLIANCE

Maintain compliance after launch: Monitor user reviews for safety concerns, bugs, or policy violations. Respond to abuse reports promptly. Update app regularly with security patches and bug fixes. Update Privacy Policy and Data Safety when practices change. Monitor Google Play policy updates (policies change regularly). Maintain content moderation quality and responsiveness. Keep subscription features working correctly. Respond to Google Play compliance notifications immediately. Maintain developer account in good standing.