Privacy Policy for Jab Al Eid (جاب العيد) Last Updated: [Date]
Introduction We respect your privacy. "Jab Al Eid" was designed with a specific focus on user privacy in social settings. This policy explains what data we collect and how we use it.
Camera and Microphone Usage We do NOT collect, store, or transmit any camera or microphone data.
The game is played entirely offline regarding gameplay mechanics.
The "Curses" (e.g., No Teeth) are physical acts performed by the player; the app does not use facial recognition or audio recording to verify them.
Usage Data: How long you play, which "Curses" are selected most often, and how many times the app is opened.
Device Information: Your device model, operating system version, and general location (country/region).
Crash Logs (Firebase Crashlytics): If the app crashes, we receive a log to help us fix the code. This may include the state of the app at the time of the crash.
Advertising Data: We may use standard advertising identifiers (IDFA/GAID) to show relevant ads via Google AdMob.
To fix technical issues (crashes).
To understand which game packs are popular so we can make more of them.
To display non-intrusive advertisements to support the free version of the app.
Google Analytics for Firebase
Firebase Crashlytics
Google AdMob
Children’s Privacy We do not knowingly collect personally identifiable information from children under the age of 13.
Contact Us If you have questions about this policy, please contact us at: [Your Email Address]
Part 2: How to Answer "App Privacy" in App Store Connect
When you submit the app, Apple will ask: "Do you or your third-party partners collect data from this app?"
You must answer YES (because of Firebase).
Here is exactly how to fill out the form so you get the "Green Checkmark":
Select these options:
Identifiers: Device ID (Used for App Functionality & Analytics).
Usage Data: Product Interaction (Used for Analytics).
Diagnostics: Crash Data (Used for App Functionality).
For each of the above, Apple will ask why you want it. Select:
Analytics (To measure user behavior).
App Functionality (To fix crashes/bugs).
Third-Party Advertising (Only select this if you have AdMob ads active).
Answer: NO.
Why? Because you don't have a login system (email/password). You don't know who the player is, you just know "Device X crashed."
Apple will ask: "Do you use this data to track the user across apps and websites owned by other companies?"
If you use AdMob/Ads: Answer YES. (This triggers the "Allow App to Track?" popup on iOS 14+).
If you do NOT use Ads yet: Answer NO.
Part 3: Where to host this?
You cannot paste text into the App Store; you need a link (URL).
The Free & Fast Method:
Go to Google Docs.
Paste the text from Part 1.
Click "Share" -> "Anyone with the link can view".
Copy that link.
Paste that link into the "Privacy Policy URL" field in App Store Connect.
Important Note for your USP
Even though you are admitting to using Firebase, your Marketing Screenshots should still say "No Camera Needed" (بدون كاميرا).
Privacy Policy = Legal document about data (Firebase).
Marketing = User experience (No photos taken).