The controller for the processing of personal data described in this privacy policy is:
Renmy UG (haftungsbeschränkt) i.G.Commercial register: Company in formation, entry at the Amtsgericht Charlottenburg pending. Managing directors: René Knierim and Mandy Bebenroth.
For questions about data protection and to exercise your rights (section 14), write to privacy@renmy.net.
Until the customer agrees to the transfer of their contract to Renmy UG (haftungsbeschränkt) i.G., contracts concluded before 2026-10-15 stay with René Knierim, trading as Renmy (formerly Nimbus Solutions), who remains the controller for the personal data processed to perform them.
The following overview summarizes the types of personal data processed and the purposes of processing:
See our subprocessors page for the full list of third parties processing personal data on our behalf.
We process personal data on the following legal bases under the GDPR:
Storage period. Where this policy names no period, we delete personal data as soon as we no longer need it for the purpose we collected it for, or when you withdraw your consent, unless statutory retention obligations (§ 147 AO, § 257 HGB) require us to keep it; we then keep it only for that obligation. Your account data stays until you delete your account in the portal; the account is then anonymized, and only the records tax law requires us to keep remain.
This website is hosted by Fly.io (Fly.io, Inc., 29 S LaSalle St Suite 440, Chicago, IL 60603, USA). The hosting provider collects the following data transmitted by your browser in server log files: IP address, date and time of request, time zone difference to GMT, content of the request, HTTP status code, amount of data transferred, referrer URL, and browser information. The log files are kept for seven days and then deleted.
The servers are in Frankfurt (the primary region), London, Ashburn, San José and Sydney; the one nearest you answers. Fly.io, Inc. is based in the USA; transfers to it are covered by the EU-U.S. Data Privacy Framework (Art. 45 GDPR), under which Fly.io is certified.
Requests to the former domain testnimbus.dev first pass through Cloudflare (section 11), which forwards them to Fly.io.
Processing is based on Art. 6(1)(f) GDPR. There is a legitimate interest in the technically error-free presentation and optimization of the website.
We use Supabase (Supabase Inc., 970 Toa Payoh North #07-04, Singapore 318992; EU data hosted in Ireland) for account sign-up, sign-in, session management, and to store account, team, and license metadata. Supabase also stores what you send through the enquiry forms (section 13).
When you create an account, the following data is stored: email address, hashed password or OAuth provider identifier (Google, GitHub), account metadata, subscription state, team memberships, consent records, and license keys (encrypted at rest). When you sign in, Supabase issues a session token that is stored in your browser's local storage to keep you signed in until you sign out. No cookies are set by this process.
When you sign up for release updates with one of the email forms on this site, Supabase stores your email address, which form you used, your browser's user agent and the page that referred you. When you submit the form, the same details are also stored in a separate table, so that your signup is not lost if saving it fails. Nothing is stored before you submit. We use the address only to email you about releases, and we keep your signup and its copy until you withdraw your consent or ask us to delete them. You can withdraw at any time by writing to privacy@renmy.net; a withdrawal applies to future emails and does not affect prior lawful processing.
Legal basis: Art. 6(1)(b) GDPR (performance of the contract for renmy runtime) and, for waitlist signups before contract, Art. 6(1)(a) GDPR (consent).
Storage location: European Union (Ireland). Supabase privacy policy: supabase.com/privacy.
The renmy CLI sends one privacy-minimal first-activation event to Supabase so we can measure which installation channels are working. It contains a random installation ID, renmy version, operating system, architecture, and distribution channel. It never contains source code, file paths, test names, Salesforce data, command arguments, hostname, username, or email address. The install script (install.sh) sends one similar event when it installs or upgrades renmy: the same random installation ID, whether it is a first install or an upgrade, the renmy version, operating system, architecture and the installer's version. The environment variables below switch it off too.
Licensed headless CI usage is stored separately from human installations. After successful license validation, renmy sends a one-way fingerprint derived from the opaque license ID, the detected CI provider, distribution channel, renmy version, operating system, and architecture. We do not send the license key, repository, branch, workflow, build arguments, or project content. The record is de-duplicated per license, CI provider, and distribution channel, so repeated pipeline runs do not create repeated activation events. AI coding-agent sessions are excluded.
You can disable this processing with NIMBUS_TELEMETRY=false, NIMBUS_NO_TELEMETRY=1, NIMBUS_NO_TRACKING=1, or nimbus.telemetry=false in nimbus.properties. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in understanding product adoption and distribution effectiveness). Storage location: European Union (Ireland).
When Salesforce rejects a deployment that renmy's local checks passed (renmy deploy, renmy release), renmy can send us a mismatch report so we can close the gap. It is sent only if you pass --report-mismatch, set mismatchReporting to always in your release profile, or answer yes after the CLI has shown you the full report; if you decline, the report stays on your machine. It contains the renmy and Salesforce CLI versions, the API version, the kind of org, the test level, the Salesforce error lines with your identifiers replaced, and the results of the local checks. It contains no source code and no account or license identifier, and we do not store your IP address with it; our server refuses reports that still look like they contain personal data.
Reports are stored in our Supabase project in the European Union (Ireland). Legal basis: Art. 6(1)(a) GDPR (consent). NIMBUS_REPORT_URL=disabled turns sending off entirely.
We use Stripe Payments Europe, Ltd. (1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland) to process payments, manage subscriptions, calculate tax, and issue invoices. Stripe is a PCI-DSS Level 1 certified payment processor.
When you purchase a renmy runtime subscription, you are redirected to a Stripe-hosted checkout page. The following data is processed by Stripe on our behalf: email address, billing address, country, VAT ID (for business customers), card last 4 digits and brand (we never see or store the full card number), transaction history, and invoice records. Stripe also stores the cookies necessary to operate its checkout and customer portal; these are set on Stripe's domain, not on renmy.net.
Some processing may take place in the United States via Stripe, Inc. Such transfers are covered by EU Standard Contractual Clauses (Art. 46(2)(c) GDPR).
Legal basis: Art. 6(1)(b) GDPR (performance of the purchase contract) and, for invoice retention, Art. 6(1)(c) GDPR (legal obligation under § 147 AO and § 14b UStG, ten-year retention).
Stripe DPA: stripe.com/legal/dpa · Privacy policy: stripe.com/privacy.
We use Keygen, Inc. (United States) to issue, validate, and track activations of renmy runtime licenses. License validation occurs from the renmy CLI on your machine and from this website during sign-in flows.
The following data is processed by Keygen on our behalf: your email address (used as the license name) and Supabase user ID (as license metadata), and, for each activated machine, a machine fingerprint (a one-way hash of a random installation ID), its hostname, its display name (on macOS the Computer Name, which often contains your name), operating system and architecture, number of CPU cores and, for CI runners and AI-agent sessions, the CI provider or agent name. Keygen also records when the license was last validated. This information is used to enforce per-seat license limits, detect license misuse, and provide license-management functionality in the customer portal. Deactivating a machine in the portal deletes its record at Keygen.
Keygen processes data in the United States. Such transfers are covered by EU Standard Contractual Clauses (Art. 46(2)(c) GDPR).
Legal basis: Art. 6(1)(b) GDPR (performance of the license contract) and Art. 6(1)(f) GDPR (legitimate interest in preventing license abuse).
Keygen DPA: keygen.sh/terms · Privacy policy: keygen.sh/privacy.
We use Sentry (Functional Software EMEA Ltd., Hanover Quay, Dublin 2, Ireland; parent company: Functional Software, Inc., USA) to detect and investigate errors on this website and in our edge functions. Sentry only receives data when something goes wrong; it does not track page views, user behavior, or successful interactions.
The following data is sent to Sentry when an error is reported: error type and message, stack trace, page URL, browser type, and operating system. IP addresses are anonymized server-side (Sentry's sendDefaultPii option is disabled). We do not send email addresses, user identifiers, or request bodies to Sentry.
Storage location: European Union (Frankfurt) via Sentry's EU data residency option. Sentry's corporate structure includes US entities; any incidental access from the United States is covered by EU Standard Contractual Clauses (Art. 46(2)(c) GDPR).
Legal basis: Art. 6(1)(f) GDPR, our legitimate interest in operating a stable, error-free service. The data minimization described above forms part of the proportionality assessment. No cookies or local storage are used by Sentry.
Sentry DPA: sentry.io/legal/dpa · Privacy policy: sentry.io/privacy.
We use Resend, Inc. (United States) to deliver email.
If you actively subscribe to renmy runtime product updates in your account portal, Resend delivers those emails. It processes your email address, the email content, delivery status, and unsubscribe headers on our behalf. Subscription is optional and is not required to use renmy runtime.
Legal basis: Art. 6(1)(a) GDPR (consent). You may withdraw consent at any time in your account portal or through the unsubscribe link in every marketing email. A withdrawal applies to future emails and does not affect prior lawful processing.
Resend also delivers the emails the service sends on its own: a team invitation to the address a team admin enters, each team enquiry to our support inbox, and each consulting enquiry to consulting@renmy.net (section 13). For these, Resend processes the recipient's email address and the content of the email. Legal basis: Art. 6(1)(b) GDPR, or Art. 6(1)(f) GDPR (the legitimate interest of our customers and us in delivering these emails) where the recipient is not a party to the contract, such as an invited team member.
Resend may process data in the United States; transfers are covered by EU Standard Contractual Clauses. Resend privacy policy: resend.com/legal/privacy-policy.
The renmy CLI signs in by opening this website in your browser. After you authenticate via Supabase, the website redirects back to a local URL (http://localhost) on your own machine, passing your email, user ID, and license key as URL parameters so the CLI can store them locally. No third party intercepts this exchange: the redirect target is your own loopback address.
Once stored, the CLI uses the license key to activate the running machine with Keygen (see section 7) and to authenticate API requests to the online services of renmy runtime. License credentials are stored in a configuration file in your home directory and never leave your machine except to validate against Keygen.
The documentation search and the chat window on this site are Cloudflare AI Search, a service of Cloudflare, Inc. (101 Townsend St, San Francisco, CA 94107, USA). Its script is loaded from a Cloudflare server on every page, so Cloudflare receives your IP address and the information your browser sends with any request.
When you search or ask something in the chat, the text you enter is sent to Cloudflare, which returns matching documentation pages and, in the chat, a generated answer. The search is set to send no usage statistics, such as the number of results or which result you open. The chat stores nothing in your browser; a conversation ends when you leave or reload the page.
Legal basis: Art. 6(1)(f) GDPR (our legitimate interest in letting visitors search the documentation).
Cloudflare may process data in the United States and other countries where it operates; transfers are covered by EU Standard Contractual Clauses (Art. 46(2)(c) GDPR).
Cloudflare DPA: cloudflare.com/cloudflare-customer-dpa · Privacy policy: cloudflare.com/privacypolicy.
renmy.net sets no cookies. We do not use analytics, advertising, or retargeting tools, and the documentation search is set to send no usage statistics (section 11). Error monitoring (section 8) operates without cookies and with anonymized IPs.
The website uses your browser's local storage for two things: to keep you signed in (the Supabase session token, removed when you sign out) and for non-tracking user-interface preferences (e.g., the theme and feature preview toggles). The session token is sent only with your requests to our services, to authenticate them; the preferences stay in your browser. No consent banner is required because no information is stored or read for purposes other than those strictly necessary to provide the service you requested (§ 25(2) TDDDG).
When you complete a purchase, the Stripe-hosted checkout page sets cookies on Stripe's own domain (not on renmy.net) that are strictly necessary to process the payment. See section 6 for the Stripe privacy policy link.
When you contact us by email or phone, your information is stored for the purpose of processing the inquiry and for follow-up questions. We will not share this data without your consent.
Our mailboxes at renmy.net are hosted by STRATO GmbH, Otto-Ostrowski-Straße 7, 10249 Berlin, Germany, which processes the emails you send us, and our replies, on our behalf under a data processing agreement (Art. 28 GDPR), on servers in Germany.
Legal basis: Art. 6(1)(b) GDPR (pre-contractual measures) or Art. 6(1)(f) GDPR (legitimate interest in processing inquiries).
The enquiry form on the consulting pages asks for your name, your work email address, your company, your message, your confirmation that you are enquiring on behalf of a business, and, if you want to tell us, how you heard about us. We use these details to answer your enquiry and, if you want to work with us, to prepare a contract.
With them we store which consulting page the form is on, your browser's user agent and the page that referred you. The form sends your details to an edge function in our Supabase project, which stores them in the European Union (Ireland; see section 5) and emails the enquiry to consulting@renmy.net through Resend (section 9), so that it reaches both founders.
Legal basis: Art. 6(1)(b) GDPR (steps taken at your request before entering into a contract). If you enquire on behalf of a company, the legal basis for your details as its contact person is Art. 6(1)(f) GDPR (our legitimate interest in answering business enquiries).
We keep an enquiry for as long as we need it to answer you and to follow up on it, and then delete it. If a contract follows, we keep the enquiry for as long as the contract and the statutory retention periods require.
The contact form on /teams asks for your name (optional), your work email address, the number of Apex developers on your team, where your Apex is kept today, and your message. With them it stores your browser's user agent and the page that referred you. The form sends them to an edge function in our Supabase project, which stores them in the European Union (Ireland) and emails them to our support inbox through Resend (section 9). When you submit the form, it first stores your email address, your browser's user agent and the referring page in a separate table of the same project, so that the enquiry is not lost if sending it fails. The legal basis, and how long we keep these details, are the same as for consulting enquiries.
Neither form sets a cookie, and this site uses no analytics tools (section 12).
You have the following rights regarding your personal data:
To exercise them, write to privacy@renmy.net.
You also have the right to lodge a complaint with a data protection supervisory authority regarding our processing of your personal data.
Where we process data in a third country (outside the EU/EEA) or where this occurs through the use of third-party services, this only takes place on the basis of an EU Commission adequacy decision, standard contractual clauses (Art. 46(2)(c) GDPR), or your explicit consent.
This privacy policy applies from 2026-10-15. Due to the ongoing development of our website or changes in legal or regulatory requirements, it may become necessary to amend this privacy policy.