Privacy Policy

1. Controller and contact

The controller for the processing of personal data at moebia (moebia.io) is:

Sascha Rahn, Lagerstr. 6b, 82178 Puchheim, Germany

Email: legal@moebia.io · Phone: +49 89 12258852

moebia is a product brand of Sascha Rahn, who runs the service as a sole trader. In this policy, "we" refers to him. We have not appointed a data protection officer. For any question about data protection and to exercise your rights, please write to legal@moebia.io.

2. Overview

With moebia you describe in a chat what a loop should show. An AI system turns this internally into a plan and the code of a loopable animation. Every message in the chat results in a new version of the loop. If you pay for it with credits from a subscription or pack or with bonus credits, you receive an HTML embed and a preview image (poster) and, at your request, an MP4 video; with starter credits, you receive a preview video with a logo, which you can unlock later. moebia is offered to businesses only. You receive credits for new versions with a monthly subscription and with credit packs.

We follow these principles:

• We only process what the service needs. We do not pass account data to the AI system.
• Your loops and results are private. Only what you make public yourself becomes public: if you create a profile, other signed-in users see your profile and the loops you create after that (section 22). Everything else is available only to you, and only after signing in. You embed and host the embeds on your own website.
• We use no analytics or tracking services, show no advertising, send no newsletter and load no fonts, scripts or embedded content from third parties. We serve fonts ourselves.
• None of our processing is based on consent.

For each processing operation, the sections below state the purpose, the data, the legal basis, the recipients, any transfer to third countries and the period for which the data are stored. "GDPR" means the General Data Protection Regulation (Regulation (EU) 2016/679), "TDDDG" the German Telecommunications Digital Services Data Protection Act.

If you act for a business. If our contracting party is not you yourself but a business you act for, such as your employer or client, we base the processing for which this policy names Art. 6(1)(b) GDPR, as far as you are concerned, on Art. 6(1)(f) GDPR. Our legitimate interest is to perform the contract with that business; the business has an interest in your being able to use the service for it.

3. Visiting the website and server logs

• Purpose: delivering the website and the app, keeping the service stable and secure, finding errors and fending off attacks.
• Data: On every request, our hosting provider necessarily processes your IP address and the details of the request (address requested, time, status code, technical details of your browser). Our application also writes operational messages, for example about errors or the outcome of a payment event. These messages contain no content, names, email addresses or user IDs, at most technical identifiers such as a receipt number.
• Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is a secure and working service. When you are signed in, the processing also serves the performance of the use contract (Art. 6(1)(b) GDPR).
• Recipients: Vercel Inc. as processor (hosting). Vercel delivers static content through a worldwide network of servers.
• Third country: USA, see section 14.
• Storage period: server logs for no more than 30 days; on our current Vercel plan, one day.

Merely visiting the website sets no cookie and stores nothing on your terminal equipment (for what happens after you sign in, see section 11).

4. Account and sign-in

• Purpose: setting up your account, confirming your email address, signing in and out, resetting your password, protecting your account against unauthorised access and misuse. When you sign up, you receive 300 starter credits (section 9). We also use the time you confirmed your email address to calculate the deadline of a welcome bonus.
• Data: name, email address, password (stored only as a hash, never in plain text), confirmation status and times, the version of the Terms of Service you accepted and your confirmation that you act as a business (section 7). For each session: session identifier, IP address, browser identifier (user agent) and expiry time. For confirming your email address and resetting your password: one-time links.
• Limiting requests: To slow down automated attacks, misuse and needless costs, we count requests in fixed windows of at most 24 hours: sign-in, sign-up, password and deletion attempts and notices (section 21) per IP address, new versions, videos, purchases and changes to the subscription, data exports and other actions per account. For this our database stores neither the IP address nor the user ID, only a check value formed with a secret key (HMAC), the count and the window. A counter can be linked to a person only with this key; these are pseudonymised data. An automatic run deletes expired counters every 15 minutes. In addition, the firewall of our hosting provider Vercel counts requests to individual areas per IP address in windows of at most ten minutes. Anyone who reaches a limit is asked to try again later.
• Number of active accounts: As an online platform, we must tell the Federal Network Agency (Bundesnetzagentur) or the European Commission on request how many users actively used our service per month on average over the last six months (Art. 24(3) DSA). For this we count, per calendar month, how many accounts signed in or used the app while signed in, each account once. So that no account is counted twice, we store for the current month a check value formed with a secret key (HMAC) from the month and the user ID, not the user ID itself; these are pseudonymised data. One day after the end of the month we delete these check values; only the month's number remains, with no link to a person. Only numbers are passed on, never personal data.
• Legal basis: Art. 6(1)(b) GDPR for the account, sign-in and links. For the IP address and user agent in sessions and for limiting requests, Art. 6(1)(f) GDPR; our legitimate interest is protecting your account and the service against misuse and overload. For the number of active accounts, Art. 6(1)(c) GDPR in conjunction with Art. 24(3) DSA.
• Recipients: Vercel Inc. (running the app and firewall), Databricks, Inc. (database), Plus Five Five, Inc. (sending emails, section 10), each as processor.
• Third country: USA, see section 14.
• Storage period: account data until the account is deleted; accounts whose email address is never confirmed are deleted 30 days after sign-up. Sessions until you sign out or until they expire after about a week without use; expired sessions are deleted no later than 30 days after expiry. Confirmation and reset links are valid for one hour; stored reset links are deleted once they expire. Counters for limiting requests until the end of their window, at most 24 hours. Check values for the number of active accounts until one day after the end of the month.

5. Loops: messages, versions and plans

• Purpose: creating your loops in the chat: planning, generating and checking versions, rendering posters, preview videos and, at your request, videos, marking them as AI-generated, providing them for download depending on the type of credit of the round, and unlocking preview versions.
• Data: your messages (prompt and corrections, up to 2,000 characters each) and the notices in the chat, for example about errors, stops and returned credits; the title of the loop, which the AI system assigns when planning the first finished version; for each version the internal plan, the generated scene code, format, duration, status and error codes and the files (HTML embed, poster, preview video with preview poster, MP4 on request); the type of credit a round was paid for with (starter credits, subscription, pack or bonus credits), the time of an unlock and whether it was made with credits or with your first purchase; times, including your last action in a loop. During a round, intermediate results arise, such as drafts of the plan and the code, check findings and still images of the animation.
• Internal plans: For each version, the AI system creates a plan of the animation (structure, sequence, texts, colours, timing) with a short summary of your previous wishes in this loop. We do not show the plan, do not provide it for download and use it only to build this version and to build later versions of the same loop on it. There is no analysis across loops or accounts. For access to plans, see section 16.
• Cost log: For budget control, we log for each AI call a run identifier that contains the loop identifier, plus the model, number of tokens, duration, cost and, where applicable, a short technical error text, but no user ID and no content. Until your account is deleted, the identifier can be linked to your account through your loops and your credit history; after that, only for a loop against which we took a measure after a notice (section 21). The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is controlling the cost of the AI service.
• Processing: The AI system Claude creates the plan and the scene code (section 6). The individual steps of a round and of a video are orchestrated by a workflow service of our hosting provider (Vercel Workflow) in Frankfurt am Main; its run data carry identifiers only and are encrypted. Checking and rendering take place in isolated execution environments (Vercel Sandbox) in Frankfurt am Main without network access, which are stopped and deleted afterwards. We store the files in a private data store (Vercel Blob) in Frankfurt am Main; only you can access them, and only after signing in; other signed-in users can also access the preview video and preview poster of public loops (section 22). In the app, we play versions from a separate address for loop content (usercontent.moebia.io), with links that are valid for 30 minutes; no cookies are read there.
• Legal basis: Art. 6(1)(b) GDPR; for the cost log as stated above.
• Recipients: Vercel Inc., Databricks, Inc. and Anthropic Ireland, Limited, each as processor.
• Third country: USA, see sections 6 and 14.
• Storage period: messages, versions, plans and files until you delete the loop or your account; you can delete a loop yourself at any time, but not individual versions. Loops without a finished version are deleted 90 days after your last action in them (creating, a message, a new attempt, requesting a video). Drafts and working files of a round are deleted when the attempt ends; Vercel deletes the run data of the workflow service 7 days after the run ends. We keep individual entries of the cost log for 24 months; after that, only monthly totals without identifiers remain.

6. Creating the loops with AI

We use the Claude API of Anthropic Ireland, Limited for the plan, the scene code and the visual check.

• What is transmitted: For the first version, your prompt. For a correction, the prompt of the first finished version, the plan and scene code of the version the correction builds on, and your new message; the plan contains a short summary of your previous wishes in this loop. For the code, the plan and, for a correction, the previous scene code; for a repair, the faulty code with the findings of the technical check. For the visual check of a version, its code and still images of the rendered animation (a contact sheet of eight frames). If a response breaks off, we send the same request again with the text received so far. Account data such as your name, email address or user ID are not transmitted.
• Free text: Whatever you write in your messages goes to the AI system unchanged and may appear as text in the animation and therefore also in the still images. Free text can contain personal data. Please do not enter personal data of third parties (such as names or contact details), confidential information or sensitive information about yourself or others.
• Purpose and legal basis: creating your loops, Art. 6(1)(b) GDPR.
• Role: Anthropic processes the data as our processor. To enforce its usage policy, Anthropic also screens inputs for misuse and in doing so pursues purposes of its own.
• Location and third country: Anthropic stores the data in the USA. Processing by the model may take place in data centres in the USA, Europe, Asia and Australia, and internal processes such as safety reviews, support and incident response also in other countries in which Anthropic, its group companies or its sub-processors operate. Anthropic is not certified under the EU-US Data Privacy Framework; the transfer is based on the standard contractual clauses of the European Commission in Anthropic's data processing agreement (Art. 46(2)(c) GDPR).
• Storage period at Anthropic: Anthropic deletes inputs, including the still images, and outputs within 30 days. It keeps them longer only if content is flagged for a possible breach of the usage policy (up to 2 years, safety classification scores up to 7 years) or if the law requires it.
• No training: Under its terms, Anthropic does not use API inputs and outputs to train its models. We do not send Anthropic any feedback that would trigger an exception to this.
• Marking as AI-generated: Posters and videos, including preview videos and preview posters, carry signed provenance data and an imperceptible watermark. They contain no information about you: only the note that the file is AI-generated, moebia as origin and provider, the version of our rendering tool, the identifier of the AI model and the time of signing, but no name, email address, account or loop identifier. A timestamping service confirms the time of signing; it receives only a check value (hash) of the signature, no file and no information about you. We keep no register that links marked files to an account.
• Checking files: The check at moebia.io/check-file runs in your browser; the file you check is not transmitted to us.

Section 5 applies to what is stored permanently in your loops.

7. Consent log

• What we log: your acceptance of the Terms of Service and your confirmation as a business at sign-up and, for every purchase of a subscription or a pack, your renewed confirmation as a business with the name of your business or self-employed activity.
• Data: type of statement, version and checksum of the text shown, language, how it was given (checkbox or button), time, reference (account or checkout session), your user ID and, at checkout, the name of your business or self-employed activity you entered. No IP address, no user agent, no device identifier. The log is kept separately from technical logs.
• Purpose: being able to prove that, and for which version of the text, you made a statement, and defending ourselves against claims, for example against a later objection that you bought as a consumer.
• Legal basis: Art. 6(1)(f) GDPR; our legitimate interest is this proof. After an account deletion, also Art. 17(3)(e) GDPR.
• Recipients: Databricks, Inc. (database) as processor.
• Third country: USA, see section 14.
• Notices of changes to the Terms of Service: When we announce a change to the Terms of Service (section 17 of the terms), we record for each account which version we announced, from when it applies and when the notice was sent, together with the number of attempts and, if sending failed, its error code. We do not store your email address or the text of the email for this. The purpose is to prove that we informed you in time; the legal basis is Art. 6(1)(f) GDPR, after an account deletion also Art. 17(3)(e) GDPR.
• Storage period: the acceptance of the terms and the confirmation as a business at sign-up, and the records of notices of changes to the terms, for as long as your account exists; after its deletion, in pseudonymised form until the end of the year of deletion plus 3 years (section 12). The confirmation at checkout with the name of your business until the end of the fourth calendar year after the year of purchase, for a purchase from 16 December onwards until the end of the fifth. If a checkout is not paid, we delete the confirmation 30 days later.

8. Subscription and credit packs through Stripe Managed Payments

You conclude the contracts for a subscription or a credit pack with Sascha Rahn. The purchase and the recurring payments are processed through Stripe Managed Payments: Sold through Link, LLC ("Link"), a Stripe company, is the merchant of record. Link acts in our name and on our account, but appears to you in its own name at checkout and handles payment, VAT, receipts and invoices, support for orders and subscriptions, refunds and chargebacks.

• What we pass to Stripe: When you buy a subscription or a pack, we redirect you to the checkout that Stripe operates for Link and pass on your user ID (so that we can assign the purchase and the subscription to your account), your email address (pre-filled at checkout and for the receipt) or, if you are already a customer at Stripe, your customer identifier, and the subscription or pack you chose; for a subscription we also store the user ID and the subscription tier in the subscription at Stripe. We do not pass on the name of your business from the purchase dialog. You enter your payment details directly with Stripe. If you change the subscription tier in the app, cancel or withdraw a cancellation, we pass this on to Stripe. If you delete your account or we end the use contract, we cancel your subscription at Stripe immediately.
• Stripe and Link as separate controllers: For checkout, payment, tax, receipts, support and the management of the order and the subscription, Stripe and Link process your data under their own responsibility, for their own purposes and with their own retention periods; under Link's terms, Stripe and we are independent controllers in this respect. This includes the checkout session, the customer record and the subscription at Stripe. You can also manage and cancel your subscription through an account at Link. If you delete your account at Link or request the deletion of your data there, Stripe cancels your subscription; we process this like any other cancellation. The Link Privacy Center (https://link.com/privacy-center) and Stripe's privacy policy (https://stripe.com/privacy) describe the details and your rights there. Stripe handles requests to delete your data at Link itself; you can contact Link about this directly.
• What we receive: According to Stripe, Link makes the order data available to the seller (contact details, payment details, tax number where applicable, billing address, order details); they are held in our Stripe account. We only evaluate Stripe's notifications about checkout, payment, subscription and refunds automatically and read the status of the subscription and the payment of an invoice at Stripe for this: payment and subscription status, order, payment, invoice, subscription and customer identifiers, user ID, subscription tier or pack, billing period, cancellation status and, for a refund, the amounts. Of these, moebia stores the status of your subscription (subscription and customer identifier at Stripe, tier, status, cancellation at the end of the billing period, end of the period and of the subscription) and, in the credit history, the order identifier with the subscription tier or pack, for subscription payments also the invoice identifier and the billing period (section 9). We do not log the content of the notifications. In addition, we receive payout reports and self-billed invoices from Stripe and Link as our accounting records.
• Purpose: processing the purchase and the subscription, crediting credits, showing and managing your subscription in the app, booking refunds, meeting tax obligations.
• Legal basis: Art. 6(1)(b) GDPR for the handover, managing the subscription, crediting and refunds; Art. 6(1)(c) GDPR in conjunction with section 147 of the German Fiscal Code (AO) and section 14b of the German VAT Act (UStG) for keeping the records.
• Third country: Stripe, LLC (USA) is certified under the EU-US Data Privacy Framework (checked on 17 October 2026). Stripe also processes Managed Payments through Stripe Technology Europe, Limited (Ireland). Sold through Link, LLC has its registered office in the USA and is not itself on the Data Privacy Framework list; Stripe describes the safeguards in its privacy policy.
• Storage period: the status of your subscription until your account is deleted. If we cancel a subscription because of an account deletion or a termination by us, we keep an order with the subscription identifier at Stripe, but without your user ID, until Stripe confirms the cancellation, and delete it 30 days after the confirmation. Payout reports and self-billed invoices for 8 years from the end of the year of issue. We do not keep the order data in our Stripe account as our own records and do not delete it ourselves; it stays with Stripe and Link under their retention periods. We delete your credit history together with your account (section 9).

9. Credit history

• Purpose: keeping your credit balance, reserving, using and releasing credits per round, booking unlocks, crediting the credits of a billing period, of packs and bonus credits and letting them expire after their validity, checking the conditions of a welcome bonus, documenting purchases and refunds and refunding unused paid credits pro rata when the contract ends.
• Data: bookings with type (starter credits, purchase of a pack, credits of a billing period, bonus credits with promotion and validity, hold, use, release, unlock, refund, expiry), amount, time, reference (loop, or order identifier with subscription tier or pack, for subscription periods also the subscription and invoice identifiers, the period and the end of validity) and your user ID. The credit history contains no payment details; for a purchase, we note the amount paid, for a refund the amount paid and the amount refunded. If you delete a loop, its booking stays in the history without a title.
• Legal basis: Art. 6(1)(b) GDPR.
• Recipients: Databricks, Inc. (database) as processor.
• Third country: USA, see section 14.
• Storage period: until your account is deleted.

10. Emails

• Emails from us: We only send emails the service needs: confirming your email address, resetting your password, notifying you when someone signs up again with your already registered address, telling you that your data archive is ready, confirming an account deletion with a receipt number, notices of changes to the Terms of Service (section 7), and the messages about reports and moderation (section 21). These emails contain no advertising. Open and click tracking is switched off. Link sends the receipts, invoices and messages about refunds and your subscription.
• Data: email address, name, content of the email including any one-time link, and delivery data such as time and delivery status.
• Emails to us: If you write to an address at moebia.io, such as legal@moebia.io, we receive and store your message with sender, content and attachments in our mailbox to deal with your request. After an account deletion, the note on the refund goes to the same mailbox (section 12).
• Legal basis: Art. 6(1)(b) GDPR for emails about the contract; for other requests to us Art. 6(1)(f) GDPR, our legitimate interest being to answer them; for messages under the Digital Services Act, including notices of significant changes to the Terms of Service (Art. 14(2) DSA), Art. 6(1)(c) GDPR (section 21).
• Recipients: for sending, Plus Five Five, Inc. (Resend); for our mailbox, Zoho Corporation GmbH, Düsseldorf (Zoho Mail); each as processor. The sending provider is itself the controller for its own account and usage data.
• Location and third country: Emails are sent through the sending provider's European region (Ireland); it always stores account data, email metadata and logs in the USA. Our mailbox is held in Zoho's European data centres (Netherlands, Ireland); for technical support, staff of the Zoho group in India may access it in individual cases. See section 14.
• Storage period: at the sending provider no more than 30 days. Emails to us and the note on the refund until the matter has been dealt with and no obligation to provide evidence or to retain them stands in the way.

11. Storage on your terminal equipment

We store on your terminal equipment only what is strictly necessary for the service you have requested. This does not require consent (section 25(2) no. 2 TDDDG); we therefore show no cookie banner.

The theme choice is read only in your browser and is not transmitted to us. If you choose nothing, the display follows your system setting without anything being stored. There are no other cookies, no tracking and no storage by third parties. Section 4 applies to the session data.

12. Account deletion

You delete your account yourself in the account settings (/app/account) with your password. Download the results you want to keep beforehand, and request an archive of your data there if you need one (section 16). A running subscription ends immediately with the deletion; we cancel it at Stripe, and nothing is charged after that. We refund paid, unused credits from packs and from the current billing period pro rata within 14 days after the deletion through Link; for this, our mailbox receives a note with the order identifiers, the unused credits and the proposed refund, without name or email address. The Terms of Service set out the details.

Deleted immediately: your account (name, email address, password hash), your sessions, open confirmation and reset links, your profile, your loops with all messages, versions, plans and files, your favourites, the status of your subscription, your data archives and your entire credit history. Your loops thereby also disappear from Explore and from other users' favourites, and your handle becomes available again. We stop rounds and videos in progress. We delete files in two passes: immediately and after about 30 minutes, so that renders still running are also covered. Finally, you receive a confirmation with a receipt number by email.

We keep only:

• Evidence of consents (section 7). We replace your user ID with a pseudonym starting with p1:. It is calculated from your email address with a secret key that only we hold. Period: the acceptance of the terms and the confirmation as a business at sign-up, and the records of notices of changes to the terms, until the end of the year of deletion plus 3 years, the confirmation at checkout as in section 7.
• Records under the Digital Services Act, if there were reports or measures concerning your content, also pseudonymised, with the periods in section 21. Open measures end with the deletion.
• A deletion receipt with the time, the number of deleted entries and technical error codes. It contains neither name nor email address nor user ID; it needs user and loop identifiers only until the second file pass. Its number appears only in the email to you. The purpose is to prove the deletion (Art. 6(1)(f) GDPR); we keep it for 3 years from the end of the year of deletion.
• The order to cancel your subscription with the subscription identifier at Stripe, without your user ID, until 30 days after Stripe confirms the cancellation (section 8).

Pseudonymised data remain personal data for us because we could link them to your email address again. We therefore do not describe them as anonymous. We block them for any other use and use them only for the stated purpose: the evidence of consents to defend against claims (Art. 6(1)(f), Art. 17(3)(e) GDPR), the records under the Digital Services Act to meet our obligations under it (Art. 6(1)(c), Art. 17(3)(b) GDPR).

Remaining with others:

• at Stripe and Link, whatever they store under their own responsibility, under their retention periods (section 8): your orders and your subscription (subscription tier or pack, date, the email address used) stay with Link and in our payment account. You request deletion there from Link.
• at Anthropic, whatever was transmitted in the last 30 days, until deleted under its periods (section 6).
• at the sending provider, whatever was sent in the last 30 days, for no more than 30 days (section 10), and in our mailbox your emails to us and the note on the refund (section 10).
• in the server logs and the run data of the workflow service, whatever arose in the last days, for no more than 30 days (sections 3 and 5).
• in the cost log, the entries with identifiers of your loops, without a user ID, for no more than 24 months (section 5).
• in the database backups for the restore window of our database plan, currently 6 hours. If we ever restore an older state, we delete the previously deleted data again.
• with other users, whatever they copied themselves before, such as the original prompt of a public loop (section 22).

13. Service providers and recipients at a glance

Apart from these service providers, the authorities named in section 21 and other signed-in users who see your public profile and your public loops (section 22), there are no recipients. The timestamp service (section 6) receives only a check value of the signature without personal data and is therefore not a recipient.

14. Transfers to third countries

Several service providers are based in the USA or process data there. Running the app in Frankfurt am Main does not change the fact that Vercel Inc. is a US company that also processes data in the USA; for the database, this applies to remote access, account data and logs.

• Data Privacy Framework: For transfers to US companies certified under the EU-US Data Privacy Framework, there is an adequacy decision of the European Commission (Implementing Decision (EU) 2023/1795). It applies only to companies on the list of the US Department of Commerce. As of 17 October 2026, the list includes Vercel Inc., Databricks, Inc. (with Neon, LLC), Stripe, LLC and Plus Five Five, Inc.; for Plus Five Five, a re-certification is under way on that date. We check the status regularly.
• Standard contractual clauses: Where there is no certification (Anthropic; the support access of the Zoho group from India) or as an additional basis, we base the transfer on standard contractual clauses of the European Commission (Art. 46(2)(c) GDPR) in the contracts with the service providers.
• Copy of the safeguards: You can obtain a copy of the relevant safeguards on request at legal@moebia.io.

15. Storage periods at a glance

We block data that we keep only because of an obligation to retain them or to provide evidence and use them only for that purpose. Tax retention periods are extended as long as the assessment period for the taxes concerned has not expired.

16. Your rights

You have the right to

• access to the data we process about you, including a copy (Art. 15 GDPR),
• rectification of inaccurate data and completion of incomplete data (Art. 16 GDPR),
• erasure (Art. 17 GDPR),
• restriction of processing (Art. 18 GDPR),
• data portability, meaning receiving the data you provided in a structured, commonly used and machine-readable format (Art. 20 GDPR),
• object (Art. 21 GDPR, section 17).

You can request a copy of your data yourself at any time in the account settings, as an archive: account data with your sessions, your profile, your loops with messages, versions and their files (for preview versions only the preview video and preview poster), your favourites, the status of your subscription, credit history, consents and records of notices of changes to the terms in machine-readable form. We email you when it is ready; it can be downloaded for 7 days, and you can request one every 24 hours. The archive also names the recipients of your data. The archive does not contain the internal plans of your loops with the code as the AI system wrote it, detailed technical error texts or the cost log (section 5), nor files of loops that we have disabled after a notice (section 21). You can request access to this data too. From the plans, we give you everything that relates to you, such as how the AI system implemented your instructions and the summary of your wishes. We withhold parts that would disclose our method only insofar as they are protected as a trade secret and your interest in access does not prevail (Art. 15(4) GDPR); we assess this case by case and give you our reasons for anything we withhold. The HTML embed, poster and video of a preview version are not in the archive: we provide them only once it is unlocked (section 3 (7) of the Terms of Service). The archive contains in full your messages from which the version was created; you can request information about the data we store for a preview version. For anything else, write to legal@moebia.io, preferably from the email address of your account. We reply without undue delay, within one month at the latest, and free of charge. If we have reasonable doubts about your identity, we ask for more information. You can delete your account yourself at any time (section 12).

We do not ask for consent to any processing that you could withdraw.

17. Right to object

You can object at any time, on grounds relating to your particular situation, to the processing of your data where it is based on Art. 6(1)(f) GDPR (Art. 21(1) GDPR). At moebia this concerns the server logs (section 3), the IP address and user agent in sessions and the limiting of requests (section 4), the cost log (section 5), the consent log (section 7), emails to us outside the contract (section 10), the deletion receipt (section 12) and the protection of the report form against misuse (section 21). If you act for a business that is our contracting party (section 2), the right to object also covers the processing we otherwise base on Art. 6(1)(b) GDPR; after an objection, you may then no longer be able to use the service for that business. After an objection, we no longer process these data unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. We do not carry out direct marketing. You can send your objection informally to legal@moebia.io.

18. Right to lodge a complaint

You have the right to lodge a complaint with a data protection supervisory authority if you consider that the processing of your data infringes the GDPR, in particular in the Member State of your habitual residence, your place of work or the place of the alleged infringement (Art. 77 GDPR).

19. Provision of data and automated decisions

We need your name, email address and password to set up your account; without them you cannot use moebia. We need a prompt to create a loop, and the name of your business for a purchase. A public profile is optional; without a profile, your loops stay private. There is no legal obligation to provide us with data.

We do not make decisions based solely on automated processing that produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR). The AI system creates content according to your messages and may decline a message if it asks for impermissible content; it does not evaluate you as a person, and a declined message uses no credits. A human decides on measures after a report.

20. No use for training or advertising

We use your messages, plans and results only to create your loops and to show public loops under section 22, and a plan only for the loop it belongs to. We do not use them to train AI models, for advertising or as a reference or example. Only what you make public yourself under section 22 is public, and only to signed-in users within the service. For training at the AI provider, see section 6.

21. Content notices and moderation

• Purpose: We handle notices of illegal content, orders from authorities and, where necessary, reports to law enforcement authorities; we block or remove content and accounts, take loops or profiles out of Explore, reset handles and give reasons to those affected.
• Data: for persons submitting a notice, the details in the report form at moebia.io/report or in the email: category, content concerned (for example a website address, the address of a profile page, a file name, a loop identifier or a description), explanation, name, email address (optional for notices about child sexual abuse material), your role if you wish, and the statement that the information is accurate. If you report a public loop or a profile via "Report", the form takes over what it concerns. No IP address and no user agent in the record of the notice. For users concerned, user ID, loops and profiles concerned, measures and statements of reasons, and for a running subscription whether it continues or ends. We keep copies of blocked files for as long as an authority requires.
• Protection against misuse: The form limits notices per email address and day, per IP address and hour and per IP address and day. For the limit per IP address we store not the address but only a check value with a count for at most 24 hours (section 4). If a very large number of notices comes in overall, we send the acknowledgements of receipt with a delay. The form detects automatically filled-in forms without third-party services.
• Legal basis: Art. 6(1)(c) GDPR in conjunction with Articles 9, 10 and 16 to 18 of Regulation (EU) 2022/2065 (Digital Services Act); for protecting the report form against misuse, Art. 6(1)(f) GDPR.
• Recipients: persons submitting a notice (acknowledgement of receipt and decision by email), users concerned (the identity of the person submitting a notice only if strictly necessary for the statement of reasons), ordering authorities and, where there is a threat to the life or safety of persons, the German Federal Criminal Police Office (Bundeskriminalamt). For database, storage and emails, the service providers in section 13.
• Storage period: notices until the end of the year of the decision plus three years; measures and statements of reasons until the end of the year in which the measure ends plus three years; orders and reports to authorities until the end of the year in which they are closed plus three years; secured files until the authority releases them; messages sent 30 days after sending. We delete an account terminated for a violation 30 days after the termination. If an account is deleted, these data are pseudonymised.

22. Public profile, Explore and favourites

Where moebia offers these functions, you can create a public profile, view the public loops of other users in Explore and mark loops as favourites. Only signed-in users see Explore and profile pages; search engines and visitors without an account cannot access them.

• Public only through your own action: Without a profile, only you can access your loops. They become public only once you create a profile yourself; when you create it, we show you what then becomes public. Only loops you create after that become public; older loops remain private. You choose your handle and display name yourself; we do not show the name of your account.
• What others see: on your profile page your handle, your display name, an avatar made from its initials and since when you have been a member ("Member since"); for each public loop the preview video and the preview poster of its latest finished version with the moebia logo, its title and the prompt of your first message (original prompt), which others may copy and use for their own prompts. Others do not see corrections, earlier versions, the HTML embed, the poster or the video. Therefore, do not write names of clients, confidential details or personal data of third parties in the first prompt of a loop that becomes public.
• Hiding and deleting: With a Pro or Studio subscription, you can hide your loops from Explore. Whether a loop is public is set when it is created; hidden loops stay hidden even after a change of subscription tier. You can delete any loop at any time; it then disappears from Explore, from your profile page and from other users' favourites. You can change your display name at any time and your handle at most once every 30 days.
• Favourites: If you mark a loop with the heart, we store this with the time. Only you see your favourites; we show no one who marked a loop, and we do not count favourites.
• Data: profile (handle, display name, type of profile, hiding setting, times of creation and of the last change of the handle); for each loop its visibility, the time of its publication and the version shown publicly; favourites with user ID, loop and time. Explore orders public loops by the time of their publication; we do not analyse favourites and do not build interest profiles.
• Legal basis: Art. 6(1)(b) GDPR. The public profile and the display of your loops in Explore are part of the service you choose by creating the profile (section 3 (8) of the Terms of Service); without this action of yours, we make nothing public (Art. 25(2) GDPR).
• Recipients: other signed-in users of moebia, including users outside the EU; Vercel Inc. and Databricks, Inc. as processors (section 13).
• Third country: for Vercel and Databricks the USA, see section 14. Signed-in users can also view your profile and your public loops from outside the EU.
• Storage period: the profile until your account is deleted or until we delete it at your request to legal@moebia.io; your loops are then no longer public, and your handle becomes available again. The visibility and publication of a loop with the loop (section 5). Favourites until you remove the heart, the loop is deleted or you delete your account. We cannot retrieve what other users copied before, such as an original prompt.

23. Changes to this privacy policy

If the service, the service providers or the legal situation change, we adapt this privacy policy. If we want to process data for a new purpose, we inform you beforehand.

Last updated: 28 October 2026