Privacy policy

Short version: we store what we need to run your account, keep your projects and bill you. Exports are rendered by your browser; we don’t get to see the finished images and videos. The one exception: if you have an AI assistant export an image, we render it on our server and keep it available for download for seven days. We use no advertising services. With PostHog we measure how Showoff is used: without your consent without cookies, with a masked recording of the visit as long as you haven’t decided, and with your consent across several visits. Our servers and PostHog’s are in the EU. Everything else is below.

1. Controller

Ryvelia UG (haftungsbeschränkt) Wasserturmstraße 3 04442 Zwenkau Germany

Represented by the managing director: Kimon Neuhoff Phone: +491631955793 Email: hi@showoff.dev

Where this policy says “we”, “us” or “Showoff”, it means Ryvelia UG (haftungsbeschränkt). Showoff is the name of the service at showoff.dev; it includes the website, the editor, the documentation at docs.showoff.dev and the app for pairing a phone.

2. Data protection officer

No data protection officer has been appointed; based on our ongoing review there is currently no obligation to appoint one. Send privacy requests to hi@showoff.dev.

3. Who is responsible for what

For your account, your organization, billing, the security of the service and its technical operation, we are the controller within the meaning of the GDPR.

You are responsible for the content of your projects — screenshots, screen recordings, videos, audio, texts — even when an AI assistant added it for you. Where it shows personal data, such as names or messages in a screenshot, we process it exclusively as a processor under Art. 28 GDPR: we store it and deliver it to your editor and to the AI assistants you connect (section 13); we do not analyze it for our own purposes. If you use Showoff for business we sign a data processing agreement with you; write to us for it.

4. Legal bases

• Art. 6 (1) (b) GDPR — performance of the contract with you (account, projects, collaboration, billing, support).
• Art. 6 (1) (c) GDPR — legal obligations, in particular commercial and tax retention duties.
• Art. 6 (1) (f) GDPR — legitimate interests, in particular security, abuse prevention, error analysis, reach measurement, recordings of visits without cookies and improving the documentation and the AI interface.
• Art. 6 (1) (a) GDPR and § 25 (1) TDDDG — consent, where we explicitly ask you, for example for analytics cookies and recordings across several visits (section 19); revocable with effect for the future.
• Art. 28 GDPR — processing on your behalf for the content of your projects.

5. Visiting this website and server logs

When you visit showoff.dev, docs.showoff.dev or the editor, your browser transmits your IP address, date and time, the requested address, the referring link, browser and operating system. We process this data to deliver the pages and secure their operation (Art. 6 (1) (f) GDPR). Server logs are overwritten continuously and usually deleted after 30 days at the latest; longer only if an incident needs investigating.

Website, editor and database are hosted on a server of OVH GmbH (OVHcloud), St.-Johanner-Straße 41–43, 66111 Saarbrücken, Germany, in a data center in France. Uploaded files and exports made by an AI assistant are stored with Wasabi Technologies, LLC, Boston, USA, in a data center in Frankfurt am Main, Germany. OVHcloud and Wasabi process on our behalf under Art. 28 GDPR; standard contractual clauses apply to Wasabi in addition.

All requests to showoff.dev and its subdomains pass through Cloudflare (Cloudflare, Inc., San Francisco, USA, represented by Cloudflare Germany GmbH). Cloudflare provides DNS and TLS certificates, forwards the requests to our server and fends off attacks; in doing so Cloudflare processes IP addresses and request data (Art. 6 (1) (f) GDPR). Cloudflare is certified under the EU-US Data Privacy Framework; standard contractual clauses apply in addition.

We serve fonts, device models and all other parts of the pages ourselves. PostHog’s scripts and requests (section 19) also run through our own address; your browser loads nothing from third-party servers.

6. Cookies and local storage

Strictly necessary (§ 25 (2) TDDDG) are: a language cookie (“showoffdev_locale”, one year) that remembers the language version you last read; after sign-in the session cookies of our authentication; “showoff_pro_wunsch” (one day) when you chose Pro on the pricing page, so that you go straight to the plan selection after signing up; and “showoff_consent” (180 days), which records your decision on analytics cookies so that we don’t ask again on every page.

Only with your consent does PostHog set cookies (“ph_…”, 180 days) and create entries in local storage (“ph_…”). They hold a random identifier, your session and your first contact with Showoff, such as the campaign you came from (section 19).

In your browser’s local storage we keep: the light/dark mode and, once you have rated a documentation page, a note about it (“showoff:docs-feedback:…”) so we do not ask again. A screen recording you make in the editor stays in your browser’s IndexedDB until its upload has finished, so that reloading the page does not lose it. None of this is transmitted to us before you upload it yourself.

There are no advertising services and no third-party cookies. You can change your decision on analytics cookies at any time with “Manage cookies” at the bottom of every page. A withdrawal takes effect immediately; PostHog then deletes its cookies and entries in your browser.

7. Account and sign-in

For registration we process your email address, name, a password (hash only), the time of registration, your preferred language and session data (session identifier, IP address, browser, time of last activity). Optionally you upload a profile picture, set up two-factor authentication (secret and recovery codes) or passkeys (public key, device identifier). There is no sign-in via third parties such as Google or GitHub. The legal basis is Art. 6 (1) (b) GDPR; for session protection and abuse prevention Art. 6 (1) (f) GDPR.

8. Organizations, invitations and sharing

Projects and folders belong to an organization that can have several member accounts. We process the organization’s name and identifier, memberships and roles, and for invitations the invited person’s email address and the inviting account (Art. 6 (1) (b) GDPR). An invitation is deleted once accepted or expired.

Within an organization, members see each other’s name, email address and profile picture, for example when sharing a project with selected people. For every project and folder we store who may access it.

9. Projects and uploaded files

We store your scenes — devices, arrangement, camera, light, animation, texts — in our database, together with the name, folder, time of the last change, the person who last changed it, and a preview image rendered by your browser.

Images, videos, audio and screen recordings that you upload or that an AI assistant adds for you (section 13) are stored as files in our storage at Wasabi (section 5). We deliver them to signed-in users only. When you remove a file from your projects or delete a project, a nightly clean-up deletes every file that no project, template or profile refers to anymore, once it is older than one day. The clean-up keeps exports by an AI assistant longer (section 13).

10. Real-time collaboration

When you open a project in the editor, your browser keeps a WebSocket connection to our server. It carries your changes to the scene, which we store, and details that only matter for the moment: who currently has the project open (name and profile picture), mouse pointers, selection and playback. These details are held in memory only and disappear once the last window is closed (Art. 6 (1) (b) GDPR).

11. Pairing a phone

With our app you can pair a phone with a project. The editor shows a QR code containing an access code that is valid for one minute and issued only for you and this project. The app uses the camera only to read this code.

The paired phone sends orientation data (its position in space) and its device name through our server to the project’s open editor windows. We do not store them; only if you apply the orientation to the scene does it become part of the project.

The image of your phone’s screen and full-resolution screenshots are sent by the app via WebRTC directly to your browser, within the same local network and without relay servers. Only the messages for setting up the connection, including the local network addresses of both devices, pass through our server; the image itself never reaches us. Only when you add a screenshot or recording to the project is it stored like any upload (section 9).

12. Rendering and export

In the editor, your browser renders the scene on your device. Exporting images and videos also happens entirely in your browser, and so does rendering a launch video; the exported files are saved directly on your device and not transmitted to us. It is different only when an AI assistant works for you: we render its previews and exports on our server (section 13).

For billing we report every export to Autumn (section 14): the time, kind (image or video) and resolution, the identifiers of the project and the person, and whether an AI assistant exported it. We do not record the content of an export.

13. AI assistants via MCP

Showoff is an MCP server. You can connect an AI assistant such as Claude, ChatGPT or Cursor to your account so that it builds mockups for you in one of your organizations. You set up the connection in the browser — sign in, choose the organization, approve — or with an access key from the MCP section of the settings. We store which assistant you approved, when and for which organization, and the tokens of that connection; of an access key only its name, its first characters and a hash, plus when it was created and last used. For organizations on Free we record when their trial began. When you disconnect an assistant or revoke a key, access ends immediately, and likewise when you leave the organization (Art. 6 (1) (b) GDPR).

The assistant works with your permissions: it sees the templates and the projects you have access to, creates projects and changes them. We store its changes like your own (sections 9 and 10). It passes screenshots and music directly or as a web address; if it gives an address, our server downloads the file from there, and that server sees our IP address, not yours. For files on your computer it gets an upload link that is valid for 30 minutes and only for that one project.

So that the assistant can see what it is building, we render preview sketches of the scene on our server, and for films and launch videos also individual frames. They are created in memory and not stored. Showoff’s answers go to your assistant: the names and structure of your projects including their texts, previews with your screenshots and links to the editor. If it asked for them when you signed in, it can also retrieve your account’s name, email address and profile picture. You decide which assistant you connect; what it and its provider do with this data is governed by the provider’s terms and privacy policy.

If you have the assistant export a finished image, we render it on our server, store it as a file alongside the uploads and give the assistant a scaled-down preview and a download link. The link is valid for seven days and works without signing in, so that your assistant, or a program you pass it to, can fetch the image directly. Anyone who knows the link can download the image during that time. We keep the file one day longer than the link is valid; after that the nightly clean-up deletes it. We do not analyze these images for our own purposes either.

To improve the interface, our server reports every call to PostHog (section 19): which tool, how long it took, whether it succeeded and which assistant asked, together with the identifiers of the account and the organization. We do not report arguments and answers, that is, the content of your projects (Art. 6 (1) (f) GDPR). You can object to this; write to us.

14. Billing and payment

Billing is per organization, according to the chosen plan. Usage, plan and invoices are managed with Autumn (Autumn Inc., USA) as our billing service; for this Autumn receives the organization’s identifier, name and handle, the name and email address of the person setting up billing, and the usage events. Payments are processed by Stripe Payments Europe, Ltd., Dublin, Ireland. Stripe processes payment data (card or account details, name, billing address, amount) under its own responsibility; full card details never reach us. We receive the payment status, the amount and the last digits of the payment method. We retain invoice data under § 147 AO and § 257 HGB for the statutory periods of up to ten years (Art. 6 (1) (b) and (c) GDPR). Standard contractual clauses apply to Autumn.

15. Emails

We send you the emails the service needs: confirmation of your address, password reset, notices about the security of your account, invitations to organizations and answers to your requests. We do not send advertising. Delivery runs through Resend (Plus Five Five, Inc., USA) on the basis of standard contractual clauses; Resend processes recipient address, subject, content and delivery status and tells us via webhook whether a message arrived.

16. Contact form and support

If you write to us through the contact form or by email we process your name, email address, phone number and company where given, and your message, in order to answer it (Art. 6 (1) (b) and (f) GDPR). Messages from the form reach us by email via Resend (section 15). We delete requests once they are settled and no retention duty applies.

The support chat is available only with your consent (section 19). What you write there is stored by PostHog on our behalf, together with the recording of your session, so that we can see what you need help with and answer you. We delete conversations like requests, once they are settled.

17. Feedback on the documentation

Below every documentation page we ask whether it helped. If you answer, we store only the page, language, yes or no and the time — without IP address, account or browser identifier. We keep your IP address in memory for at most one hour to fend off mass submissions; it never reaches the database (Art. 6 (1) (f) GDPR).

18. Error reports

If an error occurs in the editor or the dashboard while you are signed in, your browser reports it to our server. We log the time, account identifier, requested address, error message, technical stack trace and browser so that we can fix it (Art. 6 (1) (f) GDPR). The reports are kept in the server logs and deleted with them.

Unexpected errors on our server and errors that PostHog notices in the browser also go to PostHog’s error tracking; warnings and errors from the server logs go to PostHog Logs (section 19). They can contain account identifiers and the technical details from section 5. An error from the browser is linked to your account only with your consent.

19. Analytics with PostHog

To understand how visitors find and use Showoff, where they get stuck and why they decide for or against Pro, we use PostHog, a service of PostHog Inc., 2261 Market Street #4008, San Francisco, CA 94114, USA. We use PostHog Cloud EU: the data is stored in data centers in Frankfurt am Main, Germany. PostHog processes it on our behalf under Art. 28 GDPR; PostHog is certified under the EU-US Data Privacy Framework, and standard contractual clauses apply in addition. All requests run through our own address. PostHog does not store your IP address; it only derives the country from it.

As long as you haven’t decided, PostHog sets no cookies and stores nothing on your device; everything stays in the memory of the open page and is forgotten with the next reload. It records the pages you visit, the page you came from, campaign details from the address (such as “utm_source” or an ad’s identifier), clicks on buttons and links, load times, errors, and your browser, operating system, screen size and country, plus a recording of this visit, which shows how the page changes with your clicks, mouse movements and input, and heatmaps. The recording is masked as described below; it stops as soon as you decline. The legal basis is our legitimate interest in understanding how visitors use our website and where they get stuck (Art. 6 (1) (f) GDPR).

If you decline, PostHog only counts anonymously, without cookies, without storage on your device and without recording. So that the visits of one day count together, PostHog computes a hash on its server from your IP address, your browser identifier and a value that changes every day; the next day, nobody recognizes you. The legal basis is our legitimate interest in measuring the reach of our website and our advertising (Art. 6 (1) (f) GDPR).

With your consent (Art. 6 (1) (a) GDPR, § 25 (1) TDDDG), PostHog recognizes your browser through the cookie from section 6, and the following is added: recordings and heatmaps across several visits, occasional surveys and, if you open it, the support chat. If you are signed in, we link this to your account (identifier, email address, name) and your organization (identifier and handle). That way we see the path from the ad through signing up to the purchase.

In the recordings, anything personal stays in your browser: input fields and email addresses are masked there before anything is sent. In the app, that is the dashboard, the editor and the settings, only what we labeled ourselves is visible; names, projects, texts and all other content appear as asterisks. The editor’s stage, the images and videos you upload, and the content of requests to our server are not recorded.

PostHog analyzes some of these recordings for us automatically with artificial intelligence (Replay Vision) to find recurring problems, such as where visitors get stuck or why they stop before buying. For this, PostHog uses models from Google (Gemini); Google acts as PostHog’s subprocessor, under the same safeguards. The analysis only sees what the recording shows: whatever is masked there stays masked.

Independently of this, our server reports sign-ups, new organizations and projects, exports, checkouts, purchases and cancellations to PostHog, so that these numbers are right even when an ad blocker slows down the browser. With your consent they are linked to your account; otherwise they are sent without an identifier and only count. We never report the names or content of your projects. How we analyze the AI interface is described in section 13, how we analyze errors and logs in section 18.

PostHog keeps events for one year, recordings for 30 days and logs for 14 days. On request, we delete your data at PostHog earlier, including events and recordings. You can change your decision at any time with “Manage cookies” at the bottom of every page.

20. Retention and deletion

• When you delete a project we delete the scene and its sharing settings immediately; the nightly clean-up removes the uploaded files once nothing refers to them anymore.
• Exports by an AI assistant: until their download link has expired (seven days), plus one day.
• Connections to AI assistants and access keys: once disconnected or revoked they stop working immediately; we delete the records at the latest together with your account.
• When you delete your account we delete the account, sessions, organizations without other members and all projects in them. When an organization is deleted, we also delete its customer account at Autumn and Stripe. Invoice data remains stored, restricted, for the statutory period.
• Server logs and error reports: usually 30 days at most.
• At PostHog: events one year, recordings of your session 30 days, logs 14 days. “showoff_consent” and PostHog’s cookies last 180 days.
• Feedback on the documentation contains no personal data and is kept.
• Contact requests and support chat conversations: until settled, otherwise according to statutory periods.

21. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection to processing based on legitimate interests (Art. 21). You may withdraw any consent at any time, the one for analytics cookies with “Manage cookies” at the bottom of every page. Much of this you can do yourself in your account: delete projects and your account. For everything else write to the address above.

You may lodge a complaint with a data protection supervisory authority. The authority responsible for us is the Saxon Commissioner for Data Protection and Transparency, Devrientstraße 5, 01067 Dresden, Germany (datenschutz.sachsen.de).

22. Changes

We update this policy when the service or the legal situation changes. The current version is always available at this address; the date above shows its state. For material changes we inform signed-in users by email.