THE OBLONG STUDIO
Privacy policy
Match Game But With Swords
Draft prepared October 28, 2026 · Not yet effective
The Oblong Studio develops Match Game But With Swords, a mobile puzzle adventure. This draft explains the information associated with the game and the privacy details we must finalize before release.
1. Game identity and progress
The current game uses Unity Authentication to establish a player identity, including anonymous sign-in. Server-side game information is associated with that identity. This can include level and area progress, completed tasks, currencies, inventory and collections, rewards, event participation, and transaction or settlement records used to prevent duplicate rewards or spending.
Players can enter a display name. The game uses names in features such as the profile and rankings; the final visibility of names and ranking information must be confirmed for release. Players should avoid entering sensitive information as their display name.
2. Gameplay analytics and diagnostics
The game has Unity Analytics instrumentation for gameplay activity such as level starts and results, area progression, reward and currency activity, and feature usage. Analytics can help us understand engagement, balance the game and diagnose problems.
Before publication: confirm the analytics and diagnostic services enabled in the release build, the identifiers and technical information they process, and the actual consent, withdrawal and deletion controls. The Development analytics test control is not a released privacy control. This draft does not promise an analytics opt-out that has not been implemented.
3. Advertising and privacy choices
Optional rewarded advertisements are planned for the game. Advertising services may process device or advertising identifiers, IP addresses, ad interactions, and technical or diagnostic information according to their service configuration and the player’s privacy choices.
Before publication: confirm the production ad provider and any partners, their policy links, collected data, and the consent and privacy-options screens available in the released game. Do not assume Wordy Birdie’s consent behavior applies to this game.
4. Purchases and reward records
Shop purchases and special offers are planned. The game will need purchase and entitlement information to validate and deliver purchased content, reconcile interrupted purchases, and prevent duplicate fulfillment.
Before publication: confirm the launch store’s payment processing, exactly which purchase identifiers or receipts our backend retains, and the retention and deletion rules for those records.
5. Local information and support
The game stores preferences and some cached presentation or gameplay information on the device. Server-owned progress and balances are separate from local preferences. Clearing local data does not necessarily delete server-side information.
If you email the studio, we receive your email address and the information you include. Do not send passwords, full payment-card details or account access tokens.
6. Why information is used
Game information supports authentication, saved progress, gameplay features, rewards, purchases, rankings and events; helps prevent duplicate or unauthorized transactions; and supports technical troubleshooting. Confirm the released analytics and advertising purposes when those integrations are finalized.
7. Service providers and sharing
Unity provides authentication and the current analytics integration. Additional backend hosting, database, advertising and store providers must be listed against the final production configuration, including the data each processes and relevant privacy links. This section is incomplete until that review is finished.
Before publication: confirm provider locations and any international processing disclosures. Do not promise a particular processing country or protection that has not been verified.
8. Retention and deletion
Before publication: establish how long player profiles, progress, purchase/reward evidence, analytics and support messages are kept; how a player identifies their account for a request; and which records must be retained and why. Implement and verify the applicable in-game and web deletion request paths. Do not substitute a local reset or a debug reset for deletion.
9. Children and intended audience
Before publication: confirm the intended age groups and actual audience declaration. Wordy Birdie’s “not directed to children under 13” statement has not been adopted for this game.
10. Privacy questions and requests
Contact The Oblong Studio at theoblongstudio@gmail.com with privacy questions. The release policy must explain the verified process for access, correction, deletion and other applicable requests, including how we locate the relevant player record without requesting credentials.
11. Security and policy changes
The final policy must describe verified data-handling safeguards and how policy changes are communicated. No system can guarantee complete security. Replace this draft date with an effective update date only when the policy matches the released game.