Private storage
Uploads and outputs are not published by default.
Loading PornWorks content
PornWorksPrivate AI porn workspace
Create, edit, enhance and chat in one account
Loading PornWorks content
Privacy
This page describes the current PornWorks product behavior without promising controls that have not been built.
Last updated 2026-10-01
Send privacy questions or requests concerning PornWorks to this contact. You can email us without creating an account.
Uploads and outputs are not published by default.
Private conversations are excluded from search surfaces.
Usage and job records support delivery, security, and billing.
When you sign in, PornWorks receives an account identifier, email address, and display name from the identity provider. The service also processes your saved nickname, identity and pronouns, reply-language choice, adult-consent record, prompts, chat messages, uploads, generated results, character settings, notification choices, usage records, plan status, and limited technical signals needed to prevent repeated free-trial abuse. Unsubmitted Studio settings and character drafts may be kept temporarily in this browser’s session storage so sign-in or navigation does not erase your work; uploads, face references, and consent checkboxes are not restored from those drafts. For an eligible no-account image, the browser stores an opaque job identifier and a secure, HttpOnly job cookie instead of placing the private media credential in a page URL or browser-readable storage. Same-browser anonymous access ends no later than 30 days after creation and can end sooner if browser data is cleared.
Signed-in conversation history and saved characters are associated with your account. PornWorks stores generated images, videos, optional character-voice audio, and media you attach to a saved chat in private object storage and serves them through controlled responses rather than public file listings. A chat attachment remains with that conversation until its message, conversation, or account is deleted; an uploaded file that is never sent can be removed from the composer and is automatically eligible for cleanup. An attached image and its caption may be processed together so the character can respond to visible image details; image interpretation can be incomplete or wrong. An attached video is subject to file and ownership checks and stored with the saved conversation, but its frames and audio are not provided to the character in this version; the character replies from the caption. Short-lived, reply-bound access to a chat image expires and is not stored in the message. Character voice converts the selected saved reply into audio; this version does not accept voice-cloning samples. On supported browsers, the composer offers two device-speech controls. The ordinary microphone adds one transcript to the draft for review and never sends it automatically. If you explicitly start hold-to-talk voice Beta, the microphone opens only while you hold the talk control; releasing sends one final transcript as a normal chat turn through the same conversation history, limits, adult-consent gate, and reply review as typed chat. The browser or operating system may then read the reply after the local text checks, but playback never reopens the microphone automatically. Hiding or leaving the page, switching away from the browser window, going offline, canceling a hold, or reaching the 30-second hold limit stops capture without sending that unreleased spoken draft and stops device playback. A turn already submitted can still complete through the normal chat path and may appear in conversation history, but its reply will not begin device playback after that lifecycle pause. Ending the Beta stops microphone capture and device playback. Both controls use the browser or operating system speech service, which may process microphone audio under its own privacy terms. PornWorks receives the resulting text but does not store the original microphone recording for either control. Hold-to-talk voice Beta is a half-duplex device-speech preview, not a live, continuous, or WebRTC call. To perform a requested AI task, an upload, prompt, or output may pass through an AI processing provider. Text-based rules and file or permission checks do not mean that every uploaded or generated image, video, or audio file receives visual or human content review. Unused Studio source uploads can be removed from Studio, and PornWorks stops accepting every Studio source pointer after seven days; records attached to completed jobs are stripped of the source URL and original filename by maintenance. Removing your PornWorks copy does not guarantee immediate physical deletion from a processor system, whose operational retention may continue under its terms. A character appears publicly only after you choose public visibility and it passes review.
For signed-in users, PornWorks records a relationship count and stage for each character after a saved assistant reply. Cross-chat memory is off by default. If you enable it, your editable continuity notes may be included as low-trust reference context in later chats with that character; if you separately enable automatic learning, a background AI task periodically proposes a concise summary of stable preferences, explicit boundaries, relationship tone, and non-graphic story continuity. These notes can be incomplete or wrong, never establish age or current consent, and are not visible to a character Creator. You can review, correct, disable, or reset them from Account or the chat header. Disabling memory stops use without deleting the notes. Reset clears the relationship, turns memory off, and keeps a private deletion marker so older chats cannot silently teach forgotten content back into memory. Because the current summary does not attach each sentence to one source thread, deleting any saved chat with a character resets that character’s complete relationship and memory so deleted content cannot remain in later prompts.
Creating a Creator profile stores a unique handle, required display name, optional biography, review state, moderation note, publication timestamps, and the account relationship needed to manage it. The handle, approved display name and biography, public character attribution, character count, and aggregate follower count may appear on public and search-indexable pages only after approval. Individual follower identities are not shown publicly. Following a Creator stores the relationship and timestamp. An internal-credit support transfer stores an immutable transfer identifier, amount, Creator profile, timestamp, and account relationships needed to debit and credit the correct balances. A virtual character gift additionally stores the conversation and character references, gift catalog key, name, symbol, price snapshot, settlement kind, and delivery time. Creators see each received amount and time under the neutral label “PornWorks member”; sender identities are not disclosed in the Creator-facing ledger. Account exports include structured sent and received support and gift records without exposing another member’s private identity. A reserved Creator handle cannot be changed or reassigned. If you permanently delete your account, outgoing and incoming follow relationships are removed, support and gift account links are anonymized while immutable balance records are retained for integrity, and the profile is anonymized, but the handle remains reserved as a non-public deletion record to prevent impersonation or reuse.
PornWorks relies on infrastructure, identity, AI-processing, and payment-processing providers to deliver requested features. Those processors receive only the data needed for the task. Provider credentials and internal model identifiers remain server-side. PornWorks does not sell personal information.
A signed-in checkout stores a PornWorks order identifier, selected annual plan, USD price snapshot, selected payment asset and network, exact payable amount, payment address or memo when needed, processor payment reference, status timestamps, plan activation, refunds or review signals, and an immutable event digest. New orders also retain the exact billing-policy bundle, payment-terms, privacy-notice, and refund-policy versions and content digests, the server-recorded acceptance time, and the clickwrap method. Secret keys, callback signatures, and raw payment-provider payloads are not stored in browser-visible records. Safe order-level acceptance evidence is included in a private account export before deletion. Payment, acceptance, and ledger records may be retained after account anonymization when needed for reconciliation, fraud prevention, disputes, refunds, security, or legal obligations.
PornWorks records first-party aggregate counts of pricing-page visibility, checkout actions, request outcomes, and order-reminder interactions to find usability problems. Counts are grouped by UTC day, page language, selected plan or payment channel where applicable, and signed-in or signed-out state. This collection does not store visitor, account or order identifiers, prompts, payment addresses, page URLs, referrers, IP addresses or browser fingerprints in its analytics records, and does not use analytics cookies or third-party analytics services. A random per-event identifier is used briefly to reject duplicate submissions; it is not a visitor identifier and is not saved in browser storage. Supported Do Not Track and Global Privacy Control signals suppress this collection. Aggregate records become eligible for removal after 90 days. Existing payment and ledger records remain separate; aggregate browser counts do not establish individual customer journeys or a verified conversion rate.
The private in-app inbox stores neutral activity notices and remains enabled while browser Push is enabled so a committed notice can be queued atomically. If you separately enable browser Push, PornWorks stores the browser subscription endpoint, encryption public key, authentication secret, browser user-agent label, and update timestamps. The endpoint is treated as a bearer secret. Encrypted notification payloads pass through the browser vendor’s push service, while the browser or operating system may show a neutral title and neutral status text on a lock screen. PornWorks also keeps a short-lived per-device delivery record so temporary failures can be retried without resending to devices that already accepted the notice. These records do not copy the subscription endpoint or encryption secrets; successful and cancelled records are removed after seven days, failed operational evidence after thirty days, and account deletion removes the account-linked queue. Disabling one device removes its PornWorks subscription and asks that browser to unsubscribe. Disabling all devices clears PornWorks’s stored subscription records and unsubscribes the current browser; notification permission or a dormant subscription on another device must be removed in that device’s browser settings. Expired endpoints are deleted when the push service reports them gone.
Hashed network or device signals may be used to enforce one-time trials and rate limits. For new image, video, and character-voice generation requests, the network IP address supplied by our infrastructure is recorded for security and abuse investigation. Only administrators can access this record, for up to 30 days after the original request; it is then hidden and eligible for automatic deletion. Retries do not replace the original address. This security record is separate from regional aggregate statistics and is not included in user-facing media records or account exports. Usage ledgers, job records, moderation decisions, and administrator audit events are retained as needed for account integrity, dispute review, and service security.
The free image trial depends on the country or region inferred from your current network connection by our infrastructure provider. This does not determine your nationality or personal income. To manage trial availability, PornWorks records country-level daily counts of account-usage checks and region-based trial refusals. A protected identifier derived from the account identifier or network address is used to deduplicate activity within a UTC day; it changes each day, is never shown publicly, and becomes eligible for removal after that day ends. The regional statistics do not retain raw IP addresses, precise locations, prompts, or payment information. Country-level daily totals become eligible for automatic removal after 90 days and are available only to administrators. A returning visitor can be counted again on another day, and a shared network can represent several people. These counts do not establish individual purchase conversion rates.
You can keep characters private, delete characters you own, review or reset relationship memory, hide an approved Creator profile by returning it to draft, unfollow Creators, turn notification categories off, avoid uploading identifying material, and sign out at any time. The Account & persona page provides a self-service NDJSON data export of account records, relationship state and continuity notes, Creator profile and follow metadata, virtual gift records, your support tickets and their messages, support attachment metadata, and safe media metadata; image, video, and audio binary files and private media-access credentials are not embedded in that export. It also provides permanent account deletion, which removes relationship memory. Deletion is paused while a creation is still running, a non-terminal subscription or payment remains, or a payout request is processing, and billing, internal-credit settlement, fraud-prevention, safety, reserved Creator-handle, and audit records may be retained only where needed for disputes, security, preventing impersonation, or legal compliance. Use the private Support page to submit and track an access, correction, deletion, payment, or privacy request.
Privacy rights & GDPR
Where the GDPR applies, you may have rights to access and correct personal data, request erasure or restriction, object to processing, obtain portable data, and withdraw consent for processing based on that consent. The right available depends on the processing and the legal conditions; withdrawing consent does not change the lawfulness of earlier processing.
Email seoai8888@gmail.com or use private Support. Describe the request and give the account email or a relevant service reference so we can locate the records. Do not send passwords, wallet recovery phrases or intimate media. If additional information is reasonably needed to verify the requester, we will explain what is needed.
You can also raise a data-protection complaint with the supervisory authority where you live or work, or where you believe an infringement occurred. Bulgaria’s authority is the Commission for Personal Data Protection. Account controls and the retention limits described above continue to apply; a request does not automatically erase records that must be kept for a lawful reason.
Read the current content, consent, and public-review rules before uploading real-person source media.