Terms of Service
These Terms of Service, together with our Privacy Policy and the 2026 Technical Compliance Execution Guide, constitute the binding agreement between you and ZedLogic Cloud Pulse regarding your use of every application, service, and digital surface we publish. By installing, accessing, or using any of our products, you confirm that you have read, understood, and agreed to be bound by these terms.
This version reflects the 2026 Global Compliance Deep-Enhanced Edition. It comprehensively upgrades the IAA and IAP fraud enforcement rules, completes the EU Digital Services Act (DSA) content moderation framework, refines the iOS 18 / Android 15 technical compliance requirements, and adds explicit interaction design rules (dual confirmation, privacy policy discoverability, advertising quality) to ensure every release passes the strictest applicable review.
§ 01 Preamble & Acceptance
These Terms are issued by ZedLogic Cloud Pulse, located at the University of Florida Innovation Center, Gainesville, Florida, United States. They apply to every product, service, website, and digital surface operated under the ZedLogic Cloud Pulse name, including all applications published under our developer accounts on the Apple App Store and Google Play Store.
If you do not agree to any portion of these Terms, you must immediately discontinue use of our products and may request account closure by contacting our support team.
§ 02 Account Ownership & License Scope
2.1 · Non-Ownership Declaration
After you download and install our applications through the App Store or Google Play, you are granted a limited, non-transferable, non-rentable, non-loanable license to use the software. You do not acquire legal ownership of the account or any in-app virtual property (including but not limited to coins, gems, skins, levels, items, badges, or entitlements).
2.2 · Account Ownership
Accounts are registered and used by you; account ownership remains with the studio. You are granted only a usage right. Account registration requires (where applicable) true and complete information. You are responsible for safeguarding your account credentials and login information. Loss of account access or virtual property caused by your own negligence (for example, disclosure of passwords or authorization of untrusted third parties) is your sole responsibility.
2.3 · Account Reclamation
Accounts that have remained inactive for 180 consecutive days and have no payment history may be reclaimed by the studio to free server resources. At least 30 days before reclamation, we notify the user via in-app push notification and (where available) the registered email address. Upon reclamation, all virtual property and personal data associated with the account are permanently deleted (except where retention is required by law), and recovery is not possible.
2.4 · Account Use Restrictions
You may not transfer, rent, lend, or sell your account to any third party, nor use it for commercial profit, nor use it for illegal activity. If we discover a violation of these restrictions, we may suspend or terminate the account, delete all virtual property, and pursue further liability as warranted.
§ 03 IAA Advertising & Reward Policy
3.1 · Reward Eligibility
To earn rewards, you must fully watch a rewarded video advertisement, complete any required interaction (where present), and not engage in abnormal activity during playback (such as switching apps, locking the screen, using plugins to skip the ad, etc.). Rewards are credited immediately upon ad completion. If a reward does not credit due to network latency or ad-platform malfunction, you may report it through in-app customer support; we will investigate within 3 working days.
3.2 · Ad Quality Guarantee
We strictly review ad content served by third-party platforms and strive to filter violent, pornographic, vulgar, misleading, or otherwise inappropriate ads. Ad content is supplied by third parties. If you encounter an inappropriate ad, please report it via the in-app "Ad Complaint" channel. We investigate within 24 hours, take down or block offending ads, and pursue responsibility against the offending partner.
3.3 · Ad Fraud: Definition & Penalties
Definition. Any attempt to obtain ad rewards through improper means, evade ad playback, or interfere with ad statistics constitutes ad fraud, including but not limited to:
- Using plugins, scripts, cracked tools, or similar means to skip ads, accelerate ad playback, or simulate ad-watching behavior.
- Operating multiple accounts or multiple devices in bulk to view ads, then reselling or monetizing earned rewards.
- Modifying device parameters (device ID, IP address) or using VPN / proxy tools to switch regions in order to view ads in bulk.
- Switching apps, locking screens, or restarting the device frequently during ad playback to evade full-watch requirements.
- Exploiting ad-platform vulnerabilities to trigger fraudulent ad impressions or clicks for ad revenue.
- Any other behavior that interferes with normal ad playback or statistics.
Penalties (escalating).
- First violation: User warning; unused ad rewards are cleared; ad-viewing privileges suspended for 7 days.
- Second violation: Ad-viewing privileges suspended for 30 days; all ad rewards cleared; device violation information recorded.
- Third or subsequent violation: Permanent ban from ad viewing; the offending device is barred from using the application; the user is added to the platform blacklist. We reserve the right to pursue civil damages and, where applicable, refer the matter to judicial authorities.
- Severe violations (bulk fraud, malicious ecosystem disruption): Permanent account and device ban; we report the incident to the Apple App Store and Google Play to enable platform-level enforcement; civil damages are pursued; criminal matters are referred to law enforcement.
§ 04 IAP Payment, Refund & Dispute Resolution
4.1 · Final Price Disclosure
The displayed price of in-app virtual goods and value-added services includes the item price, the platform commission charged by Apple / Google, and any applicable VAT, GST, sales tax, or duty. The final price payable is the amount shown on the App Store / Play payment page. Material price changes are announced at least 7 days in advance via in-app notice and push notification.
4.2 · Payment Rules
All payment operations are completed through official App Store or Google Play channels. We do not directly collect any payment from you and do not store any payment information. Upon successful payment, virtual goods and value-added services are credited immediately. You can view order details in the in-app "My Orders" section.
4.3 · Refund Restrictions
Because virtual goods and value-added services are immediate and non-returnable, purchases that have been consumed (for example, spent coins, unlocked features) are generally not refundable. Refund requests may be considered in the following documented exceptional circumstances:
- Payment succeeded but the virtual good / value-added service was not credited, and the failure is confirmed to be caused by a technical fault on our side.
- Unauthorized purchase by a minor without guardian consent — the guardian may provide evidence (such as the minor's identification, payment record) to apply for a refund via the App Store / Google Play refund channel or our support team.
- The application experienced a material fault that prevented the use of purchased value-added services and could not be restored within 7 working days.
Refund process: Submit the refund application through the App Store / Google Play official refund channel or via in-app customer support, with relevant documentation. We verify within 3 working days and cooperate with the App Store / Play to complete the refund. Refund arrival time follows the platform's published timelines.
4.4 · IAP Fraud: Definition & Penalties
Definition. Any attempt to obtain virtual goods / value-added services through improper means, evade payment, or defraud refunds constitutes IAP fraud, including but not limited to:
- Malicious refund: Using App Store / Google Play refund-policy loopholes to obtain virtual goods, consume them, and then apply for a refund without returning the consumed virtual goods.
- Cracked payment flow: Using plugins, scripts, or cracked application versions to bypass official payment channels and obtain virtual goods / value-added services.
- Forged payment records: Forging orders or payment receipts to obtain virtual goods / value-added services.
- Stolen payment instruments: Using stolen bank cards, payment accounts, or redemption codes acquired through illegal channels to make purchases.
- Cross-region arbitrage: Using VPN / proxy tools to switch to lower-priced regions to purchase virtual goods, evading normal pricing.
- Bulk new-user abuse: Bulk account registration and exploitation of platform new-user discounts or promotional activities, followed by resale or monetization.
- Any other behavior that evades payment or defrauds virtual goods / refunds.
Penalties (escalating).
- First violation: User warning; virtual goods obtained through fraud are revoked; in-app purchase privileges suspended for 15 days.
- Second violation: In-app purchase privileges suspended for 90 days; all virtual goods in the account are cleared; device violation information is recorded and added to the platform blacklist.
- Third or subsequent violation: Permanent ban of the account and related devices from the application and related services; the incident is reported to the App Store / Google Play to enable platform-level enforcement (including account ban and device-level download restrictions).
- Severe violations (bulk fraud, malicious carding, significant economic damage): Permanent ban of the account and related devices; civil damages are pursued; criminal matters are referred to law enforcement; we cooperate with the App Store, Google Play, and payment institutions to hold the user accountable.
4.5 · Unauthorized Transactions
In the case of unauthorized transactions caused by minor misuse or stolen account credentials, the user (or guardian) must promptly contact Apple / Google official support and notify us. With supporting documentation (e.g., proof of minority, proof of account theft, payment records), we cooperate with the App Store to verify and, where refund conditions are met, assist the user in applying for a refund.
§ 05 Anti-Cheat & Security Protocol
To preserve the integrity of our products and protect both users and the studio, the following behaviors are strictly prohibited. Violations are investigated and may result in escalating penalties, including referral to law enforcement where appropriate:
- Using VPN, proxy tools, or other means to bypass regional restrictions or price differentials for cross-region purchase or ad viewing.
- Using any automated script, emulator, cheat, cracked version, plugin, or other tool to interfere with normal app operation, tamper with app data, or obtain improper advantage.
- Capturing or modifying communication packets, forging data, or interfering with core functions such as analytics, payment, or advertising.
- Bulk account registration, malicious traffic or score inflation, interference with leaderboards or rating systems, or damage to the product ecosystem.
- Stealing others' accounts, virtual property, or disclosing others' account information / personal data.
- Modifying device parameters (device ID, IMEI, MAC address) to evade enforcement or duplicate reward claims.
- Distributing cracked versions, cheating tools, or instructions that encourage others to engage in violation.
- Any other behavior that interferes with normal operation, infringes the rights of other users or the studio, or constitutes cheating.
Enforcement. Depending on severity, penalties include warning, feature restriction, account ban, device ban, and platform blacklisting. Severe cases result in civil damages and criminal referral. We may delete violation-related data and terminate service to violators without compensation.
§ 06 Content Moderation (DSA Compliance)
Where our products involve user-generated content (UGC), we fully comply with the EU Digital Services Act (DSA) and operate a complete content moderation framework.
6.1 · Moderation Mechanism
We operate a dual mechanism: AI-automated monitoring plus human review. Automated tools flag suspicious content in real time; trained moderators conduct secondary review of borderline cases and user complaints. This dual mechanism balances efficiency with accuracy.
6.2 · Notice-and-Action
When we identify prohibited content, we notify the user, explain the violation reason, and remove the content within 24 hours. Users may appeal removal decisions; we review and respond within 3 working days.
6.3 · Prohibited Content
Users may not publish the following prohibited content, including but not limited to:
- Politically sensitive content; content endangering national security or social stability.
- Racist, sexist, religiously discriminatory, or otherwise hateful content.
- Violent, pornographic, vulgar, gory, or terroristic content.
- False information, defamation, rumor-spreading, or misleading content.
- Content infringing the intellectual property, reputation, portrait, or privacy rights of others.
- Any content that violates the laws of any country or region, or public order and good morals.
6.4 · User Responsibility
When publishing UGC, you confirm that the content is lawful, truthful, and original, and that it does not infringe the lawful rights of any third party. If you publish prohibited content, we may remove the content, restrict your publishing privileges, or ban your account. You bear all legal responsibility arising from your publication; if you cause loss to the studio, we reserve the right to seek compensation.
6.5 · DSA Additional Requirements
We publish our content moderation standards, complaint-handling process, and violation handling rules. We publish periodic UGC moderation transparency reports and accept user and regulatory supervision. A dedicated Content Moderation Officer is appointed for large-scale UGC platforms and cooperates with EU regulatory inspections.
§ 07 2026 Technical Compliance · Apple App Store (iOS)
7.1 · Privacy Labels
Every iOS application accurately completes its Privacy Labels in App Store Connect, and must check "Data Linked to User" because IDFA, purchase records, and similar data are associated with the user profile. Data collection scope, purposes, and third-party sharing must match this Privacy Policy. False declarations result in rejection or removal.
7.2 · ATT Enforcement (2026 Upgrade)
- Before obtaining
device_id(IDFA),requestTrackingAuthorizationmust be called to present a consent prompt. The prompt copy must clearly inform the user of the consent purpose (such as ad personalization). Misleading users is prohibited. - If the user declines,
allow_tracking = falsemust be passed to every third-party SDK. Obtaining or using IDFA through other means to evade the ATT framework is prohibited. - Adapted to iOS 18's latest requirements: the ATT prompt may be shown only once. Repeatedly prompting is prohibited. After refusal, subsequent requests are not allowed — only deep-link to the device Settings may be used.
- Obtaining device identifiers through channels other than ATT is prohibited. Substituting MAC address or other device parameters for IDFA to evade privacy requirements is prohibited.
7.3 · Other iOS Technical Compliance
- Applications must not contain hidden features or non-compliant code. Evading App Store review rules (for example, hiding payment entry points, misleading functionality descriptions) is prohibited.
- Adapted to iOS 18's latest privacy requirements: access to sensitive data (photos, contacts) requires per-use authorization. Default or forced authorization is prohibited.
- In-app purchase items must clearly display price and subscription period. Designing inducement traps or misleading users into payment is prohibited.
- Where applications contain AI-generated content, this must be explicitly declared in the App Store detail page to comply with Apple's AI compliance requirements.
§ 08 2026 Technical Compliance · Google Play (Android)
8.1 · Data Safety Form
Every Android application accurately completes its Data Safety Form in Google Play Console. We declare: (a) HTTPS encryption for data in transit; (b) AES-256 encryption for data at rest; (c) accurate data collection scope, purposes, and third-party sharing. False declarations result in rejection or removal.
8.2 · SDK Transparency (2026 Upgrade)
- Google holds developers fully responsible for the behavior of every integrated third-party SDK. All integrated SDK versions must support the latest Android 14+ Privacy Sandbox. Outdated SDKs (which may have privacy vulnerabilities) are not used.
- The complete list of integrated third-party SDKs is published in Google Play Console, with each SDK's name, purpose, and data collection scope. SDKs found to violate data collection rules are removed and remediated immediately.
- Adapted to Android 15's latest requirements: integrated SDKs may not request permissions unrelated to app functionality and may not collect user personal information without justification.
- Where applications support Android 15 Private Space, the application logic is adjusted per type. Medical apps must explicitly advise users not to install in Private Space to avoid impacting core functionality. Launcher apps must declare relevant permissions and adapt to Private Space application display requirements.
8.3 · Other Android Technical Compliance
- Adapted to Android 15's latest privacy protections: support for OTP hiding during screen sharing, hidden sensitive fields marked manually by the developer.
- Applications must not contain malicious code or ad plugins. Forced ad pushes or inducement clicks are prohibited. Ad display must conform to Google Play ad policies.
- Applications must support 64-bit architecture. 32-bit-only builds are not accepted, to ensure compatibility with the latest Android devices.
- Where applications contain subscription services, an in-app subscription-management entry must be clearly labeled, supporting user cancellation at any time, in compliance with Google Play subscription policy.
§ 09 2026 Data Residency Compliance
With the rise of data-sovereignty awareness in 2026, more countries and regions are introducing stricter data-localization requirements. We strictly adhere to the following rules to avoid violations:
- Where an application has a large user base in a particular country or region (thresholds defined by local law), user data for that region is stored on compliant servers within that country/region. Cross-border transfer without approval is prohibited.
- Cross-border transfers must comply with local regulations: GDPR adequacy decisions (EU), China's Cross-Border Data Flow Provisions security assessment / standard contract requirements, India DPDP Act cross-border transfer approval, etc.
- With reference to the data sovereignty discussions raised in the 2026 U.S. Trade Report, U.S.-facing applications observe CLOUD Act requirements and cooperate with U.S. regulatory data-access requests where applicable.
- Storage locations are reviewed regularly to align with changing local regulations, particularly for countries introducing data localization in 2026 (Canada, Japan, Bolivia, Colombia, etc.). Storage strategies are adjusted accordingly.
- A data residency compliance ledger is maintained, recording user data storage location and transfer history. Periodic compliance self-audits are conducted, and local regulator inspections are accepted.
§ 10 Interaction Design Rules (2026)
10.1 · Dual Confirmation Mechanism
- Before a large IAP purchase (recommended threshold: single transaction ≥ USD 50 / EUR 50), an in-app secondary confirmation dialog must be presented, clearly stating the purchase amount, item name, and payment method. The user must manually tap "Confirm Purchase" before proceeding to the payment page. Mis-tap protection is mandatory.
- For auto-renewing subscriptions, after the user taps "Subscribe", a confirmation dialog must again inform the user of the subscription period, price, and renewal rules to avoid unintended subscriptions.
10.2 · Privacy Policy Discoverability (Mandatory)
The Privacy Policy link must be present in all three of the following locations to ensure users can access it at any time, in compliance with global regulations:
- The App Store / Google Play description page (in a prominent position);
- The application launch / splash screen or login screen — with "Agree" and "Decline" buttons. If the user declines, the application must not be usable;
- The application "Settings" or "About" menu — with the link prominently placed and directly clickable.
10.3 · Other Interaction Compliance Recommendations
- Permission requests: When requesting permissions (camera, photo library, location), clearly explain the purpose. Default or forced authorization is prohibited. Users may revoke authorization at any time via in-app or device settings.
- Ad interaction: Rewarded video ads must be clearly labeled "Watch full ad to earn reward" and provide a "Skip Ad" button (available after 5 seconds of playback). Forced ad viewing is prohibited.
- Complaint feedback: Convenient complaint channels must be available in-app — covering privacy complaints, ad complaints, UGC content complaints — with response timeframes (no more than 7 working days) and user feedback on outcome.
- Transparency display: Ad delivery rules, algorithmic recommendation logic, and data handling flow (simplified) are displayed prominently in-app, in compliance with DSA transparency requirements.
- Screen sharing indicator: Adapted to Android 15's latest requirements, a prominent indicator label appears in the status bar during screen sharing / casting / recording, reminding the user that the screen is being shared. The user can tap the indicator to stop sharing quickly.
§ 11 Compliance Risk Control & Periodic Review
11.1 · Compliance Risk Control Measures
- Compliance review mechanism: Before development and submission, application code, privacy policy, terms of service, and interaction design undergo full compliance review against App Store, Google Play, and global regional requirements.
- Continuous compliance monitoring: Designated staff monitor global privacy law and app store policy updates (e.g., U.S. state privacy laws, EU DSA updates, Android 15 / iOS 18 system policy changes). Application and agreement content is updated accordingly.
- Third-party partner management: Third-party ad platforms, SDK providers, and payment processors are audited for compliance on a regular basis. Compliance agreements define data handling responsibility. Violation results in immediate termination.
- User request handling: A documented process for user data requests (access, rectification, deletion, complaint) is maintained. Response and resolution occur within statutory windows. Records are retained for supervision.
- Security safeguards: Application data security is hardened through encrypted storage, encrypted transmission, access controls, and other technical means. Data-leak prevention, tamper resistance, and loss prevention are in place. Regular security testing and risk assessment are performed.
- Employee training: R&D, operations, and customer service personnel receive regular compliance training covering privacy regulations, app store policy, and anti-fraud rules, to prevent inadvertent violations.
11.2 · Periodic Review Requirements
Because the global legal environment (especially U.S. state privacy laws and EU DSA implementing rules) is continuously evolving, and app store policies and technical standards are constantly updated, we conduct a full review of these Terms and the application's compliance status at least every 6 months. The review covers:
- Agreement terms: Confirm alignment with the latest regulations and app store policies; supplement or amend as needed (e.g., add regional compliance clauses, update fraud penalties).
- Application compliance: Confirm code, SDK versions, and interaction design meet the latest technical compliance requirements (e.g., Android 15 / iOS 18 adaptation, ATT framework execution).
- Data handling: Confirm collection, storage, transmission, and sharing flows comply with local residency and third-party sharing requirements.
- Anti-fraud mechanism: Confirm ad and IAP anti-fraud rules remain robust. Update penalties as new fraud methods emerge.
- User requests: Audit the response status of user data requests. Identify late or mishandled cases and optimize the process.
§ 12 Governing Law & Dispute Resolution
These Terms are governed by the laws of the State of Florida, United States, without regard to conflict-of-laws principles. Where mandatory consumer-protection laws of your jurisdiction apply (for example, EU consumer law, UK consumer rights, California consumer law), those mandatory provisions prevail to the extent of any conflict.
Disputes are first addressed through good-faith negotiation with our support team. If negotiation fails, disputes are submitted to the competent courts of Gainesville, Florida, except where consumer law mandates the courts of the consumer's domicile.
EU and UK consumers may also use the European Commission's Online Dispute Resolution platform (ec.europa.eu/consumers/odr) and may bring proceedings in the courts of their place of residence.
Questions, Feedback, Complaints
For any question, feedback, or complaint regarding these Terms, please contact us through any of the channels below. We respond within statutory windows for every region we serve.