Effective Date: August 14, 2026
1. SCOPE AND DEFINITIONS
1.1. Introduction.
These Platform Terms ("Platform Terms") govern the Customer’s access to and use of the proprietary platform interfaces, tools, and systems provided by the Pinkdude Group ("Provider", "We", or "Us"). These terms apply globally to all users, regardless of subscription tier, and form an integral part of the Master Terms of Service.
1.2. The "Control Plane".
For the purposes of this Agreement, the "Control Plane" refers to the set of administrative interfaces and APIs used to configure, monitor, and manage the Services. This includes, but is not limited to:
(a) The Dashboard: The secure, web-based graphical user interface (GUI) accessible via console.pinkdude.com (or such other URL as we may designate).
(b) The API: The RESTful, GraphQL, or gRPC Application Programming Interfaces exposed by the Provider for programmatic interaction.
(c) CLI Tools: The command-line interface software, SDKs (Software Development Kits), and libraries distributed by the Provider.
(d) Identity Services: The authentication, authorization, and accounting (AAA) systems, including Single Sign-On (SSO) and Multi-Factor Authentication (MFA).
1.3. User Classification.
(a) "Root User": The primary account holder with ultimate administrative control and billing liability.
(b) "Authorized User": Any individual (employee, contractor, or agent) authorized by the Root User to access the Platform.
(c) "Service Account": A non-human account (e.g., CI/CD bot, application backend) used for automated interactions via API keys.
2. IDENTITY AND ACCESS MANAGEMENT (IAM)
2.1. Account Security Responsibilities.
You are solely responsible for maintaining the confidentiality and security of your account credentials.
(a) No Sharing: Credentials (usernames, passwords, MFA tokens) must uniquely identify a specific individual. You may not share credentials between multiple users. If multiple individuals require access, you must invite them as distinct Authorized Users.
(b) Credential Rotation: We recommend rotating API keys and passwords at least every ninety (90) days. The Provider reserves the right to force a password reset if we detect suspicious activity or a credential leak.
(c) Liability: You are fully responsible for all activities that occur under your account, regardless of whether such activities were authorized by you. This includes actions taken by former employees whose access you failed to revoke.
2.2. Multi-Factor Authentication (MFA).
(a) Requirement: The Provider reserves the right to mandate Multi-Factor Authentication (MFA) for specific high-risk actions (e.g., deleting production resources, changing billing information, or accessing the Root Account).
(b) Liability Shift: If your account is compromised due to a lack of MFA (e.g., weak password, credential stuffing, or phishing), the Provider is expressly released from all liability for any resulting damages, data loss, or resource usage fees. You acknowledge that MFA is a critical security control and that disabling it constitutes a material assumption of risk.
2.3. Enterprise SSO (Single Sign-On).
For Customers on eligible Enterprise Plans, we may support Federated Identity via SAML 2.0 or OIDC.
(a) IdP Responsibility: You are responsible for the availability and security of your Identity Provider (IdP) (e.g., Okta, Azure AD). The Provider is not liable for login failures caused by your IdP's downtime.
(b) JIT Provisioning: If Just-in-Time (JIT) provisioning is enabled, new users logging in via your IdP will automatically consume seats on your plan. You agree to pay for any overages resulting from such auto-provisioning.
(c) Emergency Access: You must maintain at least one "Break-Glass" administrator account that does not rely on SSO to ensure access during IdP outages.
2.4. Service Accounts and Automation.
(a) Non-Interactive Use: Service Accounts are strictly for automated, non-interactive use by applications or systems. They may not be used by humans to bypass "Per-User" licensing fees.
(b) Key Management: You are responsible for securely storing API keys for Service Accounts (e.g., using a Secrets Manager). You must not commit API keys to public code repositories (e.g., GitHub). If we detect exposed keys, we will revoke them immediately to protect your account.
3. API USAGE AND GOVERNANCE
3.1. License to Use API.
Subject to these Terms, we grant you a limited, non-exclusive, non-transferable, revocable license to use the API solely to develop, test, and support your integration with the Services.
3.2. Rate Limits and Quotas.
To protect the stability of the Platform for all customers, the Provider enforces strict Rate Limits (e.g., requests per second, concurrent connections).
(a) Dynamic Limits: Rate limits may vary based on your Plan Tier, the specific API endpoint, and overall system load.
(b) Throttling: If you exceed these limits, your requests will be throttled and return an HTTP 429 "Too Many Requests" status code. You must implement "Exponential Backoff" logic in your applications to handle these responses gracefully.
(c) Hard Cap: Continued excessive requests after receiving a 429 error may result in a temporary IP ban to prevent Denial of Service (DoS) effects.
3.3. Caching and Polling.
(a) Polling Frequency: You may not poll the API more frequently than once every five (5) seconds for status updates, unless the endpoint is specifically documented as supporting higher frequency (e.g., WebSockets).
(b) Caching: You are encouraged to cache API responses locally to reduce network traffic. However, you may not cache or store API data for longer than twenty-four (24) hours if such data constitutes "Platform Data" (e.g., user profiles, pricing tables) that is subject to change.
3.4. API Evolution and Deprecation.
(a) Breaking Changes: We strive to maintain backward compatibility. A "Breaking Change" is a change that requires you to modify your code to maintain functionality (e.g., removing a required parameter).
(b) Deprecation Policy: We will use commercially reasonable efforts to provide at least six (6) months' notice before deprecating a major API version. During the deprecation period, the API will remain operational but may be marked as "Deprecated" in documentation.
(c) Sunset: After the deprecation period expires, the API version will be "Sunset" and will no longer accept requests.
3.5. Webhooks.
If the Services provide Webhooks for event notifications:
(a) Retries: We will attempt to deliver failed webhooks for a limited period (e.g., 24 hours) using an exponential backoff strategy.
(b) Validation: You are responsible for validating the cryptographic signature of incoming webhooks to ensure they originated from the Provider.
(c) Disabling: We reserve the right to disable webhooks for your account if your endpoint consistently returns error codes (e.g., HTTP 500) or times out.
4. DASHBOARD AND INTERFACE RESTRICTIONS
4.1. Prohibited Acts.
You agree not to misuse the Control Plane. Specifically, you shall not:
(a) Scrape: Use any robot, spider, scraper, deep-link, or other automated data gathering or extraction tool, program, algorithm, or methodology to access, acquire, copy, or monitor the Dashboard or any portion of the Services.
(b) Reverse Engineer: Attempt to decipher, decompile, disassemble, or reverse engineer any of the software comprising or in any way making up a part of the Services.
(c) Circumvent: Attempt to bypass or circumvent any security mechanisms, rate limits, or access controls of the Interface.
(d) Benchmark: Access the Services for the purpose of building a competitive product or service or for the purpose of monitoring its availability, performance, or functionality for competitive benchmarking.
4.2. Acceptable Platform Load (The "Noisy Neighbor" Protection).
You agree that your use of the Control Plane and API shall not materially degrade the performance of the Platform for other customers. The Provider reserves the right to throttle, suspend, or terminate accounts that generate excessive load (e.g., crypto-mining, abusive automation, DDoS simulation, or rapid-fire API polling) unrelated to legitimate business usage, as determined in our sole discretion.
4.3. Intellectual Property Rights.
The visual interfaces, graphics, design, compilation, information, data, computer code (including source code or object code), products, software, services, and all other elements of the Dashboard (collectively, the "Materials") are protected by intellectual property and other laws. All Materials are the property of the Provider or its third-party licensors. You may not sell, license, distribute, copy, modify, publicly perform or display, transmit, publish, edit, adapt, create derivative works from, or otherwise make unauthorized use of the Materials.
5. TECHNICAL SUPPORT SERVICES
5.1. Scope of Support.
The Provider offers Technical Support Services ("Support") to assist with issues directly related to the availability and functionality of the Platform.
(a) Included: Troubleshooting platform errors (5xx), clarifying documentation, assisting with billing inquiries, and investigating potential bugs.
(b) Excluded: Support does NOT include:
Writing, debugging, or optimizing your application code (PHP, Python, Java, etc.).
Configuring your local environment, operating system, or third-party software.
Designing your system architecture or database schema (unless covered by a separate Professional Services agreement).
Training your employees on general computer use.
5.2. Support Tiers and SLAs.
Support availability depends on your Subscription Plan:
(a) Free / Starter: Access to public Community Forums and Documentation. No guaranteed response time.
(b) Pro / Business: Email support during Business Hours (09:00 – 17:00 UTC). Target response time: 24 hours.
(c) Enterprise: 24/7/365 Priority Support via Email and Chat. Target response time for Critical Impact (P1) issues: 1 hour.
5.3. Ticket Prioritization.
We triage support tickets based on severity:
P1 (Critical): Production system is down; no workaround available.
P2 (High): Major functionality is impaired; operations are severely restricted.
P3 (Normal): Minor issues, questions, or feature requests.
P4 (Low): Cosmetic issues or typos.
5.4. Customer Responsibilities.
To receive effective Support, you must:
(a) Cooperate: Provide all information reasonably requested by the Support Team (e.g., logs, screenshots, steps to reproduce).
(b) Authorized Contact: Ensure that support requests are submitted by an Authorized User listed on the account. We will not provide support to unauthorized third parties.
5.5. Abusive Behavior.
We maintain a Zero Tolerance Policy for abuse of our support staff. Use of profanity, threats, sexual harassment, or aggressive behavior will result in immediate termination of Support Services and potentially the suspension of your account.
6. AUDIT LOGS AND SECURITY MONITORING
6.1. Audit Trails.
For security and compliance purposes, the Provider logs administrative actions taken within the Control Plane (e.g., "User X deleted Server Y on Date Z") ("Audit Logs").
(a) Availability: Audit Logs may be viewable in the Dashboard or available via API, depending on your Plan Tier.
(b) Retention: We retain Audit Logs for a standard period (e.g., 90 days) unless a longer retention period is purchased via an Enterprise Add-on.
6.2. Customer Reliance.
You acknowledge that while we strive for accuracy, Audit Logs are provided "AS IS" and may not capture every single event due to technical limitations or system latency. They should not be relied upon as a complete forensic record for legal proceedings without verification.
6.3. Security Analytics.
The Provider reserves the right to analyze usage patterns, access logs, and API traffic (in an anonymized and aggregated manner) to:
(a) Detect and prevent security threats (e.g., brute force attacks).
(b) Improve the performance and usability of the Dashboard.
(c) Identify potential violations of the Acceptable Use Policy (AUP).
7. SANDBOX AND TEST ENVIRONMENTS
7.1. Definition.
The Provider may offer specific environments designated as "Sandbox," "Staging," or "Test" ("Sandbox Environments") for the purpose of testing integrations without affecting production data.
7.2. Usage Restrictions.
(a) Non-Production Data: You must NOT upload real Customer Data, Personal Data (PII), or production secrets to a Sandbox Environment. Sandbox Environments are not subject to the same strict security controls (e.g., backup frequency, access controls) as Production environments.
(b) Volatility: Data in Sandbox Environments may be wiped, reset, or deleted by the Provider at any time without notice (e.g., during a nightly reset).
(c) No SLA: Sandbox Environments are provided strictly "AS IS" and are excluded from all Service Level Agreements (SLAs) and Uptime Guarantees.
7.3. Liability Waiver.
The Provider shall have no liability for any loss of data, configuration, or work product stored in a Sandbox Environment. You assume all risks associated with the use of such environments.
8. SERVICE COMMUNICATIONS AND NOTICES
8.1. Operational Communications.
By using the Services, you consent to receive electronic communications from us deemed necessary for the administration of your account, including:
(a) Billing invoices and payment receipts.
(b) Security alerts and password reset emails.
(c) Notifications regarding updates to these Terms or the Privacy Policy.
(d) Announcements of scheduled maintenance or service degradation.
You cannot opt-out of receiving these operational messages as they are essential to the provision of the Service.
8.2. Marketing Communications.
You may opt-out of receiving marketing, promotional, or newsletter emails at any time by following the "Unsubscribe" instructions included in each email or by adjusting your notification preferences in the Dashboard.
9. EXPORT COMPLIANCE AND SANCTIONS
9.1. Representations.
You represent and warrant that you are not located in, under the control of, or a national or resident of any country to which the United States, the European Union, or the United Kingdom has embargoed goods or services (e.g., Cuba, Iran, North Korea, Syria, and the Crimea/Donbas/Luhansk regions of Ukraine).
9.2. Denied Parties.
You represent and warrant that you are not identified as a "Specially Designated National" (SDN) by the US Office of Foreign Assets Control (OFAC) or placed on any similar denied persons list by the EU or UK.
9.3. Immediate Termination.
We reserve the right to terminate your account immediately and without notice if we discover that you have breached these export compliance representations or if providing Services to you becomes prohibited by applicable law.
10. GENERAL PROVISIONS
10.1. Entire Agreement.
These Platform Terms, together with the Master Terms of Service and applicable Order Forms, constitute the entire agreement between you and the Provider regarding your use of the Control Plane.
10.2. Modifications.
We may modify these Platform Terms from time to time. If we make material changes, we will notify you via the Dashboard or email. Your continued use of the Platform after the effective date of the changes constitutes your acceptance of the modified terms.