Privacy governance for our website, mobile applications, and app marketplace operations.

2. Scope and Coverage

This Privacy Policy applies to:

• The corporate website and any related landing pages, forms, support pages, and linked resources operated under the tingzhentech.com domain.
• Mobile applications, mobile management applications, administrative tools, productivity tools, industry service apps, and related digital products distributed through Google Play, Apple App Store, and other authorized platforms.
• Business activities involving technical research and development, technical consulting, technical services, industrial design services, business information consulting, and the commercial sale or support of electronics, components, hardware, automation equipment, plastic products, metal products, electromechanical equipment, and office equipment where personal data is involved.

This policy does not control third-party websites, developer dashboards, payment processors, analytics providers, or advertising networks except to the extent we determine the purposes and means of processing under applicable law.

3. Data We Collect

Depending on how you interact with our website, our mobile applications, and our commercial services, we may collect the following categories of data:

• Name, company, job title, business email address, phone number, and inquiry content submitted through email or contact channels.
• Support communications, account relationship information, purchase discussions, and project requirements.
• Content you provide in app feedback, support tickets, or survey responses.

• IP address, approximate geolocation inferred from IP, browser type, device type, operating system, language settings, app version, device identifiers permitted by the platform, session timestamps, crash information, and diagnostic data.
• Identifiers made available by operating systems or app platforms such as Google Advertising ID, Apple Identifier for Advertisers when permissioned, Firebase installation IDs, app instance IDs, or comparable identifiers where lawful and technically available.

• Page views, button events, feature usage, session duration, navigation paths, in-app engagement, campaign attribution, and service performance metrics.
• Operational records for management features such as tasks, reports, dashboards, inventory interactions, approvals, and administrative events when our mobile management applications are used.

• Service history, quote requests, order-related communication, account classification, and business relationship records.
• When a store platform handles billing, we generally receive order status, subscription status, settlement reports, and limited transaction metadata rather than full payment card details.

• Analytics SDK outputs, attribution signals, consent status, anti-fraud signals, ad request metadata, impression and revenue events, and mediation logs from integrated advertising or analytics tools.

5. Advertising, Analytics, and Monetization SDKs

Some of our mobile applications may contain advertising, analytics, attribution, or mediation SDKs. The exact set of providers can differ by app, version, user region, store channel, or business objective. Integrated providers may include Google AdMob, Google Ad Manager, Firebase Analytics, Google Analytics for Firebase, AppLovin MAX, AppLovin, Unity Ads, Unity LevelPlay or ironSource, Meta Audience Network, Liftoff Monetize, Vungle, Mintegral, Pangle, InMobi, Chartboost, Smaato, Fyber, AdColony, Digital Turbine Exchange, Amazon Publisher Services, Moloco, Start.io, Yandex Ads, and other equivalent or successor monetization partners.

Advertising-supported apps may use app open ads, rewarded video ads, interstitial ads, banner ads, and other lawful ad formats supported by the applicable store and region. Depending on integration design, these providers may collect or receive device identifiers, IP address, app activity data, coarse location, approximate region, ad interaction data, performance metrics, crash signals, diagnostics, consent signals, and anti-fraud information.

• Where consent is required under the GDPR, UK GDPR, ePrivacy rules, or similar laws, we seek consent before storing or accessing information on a device for personalized advertising, measurement, or related processing that legally requires consent.
• Where legitimate interests are relied on for limited operational processing, we assess necessity, proportionality, and user impact.
• Users may reject or withdraw consent within the app or device settings where technically available.

• Depending on user region, consent status, age screening, and platform restrictions, we may serve personalized ads, non-personalized ads, contextual ads, or no ads.
• If a user is flagged as under the age threshold for personalized advertising or subject to child-directed treatment, ad delivery may be restricted, non-personalized, or disabled in accordance with platform and legal requirements.

• We and our partners may measure ad views, clicks, rewarded completions, impressions, revenue events, conversion signals, invalid traffic, and fraud indicators to maintain marketplace integrity and app sustainability.

6. App Marketplace and Platform Compliance

For applications distributed through Google Play, the Apple App Store, and related stores, we design our privacy disclosures to support applicable platform obligations, including but not limited to Google Play User Data requirements, Google Play Families policies where relevant, Apple App Store Review Guidelines, Apple privacy nutrition label disclosures, App Tracking Transparency requirements, and SDK disclosure expectations.

• We aim to describe data collection, sharing, retention, and deletion practices accurately in store listing disclosures and in-app notices.
• Where Apple App Tracking Transparency applies, permission is requested before tracking across apps and websites owned by other companies for advertising or measurement purposes.
• Where Google Play data safety declarations apply, we maintain statements regarding collection, sharing, security, deletion availability, and applicable handling practices.
• Where SDK runtime disclosure, consent mode, or regional policy implementation is required, we implement such mechanisms to the extent technically and legally applicable.

8. Age Limits, Teen Users, and Child Privacy

Our website is primarily intended for business audiences. Our apps may serve general audiences, enterprise users, or specific market segments depending on the product. Unless a particular app expressly states otherwise, our services are not directed to children under the minimum age permitted by applicable law and platform policy.

• We do not knowingly collect personal data from children in violation of COPPA, GDPR child consent rules, Google Play Families requirements, Apple child-directed rules, or similar laws.
• Where an app may be accessed by teens or mixed audiences, we may implement age screening, age gates, consent flows, limited ad treatment, restricted SDK behavior, or parental involvement mechanisms.
• If we learn that personal data was collected from a child without proper authorization, we will take steps to delete or de-identify that data as required by law.

9. Security, Retention, and Data Deletion

• We use reasonable organizational and technical measures to protect personal data, including access controls, supplier management, role-limited access, and security reviews proportionate to the nature of the data and service.
• No security measure is absolute, and internet, app store, and mobile platform transmissions carry inherent risk. We therefore cannot guarantee complete security in every circumstance.
• We retain personal data only for as long as necessary to provide services, meet business needs, resolve disputes, fulfill legal obligations, maintain security records, or enforce our agreements.
• Where deletion rights apply, users may request deletion by contacting us, subject to lawful exceptions including security, fraud prevention, legal retention, tax, accounting, or dispute obligations.