Contract effective date: September 18, 2024. Audit release: July 9, 2026. Runtime consent and session timestamps are recorded when users actually interact with NEXQ systems.
App Store and Platform Privacy Policy
Template and counsel-review notice. This document is a website/app integration template, not a legal opinion. Before publication, replace bracketed placeholders, confirm actual data flows, obtain advice from qualified counsel for each jurisdiction and regulated workflow, and approve final wording through privacy, security, product, marketing, health/clinical, and executive stakeholders. Do not promise controls, certifications, response times, retention periods, or legal rights unless they are actually implemented and operationally supported.
Effective date: September 18, 2024
Last updated: September 18, 2024
Organization: NEXQ Inc.
Services covered:
NEXQ websites, web applications, protected workspace surfaces, mobile app surfaces, APIs, secure healthcare and healthtech workflow demonstrations, quantum encryption, diagnostics, oncology, longevity, research collaboration, support, and related services
Privacy contact: hello@nexq.us
Security contact: hello@nexq.us
Mailing address: Irvine, CA, United States — contact hello@nexq.us for legal notices
1. Scope
This policy governs mobile app privacy labels, app-store disclosures, SDK inventories, platform permissions, deletion rights, tracking transparency, privacy manifests, required-reason APIs, health/children/financial disclosures, and mobile release gates.
2. Apple App Store controls
Before submitting an iOS, iPadOS, macOS, watchOS, tvOS, or visionOS app, complete App Privacy Details based on data collected by the app and third-party partners. Maintain Apple privacy manifest files where required and document required-reason API usage. Apps that track users across apps or websites owned by other companies require platform-specific permission and must match the published privacy policy.
3. Google Play controls
Before submitting or updating an Android app, complete the Google Play Data Safety form and ensure the privacy policy, SDK inventory, permissions, data deletion methods, and in-app disclosures match actual behavior. Data deletion options must be operational and reflected in the Data Safety section.
4. SDK and permission inventory
Every mobile SDK and permission must have an owner, purpose, data categories, retention, recipient, geography, consent basis, opt-out method, child/health/financial impact, and app-store disclosure mapping. Remove unused SDKs and permissions.
5. Release-blocking checks
Block releases when app-store disclosures conflict with code, health/children/financial workflows lack review, tracking permission is missing, deletion links are broken, sensitive permissions are not justified, SDK versions are unknown, or privacy manifests are incomplete.