Privacy Policy for ArcadeForge Studios and OurAppsX

Effective date: April 3, 2026

This Privacy Policy explains how ArcadeForge Studios, operating through OurAppsX, collects, uses, stores, shares, and protects information when you visit our website, contact us, or use any mobile application, game, tool, or related digital service that links to this Policy. It is written to support practical marketplace compliance across Apple App Store and Google Play distribution environments, while also providing a clear explanation of our operational approach to advertising, age handling, analytics, support, billing, and user rights.

1. Scope of this Policy

This Policy applies to the following categories of activity:

• Visits to our public-facing website located at ourappsx.com and associated pages.
• Direct communications sent to support@ourappsx.com, bussiness@ourappsx.com, Junaidah@ourappsx.com, or any other official ArcadeForge Studios communication channel.
• Use of iOS, iPadOS, Android, or other software products published by ArcadeForge Studios or distributed under the OurAppsX identity, where the product links to this Policy.
• Use of applications or games that contain advertising, in-app purchases, analytics, crash reporting, account-light service features, content synchronization, or customer support modules.

This Policy does not apply to third-party websites, third-party app stores, payment processors operated by platform owners, advertising partner properties, or services that are not controlled by ArcadeForge Studios, even if our products link to them or embed their SDKs. Those services have their own privacy terms and operational controls.

2. Who we are and how to contact us

ArcadeForge Studios is an independent software studio operating through the domain ourappsx.com. For privacy-related questions, data requests, support matters, or policy clarification, you may contact us using the following channels:

• General support: support@ourappsx.com
• Business inquiries: bussiness@ourappsx.com
• Enterprise or strategic matters: Junaidah@ourappsx.com

Where we determine that a request concerns privacy rights, marketplace disclosures, consent handling, billing support boundaries, or age-sensitive ad treatment, we may route the request internally to the appropriate decision-maker before responding.

3. Categories of information we may collect

3.1 Information you provide directly

• Contact details such as your name, email address, company name, or the contents of your message when you contact us.
• Support details such as product name, device model, OS version, screenshots, purchase context, issue description, and any information you voluntarily include to help us diagnose a problem.
• Business details included in partnership or commercial outreach, such as proposed collaboration type, market focus, campaign data, or technical requirements.

3.2 Information generated by your use of our website or apps

• Basic technical data such as IP address, browser type, device type, operating system, app version, language preference, and approximate regional signals.
• Interaction data such as session starts, feature usage, crash occurrence, screen transitions, retention events, or funnel milestones, depending on the product.
• Advertising-related signals such as consent state, ad request eligibility, impression events, reward completion, frequency capping identifiers, and age treatment flags where relevant.

3.3 Information provided by platform providers or integrated services

• Transaction status and purchase confirmation signals from Apple App Store, Google Play, or equivalent official app marketplace systems. We do not receive your full card number or full payment credentials from those platforms.
• Receipt validation outputs, entitlement status, subscription state, or refund-related platform events where those are needed to deliver paid digital features correctly.
• Aggregated diagnostics, attribution signals, or fraud-prevention signals from analytics, measurement, crash-reporting, or advertising providers integrated into a product.

4. Why we process information

We process information for legitimate and practical operational reasons, including:

• To provide and maintain our website, apps, games, and customer support operations.
• To diagnose bugs, crashes, compatibility issues, or monetization errors.
• To process lawful in-app entitlement checks and restore access to legitimately purchased premium content.
• To measure feature adoption, optimize performance, evaluate funnels, and improve product design.
• To support responsible advertising delivery, reward fulfillment, ad fraud prevention, pacing controls, and campaign effectiveness measurement.
• To prevent abuse, security incidents, policy violations, or improper use of premium features.
• To meet legal obligations, respond to valid regulatory or legal requests, and maintain records necessary for operational accountability.

5. Legal and operational bases for processing

Depending on your region and the context in which information is processed, we may rely on one or more of the following operational bases:

• Your consent, where consent is required for certain advertising, tracking, or optional data-processing activities.
• Performance of a contract or service relationship, such as providing app functionality, restoring purchases, or responding to support requests.
• Legitimate interests in maintaining service reliability, improving product quality, preventing abuse, and operating a sustainable business, provided those interests are balanced against user expectations and applicable law.
• Compliance with legal obligations, including obligations connected to taxation, consumer protection, legal process, or platform governance.

6. App Store and Google Play privacy adaptation

We publish products in ecosystems with distinct review and disclosure frameworks. Our privacy approach is designed to adapt to both Apple App Store and Google Play expectations without treating those requirements as superficial checklist items.

6.1 Apple ecosystem adaptation

For Apple-platform products, we aim to ensure that privacy disclosures are consistent with the categories of data actually used by the application, including data linked to the user where applicable, diagnostics, purchase-related entitlement data, and ad-related signals. Where a product requests tracking permission, that prompt is intended to appear only when operationally justified and where the applicable Apple permission framework requires user authorization before cross-app or cross-property tracking occurs.

We also design Apple-platform products to use official in-app purchase channels for digital content, premium tools, subscriptions, consumables, or feature unlocks that fall within Apple marketplace payment rules. When a product requires account restoration or subscription status handling, the relevant receipt or entitlement information may be processed to confirm access, renew service rights, or prevent duplicate or fraudulent benefit claims.

6.2 Google Play ecosystem adaptation

For Android products distributed through Google Play, we aim to align privacy practices with the product’s declared data handling, SDK behavior, age suitability, ad treatment, and billing functionality. This includes describing whether the app collects technical identifiers, diagnostics, crash data, approximate region data, or advertising signals, and whether that information is processed for app functionality, analytics, fraud prevention, personalization, or advertising.

Where Google Play Billing is used for digital goods or digital feature access, purchase processing is routed through the official store channel rather than direct off-platform payment collection inside the app where store rules require official billing. We may receive limited transaction and entitlement information from Google Play to confirm purchase state, renew access, or handle subscription restoration.

6.3 Cross-platform principle

When a product is available on both Apple App Store and Google Play, the exact data-processing flows may differ because platform SDKs, consent mechanics, device-level permissions, billing interfaces, and policy frameworks differ. Our intention is not to create contradictory disclosures, but to make sure each marketplace presentation accurately reflects the real behavior of the product as distributed in that environment.

7. Advertising, monetization, age handling, and privacy choices

Some ArcadeForge Studios products are monetized through IAA, meaning in-app advertising. In those products, advertising is not treated as a generic add-on. It is governed as part of the product experience and therefore subject to policy, privacy, and age-treatment controls.

7.1 What advertising-related data may be processed

• Device or app identifiers permitted by the platform or advertising framework.
• Consent state or privacy choice signals, including whether a user has granted or denied certain categories of ad-related processing where required.
• Approximate geography or locale information used for campaign eligibility, legal compliance, language selection, or reporting.
• Ad request data, impression events, reward completion status, viewability or anti-fraud signals, and ad frequency capping data.
• Contextual signals such as session state, placement type, level completion, or feature-trigger context needed to serve and measure a particular placement.

7.2 Age-sensitive advertising treatment

We recognize that age treatment is a compliance and safety issue, not merely a commercial setting. For products directed to broad audiences, mixed audiences, or younger users, we may implement one or more of the following controls depending on product category, storefront settings, region, and SDK capabilities:

• Use of age screens or age gates where operationally appropriate and permitted.
• Marking users or sessions for restricted ad treatment, child-directed handling, teen treatment, or non-personalized delivery where product design or platform policy indicates this is necessary.
• Disabling personalized advertising or certain categories of ad targeting where the user is known or treated as under a relevant age threshold.
• Limiting data sharing for ad measurement or behavioral profiling where platform or legal rules require a stricter handling model.
• Favoring contextual or less data-intensive ad serving modes for sensitive age categories or consent-restricted environments.

Not all products are intended for children, and some may be designed for general or older audiences only. Where a product is not directed to children, we still may implement age-sensitive safeguards when policy, SDK capabilities, or regional legal requirements make them appropriate.

7.3 Personalized and non-personalized advertising

Depending on the product, region, device settings, platform permission state, and consent status, advertisements may be personalized, contextual, or non-personalized. Personalized advertising typically relies on additional signals to improve relevance. Non-personalized advertising may still use limited contextual data, approximate region, anti-fraud measures, basic delivery controls, or frequency capping, but is not intended to rely on full behavioral profiling in the same way as personalized advertising.

7.4 Rewarded advertising

Where a product offers rewarded video or another reward-based ad format, the system may record whether the reward was offered, initiated, completed, canceled, or credited so that the promised in-app benefit can be delivered reliably and abuse can be prevented. Rewarded advertising is generally structured as an opt-in action tied to explicit user value.

7.5 Advertising partners

We may work with third-party advertising networks, mediation providers, analytics providers, attribution partners, anti-fraud services, and measurement vendors. Those providers may process data according to their own role, contract, and privacy terms. We aim to configure them in a way that supports legal compliance, consent signaling, and age-sensitive treatment, but we do not control every downstream operational detail of an independent third-party platform.

8. In-app purchases and official payment channels

Products using IAP models may offer subscriptions, premium unlocks, consumables, or lifetime access packages. For digital features and content distributed inside a mobile app, payments are handled through the official application marketplace billing mechanisms required by the platform, such as Apple In-App Purchase or Google Play Billing, where those rules apply.

We do not ask users to provide complete payment card information directly to ArcadeForge Studios through the app for such digital purchases. Instead, the transaction is processed by the applicable store operator. We may receive limited information needed to determine whether a purchase succeeded, whether a subscription is active, whether a receipt is valid, whether a refund occurred, or whether a user is entitled to restore access. This limited information is used for entitlement management, support handling, fraud prevention, and accounting controls.

Billing disputes, refund rights, subscription cancellation, and renewal controls may also be subject to the specific policies and interfaces of the platform operator. When users contact us for assistance, we may explain the correct route for managing a subscription or digital purchase based on the store in which the transaction occurred.

9. Analytics, diagnostics, and product improvement

We may use analytics and diagnostics to understand performance, reliability, and product effectiveness. This may include event measurement, crash reports, load times, retention cohorts, feature completion rates, and funnel behavior. Where possible and appropriate, we prefer data use that is proportionate to the product need and limited in scope.

Analytics may be used to answer questions such as:

• Which features are used and which ones produce friction.
• Which screens, levels, or workflows have abnormal abandonment rates.
• Whether an app version introduces crashes or performance regressions on specific device families.
• Whether ad placements or premium prompts are functioning as intended without causing operational issues.

Where a product requires consent for certain analytics or advertising-related tracking, those activities may be reduced, disabled, or modified until the required signal is present.

10. Local processing and data minimization

For certain utility products, ArcadeForge Studios may intentionally favor on-device or local-first processing wherever practical. This design choice exists for several reasons: faster response, lower infrastructure dependency, reduced transfer risk, and stronger privacy posture for tasks involving personal media or device-local content. However, not every feature in every product can operate entirely on-device, and this Policy should not be read as a universal guarantee that no data ever leaves the device. Where remote services are involved, we aim to limit collection to what is needed for the relevant feature, security, or support task.

11. Children, teens, and younger users

Some products may be intended for general audiences, while others may be aimed at older users. We take special care when age status is relevant to ad delivery, consent, purchase flows, or content suitability. If a product is directed to children or a mixed audience, or if platform policy requires teen-sensitive or child-sensitive handling, we may apply stricter rules around data collection, personalized advertising, and cross-service tracking.

Parents or guardians who believe a child has provided personal information beyond what is appropriate may contact us. Where required by law or applicable policy and where we can reasonably identify and verify the request, we will review the matter and take steps consistent with applicable obligations.

12. How information may be shared

We do not sell personal information in the ordinary sense of transferring user data to unrelated parties for unrestricted independent use. We may share information in the following categories of circumstances:

• With service providers that support hosting, analytics, crash reporting, customer support, security, anti-fraud, advertising, or attribution.
• With platform operators such as Apple or Google as part of normal marketplace operation, billing, receipt validation, or compliance processes.
• With legal authorities or other parties where disclosure is required by law, court order, valid legal process, or necessary to protect rights, property, safety, or service integrity.
• In connection with a merger, restructuring, financing, acquisition, or similar business transaction, subject to appropriate confidentiality and lawful handling expectations.

Where service providers act on our behalf, we aim to use them in ways that are proportionate to the service need and consistent with the product’s declared privacy behavior.

13. Data retention

We retain information for as long as reasonably necessary to fulfill the purpose for which it was collected, support legitimate business records, resolve disputes, prevent abuse, meet legal obligations, or maintain reliable service operation. Retention periods vary depending on the data type:

• Support communications may be retained to track issue history, improve resolution quality, and document operational decisions.
• Purchase and entitlement records may be retained for restoration, anti-fraud review, audit support, and accounting obligations.
• Diagnostics and analytics may be kept in raw or aggregated form for shorter or longer periods depending on operational need, vendor configuration, and legal requirements.
• Advertising event data may be retained according to the requirements of fraud prevention, reporting, settlement, or compliance review.

When information is no longer reasonably needed, we aim to delete, anonymize, aggregate, or otherwise de-identify it where feasible.

14. Security

We use reasonable technical and organizational measures intended to protect information against unauthorized access, misuse, accidental loss, or improper disclosure. No method of transmission or storage is perfectly secure, and we do not guarantee absolute security. Our approach is to limit exposure, reduce unnecessary collection, and use providers and workflows that support secure operation at a practical level.

15. International use and transfers

Our website, apps, vendors, and platform relationships may involve data processing in more than one country. If information is transferred across borders, we aim to use service relationships, contractual arrangements, and practical controls that support lawful handling in the relevant context. Because our products may be distributed worldwide, local rights and regulatory expectations can vary.

16. Your choices and privacy rights

Depending on your location and the nature of the service, you may have rights or choices regarding access, correction, deletion, objection, restriction, portability, consent withdrawal, or appeal. Those rights are not identical in every region, and they may be subject to lawful limitations, identity verification, billing record retention, security needs, or technical feasibility.

You may also have practical controls through your device or platform, including:

• App-level permission controls managed through iOS, iPadOS, or Android settings.
• Advertising or tracking controls made available by Apple, Google, or other platform operators.
• Subscription cancellation, purchase history, and billing management tools made available in the official app marketplace account environment.

To exercise a privacy-related request, contact support@ourappsx.com with enough information for us to understand the scope of the request. If the request concerns a store-managed purchase or platform-level identifier, we may direct you to the platform workflow that controls that specific element.

17. Website cookies and similar technologies

Our website may use basic cookies, local storage, or similar technologies for security, functionality, analytics, or preference preservation. Cookie usage on the website may differ from data use within mobile apps. When legally required, consent or preference management may be implemented for website technologies that go beyond essential operation.

18. Links to third-party services

Our website and apps may link to third-party services, social channels, support forms, app marketplaces, privacy dashboards, or commercial resources. We are not responsible for the privacy practices of third parties outside our control. Users should review the privacy policies of those services before providing information or relying on them for transaction handling.

19. Changes to this Privacy Policy

We may update this Policy to reflect product evolution, legal changes, platform policy changes, operational improvements, or revised SDK and billing behavior. When a change is material, we may update the effective date, publish a revised version on this website, and where appropriate provide notice through the app, store listing, or another suitable channel.

20. Final notes on billing, ads, and user expectations

ArcadeForge Studios operates products across both IAA and IAP models. That means some products depend on advertising to remain free or broadly accessible, while others depend on subscriptions or premium unlocks to deliver sustainable value. Our privacy approach is therefore designed to make clear distinctions between support data, diagnostics, product improvement data, ad-related data, and official marketplace billing data. We aim to keep those categories understandable rather than hidden behind generic statements.

If you have questions about how a particular product handles privacy, ads, age restrictions, or in-app purchases, contact us and identify the specific product and platform. That is the fastest route to an accurate and useful answer.