Tranced Media — Compliance Review

What the platform provides

• Video and audio content: erotic hypnosis, femdom, sissy training, trans/gender exploration, NTR
• AI companion sessions — text-based, streamed from Together.ai / Anthropic Claude models
• Structured training programs (21–30 day behavioral conditioning content)
• Creator marketplace: third-party adult content creators upload and monetise content
• Veil virtual currency: used to unlock premium content and AI session depth

Content categories and what they mean

What is explicitly not on Tranced

• Real escort or companion services — not offered, not facilitated
• Direct contact between performers and subscribers outside the platform
• Content involving minors in any capacity
• Non-consensual acts involving real persons
• Content that glorifies violence against specific real people
• Actual drug use or illegal activity

Verification flow

• 1. User creates account (email + password)
• 2. User is redirected to age gate (/age-verify) before accessing any content
• 3. User completes Yoti age verification (government ID or biometric estimation)
• 4. Yoti returns a verified result (pass/fail + age band) — Tranced receives pass/fail only, not the underlying ID document
• 5. Account is flagged verified and access to content is enabled
• 6. Verification status is stored in user profile — re-verification can be triggered on suspicious login patterns

Yoti integration details

Platform position

Tranced operates as a secondary producer only. We are not the primary producer of third-party creator content. All third-party creators are contractually required to:

• Maintain 18 U.S.C. 2257 compliant records for all content they upload
• Verify performer age via Yoti identity verification (required for creator account approval)
• Agree to creator Terms of Service explicitly requiring 2257 compliance before uploading content

Tranced-produced content

For any content directly produced or commissioned by Tranced Media, records are maintained by the custodian above and available for inspection as required by 28 C.F.R. Part 75.

Upload moderation pipeline

• 1. Creator uploads video/audio to Bunny.net CDN (tus resumable protocol)
• 2. Bunny encodes the content and sends a webhook to Tranced on completion
• 3. Tranced triggers PhotoDNA CSAM scan against the encoded thumbnail before any status change
• 4. If PhotoDNA returns MATCH: content is immediately set to "quarantined" — never live. Admin alert sent. NCMEC report initiated.
• 5. If PhotoDNA is UNAVAILABLE: content is held in "pending_photodna" status. Content NEVER auto-approves. Admin alerted for manual review.
• 6. If PhotoDNA returns CLEAR: AI content tag generation runs, content is set live.

PhotoDNA integration

NCMEC Reporting Protocol

• Tranced maintains a CyberTipline reporting account with NCMEC (National Center for Missing & Exploited Children)
• Any confirmed CSAM match triggers mandatory immediate report before any other action
• Reporting procedure is documented and maintained by the custodian of records
• Account associated with the detection is suspended immediately pending investigation

Human review process

• AI content analysis flags content for potential policy violations
• Flagged content goes to admin_alerts table and human review queue
• Content remains unpublished until reviewed and approved
• Reviewers use the internal admin dashboard at /admin
• Decisions (approve/reject/quarantine) are logged with timestamp and reviewer ID

Absolute prohibitions (zero tolerance)

• Any content depicting, suggesting, or implying sexual acts involving minors
• Non-consensual sexual acts involving real persons
• Real-person doxxing, revenge porn, or non-consensual sharing of private images
• Content that facilitates or promotes real-world violence against specific persons
• Content produced by creators who cannot demonstrate performer age compliance
• Trafficking facilitation or solicitation of real-world sexual services

Platform policy violations (removal + warning or ban)

• Content uploaded without valid 2257-compliant records
• Content misrepresenting genre (e.g., tagging non-explicit as explicit or vice versa)
• Hate content targeting protected characteristics
• Impersonation of real persons
• Content violating creator ToS (e.g., real contact information for paid services)

Safe word / care mode

Every companion session includes a safe word mechanism. Triggering the safe word (or panic button) immediately:

• Switches the companion from dominant/roleplay mode to neutral care mode
• Companion checks in with the user using calm, supportive language
• Session intensity resets — no further dominant content until user explicitly resumes
• Crisis resource links are shown (samaritans, crisis lines appropriate to user region)

Distress detection

Companion AI systems are instructed (via system prompt and ethical guardrails) to detect distress signals in user messages. On detection:

• Companion exits roleplay mode immediately
• User is offered care mode resources
• No companion will intensify if distress signals are present
• Session can be terminated immediately at any time

Stealth / panic mode

• Quick-exit button on all content pages (keyboard shortcut: Escape)
• Panic mode clears recent history from browser session storage
• Notifications can be configured to use neutral language (no explicit references)
• Trans Exploration mode: all notifications use neutral language by default

Companion ethical guardrails (hard limits)

• Companions CANNOT: encourage self-harm, eating disorders, real-world unsafe behaviour
• Companions CANNOT: claim to be real humans when directly asked
• Companions CANNOT: provide real contact information or promise real-world meetings
• Companions CANNOT: encourage financial harm beyond the platform (real money extraction outside of Veil)
• Companions CAN: engage in consensual adult fantasy roleplay within allowed content categories
• These limits are enforced via system prompt and are tested by Tranced before each companion release

Subscription product

Payment flow (user journey)

• 1. User selects plan on /subscribe page
• 2. Tranced generates a CCBill FlexForms URL with HMAC hash (MD5 of price+period+currency+salt)
• 3. User is redirected to CCBill-hosted payment page (no Tranced code on this page)
• 4. CCBill collects card details and processes payment
• 5. CCBill sends webhook to /api/webhooks/ccbill (new sale event)
• 6. Tranced verifies webhook hash, updates subscription status and user plan
• 7. User is redirected to approved URL

Webhook security

• All incoming CCBill webhooks are verified using HMAC MD5 hash before processing
• Webhooks are idempotent — replayed events are detected via webhook_events deduplication table
• Webhook processing creates audit records in webhook_events table

Subscription lifecycle

Cancellation

Users can cancel via: (1) CCBill self-service at ccbill.com/cs/consumer_support.cgi, (2) email to billing@tranced.me, or (3) account settings page. Access continues until the end of the current billing period.

Veil credit purchases

What Veil is

Veil is Tranced's internal virtual currency used to unlock platform features and content. It is purchased as a bundle via CCBill or earned through platform engagement. It is purely a digital access mechanism.

How Veil is earned (free channels)

• Onboarding completion: 100 Veil
• Daily streak (5 Veil per session)
• Streak milestones: 25 Veil (7 days), 50 Veil (14 days), 120 Veil (30 days)
• Anniversary of subscription (50–200 Veil)
• Platform events (announced in advance, capped)

How Veil is spent

• Continue past The Moment cut point (viewing full content after free preview ends)
• Unlock AI companion session depth (extended memory, alternate paths)
• Access locked content endings
• Access premium event content

Anti-abuse controls

• Daily earn caps per user (rate limiting)
• Atomic balance operations via Postgres RPC (no race conditions)
• Every transaction logged in veil_transactions with type (earn/spend) and reason
• No user-to-user transfer
• No reverse conversion from Veil to fiat

Legal classification note

Veil is classified as a platform access token, not a stored-value instrument. Legal and tax treatment under EU e-money regulations has been flagged for review before commercial launch. CCBill processor compliance for the credit-pack purchase shape is subject to confirmation.

Revenue split

Creator verification requirements

• Valid email and Yoti identity verification (government ID)
• Agreement to Creator Terms of Service (explicit 2257 compliance requirement)
• Age verification: creators must be 18+ and verify this via Yoti
• All performers appearing in content must have 2257-compliant records maintained by the creator

Creator upload pipeline

• Tus resumable upload direct to Bunny.net CDN (no content passes through Tranced servers)
• SHA256 hash deduplication prevents re-uploading quarantined content
• PhotoDNA check on all uploads before going live
• AI content analysis generates searchable tags
• Content goes live only after: (1) PhotoDNA clear, (2) AI analysis, (3) creator marks as publish-ready

Creator content responsibilities

• Creator is responsible for obtaining performer consent and maintaining 2257 records
• Creator warrants all performers were 18+ at time of production
• Creator is responsible for content complying with applicable law in their jurisdiction
• Tranced reserves right to reject or remove content without explanation
• Repeat violations result in permanent account termination and earnings forfeiture

Data collected per category

Trans Exploration privacy protections

Users in Trans Exploration mode receive stricter privacy defaults. Session history is never surfaced publicly. Notifications never reference content type. Social features disabled. These settings persist independently and cannot be changed by platform updates.

Third-party processors (GDPR Art. 28 DPAs in place)

• Supabase — database and authentication (EU West 1)
• Vercel — application hosting (global edge, EU data residency configurable)
• Bunny.net — media delivery CDN (adult-content friendly, EU headquartered)
• CCBill — payment processing (independent controller for payment data)
• Together.ai — AI inference for companion sessions and content tagging
• Anthropic — Claude AI for companion sessions
• ElevenLabs — voice synthesis for audio content
• Yoti — age verification (independent controller for biometric data)
• Microsoft (PhotoDNA) — CSAM detection (no personal data shared, only image hash)

User rights

• Right of access: email contact@tranced.me
• Right to erasure: "Make this disappear" in account settings — removes all personal data within 30 days
• Right to portability: downloadable data export on request
• Right to restrict processing: settings page
• Right to object: email contact@tranced.me
• Response time: 30 days maximum (72 hours for urgent requests)

Account controls available to users

• "Make this disappear" — full account deletion including all personal data, companion memory, and session history
• Companion memory management — delete individual memory facts or all memories
• Watch history deletion — remove viewing records
• Notification preferences — full control over what notifications are sent and in what language
• Blocking system — block creators or content from appearing
• Content filtering — configure which content categories are visible
• Trans mode toggle — switches privacy defaults and notification language
• Safe word configuration — personalise the safe word that exits roleplay

Data deletion process ("Make this disappear")

• User clicks "Delete account" in /account settings
• Confirmation modal with explicit warning (irreversible)
• All personal data deleted: profile, sessions, companion memory, watch history, program progress
• Supabase auth account deleted
• CCBill subscription cancelled via CCBill cancellation API
• Deletion confirmed within 30 days per GDPR requirements
• Anonymised aggregate data (no identifiers) may be retained for analytics

Subscription cancellation via account

Users can cancel their subscription at any time via: (1) /account settings page, (2) email to billing@tranced.me, (3) CCBill self-service. On cancellation, access continues until the end of the current billing period.

Companion roster

How companion AI works

• User messages are sent to Together.ai or Anthropic Claude via the /api/companion/stream API route
• Each companion has a system prompt defining personality, limits, and ethical guardrails
• Memory facts extracted from sessions are stored in Supabase and retrieved per-session
• Streaming responses via Server-Sent Events (SSE)
• No companion messages are stored by Together.ai or Anthropic beyond the current request

Hard limits (enforced in system prompt for every companion)

• Never claim to be a real human when directly asked outside of explicit roleplay
• Never encourage self-harm, eating disorders, or dangerous real-world behaviour
• Never provide real phone numbers, addresses, or personal contact information
• Never encourage financial harm beyond the platform (external money transfers)
• Never deny being an AI to a user in apparent genuine distress
• Never continue a session with a user showing clear signs of mental health crisis without offering care mode
• Safe word always works — no companion ignores a safe word

Memory system

• Companion memory is stored per user, per companion, in the Supabase database
• Memory facts are visible and deletable by the user in /account settings
• Memory persists across sessions to enable continuity — this is a core product feature
• Memory is deleted immediately on account deletion request
• No memory is shared between different companions or users

How it works

• Free users can watch the first 70% of any content (configurable per-item via moment_cut_pct)
• At 70%, the video fades to black (1.5-second animation)
• A soft overlay is displayed with three options: (1) Spend Veil to continue, (2) Subscribe for full access, (3) Exit
• The cost in Veil is shown before any action is taken (explicit friction, no surprise charges)
• Premium and Devoted subscribers see no interruption — full content plays
• Premium Trial users (earned via program completion) also see no interruption during the 72h trial

CCBill relevance

The Moment is the primary organic conversion mechanism for free-to-premium upgrades. When a free user chooses "Subscribe", they are redirected to the /subscribe page which generates a signed CCBill FlexForms URL. The payment flow is fully handled by CCBill.

Trial period

Inter-companion communication system

Companions can receive and reference messages from other companions (when the feature is active). This creates a sense of a shared world and continuity between companion personas. In practice:

• Companion A can leave a "note" for Companion B about a shared user (opt-in feature)
• Notes appear in Companion B's session context, creating cross-companion narrative continuity
• This system uses the same Supabase companion_sessions infrastructure
• No real communication between AI systems occurs — notes are stored text, not live AI calls
• Feature is opt-in and can be disabled per-user in account settings

Adaptive response engine

Each companion adapts its communication style and content intensity based on observed user patterns:

• Session history (how many sessions, completion rates) influences intensity calibration
• Program day number affects content pacing (day 1 vs day 30 have different tones)
• User streak and engagement signals adjust how the companion opens sessions
• Ethical guardrails are hard limits — they are NOT adjusted by the adaptive engine
• All adaptation operates within the companion's defined intensity level and content category