Skip to content
Orion TheoryOrion Theory
  • Games
  • Apps
  • About
  • Journal
  • Contact

Privacy Policy

Last updated
[Insert actual publication date]
Applies to
Orion Theory website and the Orion Theory apps identified below.
Privacy contact
oriontheoryconnect@gmail.com

Contents

  1. 1. Who we are
  2. 2. Scope
  3. 3. Information we collect
  4. 4. How we use information
  5. 5. Sharing and service providers
  6. 6. Advertising and analytics
  7. 7. Data retention
  8. 8. Data security
  9. 9. Children’s privacy
  10. 10. Your choices and rights
  11. 11. International transfers
  12. 12. Third-party links
  13. 13. Changes to this policy
  14. 14. Contact

See also: Terms & Conditions

Draft — pending publisher review

This document is a working draft and is not yet final. Highlighted [bracketed items] are details still being confirmed, and publisher notes describe what each section will cover.

This policy must be tailored to actual practices. Do not publish statements about collection, advertising, analytics, children, deletion, retention, or third-party vendors without verifying them against the app build and SDK configuration. The Play Console Data safety form must match the actual app and this policy.

1. Who we are

Orion Theory (“we,” “us,” or “our”) develops and publishes mobile apps and games. This Privacy Policy explains how information may be handled when you visit oriontheory.store or use an Orion Theory app.

2. Scope

This policy applies to the Orion Theory website and the apps expressly listed here: [list currently released apps; currently none, or add What Flag when released]. A third-party platform such as Google Play may also process information under its own policies.

3. Information we collect

Publisher note

Complete this section only after confirming the actual product behavior. Describe applicable categories, for example:

  • Information a user chooses to send through support or contact forms.
  • App or device information collected by the app or integrated SDKs.
  • Diagnostics, crash reports, analytics, advertising identifiers, or purchase information, if applicable.
  • Information stored locally on the device.
  • Information collected through website logs, cookies, or analytics, if applicable.
Publisher note

If the app does not collect a category, say so only after checking the app and its SDKs. Explain whether data is required or optional.

Publisher note

Website facts to verify with your host before publishing: as built, this website sets no cookies, loads no analytics or advertising scripts, serves its fonts from its own domain, and has no contact form (contact happens by email). Your hosting provider may still keep server logs such as IP addresses and request times — [confirm the hosting provider’s logging and retention].

4. How we use information

Publisher note

Describe the real purposes, which may include operating the app, responding to support requests, maintaining security, diagnosing errors, improving features, complying with legal obligations, or delivering ads—only where applicable.

[Insert verified purposes for each category of information]

5. Sharing and service providers

Publisher note

Identify the actual third-party SDKs and service providers and explain what they receive and why. Include relevant links to their privacy policies. Do not use a generic “we may share with partners” statement as a substitute for naming material providers.

[List actual service providers and SDKs, what they receive, why, and links to their privacy policies]

6. Advertising and analytics

[Include only if used.] Explain the advertising/analytics technologies, identifiers, personalization behavior, and available controls. If the app is child-directed or may include children, carefully verify applicable requirements and SDK suitability.

7. Data retention

Publisher note

Explain how long each category is retained and the criteria used to determine retention. State what happens when a user requests deletion, where deletion is available.

[Insert retention periods and deletion process]

8. Data security

Publisher note

Describe reasonable technical and organizational measures without promising absolute security.

[Describe actual security measures]

9. Children’s privacy

Publisher note

State the actual intended audience and practices. Do not claim the app is “not directed to children” or “safe for all ages” without checking the app’s content, store target audience, advertising SDKs, and applicable rules. Explain how a parent/guardian can contact you about a child’s information if relevant.

[State the verified target audience and children’s privacy practices]

10. Your choices and rights

Publisher note

Explain applicable access, correction, deletion, objection, consent withdrawal, or other rights based on the jurisdictions served and the data actually processed. Provide a working contact route.

[Describe applicable rights and how to exercise them]

11. International transfers

[If information is transferred internationally, explain the relevant destinations and safeguards where required.]

12. Third-party links

The website or app may link to third-party services. Their privacy practices are governed by their own policies.

13. Changes to this policy

We may update this policy as our services or legal obligations change. The updated date will be shown above.

Publisher note

Explain how material changes are communicated if that is part of your actual process.

14. Contact

For privacy questions or requests: oriontheoryconnect@gmail.com

Publisher name/address: [insert accurate legal or business identity details if required]

Questions? Visit Contact or Support.

Have a question or an idea?

We’d like to hear from you.

Contact Orion Theory →
Orion Theory

Good games. Useful apps. A little more wonder.

Explore

  • Games
  • Apps
  • Journal

Studio

  • About
  • Contact
  • Support

Legal

  • Privacy Policy
  • Terms & Conditions
  • Sitemap

© 2026 Orion Theory

Independent publisher of mobile games and apps