1. Scope and contact
This policy applies to the RUNVOK Android game developed by Duvar Mobile and its support services. For privacy questions or requests, contact duvarmobile@gmail.com.
This policy covers RUNVOK and its related services, including Google connections shown as RUNVOK or RUNVOK Destek. The v0.8.9 test build uses local game saves, Google Mobile Ads rewarded test ads, server time, and optional bug reports. Google Play Games sign-in, game-managed cloud saves, and real-money purchases are not active in that build. A separate Play Games authentication service is being prepared and tested; its data handling is described below for anyone who uses it. Gmail report delivery is described for when that connection is enabled. Describing these services does not mean they are already available in every game build.
2. Game data stored on your device
Game progress, your chosen player name and character, profile preferences, race and tournament results, missions, in-game balances, and settings are stored on your device. In the current version, they are not automatically uploaded to a Duvar Mobile account or a game-managed cloud save service. Android system backup may separately back up app data depending on your device and Google Account settings; you can manage this through Android/Google backup settings.
Life, wheel, and mission timers use server time and time elapsed since the device started, rather than the date and time you can manually change on your phone. A hash of the Android identifier and the device boot count are stored locally to distinguish device restarts. These values are not sent with time requests.
3. Server time
When needed at game launch or after a device restart, the game connects to the time service over HTTPS. The request contains a random, temporary value used to match the response to that request. Your player name, progress, and balances are not part of the time request.
As part of providing internet services, hosting and security providers may process your IP address, connection time, and basic request information. The time service does not use this information to build player profiles or target advertising.
4. Optional bug reports and support
If you use “Report a bug,” your description, game version, device model, operating system, client-side player identifier, random installation identifier, and report identifier are sent to the support server. Do not include passwords, payment details, or unnecessary personal information in your description.
We process this information to investigate issues, prevent duplicate submissions, and limit misuse. The server uses keyed hashes of the installation identifier and IP address. Report content is stored in a support record and, when the email service is enabled, is forwarded only to duvarmobile@gmail.com. No screenshot, photo, contact list, or location is automatically attached.
If submission fails, the draft remains on your device and is not shown as successfully sent. If you contact us directly by email, we also process your email address and the information in your message to handle your support request.
5. Google Play Games and support email
Play Games authentication
If you use our Play Games authentication service, Google supplies a temporary authorization code. Our server exchanges it for authorization to verify your Play Games player identity for RUNVOK. We use the verified player identifier to recognize the same player and create a RUNVOK account identifier and a temporary sign-in session.
We store the Google Play Games player identifier, the associated RUNVOK account identifier, the game application identifier, and the account creation time. Session records contain a protected form of the session token and its creation and expiry times. A keyed hash of the connecting IP address is used briefly to limit excessive sign-in attempts. This connection does not request your Google password, email address, contact list, or Gmail inbox. We do not retain the authorization code or Google's access or refresh tokens from this sign-in exchange. This authentication service does not itself upload your game progress or balances.
Gmail for developer support delivery
When enabled, the Gmail connection lets the developer's authorized sending account send submitted RUNVOK bug reports to duvarmobile@gmail.com. Players are not asked to connect their own Gmail accounts. The integration requests permission to send email; it does not read a mailbox or address book. Report emails contain the support information described in section 4. We store the resulting message identifier and delivery status to check delivery and avoid duplicate reports.
Authorization credentials for the sending account are kept on the server and used only to send these support messages. Support staff may read reports and messages you submit to investigate your request. Connecting the sender account does not give the game access to players' email.
Limits on Google data use
Our use of information received through Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Information received through Gmail is also handled according to the Google Workspace API User Data and Developer Policy. We use this information only to provide the authentication and support features described here.
We do not sell Play Games or Gmail data, use it for advertising or credit decisions, or use it to train AI models. Access by people is limited to support you request or authorize, security investigations, or legal obligations. Transfers are limited to the providers needed to operate these features, legal requirements, and service security. The separate advertising SDK processing described below does not receive data from our Play Games or Gmail integration.
6. Service providers and sharing
We do not sell your personal information. We use GitHub Pages for this website, OpenAI Sites and Cloudflare infrastructure for time, authentication, and report services, Google Play Games for player verification when that service is used, Google AdMob for rewarded test ads, and Google Gmail when support email delivery is enabled. These providers may process connection and service data under their own privacy policies, including on servers outside your country.
We may share information with competent authorities when necessary to meet legal obligations or protect the service and its users.
7. Advertising and purchases
RUNVOK contains rewarded advertising provided through Google Mobile Ads (AdMob). Players choose whether to watch a rewarded ad. The v0.8.9 test build uses Google's official rewarded test ad unit; these test ads do not generate advertising revenue. The game does not show banner ads or forced interstitial ads. An ad reward is granted only after the ad network reports completion.
Using test ads does not mean that the advertising SDK processes no data. The SDK initializes when the game starts. According to Google's disclosure, it may automatically collect and share with Google your IP address (which can be used to estimate approximate location), interactions such as app launches, taps, and video views, performance and diagnostic information, and device identifiers such as the advertising ID and app set ID. These data are used for advertising delivery and measurement, analytics, and fraud prevention. Choosing not to watch an ad does not necessarily stop all data processing during SDK initialization. SDK data is encrypted in transit using TLS.
You can reset or delete your advertising ID using Android's advertising privacy settings. This does not stop all technical data processing. For choices and retention practices relating to data processed by Google, see the Google Privacy Policy, My Ad Center, and Google Mobile Ads data disclosure.
Real-money purchases cannot be initiated in the current version. The game does not request card numbers, card security codes, or payment account details. Before enabling real Google Play payments or revenue-generating ads, we will implement the relevant data flows and required consent choices and update this policy.
8. Retention and deletion
You can delete local game data by clearing the app's storage in Android settings. This removes your game progress. Support records and emails that have reached the server are separate from local app data.
Completed server reports have a 90-day cleanup threshold: when a new submission succeeds, completed records older than this threshold are deleted. Deletion may therefore occur after, rather than exactly on, day 90. Reports with uncertain delivery or unresolved issues are kept until their investigation is complete. Support emails are retained for as long as necessary to respond to your request, resolve disputes, or meet legal obligations. Providers' technical logs are subject to their own retention policies.
The Play Games-to-RUNVOK identity record is kept until you request deletion, unless a limited legal or security reason requires retention. RUNVOK sign-in sessions expire after one hour; expired session records are removed during a later successful sign-in. Sign-in rate-limit records expire after two minutes and are cleaned up on a later authentication attempt. Expired records may therefore remain stored until cleanup occurs, but expired sessions cannot authorize access.
The developer's Gmail authorization is retained while support delivery is connected and needed. It is removed when we disconnect that integration. Reports already sent and their delivery records follow the support retention practices above.
9. Your choices and data deletion requests
RUNVOK data deletion request: Email duvarmobile@gmail.com with the subject “RUNVOK data deletion request.” If available, include your report number and identify the support record you want deleted. Do not send passwords or payment details. If you have used the new authentication service, you may also request deletion of your RUNVOK account and its associated data. Include your RUNVOK account identifier if available; never send a sign-in token. After verifying your request, we will delete or de-identify the relevant report text, associated device/installation information, and support correspondence under our control. Account deletion also removes the Play Games-to-RUNVOK identity record and associated sign-in sessions. Records needed for security, disputes, or legal obligations may be retained only as long as necessary for those purposes; we will explain any such exception in our response.
To delete game progress on your device, go to Android Settings → Apps → RUNVOK → Storage → Clear data. To manage Google advertising data, use the Google links above and Android advertising privacy settings. The v0.8.9 game build does not create a server account; records created by separately testing our new authentication service can be deleted through the request above. Clearing local app storage does not delete server records, and deleting a RUNVOK record does not delete your Google Account or data held independently by Google.
You can manage connected services in your Google Account connections and Play Games settings. Revoking Google access does not automatically delete existing RUNVOK server records; use the deletion request above for those records.
Submitting a bug report is optional. Depending on the rules where you live, you may have rights to access, correct, delete, or object to the processing of your information. Send requests to duvarmobile@gmail.com, preferably with the relevant report number. We will request only the additional information necessary to verify your request.
If you are a parent or guardian and believe your child has shared personal information through support, contact us so we can investigate and delete it when appropriate.
10. Security and changes
Time, authentication, and report connections use HTTPS, and Google Mobile Ads data is transferred using TLS. Email authorization credentials are held on the server, not included in the game package. No electronic system can guarantee absolute security.
We will update this policy and its revision date when game features or data processing practices change. Where required, we will also announce significant changes in the app.