TRUTH OR DARE +18 — PRIVACY POLICY
Effective date: August 6, 2026
Truth or Dare +18, also known as AOV18, is published by G3F Digital (“we”, “us” or “our”).
Application: Truth or Dare +18
Android package: com.g3fdigital.daretruth18
Privacy contact: truthordare18.app@gmail.com
1. SCOPE AND FEATURE AVAILABILITY
This Privacy Policy explains how the Truth or Dare +18 mobile application and its related support and safety channels handle information.
Not every feature described below is available in every application version, country or distribution channel.
Sections concerning one-time purchases, premium content packs, location groups or future online custom-content sharing apply only when the relevant feature is actually available and used.
This Policy is designed to cover the planned V4 features currently described by G3F Digital. It must nevertheless be revised if the final implementation differs materially, if a new provider or data-processing feature is introduced, or if applicable law requires a change.
2. ADULTS-ONLY APPLICATION
Truth or Dare +18 is intended exclusively for adults aged 18 or older.
It is not directed to children, and minors must not use the application or participate in an online room.
If we learn that identifiable information relating to a minor has been received through our systems, we will take reasonable steps to delete it where technically possible and act as required by applicable law.
3. NO NAMED AOV18 ACCOUNT
The application can be used without creating a named AOV18 account.
Online mode uses a technical anonymous Firebase identifier. Users do not provide an AOV18 email address, password, public profile or social-media account.
The anonymous Firebase identifier is used to secure and operate private online rooms. It is not presented as a user account that can be accessed through a profile page.
4. INFORMATION STORED LOCALLY
Depending on the features used, the application may store the following information on the device:
- language, appearance, music, sound, vibration and interface preferences;
- player names or nicknames;
- declared gender and group selections;
- game configuration, state and history;
- custom questions and custom events;
- content-pack and event-pack selections;
- locally hidden peer or device identifiers;
- sanitized diagnostic events and technical error information;
- information indicating whether an invitation link has already been processed;
- consent-screen state for the current application session;
- locally cached purchase entitlements and billing states, if V4 purchasing features are available.
Information used exclusively in local mode is not transmitted to Firebase.
Custom questions and events remain local by default. They are not uploaded as a complete catalog.
A user may voluntarily export custom content through the Android sharing interface. The exported file is transferred only to the application or recipient selected by the user. G3F Digital does not receive that file unless the user deliberately sends it to G3F Digital.
Depending on the installed version and Android configuration, custom questions may have been included in an Android system backup or device-to-device transfer. G3F Digital cannot directly access these Android backups. Version 3.1.2 and later are intended to exclude AOV18 application data from Android cloud backup and automatic device transfer. Previously created backups remain subject to Google’s or the device manufacturer’s retention and deletion rules.
Local information normally remains until it is deleted through the application, the application data is cleared through Android settings, or the application is uninstalled.
5. ONLINE ROOMS AND FIREBASE
When online mode is selected, the application uses Firebase Authentication, Firebase Realtime Database, Firebase App Check and Google Play Integrity.
Firebase creates an anonymous user identifier. Firebase and related Google services may also process technical information such as:
- IP addresses;
- user-agent strings;
- device and operating-system metadata;
- the Firebase application identifier;
- a Firebase installation identifier;
- application and SDK versions;
- Play Integrity requests, attestation information and tokens;
- application licensing and integrity status.
Information processed for an online room may include:
- the private room code;
- anonymous Firebase and installation identifiers;
- player names or nicknames;
- declared gender and group;
- device label;
- host or guest role;
- presence, readiness and admission status;
- application and online-protocol versions;
- creation, activity, connection, presence and expiration timestamps;
- room status and lock state;
- WebRTC signaling information, including SDP, ICE candidates and network addresses;
- the current game state and revealed-turn information required to synchronize participants;
- a short-lived capacity lease containing an anonymous identifier and expiration timestamp.
Google Play Install Referrer may be read when the application is installed or opened from a Google Play invitation link. It is used only to recover the invited room code and is not used for advertising.
6. PHYSICAL GAME CONTEXT IN V4
A future V4 release may let the host identify which invited devices represent players who are physically together.
For this purpose, the application may use an ephemeral “location group” identifier.
A location group is not GPS data, a street address, precise location or approximate geographic tracking. It indicates only that selected players are considered physically able to interact during the current game.
7. PEER-TO-PEER AUDIO, VIDEO AND GAME COMMUNICATION
Live audio, video and synchronized game communication use encrypted WebRTC connections between admitted devices.
Google STUN services may receive network-address information required to establish the connection. Other admitted participants’ devices may also receive connection metadata required by WebRTC.
AOV18 and G3F Digital do not record or centrally store live audio or video.
The current revealed game information may be transmitted directly between room participants. Other participants can see information intentionally used in the room, including names or nicknames, device labels, presence, game roles and current revealed content.
The full question catalog, the full custom-content catalog, purchase tokens, receipts and the complete list of owned packs are not uploaded to Firebase or transmitted to room participants under the planned V4 design.
If a future compliant version permits an individual custom card to be displayed to invited online participants, only the currently used content and required game state may be transmitted. The full local custom catalog will remain on the host device unless a separate, clearly disclosed synchronization feature is introduced.
8. GOOGLE PLAY SERVICES AND APPLICATION UPDATES
The application uses Google Play services for distribution, integrity checks, licensing, invitation handling and application updates.
The in-app update mechanism may process device metadata, application version information and information about installed application modules or asset packs to determine whether an update is available.
Google Play processes this information according to Google’s terms and privacy policy.
9. SPOTIFY
Some builds distributed before version 3.1.2 may include an optional Spotify embedded player that loads only after the user selects Spotify.
Loading an embedded Spotify player may allow Spotify to process information such as:
- IP address;
- browser, WebView and device characteristics;
- language and regional information;
- cookies or similar technologies;
- interactions with the Spotify player;
- approximate location inferred by Spotify from an IP address.
Spotify may also cause third-party cookies or similar technologies to be used as described in its terms.
G3F Digital does not receive a user’s Spotify password or payment information.
Version 3.1.2 and later are intended to open Spotify only in the external Spotify application or the system browser following an explicit user action. Activity occurring in the external Spotify service is controlled by Spotify and is not part of the AOV18 mobile application.
Spotify Privacy Policy:
https://www.spotify.com/legal/privacy-policy/
10. SAFETY REPORTS, DIAGNOSTICS AND SUPPORT
The application can prepare a safety report or diagnostic file for the user to send voluntarily by email.
A safety report may contain:
- application version;
- support code;
- timestamp and language;
- full room code;
- anonymous reporter and reported identifiers;
- the reported device label;
- a report category or reason.
A diagnostic report may contain:
- application and online-protocol versions;
- platform and build information;
- language;
- sanitized application state;
- redacted room information;
- recent errors;
- a limited number of sanitized technical events.
The diagnostic system is designed not to include player names, custom-question text, the full room code or the Firebase user identifier unless specifically stated for a safety report.
The application opens a draft in the user’s selected email application. No report is transmitted unless the user chooses to send it.
If the email is sent, G3F Digital and the relevant email providers receive the sender’s email address, email subject and content, and any attached report file.
Temporary report files are subject to best-effort cleanup. The application attempts to remove them when the reporting feature is used again, before another report is created, when application data is reset, or after they become obsolete.
Immediate deletion at an exact time cannot be guaranteed if the application is not reopened or cleanup fails.
11. PLANNED V4 PURCHASES AND CONTENT PACKS
If the planned V4 purchasing features are released, the application may offer optional one-time, non-consumable content-pack purchases through Google Play Billing.
No subscription is planned.
For these features, Google Play and the application may process:
- Google Play product identifiers;
- localized product descriptions, prices and offers;
- purchase and entitlement status;
- pending, purchased, acknowledged, restored, refunded or revoked states;
- purchase timestamps;
- normalized billing error and availability information;
- purchase tokens, signed purchase data or order references where technically required to verify, restore or acknowledge a purchase.
Payment-card details, bank-account information and the user’s Google account password are processed by Google Play. G3F Digital does not receive those payment credentials through the planned implementation.
Purchase and entitlement information may be stored in private local application storage and reconciled with Google Play.
Purchase tokens, receipts and order identifiers are not intended to be written to Firebase, exposed in the web interface, sent to other room participants or included in diagnostic reports.
Under the planned V4 design, G3F Digital will not operate a separate purchase-validation server. Purchase verification and restoration will therefore rely on the local application and Google Play Billing.
Google Play may retain transaction records according to its own legal obligations and privacy policy.
12. PURPOSES OF PROCESSING
Information is processed only as reasonably necessary to:
- provide local and online game functionality;
- establish, secure and synchronize private online rooms;
- admit participants and maintain room presence;
- establish peer-to-peer connections;
- maintain application integrity, licensing and service capacity;
- prevent abuse, fraud and unauthorized access;
- provide and enforce application updates;
- diagnose technical problems;
- respond to voluntary support, privacy and safety requests;
- verify, acknowledge and restore purchases when V4 purchasing is available;
- comply with legal obligations;
- protect users, G3F Digital and the service.
Where applicable, processing is based on providing a user-requested service, the user’s consent or deliberate action, G3F Digital’s legitimate interests in operating and protecting the application, or compliance with legal obligations.
13. ADVERTISING, ANALYTICS AND SALE OF DATA
G3F Digital does not sell personal information.
The AOV18 mobile application does not use personal information for targeted advertising and is intended not to contain an advertising SDK.
The application does not currently include Google Analytics for Firebase or Firebase Crashlytics.
Firebase, Google Play and other technical providers may generate operational, integrity, security or service-usage metrics as described in their own documentation.
Third-party services opened outside the application, or an embedded Spotify player present in an older build, may have their own advertising, cookie or analytics practices.
14. SERVICE PROVIDERS AND RECIPIENTS
Information may be processed by or disclosed to:
- Google Firebase, for anonymous authentication, online-room data and application integrity;
- Google Play and Play Integrity, for distribution, licensing, updates and security;
- Google Play Billing, if V4 purchase features are released;
- Google STUN services and admitted peer devices, for WebRTC connection establishment;
- Spotify, only when an older embedded player is loaded or the user opens Spotify externally;
- the user’s and G3F Digital’s email providers, when the user sends a report or support email;
- invited room participants, for information required by the online game;
- public authorities or other recipients when required by law or reasonably necessary to protect users or legal rights.
Information sent to service providers may be processed in countries where those providers operate.
Google Privacy Policy:
https://policies.google.com/privacy
Firebase Privacy and Security:
https://firebase.google.com/support/privacy
15. RETENTION
Online rooms are designed to remain accessible for no more than two hours.
Firebase security rules are intended to reject access after a room expires. The application also attempts to delete a room when the host exits normally or when expiration is detected.
Deletion of the underlying database record at exactly the two-hour limit cannot be guaranteed. If a host device is offline, the application is terminated or cleanup fails, an expired and inaccessible record may remain until later technical or administrative cleanup.
Capacity leases are intended to expire after approximately five minutes unless renewed. A stale record may remain until it is reclaimed or cleaned up.
Anonymous Firebase identifiers and Google technical logs may be retained according to operational, security and legal requirements.
Support emails, safety reports and attachments may be retained for as long as reasonably necessary to answer the request, investigate abuse, comply with legal obligations and protect the service.
Local purchase entitlements remain until application data is cleared or uninstallation occurs, and may be restored or reconciled again through Google Play.
Google Play retains purchase records under its own policies and legal obligations.
16. SECURITY
Data transmitted between the application and Firebase or Google Play is protected using transport encryption.
WebRTC audio, video and game communication is encrypted in transit.
The application uses Firebase security rules, anonymous authentication, Firebase App Check and Play Integrity to reduce unauthorized access and abuse.
Local information is protected by Android’s application sandbox, but not every local value is necessarily separately encrypted by AOV18.
No storage or transmission method can be guaranteed to be completely secure.
Users should share room codes only with trusted adults and avoid including unnecessary sensitive information in nicknames, custom content, reports or support emails.
17. USER CHOICES, RIGHTS AND DELETION REQUESTS
Users can avoid Firebase room processing by using only local mode.
Camera and microphone access can be refused or revoked through Android settings. Audio and video functionality will then be unavailable.
Users can delete local information through available application controls, by clearing the application’s data in Android settings, or by uninstalling the application.
Privacy, access, correction or deletion requests concerning identifiable information held by G3F Digital or Firebase may be sent to:
truthordare18.app@gmail.com
Because the application does not use named AOV18 accounts, we may be unable to locate online information without sufficient technical details.
We may request the anonymous Firebase identifier, the full room code, an approximate date and time, or an existing report attachment. A support code alone does not identify a Firebase user.
Requests concerning a Google Play or Spotify account must normally be directed to the relevant provider.
Subject to applicable law, users may request access, correction, deletion, restriction or portability of identifiable information, or object to certain processing. Users may also contact their competent data-protection authority.
18. PUBLIC POLICY AND SAFETY WEB PAGES
This Privacy Policy and the Child Safety Standards may be hosted by third-party website providers.
The current Flycricket privacy-policy page is separate from the AOV18 mobile application. Flycricket may use cookies, analytics, advertising, sponsored links, impression logging or click logging on the hosted web page.
A child-safety page hosted through app-ads-host.com may also generate ordinary web-server access logs.
These website-hosting practices do not mean that the AOV18 mobile application contains an advertising SDK.
Flycricket Privacy Policy:
https://www.flycricket.com/privacy.html
Flycricket Cookie Policy:
https://flycricket.com/cookie_policy.html
19. CHANGES TO THIS POLICY
We may revise this Policy if the application, its service providers, legal requirements or data-handling practices change.
A V4 release matching the conditional features already described above should not require a complete rewrite. A material difference in implementation may still require an amendment.
The effective date at the beginning of the Policy will identify the latest published version.
20. CONTACT
Privacy questions and requests may be sent to:
G3F Digital
truthordare18.app@gmail.comTRUTH OR DARE +18 — PRIVACY POLICY
Effective date: August 6, 2026
Truth or Dare +18, also known as AOV18, is published by G3F Digital (“we”, “us” or “our”).
Application: Truth or Dare +18
Android package: com.g3fdigital.daretruth18
Privacy contact: truthordare18.app@gmail.com
1. SCOPE AND FEATURE AVAILABILITY
This Privacy Policy explains how the Truth or Dare +18 mobile application and its related support and safety channels handle information.
Not every feature described below is available in every application version, country or distribution channel.
Sections concerning one-time purchases, premium content packs, location groups or future online custom-content sharing apply only when the relevant feature is actually available and used.
This Policy is designed to cover the planned V4 features currently described by G3F Digital. It must nevertheless be revised if the final implementation differs materially, if a new provider or data-processing feature is introduced, or if applicable law requires a change.
2. ADULTS-ONLY APPLICATION
Truth or Dare +18 is intended exclusively for adults aged 18 or older.
It is not directed to children, and minors must not use the application or participate in an online room.
If we learn that identifiable information relating to a minor has been received through our systems, we will take reasonable steps to delete it where technically possible and act as required by applicable law.
3. NO NAMED AOV18 ACCOUNT
The application can be used without creating a named AOV18 account.
Online mode uses a technical anonymous Firebase identifier. Users do not provide an AOV18 email address, password, public profile or social-media account.
The anonymous Firebase identifier is used to secure and operate private online rooms. It is not presented as a user account that can be accessed through a profile page.
4. INFORMATION STORED LOCALLY
Depending on the features used, the application may store the following information on the device:
- language, appearance, music, sound, vibration and interface preferences;
- player names or nicknames;
- declared gender and group selections;
- game configuration, state and history;
- custom questions and custom events;
- content-pack and event-pack selections;
- locally hidden peer or device identifiers;
- sanitized diagnostic events and technical error information;
- information indicating whether an invitation link has already been processed;
- consent-screen state for the current application session;
- locally cached purchase entitlements and billing states, if V4 purchasing features are available.
Information used exclusively in local mode is not transmitted to Firebase.
Custom questions and events remain local by default. They are not uploaded as a complete catalog.
A user may voluntarily export custom content through the Android sharing interface. The exported file is transferred only to the application or recipient selected by the user. G3F Digital does not receive that file unless the user deliberately sends it to G3F Digital.
Depending on the installed version and Android configuration, custom questions may have been included in an Android system backup or device-to-device transfer. G3F Digital cannot directly access these Android backups. Version 3.1.2 and later are intended to exclude AOV18 application data from Android cloud backup and automatic device transfer. Previously created backups remain subject to Google’s or the device manufacturer’s retention and deletion rules.
Local information normally remains until it is deleted through the application, the application data is cleared through Android settings, or the application is uninstalled.
5. ONLINE ROOMS AND FIREBASE
When online mode is selected, the application uses Firebase Authentication, Firebase Realtime Database, Firebase App Check and Google Play Integrity.
Firebase creates an anonymous user identifier. Firebase and related Google services may also process technical information such as:
- IP addresses;
- user-agent strings;
- device and operating-system metadata;
- the Firebase application identifier;
- a Firebase installation identifier;
- application and SDK versions;
- Play Integrity requests, attestation information and tokens;
- application licensing and integrity status.
Information processed for an online room may include:
- the private room code;
- anonymous Firebase and installation identifiers;
- player names or nicknames;
- declared gender and group;
- device label;
- host or guest role;
- presence, readiness and admission status;
- application and online-protocol versions;
- creation, activity, connection, presence and expiration timestamps;
- room status and lock state;
- WebRTC signaling information, including SDP, ICE candidates and network addresses;
- the current game state and revealed-turn information required to synchronize participants;
- a short-lived capacity lease containing an anonymous identifier and expiration timestamp.
Google Play Install Referrer may be read when the application is installed or opened from a Google Play invitation link. It is used only to recover the invited room code and is not used for advertising.
6. PHYSICAL GAME CONTEXT IN V4
A future V4 release may let the host identify which invited devices represent players who are physically together.
For this purpose, the application may use an ephemeral “location group” identifier.
A location group is not GPS data, a street address, precise location or approximate geographic tracking. It indicates only that selected players are considered physically able to interact during the current game.
7. PEER-TO-PEER AUDIO, VIDEO AND GAME COMMUNICATION
Live audio, video and synchronized game communication use encrypted WebRTC connections between admitted devices.
Google STUN services may receive network-address information required to establish the connection. Other admitted participants’ devices may also receive connection metadata required by WebRTC.
AOV18 and G3F Digital do not record or centrally store live audio or video.
The current revealed game information may be transmitted directly between room participants. Other participants can see information intentionally used in the room, including names or nicknames, device labels, presence, game roles and current revealed content.
The full question catalog, the full custom-content catalog, purchase tokens, receipts and the complete list of owned packs are not uploaded to Firebase or transmitted to room participants under the planned V4 design.
If a future compliant version permits an individual custom card to be displayed to invited online participants, only the currently used content and required game state may be transmitted. The full local custom catalog will remain on the host device unless a separate, clearly disclosed synchronization feature is introduced.
8. GOOGLE PLAY SERVICES AND APPLICATION UPDATES
The application uses Google Play services for distribution, integrity checks, licensing, invitation handling and application updates.
The in-app update mechanism may process device metadata, application version information and information about installed application modules or asset packs to determine whether an update is available.
Google Play processes this information according to Google’s terms and privacy policy.
9. SPOTIFY
Some builds distributed before version 3.1.2 may include an optional Spotify embedded player that loads only after the user selects Spotify.
Loading an embedded Spotify player may allow Spotify to process information such as:
- IP address;
- browser, WebView and device characteristics;
- language and regional information;
- cookies or similar technologies;
- interactions with the Spotify player;
- approximate location inferred by Spotify from an IP address.
Spotify may also cause third-party cookies or similar technologies to be used as described in its terms.
G3F Digital does not receive a user’s Spotify password or payment information.
Version 3.1.2 and later are intended to open Spotify only in the external Spotify application or the system browser following an explicit user action. Activity occurring in the external Spotify service is controlled by Spotify and is not part of the AOV18 mobile application.
Spotify Privacy Policy:
https://www.spotify.com/legal/privacy-policy/
10. SAFETY REPORTS, DIAGNOSTICS AND SUPPORT
The application can prepare a safety report or diagnostic file for the user to send voluntarily by email.
A safety report may contain:
- application version;
- support code;
- timestamp and language;
- full room code;
- anonymous reporter and reported identifiers;
- the reported device label;
- a report category or reason.
A diagnostic report may contain:
- application and online-protocol versions;
- platform and build information;
- language;
- sanitized application state;
- redacted room information;
- recent errors;
- a limited number of sanitized technical events.
The diagnostic system is designed not to include player names, custom-question text, the full room code or the Firebase user identifier unless specifically stated for a safety report.
The application opens a draft in the user’s selected email application. No report is transmitted unless the user chooses to send it.
If the email is sent, G3F Digital and the relevant email providers receive the sender’s email address, email subject and content, and any attached report file.
Temporary report files are subject to best-effort cleanup. The application attempts to remove them when the reporting feature is used again, before another report is created, when application data is reset, or after they become obsolete.
Immediate deletion at an exact time cannot be guaranteed if the application is not reopened or cleanup fails.
11. PLANNED V4 PURCHASES AND CONTENT PACKS
If the planned V4 purchasing features are released, the application may offer optional one-time, non-consumable content-pack purchases through Google Play Billing.
No subscription is planned.
For these features, Google Play and the application may process:
- Google Play product identifiers;
- localized product descriptions, prices and offers;
- purchase and entitlement status;
- pending, purchased, acknowledged, restored, refunded or revoked states;
- purchase timestamps;
- normalized billing error and availability information;
- purchase tokens, signed purchase data or order references where technically required to verify, restore or acknowledge a purchase.
Payment-card details, bank-account information and the user’s Google account password are processed by Google Play. G3F Digital does not receive those payment credentials through the planned implementation.
Purchase and entitlement information may be stored in private local application storage and reconciled with Google Play.
Purchase tokens, receipts and order identifiers are not intended to be written to Firebase, exposed in the web interface, sent to other room participants or included in diagnostic reports.
Under the planned V4 design, G3F Digital will not operate a separate purchase-validation server. Purchase verification and restoration will therefore rely on the local application and Google Play Billing.
Google Play may retain transaction records according to its own legal obligations and privacy policy.
12. PURPOSES OF PROCESSING
Information is processed only as reasonably necessary to:
- provide local and online game functionality;
- establish, secure and synchronize private online rooms;
- admit participants and maintain room presence;
- establish peer-to-peer connections;
- maintain application integrity, licensing and service capacity;
- prevent abuse, fraud and unauthorized access;
- provide and enforce application updates;
- diagnose technical problems;
- respond to voluntary support, privacy and safety requests;
- verify, acknowledge and restore purchases when V4 purchasing is available;
- comply with legal obligations;
- protect users, G3F Digital and the service.
Where applicable, processing is based on providing a user-requested service, the user’s consent or deliberate action, G3F Digital’s legitimate interests in operating and protecting the application, or compliance with legal obligations.
13. ADVERTISING, ANALYTICS AND SALE OF DATA
G3F Digital does not sell personal information.
The AOV18 mobile application does not use personal information for targeted advertising and is intended not to contain an advertising SDK.
The application does not currently include Google Analytics for Firebase or Firebase Crashlytics.
Firebase, Google Play and other technical providers may generate operational, integrity, security or service-usage metrics as described in their own documentation.
Third-party services opened outside the application, or an embedded Spotify player present in an older build, may have their own advertising, cookie or analytics practices.
14. SERVICE PROVIDERS AND RECIPIENTS
Information may be processed by or disclosed to:
- Google Firebase, for anonymous authentication, online-room data and application integrity;
- Google Play and Play Integrity, for distribution, licensing, updates and security;
- Google Play Billing, if V4 purchase features are released;
- Google STUN services and admitted peer devices, for WebRTC connection establishment;
- Spotify, only when an older embedded player is loaded or the user opens Spotify externally;
- the user’s and G3F Digital’s email providers, when the user sends a report or support email;
- invited room participants, for information required by the online game;
- public authorities or other recipients when required by law or reasonably necessary to protect users or legal rights.
Information sent to service providers may be processed in countries where those providers operate.
Google Privacy Policy:
https://policies.google.com/privacy
Firebase Privacy and Security:
https://firebase.google.com/support/privacy
15. RETENTION
Online rooms are designed to remain accessible for no more than two hours.
Firebase security rules are intended to reject access after a room expires. The application also attempts to delete a room when the host exits normally or when expiration is detected.
Deletion of the underlying database record at exactly the two-hour limit cannot be guaranteed. If a host device is offline, the application is terminated or cleanup fails, an expired and inaccessible record may remain until later technical or administrative cleanup.
Capacity leases are intended to expire after approximately five minutes unless renewed. A stale record may remain until it is reclaimed or cleaned up.
Anonymous Firebase identifiers and Google technical logs may be retained according to operational, security and legal requirements.
Support emails, safety reports and attachments may be retained for as long as reasonably necessary to answer the request, investigate abuse, comply with legal obligations and protect the service.
Local purchase entitlements remain until application data is cleared or uninstallation occurs, and may be restored or reconciled again through Google Play.
Google Play retains purchase records under its own policies and legal obligations.
16. SECURITY
Data transmitted between the application and Firebase or Google Play is protected using transport encryption.
WebRTC audio, video and game communication is encrypted in transit.
The application uses Firebase security rules, anonymous authentication, Firebase App Check and Play Integrity to reduce unauthorized access and abuse.
Local information is protected by Android’s application sandbox, but not every local value is necessarily separately encrypted by AOV18.
No storage or transmission method can be guaranteed to be completely secure.
Users should share room codes only with trusted adults and avoid including unnecessary sensitive information in nicknames, custom content, reports or support emails.
17. USER CHOICES, RIGHTS AND DELETION REQUESTS
Users can avoid Firebase room processing by using only local mode.
Camera and microphone access can be refused or revoked through Android settings. Audio and video functionality will then be unavailable.
Users can delete local information through available application controls, by clearing the application’s data in Android settings, or by uninstalling the application.
Privacy, access, correction or deletion requests concerning identifiable information held by G3F Digital or Firebase may be sent to:
truthordare18.app@gmail.com
Because the application does not use named AOV18 accounts, we may be unable to locate online information without sufficient technical details.
We may request the anonymous Firebase identifier, the full room code, an approximate date and time, or an existing report attachment. A support code alone does not identify a Firebase user.
Requests concerning a Google Play or Spotify account must normally be directed to the relevant provider.
Subject to applicable law, users may request access, correction, deletion, restriction or portability of identifiable information, or object to certain processing. Users may also contact their competent data-protection authority.
18. PUBLIC POLICY AND SAFETY WEB PAGES
This Privacy Policy and the Child Safety Standards may be hosted by third-party website providers.
The current Flycricket privacy-policy page is separate from the AOV18 mobile application. Flycricket may use cookies, analytics, advertising, sponsored links, impression logging or click logging on the hosted web page.
A child-safety page hosted through app-ads-host.com may also generate ordinary web-server access logs.
These website-hosting practices do not mean that the AOV18 mobile application contains an advertising SDK.
Flycricket Privacy Policy:
https://www.flycricket.com/privacy.html
Flycricket Cookie Policy:
https://flycricket.com/cookie_policy.html
19. CHANGES TO THIS POLICY
We may revise this Policy if the application, its service providers, legal requirements or data-handling practices change.
A V4 release matching the conditional features already described above should not require a complete rewrite. A material difference in implementation may still require an amendment.
The effective date at the beginning of the Policy will identify the latest published version.
20. CONTACT
Privacy questions and requests may be sent to:
G3F Digital
truthordare18.app@gmail.com