Privacy policy

1Who we are

1.1Rendergrid (rendergrid.io, “we”) is responsible for processing your data. Contact for data questions: support@rendergrid.io. We do not have a separate data protection officer (DPO): write to this address.

1.2This policy applies to the rendergrid.io website, the portal and the API.

2What data we collect

2.1Account data: email address, login details, settings, interface language.

2.2Usage data: request parameters (model, resolution, aspect ratio), time, status, cost, and the key used to make the request.

2.3Your content: the prompts and reference images you send, and the generation results.

2.4Payment data: top-up amount, wallet address and transaction hash, payment status. We hold no bank card data.

2.5Technical data: IP address, browser and device type, technical logs of requests to the website and the API.

2.6Correspondence with support and the requests you submit on the website.

2.7Google Analytics 4 receives information about page views on the website while analytics is on. Where the law requires consent, analytics is turned on only after you give it (see the Cookie policy). The analytics counter is not loaded on login pages, in emails or in the portal. Besides page views, we ourselves send Google Analytics 4, from our server, two account events: a balance top-up (the amount in US dollars, the operation number and the time) and the first successful API request of a new account (within 30 days of registration; it carries only the time). We send them only if you yourself allowed analytics, in the choice window or in “Cookie settings”. Your browser reports its saved choice to our server at every sign-in to your account and at every load of a portal page and, when analytics is allowed, the identifier from the _ga cookie as well, if that cookie exists. For the choice the last report applies; if a permission arrives without an identifier, we keep the one stored earlier. If the browser holds no saved choice (for example, where there is no choice window and analytics is on by default), it reports nothing, our record does not change, and no event is sent for an account that has never reported that analytics is allowed. The events are linked only to your browser’s analytics identifier. We do not send your email address, name, account identifier, IP address, API keys, prompts or results. Our server keeps your choice and this identifier with your account until the browser reports that analytics is off (then we record the refusal and erase the identifier, and events still waiting to be sent are not sent: we read the choice again before every send) or until you delete your account (then sending stops, and our record of the choice and our records of these events are erased). A change in “Cookie settings” stops the counter on the website at once, but it reaches our server only at your next sign-in or portal page load, because the pages with the settings do not know your session. Google keeps events already sent individually for at most 14 months, and only summary figures remain in its reports.

3Why we use it

3.1To provide the service: to create an account, accept requests, run generations, and keep the balance and refunds.

3.2To protect the service: to detect abuse, limit load and investigate failures.

3.3To contact you: emails about payment, keys, incidents and changes to the terms.

3.4To comply with the law and keep records.

4Prompts and images

4.1We send your request and references to the selected model so that it can create an image. The models belong to their makers, who may have their own data processing rules.

4.2We do not use your prompts, images and results to train models.

4.3Do not send data in requests that must not reach third parties: passport data, passwords, medical information.

5Who we share data with

5.1Providers of image generation models: the request and references, to create the image.

5.2The payment processor: USDT payment data.

5.3Hosting and file storage providers, email delivery providers and website protection providers: to the extent needed for them to work.

5.4Google: Google Analytics 4 analytics data: information about page views, while analytics is on, and two account events on the terms of clause 2.7.

5.5Public authorities: on a lawful request.

5.6We do not sell your data.

6International data transfers

6.1Servers and providers may be located in different countries.

7How long we keep data

8How we protect data

8.1We store a hash of the API key and its beginning (rg_live_ and 8 characters) so that you can recognize the key in the list; we show the key itself once, when it is created.

8.2Access to the portal is protected by account login; the session is kept in secure cookies (see the Cookie policy). The playground issues you a short-lived key for the duration of the session and keeps it only in the page’s memory: it does not end up in cookies or in the browser’s storage, and it is closed together with the session.

8.3Technical protection measures:

• The service runs in the DigitalOcean cloud (Amsterdam), in a closed Kubernetes cluster; there is no SSH access to the servers in the cluster.
• The database is managed PostgreSQL, reachable only from the internal network.
• Secrets are stored in encrypted files (SOPS) and enter the cluster at deployment; they are not in the code or the repository.
• The website and the API sit behind Cloudflare. The load balancer cannot be reached directly: its firewall admits only Cloudflare addresses.
• HTTPS certificates are issued and renewed automatically.
• Result files are kept in DigitalOcean Spaces storage (Amsterdam), behind Cloudflare, and are deleted automatically. A link to a result opens without logging in to an account: do not publish it if the image is not meant for everyone.
• The database has backups with point-in-time recovery; we rehearse the recovery.
• Login to the administrative part is separate and is blocked after several wrong passwords.

8.4No protection is absolute. If a data leak that affects you occurs, we will tell you and the authorities within the time the law requires.

9Your rights

9.1You can request access to your data, its correction, deletion, restriction of processing, portability and an objection to processing; and you can withdraw consent where processing is based on it.

9.2Write to support@rendergrid.io from your account email. We will reply within the time the law requires. If you believe we have violated your rights, you can contact the data protection authority in your country.

9.3Deleting your account erases your prompts; data we are required to keep by law remains for the period the law requires. The remaining balance is not refunded on deletion (see the Terms of use).

10Cookies

10.1Which cookies we use and how to manage them is described in the Cookie policy.

11Children

11.1The service is not intended for people under 18, and we do not knowingly collect their data. If you believe a child has created an account, write to us: support@rendergrid.io.

12Changes to this policy

12.1We may change this policy. We will tell you about material changes by email to your account address in advance. The date of the version is shown at the beginning of the document.