HACC Gen — API Terms

Effective Date: 12th September 2026
Last Updated: 12th September 2026

These API Terms (“API Terms”) govern access to and use of the HACC Gen Application Programming Interface (“API”) provided by Dynamic Pixel Multimedia Solutions (“Dynamic Pixel”, “HACC Gen”, “we”, “us”, or “our”).

The API is currently made available primarily for integration with HACC Gen-supported Moodle plugins and related integrations. These API Terms apply to any customer, organization, developer, administrator, or other authorized user (“API User”, “you”, or “your”) who accesses or uses the HACC Gen API.

By obtaining API credentials, configuring an HACC Gen integration, or using the API, you agree to these API Terms, the HACC Gen Terms of Service, Acceptable Use Policy, and Privacy Policy.

If there is a conflict between these API Terms and the HACC Gen Terms of Service, these API Terms will control only with respect to API-specific matters. The Terms of Service will otherwise continue to govern your use of HACC Gen.

1. API Access

1.1 Authorization

HACC Gen may provide you with API access subject to your applicable HACC Gen plan, credits, usage limits, subscription or purchase terms, and technical requirements.

API access is a limited, non-exclusive, non-transferable authorization to use the API for legitimate purposes permitted under these API Terms.

1.2 Current API Offering

HACC Gen currently provides API functionality primarily to support HACC Gen Moodle plugins and related integrations.

The API may enable an authorized Moodle installation or other supported integration to communicate with HACC Gen services and access functionality made available through the applicable integration.

HACC Gen may introduce additional API functionality, integrations, endpoints, or supported platforms in the future. These API Terms may apply to such functionality unless separate terms are provided.

1.3 Eligibility

You must have authority to use the HACC Gen account, Moodle installation, organization, or other system for which API access is being configured.

If you are using the API on behalf of an organization, you represent that you have authority to accept these terms on its behalf.

2. API Credentials and Security

2.1 API Credentials

API access may require credentials such as an API Key, API Secret, authentication token, or other credentials issued by HACC Gen.

API credentials are confidential and must be protected from unauthorized access.

2.2 Your Responsibility

You are responsible for:

  • keeping API credentials secure;
  • preventing unauthorized persons from accessing or using your credentials;
  • configuring integrations correctly;
  • restricting access to authorized administrators and systems;
  • promptly notifying HACC Gen if you believe credentials have been compromised; and
  • all API activity conducted using your credentials, except to the extent caused by HACC Gen's own unauthorized actions.

You must not publish API credentials in publicly accessible repositories, websites, documentation, client-side code, forums, or other publicly accessible locations.

2.3 Credential Rotation and Revocation

HACC Gen may require you to replace, rotate, or regenerate API credentials for security, operational, or technical reasons.

HACC Gen may revoke compromised, misused, or otherwise unauthorized credentials.

3. Moodle Plugin Integrations

3.1 Supported Integrations

Where the API is used through an HACC Gen-supported Moodle plugin, you are responsible for maintaining the Moodle environment and ensuring that the plugin is installed and configured appropriately.

3.2 Moodle Environment

You are responsible for:

  • your Moodle installation;
  • Moodle hosting and infrastructure;
  • Moodle administrator accounts and permissions;
  • third-party Moodle plugins and customizations;
  • the security of your Moodle environment; and
  • ensuring that users accessing HACC Gen functionality through Moodle are authorized to do so.
3.3 Plugin Compatibility

HACC Gen may update, modify, replace, or discontinue versions of its Moodle plugins or related API functionality.

HACC Gen does not guarantee that every version of Moodle, third-party plugin, hosting environment, customization, or infrastructure will remain compatible with the API indefinitely.

3.4 Domain Restrictions

Where supported, API credentials may be restricted to an authorized LMS or domain.

You must not attempt to bypass, disable, manipulate, or circumvent such restrictions.

4. API Usage, Credits and Limits

4.1 Plan-Based Access

API access and usage may be subject to the limits and entitlements of your applicable HACC Gen plan.

These may include limits relating to:

  • content generation;
  • text processing;
  • images;
  • audio;
  • video;
  • API requests;
  • storage;
  • processing capacity; or
  • other resources.

The specific allowances applicable to your account are those displayed in the applicable HACC Gen pricing, account, or service documentation.

4.2 Usage-Based Services

Where API usage is provided on a usage-based basis, usage may consume credits or other purchased allowances according to the applicable HACC Gen pricing and service terms.

You are responsible for monitoring your usage and maintaining sufficient credits or entitlement to continue using paid API functionality.

4.3 No Circumvention

You must not attempt to circumvent API limits, credits, authentication requirements, rate limits, domain restrictions, technical controls, or other usage restrictions.

This includes using multiple accounts, credentials, systems, requests, integrations, or technical mechanisms for the purpose of avoiding applicable limits or charges.

4.4 Fair Use

You must use the API in a manner that does not unreasonably interfere with HACC Gen's systems or the availability of the service to other customers.

HACC Gen may apply reasonable technical restrictions where necessary to protect system stability, security, performance, or availability.

5. Permitted Use

Subject to these API Terms, the Terms of Service, and the Acceptable Use Policy, you may use the API to:

  • connect supported Moodle installations or other authorized systems to HACC Gen;
  • access HACC Gen functionality made available through the API;
  • generate or process learning content and related educational materials;
  • support authorized users of your Moodle or other supported integration; and
  • perform other legitimate activities expressly supported by HACC Gen.

Your use must comply with all applicable laws, regulations, contractual obligations, and third-party rights.

6. Prohibited API Use

You must not use the API to:

  • violate applicable law or regulation;
  • infringe intellectual property, privacy, publicity, or other rights;
  • access accounts, systems, data, or services without authorization;
  • interfere with or disrupt HACC Gen systems;
  • introduce malware, malicious code, or harmful content;
  • probe, scan, or test HACC Gen systems for vulnerabilities without authorization;
  • circumvent authentication, rate limits, usage limits, credits, or other technical controls;
  • reverse engineer or attempt to extract the underlying source code, models, algorithms, or proprietary systems;
  • scrape or systematically collect HACC Gen services or outputs except through functionality expressly provided for that purpose;
  • use the API to build a substantially competing service by systematically replicating HACC Gen functionality;
  • use API credentials belonging to another person or organization without authorization;
  • resell or sublicense API access unless expressly authorized by HACC Gen; or
  • otherwise violate the HACC Gen Acceptable Use Policy.

HACC Gen may suspend or terminate API access where it reasonably believes that prohibited activity is occurring.

7. User Content and Data Submitted Through the API

7.1 Your Content

You may submit text, prompts, files, course materials, instructions, media, or other information through an authorized API integration (“User Content”).

You retain your rights in your User Content, subject to the rights necessary for HACC Gen to provide the services.

7.2 Authorization

You are responsible for ensuring that you have all necessary rights, permissions, consents, and legal authority to submit User Content through the API and to permit HACC Gen and its service providers to process that content as necessary to provide the services.

7.3 Personal and Confidential Information

You should not submit personal, confidential, sensitive, or regulated information through the API unless such submission is necessary for your intended use and you have an appropriate legal basis and authorization to do so.

You are responsible for configuring your systems and integrations appropriately to prevent unauthorized disclosure of such information.

7.4 Privacy

Information submitted through the API may be processed in accordance with the HACC Gen Privacy Policy and applicable contractual arrangements.

Where an organization uses HACC Gen on behalf of its users, the organization remains responsible for providing appropriate notices and obtaining any required permissions or consents relating to its users and data.

8. AI Processing and Generated Content

The API may provide access to AI-powered functionality, including content generation, transformation, translation, multimedia generation, summarization, and other processing.

AI-generated output may be inaccurate, incomplete, inappropriate, or unsuitable for a particular purpose.

You are responsible for reviewing and validating API-generated output before using, publishing, distributing, or relying upon it.

HACC Gen does not guarantee that AI-generated output will be unique, accurate, error-free, or suitable for every intended use.

Where the API is used to generate educational content, the API User remains responsible for appropriate instructional, factual, legal, regulatory, and quality review.

9. Third-Party AI and Technology Providers

HACC Gen may use third-party AI models, cloud infrastructure, storage services, media-generation services, translation services, analytics providers, or other technology providers to operate or support API functionality.

Your use of the API authorizes HACC Gen to process User Content and other necessary information through such providers to the extent required to provide the applicable services, subject to the HACC Gen Privacy Policy and applicable contractual terms.

HACC Gen may change or replace third-party technology providers where reasonably necessary to operate, improve, secure, or maintain the services.

10. Intellectual Property

10.1 HACC Gen Technology

The API, its software, documentation, interfaces, architecture, underlying technology, and related intellectual property remain the property of Dynamic Pixel or its licensors.

Except for the limited rights expressly granted under these API Terms and the Terms of Service, no intellectual property rights are transferred to you.

10.2 API Outputs

Subject to applicable law, third-party rights, and the HACC Gen Terms of Service, you may use API-generated output for your permitted business or educational purposes.

You are responsible for determining whether particular output can lawfully be used, published, distributed, or incorporated into your materials.

10.3 Feedback

If you provide suggestions, feedback, or recommendations concerning the API or related integrations, HACC Gen may use that feedback without restriction or compensation, provided that such use does not disclose your confidential information.

11. Commercial Use and Redistribution

Unless otherwise agreed in writing, API access is provided for use within your authorized systems and integrations.

You must not:

  • sell or sublicense API credentials;
  • provide API access to unauthorized third parties;
  • expose the API as an unrestricted public service using your HACC Gen credentials;
  • allow third parties to consume your API entitlement for their own independent purposes; or
  • commercially redistribute HACC Gen API functionality as a standalone service,

unless expressly authorized by HACC Gen in writing.

Use of the API to provide HACC Gen-powered functionality to authorized users of your own Moodle environment is permitted where supported by your applicable plan.

12. API Availability and Changes

HACC Gen will use reasonable efforts to maintain API availability but does not guarantee uninterrupted or error-free API operation.

The API may occasionally be unavailable because of:

  • maintenance;
  • upgrades;
  • security measures;
  • infrastructure failures;
  • third-party service interruptions;
  • network issues;
  • excessive or abusive usage; or
  • circumstances beyond HACC Gen's reasonable control.

HACC Gen may modify, add, remove, or discontinue API endpoints, features, functionality, technical requirements, or supported integrations.

Where reasonably practicable, HACC Gen may provide notice of material changes that are likely to substantially affect continued use of the API.

13. Security and Incident Response

HACC Gen may implement authentication, access controls, monitoring, rate limits, logging, and other reasonable security measures for the API.

You must promptly notify HACC Gen if you become aware of:

  • unauthorized API access;
  • compromised API credentials;
  • suspected security vulnerabilities affecting the API integration;
  • unauthorized access to User Content through the integration; or
  • other security incidents materially affecting your use of the API.

You must cooperate reasonably with HACC Gen in investigating and addressing such incidents.

14. Suspension and Revocation of API Access

HACC Gen may suspend, restrict, or revoke API access where reasonably necessary to:

  • protect the security or availability of HACC Gen systems;
  • address suspected unauthorized or abusive use;
  • prevent violation of these API Terms, the Terms of Service, or AUP;
  • comply with legal or regulatory requirements;
  • address non-payment or exhausted entitlements;
  • protect HACC Gen or other customers from material harm; or
  • address a security incident.

Where reasonably practicable and appropriate, HACC Gen may provide notice before suspension and an opportunity to resolve the issue.

Nothing in this section limits HACC Gen's ability to take immediate action where necessary to protect security, systems, users, or legal interests.

15. Fees, Payment and Taxes

API fees, credits, usage allowances, payment terms, taxes, refunds, and related commercial matters are governed by the applicable HACC Gen pricing and the Terms of Service.

Where API access is purchased on a usage-based basis, usage may be deducted from the applicable credits or allowances associated with your account.

Unless otherwise expressly stated, unused credits or allowances do not create a right to cash redemption or refund.

16. Relationship with Other HACC Gen Policies

Your use of the API is also governed by:

  1. HACC Gen Terms of Service;
  2. HACC Gen Acceptable Use Policy; and
  3. HACC Gen Privacy Policy.

These API Terms supplement those documents and do not replace them.

The Acceptable Use Policy applies to API use in the same manner as it applies to other HACC Gen services.

17. Disclaimer

To the maximum extent permitted by applicable law, the API is provided on an “as available” and “as is” basis.

HACC Gen does not warrant that:

  • the API will always be available;
  • the API will be uninterrupted or error-free;
  • API-generated content will always be accurate or complete;
  • the API will satisfy every particular business or educational requirement;
  • the API will remain compatible with every third-party system or future version of Moodle; or
  • generated content will be free from errors, omissions, or unintended results.

You are responsible for evaluating and reviewing API outputs and ensuring that your implementation is appropriate for your intended use.

18. Limitation of Liability

HACC Gen's liability arising from or relating to API access and use is subject to the limitations and exclusions set out in the HACC Gen Terms of Service.

Nothing in these API Terms creates a separate or greater liability obligation beyond the limitations applicable under the Terms of Service, except where such limitation is prohibited by applicable law.

19. Indemnification

Your indemnification obligations relating to API use are governed by the HACC Gen Terms of Service.

You remain responsible for claims arising from your unlawful use of the API, unauthorized access, violation of third-party rights, misuse of User Content, or violation of these API Terms.

20. Changes to These API Terms

HACC Gen may update these API Terms from time to time.

If we make material changes, we may provide reasonable notice through the HACC Gen website, dashboard, email, or other appropriate means.

Your continued use of the API after the effective date of updated terms constitutes acceptance of the revised API Terms, to the extent permitted by applicable law.

21. Termination

These API Terms will remain applicable while you have API access or otherwise use the HACC Gen API.

Termination or suspension of your HACC Gen account, applicable plan, or API access may result in termination or suspension of your right to use the API.

Upon termination, you must stop using the API and must no longer use revoked API credentials.

Sections that by their nature should survive termination—including intellectual property, confidentiality, disclaimers, limitations of liability, indemnification, and applicable provisions concerning User Content—will survive termination.

22. General

If any provision of these API Terms is found to be invalid or unenforceable, the remaining provisions will remain in effect.

Failure by HACC Gen to enforce a provision does not constitute a waiver of that provision.

These API Terms, together with the HACC Gen Terms of Service, Acceptable Use Policy, Privacy Policy, and applicable commercial terms, constitute the agreement governing your use of the API.

23. Governing Law and Jurisdiction

These API Terms will be governed by the laws specified in the HACC Gen Terms of Service.

Any dispute arising from or relating to API access or use will be subject to the jurisdiction and dispute-resolution provisions specified in the Terms of Service.

24. Contact

For API-related questions, security concerns, credential issues, or other API matters, contact:

Dynamic Pixel Multimedia Solutions
Email: info@dynamicpixel.co.in

For security incidents involving API credentials or unauthorized access, please clearly identify the communication as an API Security Issue where appropriate.

By obtaining, configuring, or using HACC Gen API access, you acknowledge that you have read and agree to these API Terms.