Terms of Service

1. Preamble and Acceptance

These Terms of Service (the “Terms”) constitute a binding agreement between you (“the user”, “you”) and arkdevbitrealm (“we”, “our”, “us”), a United Kingdom mobile-research and development studio headquartered at St John’s Innovation Centre, Cambridge CB4 0WS, United Kingdom. They govern your use of every mobile application, website, and service that we publish under the arkdevbitrealm name, including but not limited to Pet Health Archive, Home Renovation Engine, Language Memory, Wardrobe Planner, Sheet Music Archive, Monthly Finance Suite, and any successor or ancillary product (collectively, the “Services”).

This document is the 2026 Global Compliance Edition. It supersedes all prior versions. By installing, accessing, or using the Services, you confirm that you have read, understood, and agreed to these Terms, our Privacy Policy, and any additional terms that may apply to a specific feature. If you do not agree, do not install or use the Services.

2. Account Ownership and Licence Scope

2.1 Non-ownership notice

By downloading or installing the Services from the App Store, Google Play, or any other authorised distribution channel, you are granted a limited, non-transferable, non-rentable, non-loanable, revocable licence to use the software for personal, non-commercial purposes. You do not acquire legal ownership of the account, the application, or any in-app virtual property (including but not limited to coins, credits, points, skins, levels, items, unlocks, or subscriptions).

2.2 Account registration and ownership

Where account creation is required, the account is registered and used by you. You agree to provide true, complete, and current information at the point of registration and to update it promptly if it changes. The account is owned by arkdevbitrealm; you hold a usage right only. You are responsible for safeguarding your credentials and for any activity that occurs under your account. Loss or damage arising from your own negligence (for example, disclosing your password, or authorising an untrusted third party) is your responsibility.

2.3 Account recovery and deactivation

If an account remains inactive (no login, no paid activity) for a continuous period of 180 days, we may deactivate the account to free server resources. We will notify you in advance via in-app push, system notification, and / or your registered email (where applicable) at least 30 days before deactivation. On deactivation, all in-app virtual property and personal data associated with the account are permanently deleted (except where retention is required by law) and cannot be recovered.

2.4 Restrictions on account use

• You must not transfer, rent, lend, sell, or otherwise commercially exploit the account.
• You must not use the account for any unlawful purpose or to engage in any illegal activity.
• You must not use the account to interfere with the operation of the Services, the privacy of other users, or the integrity of our systems.
• If we find that you have breached these restrictions, we may suspend or permanently ban the account, delete associated virtual property, and pursue any other remedies available to us.

3. IAA — Advertising and Reward Policy

The Services may display advertising in the form of rewarded video, interstitial, splash (app-open), and adaptive banner units, served through the certified mediation partners listed in our Privacy Policy. The following rules govern the use of advertising and the award of advertising-related rewards.

3.1 Reward eligibility

To receive an in-app reward in exchange for viewing an ad, the user must watch the rewarded video in full, complete any required interaction (for example, tapping a call-to-action), and the playback must not be interrupted by abnormal behaviour such as switching apps, locking the device, muting the system, or using a plugin to skip. Rewards are credited to the user’s account immediately on successful completion. If a reward is not credited due to a network delay, an ad-platform outage, or another technical reason, the user may report the issue through the in-app support channel, and we will investigate within 3 working days.

3.2 Ad-quality guarantee

We strictly review the ad inventory sourced from our third-party partners and do our best to filter ads that contain violence, pornography, vulgar content, misleading claims, or other inappropriate material. Ad creative is, however, ultimately controlled by the third party. If you encounter an inappropriate ad, please report it through the in-app “Report Ad” channel. We will review reports within 24 hours, block or remove the offending creative, and pursue remedy with the third-party network.

3.3 Ad-fraud definitions and penalty rules (highly detailed)

3.3.1 Definition of ad fraud

Any attempt to obtain advertising rewards, evade ad playback, or interfere with ad statistics through improper means is treated as ad fraud. Examples include, but are not limited to:

• Using plugins, scripts, cracked tools, or automation to skip ads, accelerate ad playback, or simulate ad viewing.
• Operating multiple accounts or multiple devices to mass-view ads and then resell or monetise the resulting rewards.
• Modifying device parameters (device ID, IP address) or using VPNs / proxy tools to switch regions and bulk-view ads.
• Frequently switching apps, locking the device, or rebooting during ad playback in order to circumvent the full-view requirement.
• Exploiting ad-platform vulnerabilities to falsely trigger ad impressions or clicks and obtain revenue.
• Any other behaviour that interferes with the normal playback or measurement of advertising.

3.3.2 Penalty rules

• First violation: Warning. All unredeemed ad rewards on the account are cleared. Ad-viewing privileges are suspended for 7 days.
• Second violation: Ad-viewing privileges are suspended for 30 days. All ad rewards on the account are cleared. The device’s violation information is recorded.
• Third (and subsequent) violations: Permanent revocation of ad-viewing privileges. The relevant device is added to the platform block-list, and the user loses the right to use the application on that device. We reserve the right to seek civil damages and, where the conduct is criminal, to refer the matter to the relevant authorities.
• Severe cases (bulk fraud, malicious ecosystem interference): Permanent account and device ban. We report the case to the App Store, Google Play, and other distribution platforms and assist them in applying further penalties. We pursue civil damages and, where appropriate, criminal prosecution.

4. IAP — Payment, Refunds and Dispute Resolution

4.1 Final-price disclosure

The price displayed for in-app virtual goods and value-added services includes the base price, the App Store / Google Play platform commission, and any applicable VAT, GST, sales tax, or customs duty. The final price charged is the price shown on the App Store / Google Play payment page at the moment of confirmation. We will give at least 7 days’ advance notice of any price change via in-app announcement and / or push notification.

4.2 Payment rules

All payments are processed through the official App Store / Google Play payment systems. We do not collect or store bank-card numbers, CVV codes, payment passwords, or any other sensitive payment information. On successful payment, the virtual goods or value-added service are delivered to your account instantly, and the order is visible under “My Orders” in the application.

4.3 Refund restrictions

Because virtual goods and value-added services are consumed instantly and are not returnable, refunds are generally not supported once a purchase has been used (for example, coins already spent, or features already unlocked). Refund exceptions are limited to the following cases, each of which requires supporting evidence:

• Payment was successful but the virtual goods / value-added service was not delivered, and the failure is confirmed to be caused by our technical fault.
• A minor made a purchase without the consent of a parent or legal guardian. The parent or legal guardian may provide the minor’s identity documents and the relevant payment record, and apply for a refund through the App Store / Google Play or our support channel.
• The application experienced a material fault that prevents the user from using the purchased value-added service, and the fault cannot be resolved within 7 working days.

4.4 Refund process

Refund requests must be submitted through the App Store / Google Play official refund channel or the in-app support channel, accompanied by the relevant evidence. We will review the request within 3 working days and cooperate with the App Store or Google Play to process the refund. The actual time for the refund to reach the user is governed by the App Store or Google Play official policy.

4.5 IAP fraud definitions and penalty rules (highly detailed)

4.5.1 Definition of IAP fraud

Any attempt to obtain in-app virtual goods or value-added services through improper means, or to evade payment or obtain refunds through fraud, is treated as IAP fraud. Examples include, but are not limited to:

• Malicious refund: Exploiting the App Store / Google Play refund policy to obtain virtual goods, use them, and then request a refund without returning the used goods.
• Payment-process cracking: Using plugins, scripts, cracked applications, or other means to bypass the official payment channels and obtain virtual goods or services for free.
• Forged payment records: Forging orders or payment receipts to obtain virtual goods or services.
• Stolen payment instruments: Using stolen bank cards, payment accounts, or illegally obtained redemption codes to make purchases.
• Region-price arbitrage: Using VPNs / proxy tools to switch into low-price regions to purchase virtual goods, circumventing normal regional pricing.
• Bulk-account abuse: Creating accounts in bulk to exploit App Store / Google Play new-user offers or discount events, and then reselling or monetising the resulting virtual goods.
• Any other behaviour that evades payment or obtains virtual goods or refunds through deception.

4.5.2 Penalty rules

• First violation: Warning. All virtual goods obtained through fraud are recovered. In-app purchase privileges are restricted for 15 days.
• Second violation: In-app purchase privileges are suspended for 90 days. All virtual goods on the account are cleared. The device’s violation information is recorded and added to the platform block-list.
• Third (and subsequent) violations: Permanent account and device ban. The user is prohibited from using the application and related services. We report the case to the App Store / Google Play and assist them in applying further penalties (such as account suspension, download restrictions).
• Severe cases (bulk fraud, malicious stolen-card use, material financial loss): Permanent account and device ban. We pursue civil damages and, where appropriate, criminal prosecution. We report the case to the App Store, Google Play, and payment institutions, and assist them in pursuing the user.

4.6 Unauthorised transactions

If an unauthorised transaction occurs as a result of a minor’s mistaken operation or a stolen account, the user (or their parent / guardian) should contact Apple / Google official support immediately, and notify us with the relevant evidence (for example, the minor’s identity documents, proof of account theft, payment record). Subject to the refund conditions above, we will cooperate with the App Store or Google Play to verify and process the refund.

5. Anti-Cheat and Security Agreement

To maintain the integrity of the Services and protect the legitimate interests of users and of arkdevbitrealm, the following behaviours are strictly prohibited. Violations will be penalised according to their severity, and severe cases will be referred to the relevant authorities.

• Using VPNs, proxy tools, or other means to bypass regional restrictions or price differences for cross-regional purchase or ad viewing.
• Using any automated script, emulator, plug-in, cracked build, or other tool to interfere with normal operation of the application, tamper with data, or obtain unfair advantage.
• Capturing or modifying packets, forging data, or otherwise interfering with the application’s communication protocol and its statistics, payment, or advertising functions.
• Bulk-creating accounts, artificially inflating installs or scores, interfering with rankings or review systems, or damaging the application ecosystem.
• Stealing another user’s account or virtual property, or disclosing another user’s account information or personal data.
• Modifying device parameters (device ID, IMEI, MAC address) to circumvent penalties or repeatedly obtain rewards.
• Distributing cracked versions of the application, cheating tools, or instructions for committing any of the above.
• Any other behaviour that interferes with the normal operation of the application, or infringes the legitimate rights of users or of arkdevbitrealm.

Penalties may include, by severity: warning, feature restriction, account suspension, device ban, and block-list inclusion. Severe cases will result in civil liability and, where appropriate, criminal referral. We may also delete the relevant user’s data, terminate the provision of the Services to that user, and owe no compensation.

6. Content Moderation (DSA Compliance)

Where a Service involves user-generated content (UGC), we strictly comply with the European Digital Services Act (DSA) and implement a robust content-moderation system.

6.1 Moderation mechanism

We operate a dual “AI-automated monitoring + human review” mechanism. AI tooling monitors UGC in real time, flags potentially non-compliant content, and provides first-pass interception. Human moderators then review flagged content and user complaints to ensure both efficiency and accuracy.

6.2 Notice-and-takedown

When we identify non-compliant content, we notify the user, explain the reason, and remove the content within 24 hours. Users may appeal the takedown decision; we will review and respond within 3 working days.

6.3 Prohibited content

Users must not post content that is:

• Politically sensitive, endangering national security, or undermining social stability.
• Discriminatory on the basis of race, gender, religion, or other protected characteristic.
• Violent, pornographic, vulgar, gory, or otherwise inappropriate.
• Misleading, fabricated, defamatory, or fraudulent.
• Infringing the intellectual property, reputational, image, privacy, or other legal rights of a third party.
• In violation of any applicable law or accepted public-order norms.

6.4 User responsibility

Users must ensure that their UGC is lawful, truthful, and original, and that it does not infringe the legal rights of others. If a user posts non-compliant content, we may remove the content, restrict the user’s posting rights, or ban the user. The user is liable for any resulting damages, and we reserve the right to seek compensation.

6.5 DSA additional requirements

We publish our content-moderation standards, complaint-handling process, and remediation procedures, and we issue periodic UGC moderation reports. We accept oversight by users and regulators. A dedicated content-moderation contact is appointed for large-scale UGC and cooperates with EU regulatory inspections.

7. Apple App Store (iOS) Technical Compliance

7.1 Privacy labels

We accurately complete the privacy-label information in the App Store backend. We do not conceal data-association relationships. The data collected, the purpose of use, and the third-party sharing details are stated truthfully and consistently with this Privacy Policy. Submitting false information will result in App Store rejection or removal of the application.

7.2 ATT enforcement (2026 updates)

• Before accessing device_id (IDFA), we call requestTrackingAuthorization to display a consent dialog. The consent text clearly states the purpose (e.g., personalised advertising).
• If the user declines, we transmit allow_tracking = false to all third-party SDKs. We do not access or use IDFA, and we do not circumvent the ATT framework.
• In line with iOS 18 requirements, the ATT prompt is displayed only once. We do not harass the user with repeat prompts. If declined, the user is not prompted again and is gently directed to the device-level settings to grant consent.
• We do not access device identifiers through non-ATT channels or substitute other device parameters (e.g., MAC address) for IDFA in order to evade this Privacy Policy.

7.3 Other iOS technical compliance

• Applications do not contain hidden features, non-compliant code, or behaviours designed to evade App Store review (such as hidden payment entries or misleading feature descriptions).
• We adapt to the latest iOS 18 privacy requirements. Access to sensitive data (for example, photos, contacts) requires per-request authorisation. We never default-authorise or force-authorise access.
• In-app purchase items clearly display price and subscription period. We do not include deceptive purchase prompts or misleading paywalls.
• Where the application contains AI-generated content, the App Store detail page clearly discloses this in accordance with Apple’s AI-compliance requirements.

8. Google Play (Android) Technical Compliance

8.1 Data-safety form

We accurately complete the data-safety form in the Google Play backend. We declare that data in transit is encrypted with HTTPS / TLS, and data at rest is encrypted with AES-256. The data collected, the purpose of use, and the third-party sharing details are stated truthfully and consistently with this Privacy Policy. Submitting false information will result in Google Play rejection or removal of the application.

8.2 SDK transparency (2026 updates)

• Google requires that the developer take full responsibility for the behaviour of all third-party SDKs integrated. We ensure that all integrated SDK versions support the latest Android 14+ Privacy Sandbox and do not use out-of-date SDKs that may contain privacy or security vulnerabilities.
• We publish a full list of integrated third-party SDKs in the Google Play backend, including the SDK name, purpose, and data-collection scope, to ensure SDK data processing is compliant. If an SDK is found to collect data in violation of policy, we will remove it and remediate the application without delay.
• In line with Android 15 requirements, integrated SDKs do not request permissions unrelated to the application’s functionality, do not collect personal information without consent, and do not interfere with normal device operation.
• If the application supports the Android 15 Private Space feature, logic is adjusted appropriately. For example, medical applications should clearly advise users not to install in Private Space to avoid affecting core functionality; launcher applications must declare the relevant permissions to support Private Space app visibility.

8.3 Other Android technical compliance

• We adapt to the latest Android 15 privacy protections, including dynamic OTP concealment (sensitive content is hidden during screen sharing) and manual sensitive-field marking, to safeguard user privacy.
• The application does not contain malicious code, ad plug-ins, forced push notifications, or click-bait. Ad display is in line with the Google Play ad policy.
• The application supports the 64-bit architecture. A 32-bit-only build is not provided, ensuring compatibility with the latest Android devices.
• If the application offers subscriptions, the in-app interface clearly marks the subscription management entry, supports one-tap cancellation, and complies with the Google Play subscription policy.

9. 2026 Data-Residency Compliance

With the global rise of data-sovereignty awareness in 2026, many countries and regions are introducing stricter data-localisation requirements. We follow the rules below to ensure full compliance.

• Where an application has a significant user base in a particular country or region (the specific threshold being that country’s regulation, e.g., China, India, Saudi Arabia, Brazil, the EU, Canada), data of users in that region is stored on compliant servers within the country or region, and is not transferred abroad without authorisation.
• Cross-border data transfers strictly follow local regulations — for example, the EU GDPR adequacy decision, China’s Provisions on Promoting and Regulating Cross-border Data Flows (security assessment / standard contract), India’s DPDP Act cross-border transfer approval. No cross-border transfer is made without the required approval.
• For 2026 US trade-report discussions on global data-sovereignty disputes, we monitor developments to avoid compliance risks. Applications serving US users comply with the CLOUD Act where applicable and cooperate with US regulatory data-access requests when lawful.
• We regularly review data-storage locations to ensure ongoing compliance with changes in local regulation — in particular for the 2026 newly introduced data-localisation requirements in Canada, Japan, Bolivia, Colombia, and other jurisdictions.
• We maintain a data-residency compliance register recording user-data storage locations and cross-border transfer details. We conduct regular self-audits and cooperate with local regulators.

10. Interaction-Design Standards

10.1 Double-confirmation mechanism

• For high-value IAP purchases (we recommend threshold ≥ USD / EUR 50 per single transaction), the application surfaces an in-app second confirmation dialog clearly stating the purchase amount, the item name, and the payment method. The user must manually tap “Confirm Purchase” before being redirected to the payment page, in order to prevent accidental purchase.
• For auto-renewing subscriptions, after the user taps “Subscribe”, a second confirmation dialog appears stating the billing period, the price, and the renewal rules, in order to prevent accidental subscription.

10.2 Easy access to the Privacy Policy (mandatory)

The link to the Privacy Policy is present in all three of the following locations at all times, ensuring users can review the policy whenever they wish and meeting global compliance requirements:

1. The App Store / Google Play description page, in a prominent position.
2. The application launch screen (or login page), where the user may tap a link to read the full Privacy Policy. The launch screen presents “Agree” and “Decline” buttons; if the user declines, the application cannot be used.
3. The in-app “Settings” or “About” menu, in a prominent position. Tapping the link opens the full Privacy Policy directly, and is accessible at any time.

10.3 Other interaction-compliance recommendations

• Permission requests: When requesting a permission (camera, photo library, location), the application clearly states the purpose of the permission. We do not default-authorise or force-authorise. The user may revoke authorisation at any time via the in-app settings or the device-level settings.
• Ad interaction: Rewarded video ads are clearly labelled “Watch the full ad to earn a reward” and provide a “Skip Ad” button (available after 5 seconds of playback). We never force the user to watch an ad.
• Complaints and feedback: The application provides easy in-app channels for privacy complaints, ad complaints, UGC complaints, and others. Feedback is acknowledged and resolved within 7 working days at most, and the user is informed of the result.
• Transparency display: The application prominently displays the ad-placement rules, the algorithmic-recommendation logic, and the data-handling workflow (simplified) in compliance with the DSA transparency requirements.
• Screen-sharing notification: In line with Android 15 requirements, during screen sharing, casting, or screen recording, the status bar displays a prominent indicator reminding the user that screen sharing is active. The user may tap the indicator to stop sharing immediately.

11. Compliance Risk Control

• Compliance-review mechanism: Before development and App Store / Google Play submission, we conduct a full compliance review of the application code, Privacy Policy, Terms of Service, and interaction design to ensure compliance with App Store, Google Play, and global regulations.
• Compliance knowledge update: We designate personnel to monitor the latest changes in global privacy regulations and app-store policies (e.g., US state privacy laws, EU DSA updates, Android 15 / iOS 18 system-policy changes), and update the application and these documents promptly.
• Third-party partner management: We regularly audit the compliance of third-party ad platforms, SDK providers, and payment processors, sign compliance agreements that clearly define data-processing responsibility, and terminate the partnership immediately in the event of a partner violation.
• User-request handling: We maintain a process for handling user data-related requests (access, rectification, deletion, complaint). All requests are acknowledged and processed within the required timeframes, with full records retained.
• Security: We strengthen application data security with encryption at rest, encryption in transit, access control, and other technical measures, and conduct regular security testing and risk assessment.
• Staff training: We conduct regular compliance training for R&D, operations, and customer-service staff, covering privacy regulation, app-store policy, and anti-fraud rules, to raise compliance awareness and avoid violations caused by operational errors.

12. Periodic Review

Because the global legal environment (especially US state privacy laws, the EU DSA implementing rules) is in continuous flux, and app-store policies and technical standards are constantly updated, we conduct a full review of these Terms and of our application’s compliance every 6 months. The review covers:

• Terms: Whether these Terms are consistent with the latest regulations and app-store policies, and whether additions or modifications are needed (e.g., new regional compliance clauses, updated anti-fraud penalty rules).
• Application compliance: Whether the application code, SDK versions, and interaction design are consistent with the latest technical-compliance requirements (e.g., Android 15 / iOS 18 adaptation, ATT framework execution).
• Data processing: Whether data collection, storage, transfer, and sharing flows are compliant, whether data residency meets local requirements, and whether third-party data sharing is controllable.
• Anti-fraud: Whether the ad- and IAP-fraud rules are sufficient, and whether the penalty rules need to be updated to address the latest fraud methods.
• User requests: A review of past user data-related requests, identification of any unacknowledged or mishandled cases, and process optimisation.

13. Liability and Disclaimers

To the maximum extent permitted by applicable law, the Services are provided “as is” and “as available”, without warranty of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the Services will be uninterrupted, error-free, or free of harmful components, or that defects will be corrected.

To the maximum extent permitted by applicable law, in no event shall arkdevbitrealm, its directors, employees, partners, agents, or suppliers be liable for any indirect, incidental, special, consequential, or punitive damages, including but not limited to loss of profits, data, goodwill, or other intangible losses, arising out of or in connection with your use of (or inability to use) the Services.

Nothing in these Terms excludes or limits liability that cannot be excluded or limited under applicable law, including liability for death or personal injury caused by negligence, or for fraud or fraudulent misrepresentation.

14. Governing Law and Dispute Resolution

These Terms are governed by the laws of England and Wales, without regard to its conflict-of-laws principles. Any dispute arising out of or in connection with these Terms — including any question regarding its existence, validity, or termination — shall be referred to and finally resolved by the courts of England and Wales, except where mandatory consumer-protection laws of the user’s country of residence require otherwise.

Consumers in the EU and UK may also use the European Commission’s Online Dispute Resolution platform (https://ec.europa.eu/consumers/odr) and the relevant alternative-dispute-resolution bodies in their country of residence.

15. Changes to these Terms

We may update these Terms as our products evolve, new regulations come into force, or third-party partners change. The “Effective” date at the top of this document reflects the most recent update. For material changes, we will notify you via in-app message and, where required by law, request renewed consent. Continued use of the Services after the effective date of the updated Terms constitutes acceptance of the changes.

16. Contact

For any questions, comments, complaints, or reports regarding these Terms or the Services, please contact us at:

• General inquiries: contact@arkdevbitrealm.com
• Business support: support@arkdevbitrealm.com
• Post: arkdevbitrealm, St John’s Innovation Centre, Cowley Road, Cambridge CB4 0WS, United Kingdom