1. Developer and scope
This Privacy Policy is published by Vector PeakApp ("we", "us" or "the Developer") and applies to the applications for which Vector PeakApp is identified as the developer or publisher, to the extent that this policy is linked from the relevant app listing or made available within that app. The legal person or entity responsible for a particular app is the person or entity identified in that app's store listing and other applicable legal notices.
This Policy explains categories of information that may be processed, purposes of processing, possible recipients, security, retention and user choices. The exact practices vary by app, platform, region, enabled features, SDK versions and consent configuration. App-specific notices and the relevant store listing must be reviewed together with this Policy.
Privacy contact: For privacy questions or requests, use the active developer support email/contact method displayed on the relevant app's Google Play store listing. Identify the app and describe the request. Do not include passwords, payment-card numbers or unnecessary sensitive information.
2. Categories of information that may be processed
Depending on the particular app and its implementation, the following categories may be processed:
- Device and technical information: device model, manufacturer, operating system and version, language, app version, network type, IP address, crash reports, performance diagnostics and security-related technical events.
- App activity and interaction information: app launches, screens or features used, taps, session events, game or content interactions, advertising impressions, ad clicks or video views, where the relevant analytics or advertising technology is enabled.
- Identifiers: advertising identifiers, app-scoped identifiers, installation identifiers or other device/account identifiers made available to the app or its SDKs, subject to platform rules, user settings and applicable law.
- Advertising and consent information: ad request and delivery data, consent choices, privacy settings, ad measurement and fraud-prevention signals, where advertising is used.
- Information voluntarily submitted to support: email address, message contents, app/version details and any information a user chooses to include when contacting support.
- Feature-specific information: information entered or generated when a specific app offers accounts, cloud synchronization, saved progress, subscriptions, purchases, multiplayer, location-based features, user-generated content or other online functionality. Such information must be described specifically in the app's own disclosures.
- Location information: approximate or precise location only if the particular app or an integrated SDK accesses it and the relevant permission or other lawful basis applies. The app-specific notice must state the actual purpose and whether location is collected or shared.
Not every app processes every category above. The developer must check the actual app build and all integrated third-party SDKs before publication and update this Policy and the Play Console Data safety form whenever practices change.
3. Google Mobile Ads / AdMob
Some Vector PeakApp applications may use Google Mobile Ads SDK and Google AdMob to request, display, measure and protect advertising, where disclosed in the relevant app. Google's published Google Play data-disclosure information for the latest Google Mobile Ads SDK states that the SDK automatically collects and shares IP address, user product interactions, diagnostic information, and device/account identifiers for advertising, analytics and fraud-prevention purposes. The exact data processed may depend on the SDK version, optional features, manifest settings, consent configuration and app implementation.
These categories may include an IP address (which can be used to estimate general location), interactions such as app launches, taps and video views, performance/diagnostic information, and identifiers such as Android Advertising ID or App Set ID where applicable. Google states that data collected by the SDK is encrypted in transit using TLS. Users may have advertising and privacy controls in Android settings and through consent or privacy choices presented in the app, depending on region and implementation.
Google processes information under its own privacy terms and product documentation. For additional details, see Google Mobile Ads SDK data disclosure and Google Privacy Policy. The developer remains responsible for accurately completing the app's Data safety and advertising declarations.
4. Purposes of processing
Where relevant to a particular app, information may be used to: provide and operate app features; save or synchronize user progress; respond to support requests; diagnose crashes and improve stability; protect the app, users and services against fraud, abuse and security incidents; measure app performance; deliver and measure advertising; manage consent and privacy choices; comply with legal obligations; and enforce applicable terms.
Information must not be used for a purpose incompatible with the disclosures made to users or prohibited by applicable platform rules or law. Where consent is legally required, the relevant processing must be based on valid consent and the app must provide the required choice mechanism.
5. Sharing and recipients
Depending on the app's functionality, information may be disclosed to:
- Google and advertising providers: Google LLC and Google Mobile Ads/AdMob, when those services are integrated, for ad delivery, measurement, analytics and fraud prevention.
- Technical service providers: hosting, crash reporting, analytics, customer-support, security, payment or cloud providers actually integrated into the app.
- Other users: only when the app includes social, multiplayer, community or user-content functionality and the user chooses to make information visible.
- Authorities or other parties: where disclosure is required by law, valid legal process, or necessary to protect rights, safety and security.
- Business successors: in connection with a lawful merger, restructuring or transfer of the relevant app or business, subject to applicable privacy requirements.
Only recipients relevant to the particular app should be listed in that app's final privacy disclosures. The developer must not imply that a service provider is used when it is not integrated.
6. Data retention and deletion
Retention depends on the type of information, the purpose for which it was collected, the app's functionality, applicable legal requirements and the policies of third-party providers. Support correspondence may be retained for the time reasonably necessary to investigate and respond to a request, maintain appropriate records, resolve disputes and comply with legal obligations. Information processed directly by third-party services is also subject to those providers' retention policies and controls.
Where an app stores information locally on a device, uninstalling the app may remove locally stored app data, but it may not delete data already held by a third-party service, a cloud account, a backup or another device. Users should use any in-app deletion controls and contact the developer for assistance where applicable.
Where an app allows users to create an account, the developer must provide an easily discoverable in-app path to request account deletion and an external web-based method, and must delete the account and associated user data as required by Google Play policy and applicable law. Any information that must be retained for legal, security or fraud-prevention reasons should be limited, protected and retained only for the legally permitted period, with the reason explained where required. See Account and Data Deletion.
7. Security
The developer aims to use reasonable administrative, technical and organizational safeguards appropriate to the nature of the information and the app's design. No method of transmission or storage is completely secure. Users should keep their devices and operating systems updated, use device security controls and avoid sharing account credentials. Third-party providers are responsible for the security practices of the services they operate, subject to their applicable terms and law.
8. Children's privacy and age-appropriate design
The target audience for each app is declared separately in its store listing and Play Console. This Policy does not determine or change an app's age rating or target audience. If an app targets children or includes children in its target audience, the developer must apply the applicable Google Play Families requirements and relevant child-protection laws, use permitted advertising SDKs and age-appropriate advertising practices, and ensure that content and data practices are suitable for that audience. Parents or guardians may use the developer contact method shown on the relevant store listing for privacy questions.
9. International processing and legal rights
Depending on the app and the services it uses, information may be processed in countries other than the user's country. Where applicable law grants rights to access, correct, delete, restrict or object to processing, or to withdraw consent, users may submit a request using the developer contact method shown on the relevant store listing. The developer may need to verify the request and may retain limited information where required or permitted by law.
10. Third-party services and links
An app may contain links to or integrations with services operated by third parties. Their privacy practices are governed by their own notices and terms. Vector PeakApp does not control independent third-party websites or services and encourages users to review their privacy information before using them.
11. Changes to this Policy
This Policy may be updated to reflect changes in app features, SDKs, legal requirements or platform policies. The current version and revision date will be posted on this page. Where required, material changes will be presented to users in the app or through another legally appropriate method.
12. Contact
For privacy questions, data requests, complaints or account-deletion requests, use the active developer support email/contact method shown on the relevant app's Google Play store listing. Include the app name and enough detail to identify the issue. Do not send your password or full payment credentials.