<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0"
  xmlns:atom="http://www.w3.org/2005/Atom"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Security - YossGate Blog</title>
    <link>https://yossgate.com/blog/tags/security/</link>
    <description>Security</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 06 Sep 2026 12:58:01 &#43;0000</lastBuildDate>
    <atom:link href="https://yossgate.com/blog/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Acceptable Use Policy</title>
      <link>https://yossgate.com/blog/policies/acceptable-use-policy/</link>
      <pubDate>Sun, 01 Mar 2026 00:00:00 &#43;0000</pubDate>
      <guid>https://yossgate.com/blog/policies/acceptable-use-policy/</guid>
      <description>Review the YossGate Acceptable Use Policy (AUP). Understand prohibited activities, AI abuse prevention guidelines, and compliance requirements.</description>
      <content:encoded><![CDATA[<p>This Acceptable Use Policy (the &ldquo;Policy&rdquo;) governs your access to and use of the services provided by <strong>YossGate Team</strong> (&ldquo;YossGate&rdquo;, the &ldquo;Company&rdquo;, &ldquo;we&rdquo;, &ldquo;us&rdquo; or &ldquo;our&rdquo;), including our unified AI API aggregation platform, developer console, documentation, and related services available at <strong>yossgate.com</strong> (collectively, the &ldquo;Service&rdquo;).</p>
<p>This Policy supplements, and forms an integral part of, our <a href="../terms-of-service/">Terms of Service</a>
. By accessing or utilizing the Service, you agree to strictly comply with this Policy.</p>
<hr>
<h2 id="1-scope">1. Scope</h2>
<p>This Policy applies to all access and use of the Service to generate, process, transmit, route, or store text, images, audio, video, code, and any other data or content. It applies to every account holder, developer, organisation, and any end users to whom you make the Service available through your own applications, software, or integrations.</p>
<hr>
<h2 id="2-prohibited-content-and-uses">2. Prohibited Content and Uses</h2>
<p>You must not use the Service, and must not permit, authorise, or facilitate any third party or end user to use the Service, to create, upload, process, transmit, distribute, or facilitate any of the following:</p>
<ul>
<li><strong>Child Sexual Abuse Material (CSAM) or Exploitation:</strong> Any material involving child sexual abuse, sexual exploitation of minors, or non-consensual sexual content.</li>
<li><strong>Violence, Harm, and Terrorism:</strong> Content that promotes, incites, glorifies, or provides actionable instructions for violence, terrorism, self-harm, suicide, or hate speech targeting protected characteristics.</li>
<li><strong>Illegal Acts and Cyberattacks:</strong> Facilitating illegal activities, developing malicious code, malware, ransomware, exploits, or conducting fraud, phishing, scamming, unauthorized penetration testing, or financial crimes.</li>
<li><strong>Intellectual Property and Misrepresentation:</strong> Content that infringes copyrights, patents, trademarks, or trade secrets, or that impersonates any brand, entity, or individual.</li>
<li><strong>Disinformation and Deceptive Practices:</strong> Disinformation campaigns, deceptive synthetic media (deepfakes), social engineering, or unlawful public opinion manipulation.</li>
<li><strong>Privacy Violations:</strong> Unauthorized harvesting, scraping, or processing of personally identifiable information (PII) or sensitive personal data in violation of applicable data protection laws.</li>
<li><strong>Circumvention and Abuse:</strong> Any attempt to circumvent, bypass, or defeat rate limits, security barriers, authentication safeguards, access controls, or filtering mechanisms imposed by YossGate or upstream model providers.</li>
<li><strong>Violations of Upstream Terms:</strong> Any activity that violates the published terms of service or acceptable use policies of the underlying AI model providers (including but not limited to OpenAI, Anthropic, Google DeepMind, and Meta).</li>
</ul>
<hr>
<h2 id="3-content-controls-and-moderation">3. Content Controls and Moderation</h2>
<p>To safeguard the platform and downstream users, YossGate reserves the right to apply reasonable technical and operational controls to API requests and responses, including automated filtering, anomaly detection, rate limiting, and temporary logging for security triage.</p>
<p>YossGate does not proactively monitor all real-time API payloads, but we reserve the right to audit suspicious activity where necessary to preserve service stability, protect users, and comply with binding legal obligations.</p>
<hr>
<h2 id="4-enforcement-and-penalties">4. Enforcement and Penalties</h2>
<p>If we determine or reasonably suspect that you or your end users have violated this Policy, we may take one or more of the following actions depending on the severity of the violation:</p>
<ol>
<li>Issue a formal warning or notice to cure;</li>
<li>Temporarily restrict, throttle, or disable access to specific models, tokens, or endpoints;</li>
<li>Suspend or freeze account balance, API keys, or credits;</li>
<li>Terminate the account permanently without refund for breach of terms;</li>
<li>Report unlawful conduct to competent law enforcement agencies where required by applicable law.</li>
</ol>
<hr>
<h2 id="5-reporting-violations-and-appeals">5. Reporting Violations and Appeals</h2>
<p>If you discover suspected violations of this Policy, or if you believe an enforcement action was made in error and wish to appeal, please contact our review team:</p>
<ul>
<li><strong>Abuse and Compliance Email:</strong> <a href="mailto:support@yossgate.com">support@yossgate.com</a>
<br>
<em>(Please include &ldquo;Abuse Report&rdquo; or &ldquo;AUP Appeal&rdquo; along with relevant request IDs or details in the subject line).</em></li>
</ul>
<p>All reports will be assessed in accordance with our internal review procedures.</p>
<hr>
<h2 id="6-developer-and-customer-responsibility">6. Developer and Customer Responsibility</h2>
<p>You remain solely and strictly responsible for all activity conducted under your account credentials and API keys. If you integrate the Service into your own products or customer-facing applications, you must implement appropriate application-level safety filters, rate limiting, and enforce end-user terms that are at least as restrictive as this Policy.</p>
<hr>
<h2 id="7-modifications">7. Modifications</h2>
<p>We may modify this Policy periodically to reflect evolving legal standards, security threats, or upstream provider guidelines. Continued use of the Service following the publication of revised terms constitutes your acceptance of the updated Policy.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
