APPLICATION TRUST
Application privacy information.
Privacy information for applications published by Kurtz Global IT Solutions Inc., including data practices, rights and support contacts.
This policy is published by Kurtz Global IT Solutions Inc. and describes the commitments and information that apply to the subject below. It should be read alongside any applicable written service agreement or application-specific notice.
Scope
Kurtz Global IT Solutions Inc. provides this central resource for privacy questions about applications published under its developer accounts. Each application needs disclosures tailored to its actual features, permissions, SDKs, data collection, sharing and retention. This page does not claim that all applications collect or avoid collecting the same categories of data.
Information that may be involved
Depending on the particular application, data categories can include account details, app-generated content, purchase-related transaction references, customer support messages, device information and diagnostics. Sensitive permissions such as location, contacts, photos or camera access must be explained by the application that requests them. The actual practices for a particular app must be described in its own published privacy materials and store declarations.
Processing and providers
Data may be used to provide the app's features, maintain accounts, troubleshoot problems, manage purchases, prevent abuse or comply with law. Third-party infrastructure, authentication, payment or analytics providers must be identified when they are used by a particular app. The developer is responsible for matching the app's real behavior to its Apple privacy labels and Google Play Data safety answers.
Data retention, requests and deletion
Any data retention or deletion rule must match the applicable application's actual storage and backup behavior. For questions about an application's data, email [email protected]. To request account deletion, use account deletion. We verify ownership before disclosing or changing personal account data.
Security and contact
Application security is addressed through technical controls appropriate to each product, but no system is risk-free. Report privacy concerns to [email protected], app issues to [email protected] and vulnerabilities to [email protected].
Important store-disclosure distinction
Apple and Google require an application’s privacy description to accurately cover its real data practices. Before a new application is published, its product-specific privacy page, in-app disclosures and app store answers must be reviewed together. A general corporate policy alone is not a substitute for that review.
1. Scope of the application privacy framework
This central resource explains how Kurtz Global IT Solutions Inc. approaches privacy for applications released under its own developer accounts. It is not a substitute for the accurate, application-specific privacy disclosure required for an individual product. An application's privacy statement and store disclosures must describe that product's actual behavior, including current versions and integrated SDKs.
2. Data categories depend on the application
An application may process some or none of the following, depending on its features: contact or registration details; account identifiers; user-generated content; device or diagnostic information; customer support correspondence; purchase or entitlement references; and optional permissions such as location, photos, microphone, contacts or camera. The mere listing of a category here does not mean that every application collects it.
3. Permissions and choices
Device permissions, where requested, should be limited to the feature requiring access and explained in context. Users can generally manage operating-system permissions through their device settings. Denying a permission may make a related feature unavailable, but should not be represented as consent to unrelated collection.
4. External processors, SDKs and platform services
Depending on the application, operating-system providers, app marketplaces, cloud hosts, login services, error reporting, or payment infrastructure may process information. Each application is responsible for identifying relevant third parties and describing collection and sharing in its own disclosures. Apple App Store privacy labels and Google Play Data safety responses must be kept aligned with implementation and SDK behavior.
5. Purposes and protections
Where applicable, information may be processed to provide core app features, authenticate users, protect against misuse, respond to support requests, administer purchase entitlements, maintain functionality, or comply with law. Appropriate access control, transport safeguards, and system administration practices are selected based on the product's data and risk profile; no absolute security guarantee is offered.
6. Retention and deletion
Data retention differs by app and storage system. Any app that offers account creation must implement the deletion option required by the applicable platform, and the user must be able to request deletion using our external deletion pathway where required. App-specific disclosures must explain what is deleted, any legally retained records, how backups expire, and when removal is completed. We do not make a universal deletion deadline that we cannot verify for all products.
7. Children and special categories
Apps intended for children, or apps that process sensitive categories such as health or precise location, require additional design, consent, data minimization, platform, and legal review. Product-specific requirements take precedence over this general summary.
8. Privacy inquiries and version updates
For questions about an individual app, identify the exact application name and platform and write to [email protected]. For technical support, contact [email protected]. For account deletion, contact [email protected] or use Account Deletion. This general framework may be updated as applications are launched or materially changed.