Privacy Policy

Effective from [[EFFECTIVE_DATE]]

This page explains what information Render Studio collects, what happens to the images you upload, who else receives them, how long things are kept and what your choices are.

1. Who is responsible

The service is operated by [[LEGAL_ENTITY]], [[POSTAL_ADDRESS]]. We decide how your personal data is used (in data-protection law: the "controller"). For any question about your data, or to use the rights in section 9, write to [[PRIVACY_EMAIL]].

2. What we collect

• Account details. Your email address; your password, stored only as a one-way hash that we cannot read back; whether and when the address was confirmed; when the account was created and when you last signed in; and the version of the Terms you agreed to, with the date.
• The images you upload. Input images, reference images and painted areas that you add in a tool. They are used to produce the result and are not kept on our server once the request has finished.
• Your prompts and settings. The notes you type, the options you choose in a tool, and the instruction text built from them that is sent to the image model.
• The generated images. Each result, a small preview of it, and the prompt and settings that produced it, stored in your private History.
• Credit movements. Every time credits are added to or taken from your account: the amount, the reason, the date and the resulting balance.
• Technical data. Your IP address, which is used to limit how many sign-ups, sign-in attempts and images can come from one network. Limits are also counted per account and, for sign-in and password-reset attempts, per email address. Each counter is a small file on our server that contains only a start time and a number. The file is named after a one-way hash of what is being counted (the kind of limit together with the IP address, account number or email address), so the address itself is not written into it. The hash is not keyed, however: someone with access to the server who already knows an address could work out which counter belongs to it. Our server also writes logs: usage logs (account number, tool, resolution, time, whether the request succeeded), error logs (technical error messages, which can include an account number) and a log of what administrators do (which administrator changed what on which account number). Our hosting provider keeps the usual web-server access logs (IP address, time, the address requested and the browser type).
• Emails that could not be sent. If outgoing email is switched off or not fully set up on the server, a message that should have gone to you (your email address, its text and the link in it) is written to a log file on our server instead of being sent.
• Messages you send us. If you email us, we keep the correspondence for as long as it takes to deal with your request and for our records.

We do not ask for your name, postal address or payment details on the website, and we do not build advertising profiles. Files you upload are sent on as you provide them, so they may include information stored inside the file, such as the place and time a photograph was taken; photographs that have to be rotated or resized in your browser lose this information before they are uploaded. Remove it yourself beforehand if it must not be shared.

3. Your uploads are sent to Google

Render Studio does not generate images itself. Every input image, reference image and prompt you submit is transmitted to the Gemini API, a service of Google, which produces the result and returns it to us. This happens for every image you generate; the service cannot work without it.

• The transfer is made from our server. Google does not receive your email address, your account number or your IP address from us, only the images and the instruction text.
• We send requests with Google's option to store the request switched off wherever the interface offers it. Google may nevertheless keep content for a limited time, for example to detect abuse, and decides this itself.
• Google processes this content under its own terms: the Gemini API Additional Terms of Service and its usage policies. Those documents say how Google may use submitted content and how long it keeps it.
• Google may process the content on servers outside your country, including in the United States (see section 8).

Do not upload material that you are not permitted to pass to such a provider, and do not upload images of identifiable people unless you are allowed to.

4. How long we keep things

• Uploaded input images: only while the request is being processed. They are not written to our storage.
• Generated images, with their prompt and settings: 30 days from the moment they were made. They are then deleted automatically. You can delete any image earlier in your History.
• Account details: until you delete your account.
• Credit movements: for as long as the account exists, and afterwards in anonymous form (see section 7).
• Sign-in session: up to 30 days after you last signed in, or until you sign out.
• Confirmation and password-reset links: they work for 3 days and 1 hour respectively, and stop working earlier once they are used or replaced by a newer one. We store only a hash of each link, never the link itself; that record is deleted 7 days after the link expired.
• Rate-limit counters: a counter covers at most 24 hours. Its file is removed by the server's regular clean-up once it has not been used for two days.
• Error, usage, administration and unsent-email logs: these have no fixed deletion date. A log file is closed when it reaches 5 MB and is deleted 90 days after that. On a site with little traffic a file takes a long time to fill, so an entry can be kept for considerably longer than 90 days. The record of which version of the Terms an account number agreed to, and of account deletions, is not deleted on a schedule: it is kept for as long as it may be needed as evidence; it contains no email address.
• Backups: our hosting provider makes backups of the server. Deleted data can remain in those backups for [[BACKUP_RETENTION]] before it is overwritten.

5. Who else receives data

• Google (Gemini API): your uploaded images and prompts, as described in section 3.
• Hostinger, our hosting provider: stores the website, the database and your generated images on its servers in [[HOSTING_LOCATION]] and handles the network traffic to them. It acts on our instructions.
• Email delivery: the confirmation, password-reset and account-deletion emails are handed to a mail service for delivery. That service receives your email address and the content of the message.
• Our staff: administrators of the service can see your email address, account status, credit balance, the number of images you have generated and your sign-up and last sign-in dates. The administration area does not show your images or prompts. They are stored on the server, which we and the hosting provider can technically access when this is needed to keep the service running or to investigate abuse.

We do not sell your data and we do not pass it on for advertising. We disclose data to authorities only where the law obliges us to.

6. Cookies and storage in your browser

• One sign-in cookie (rs_sid). It is set when you sign in or create an account, lasts up to 30 days and is removed when you sign out. It is strictly necessary to keep you signed in. A visitor who has never signed in receives no cookie. A browser that still presents an old or unknown rs_sid cookie may be given a fresh, empty one in its place; it identifies nobody.
• Local storage: the site remembers in your browser whether the menu groups in the sidebar are open or closed. This never leaves your device.
• Session storage: in one rare case (an image that could not be saved to your History is passed from one tool to another) the image is held in your browser's temporary storage until the next page has loaded.

There are no analytics, advertising or social-media cookies, no tracking pixels, and no fonts or scripts loaded from other companies' servers. Because only the strictly necessary cookie is used, there is no cookie banner.

7. Deleting your account

You can delete your account yourself at any time on the Account page. You are asked for your password and to type a confirmation word. Deletion takes effect immediately.

Deleted straight away

• all images in your History, their previews, prompts and settings;
• your email address and your password hash;
• any confirmation or password-reset links.

Every sign-in session stops working at the same moment. The session of the browser you used is deleted. If you were also signed in on other devices, the server may keep their session records, which can no longer be used and hold only your account number, for up to 30 days until they are cleaned up.

Kept after deletion

• The record of credit movements (amounts, reasons and dates). It stays attached to an empty account record with no name and no email address, and is kept so that our accounts remain complete.
• A keyed, non-reversible hash of your email address, for 12 months. The address is run through a one-way function together with a secret key held on our server; the result cannot be turned back into the address. Its only purpose is to recognise the same address if it signs up again, so that the free sign-up credits are not given out repeatedly. It is erased after 12 months.
• Log entries that refer to your account number, for the periods in section 4, and copies in backups until these are overwritten.

We send one last email to the address to confirm that the account was deleted. Any credits left on the account are removed with it. If you cannot sign in, reset your password first, or write to us from the address of the account.

8. Why we are allowed to use your data, and transfers abroad

• To provide the service you asked for (performance of a contract): your account, your uploads, your results, your credits and the emails needed to run the account.
• Our legitimate interest in keeping the service secure and affordable: rate limits based on IP address, account and email address, logs, and the hash of the email address kept after deletion to prevent repeated free credits. You can object to this (section 9).
• Legal obligations: where the law requires us to keep records.

Google, and possibly our hosting and email providers, may process data in countries outside the one you live in, including countries outside the European Economic Area and the United Kingdom such as the United States. Where the law requires it, such transfers are covered by safeguards such as an adequacy decision or standard contractual clauses agreed with the provider.

9. Your rights

Depending on where you live, you have the right to:

• ask what data we hold about you and receive a copy of it;
• have incorrect data corrected (an email address that is not yet confirmed can be changed on the Account page; for a confirmed address, write to us);
• have your data deleted (see section 7) or its use restricted;
• receive the data you gave us in a common format (you can download every image from your History yourself);
• object to uses that rest on our legitimate interest;
• complain to the data-protection authority of the country you live or work in.

To use any of these rights, write to [[PRIVACY_EMAIL]] from the address of your account. We may ask for a further check that the request really comes from you.

10. Minimum age

The service is intended for professional use and is not directed at children. You must be at least [[MIN_AGE]] years old to create an account. If we learn that an account belongs to someone younger, we will close it.

11. Changes to this policy

When the service changes, this policy is updated and the date at the top of the page changes with it. If a change significantly affects how your data is used, we will tell you by email or on the site before it takes effect.

12. Contact