69 lines
7.6 KiB
HTML
69 lines
7.6 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="UTF-8">
|
||
<title>Security & Privacy Policy — HypnoSVG</title>
|
||
</head>
|
||
<body>
|
||
TEMPORARY DRAFT
|
||
|
||
<h1>Security & Privacy Policy (SECURITY)</h1>
|
||
|
||
—teaser:
|
||
|
||
<p>We don’t know who you are… and we don’t want to know. The Hypn0.xyz (HypnoSVG) platform operates in strict compliance with Inter­galactic DOOP Protocols and GDPR directives, adhering to the Zero Personally Identifiable Information (Zero-PII) doctrine. No registration, logins, passwords, emails, SMS, or phone numbers. The database contains zero user or account tables. Synthesized SVG files contain purely mathematical coordinates of vector primitives and inline CSS animations. No source image metadata is embedded (EXIF tags, geolocation, and hardware device profiles are purged during raster­ization).</p>
|
||
<h2>Prologue: The Anatomy of Privacy in the Age of Mental Resonance</h2>
|
||
<p><em>We are the Hypnotoad, the Brain Slugs, and the Receptors of Planetary Mind-Numbing. And we don’t want to know who you are. Don’t even try to persuade us.</em></p>
|
||
<p>The Hypn0 platform is engineered from the ground up on the <strong>Zero-PII (Zero Personally Identifiable Information)</strong> doctrine. We do not require registration, logins, passwords, email addresses, or phone numbers. In the project database, user and account tables simply do not exist. Generated SVG files contain only mathematical coordinates of geometric primitives and inline CSS keyframes. Zero metadata from source images is retained (EXIF tags, GPS coordinates, device specs, and even source file names are completely stripped during raster­ization).</p>
|
||
<hr/>
|
||
<h2>Section I. No-Consent Mode (Default / No-Tracking)</h2>
|
||
<p>If you have not clicked the “<strong>Submit to Hypnotoad!</strong>” button—you are completely invisible in the astral realm. This means:</p>
|
||
<ol>
|
||
<li>Hypn0 (HypnoSVG) does not deploy <strong>any client identifiers</strong>. Neither cookies nor browser <code>localStorage</code> records are created.</li>
|
||
<li><strong>External analytics systems are disabled</strong>: tracking beacons and metric counters (Google Tag Manager, analytics scripts, etc.) are blocked at the template level and physically never loaded onto the client device.</li>
|
||
<li><strong>Server logs</strong>—the only baseline telemetry captured by infrast­ructure (IP address, User-Agent, requested URL, and timestamp) — are utilized strictly for DDoS defense and uptime monitoring, retained for a minimal duration with regular rotation faster than memories fade after a hypnosis session.</li>
|
||
</ol>
|
||
<hr/>
|
||
<h2>Section II. Restrictions for Free Humanoids Without a Brain Slug</h2>
|
||
<p>Humanoids who decline tracking or withhold explicit consent can freely use the local vector generator and browse the gallery. However, they <strong>cannot access pseudo-social platform features</strong>:</p>
|
||
<ul>
|
||
<li>Publishing original works to the public “<a href="/gallery">Trance Gallery</a>”;</li>
|
||
<li>Voting for artworks (transmitting psychic resonance / likes);</li>
|
||
<li>Submitting complaints or flagging spam and non-transcendent content.</li>
|
||
</ul>
|
||
<h3>Reason for Restrictions: Anti-Abuse & Bot Defense</h3>
|
||
<p>To operate the gravit­ational Brain Slug sorting algorithm (curated ranking) and fairly distribute artworks across tiers (“Incubator”, “Approved by Brain Slug”, “Deep Trance Hall of Fame”), the platform requires a unique anonymous client anchor.</p>
|
||
<p>Because a humanoid who has not “surrendered to the Hypnotoad” carries no device anchor, the Lord of Mental Intros­pections (the server) cannot recognize duplicate votes. This would lead to instant scripted vote tampering, spam surges, and the destabi­lization of the entire gallery ecosystem.</p>
|
||
<hr/>
|
||
<h2>Section III. Consent Mechanism via “Submit to Hypnotoad!”</h2>
|
||
<ol>
|
||
<li>The browser generates a cryptog­raphic pseudo-random identifier via <code>crypto.randomUUID()</code> (UUID v4).</li>
|
||
<li>The value is stored in a cookie and/or browser <code>localStorage</code> under the key <code>hypn0_vid</code>.</li>
|
||
<li>The lifespan is configured for two Earth years, with transmission flags set to safe mode (<code>path=/; SameSite=Lax</code>).</li>
|
||
<li>The <code>hypn0_vid</code> token is a purely random string and cannot be linked to your real identity, physical vessel, or cerebral Theta/Alpha brainwaves.</li>
|
||
<li>The identifier is used by the backend exclusively for rate limiting and enforcing the “one vote per artwork per browser” rule.</li>
|
||
</ol>
|
||
<hr/>
|
||
<h2>Section IV. File Processing Security during SVG Generation</h2>
|
||
<ul>
|
||
<li><strong>Input Data Sanitization (Source Images):</strong> All inbound images pass through the Pillow mental shredder, decoded exclusively in RAM, and immediately cleansed of mundane metadata. No EXIF tags, geolocation, camera models, or temporary disk artifacts remain on server storage.</li>
|
||
<li><strong>Output Vector Security:</strong> The server stores only vector artworks synthesized by the native Hypn0 (HypnoSVG) core. Output SVGs are generated strictly program­matically and contain no <code><script></code> tags, external <code>xlink:href</code> links, or event handlers like <code>onload</code> or <code>onclick</code>. This eliminates Stored XSS risks when viewing other humanoids’ works: foreign halftones are completely harmless to your optic nerves (aside from the risk of spontaneous hypnotic trance).</li>
|
||
<li><strong>Resource Limits (DoS Prevention):</strong> Strict thresholds are? enforced on maximum upload size, grid density (<code>cols</code>), and element radii, preventing memory exhaustion and overheating of New New York processors.</li>
|
||
</ul>
|
||
<hr/>
|
||
<h2>Epilogue: Matrix Anomalies & Vulner­ability Disclosure</h2>
|
||
<p>If you discover a security flaw capable of bypassing the will of the Hypnotoad or injecting alien code into the consciousness of Hypn0 — please approach disclosure with utmost inter­galactic respon­sibility:</p>
|
||
<ul>
|
||
<li>Do not publish vulner­ability details publicly, preventing space pirates and rogue bots from exploiting them before a patch is deployed.</li>
|
||
<li>Send a detailed report to the project maintainer via the <a href="https://github.com/erjemin/2026-hypn0-site/issues" target="_blank">repository issue tracker</a> marked as security, or directly to the <a href="#" id="c-l" onclick="this.href='ma'+atob('aWx0bzplcmplb'+'WluQGdtYWlsLmNvbQ==');">admin­istrator’s email</a>.</li>
|
||
<li>Describe attack vectors, step-by-step reproduction (PoC), and potential system impact.</li>
|
||
<li>We will promptly acknowledge receipt and neutralize the anomaly. Please refrain from public disclosure until the vulner­ability is resolved.</li>
|
||
</ul>
|
||
|
||
<hr/>
|
||
<hr/>
|
||
<hr/>
|
||
<hr/>
|
||
|
||
</body>
|
||
</html> |