✦ MEKI CONTROL CENTERStudioDrama

Legal & privacy center

INTERNAL REVIEW DRAFT — NOT FINAL LEGAL NOTICES. Prepared 19 November 2026. Business identity, legal bases, retention, providers, and contract terms require verification. No launch, consent or compliance certification is implied. No personal operator details are included.

Impressum – Entwurf

Angaben gemäß § 5 DDG (soweit anwendbar).

Diensteanbieter / Verantwortlicher
[Vollständiger registrierter Name und Rechtsform]
Ladungsfähige Anschrift
[Straße, Hausnummer, PLZ, Ort, Land]
Kontakt
[Geschäftliche E-Mail-Adresse und geeigneter unmittelbarer Kontaktweg]
Vertretung, Register, Umsatzsteuer-ID
[Vertretungsberechtigte, Registergericht und Nummer, USt-IdNr. jeweils sofern zutreffend]
Verbraucherstreitbeilegung
[Anwendbarkeit nach §§ 36, 37 VSBG und Teilnahmebereitschaft/-pflicht prüfen]
Redaktionelle Verantwortung
[Bei journalistisch-redaktionellen Angeboten gesondert prüfen]

Hinweis: MEKI AI Studio und MEKI Drama sind derzeit Entwicklungsangebote. Diese Vorlage ist noch kein vollständiges Impressum.

Privacy notice – review draft

Scope: MEKI AI Studio and MEKI Drama on mekinews.us. The controller is [legal name, address and privacy contact]. DPO information [if required]. This notice must be finalized before being relied on by customers.

What may be processed, why, and proposed legal basis

ProcessingPurpose / proposed GDPR basis
Account email, account identifier, verification and session dataAuthentication, account security and delivery of requested account services; Art. 6(1)(b) and (f), as applicable.
Cloud drafts, prompts, settings, credit and generation-job recordsSave and manage requested creations; Art. 6(1)(b). Security and abuse prevention; Art. 6(1)(f), subject to balancing.
Drama viewing preferences, watch progress, memberships and access recordsRequested playback, continuity and access control; Art. 6(1)(b) where necessary. Optional storage requires further consent assessment.
Support requests and repliesRespond to inquiries; Art. 6(1)(b) or (f); legal obligations Art. 6(1)(c) where applicable.
Referral codes and test rewardsAdminister requested test participation and detect duplicate claims; Art. 6(1)(b)/(f), subject to review.
Request logs, device/network dataDeliver and secure the site; Art. 6(1)(f), balancing and retention to be verified.
Payment identifiers and billing eventsTest billing only at this stage; after launch contract fulfillment and accounting obligations (Art. 6(1)(b)/(c)). Verify actual data flows before enabling.

Recipients and transfers

Vercel (hosting) and Supabase (authentication, database, storage) are used by the current website. Stripe sandbox, email via Resend, external delivery of browser-library files and test providers require a verified data-flow inventory. PayPal, RevenueCat, AdSense/AdMob, RunPod and other generation providers are planned or separately tested; do not treat them as active production integrations. Complete processor agreements, provider roles, region, subprocessors, international-transfer safeguards (including adequacy or SCCs where needed) and access to copies before publication.

Retention

Specify actual storage periods or criteria for accounts, cloud drafts, uploaded references, jobs/outputs, viewing history, support, logs, billing, backups and test-rewards records. No unsupported guarantee of automatic deletion is made. Finalize retention schedules and deletion jobs.

Your privacy rights

Subject to legal conditions, individuals may request access, correction, deletion, restriction, portability, and object to legitimate-interest processing. Consent may be withdrawn prospectively where used. Complaints may be filed with a competent supervisory authority. For a controller established in Baden-Württemberg, see the LfDI BW complaint information; confirm competence. Provide verified privacy contact, identity verification and response procedures, normally within one month under Art. 12 GDPR.

Clarify required versus optional data, consequences if not supplied, and any automated decision-making under Art. 22; verify whether a DPO, DPIA or special-category data safeguards are needed.

Terms of use – review draft

Provider: [confirmed legal entity]. These proposed terms cover the two MEKI beta services. They are not a live consumer contract.

Accounts and beta features

Use accurate account information and protect credentials. Test credits and points are not cash, cannot be withdrawn and do not establish paid entitlements. AI creation tools prepare drafts; production generation is not publicly enabled. Availability, features, supported devices and limits must be accurately specified before contract formation.

Acceptable use and content

Users must have necessary rights to uploaded prompts, images, audio, likenesses and other material. Prohibit unlawful content, non-consensual intimate imagery, sexual exploitation, impersonation for fraud, harassment and unauthorized access. Do not upload others' sensitive personal data without a lawful basis. Define a proportionate reporting, review, removal and appeal process.

Ownership and service license

Users retain whatever rights they hold in their material. Propose a limited license strictly to provide the requested services, with duration, recipients and deletion terms verified. No automatic guarantee of exclusive copyright in AI output. Confirm model-license restrictions and permitted commercial uses; do not assert rights the provider cannot grant.

MEKI Drama

Published episodes 1–10 are intended to be free. Episode 11 onward is locked unless authorized by verified access. VIP unlimited and ad-free viewing are planned; ad rewards are not active. Viewing access is personal, subject to applicable law and actual plan details. Finalize content availability, territories, age ratings and accessibility.

Consumer protections

Mandatory consumer rights, digital product conformity and update duties, remedies, liability for intent or gross negligence, and injury to life, body or health cannot be excluded by generic beta disclaimers. Review limitation clauses, applicable law, jurisdiction, complaints and termination with qualified counsel.

Subscriptions, refunds & withdrawal – review draft

No real charges are enabled by this document. Displayed pricing plans are provisional until payment configuration and legal review are complete.

Before checkout

Disclose the total price including applicable taxes, billing interval, renewal, minimum term, included credits or episode access, any expiry, payment method and cancellation terms. Confirm the consumer's payment obligation using an unambiguous checkout button; send contract confirmation on a durable medium.

Cancellation and withdrawal

For applicable consumer distance contracts, statutory withdrawal generally lasts 14 days. Any early performance or loss of the right depends on whether the contract is a digital service or digital content, and on the required express consent, acknowledgment and confirmation. Never impose a blanket no-refunds rule. Insert the correct statutory withdrawal instruction and model form with provider contact details. Implement the required electronic withdrawal function under § 356a BGB and the subscription termination process under § 312k BGB where applicable, including timely electronic confirmations. App-store purchases must follow the applicable platform process without restricting statutory rights.

Refunds and service failures

Explain cancellation effective dates, unused credits, failed jobs, duplicate charges, billing errors, refunds and chargebacks accurately. Preserve mandatory remedies for defective or unavailable digital products. Finalize with real billing and receipt records before selling subscriptions.

Cookies & browser storage – review draft

MEKI currently uses authentication/session storage and browser-local features such as drafts, character profiles, saved series and watch history. These can remain on the device until cleared; shared-device privacy must be considered. Audit the actual keys, purposes, expiry and providers across every route, including mobile apps, embedded libraries and service workers.

Strictly necessary storage must be assessed against § 25(2) TDDDG. Where not exempt, obtain informed prior consent under § 25 TDDDG and GDPR. Do not load non-essential ad or tracking scripts before required consent. A banner alone does not implement consent. Design equally accessible accept/reject choices, granular controls, withdrawal, consent records and preference reopening. Verify the actual ad/measurement integrations before activation.

Local data can be managed using individual app controls where provided, or by clearing site data in the browser; this may remove saved work and sign-in sessions. Account deletion requires a separate server-side process.

AI, likeness & content safety – review draft

For future generation, require authorization for identifiable faces, voice cloning, reference images and copyrighted material. A checkbox by itself does not prove consent or lawful processing. Provide reporting, removal, rights verification, revocation and safeguards for children; do not train on user uploads without specifying the legal basis, purpose and choice. Determine whether facial or voice processing is biometric processing for unique identification and whether Art. 9 GDPR applies.

Assess provider and deployer obligations under EU AI Act Art. 50, including technical marking of synthetic outputs where applicable and disclosure of AI-generated/manipulated deepfakes, with appropriate artistic-work treatment. Validate the engine's output labeling before public release. Review copyright and licensing of model weights, generated outputs, music, voices and original drama assets. Do not launch public casting or creator uploads before separate contract and safety review.

Launch gates — all require verification

No checkbox implies a completed legal audit. This is a review checklist, not an activation control.

Primary legal references

DDG § 5 · GDPR · TDDDG § 25 · BGB § 312k · BGB § 356a · BGB § 356 · EU AI Act