Privacy Policy — Castle-Key
App Name: Castle-Key Developer: Hamam A. Alabdulla Contact Email: dev.hamam@gmail.com Effective Date: 9 May 2026 Last Updated: 9 May 2026
1. Overview
Hamam A. Alabdulla (“we”, “our”, or “us”) built Castle-Key as a free-to-play game with an optional one-time in-app purchase. This Privacy Policy explains what information is collected when you use Castle-Key, how it is used, and what choices you have.
Castle-Key is designed for a general audience aged 9 and older. We do not knowingly collect personal information from children under 13. See Section 8 for details.
2. Information We Collect
2a. Information We Do NOT Collect
We operate no backend servers for Castle-Key. The following data types are never sent to our servers because we have no servers to receive them:
- Your name, email address, or any account credentials
- Your location
- Your contacts or address book
- Your photos or files
- In-game progress, scores, or completion state (all game state is stored locally on your device using SwiftData and never leaves your device)
- Any personally identifiable information of any kind
2b. Information Collected by Third-Party SDKs (Advertising)
Castle-Key integrates Google AdMob to serve ads in the free version of the game. AdMob may collect the following data types, subject to your consent via Apple’s App Tracking Transparency (ATT) prompt:
Device Identifier (IDFA — Identifier for Advertisers)
- Purpose: Personalized advertising and ad attribution
- Linked to your identity: No
- Used for tracking: Yes, if you grant ATT permission; No, if you deny ATT permission
- Controlled by: Google LLC (see Google’s Privacy Policy)
Advertising Data (ad interaction signals)
- Purpose: Measuring ad performance, improving ad relevance
- Linked to your identity: No
- Used for tracking: Yes, if you grant ATT permission
Crash Data and Performance Data
- Purpose: App stability and functionality improvements
- Linked to your identity: No
- Used for tracking: No
- Note: These are collected by the Google Mobile Ads SDK for SDK health purposes, not by Castle-Key directly.
If you deny the ATT prompt, AdMob serves non-personalized ads only. Your IDFA is not used for cross-app tracking. Crash and performance data may still be collected in a non-tracking, aggregated form.
If you grant the ATT prompt, AdMob uses your IDFA to serve personalized ads and measure ad attribution across apps and websites.
You can change your ATT decision at any time in: Settings > Privacy & Security > Tracking > Castle-Key.
2c. Consent for Users in the European Economic Area (EEA) and UK
For users in the EEA and UK, Castle-Key uses Google’s User Messaging Platform (UMP) to obtain GDPR consent before AdMob initializes. You may accept, reject, or customize consent options through the UMP consent dialog, which appears on first launch.
3. How We Use Information
Since we collect no personal data on our own servers, we have no personal data to use. All data processing described in Section 2b is performed by Google AdMob under Google’s own terms and privacy policies, not by Hamam A. Alabdulla.
The local game state stored on your device (current room, collected keys, premium status) is used solely to provide the game experience. It is never transmitted anywhere.
4. In-App Purchases
Castle-Key offers one optional non-consumable in-app purchase: Castle-Key Premium at $2.99 USD (or local-currency equivalent set by Apple).
All purchase transactions are processed entirely by Apple Inc. through the App Store. We receive only a transaction receipt confirmation from Apple — no payment card details, no billing address, and no personally identifiable financial information. Apple’s handling of purchase data is governed by Apple’s Privacy Policy.
Purchasing Castle-Key Premium removes banner and interstitial ads and unlocks cosmetic player skins. Your purchase is tied to your Apple ID and can be restored on any device signed in with the same Apple ID using the Restore Purchases button in Settings.
5. Third-Party SDKs and Services
Castle-Key includes the following third-party SDKs:
| SDK | Provider | Purpose | Privacy Link |
|---|---|---|---|
| Google Mobile Ads SDK | Google LLC | Display advertising | policies.google.com/privacy |
| Google User Messaging Platform (UMP) | Google LLC | GDPR consent management | policies.google.com/privacy |
We do not include analytics SDKs, crash reporting SDKs (such as Firebase Crashlytics), social login SDKs, or any backend database SDKs. Castle-Key has no Firebase integration.
6. Data Retention
We retain no user data because we collect none. Game state data stored locally on your device is managed by your device’s operating system. Uninstalling Castle-Key will delete all local game data.
Google’s data retention policies for AdMob-collected data are described in Google’s Privacy Policy.
7. Data Security
We apply no server-side data security measures because there is no server-side data. Local game state is stored in your device’s sandboxed app container managed by iOS, which provides standard operating system level protection.
8. Children’s Privacy
Castle-Key is rated 9+ on the App Store and is designed for a general audience. It is not listed in the App Store’s Kids Category and is not specifically directed at children under 13.
We do not knowingly collect personal information from children under 13. If you believe your child has provided personal information to us through the app, please contact us at dev.hamam@gmail.com and we will address the situation promptly.
AdMob serves general-audience (non-child-directed) ads in Castle-Key. The app is not configured with tagForChildDirectedTreatment or tagForUnderAgeOfConsent.
9. Your Privacy Rights
Depending on your jurisdiction, you may have rights including:
- The right to know what data is collected about you
- The right to request deletion of your data
- The right to opt out of the sale or sharing of your personal information
- The right to non-discrimination for exercising your privacy rights
Because Castle-Key collects no personal data on our servers, most of these rights are satisfied by default. For data collected by Google AdMob, exercise your rights directly with Google at policies.google.com/privacy.
For California residents (CCPA): we do not sell personal information. The ad-supported free tier involves sharing device identifiers with Google AdMob for advertising purposes, subject to your ATT consent.
10. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. Changes will be posted at this URL with an updated “Last Updated” date. Continued use of Castle-Key after changes constitutes acceptance of the revised policy. If changes are material, we will provide additional notice within the app where feasible.
11. Contact Us
If you have questions or concerns about this Privacy Policy, contact:
Hamam A. Alabdulla dev.hamam@gmail.com Qatar