Privacy Policy
This policy explains what information DramaFork processes, why it is needed, where it goes, how long it is kept, and the choices available to you.
Effective and updated
1. Scope and controller
This policy applies to dramafork.com, its public catalog, creator tools, interactive films, text games, character conversations, community features, creator partnership applications, exports, and related support. “DramaFork,” “we,” and “us” refer to the team operating the service. For a privacy request, use the contact address at the end of this page.
Third-party sites and services have their own policies. This policy describes processing DramaFork controls or configures; it does not replace a provider's notice for processing that provider independently determines.
2. Information we process
The categories depend on the feature you use.
- Account and profile: Supabase user ID, Google account identifier, email address, display name, avatar, role, account status, sign-in session, and account settings.
- Creative and gameplay data: ideas, scripts, prompts, characters, storyboards, interaction nodes, game state, saves, checkpoints, conversation messages, memories, generated output, uploaded images, audio, video, and export records.
- Community and creator data: published works, creator attribution and profile, follows, likes, comments, favorites, play history, discussions, applications, portfolio links, and review status.
- Service and transaction data: credits, rewards, invitations, quota use, generation status, model usage metadata, moderation and administrative audit records.
- Technical data: IP address and request metadata available to hosting or service providers, device and browser type, timestamps, error and security logs, and coarse page, referrer-origin, interaction, and web-vitals analytics.
3. Why we process information
We process information to provide the service you request, authenticate accounts, save and restore work, run games and conversations, generate requested material, deliver exports, maintain community features, account for credits, answer support requests, protect users and infrastructure, prevent abuse, enforce these terms, and comply with law.
Depending on where you live, the legal basis is performance of a contract or steps you request before entering one; your consent where required for a clearly identified use; our legitimate interests in security, reliability, support, and service improvement where those interests do not override your rights; or a legal obligation. Where consent is the basis, you may withdraw it without affecting earlier lawful processing.
4. Cloud storage and account separation
Supabase provides authentication, PostgreSQL database, and object storage. Signed-in business data is associated with the verified account and protected by server-side authorization and row-level access rules. Private uploads use authenticated access or time-limited signed URLs where implemented; publishing a work makes the selected public fields and assets available to others.
DramaFork does not use localStorage, sessionStorage, IndexedDB, SQLite, or PGlite as the authoritative business database. A compatibility tool may read older DramaFork browser records for a one-time, account-scoped import to Supabase; it does not silently delete the original browser copy.
5. AI generation and automated output
When you request generation, the configured provider receives the prompt, relevant project or conversation context, references, task settings, and the minimum account or request metadata needed to operate and audit the task. The provider and model may differ by feature and environment. Provider records may be retained for safety, support, billing, or reliability under that provider's terms.
AI output is not used by DramaFork to make legal, employment, credit, health, or similarly significant decisions about you. Do not include unnecessary personal or sensitive information in prompts or uploads.
6. When information is disclosed
We disclose information only as needed to: Supabase and hosting/infrastructure providers; Google for sign-in and GA4; Microsoft for Clarity; configured AI and media-generation providers; people who receive an export or view content you publish; advisers or authorities where reasonably necessary to protect rights, investigate abuse, or comply with law; or a successor in a merger, financing, reorganization, or sale subject to appropriate notice and safeguards.
DramaFork does not sell personal information and does not use GA4 advertising storage, Google Signals, user-provided-data matching, or ad personalization in the current implementation. We do not disclose private project text to other users unless you choose to publish or share it.
7. International processing
Supabase, Google, Microsoft, hosting, and configured AI providers may process information in countries or regions other than yours. Data-protection rules may differ there. Where required, transfers should rely on a recognized legal mechanism and appropriate contractual, technical, or organizational safeguards. Contact us if you need information about the mechanism applicable to your data.
8. Retention and deletion
We use category-based retention rather than one period for every record.
- Account, profile, private projects, saves, conversations, favorites, and history are generally kept while the account or record remains active, then deleted or de-identified after a verified deletion request unless continued retention is required.
- Published content and comments remain until unpublished or deleted, but copies already downloaded, quoted, cached, or lawfully retained by others cannot be recalled.
- Creator applications are kept while reviewed and for reasonable follow-up, dispute, and duplicate-submission records; rejected or withdrawn applications should not be kept longer than necessary for those purposes.
- Security, generation, credit, moderation, and administrative audit records are kept for the period needed to investigate incidents, maintain integrity, resolve disputes, and satisfy legal obligations.
- Google analytics cookies may last up to two years unless browser or property settings shorten that period. Provider backups and logs expire under provider schedules and may not disappear immediately after an application record is deleted.
9. Your rights and choices
Subject to applicable law, you may ask to access, correct, export, delete, restrict, or object to processing of your personal information, withdraw consent, or appeal a refusal. You may delete individual projects through available product controls, unpublish content, use browser privacy controls, or contact us for an account-level request. We may verify identity and preserve data where retention is legally required or necessary to protect another person's rights.
You may also complain to the data-protection authority where you live. California residents may have rights to know, correct, delete, limit certain sensitive-data uses, and opt out of sale or sharing; DramaFork does not currently sell or share personal information for cross-context behavioral advertising.
10. Security and incidents
We use account authentication, scoped server access, row-level database rules, private storage controls, audit trails, request limits, and encrypted network transport where supported. No service can promise absolute security. If an incident creates a legally reportable risk, we will notify affected users and authorities as required.
11. Children
DramaFork is not designed to knowingly collect personal information from children below the minimum age permitted for an independent online account in their location. A minor should use the service only with a parent or guardian where required. In China, personal information of children under 14 is sensitive personal information and requires the legally required guardian authorization and protections. If you believe a child provided data without valid authorization, contact us so we can review and delete it where required.
12. Changes and contact
We may update this policy when features, providers, or legal requirements change. We will change the date above and provide additional notice for material changes where required. Email [email protected] with “Privacy request” and the account email or public account ID needed to locate the record; do not send passwords, access tokens, or unnecessary identity documents.
Microsoft Clarity
Unless your browser sends DNT or GPC, Microsoft Clarity helps us understand clicks, scrolling, and interaction patterns through heatmaps and reconstructed page sessions on selected public pages. Page content is masked. We do not enable it in private workspaces, administration, accounts, conversations, or gameplay, or on URLs with sensitive or unsupported query parameters or fragments. Standard campaign, pagination and catalog-filter parameters are supported. We do not send account identifiers to Clarity.
Clarity may use _clck and _clsk cookies to distinguish browsers and sessions; Microsoft processes the resulting interaction and device data under its privacy policy and retention settings, potentially outside your country. Advertising storage remains denied, advertising-cookie extraction and cookie-sync pixels are disabled, and collection requests omit cookies and referrer headers. Referrer metadata is limited to the originating domain. Browser DNT or GPC disables Clarity and attempts to delete accessible first-party analytics cookies. This does not retract data already sent or delete Microsoft-domain cookies. DNT and GPC keep it disabled.