1. Prohibited and Malicious Content
The relyd infrastructure must not be utilized for the storage, transmission, processing, or distribution of illicit, exploitative, or structurally harmful data.
Prohibited activities include:
Illicit Operations: Deploying the service to support illegal gambling architectures, unlawful financial schemes, or any form of exploitative material.
Deceptive and Fraudulent Practices: Hosting or promoting unauthorized financial services, unlicensed trading platforms, pyramid or Ponzi schemes, deceptive advertising, or phishing campaigns designed to defraud users.
Intellectual Property Infringement: Processing any content that violates, misappropriates, or infringes upon the copyrights, patents, trademarks, or proprietary rights of third parties.
Harmful Materials: Uploading or distributing malicious software, including but not limited to viruses, trojan horses, ransomware, worms, or logic bombs.
Deceptive Infrastructure: Creating hyperlink structures intended to mislead end-users, artificially inflate third-party search engine rankings, or execute "black-hat" search engine optimization (SEO) exploits that leverage the reputational integrity of relyd.
2. Communication and Messaging Abuse
The outbound networking capabilities of relyd must not be exploited for automated or unsolicited communication.
Users are strictly bound by the following protocols:
Unsolicited Bulk Messaging: The dissemination of bulk marketing materials or unsolicited electronic communications (spam) is strictly forbidden. Clients utilizing mass-distribution lists must maintain verifiable, legally compliant double opt-in consent records for all recipients.
Identity Obfuscation: The forgery, alteration, or obfuscation of mail headers, routing information, or digital identities (spoofing) is entirely prohibited.
3. Infrastructure Integrity and Security Violations
Any unauthorized attempt to probe, breach, or manipulate the security architecture of the relyd environment will result in immediate termination of service.
Prohibited actions include:
Unauthorized Access: Attempting to access, modify, or interact with infrastructure nodes, system metadata, or data assets belonging to other tenants without explicit authorization.
Unsanctioned Security Testing: Conducting independent penetration testing, vulnerability scanning, or automated auditing of relyd systems without prior written authorization from our security operations team.
Network Interception: Executing packet sniffing, traffic analysis, or unauthorized data recording within the relyd network architecture.
Social Engineering: Utilizing non-technical attack vectors, including social engineering, pretexting, or impersonation, against relyd personnel or infrastructure.
4. System and API Resource Management
To maintain optimal performance and eliminate operational friction across our multi-tenant database backbone, clients must adhere to strict resource allocation boundaries:
Denial of Service: Engaging in activities that trigger a Denial of Service (DoS) or Distributed Denial of Service (DDoS) state, or otherwise saturating network paths to degrade performance for other tenants.
API and RPC Throttling: Executing unthrottled Remote Procedure Calls (RPC) or API requests that threaten system stability. As a standardized baseline, API integration queries must be limited to a sustained rate of one (1) request per second, executed sequentially without parallel threads. High-volume batch data ingestion must utilize designated bulk endpoints.
Resource Overloading: Intentionally stressing system memory, CPU capacity, or disk I/O through synthetic data inflation, such as log flooding or email bombing.
Capacity Thresholds: Production database environments exceeding one hundred (100) gigabytes (GB) of raw storage will trigger an internal architecture review. In such events, clients may be required to optimize storage structures, remove historical telemetry, or transition to a dedicated enterprise-tier metered storage solution.
Automated Scraping and Registration: Deploying automated crawlers or scraping daemons that degrade platform availability, or utilizing automated scripts to generate fraudulent account registrations.
5. Enforcement and Reporting
To report infrastructure abuse or a violation of this policy originating from the relyd network, please submit all technical logs and evidence to our dedicated security desk: abuse@relyd.co