General Terms and Conditions of Use

Preamble

These General Terms and Conditions of Use (hereinafter collectively referred to as the “Terms”, this “Agreement”, or the “Instrument”) constitute a binding juridical instrument entered into between CodeFryDev (hereinafter the “Service Provider”, “we”, “us”, or “our”) and any natural or juridical person who accesses, registers for, or otherwise avails themselves of the Service Provider’s digital offerings (hereinafter the “User”, “you”, or “your”).

The present Agreement governs the modalities, conditions, restrictions, permissions, and legal consequences attendant upon any form of engagement with the Service Provider’s websites, mobile and desktop applications, browser-based tools, online games, artificial intelligence interfaces, design utilities, educational platforms, application programming interfaces, software artefacts, documentation repositories, developer portals, and any ancillary or successor digital services that may be introduced from time to time (hereinafter collectively designated the “Digital Properties”).

The CodeFryDev Ecosystem comprises dozens of individual products—spanning developer tools, creative applications, games, AI services, and mobile apps—each accessible through paths under codefrydev.in as enumerated in Schedule E. Unless a Product Terms expressly provides otherwise, this single Agreement governs every product in the Ecosystem, including your use of analytics and session intelligence technologies deployed uniformly across those properties.

By effectuating access to, installation of, registration within, or continued utilisation of any Digital Property, the User expressly acknowledges that they have read, comprehended, and voluntarily accepted the entirety of this Agreement, together with any Product-Specific Terms incorporated herein by reference, the Service Provider’s Privacy Policy , and any additional policy instruments expressly cited within these Terms. Should the User dissent from any provision herein contained, they are under a corresponding obligation to refrain forthwith from any further interaction with the Digital Properties.

Dissent and Immediate Cessation of Use

If the User finds any provision of this Agreement—or any associated Privacy Policy , Product Terms, open source licence notice, or analytics and session-recording practice described herein or incorporated by reference—to be unacceptable, disagreeable, unconscionable, or incompatible with their personal convictions, commercial requirements, or legal obligations, the User is under an immediate and unconditional obligation to discontinue all use of the Digital Properties without delay.

Such discontinuance shall include, without limitation: closing all browser tabs, windows, or embedded frames displaying CodeFryDev content; terminating active sessions and authenticated Accounts; uninstalling any Application from all devices; and refraining from any subsequent access, whether direct, automated, or through third-party links.

No use of the Digital Properties is permitted on altered or partial terms. The Service Provider extends no invitation to negotiate bespoke contractual arrangements through continued use. Should the User withhold assent to these Terms, the User must forthwith close this site and discontinue all access immediately.

Continued presence upon, navigation within, or interaction with any Digital Property after having been afforded a reasonable opportunity to review this Agreement shall constitute conclusive evidence of assent, notwithstanding any subjective dissatisfaction, entertainment-related objection, or retrospective disagreement the User may thereafter express.

Nothing in this Preamble shall be construed as limiting the operative force of the substantive provisions that follow. Where a conflict arises between the Preamble and an operative Article, the operative Article shall prevail.

Article 1 — Interpretation, Construction, and Definitions

1.1 Rules of Construction

Unless the context otherwise requires, the following rules of construction shall apply to this Agreement:

(a) words importing the singular shall include the plural and vice versa, and words importing any gender shall include all genders;

(b) references to “including”, “include”, or “includes” shall be deemed followed by “without limitation”;

(c) references to statutes include amendments, re-enactments, and subordinate legislation;

(d) headings are for convenience only and do not affect interpretation;

(e) “days” means calendar days unless stated as business days;

(f) “writing” includes email and durable electronic communications;

(g) “herein” and cognate expressions refer to this Agreement as a whole;

(h) time periods calculated from an event exclude the day of the event;

(i) no contra proferentem rule applies against the Service Provider solely because it drafted a provision.

1.2 Hierarchy of Instruments

In the event of inconsistency, the following order of precedence applies:

1. a separate written agreement executed by authorised representatives of both parties;

2. Product-Specific Terms for the relevant product;

3. these General Terms and Conditions of Use;

4. the Privacy Policy, Cookie Policy , and incorporated policies;

5. the Community Code of Conduct Instrument and Security Policy where applicable;

6. marketing materials, FAQs, and help documentation (informational only unless expressly contractual).

1.3 Glossary of Defined Terms

• “Account” a unique profile or credential set created or assigned to the User for authenticated access.

• “Affiliate” an entity controlling, controlled by, or under common control with the Service Provider.

• “Agreement” these Terms as amended, with incorporated documents.

• “API” application programming interfaces, SDKs, webhooks, and programmatic endpoints provided by the Service Provider.

• “Application” software published by the Service Provider for mobile, desktop, web, or embedded platforms.

• “Beta Feature” alpha, beta, preview, or experimental functionality that may be incomplete or withdrawn.

• “Confidential Information” non-public information designated or reasonably understood as confidential.

• “Content” all materials disseminated through the Digital Properties, including code, UI, media, and documentation.

• “Digital Properties” all websites, Applications, APIs, platforms, and services operated by the Service Provider, including the CodeFryDev Ecosystem hosted at codefrydev.in, its subdomains, path-based applications (e.g. /games/, /JsonPlayground/, /ai/), mobile applications, and any successor domains or platforms listed or referenced in Schedule E.

• “CodeFryDev Ecosystem” the interconnected portfolio of digital products, tools, games, utilities, documentation sites, and experimental services published under the CodeFryDev brand and accessible via codefrydev.in and associated URLs identified in Schedule E, whether accessed individually or collectively.

• “Analytics Services” third-party measurement and intelligence platforms deployed across the CodeFryDev Ecosystem, presently including Google Analytics (Measurement ID: G-VM01Q3R43D) and Microsoft Clarity (Project ID: mxr4hxioh4), together with any successor or supplementary analytics tools the Service Provider may deploy upon updating the Privacy Policy.

• “Session Recording” technology that captures interaction data—including clicks, scroll behaviour, pointer movement, and page composition—for replay and heatmap analysis, as implemented through Microsoft Clarity and analogous services.

• “Telemetry” automated collection of usage metrics, diagnostic events, performance data, and interaction signals across Digital Properties for operational monitoring, product analytics, and quality assurance.

• “Feedback” suggestions, bug reports, or improvement ideas submitted regarding the Digital Properties.

• “Services” signifies the aggregate of functionalities, capabilities, features, and operational affordances made available to the User through the Digital Properties.

• “Subscription” means any recurring or time-limited paid access plan, premium tier, or in-application purchase offering, where and when such offerings are made available.

• “Third-Party Service” means any service, platform, library, payment processor, analytics provider, hosting provider, or content source not owned or controlled by the Service Provider but integrated with or accessible through the Digital Properties.

• “User Data” denotes any information, content, files, or material submitted, uploaded, transmitted, stored, or otherwise furnished by the User through the Digital Properties, the processing of which is governed by the Privacy Policy.

• “User-Generated Content” means any content created, submitted, posted, or transmitted by the User through interactive features of the Digital Properties.

• “Open Source Software” or “OSS” means software whose source code is made publicly available under a licence approved by the Open Source Initiative (OSI) or widely recognised as open source, including the MIT Licence, Apache Licence 2.0, BSD Licences, and GNU General Public Licence (GPL) family licences.

• “MIT Licence” means the Massachusetts Institute of Technology permissive licence template, permitting free use, modification, and distribution subject to inclusion of the copyright notice and licence text, and disclaiming warranties.

• “Product Licence” means the open source or proprietary licence under which a specific Digital Property’s source code is published, as identified in the LICENSE, LICENCE, or COPYING file in the corresponding source repository or product documentation.

• “Copyleft Licence” means an open source licence (such as GPL or AGPL) requiring derivative works distributed in certain forms to be licensed under the same or compatible terms.

• “Intellectual Property” patents, copyrights, trade marks, trade secrets, designs, database rights, and analogous protections.

• “Personal Data” information about identifiable individuals, as defined under applicable data protection law.

• “Product-Specific Terms” additional terms for a specific Application or service, incorporated by reference.

• “Prohibited Content” content violating Article 7 or applicable law.

• “Force Majeure Event” events beyond reasonable control, including natural disasters, war, epidemic, governmental acts, and infrastructure failures not caused by negligence.

Article 2 — Formation, Acceptance, and Eligibility

2.1 Contractual Formation

The User’s engagement with the Digital Properties constitutes an affirmative act of assent sufficient to establish a legally enforceable contractual relationship under applicable principles of contract law.

Electronic acceptance is expressly contemplated and shall be of equivalent force to written signature where permitted by law, including under the Information Technology Act, 2000 (India) and analogous statutes in other jurisdictions.

2.2 Deemed Acceptance Through Conduct

Acceptance may be inferred from conduct including browsing beyond a landing page, Account creation, Application download, activation of an “I Agree” control, or continued use after notice of amended Terms.

The User bears responsibility for ensuring that anyone accessing the Digital Properties through the User’s device or Account also complies with this Agreement.

2.3 Representations Regarding Capacity

The User represents that they possess full legal capacity; have attained sixteen (16) years or the minimum age required by law; and, where accepting for an entity, hold authority to bind that entity.

Use by minors above the minimum age should occur only with appropriate parental or guardian supervision where required by law.

2.4 Prohibition on Use by Ineligible Persons

The Service Provider may refuse or terminate access for Users who fail eligibility requirements or supply false registration information.

2.5 No Reliance on External Representations

The User has not relied upon oral statements, informal communications, or marketing hyperbole not expressly reflected in this Agreement or the Privacy Policy.

2.6 Dissent, Non-Acceptance, and Mandatory Exit

(a) Access to the Digital Properties is voluntary and conditional upon acceptance of this Agreement in its entirety.

(b) If the User does not fully and unequivocally agree to each provision herein—including disclaimers, limitations of liability, analytics processing, open source licence cross-references, and governing law—they must not access or use any Digital Property and must immediately exit all CodeFryDev websites and Applications.

(c) Entertainment, amusement, curiosity, or casual browsing do not exempt the User from these Terms. If content, functionality, analytics, or legal conditions are not to the User’s liking, the appropriate and only permitted response is immediate cessation of use.

(d) The User shall not circumvent dissatisfaction by continued use whilst professing non-acceptance; such conduct shall be interpreted as binding assent to the fullest extent permitted by law.

(e) Parents and guardians who do not accept these Terms on behalf of minors under their supervision must ensure such minors do not access the Digital Properties.

Article 3 — Scope, Classification, and Nature of the Services

3.1 Comprehensive Application

This Agreement applies to all present and future Digital Properties unless displaced by a separate written instrument.

3.2 Classification of Offerings

Offerings may include informational websites, utility Applications, APIs, documentation portals, and experimental services described on product pages or in Terms of Use.

3.3 Gratuitous and Remunerated Provision

Services are generally gratuitous unless otherwise stated. The Service Provider may introduce fees, Subscriptions, or premium tiers with prior notice where required.

3.4 Absence of Fiduciary Relationship

No partnership, agency, fiduciary, franchise, or employment relationship is created.

3.5 No Binding Roadmap Commitments

Roadmaps and previews are aspirational and not binding delivery commitments unless set out in a signed agreement.

3.6 Portfolio Modifications

The Service Provider may add, modify, consolidate, or retire Digital Properties subject to mandatory law.

Article 4 — Licence Grant, Reservation of Rights, and Restrictions

4.1 Limited, Revocable Licence

Subject to compliance, the Service Provider grants a limited, non-exclusive, non-transferable, non-sublicensable, revocable licence for intended personal or authorised internal business use.

4.2 Commercial Use Restrictions

Commercial exploitation, resale, sublicensing, or use as part of a competing paid offering requires separate written authorisation.

4.3 Reservation of Rights

All rights not expressly granted are reserved to the Service Provider and its licensors.

4.4 Copying and Derivative Works

Copying, distribution, public display, and derivative works are prohibited except as permitted by mandatory law or express written consent.

4.5 Reverse Engineering

Reverse engineering, decompilation, and disassembly are prohibited except to the limited extent non-waivable under applicable law.

4.6 Circumvention of Security

Bypassing authentication, rate limits, DRM, or access controls is prohibited.

4.7 Automated Access

Bots, scrapers, and bulk extractors require prior written permission unless permitted by robots.txt and law.

4.8 Proprietary Notices

Legal notices and attribution may not be removed or obscured.

4.9 Permitted Ordinary Use and Material Modifications

(a) Ordinary Use Contemplated. The Service Provider expressly contemplates and welcomes ordinary, good-faith utilisation of the Digital Properties within their intended design parameters—browsing, playing, converting, experimenting, learning, or otherwise employing the Services for their intrinsic purpose without alteration of identity, branding, or core attribution. Such “as-is” engagement, conducted in compliance with this Agreement, requires no separate licence, fee, or prior approval.

(b) Material Modifications Distinguished. Notwithstanding permissive open source licences applicable to source code, material modifications—including, without limitation, substantive rebranding, removal or obscuration of proprietary notices, passing off modified works as official CodeFryDev products, redistribution under confusingly similar names or trade dress, injection of malicious or deceptive functionality, or deployment in manners that cause or foreseeably risk consumer confusion, reputational harm, or safety endangerment—fall outside the scope of ordinary use and may constitute a breach of this Agreement, infringement of intellectual property, or violation of trade mark and unfair competition law.

(c) Reservation of Remedies. Where a User or third party effects major modifications of any Digital Property, derivative work, or associated branding in a manner inconsistent with Sections 4.9(a)–(b), Article 29, Article 49, or the Trade Mark & Brand Usage Guidelines , the Service Provider expressly reserves the right to pursue all available legal and equitable remedies, including, without limitation, injunctive relief, takedown demands, account termination, DMCA notice-and-takedown, trade mark opposition or cancellation proceedings, civil claims for damages, and referral to competent law enforcement authorities where warranted.

(d) No Waiver Through Permissive Licensing. Nothing in the MIT Licence, any other Product Licence, or the present Article shall be construed as waiving the Service Provider’s right to enforce trade mark, passing off, misrepresentation, and unfair competition claims against materially modified derivatives that exceed the bounds of ordinary open source redistribution contemplated by the applicable licence.

Article 5 — Account Registration, Credentials, and Security

5.1 Registration Accuracy

Account information must be accurate, current, and complete, and updated upon change.

5.2 Credential Security

The User must safeguard credentials and use strong, unique passwords.

5.3 Account Activity

The User is responsible for activity under the Account except where caused by the Service Provider’s gross negligence.

5.4 Breach Notification

Suspected unauthorised access must be reported promptly to codefrydev@gmail.com .

5.5 Suspension for Investigation

Accounts may be suspended to investigate security incidents or suspected violations.

5.6 Non-Transferability

Accounts may not be sold, shared, or transferred without authorisation.

Article 6 — User Obligations and Standards of Conduct

6.1 Lawful Use

The User shall comply with all applicable laws, regulations, and industry standards.

6.2 Truthfulness

Submitted information shall not be fraudulent or misleading.

6.3 Cooperation

The User shall reasonably cooperate with abuse investigations and lawful requests.

6.4 Respect for Persons

Harassment, threats, and abuse toward users or personnel are prohibited.

6.5 Export and Sanctions Compliance

The User shall not use the Digital Properties in violation of export controls or sanctions.

6.6 Device Security

The User is responsible for securing devices and networks used for access.

Article 7 — Acceptable Use Policy and Prohibited Conduct

7.1 General Standard

The Digital Properties shall not be used in any manner that violates law, infringes rights, compromises security, or materially interferes with the Services or other users.

7.x Prohibition: Unlawful and Fraudulent Conduct

• Engaging in fraud, identity theft, phishing, or financial crime.

• Money laundering or structuring transactions to evade reporting obligations.

• Trafficking in stolen credentials, accounts, or access tokens.

Violations within the category of Unlawful and Fraudulent Conduct may result in immediate suspension, permanent termination, and referral to law enforcement where appropriate.

7.x Prohibition: Intellectual Property Violations

• Uploading or distributing infringing copies of software, media, or literary works.

• Misusing trade marks, logos, or branding to suggest false affiliation with CodeFryDev.

• Circumventing technological protection measures protecting copyrighted content.

Violations within the category of Intellectual Property Violations may result in immediate suspension, permanent termination, and referral to law enforcement where appropriate.

7.x Prohibition: Security Violations

• Introducing malware, ransomware, spyware, or destructive code.

• Conducting unauthorised vulnerability scans or penetration tests.

• Launching denial-of-service attacks or traffic amplification against infrastructure.

Violations within the category of Security Violations may result in immediate suspension, permanent termination, and referral to law enforcement where appropriate.

7.x Prohibition: Abusive Communications

• Transmitting spam, bulk unsolicited messages, or chain letters.

• Publishing defamatory, harassing, hateful, or threatening content.

• Doxxing or publishing private personal information without lawful basis.

Violations within the category of Abusive Communications may result in immediate suspension, permanent termination, and referral to law enforcement where appropriate.

7.x Prohibition: Platform Abuse

• Creating multiple Accounts to evade enforcement actions.

• Manipulating ratings, reviews, analytics, or referral systems.

• Abusing support channels with frivolous, repetitive, or malicious tickets.

Violations within the category of Platform Abuse may result in immediate suspension, permanent termination, and referral to law enforcement where appropriate.

7.x Prohibition: Data Misuse

• Harvesting personal data of other users without consent and lawful basis.

• Large-scale scraping for competitive intelligence or unauthorised model training.

• Re-identifying anonymised datasets without authorisation.

Violations within the category of Data Misuse may result in immediate suspension, permanent termination, and referral to law enforcement where appropriate.

7.x Prohibition: Technical Interference

• Overloading systems through excessive automated requests.

• Interfering with other users’ sessions or data.

• Exploiting bugs for unauthorised access or advantage rather than responsible disclosure.

Violations within the category of Technical Interference may result in immediate suspension, permanent termination, and referral to law enforcement where appropriate.

Article 8 — User-Generated Content and User Data

8.1 Ownership of User-Generated Content

The User retains ownership of User-Generated Content they create, subject to licences granted herein.

8.2 Licence to the Service Provider

The User grants a worldwide, non-exclusive, royalty-free licence to host, reproduce, adapt, and display User-Generated Content solely to operate and improve the Services, consistent with the Privacy Policy.

8.3 Responsibility for Content

The User is solely responsible for User-Generated Content and its legality, accuracy, and appropriateness.

8.4 Monitoring and Removal

The Service Provider is not obligated to monitor all User-Generated Content but may remove content that violates this Agreement or law.

8.5 No Endorsement

Presence of User-Generated Content does not imply endorsement by the Service Provider.

8.6 Backup Obligations

The User should maintain independent backups of important User Data; the Service Provider does not guarantee permanent retention.

Article 9 — Intellectual Property and Proprietary Rights

9.1 Ownership

All Intellectual Property in the Digital Properties remains the property of the Service Provider or licensors.

9.2 Trade Marks

CodeFryDev names and logos may not be used without prior written consent.

9.3 Feedback Licence

Feedback may be used by the Service Provider without restriction or compensation, unless prohibited by law.

9.4 DMCA and Takedown

Copyright owners may submit infringement notices as described in Article 26.

9.5 Reservation of Enforcement Rights

The Service Provider may pursue civil and criminal remedies for IP violations.

Article 10 — Privacy, Data Protection, and Information Security

10.1 Privacy Policy Incorporation

Personal Data processing is governed by the General Privacy Policy , incorporated by reference.

10.2 Lawful Basis and Consent

Where consent is required, the User provides it through use of relevant features after reviewing applicable disclosures.

10.3 Security Measures

Reasonable safeguards are implemented, but absolute security cannot be guaranteed.

10.4 Data Subject Rights

Requests to exercise data subject rights should be submitted via codefrydev@gmail.com and will be handled per applicable law.

10.5 Cross-Border Processing

Personal Data may be processed in jurisdictions where the Service Provider or processors operate, subject to safeguards required by law.

10.6 Breach Notification

The Service Provider will notify Users and authorities of personal data breaches where legally required.

Article 11 — Third-Party Services, Integrations, and External Links

11.1 Third-Party Terms

Third-Party Services are governed by their own terms and privacy policies.

11.2 No Endorsement

Integration or linking does not constitute endorsement.

11.3 User Discretion

Interactions with third parties are at the User’s sole risk.

11.4 Payment Processors

Where payments are processed by third parties, their terms apply to payment transactions.

Article 12 — Application Programming Interfaces and Developer Terms

12.1 API Access

API access may require keys, registration, or separate developer terms.

12.2 Rate Limits

The Service Provider may impose rate limits and usage quotas.

12.3 Prohibited API Uses

APIs may not be used to build competing services, scrape at scale, or circumvent Application functionality without authorisation.

12.4 Key Confidentiality

API keys must be kept confidential and not embedded in public client-side code where avoidable.

Article 13 — Subscriptions, Billing, and Refunds

13.1 Introduction of Paid Features

Paid features, when offered, will be described at purchase with applicable pricing and renewal terms.

13.2 Taxes

Prices may exclude applicable taxes, which the User is responsible for where required.

13.3 Renewals

Subscriptions may renew automatically unless cancelled in accordance with disclosed procedures.

13.4 Refunds

Refunds are provided only where required by applicable consumer protection law or expressly stated at purchase.

Article 14 — Beta, Preview, and Experimental Features

14.1 As-Is Provision

Beta Features are provided as-is, may contain defects, and may change or be withdrawn without notice.

14.2 Feedback Expectation

Users of Beta Features may be encouraged to provide Feedback but are not obligated unless under a separate beta agreement.

14.3 No Production Reliance

Beta Features should not be relied upon for mission-critical or life-critical purposes.

Article 15 — Service Availability, Maintenance, and Support

15.1 Availability Target

The Service Provider aspires to high availability but does not guarantee uninterrupted access.

15.2 Maintenance Windows

Scheduled maintenance may temporarily affect availability; reasonable efforts will be made to minimise disruption.

15.3 Support Channels

Support is provided via published channels and email; no specific response time is guaranteed unless under a paid support agreement.

15.4 Force Majeure

Availability may be affected by Force Majeure Events as defined in Article 21.

Article 16 — Software Updates, Patches, and Compatibility

16.1 Updates

Updates may be required for security, compatibility, or functionality.

16.2 End of Support

Older versions may cease to be supported; continued use of unsupported versions is at the User’s risk.

16.3 Automatic Updates

Applications may update automatically depending on device settings and platform policies.

Article 17 — Disclaimers and Exclusion of Warranties

17.1 As-Is Basis

TO THE FULLEST EXTENT PERMITTED BY LAW, THE DIGITAL PROPERTIES ARE PROVIDED “AS IS” AND “AS AVAILABLE” WITHOUT WARRANTIES OF ANY KIND.

17.2 Implied Warranties

All implied warranties including merchantability, fitness for a particular purpose, and non-infringement are disclaimed.

17.3 Informational Content

Content is for general information and not professional advice.

17.4 Third-Party Accuracy

The Service Provider does not warrant accuracy of third-party information.

Article 18 — Limitation of Liability

18.1 Exclusion of Indirect Damages

THE SERVICE PROVIDER SHALL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES.

18.2 Cap on Liability

Aggregate liability shall not exceed the greater of amounts paid in the twelve (12) months preceding the claim or INR 100, except where liability cannot be limited by law.

18.3 Jurisdictional Variations

Limitations apply to the fullest extent permitted in each jurisdiction.

Article 19 — Indemnification

19.1 User Indemnity

The User shall indemnify the Service Provider against claims arising from misuse, violations, infringement, or User Data.

19.2 Defence Control

The Service Provider may assume exclusive defence of indemnified matters; the User shall cooperate.

Article 20 — Termination, Suspension, and Survival

20.1 Termination by User

The User may terminate by ceasing use and deleting Accounts and Applications.

20.2 Termination by Service Provider

Access may be suspended or terminated for violations, security risks, or discontinuance of Services.

20.3 Effect of Termination

Licences cease; surviving provisions include IP, disclaimers, liability limits, indemnity, and governing law.

20.4 Data Retention Post-Termination

Personal Data retention after termination follows the Privacy Policy and applicable law.

Article 21 — Force Majeure

21.1 Excused Performance

Neither party is liable for failure or delay due to Force Majeure Events beyond reasonable control.

21.2 Mitigation

The affected party shall use reasonable efforts to mitigate impact and resume performance.

21.3 Termination Right

If a Force Majeure Event continues for an extended period, either party may terminate affected Services where permitted by law.

Article 22 — Export Controls, Sanctions, and Geographic Restrictions

22.1 Compliance

The User shall comply with applicable export control and sanctions laws of India, the United States, the European Union, and other relevant jurisdictions.

22.2 Restricted Persons

Use is prohibited by persons on applicable denied-party or sanctions lists.

22.3 Geographic Limitations

The Service Provider may restrict access from certain territories for legal or operational reasons.

Article 23 — Children, Minors, and Age-Restricted Services

23.1 Minimum Age

Users must meet minimum age requirements stated in Article 2.

23.2 Parental Consent

Where required, verifiable parental consent must be obtained for minors.

23.3 No Knowing Collection

The Service Provider does not knowingly collect Personal Data from children below applicable thresholds in violation of law.

Article 24 — International Users and Cross-Border Transfers

24.1 Global Access

Digital Properties may be accessed internationally; local laws may impose additional obligations on Users.

24.2 Language

The English version of this Agreement is authoritative unless a translated version is expressly designated as controlling in a jurisdiction.

24.3 Local Law Conflicts

If a provision is unenforceable in a jurisdiction, it shall be modified minimally to be enforceable.

Article 25 — Electronic Communications and E-Signatures

25.1 Consent to Electronic Communications

The User consents to receive communications electronically, including notices and disclosures.

25.2 Legal Effect

Electronic records and signatures satisfy legal writing requirements where permitted.

Article 26 — Copyright Complaints and Intellectual Property Notices

26.1 Designated Contact

Copyright complaints may be sent to codefrydev@gmail.com with subject “Copyright Notice” including identification of the work, infringing material, contact information, and a good-faith statement.

26.2 Repeat Infringers

Accounts of repeat infringers may be terminated.

26.3 Counter-Notification

Where applicable law provides counter-notification procedures, the Service Provider will describe them upon request.

Article 27 — Feedback, Suggestions, and Improvements

27.1 Voluntary Feedback

Feedback is voluntary and may be used without obligation or compensation unless agreed otherwise in writing.

27.2 No Confidentiality Expectation

Feedback is not considered Confidential Information unless covered by a separate NDA.

Article 28 — Publicity and Use of Name

28.1 No Endorsement

Users may not imply endorsement or partnership without written consent.

28.2 Service Provider Publicity

The Service Provider may list generic customer categories or logos only pursuant to separate publicity agreements.

Article 29 — Open Source Software, Licences, and Source Code

29.1 Open Source Portfolio

A substantial portion of the CodeFryDev Ecosystem consists of Open Source Software projects. Many products—including developer tools, games, design utilities, educational applications, and AI experiments—publish source code under permissive licences, most commonly the MIT Licence, unless a different licence is expressly identified in the product repository or documentation.

The Service Provider embraces open source as a development philosophy whilst maintaining hosted services, branding, analytics, and certain proprietary platform components under this Agreement.

29.2 Dual-Layer Legal Framework

Users must distinguish between two complementary legal layers:

Using the hosted website does not automatically grant rights beyond the Product Licence when you download or fork source code, and possessing MIT-licensed source code does not exempt you from this Agreement when using the hosted deployment.

29.3 MIT Licence — Standard Terms Summary

Where a product’s LICENSE file specifies the MIT Licence, the following permissions and conditions apply to source code (summarised for convenience; the canonical licence text in the repository prevails):

Permissions: use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software.

Conditions: include the original copyright notice and MIT Licence text in all copies or substantial portions.

Limitations: the software is provided “AS IS”, without warranty of any kind; authors are not liable for claims or damages.

The MIT Licence does not grant permission to use the CodeFryDev trade name, logo, or official hosted infrastructure as an implied endorsement.

29.4 Other Open Source Licences

Individual products or dependencies may use licences other than MIT, including Apache Licence 2.0, BSD 2-Clause / 3-Clause, GNU GPL / LGPL / AGPL, and Creative Commons for documentation or assets. The User must review each product’s licence files and dependency manifests before redistribution or commercial embedding.

29.5 Copyleft Compliance

Where a product incorporates or is licensed under a Copyleft Licence, the User is solely responsible for compliance with source-offer and licence propagation obligations when distributing derivative works. The Service Provider’s hosted instance at codefrydev.in does not, by itself, trigger your copyleft obligations; distribution of modified binaries or source does.

29.6 Third-Party and Dependency Licences

Open source products frequently bundle dependencies under heterogeneous licences. A product’s root MIT Licence does not override dependency licences. Users forking or vendoring code must comply with all transitive licence obligations.

29.7 Contributions to Open Source Projects

If the Service Provider accepts contributions via pull requests or similar channels, contributors represent they have the right to submit the work; contributions may be licensed under the project licence (typically MIT) unless a separate Contributor Licence Agreement applies.

29.8 Trademarks and Branding

Open source licences do not grant trade mark rights. The names CodeFryDev, product names, logos, and domain names remain the Service Provider’s trade mark property. Forks must not imply official status without written consent.

29.9 Proprietary and Mixed-Licensing Products

Core platform pages, proprietary services, or products without a public LICENSE file remain proprietary notwithstanding OSS components embedded therein. Schedule F identifies typical licensing posture by category; the repository licence file always prevails.

29.10 Attribution and NOTICE Files

Users redistributing open source code must preserve LICENSE, NOTICE, and attribution files and comply with all attribution requirements.

29.11 No Viral Conversion

Use of proprietary hosted services does not convert proprietary components into open source. Hosting MIT-licensed code does not contaminate proprietary infrastructure when copyleft obligations are respected.

29.12 Source Availability and Forking

For MIT-licenced products, the User may fork and modify source independently. The Service Provider does not guarantee maintenance or security patches for third-party forks.

29.13 Ordinary Use, Material Modifications, and Lawful Enforcement

(a) Private and Ordinary Use. Users who merely employ open source code for private study, experimentation, or unmodified personal utility—without public redistribution or brand misappropriation—engage in conduct fully aligned with the open source ethos and require no consent beyond the applicable Product Licence and this Agreement.

(b) Material Modifications and Public Deployment. Users who materially modify CodeFryDev software and release, distribute, commercially offer, or publicly deploy such modifications in any manner that:

(i) retains, imitates, or appropriates official branding, logos, domain names, or trade dress;

(ii) omits required copyright, licence, or attribution notices;

(iii) falsely suggests official endorsement, sponsorship, maintenance, or security stewardship by the Service Provider;

(iv) materially alters security-sensitive behaviour while presenting the work as an authentic Service Provider product; or

(v) otherwise creates a likelihood of confusion among reasonable consumers as to origin, affiliation, or official status,

may face enforcement action by the Service Provider notwithstanding permissive copyright licensing under the MIT or analogous Product Licence.

(c) Copyright Permission Is Not Immunity. Permission to modify source code under an open source licence does not immunise unlawful trade mark misuse, passing off, deceptive trade practices, or breach of this Agreement. The Service Provider may take legal action—including civil proceedings and platform takedown requests—against persons who effect major modifications that exceed the bounds of lawful open source redistribution or that mislead the public regarding the provenance, safety, or official character of the modified work.

Article 30 — Application Marketplace and Platform Terms

30.1 Store Terms

Downloads via Apple App Store, Google Play, or other marketplaces are also subject to store terms.

30.2 Billing Through Stores

In-app purchases through stores are billed by the store operator under its policies.

30.3 Platform Requirements

Applications comply with platform content and technical guidelines where distributed.

Article 31 — Accessibility and Reasonable Accommodations

31.1 Commitment

The Service Provider endeavours to improve accessibility of Digital Properties over time.

31.2 Feedback

Accessibility feedback may be submitted to codefrydev@gmail.com .

Article 32 — Monitoring, Enforcement, and Remedies

32.1 Monitoring Discretion

The Service Provider may monitor use to enforce this Agreement and protect security, without obligation to monitor all activity.

32.2 Remedies

Remedies include warnings, suspension, termination, IP blocking, and legal action.

32.3 Reporting Violations

Violations may be reported to codefrydev@gmail.com .

Article 33 — Compliance, Anti-Corruption, and Ethical Use

33.1 Anti-Bribery

Users shall not offer bribes or improper payments in connection with use of the Digital Properties.

33.2 Ethical Standards

Use for deceptive, exploitative, or unethical purposes is prohibited.

Article 34 — Data Retention, Backup, and Loss of Data

34.1 Retention

Data retention periods are specified in the Privacy Policy and may vary by data category.

34.2 User Backups

Users are responsible for maintaining backups of important User Data.

34.3 No Guarantee Against Loss

The Service Provider is not liable for loss of data except where caused by its gross negligence or as required by law.

Article 35 — Governing Law and Jurisdiction

35.1 Governing Law

This Agreement is governed by the laws of India, excluding conflict-of-law rules.

35.2 Exclusive Jurisdiction

Courts in India have exclusive jurisdiction, subject to mandatory consumer protections.

35.3 Injunctive Relief

The Service Provider may seek injunctive relief in any jurisdiction for IP or security breaches.

Article 36 — Dispute Resolution and Escalation Procedures

36.1 Informal Resolution

Parties shall attempt good-faith informal resolution for thirty (30) days after written notice of a dispute.

36.2 Escalation

Unresolved disputes may be escalated to senior representatives of each party.

36.3 Formal Proceedings

If informal resolution fails, disputes proceed to courts under Article 35.

Article 37 — Amendments, Severability, and Non-Waiver

37.1 Amendments

The Service Provider may amend this Agreement by posting updated Terms with a revised effective date.

37.2 Continued Use

Continued use after amendments constitutes acceptance where permitted by law.

37.3 Severability

Invalid provisions are reformed minimally; remaining provisions survive.

37.4 Non-Waiver

Failure to enforce a provision is not a waiver.

Article 38 — Entire Agreement, Assignment, and Third-Party Rights

38.1 Entire Agreement

This Agreement, the Privacy Policy, and Terms of Use constitute the entire agreement.

38.2 Assignment by User

The User may not assign without consent.

38.3 Assignment by Service Provider

The Service Provider may assign in connection with merger, acquisition, or asset sale.

38.4 Third-Party Beneficiaries

No third-party beneficiaries except as expressly stated.

Article 39 — Language and Translation

39.1 English Controlling

The English text controls in case of translation discrepancies unless local law requires otherwise.

Article 40 — Notices and Correspondence

40.1 Contact

Notices to the Service Provider: CodeFryDev, codefrydev@gmail.com .

40.2 Email Notice

Email notices are effective upon successful transmission absent evidence of non-delivery.

Article 41 — Miscellaneous Provisions

41.1 Independent Contractors

Parties are independent contractors.

41.2 No Third-Party Rights

Except Affiliates enforcing IP rights, no third party may enforce this Agreement.

41.3 Headings

Headings do not affect interpretation.

41.4 Counterparts

Electronic counterparts are valid.

41.5 Further Assurances

Parties shall execute further documents reasonably required to give effect to this Agreement.

Article 42 — Effective Date and Version History

42.1 Effective Date

These Terms are effective 24 May 2026.

42.2 Version

Version 2.0 — Comprehensive Master Agreement.

Schedule A — Illustrative List of Prohibited Uses (Non-Exhaustive)

This Schedule supplements Article 7. The following illustrative examples do not limit the generality of prohibited conduct described elsewhere in this Agreement.

1. Attempting unauthorised access to infrastructure, Accounts, or administrative interfaces.

2. Using the Services to distribute pirated software, media, or counterfeit goods.

3. Operating botnets, cryptomining malware, or command-and-control infrastructure.

4. Conducting social engineering attacks against other users or staff.

5. Publishing content that violates applicable obscenity, hate speech, or harassment laws.

6. Using geo-evasion tools to access Services from embargoed territories where prohibited.

7. Reselling API access or Account credentials on secondary markets.

8. Automated creation of Accounts for promotional spam or fake engagement.

9. Deep-linking to bypass paywalls or authentication where prohibited.

10. Reverse engineering authentication tokens or session management schemes.

11. Uploading content containing active exploits targeting users or infrastructure.

12. Using the Digital Properties to stalk, surveil, or unlawfully monitor individuals.

13. Falsifying geolocation, device identifiers, or telemetry to commit fraud.

14. Interfering with disaster recovery, backup, or logging systems.

15. Publishing others’ trade secrets or confidential information without authority.

Schedule B — Regulatory and Compliance Reference Framework

This Schedule summarises regulatory contexts that may apply to use of the Digital Properties. It is informational and does not constitute legal advice.

India — Digital Personal Data Protection Act, 2023

Governs processing of digital personal data in India; Users processing personal data must comply with their independent obligations as data fiduciaries or processors.

India — Information Technology Act, 2000

Establishes intermediary liability framework and electronic record validity; Users must not transmit prohibited content under applicable rules.

India — Consumer Protection Act, 2019

May confer mandatory consumer rights for gratuitous and paid digital offerings that cannot be waived where prohibited.

India — Copyright Act, 1957

Protects literary and software works; infringement notices handled under Article 26.

European Union — GDPR

May apply to Users or processing involving EU data subjects; Privacy Policy describes applicable practices.

United States — COPPA

Restricts collection from children under 13; Applications directed at children require dedicated compliance review.

Application Store Policies

Apple App Store Review Guidelines and Google Play Developer Program Policies impose additional distribution requirements.

Schedule C — Operational Expectations and Service Limitations

Content Accuracy

While the Service Provider strives for accuracy, informational content may contain errors or become outdated; Users should verify critical information independently.

Third-Party Outages

Failures of cloud providers, CDNs, DNS, or telecommunications networks may affect availability without constituting breach.

Security Incidents

The Service Provider will respond to confirmed security incidents using commercially reasonable procedures but cannot guarantee prevention of all attacks.

Feature Deprecation

Features may be deprecated with or without notice; dependent workflows should include contingency planning.

Localisation

Services may not be fully localised in all languages or regions; English is the primary language of operation unless otherwise stated.

Hardware Dependencies

Mobile Applications depend on device hardware sensors, notifications permissions, and OS policies outside the Service Provider’s control.

Backup and Export

Where export tools exist, Users should periodically export important data; not all Services provide export functionality.

Community Standards

Future community features, if introduced, will be subject to additional community guidelines incorporated by reference.

Schedule D — Definitions of Key Legal and Technical Concepts

Personal Data

Information relating to an identified or identifiable natural person, including identifiers such as name, email, IP address, device ID, and online identifiers when linkable to an individual.

Processing

Any operation performed on Personal Data, including collection, storage, use, disclosure, erasure, or destruction.

Anonymisation

Irreversible transformation such that the data subject is no longer identifiable, subject to reasonable re-identification risk analysis.

Encryption in Transit

Use of TLS or equivalent protocols to protect data during network transmission, reducing interception risk but not eliminating endpoint compromise.

Authentication

Verification of identity through credentials, tokens, biometrics, or multi-factor mechanisms prior to granting access.

Authorisation

Determination of permitted actions after authentication, enforced through access controls and policy engines.

Rate Limiting

Technical throttling of requests to preserve stability and prevent abuse.

Session Management

Creation, maintenance, and termination of authenticated sessions, including timeout and revocation.

Telemetry

Operational metrics and diagnostic events collected to monitor performance, crashes, and usage patterns, often in aggregated form.

Subprocessor

Third party engaged by the Service Provider to process Personal Data on its behalf, as described in the Privacy Policy.

Article 43 — Analytics, Telemetry, and Behavioural Measurement

43.1 Uniform Deployment Across the Ecosystem

The Service Provider deploys Analytics Services consistently across the CodeFryDev Ecosystem to understand how Users interact with each Digital Property, to diagnose defects, to optimise user experience, and to prioritise development investment across its product portfolio. By accessing any Digital Property—whether a single utility such as JsonPlayground or a game such as Snake—you acknowledge that Analytics Services may be active for that session.

This Article applies cross-product: analytics configuration is shared at the platform level unless a specific product’s Terms of Use or Privacy Policy expressly describes additional or alternative measurement practices.

43.2 Google Analytics

The Service Provider utilises Google Analytics (Google tag / gtag.js; Measurement ID G-VM01Q3R43D) to collect statistical information regarding visits, traffic sources, page views, session duration, device categories, browser types, geographic regions (derived from IP address), and conversion-related events.

Google Analytics operates as a Subprocessor under Google’s terms and privacy policies. Data collected may be processed on servers located outside your country of residence. The Service Provider configures Analytics for legitimate interest in product improvement and, where required, relies upon consent obtained through your continued use of the Digital Properties after reviewing the Privacy Policy .

You may learn about Google’s practices at https://policies.google.com/privacy and may install Google’s opt-out browser add-on or adjust ad/analytics preferences made available by Google.

43.3 Microsoft Clarity

The Service Provider utilises Microsoft Clarity (Project ID mxr4hxioh4) to capture Session Recording data, heatmaps, rage-click indicators, dead-click analysis, and scroll-depth metrics. Clarity may record interactions with page elements, pointer movement patterns, and page rendering characteristics sufficient to generate session replays for internal UX review.

Clarity is intended for product improvement and defect identification, not for capturing deliberately entered sensitive credentials. Nevertheless, Users are cautioned not to enter passwords, payment card numbers, government identifiers, or other highly sensitive Personal Data into any Digital Property whilst Session Recording is active, as such data could inadvertently appear in recordings accessible to authorised Service Provider personnel.

Microsoft processes Clarity data under its privacy terms at https://privacy.microsoft.com . Clarity operates as a Subprocessor.

43.4 Lawful Purposes of Analytics Processing

Analytics and Telemetry collected across the CodeFryDev Ecosystem are processed for the following purposes, without limitation:

(a) measuring aggregate and per-product traffic, engagement, and retention;

(b) comparing performance across tools, games, and utilities to guide maintenance priorities;

(c) identifying UI friction, errors, crashes, and anomalous interaction patterns;

(d) evaluating the effectiveness of new features, layouts, and onboarding flows;

(e) detecting abuse, bot traffic, and security-relevant anomalies;

(f) producing internal reports for the Service Provider’s development team; and

(g) supporting compliance with this Agreement through audit trails of access patterns where appropriate.

Analytics data is not used to make solely automated decisions producing legal or similarly significant effects concerning Users, unless expressly disclosed for a specific product feature.

43.5 Cross-Product and Cross-Session Correlation

Because Analytics Services are deployed at the platform level under a shared Measurement ID and Clarity project, the Service Provider may correlate your interactions across multiple Digital Properties visited within the same browser session or through persistent identifiers (such as cookies or local storage) where permitted by applicable law. For example, navigation from the main portal to a game, then to a developer tool, may appear as a connected journey in analytics dashboards.

This cross-product visibility enables the Service Provider to understand the Ecosystem holistically rather than as isolated silos, and constitutes a material term of use for all Digital Properties.

43.6 Cookies, Local Storage, and Similar Technologies

Analytics Services rely upon cookies, local storage, pixels, and comparable tracking technologies to persist identifiers and session state. By using the Digital Properties, you consent to such technologies to the extent consent is required in your jurisdiction, in addition to strictly necessary technologies required for basic functionality (e.g. theme preferences, session authentication).

Further detail regarding cookie categories and retention is provided in the Privacy Policy .

43.7 Data Minimisation and Retention

The Service Provider configures Analytics Services to collect data proportionate to stated purposes and retains analytics datasets according to vendor default retention periods or shorter internal retention schedules where configurable. Aggregated statistics may be retained indefinitely for historical trend analysis.

Individual Session Recordings are accessed only by authorised personnel with a legitimate need and are not published publicly unless anonymised beyond reasonable re-identification risk.

43.8 User Choices and Limitations

You may reduce analytics collection by:

(a) configuring browser settings to block or delete cookies;

(b) enabling “Do Not Track” or Global Privacy Control signals where the Service Provider honours such signals for applicable products;

(c) using vendor-provided opt-out tools for Google Analytics;

(d) discontinuing use of the Digital Properties; or

(e) contacting codefrydev@gmail.com with analytics-related privacy requests, subject to verification and applicable law.

Blocking analytics technologies may degrade certain features or prevent the Service Provider from diagnosing errors you report.

43.9 Relationship to the Privacy Policy

Matters concerning legal bases for processing, data subject rights, international transfers, and subprocessors are elaborated in the Privacy Policy . This Article establishes your contractual acknowledgment that Analytics Services are integral to the operation and improvement of the CodeFryDev Ecosystem.

43.10 Changes to Analytics Configuration

The Service Provider may change Analytics Service providers, measurement identifiers, or deployment scope upon updating the Privacy Policy and, where material, providing reasonable notice. Continued use after such changes constitutes acceptance to the extent permitted by law.

Article 44 — Product Portfolio and Ecosystem-Wide Application

44.1 Single Agreement, Many Products

The CodeFryDev Ecosystem is a multi-product platform. Each tool, game, utility, or application listed in Schedule E—or published subsequently at a codefrydev.in URL—is governed by this Agreement unless superseded by a signed enterprise contract or a Product Terms.

Users are not required to accept separate terms for each product individually; acceptance of this Agreement upon first use of any Digital Property extends to all present and future Ecosystem products unless you discontinue use entirely.

44.2 Product Categories

Schedule E organises the Ecosystem into categories for clarity. Category assignment does not limit the applicability of this Agreement, Article 43 (Analytics), or the Privacy Policy.

44.3 New Products

Products added to codefrydev.in after the Effective Date—including those appearing in the site map —are automatically covered without requiring re-acceptance, subject to amendment procedures in Article 37.

44.4 Product Termss

Where a product presents materially distinct risks or data practices—such as mobile Applications accessing device sensors—Terms of Use may be published in this repository. Product Terms add to rather than replace this Agreement and Article 43 unless explicitly stated.

Schedule E — CodeFryDev Ecosystem Product Catalogue

This Schedule identifies Digital Properties within the CodeFryDev Ecosystem as referenced in the CodeFryDev site map . Each product listed below has its own Terms of Use page organised by category:

The catalogue below is illustrative; the category index pages contain direct links to every product’s Terms.

Analytics Notice: Unless a product-specific Privacy Policy states otherwise, Google Analytics (G-VM01Q3R43D) and Microsoft Clarity (mxr4hxioh4) are deployed across web-based properties in this catalogue.

E.1 Core Platform and Informational Properties

E.2 Artificial Intelligence and Prompt Tools

E.3 Developer Tools, Utilities, and Productivity Applications

E.4 Design, Creative, and Media Tools

E.5 Educational and Learning Tools

E.6 Games and Interactive Entertainment

E.7 Hardware, Embedded, and Specialised Tools

E.8 Mobile Applications

Mobile Applications may employ platform-native analytics SDKs in addition to, or instead of, web-based Google Analytics and Microsoft Clarity, as described in applicable Privacy Policies.

E.9 Successor Products

Any product added to the CodeFryDev Ecosystem after publication of this Schedule—including entries subsequently added to codefrydev.in/sitemap.xml —is governed by this Agreement and Article 43 from the date of public availability.

Schedule F — Open Source Licensing by Product Category

This Schedule describes the typical open source licensing posture for products in each category. The LICENSE file in the product’s source repository always prevails over this Schedule in case of any inconsistency.

F.1 MIT Licence Obligations for Developers

Persons who clone, fork, or redistribute CodeFryDev MIT-licenced source code must:

1. retain the copyright notice and MIT Licence text;
2. document material modifications where appropriate;
3. comply with dependency licences specified in package.json, go.mod, or equivalent manifest files;
4. refrain from employing CodeFryDev trade marks in a manner suggesting official affiliation of the derivative work; and
5. accept the software “AS IS”, without warranty from the Service Provider.

F.2 Finding the Product Licence

Each open source product’s licence is located in:

• the root LICENSE or LICENCE file of its GitHub or Git repository;
• an in-app “About”, “Licences”, or “Open Source” notice where implemented; or
• the Product’s Terms of Use page under Open Source Licence section.

F.3 Permitted Uses Under MIT (Source Code)

Subject to the MIT Licence and third-party dependency terms, the User may:

• employ the code for commercial purposes;
• modify and create derivative works;
• distribute original or modified code;
• grant sublicences; and
• utilise the code privately without obligation to contribute modifications upstream.

Hosted use at codefrydev.in remains subject to this Agreement, Article 43 (Analytics), and the Privacy Policy regardless of MIT source availability.

F.4 Ordinary Use Versus Major Modifications

The User may utilise CodeFryDev products in their ordinary, intended manner—encompassing recreational play, data conversion, experimentation, and personal or internal commercial utility—subject to this Agreement.

Where the User materially modifies source code and redistributes or publicly offers the result, the User must comply with the Product Licence and ensure the modification does not impersonate, dilute, or engender confusion with official CodeFryDev offerings. Major modifications that mislead reasonable consumers into believing they are accessing an official product may expose the modifier to legal action, including trade mark enforcement and claims for unfair competition or passing off, notwithstanding MIT copyright permissions.

Article 45 — Code of Conduct and Community Participation

45.1 Applicability

Participation in CodeFryDev open source repositories, issue trackers, discussion forums, and community channels is governed by the Community Code of Conduct Instrument , incorporated herein by reference.

45.2 Enforcement

Violations may result in removal of contributions, temporary restriction, or permanent ban from community spaces, in addition to remedies under this Agreement.

45.3 No Harassment

The Service Provider maintains zero tolerance for harassment, discrimination, or abusive conduct toward users, contributors, or personnel.

Article 46 — Responsible Security Disclosure

46.1 Reporting Vulnerabilities

Security vulnerabilities should be reported in accordance with the Security and Responsible Disclosure Policy Policy . Public disclosure before coordination may forfeit safe-harbour protections.

46.2 Prohibited Testing

Unauthorised penetration testing, denial-of-service attacks, or exploitation of discovered vulnerabilities beyond proof-of-concept is prohibited.

46.3 Open Source Dependencies

Users and researchers discovering vulnerabilities in bundled dependencies are encouraged to report upstream and notify CodeFryDev where our products are affected.

Article 47 — Artificial Intelligence: Models, Outputs, and Limitations

47.1 Non-Reliance on AI Outputs

AI-enabled Digital Properties may generate text, code, images, recommendations, or other outputs that are probabilistic, incomplete, or incorrect. Outputs do not constitute professional advice and must be independently verified.

47.2 User Responsibility for Prompts and Outputs

The User is solely responsible for prompts submitted and for any use, publication, or deployment of AI-generated outputs, including compliance with law and third-party rights.

47.3 Third-Party Models and APIs

AI features may rely on third-party model providers. Their terms and privacy policies apply to inference processing. Model availability may change without notice.

47.4 No Training Guarantee

Unless expressly stated in a product Privacy Policy, User Data submitted through general tools is not sold for third-party AI training. Analytics data is used for product improvement as described in Article 43 and the Privacy Policy.

47.5 High-Risk Use Prohibited

AI outputs must not be used as the sole basis for medical diagnosis, legal decisions, financial transactions, safety-critical systems, or autonomous weapons without qualified human oversight and domain-specific compliance review.

Article 48 — Emergency, Safety-Critical, and Prohibited High-Risk Uses

48.1 No Emergency Services

Digital Properties are not a substitute for emergency services. The User must not rely upon any CodeFryDev product for emergency communication, medical triage, or life-safety determinations.

48.2 Safety-Critical Systems

The User shall not deploy Digital Properties or open source code in safety-critical environments—including medical life support, aviation navigation, nuclear facilities, or autonomous vehicles—where failure could cause death or serious injury, unless independently validated and licensed for such use.

48.3 Health and Wellness Tools

Hydration reminders, wellness games, and informational utilities are not medical devices and do not provide clinical advice.

Article 49 — Trade Marks, Logos, and Brand Assets

49.1 Reserved Rights

CodeFryDev, product names, logos, and trade dress are protected. MIT and other open source licences do not grant trade mark rights.

49.2 Permitted Reference

The User may truthfully represent that a derivative work is “based on” or “forked from” a CodeFryDev project provided that no impression of official endorsement is created.

49.3 Prohibited Uses

The User must not employ CodeFryDev branding upon modified forks, merchandise, or competing services absent express written permission. The User must not register domain names or social media handles that are confusingly similar to CodeFryDev marks.

49.4 Ordinary Use Versus Major Modifications

(a) Unmodified Ordinary Use. Accessing, playing, converting, or otherwise using CodeFryDev Digital Properties in their ordinary, intended manner—without material alteration of branding, identity, or core attribution—is permitted subject to this Agreement and requires no separate trade mark licence.

(b) Major Modifications and Enforcement. Where a User or third party materially modifies a Digital Property or derivative work and distributes, publishes, or deploys it in a manner that associates the modification with CodeFryDev branding, conveys an impression of official origin, or creates consumer confusion, the Service Provider may seek injunctive relief, removal from app stores and code repositories, account termination, and damages, without prejudice to rights under the applicable Product Licence or applicable intellectual property law.

(c) Standing to Enforce. The Service Provider may act against major modifications whether effected by forkers, republishers, or end users who exceed the scope of ordinary personal use, to the fullest extent permitted by law.

Article 50 — Donations, Sponsorship, and Commercial Support

50.1 Gratuitous Services

Most Digital Properties are offered free of charge. Donations or sponsorships, if solicited, are voluntary and non-refundable unless required by law.

50.2 No SLA for Free Tier

Free services are provided without service-level agreements, uptime guarantees, or dedicated support unless under a separate paid contract.

50.3 Enterprise Arrangements

Commercial licences, support contracts, or custom agreements require separate written negotiation.

Article 51 — Communications, Marketing, and Anti-Spam

51.1 Transactional Communications

The Service Provider may send service-related emails or notifications (security alerts, policy updates) as permitted by law.

51.2 Marketing Opt-Out

Where marketing communications are sent, unsubscribe mechanisms will be provided where legally required.

51.3 Anti-Spam Obligations

Users shall not use Digital Properties to harvest emails, send unsolicited bulk messages, or operate spam campaigns.

Article 52 — Robots, Crawlers, and Automated Access

52.1 robots.txt Compliance

Automated agents must respect robots.txt directives and applicable rate limits.

52.2 Prohibited Scraping

Large-scale scraping of content, user data, or APIs for competitive intelligence, dataset construction, or resale is prohibited without written authorisation.

52.3 Search Engine Indexing

Public pages may be indexed by search engines; excluded paths should be configured via robots directives.

Article 53 — Professional Advice Disclaimer

No Digital Property provides legal, medical, financial, tax, or engineering professional advice. Consult qualified professionals. Educational content is for general learning only and is not accredited certification.

Article 54 — Grievance Redressal and Regulatory Contact (India)

54.1 Grievance Officer

In accordance with applicable Information Technology Rules in India, grievances relating to content, privacy, or Terms may be submitted to:

Grievance Officer — CodeFryDev
Email: codefrydev@gmail.com
Subject line: “Grievance – [Topic]”

54.2 Acknowledgement

The Service Provider shall endeavour to acknowledge grievances within twenty-four (24) hours and resolve eligible matters within fifteen (15) days, or such other period as mandated by applicable law.

54.3 Escalation

Unresolved grievances may be escalated to relevant regulatory authorities as permitted by law.

Article 55 — Related Policies and Document Index

The following documents form part of the CodeFryDev legal and community framework:

Schedule G — Cookie and Local Storage Categories

See the dedicated Cookie Policy for full detail. Summary:

Schedule H — Regional Privacy Rights Summary

This Schedule summarises rights that may apply based on your location. See the General Privacy Policy for procedures.

Response timeframe: We aim to respond to verified requests within thirty (30) days, extendable where permitted by law.

Schedule I — Open Source Project Norms (GitHub / GitLab Inspired)

CodeFryDev open source projects typically include:

Pull requests may be reviewed at maintainer discretion. Issues should include reproduction steps. Releases may be tagged semver. Security patches prioritised for actively maintained repositories.

Article 56 — Content Moderation and Intermediary Liability

56.1 Intermediary Status

To the extent CodeFryDev qualifies as an intermediary under the Information Technology Act, 2000 (India) and applicable rules, it operates as a platform hosting user-facing tools and informational content subject to statutory due diligence obligations.

56.2 Prohibited Content Removal

The Service Provider may remove, restrict, or disable access to content or Accounts that violate Article 7, applicable law, or valid legal process, with or without prior notice where exigent circumstances require.

56.3 Reporting Unlawful Content

Reports of unlawful or infringing content may be submitted to codefrydev@gmail.com or via the DMCA / Copyright Policy . Include sufficient detail for investigation.

56.4 No General Monitoring Obligation

The Service Provider is not obligated to proactively monitor all User Data or User-Generated Content but may use automated and manual review for security, abuse prevention, and legal compliance.

Article 57 — Downloads, Distribution, and Malware Disclaimer

57.1 Software Downloads

Open source repositories and release artefacts may be downloaded from official sources linked from codefrydev.in or GitHub. Users should verify checksums and signatures where published.

57.2 No Guarantee of Virus-Free Binaries

The Service Provider does not warrant that downloadable files are free from malware, vulnerabilities, or defects. Users should scan downloads with current antivirus tools before execution.

57.3 Unofficial Mirrors

Downloads from third-party mirrors, package registries, or unofficial app stores are at the User’s own risk. Prefer official CodeFryDev sources.

57.4 Package Managers

Community-maintained packages (npm, Homebrew, etc.) may lag behind official releases; verify publisher identity before installation.

Article 58 — Appeals, Reinstatement, and Account Recovery

58.1 Suspension Appeals

Users whose access was suspended or terminated may appeal to codefrydev@gmail.com with subject “Account Appeal”, explaining the basis for reinstatement.

58.2 Reinstatement Discretion

Reinstatement is at the Service Provider’s sole discretion. Good-faith mistakes, first-time minor violations, and remediated security issues may be considered.

58.3 No Guarantee of Restoration

The Service Provider is not obligated to restore deleted data, scores, or configurations after termination.

Article 59 — LLM, Crawler, and Automated Agent Access

59.1 llms.txt and AI Crawlers

CodeFryDev publishes llms.txt and related documentation to guide AI crawlers and language models. Automated access must respect robots.txt, rate limits, and Article 52.

59.2 No Waived Terms for Bots

Automated agents accessing Digital Properties remain bound by this Agreement. Scraping for model training without authorisation is prohibited unless explicitly permitted in llms.txt or a separate licence.

59.3 Attribution

AI systems incorporating CodeFryDev public documentation should attribute the source where technically feasible.

Schedule J — Legal Compliance Checklist (Summary)

Closing Provisions

These General Terms and Conditions of Use, including all Schedules hereto, constitute the master contractual framework for CodeFryDev Digital Properties. Product-Specific Terms modify this Agreement only to the extent expressly stated therein.

For questions regarding interpretation, compliance, or enforcement, contact CodeFryDev at codefrydev@gmail.com .

Disclaimer: This comprehensive instrument is furnished for general informational purposes and does not constitute legal advice. Independent legal counsel should be consulted prior to commercial reliance, regulatory filing, or application marketplace submission.