Overview
This policy explains how TECCOD, LLC ("we") handles information when you use the DreamSpend mobile app (the "App"). It covers the published version of DreamSpend 1.0 (build 17) and DreamSpend 1.0 test build 18 and subsequent builds that include the Unity Ads SDK.
Questions about privacy can be sent to apps@teccod.com.
1What the App does
DreamSpend is a game in which you record imaginary purchases and track game progress. The App is not intended for making real payments.
2Data you enter into the App
Records of imaginary purchases, their categories and amounts, game progress, achievements and settings are stored on your device.
You do not need to create a DreamSpend account to use the main features of the App. On the basis of the current implementation, we do not receive your purchase records or your game progress on TECCOD servers.
Your main game records stay on your device, and most of the App works without an internet connection. Two features do require a connection: loading a test advertisement (see section 5) and manually requesting a currency rate update (see section 3).
Data may be included in device backups depending on your device settings and on the Apple services you use.
3Currency rates
If you manually request a currency rate update in the settings, the App contacts the external Frankfurter service (https://www.frankfurter.app/). The request contains the currency codes for which rates are requested.
When an external service is contacted, the technical details required to establish the connection, including an IP address, may be available to the service provider and to other parties involved in the transfer of data, in accordance with their rules. Your imaginary purchase records are not included in the rate request.
4Reminders
If you enable reminders and allow notifications in iOS settings, the App creates local notifications on your device. You can turn them off in the App settings or in your device settings.
5Advertising and analytics
Published version 1.0 (build 17)
The version of DreamSpend currently published on the App Store, 1.0 (build 17), does not include an advertising SDK, and no third-party advertising analytics tools are connected in it.
DreamSpend 1.0 test build 18 and subsequent builds that include the Unity Ads SDK
DreamSpend 1.0 test build 18 and subsequent builds that include the Unity Ads SDK connect the Unity Ads SDK, so that the team can check how test advertisements are displayed and how they behave inside the App.
Those builds are not a launch of advertising monetisation. They exist to verify test advertisements, and the published version 1.0 (build 17) stays without an advertising SDK.
The set of SDKs included in a build may change over time, so this section describes only the SDK that the builds named above contain.
How the SDK is started
The Unity Ads SDK does not start on its own. It runs only after you choose to load a test advertisement in the App and confirm the warning shown on screen. If you do not confirm, no advertisement is requested.
Test mode is switched on programmatically inside the App, so that the Unity Ads SDK serves test advertisements rather than live ones.
Settings the App passes to the SDK
Before the SDK is started, the App passes it the following refusal-of-personalisation and data-collection settings: setUserConsent(false), setUserOptOut(true) and setNonBehavioral(true). In practice this means that the App does not give consent for personalised advertising, that the user is treated as opted out, and that behavioural advertising signals are not passed.
These are requests from the App to the SDK, not a guarantee. They do not confirm that no data at all is transmitted, and they do not replace the terms of the Unity Ads SDK itself.
Technical data the SDK may receive
When you load a test advertisement, Unity Ads connects to the internet and may receive technical device and connection data. This covers the information needed to establish and maintain the connection, the app and device characteristics the SDK requires in order to work, and diagnostic and security information used to operate, troubleshoot and protect the service.
The exact set of data depends on the version of the Unity Ads SDK used in the test build and on how the service is configured. Details such as identifiers, retention periods and transfer locations are not stated here, because they follow the version of the SDK in use and Unity's current terms. You can read them in the Unity privacy policy: https://unity.com/legal/privacy-policy. Please read that policy together with this one.
Your game data
Your main game records are stored locally on your device. The App does not include them in the advertisement request.
6Support requests
If you contact us by email, we receive your email address and whatever information you decide to include in the message. We use it to answer your request and to solve the problem you describe.
Please do not send us passwords, bank card details or other information that is not needed to consider your request.
7Storage and deletion
Game data is stored on your device until you delete it. You can reset your game progress in the App settings or delete the App from your device. Data included in backups is managed separately through the settings of the backup service you use.
To ask a question about your data in a support request, or to request its deletion, write to us at the address above. We will consider the request in line with applicable requirements and with the need to retain information where the law requires it.
8Security
We aim to limit the processing of data to the amount the App needs in order to work. To protect data on your device, we recommend using the protection features available in iOS, including a passcode or biometric lock.
9Changes to this policy
We may update this policy when the features of the App or the way data is handled change. The current version is published on this page together with its effective date, and the previous revision is listed in the revision history below.