Privacy Policy
Last updated October 2026
1. Overview
This Privacy Policy explains what Renderball (“we”) collects, why, and your choices. It applies to renderball.com and the Renderball service. Renderball is operated by Flarebit, Corp., a Delaware corporation, 131 Continental Dr, Suite 305, Newark, Delaware 19713, United States.
2. What we collect
Account data: your name and email, provided through our authentication provider when you sign up or sign in.
Content you provide: briefs, prompts, uploaded brand assets (logos, images), and the website URLs you ask us to analyze.
Usage data: the documents you generate, build and export history, and basic technical logs needed to operate and secure the Service.
Payment data: processed by our third-party payment processor, Stripe. We do not store your full card details.
3. How we use it
To provide and improve the Service: authenticating you, generating and building your documents, hosting your files, processing payments, preventing abuse, and providing support. We do not sell your personal information.
4. AI assistants
You can connect Renderball to an AI assistant you use, such as ChatGPT or Claude. You sign in with your Renderball account, which gives the assistant an access token: with it, the assistant can use Renderball’s tools on your designs and see your account’s name and email address. It sends us your brief, your brand details and the pages it writes; we send back each page’s instructions, the rendered pages as text and images, and the links to your design. What you tell the assistant, and what it does with our replies, is governed by that assistant’s own terms and privacy policy.
For each design made this way we keep an activity record: which Renderball tools were used and when, a label naming the assistant, the brand details it gave us (name, website, colours and fonts), and the one-line direction it wrote for each page. We use it to support you and to improve the Service. It is stored with the design and deleted with it; a copy goes to our server logs, which our hosting provider keeps for a limited time. You can disconnect Renderball in your assistant’s settings at any time.
5. Subprocessors
We share data with vendors that help us run the Service, only as needed to provide it. These currently include: authentication (Clerk), AI model inference (Anthropic, whose Claude models write, check and edit your documents and read brand websites you submit), website screenshots and logo lookups for brand websites you submit (Microlink, Clearbit), network delivery, security and email forwarding (Cloudflare), file and database storage (Cloudflare R2, Neon), application hosting (Railway), stock imagery lookup (Pexels), and payments (Stripe). Each processes data under its own terms.
6. Retention and deletion
We keep your account, your designs, their files and their activity records until you delete them. Designs made without an account are deleted 7 days after they are created unless you sign in to keep them.
You can delete a design from your designs page, stop sharing a design from the editor’s Share menu, and delete your whole account from your account page. When you delete a design or your account, we remove it from our database and file storage; copies in our providers’ caches, backups and server logs are removed on their own schedules. You can also ask us for access to, correction of, or deletion of your personal data by email. After a deletion we keep only usage records (which account and design used how many tokens, and when, never their content) for billing, the record of credits you bought, used and were refunded (which we keep for tax, refunds and chargebacks), and records the law requires, such as payment records held by Stripe.
7. Cookies
We use only the cookies the Service needs to work: to keep you signed in (through our authentication provider) and to keep a design you made without an account. We do not use advertising or analytics cookies.
8. Security
We use industry-standard measures to protect your data, including access controls and encrypted connections. No system is perfectly secure, but we work to safeguard your information.
9. Children
The Service is not directed to children under 18, and we do not knowingly collect their data.
10. Changes
We may update this policy; material changes will be posted here with a new effective date.
11. Contact
Privacy questions or data requests: [email protected].