Skip to content

Privacy Policy

Updated

Who we are

RenderSplash is run by Fleet and Fury LLC, a Wyoming company (30 N Gould St, Ste R, Sheridan, WY 82801, US). This policy covers rendersplash.com, the RenderSplash app and the free pool visualizer. We decide why and how your information is used. Our contact for anything privacy related is privacy@rendersplash.com.

What we collect

Account information: your name, email, business name, and password when you sign up. Your password is stored as a hash, not as plain text.

Content you upload: rendered stills, flythrough videos, 2D plans, 3D files, and site photos you give us to make a video, plus the finished videos we generate for you.

Payment information: collected and stored by Stripe, not by us. We never see or store your card number.

Usage information: basic technical logs, such as IP address, browser, and the pages requested, that help us run and secure the service.

Waitlist and email forms: if you leave your email on the waitlist or on a form on our blog or help pages, we keep that address, the page you were on, the campaign tag on the link you used and how you found us (see Cookies). We use it to write to you about RenderSplash. Ask us to remove it at any time and we will. These forms are for builders. Homeowner details from the pool visualizer never go on this list.

Free trial video: if you try RenderSplash before you sign up, we keep your email address (confirmed with a code we send), the renders you upload and the video we make. If you do not keep it by creating an account, we delete the renders, the pictures made from them, the video and the email address 30 days after the video was made.

Free pool visualizer: the photo you add (we re-encode it, which removes any location stored in the file), the area you mark and the options you pick, your email if you give one, and an approximate location taken from your network connection (country, state or region, city, and coordinates rounded to about 10 km). We use the location to understand where interest in the visualizer comes from. We do not store your IP address for this, only a one-way hash that limits how many pools one person can draw a day. If you ask for your design and planning range by email, we keep that email address, your state and the choices you made, only to send it and for 30 days. We do not add it to a mailing list. The photo, the image, the email and the location are deleted 30 days after you submit. The photo is sent to AI providers to draw the pool (see Who processes your data). We also keep where the visit came from (see Cookies) and your device type, browser and operating system. That record holds no name, email or network address, and it stays after the 30 days so we can count which pages and campaigns help people. We also log the steps you took on the visualizer (for example that you viewed the result or left your details), without anything you typed.

Talk to a pool builder: if you leave your details on the visualizer, we keep your first name, email, optional phone and ZIP code to email you about your pool. If you press "Talk to a pool builder about it" and tick "Share my name, email, phone and ZIP with one pool builder near me so they can contact me" (it is never ticked for you), a person on our team will email you about finding a builder near you, and we may share your name, email, ZIP and phone (if you gave one) with one pool builder near you so they can contact you about that pool. We record that you asked and when. We do not add these details to a mailing list. We share them with no one else except the services that run RenderSplash, and we never sell them. We keep them until you ask us to delete them: email privacy@rendersplash.com and we will.

Homeowner videos: when you buy a video, the email you give us for the receipt and the video, the picture the video is made from (the visualizer picture or the pool idea), your yard photo when the video opens on it, the video you chose and the family you picked, and the Stripe payment reference. We copy the pictures from the visualizer, because the visualizer deletes its own copy after 30 days. We never collect a photo of you or your family: the people in the video are AI characters from our own library.

Anything you send us directly: messages through our contact form, and anything you tell us by phone or email.

Cookies and similar technologies

We use cookies of our own, and none of them follows you to another website:

  • Signing in. A cookie that signs you in and keeps you signed in, provided through Supabase, our authentication provider. Without it you would have to sign in on every page.
  • Remembering how you left a screen. A cookie called sidebar_state that stores whether the sidebar in the signed-in app is open or closed. It holds one word.
  • Remembering how you found us (rs_ft and rs_lt). They keep, for 90 days, how you first and most recently arrived: the campaign tag on the link, the site that sent you (its address without any search terms), the page you landed on and an ad click id. When you make a pool picture or leave your email, we save that with it, along with your device type, browser and operating system, so we can tell which pages and campaigns help people. They hold no name, email or network address. They are not set on our staff console or for people who opt out below.
  • Where you are (rs_region). It holds one word, eu or other, chosen from the country your network connection appears to be in, and lasts 30 days. We use it to decide whether to load Microsoft Clarity (see Analytics).
  • Microsoft Clarity (_clck and _clsk). Clarity sets these two itself, and only when Clarity loads for you (see Analytics). _clck lasts about a year and holds a random identifier that tells a return visit from a new one. _clsk lasts about a day and ties the pages you view into one session. They hold no name, email or network address.
  • Opting out (rs_no_track). It holds 1 or 0, lasts a year, and tells our own pages not to load analytics or advertising tools for you. See "Your choices and rights" for how to set it.

Your browser also keeps a few settings for you on your own device, such as your light or dark theme and the choices you made on the pool visualizer. These do not leave your browser.

Other companies set their own cookies when you use their tools on our site: Google Analytics (described under Analytics), Meta (below), and Stripe when you pay on its page. If you use Sign in with Google, Google may set cookies too.

We use a Meta Pixel. It is a small piece of JavaScript that Meta (Facebook) places when you visit our site. It records which pages you viewed and whether you took a step such as signing up or buying a plan, so that we can measure how our ads perform and show relevant ads to people who have visited. When you sign up, join a list or buy, we also tell Meta about it from our server (Meta's Conversions API). That message can include a hashed (scrambled) version of your email address, your IP address and browser details, so Meta can match the step to an ad. Meta stores this data and may use it as set out in Meta's privacy policy.

We do not currently show a cookie banner. Analytics and advertising tools load when you arrive, except for the cases in "Your choices and rights" and Microsoft Clarity, which does not load for visitors in the European Economic Area, the UK or Switzerland.

Analytics

We use Vercel Web Analytics, and Umami, an open-source analytics tool we run on our own server, to see which pages get used, where the site is confusing, and how many people finish a step such as signing up, sending the contact form, or buying a plan or credits. They record the page address, the site that sent you, your browser, device type and country, and the name of the step, with the plan or amount for a purchase. Neither sets a cookie, neither follows you to other sites, and both give us counts rather than people. We cannot use them to identify you. Google Analytics, described next, does set cookies.

We also use Google Analytics 4, provided by Google LLC, on rendersplash.com. It sets first-party cookies (named _ga and _ga_ followed by our property id) that hold a random identifier, so it can tell a return visit from a new one. It records the pages you view, the site that sent you, the campaign tag on the link you used, your browser, device type, approximate location (country and city, taken from your network address, which Google does not store), how long you stayed, and the steps you take: signing up, sending a form, viewing a sample video, buying a plan or credits (with the amount). It never receives your name, email address or payment details, and the addresses of private links are shortened before they are sent. We have turned off Google signals and ad personalization, so we do not use it for advertising. Google processes this data for us. You can stop it by installing Google's Analytics opt-out browser add-on, and you can learn more at Google's privacy policy. Our own staff and test visits are not counted.

We also use Microsoft Clarity on our marketing pages, the free try page and the sign-in, sign-up and setup pages, except for visitors in the European Economic Area, the UK and Switzerland. Clarity records session replays and heatmaps so we can see where the site is unclear or broken: mouse movements, clicks, scrolls, and a recording of the page as it appeared during your visit. It sets two cookies of its own, _clck and _clsk (see Cookies), so it can join your page views into one visit. On the sign-in, sign-up and setup pages everything on the page is masked, so nothing you see or type there is recorded. On the other pages Clarity records, form inputs (email address, name, message) are masked. Clarity never runs in your project workspace or on your videos or uploaded designs. Microsoft stores this data. You can learn more at Microsoft's privacy statement.

Who processes your data

We use the following companies to run RenderSplash:

  • Supabase for our database, file storage, and account sign-in, hosted in the us-east-1 region (Virginia, United States).
  • Stripe to process subscription payments, credit purchases and the payment for a homeowner video. We never see your card number.
  • Resend to send our emails (receipts, video-ready notices and replies to your questions), and Slack for internal team notices that can include your name, email, ZIP and phone when you ask for a pool builder.
  • Vercel to host the website and the application, and for cookieless website analytics.
  • Cloudflare for our domain name (DNS) records.
  • Umami (self-hosted by us) for cookieless page and event analytics.
  • Google LLC via Google Analytics 4 for website analytics. See Google's privacy policy and the opt-out add-on.
  • Microsoft Clarity for session recordings and heatmaps on our marketing pages, the free try page and the sign-in, sign-up and setup pages, with form inputs masked everywhere and all text masked on sign-in, sign-up and setup. See Microsoft's privacy statement.
  • Meta (Facebook) via the Meta Pixel for ad performance measurement and retargeting. See Meta's privacy policy.
  • OpenAI, Google, and BytePlus (a ByteDance company), whose AI models process the pictures and photos you give us. For a builder, they generate the photoreal key frames and the finished video from the files you upload. For the free pool visualizer, your yard photo and the area you marked are sent to OpenAI, which draws the pool onto the photo, and a small copy of the photo goes to Google (Gemini) to check that it is a usable yard photo. For a homeowner video, your yard photo and the visualizer picture are sent to these providers too: OpenAI checks and describes the pictures and can redraw the yard before the pool; BytePlus (Seedream) can widen an upright photo and draws the family's portraits, and BytePlus (Seedance) or Google (Gemini Omni) videos the video; Google (Gemini) checks the widened photo. We do not use your uploads or your finished videos to train models.

We also share information when the law requires it, to protect our rights or someone's safety, or if the business is sold or merged. We do not sell your personal information for money.

Where your data is stored

Your account data, uploads, and videos are stored on Supabase infrastructure in the us-east-1 region (Virginia, United States). RenderSplash is run from the United States. If you use it from another country, your information is sent to and handled in the United States, and our other providers may handle it elsewhere. Storage buckets are private: a file is only ever reachable through a short-lived signed link generated at the moment you or your team view it.

How long we keep it

Uploads and finished videos are kept while your account is active so you can come back to a job, and you can delete any of it yourself at any time. If you close your account, we delete your content within a reasonable period afterward, except where we need to keep something briefly for a legal or accounting reason.

We keep email addresses on the waitlist and email forms until you ask us to remove them. Details you leave for a pool builder are kept until you ask us to delete them. Records of where visits came from and of the steps taken on a page are kept without names or contact details.

Free pool visualizer submissions are different: the photo, the image, the email and the approximate location are deleted 30 days after you submit, and the location is deleted with them. An emailed planning range (the address, state and choices) is deleted after 30 days too.

Homeowner videos: the video, its page, the pictures it was made from (your yard photo, the visualizer picture or the pool idea, and the pictures made while preparing the video) are deleted 60 days after the video is ready. We delete your email address with them, unless your refund could not be sent automatically, in which case we keep it until a person has reached you. The payment record stays with Stripe and in our accounts for as long as the law requires us to keep financial records.

Connecting RenderSplash to ChatGPT

You can link your RenderSplash account to ChatGPT through the RenderSplash connector in ChatGPT's settings. This section describes what happens when you do.

What ChatGPT can access

When you connect, RenderSplash shows you the permissions ChatGPT is asking for, and you allow or cancel. RenderSplash uses OAuth 2.1 with PKCE, a standard authorization protocol. The permissions ChatGPT requests by default are: view your projects and renders; create projects and upload renders; view your videos; generate videos (which spends credits); and view your credit balance. ChatGPT can only act within the permissions you allow, and a video will not start until you confirm the credit cost.

What we receive and what we send back

ChatGPT sends us tool requests, such as a project ID to retrieve its renders, an image URL from a file you share in the conversation, or a choice of video resolution. We send back project names, video status, links to your renders and videos that expire within one hour, a share link for any video you choose to share (it works until you switch it off), and credit balances. We do not receive the contents of your ChatGPT conversation beyond those tool requests.

Renders fetched from image URLs you share in ChatGPT are stored in our Supabase Storage the same way as any render you upload directly. The same retention described above applies, and you can delete them from your project at any time.

Tokens and security

Access tokens expire after one hour. Refresh tokens expire after 30 days and rotate on every use, so each refresh produces a fresh set of tokens. We never store tokens in plain text: both access and refresh tokens are kept only as SHA-256 hashes in our database.

What we log

Every ChatGPT tool call is recorded in an audit log for security and rate-limit purposes. Each log entry stores the tool name, whether it succeeded or failed, an error code if it failed, how long it took, and the date and time. Audit records are kept for as long as your account is active.

How to disconnect

Go to Settings, then Connected apps, and click Disconnect next to ChatGPT. Access is revoked immediately. You can also disconnect from ChatGPT's own settings. Revoking access does not delete any projects, renders, or videos in your account.

OpenAI's privacy policy

OpenAI's handling of your ChatGPT conversation, including text you type and files you share, is governed by OpenAI's privacy policy. We do not receive that conversation beyond the tool requests described above.

YouTube API Services

RenderSplash uses YouTube API Services to publish our own videos to the RenderSplash YouTube channel. Only RenderSplash staff use this connection, through our own admin console. It never acts on a visitor's or a customer's YouTube account, and it collects no data from the people who watch our videos. What we keep from it is the access token for our own channel, stored encrypted, and the YouTube ids of the videos we upload.

By using YouTube API Services we are bound by the YouTube Terms of Service, and Google's handling of data is described in the Google Privacy Policy. Access that RenderSplash holds to our own channel can be revoked at any time from the Google security settings, and we can disconnect it from our admin console.

Your choices and rights

Opt out of tracking. Visit rendersplash.com/?track=off in each browser you use. It sets the opt-out cookie described above. After that, our pages do not load Google Analytics, Umami, Vercel Analytics, Microsoft Clarity or the Meta Pixel for you, do not set the "how you found us" cookies, and we do not send Meta server events about you. Clearing your cookies resets it. You can also use Your Ad Choices, your browser's settings, or Google's Analytics opt-out add-on.

Your rights. Whatever country you live in, you can ask us to:

  • tell you what personal information we hold about you and give you a copy;
  • correct it;
  • delete it;
  • stop using it for a purpose, or hand it to you in a portable format, where the law gives you that right.

Email privacy@rendersplash.com from the address we hold for you. We may need to confirm it is you before we act. We answer within the time the law allows (45 days for California requests, one month under the GDPR). You can edit your profile and delete projects and videos inside RenderSplash. To close your account or have everything deleted, email us. We will not treat you worse for using these rights.

California. Under the CCPA you may know what we collect, ask us to delete or correct it, and opt out of the "sale" or "sharing" of your personal information. We do not sell personal information for money. Our use of the Meta Pixel to measure and retarget ads may count as "sharing" for advertising under California law. To opt out, use the opt-out link above or email us. We do not knowingly sell or share the information of anyone under 16. In the last 12 months we collected the kinds of information listed in "What we collect" (identifiers like name, email and network address, commercial information like purchases, internet activity, approximate location, and the pictures you gave us) for the purposes described in this policy. You can use an authorized agent to make a request.

EEA, UK and Switzerland. You also have the right to object to our use of your information, to withdraw consent you gave us, and to complain to your local data protection authority. We use your information to give you the service you asked for, to run and secure it, to measure how it is doing and to advertise it, and where the law requires it, with your consent.

Children

RenderSplash is a business tool for outdoor construction companies. It is not directed at children, and we do not knowingly collect information from anyone under 18, which includes anyone under 13 and under 16. If you think a child has given us information, email privacy@rendersplash.com and we will delete it.

Changes to this policy

We may update this policy as the product changes. We will update the date at the top of this page when we do, and for a big change we will tell account holders by email.

Contact

Questions about this policy or a request about your data: privacy@rendersplash.com. Fleet and Fury LLC, 30 N Gould St, Ste R, Sheridan, WY 82801, US.