Creator Guidelines
Identity Armor exists to protect creators, not restrict them. These guidelines establish the practices, standards, and rules that keep the registry trustworthy, the licensing ecosystem fair, and the platform safe for every creator who anchors their identity here.
Effective Date: July 1, 2025 | Last Updated: July 26, 2025 | Version 1.0
Core Principle: Every registered identity on Identity Armor belongs exclusively to the person who created it. Our role is to make that ownership provable, enforceable, and commercially viable — not to gatekeep or profit from your creative output beyond our disclosed platform fee.
1. Safe Asset Anchoring Practices
Anchoring is the act of permanently registering a digital asset fingerprint into the Identity Armor registry. Follow these practices to ensure your registration is valid, defensible, and maximally protected.
Asset Quality Standards
- ›3D Meshes & Avatars: Submit in standard interchange formats (FBX, GLB, OBJ, VRM). Include rig hierarchy and blend shape data where applicable. Higher-fidelity source files produce more unique fingerprints and are harder to spoof.
- ›Voice Baseline Masters: Submit uncompressed or losslessly-compressed audio (WAV, FLAC) at minimum 44.1 kHz / 16-bit. Recordings should include a minimum of 60 seconds of continuous speech across varied phonetic contexts. Avoid heavily processed or pitch-corrected masters — the baseline must represent your natural voice.
- ›Headshot & Photo Reference Sets: Submit the highest-resolution originals available. Include a minimum of 8 photos across varied lighting conditions, angles, and expressions. Photos must clearly show the face, be unobstructed, and not have AI-enhancement filters applied.
- ›Do not compress, transcode, or reduce resolution before uploading. Original source files produce the strongest fingerprint signatures.
File Security Pre-Upload
- ›Ensure your device is free of malware before uploading — compromised systems may expose your assets during the upload process.
- ›Use a secure, private network (avoid public Wi-Fi) when uploading sensitive vault assets.
- ›After uploading, verify your vault fingerprint hash matches the hash of your original local file. Identity Armor displays this hash in the registry confirmation screen.
2. Proof-of-Ownership Requirements
Identity Armor requires verified proof of ownership before generating an Identity Token for any asset type. This prevents fraudulent registrations and protects legitimate creators from impersonation.
Proof-of-ownership verification must be completed before your Identity Token is issued. Assets uploaded but not verified are held in a quarantine state and do not receive registry protection.
- 01
Identity Verification
Confirm your legal identity via government-issued ID or verified social account linkage (YouTube, Twitch, Twitter/X, or LinkedIn with established account age). This links your legal person to the registered digital identity.
- 02
Asset Provenance Documentation
For 3D avatars: submit original project files (Blender .blend, Maya .ma, etc.), commissioner agreements, or a dated portfolio trail demonstrating creation history. For voice: submit original recording session files with metadata, or a live verification sample recorded on demand via our in-browser recorder. For photos: submit originals with EXIF metadata intact, or photographer release forms.
- 03
Live Challenge Verification (Voice & Face)
For voice and facial asset registration, Identity Armor performs a live challenge — we issue a randomized phrase or pose prompt that you must record/photograph in real-time. This prevents replay attacks and confirms the registrant is the actual asset owner.
- 04
Review & Issuance
Our verification team reviews submitted documentation within 1-3 business days. Upon approval, your Identity Token is issued and the asset fingerprint is anchored to the tamper-evident registry.
If ownership of a registered asset is disputed by a third party with credible documentation, Identity Armor may temporarily freeze the token pending adjudication. Both parties will be notified and given 14 days to submit evidence.
3. Adult & Mature Content Licensing
Identity Armor supports creators who produce adult or mature content in contexts where it is legal and regulated. This section governs the rules for enabling and operating the mature content licensing toggle.
Adult content licensing is OFF by default for all accounts. Enabling it requires age verification and active acknowledgment of the rules below. Violation of these rules results in immediate toggle revocation and may result in account termination.
Eligibility to Enable
- ›You must be at least 18 years of age. Identity Armor requires age verification (government ID cross-reference) before enabling adult content licensing.
- ›The assets you are licensing under the mature content toggle must feature only consenting adults. You must retain documentation confirming the age and consent of any depicted persons.
- ›You must be operating in a jurisdiction where adult content production and licensing is legal.
Scope of the Toggle
- ›The mature content toggle permits licensees to request access to your avatar, voice, or likeness for use in adult-rated productions that meet applicable platform policies.
- ›You retain granular control: you may restrict mature content licenses to specific asset types (e.g., voice only), specific Licensee categories (e.g., verified adult studios only), or specific use case descriptions.
- ›Each mature content license must contain an explicit use-case description. Generic or ambiguous license scope is not permitted for mature content deals.
- ›Identity Armor does not host, store, or distribute any adult content produced under these licenses. We license the identity asset; what the Licensee creates with it under their license terms is their legal responsibility.
Absolute Prohibitions
- ›No mature content license may be issued for any production depicting minors in sexual or sexually-adjacent contexts. This is a zero-tolerance absolute prohibition.
- ›No mature content license may be issued for non-consensual scenarios without explicit documentation of real-world performer consent.
- ›Enabling the mature content toggle does not override any other platform restriction or legal obligation.
4. Watermark Enforcement & Legal Evidence Bundles
Identity Armor embeds steganographic digital watermarks into all assets delivered to Licensees under active license agreements. These watermarks are invisible to the human eye but detectable by our scanner infrastructure.
How Watermarking Works
- ›When a license is activated and assets are delivered to a Licensee, Identity Armor applies a watermark encoding: the creator's identity token ID, the license deal ID, the Licensee's account ID, the delivery timestamp, and a cryptographic signature.
- ›Watermarks are embedded at multiple layers: pixel/spectral domain (images/audio), mesh geometry (3D assets), and metadata headers. This multi-layer approach makes watermarks resilient to common removal attacks (re-encoding, cropping, compression).
- ›You can run a watermark scan on any suspected unauthorized use of your assets via the Scanner tool in your dashboard. Upload the suspect content and the scanner will attempt to extract and decode any embedded Identity Armor watermark.
Evidence Bundle Compilation
When unauthorized use is detected, Identity Armor automatically compiles a Legal Evidence Bundle (LEB) for use in DMCA takedowns, platform abuse reports, and civil litigation.
A standard LEB contains:
- ›Original asset registration record: timestamp, fingerprint hash, and registry transaction ID.
- ›Scanner analysis report: the detected watermark payload, confidence score, and chain-of-custody from the original licensed delivery.
- ›Side-by-side forensic comparison: visual/spectral overlay of the original registered asset against the infringing content.
- ›License audit log: proof that no active license authorizing the detected use is on record.
- ›Cryptographic proof certificate: a signed attestation generated by Identity Armor confirming the above, suitable for inclusion in legal filings.
To initiate an evidence bundle and takedown request, navigate to Scanner › Report Infringement in your dashboard, or email ghostrender_support@proton.me with subject line "Infringement Report" and include the suspected infringing URL or file.
DMCA & Platform Takedown Process
- ›Identity Armor will file DMCA takedown notices on your behalf to platforms hosting infringing content, using your LEB as supporting documentation.
- ›Platform response times vary (typically 1-14 business days). Identity Armor will notify you of responses and escalation options.
- ›For persistent or high-severity infringement, Identity Armor can refer your case to our network of digital rights attorneys for civil action consultation.
5. Scanner Ethics & Responsible Use
The Identity Armor scanner infrastructure is a powerful tool. We require that it be used responsibly:
- ›The scanner may only be used to scan content you have reason to believe infringes on your own registered assets.
- ›Using the scanner to investigate assets you do not own or have not licensed is prohibited and may result in account suspension.
- ›Repeated bad-faith scanner submissions (e.g., mass-scanning for intelligence gathering unrelated to your assets) will trigger rate limits and may prompt account review.
- ›Scan results are not legal opinions. Consult a qualified attorney before initiating legal proceedings based on scanner output.
6. Community Standards & Enforcement
Identity Armor is a professional platform for serious creators. We expect all community members to operate in good faith:
- ›Treat other creators with respect in any shared community spaces or public registry interactions.
- ›Do not file fraudulent infringement reports against other creators. Bad-faith reports will result in account termination.
- ›Report suspected platform abuse, security vulnerabilities, or policy violations to ghostrender_support@proton.me.
- ›Identity Armor reserves the right to update these guidelines at any time. Material changes will be communicated with 14 days' notice.
Questions about these guidelines? Contact us at ghostrender_support@proton.me