Legal

3.0 SERVICE-SPECIFIC TERMS FRAMEWORK

3 min read

Effective Date: August 14, 2026

1. SCOPE AND APPLICABILITY

1.1. Incorporation.

These Service-Specific Terms ("Service Terms") form an integral part of the Agreement between the Pinkdude Group ("Provider") and the Customer. They are incorporated by reference into the Master Terms of Service (Document 2.1).

1.2. Modular Application.

The Service Terms are modular. You are only bound by the specific terms corresponding to the Services you actually access, use, or subscribe to.

  • Example: If you use Cloud Storage but not Accounting, you are bound by Section 3.4 but not Section 3.5.

1.3. Activation.

By activating, accessing, or using a specific Service (e.g., clicking "Enable" in the Dashboard or calling the Service via API), you explicitly agree to the Service Terms applicable to that Service.

2. ORDER OF PRECEDENCE

2.1. Conflict Resolution.

In the event of a conflict or inconsistency between documents, the following order of precedence shall apply (from highest to lowest authority):

  1. The Specific Service Terms (Documents 3.1 through 3.10) — Governs specific technical constraints.

  2. The Master Terms of Service (Document 2.1) — Governs general liability and contract relations.

  3. The Privacy Policy & DPA (Documents 2.2 & 2.3) — Governs data processing.

  4. General Explanations (FAQs, Knowledge Base, Marketing pages) — Non-binding.

2.2. Entire Agreement (The "Nuclear Clause").

Except as expressly stated in the Agreement, all other materials, including presentations, product demonstrations, sales communications, or advertising claims, are provided for informational purposes only and are non-binding. The Customer acknowledges that it has not relied on any representation, promise, or warranty that is not expressly set forth in the Agreement.

3. BETA AND PREVIEW SERVICES

3.1. Definition.

From time to time, the Provider may invite the Customer to try services designated as "Beta," "Preview," "Early Access," or "Evaluation" ("Beta Services").

3.2. No Warranties.

Beta Services are provided "AS IS" with no warranties of any kind. They may contain bugs, errors, or incomplete features.

  • (a) No SLA: Beta Services are excluded from any Service Level Agreement (SLA).

  • (b) Data Loss: The Customer acknowledges that Beta Services may be unstable. To the maximum extent permitted by applicable law, the Provider shall not be liable for any data loss, corruption, or service interruption arising from the use of Beta Services.

3.3. Termination.

The Provider reserves the right to discontinue Beta Services at any time without prior notice.

4. SERVICE LIFECYCLE AND EVOLUTION

4.1. Service Evolution.

The Services are continuously evolving, and features, functions, or APIs may be added, altered, or removed as part of ongoing product development. The Customer acknowledges that the Services are not static.

4.2. Right to Modify.

The Provider may update, modify, or deprecate specific features or APIs within a Service at its sole discretion.

4.3. Deprecation Policy.

For non-Beta Services, the Provider will use commercially reasonable efforts to provide at least thirty (30) days' notice via the Dashboard or email before deprecating a core feature or API endpoint, where reasonably practicable. This notice period may be shortened or waived in the event of security emergencies, legal requirements, or abuse prevention.

5. GEOGRAPHIC AVAILABILITY

5.1. Eligibility.

Certain Services may not be available in all jurisdictions, and the Provider reserves the right to limit the availability of any Service or feature to any person or geographic area at its sole discretion.

5.2. Restrictions.

Access to the Services is strictly prohibited from any jurisdiction subject to comprehensive sanctions by the US Office of Foreign Assets Control (OFAC), the European Union, or the United Nations (e.g., North Korea, Iran, Syria). The Customer represents that it is not located in any such jurisdiction.

6. SEVERABILITY

6.1. Independence.

If a specific provision within a Service Term (e.g., Section 3.6 Domain Terms) is found to be unenforceable, that finding will not invalidate the Master Terms or the Terms of any other Service (e.g., Section 3.4 Cloud Storage).