Privacy policy

What we collect

We collect four kinds of data, and nothing else.

• Account data. Your email address, and if you sign in with Google, the name and profile picture Google returns. If you create a public profile you also give us a handle, a display name, an optional bio and an optional avatar.
• Content you create. The prompts you write, the tools built from them, the conversation you have while editing a tool, the parameters you set, the images you attach as references, and anything you publish to the community, including comments.
• Usage and billing records. Which plan you are on, credits granted and spent, the cost of each build, when you were last active, and the payment records Stripe returns to us. We never see or store your card number.
• Connection data. If you connect a GitHub account, we store the connection and an encrypted token so we can push a tool to a repository at your request.

What we do not collect

• We do not run advertising, and we do not sell or share personal data for advertising or any other purpose. There is nothing here to opt out of.
• We do not run third-party analytics or advertising trackers on the site.
• We do not ask for a date of birth, a phone number, a postal address or a government identifier, and you should not send them to us.

Why we are allowed to hold it

Under the GDPR we rely on three legal bases. Account data, content and connection data are processed to perform the contract you enter into when you use the service. Billing records are processed to comply with a legal obligation, since tax law requires us to keep them. Security logging and abuse prevention rest on our legitimate interest in keeping the service working for everyone.

Where we ever rely on consent, we will ask for it separately and you will be able to withdraw it as easily as you gave it.

Who else processes it

Rendeer is a small service built on other people’s infrastructure. Each of the following is a processor acting on our instructions, and each holds only the data it needs to do its job.

• Supabase, for the database and for sign-in.
• Hetzner, for the server that builds your tools. It runs in Falkenstein, Germany.
• Vercel, for serving this website.
• Stripe, for payments. Stripe is the controller of your card details, not us.
• Resend, for the few emails we send, such as the warning before an idle account is cleaned up.
• AI model providers, for generating tools. Your prompt and the source of the tool being built are sent to the provider running that build. We use providers who contractually do not train on data sent through their API.

Where it goes

The build server is in Germany. Some processors listed above are established in the United States, so your data is transferred there. Those transfers rely on the European Commission’s standard contractual clauses, which are part of the agreement each of those providers publishes.

How long we keep it

Built tools are storage, and storage costs money, so an account that goes quiet is eventually cleaned up. The schedule is fixed and you are always warned first.

• After 60 days with no activity, we email you a warning.
• After 90 days with no activity, and never less than 30 days after that warning was sent, the built copies of your tools are deleted. The source and the record of the tool are kept, so a rebuild is free and produces the same tool.
• If you have ever paid us anything, both windows double, to 120 and 180 days.
• An account with an active subscription is never touched by this process.
• Billing records are kept for as long as tax law requires, currently seven years, and are not deleted on request.

Your rights

If you are in the UK, the EU, or a country with comparable law, you have the right to get a copy of your data, correct it, delete it, restrict or object to what we do with it, and take it elsewhere in a portable form. If you are in California, you have the right to know what we collect, to delete it, to correct it, and not to be treated differently for asking.

Ask at hello@rendeer.design and we will answer within 30 days. Deleting your account deletes your tools, your published work and your profile. It does not delete the billing records described above, and it does not retract a copy of your published tool that somebody else already remixed, because that copy is now their work.

If you think we have handled your data badly, you can complain to your national data protection authority. In the EU that is the authority where you live; in the UK it is the Information Commissioner’s Office.

Cookies and local storage

We set no advertising or analytics cookies, so there is no consent banner. Sign-in uses a session token, and the site keeps a few preferences in your browser’s local storage, such as your theme, the width of the chat rail, and a cached copy of your own tool list so a reload is instant. All of it is strictly necessary or set by you, and none of it leaves your browser.

Security

Everything is served over HTTPS. Passwords are handled by Supabase and never reach our server. GitHub tokens are encrypted before they are stored. Builds run in isolated containers with a memory ceiling and a wall-clock limit, so one build cannot reach another.

We are a small service and we will not pretend to a certification we do not hold. If you find a security problem, write to hello@rendeer.design and we will respond.

Children

Rendeer is not for anyone under 16. We do not knowingly collect data from children, and if we learn that we have, we will delete it.

Changes

If we change this policy in a way that matters, we will email the address on your account before the change takes effect. The date at the top is the date this text last changed.