Legal
Privacy Notice
Last updated: 18 October 2026
This notice explains how Renku Studio and gorenku.com handle information. Kerem Karatal is responsible for the website and its analytics. You can contact him at support@codingventures.com.
Renku Studio runs locally
Renku Studio stores your projects, screenplays, media, settings, and provider API keys on your computer. It does not require a Renku account. It never sends us your project files, file paths, prompts, screenplay text, media, project names or API keys. If you turn on usage statistics, it sends only the events listed in Optional app usage statistics. We cannot access your local project data unless you choose to share it with us, such as in a support request.
Optional app usage statistics
Renku Studio can send a few usage statistics so we can see which versions people run and whether projects and generations work. They are off until you turn them on: on the last first-run screen, in Studio Settings under Usage statistics, or with renku telemetry enable.
Turning them on creates a random install ID and saves it in telemetry.json in Renku’s configuration folder on your computer. Every event carries that ID, so events from one computer can be linked, but the ID is not linked to your name, email or projects. Turning them off deletes the file and its ID; turning them on again creates a new one.
Every event contains these fields:
- Install ID: the random ID described above.
- Time: when the event happened.
- Surface: always
studio, to tell app events apart from website events. - Version: the installed Renku version, or
developmentfor a source checkout. - System: the operating system (
darwin,win32orlinux) and chip type (arm64orx64).
These are the only events, and the only extra field each one has:
studio_started: Studio started.project_created: a new project was created.fdx_imported: a Final Draft (FDX) screenplay was imported into a project.sample_film_download_started: the sample film started downloading.sample_film_download_finished: that download ended, withresult(installedorfailed) and, when it failed, Renku’s error code (for exampleSAMPLE_FILM_DOWNLOAD_FAILED), never the error message.sample_film_opened: Studio opened the sample film project.generation_completed: a generated file was saved into a project, withmedia_kind(image,videooraudio).heard_about: your optional answer to “Where did you hear about Renku?” at first run, as one of a fixed list of choices. There is no free-text answer.telemetry_opted_out: you turned usage statistics off. This is the last event sent with your install ID.
Renku never sends file names, file paths, project names, titles, loglines, screenplay or prompt text, media or reference files, API keys, which provider or model you used, error messages, or any text you type. The events have no field that could hold them.
Events go directly from your computer to PostHog’s EU service, which receives your network address with each request, as with any web request. Renku asks PostHog not to work out a location from it. Events go to the same PostHog project as the website analytics.
To stop sending, turn usage statistics off in Settings or run renku telemetry disable. Renku also sends nothing while the DO_NOT_TRACK or RENKU_TELEMETRY_DISABLED environment variable is set, or while it runs in CI. To see exactly what would be sent without sending anything, set RENKU_TELEMETRY_DEBUG=1: Renku then prints each event instead. renku telemetry status shows your choice and your install ID.
Providers you connect
If you add an API key for an external model provider and request a generation, Renku sends that provider the key needed to authenticate the request, along with the relevant prompt, settings, and any media or reference files selected for that request. The provider processes that information and returns results under its own terms and privacy policy. Renku saves returned media in your local project.
You choose which providers to connect. Review their privacy policies before sending sensitive material. If you use a separate AI agent with Renku, that agent’s own privacy terms also apply to information you share with it.
Website hosting
The website is hosted on Cloudflare Pages. When you visit, Cloudflare processes technical request information such as your IP address, browser details, and requested pages to deliver and protect the site. This happens whatever you choose in the analytics banner. Our legal basis is our legitimate interest in operating and securing the website. See Cloudflare’s privacy policy for its handling of this information.
Renku downloads at downloads.gorenku.com are also served by Cloudflare. We keep daily counts of how often each file is downloaded, split by country, which Cloudflare works out from the network address, and store these counts in PostHog’s EU service. The counts contain no addresses or identifiers.
Website analytics
We use PostHog’s EU service to learn how people find gorenku.com and which pages, guides, and downloads are useful. The analytics banner asks whether we may store an analytics identifier in your browser. Until you answer, the website does not load PostHog and sends it nothing.
If you choose Yes, PostHog stores a browser identifier in your browser’s local storage and receives page views and when you leave a page; the website or tagged link that brought you here; clicks to the download page and to Renku’s GitHub repositories; copies of the installation commands; and when you start one of the website’s videos. This can include the page address, event time, the browser identifier, browser and device information, and approximate location derived from your network address. We may show a one-question survey on the Download page; if you answer, PostHog stores your answer with these events.
If you choose No, we store nothing in your browser except your choice. We still count page views and when you leave a page, without a browser identifier. To tell visits apart within one day, PostHog calculates a code on its servers from your network address, browser details, and the website’s name, combined with a random value it replaces every day. PostHog does not keep your network address or a location with these events, and the daily change means a returning visitor is counted again on another day. They are not linked to any visit in which you chose Yes. Our legal basis for this counting is our legitimate interest in knowing how many people visit the website and where they come from.
We do not use website analytics to record your screen, capture every click automatically, identify you by name, or collect your Renku project data. We do not use it for advertising or automated decisions. See PostHog’s privacy policy for information about its service.
Your analytics choice
We save your Yes or No choice in your browser’s local storage so you are not asked on every visit, and PostHog keeps its own copy of that choice there. If you choose Yes, PostHog also stores a browser identifier there. You can change your choice at any time with Analytics choice in the website footer. Changing from Yes to No removes PostHog’s browser identifier; after that your visits are only counted as described above. Your choice does not affect the technical information Cloudflare needs to serve the website. You can also clear your browser’s site data to remove stored choices and identifiers.
Sharing and retention
We do not sell your personal information. Website request data is handled by Cloudflare, which operates a global network; website analytics is handled through PostHog’s EU endpoint. Their linked policies describe their service providers and any international transfers. Model providers and AI agents that you choose to use receive information through your requests and apply their own retention rules.
Renku’s local copies of your project files and API keys remain on your device until you remove them. Your website analytics choice remains in your browser until you change it or clear site data. Your app usage statistics install ID remains on your computer until you turn usage statistics off. App usage statistics follow the same retention as website analytics. We keep analytics information only while needed to understand website use and improve the site, then delete or aggregate it. PostHog deletes analytics events after one year under our current plan. If you email us, we use your address and message to reply, based on our legitimate interest in handling your request, and keep them only as long as needed for that request or a legal obligation.
Your rights
Depending on where you live, you may ask to access, correct, delete, or limit the use of personal information we hold about you, and you may have rights to object or receive a copy of it. You can withdraw website analytics consent or app usage statistics consent at any time without affecting earlier lawful processing. To have past app usage statistics deleted, send us the install ID shown by renku telemetry status before you turn usage statistics off, because turning them off deletes the ID from your computer. Email support@codingventures.com with a request. If applicable, you may also complain to your local data protection authority.
Changes to this notice
We may update this notice when the website or Renku’s data practices change. The date above shows when it was last revised.