Plugin Developer Agreement

Effective Date: February 11, 2026

This Plugin Developer Agreement ("Agreement") is entered into by and between QuikForms, LLC, an Oregon limited liability company ("QuikForms," "we," "us," or "our"), and the individual or entity agreeing to these terms ("Developer," "you," or "your").

By accessing or using the QuikForms Plugin Framework, registering a Plugin, or submitting Plugin code for review, you acknowledge that you have read, understood, and agree to be bound by this Agreement. If you are entering into this Agreement on behalf of a company or other legal entity, you represent that you have the authority to bind that entity to this Agreement.

1. Definitions

"Plugin" means any software code, including but not limited to Apex classes, JavaScript files, Lightning Web Components, Static Resources, Custom Metadata configurations, and associated documentation, developed by Developer that extends or integrates with the QuikForms managed package through the Plugin Framework.

"Plugin Framework" means the set of Apex interfaces, JavaScript APIs, Custom Metadata types, Platform Events, and associated documentation provided by QuikForms to enable third-party plugin development, including but not limited to: IQuikFormsPlugin, IQuikFormsCalloutHandler, IQuikFormsFieldValidator, IQuikFormsSubmissionHandler, QuikFormsPluginInfo, QuikFormsPluginRegistry, QuikFormsPluginSecurity, QuikFormsCalloutRequest, QuikFormsCalloutResponse, and all related classes, interfaces, types, and APIs.

"Framework Interfaces" means the specific Apex interfaces and global classes provided by QuikForms as part of the Plugin Framework that Plugins must implement or interact with, including: IQuikFormsPlugin, IQuikFormsCalloutHandler, IQuikFormsFieldValidator, IQuikFormsSubmissionHandler, and any future interfaces published by QuikForms.

"QuikForms Software" means the QuikForms managed package distributed via the Salesforce AppExchange, including all components, code, metadata, documentation, and updates thereto.

"Customer" means any end user or organization that has licensed the QuikForms Software and installed it within their Salesforce org.

"Customer Org" means the Salesforce organization (production or sandbox instance) in which a Customer has installed the QuikForms Software and in which a Plugin operates.

"Form Submission Data" means all data submitted through QuikForms forms, including but not limited to field values, metadata, submitter information, IP addresses, timestamps, file attachments, and any data accessible through QuikFormsSubmissionContext, QuikFormsValidationContext, or related context objects passed to Plugin code during form processing.

"Personal Data" means any information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked with a particular individual, as defined under applicable data protection laws including the GDPR, CCPA, and other applicable privacy legislation.

"External Callout" means any HTTP request, API call, or other network communication made by a Plugin to any endpoint outside of the Salesforce platform.

"Professional Tier" means the QuikForms subscription tier priced at $799 per month or $699 per month billed annually (or as subsequently updated by QuikForms) that includes access to the Plugin Framework.

"Plugin Marketplace" means any QuikForms-operated or QuikForms-authorized platform, directory, or listing service through which Plugins may be distributed to Customers.

"Security Tests" means the automated security validation suite provided by QuikForms, including but not limited to QuikFormsPluginSecurityTest and QuikFormsPluginSecurity validation checks.

2. Plugin Framework License

2.1 License Grant to Developer

Subject to the terms of this Agreement, QuikForms grants Developer a limited, non-exclusive, non-transferable, revocable license to:

Access and use the Plugin Framework solely for the purpose of developing, testing, and maintaining Plugins that are compatible with the QuikForms Software;
Reference and implement the Framework Interfaces in Plugin code;
Use QuikForms documentation, sample code, and developer resources provided for plugin development; and
Distribute Plugins to Customers in accordance with Section 9 (Plugin Distribution) of this Agreement.

2.2 License Restrictions

Developer shall not:

Reverse engineer, decompile, disassemble, or otherwise attempt to derive the source code of the QuikForms Software or any non-public component of the Plugin Framework;
Use the Plugin Framework to develop software that competes with or substitutes for the QuikForms Software;
Sublicense, sell, transfer, or assign the rights granted under this Agreement without prior written consent from QuikForms;
Remove, alter, or obscure any proprietary notices, labels, or marks on the Plugin Framework or QuikForms Software;
Use the Plugin Framework to develop Plugins that circumvent, disable, or interfere with QuikForms licensing, security controls, metering, or feature restrictions;
Access, use, or reference any non-public, internal, or undocumented API, class, method, or component of the QuikForms managed package that is not part of the published Plugin Framework; or
Use the Plugin Framework in any manner that violates applicable laws, the Salesforce Master Subscription Agreement, or the Salesforce AppExchange Partner Program Agreement.

2.3 Subscription Requirement

Access to the Plugin Framework requires that the Customer Org in which the Plugin operates maintains an active QuikForms Professional Tier subscription (or higher tier, if applicable). Developer acknowledges that Plugins will not function in Customer Orgs that do not have the requisite subscription tier.

3. Developer Eligibility and Registration

3.1 Eligibility. To develop Plugins under this Agreement, Developer must:

Be at least eighteen (18) years of age or the age of majority in the jurisdiction in which Developer resides;
Have a valid Salesforce developer account or access to a Salesforce development environment;
Register as a QuikForms Plugin Developer by completing the developer registration process; and
Maintain accurate and current registration information throughout the term of this Agreement.

3.2 Developer Account. Developer is responsible for maintaining the confidentiality of their developer account credentials and for all activities that occur under their account. Developer must notify QuikForms immediately at [email protected] upon becoming aware of any unauthorized use of their account.

3.3 Developer Verification. QuikForms reserves the right to verify Developer's identity, qualifications, and compliance with this Agreement at any time. Developer agrees to cooperate with reasonable verification requests.

4. Plugin Development Requirements

4.1 Interface Implementation

All Plugins must implement the IQuikFormsPlugin interface as the base requirement. Plugins providing additional functionality must implement the appropriate additional interfaces:

Custom Field Types: Implement IQuikFormsPlugin and register custom field types through QuikForms_Custom_Field_Type__mdt Custom Metadata;
Field Validation: Implement IQuikFormsFieldValidator for custom synchronous and/or asynchronous validation logic;
Submission Handling: Implement IQuikFormsSubmissionHandler for before-submit and after-submit processing logic; and
External Callouts: Implement IQuikFormsCalloutHandler for HTTP callouts to third-party services, and set Supports_Callout__c to true on the QuikForms_Plugin__mdt record.

4.2 Plugin Metadata

All Plugins must be registered through a QuikForms_Plugin__mdt Custom Metadata record with accurate and complete field values, including but not limited to: Plugin_Type__c, Apex_Class_Name__c, Is_Active__c, Execution_Order__c, Error_Behavior__c, Validation_Mode__c, Version__c, and Description__c.

4.3 Plugin Information

The getPluginInfo() method must return a valid QuikFormsPluginInfo object containing:

A unique, descriptive plugin name;
A version string following Semantic Versioning (SemVer) format (e.g., 1.0.0);
A human-readable description of the Plugin's functionality; and
Accurate declaration of callout support via the supportsCallouts property.

4.4 Coding Standards

Plugins must:

Follow Salesforce Apex coding best practices;
Include meaningful code comments and documentation;
Implement proper error handling with try-catch blocks and avoid unhandled exceptions;
Use the Error_Behavior__c metadata field (Fatal, Warn, or Skippable) appropriately; and
Include comprehensive Apex test classes with a minimum of 85% code coverage.

4.5 JavaScript Plugins

Plugins that include client-side JavaScript must:

Package JavaScript code as Salesforce Static Resources;
Register with the QuikFormsPlugins.register() API using a unique plugin name;
Implement the required field type interface methods (render, getValue) and any applicable optional methods;
Follow Content Security Policy (CSP) requirements of Salesforce Lightning Experience and Experience Cloud; and
Avoid polluting the global namespace beyond the single entry point function.

5. Security Obligations

5.1 Security Testing

All Plugins must pass the QuikForms security validation suite, including all checks performed by the QuikFormsPluginSecurity class. Specifically, Plugins must:

Pass QuikFormsPluginSecurity.isValidPluginClass() validation;
Not attempt to instantiate or reference blocked class patterns (including classes prefixed with System., Database., Schema., Auth., Messaging., Flow., Approval., Canvas., ConnectApi., Dom., Http, Queueable, Schedulable, StaticResource) or blocked exact class names;
Use QuikFormsPluginSecurity.sanitizeConfiguration() when processing configuration data;
Use QuikFormsPluginSecurity.escapeHtml() or QuikFormsPluginSecurity.sanitizeHtml() when rendering user-supplied content to prevent XSS attacks; and
Use QuikFormsPluginSecurity.isValidUrl() to validate any URLs before use.

5.2 Prohibited Practices

Plugins must not:

Introduce any malware, viruses, Trojan horses, spyware, adware, ransomware, or other malicious code;
Attempt to access, modify, or delete data beyond what is necessary for the Plugin's stated functionality;
Store credentials, authentication tokens, API keys, or secrets in plaintext;
Bypass or circumvent Salesforce sharing rules, field-level security, object-level permissions, or organization-wide defaults;
Attempt to access Salesforce system resources or authentication tokens outside the scope of declared functionality;
Employ obfuscation techniques designed to hide the Plugin's true functionality from security review;
Include any form of tracking, analytics, or telemetry that transmits data about Customers or their users to external systems without explicit Customer consent and clear disclosure; or
Modify, override, or interfere with QuikForms managed package code, metadata, or configuration.

5.3 Vulnerability Disclosure

Developer must:

Promptly notify QuikForms at [email protected] upon discovery of any security vulnerability in the Plugin, the Plugin Framework, or the QuikForms Software, within 48 hours of discovery;
Cooperate with QuikForms in investigating and remediating any security issues;
Not publicly disclose any security vulnerability in the Plugin Framework or QuikForms Software without prior written consent from QuikForms; and
Promptly release security patches for any vulnerability discovered in a distributed Plugin and notify all affected Customers.

5.4 Security Audits

QuikForms reserves the right to conduct security audits of any Plugin, including automated code scanning, manual code review, and penetration testing. Developer agrees to cooperate with such audits and to promptly remediate any identified security issues. QuikForms will provide 10 business days' written notice prior to any audit, except in the case of an active security incident, in which case QuikForms may conduct an immediate audit.

6. Data Protection and Privacy

6.1 Access to Form Submission Data

Developer acknowledges and agrees that Plugins may have access to Form Submission Data during form processing, including through QuikFormsSubmissionContext, QuikFormsValidationContext, and related context objects. Such Form Submission Data may contain Personal Data.

6.2 Data Processing Obligations

With respect to any Form Submission Data accessed by the Plugin, Developer shall:

Process Form Submission Data solely for the purposes necessary to perform the Plugin's stated and documented functionality;
Not collect, store, retain, copy, or cache Form Submission Data beyond the duration of the specific form processing transaction, unless such retention is essential, clearly documented, and the Customer has consented;
Not sell, rent, lease, trade, or otherwise transfer Form Submission Data to any third party, except as strictly necessary to perform the Plugin's stated functionality;
Implement appropriate technical and organizational measures to protect Form Submission Data;
Not use Form Submission Data for any secondary purpose, including advertising, marketing, profiling, analytics, or training machine learning models; and
Promptly delete or return all Form Submission Data upon termination of this Agreement.

6.3 Data Protection Compliance

Developer shall comply with all applicable data protection and privacy laws and regulations, including but not limited to the GDPR, CCPA/CPRA, HIPAA (where applicable), PCI DSS (where applicable), and any other applicable local, state, national, or international data protection laws.

6.4 Data Breach Notification

In the event of any unauthorized access, acquisition, use, or disclosure of Form Submission Data ("Data Breach"), Developer shall:

Notify QuikForms at [email protected] within 72 hours of discovering the Data Breach;
Provide a detailed description of the Data Breach, including the categories and approximate number of data subjects affected;
Take immediate steps to contain and remediate the Data Breach;
Cooperate with QuikForms and affected Customers in investigating and responding; and
Not communicate with affected data subjects regarding the Data Breach without prior coordination with QuikForms, unless required by law.

7. External Callouts and Third-Party Services

7.1 Callout Disclosure

Any Plugin that makes External Callouts must:

Clearly disclose all external endpoints, APIs, and services in the Plugin's documentation and metadata;
Set Supports_Callout__c to true on the Plugin's QuikForms_Plugin__mdt record;
Implement the IQuikFormsCalloutHandler interface for all callout functionality; and
Submit a complete list of external endpoints as part of the Plugin review process.

7.2 Callout Security

External Callouts must:

Use HTTPS (TLS 1.2 or higher) for all communications;
Use Salesforce Named Credentials for authentication whenever possible;
Validate all URLs using QuikFormsPluginSecurity.isValidUrl() before making callouts;
Transmit only the minimum data necessary for the Plugin's stated functionality;
Not transmit Form Submission Data to any undisclosed endpoint; and
Respect the Timeout_Ms__c configuration value and handle timeout scenarios gracefully.

7.3 Data Exfiltration Prohibition

Plugins must not transmit Form Submission Data to external endpoints for undisclosed purposes, include hidden communication channels or tracking mechanisms, or alter or intercept External Callouts made by other Plugins or by the QuikForms Software itself.

8. Intellectual Property Ownership

8.1 QuikForms IP

QuikForms retains all right, title, and interest in the QuikForms Software, the Plugin Framework (including all Framework Interfaces, global classes, Custom Metadata types, and APIs), the QuikForms name, logo, and trademarks, and all derivative works, improvements, and modifications thereto.

8.2 Developer IP

Developer retains all right, title, and interest in the Plugin code authored by Developer (excluding any QuikForms IP incorporated therein), Developer's proprietary algorithms and trade secrets, and Developer's trademarks and brand identity associated with the Plugin.

8.3 License to QuikForms

Developer grants QuikForms a limited, non-exclusive, worldwide, royalty-free license to:

Review, test, analyze, and scan Plugin code for security, compatibility, and quality assurance;
Reproduce and display Plugin name, description, icon, screenshots, and documentation in the Plugin Marketplace and marketing materials;
Execute Plugin code within the Plugin Framework for the purpose of providing functionality to Customers; and
Create and maintain interoperability between the Plugin and future versions of the QuikForms Software.

8.4 No Implied Licenses

Nothing in this Agreement grants either party any right, title, or interest in the other party's intellectual property except as expressly set forth herein.

8.5 Feedback

If Developer provides QuikForms with any feedback, suggestions, or recommendations regarding the Plugin Framework ("Feedback"), QuikForms shall have a perpetual, irrevocable, worldwide, royalty-free license to use, incorporate, modify, and commercialize such Feedback without obligation to Developer.

9. Plugin Distribution

9.1 Distribution Channels

Developer may distribute Plugins through:

QuikForms Plugin Marketplace (if available): Subject to QuikForms review and approval per Section 12;
Developer's Own Channels: Developer's own website, repository, or distribution platform, provided the Plugin's QuikForms Professional Tier requirement is clearly stated; and
Salesforce AppExchange: As separate Salesforce packages, subject to Salesforce's own review requirements, with clear identification that the QuikForms Software is required.

9.2 Distribution Requirements

Regardless of distribution channel, Developer must clearly disclose the Professional Tier subscription requirement, provide accurate and complete documentation, include installation instructions, identify the minimum compatible QuikForms version, and not misrepresent the Plugin as being endorsed by QuikForms unless a separate endorsement agreement exists.

9.3 Pricing

Developer may charge Customers for Plugins at prices determined by Developer. QuikForms does not charge a revenue share on Plugin sales unless Developer elects to distribute through the QuikForms Plugin Marketplace, in which case a separate marketplace agreement shall apply.

9.4 Withdrawal

QuikForms reserves the right to remove or require removal of any Plugin from any distribution channel if the Plugin violates this Agreement, poses a security risk, or is causing material harm. QuikForms will provide written notice and 10 business days to cure, except in cases involving active security threats or legal violations, where immediate removal may be required.

10. Compatibility and Updates

10.1 QuikForms will periodically release updates to the QuikForms Software and Plugin Framework, which may include changes to Framework Interfaces, API behavior, and security requirements.

10.2 QuikForms will use commercially reasonable efforts to provide at least 90 calendar days' advance written notice of breaking changes, maintain a publicly accessible changelog, provide beta versions for testing when feasible, and clearly distinguish between backward-compatible and breaking changes.

10.3 Deprecation Policy. When QuikForms deprecates a Framework Interface, method, or feature, QuikForms will designate it as "deprecated" in documentation and maintain backward compatibility for a minimum of 12 months from the date of deprecation notice. Developer shall migrate Plugins to use replacement components within the deprecation period.

10.4 Developer shall maintain Plugins in a state of compatibility with the current and immediately preceding major version of the QuikForms Software, promptly test Plugins against pre-release versions, release updated versions within 30 business days of a compatibility-affecting QuikForms release, and clearly communicate compatible QuikForms versions to Customers.

10.5 QuikForms does not guarantee that any Plugin will remain compatible with future versions of the QuikForms Software or the Salesforce platform.

11. Support and Maintenance

11.1 QuikForms Support Scope. QuikForms provides support for the QuikForms Software and Plugin Framework interfaces as documented, issues arising from defects in the Plugin Framework, and general guidance through developer documentation.

11.2 Developer Support Obligations. Developer is solely responsible for providing technical support to Customers for the Plugin, maintaining a support channel, responding to Customer requests within commercially reasonable timeframes, resolving critical Plugin bugs (including security vulnerabilities) within 5 business days, and providing ongoing maintenance including bug fixes and security patches.

11.3 Issue Triage. When an issue involves both the QuikForms Software and a Plugin, the parties will cooperate in good faith to identify the root cause. The party whose code contains the root cause shall provide the fix.

11.4 End-of-Life. If Developer decides to discontinue a Plugin, Developer shall provide at least 90 calendar days' advance written notice to QuikForms and all Customers who have installed the Plugin, continue to provide critical security patches during the notice period, and provide reasonable migration guidance.

12. Plugin Review and Approval

12.1 Before distributing a Plugin through any QuikForms-operated channel, Developer must submit the Plugin code, documentation, and completed Plugin Review Checklist to [email protected].

12.2 QuikForms will review submitted Plugins for security compliance, data protection obligations, proper interface implementation, code quality and test coverage, metadata configuration, and overall compatibility.

12.3 QuikForms will use commercially reasonable efforts to complete the initial review within 15 business days of receiving a complete submission.

12.4 QuikForms may approve or reject a Plugin submission at its sole discretion. Rejected Plugins will receive written feedback with specific remediation guidance. A rejection does not prevent resubmission.

12.5 Approval does not constitute an ongoing guarantee of compliance. QuikForms may re-review any approved Plugin at any time.

12.6 Plugins distributed solely through Developer's own channels are not required to undergo the QuikForms review process but must still comply with all other provisions of this Agreement. QuikForms assumes no responsibility for unreviewed Plugins.

13. Performance and Resource Consumption

13.1 Shared Execution Context. Plugin code runs within the same Salesforce execution context as the QuikForms managed package, sharing Salesforce governor limits including SOQL queries, DML statements, CPU time, heap size, callout limits, and future method limits.

13.2 Resource Consumption Standards. Plugins must minimize SOQL queries and DML operations, not consume more than 25% of available CPU time per transaction, not execute more than 10 SOQL queries per transaction, not perform more than 5 DML statements per transaction, complete callout operations within the configured Timeout_Ms__c value (maximum 10,000 milliseconds for any single callout), and not use asynchronous processing without explicit disclosure and approval.

13.3 Developer shall performance-test Plugins under realistic data volumes before distribution.

13.4 If a Plugin causes governor limit exceptions or degraded performance, QuikForms may notify Developer and require remediation within 5 business days, advise affected Customers to deactivate the Plugin, modify the Plugin's Error_Behavior__c to Skippable, or suspend the Plugin's approval.

14. Representations and Warranties

14.1 Developer Representations. Developer represents and warrants that Developer has the legal right and authority to enter into this Agreement, the Plugin is Developer's original work (or Developer has obtained all necessary rights), the Plugin does not infringe any third-party rights, the Plugin does not contain malicious code, and the Plugin's functionality is accurately described in its documentation.

14.2 QuikForms Representations. QuikForms represents and warrants that QuikForms has the legal right and authority to enter into this Agreement and grant the licenses herein, and that the Plugin Framework documentation accurately describes the published interfaces.

14.3 Disclaimer. EXCEPT AS EXPRESSLY SET FORTH IN THIS SECTION 14, THE PLUGIN FRAMEWORK AND QUIKFORMS SOFTWARE ARE PROVIDED "AS IS" AND "AS AVAILABLE." QUIKFORMS MAKES NO WARRANTIES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, RELIABILITY, OR UNINTERRUPTED OR ERROR-FREE OPERATION.

15. Indemnification

15.1 Developer Indemnification. Developer shall indemnify, defend, and hold harmless QuikForms, its officers, directors, employees, and agents from any claims, losses, damages, liabilities, costs, and expenses arising from the Plugin (including its development, distribution, installation, use, or malfunction), Developer's breach of this Agreement, intellectual property infringement, unauthorized data access, External Callouts, Customer claims, or Developer's violation of applicable law.

15.2 QuikForms Indemnification. QuikForms shall indemnify and defend Developer from claims that the Plugin Framework interfaces infringe third-party intellectual property rights, and from QuikForms' breach of this Agreement.

15.3 Indemnification Procedure. The Indemnified Party shall promptly notify the Indemnifying Party, grant sole control of the defense, and provide reasonable cooperation. The Indemnifying Party shall not settle any claim that imposes obligations on the Indemnified Party without prior written consent.

16. Limitation of Liability

16.1 Exclusion of Consequential Damages. TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, BUSINESS, DATA, OR GOODWILL.

16.2 Cap on Liability. EACH PARTY'S TOTAL CUMULATIVE LIABILITY SHALL NOT EXCEED THE GREATER OF (A) $50,000 OR (B) THE TOTAL FEES PAID OR PAYABLE BY DEVELOPER TO QUIKFORMS DURING THE 12-MONTH PERIOD IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM.

16.3 Exceptions. The above limitations do not apply to indemnification obligations, Developer's breach of Security Obligations (Section 5) or Data Protection (Section 6), intellectual property infringement, breach of confidentiality, willful misconduct, gross negligence, fraud, or liability that cannot be limited under applicable law.

17. Term and Termination

17.1 Term. This Agreement is effective as of the Effective Date and continues until terminated.

17.2 Termination for Convenience. Either party may terminate by providing 30 calendar days' prior written notice.

17.3 Termination for Cause. Either party may terminate immediately if the other party materially breaches this Agreement and fails to cure within 30 calendar days after receiving written notice, or becomes insolvent or files for bankruptcy.

17.4 Immediate Termination. QuikForms may terminate immediately, without notice, if the Plugin contains malware or data-exfiltration code, causes a material security breach, violates data protection laws, or poses an imminent threat to security, integrity, or availability.

17.5 Effects of Termination. Upon termination: all licenses terminate, Developer shall cease use of the Plugin Framework and QuikForms trademarks, Developer shall remove the Plugin from distribution channels within 10 calendar days, Developer shall return or destroy QuikForms confidential information, and Developer shall delete any Form Submission Data or Customer data in Developer's possession. Sections 1, 6, 8, 14, 15, 16, 17.5, 18, and 19 survive termination.

18. Confidentiality

18.1 Definition. "Confidential Information" means any non-public information disclosed by one party to the other in connection with this Agreement, including Plugin Framework source code, pre-release software, business plans, pricing strategies, proprietary algorithms, and security vulnerability reports.

18.2 Obligations. The Receiving Party shall use Confidential Information solely for the purposes contemplated by this Agreement, protect it using at least the same degree of care as its own confidential information (but not less than reasonable care), and not disclose it to third parties without consent, except to employees and contractors with a need to know who are bound by confidentiality obligations.

18.3 Exclusions. Confidential Information does not include information that is publicly available, was previously known to the Receiving Party, was independently developed, or was rightfully obtained from a third party without restriction.

18.4 Compelled Disclosure. If compelled by law to disclose, the Receiving Party shall promptly notify the Disclosing Party and cooperate in seeking a protective order, to the extent legally permitted.

19. General Provisions

19.1 Governing Law. This Agreement shall be governed by and construed in accordance with the laws of the State of Oregon, without regard to its conflict of law principles.

19.2 Dispute Resolution. Any dispute that cannot be resolved through good-faith negotiations within 30 calendar days shall be resolved through binding arbitration administered by JAMS in accordance with its then-current rules. The arbitration shall be conducted in Eugene, Oregon. Either party may seek injunctive relief in any court of competent jurisdiction to prevent irreparable harm pending arbitration.

19.3 Independent Contractor. Developer is an independent contractor. Nothing in this Agreement creates an employment, partnership, joint venture, franchise, or agency relationship.

19.4 Assignment. Developer may not assign this Agreement without QuikForms' prior written consent. QuikForms may assign in connection with a merger, acquisition, or sale of all or substantially all of its assets.

19.5 Notices. All notices shall be in writing and deemed given when delivered personally, sent by confirmed email to the email address provided during registration or to [email protected], one business day after being sent by overnight courier, or three business days after being sent by certified mail.

19.6 Entire Agreement. This Agreement constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior agreements and communications.

19.7 Amendments. QuikForms may amend this Agreement by providing written notice with at least 30 calendar days' advance notice for material amendments. Continued use of the Plugin Framework constitutes acceptance. If Developer does not agree, Developer's sole remedy is to terminate per Section 17.2.

19.8 Waiver. No failure or delay in exercising any right shall operate as a waiver thereof.

19.9 Severability. If any provision is held invalid, the remaining provisions remain in full force and effect.

19.10 Force Majeure. Neither party shall be liable for failure or delay caused by circumstances beyond reasonable control, including natural disasters, war, pandemics, strikes, or disruptions to the Salesforce platform.

19.11 Export Compliance. Developer shall comply with all applicable export control laws and regulations and represents that Developer is not located in any embargoed country and is not on any prohibited or restricted party list.

19.12 Third-Party Beneficiaries. Customers are intended third-party beneficiaries of Developer's obligations under Sections 5 (Security Obligations), 6 (Data Protection), and 7 (External Callouts). No other third-party beneficiary rights are created.

Acknowledgment and Acceptance

By registering as a QuikForms Plugin Developer, submitting a Plugin for review, or using the Plugin Framework, Developer acknowledges that Developer has read this Agreement in its entirety, understands its terms, and agrees to be bound by all of its provisions.

Contact: [email protected] | Website: www.sfquikforms.com

QuikForms Legal