Skip to content
Start free trial

Privacy Policy

Last updated: September 23, 2026

RD Apex Software LLC, a Utah limited liability company doing business as FloorCast3D, operates FloorCast3D. This page explains what we collect, why, and who else sees it. FloorCast3D has two parts that work very differently — the application on your computer, and this website — so we cover them separately, starting where your actual work lives.

The application: your projects live on your computer

Your layouts, drawings, exports, customer names, pricing, and branding are files on your own machine. The application is a desktop program with its own window — as of version 2.0 it runs no network server unless you turn on phone transfer (described below). (Versions before 2.0 showed their interface in your web browser through a small server reachable only from your own machine.) Your project data stays on your computer unless you use one of the optional features below that sends part of it elsewhere, and none of them sends it to us. We operate no server that receives any of it. We cannot see your projects, and we could not produce them if someone asked us to. Your saved settings — rate card, company details, logo, capacity catalog — are likewise files in your own Windows app-data folder, not accounts on our systems.

Two automatic behaviors are worth knowing. The application deletes generated output packages after 30 days (or once more than 200 accumulate) to keep them from filling your disk — packages can be regenerated from a saved project, but if you need one kept, save it somewhere of your own; this is not a backup service and we hold no copy. Before deleting, the application writes a line to a local record (customer name, date, filenames, sizes) that is kept indefinitely so you can see a package existed — it is a file on your computer, never transmitted, and yours to delete.

The application also writes a local diagnostic log to help troubleshoot problems. It stays on your machine and is not uploaded; if you send it to us for support, you are sending it deliberately, and you should look at it first.

When something goes wrong, the application saves a crash report beside that log: what failed, where, which version, and the recent log lines. It holds no part of your layout, it is shown to you in full before you copy it, and nothing is sent anywhere. The last twenty are kept for thirty days, and a button deletes them all.

A few pieces of network traffic are worth knowing about. When the application starts, unless it already had an answer in the last 24 hours, and whenever you press Check for updates, it asks floorcast3d.com whether a newer version has been released. The request identifies itself only as FloorCast3D and carries nothing about you or your projects; like other requests to this site, it shows us your computer’s IP address and the time of the request in our hosting provider’s logs, described below. The answer is a version number and a link, and the application never downloads or installs anything on its own. If a newer version exists you get a dismissible notice and you decide whether to go and get it.

The application also contacts floorcast3d.com about its licence. Whenever it starts while online with no licence on file, it asks for its 14-day trial by sending the install identifier described in the next paragraph and nothing else: no name, email address or project data. We keep that identifier with the trial’s key and expiry, so the same computer normally gets the same trial back rather than a new one. Once the application has a key, whether the trial’s or one you entered, it sends that key to renew its signed licence: a record of your licence, signed by us and kept on your computer, that lasts at most 14 days. While it has no active paid licence it does this every time it starts; with one, only when the signed licence is within three days of expiring. It also sends the key whenever you enter one in Settings. These requests carry the key and nothing else. Our licence records do not include your IP address, but like other requests to this site, these requests pass through our hosting provider, Cloudflare, and we can search its logs of them, which include your IP address, for up to seven days.

Usage sharing is off unless you switch it on. If you turn it on in Settings, the application tells floorcast3d.com when four milestones happen: it was opened, a project with racking in it was saved, a package export succeeded, or a package export failed. Each is reported at most once per day (days are counted in UTC), together with the application version, the licence status of the copy (trial, licensed, lapsed or locked), and the install identifier the application uses to start its trial. That identifier is normally a one-way digest the application derives on your computer from Windows’ machine identifier; the machine identifier itself is never sent and the digest stays the same if you reinstall. If that identifier cannot be read, the application makes up a random one instead and keeps it in its own settings folder. Either way, our records do not link it to a name or email address. Nothing from inside a project is sent: no names, files, dimensions, quantities, prices or text. We do not store your IP address with these records; like any request to this site, an upload does appear in our hosting provider’s standard request logs, described below. The records are deleted after 400 days. Nothing is recorded before you switch it on; switch it off and the application stops recording at once and discards anything still waiting to be sent.

Three more features use the network, and only when you use them. If you press Enable phone transfer, the application listens on port 5366 on every network your computer is connected to, so that a phone running FloorCast Field can send it site surveys over Wi-Fi. It answers only devices with private network addresses, such as those on an office or home network, and refuses the rest. Any such device that asks is told this computer’s name; a phone can send surveys only after you pair it with a one-time code shown on your screen, and it stays paired until you press Revoke access. What arrives goes into an inbox on your computer, and nothing passes through us. Transfers are not encrypted: the pairing code, the phone’s access token and the surveys cross your network as plain HTTP, so use phone transfer only on a network you trust. The receiver runs whenever FloorCast3D is open, including after you restart it, until you press Stop receiving. If you press Look up Ss / S1 from USGS, the application sends the latitude and longitude of the centre of the job site’s ZIP code, worked out on your computer, to the U.S. Geological Survey’s seismic design service, and nothing else about the project. And if an administrator of a warehouse management system (WMS) your organization runs has given you a connection file, pressing Publish layout sends that WMS server the layout (every storage position, the shape and position of every modelled object from racking to walls, doors and docks, the zone names and the building’s dimensions) together with the project’s customer name and the application version. None of it comes to us.

AI features: off unless you turn them on

Optional AI features require you to enter your own Anthropic API key in Settings. Three features send content to Anthropic, and this is the complete list: floor-plan analysis sends the plan or drawing file you upload; obstacle extraction sends the free-text notes you write about a warehouse together with its dimensions; and “Describe it” sends the building description you type. In every case the content goes from your computer directly to Anthropic, under your API key, your account, and your own agreement with Anthropic — it does not pass through us, and we do not receive, store, or see it. If your facility layouts are confidential — particularly if they belong to your own client — read Anthropic’s terms before enabling these features. If you never enter a key, the app sends nothing to Anthropic.

This website: what we collect

  • Design-partner applications — the name, company, email address, timeline, and message you submit on the /partners form. The address is also kept in our own contact records, the same way a sample download is, so we can follow up.
  • Sample-file downloads — the email address you enter at the download gate, which we store in our own contact records alongside the campaign or page you arrived from. The file itself downloads immediately in your browser; the address is not used to deliver it.
  • Trial and licence records — when you request a trial key or subscribe, we store the email address you used (or, for a trial the application started itself, its install identifier), the licence key we issued to it, and its status and expiry, so the app can validate your licence and we can resend your key.
  • Billing records — for subscribers, the customer and subscription identifiers Paddle assigns, the subscribed plan, the subscription’s status, and any scheduled change to it, so the site and app can check whether your subscription grants access.
  • Server logs— our hosting provider, Cloudflare, records each request to this site, including the requests the application makes: the IP address, the time, the full address requested, and the request’s headers, which include the browser’s user-agent and language, the referring page and any cookies. We have this logging switched on for security and reliability, and we can search those records for up to seven days. We also keep our own request log for this site — page, time, IP address, country, browser and its language, network operator, the Cloudflare data centre that served it, referring page and campaign parameters — for 90 days, to tell people from automated traffic and to see which campaign led to a trial. Browsers that send the Global Privacy Control signal are left out of our own log, though not out of Cloudflare’s records.
  • Site analytics — we record which pages you view, how long they stay on screen, how far you scroll and what you click, using two first-party cookies (fc3d_vid, one year; fc3d_sid, 30 minutes) and a small script that reports only to this site. No analytics vendor receives it. When you open a checkout we attach a one-time reference to your Paddle transaction so we can connect the purchase to the visit that led to it.
  • Company identification — we use Apollo.io’s website tracker to recognize, where it can, which companies visit this site and which pages they viewed, so we can follow up with businesses that look like a fit. It may set cookies or similar identifiers and works at the company level; it does not load on the post-checkout page.
  • Ad conversion measurement — if we are running a Google Ads campaign, the Google tag (gtag.js) loads so we can tell whether someone who arrived from one of our ads went on to download the sample package or request a trial. It may set cookies. We turn ad personalization off in the tag and do not build remarketing audiences from it; it does not load on the post-checkout page.
  • Our own contact records — the addresses we hold from a sample download, a trial request or a design-partner application are read by our own private contact system, together with whether each has since become a trial or a subscription, so we can follow up usefully. No third-party CRM script loads on this site and nothing about your visits is copied to one.

We use this to respond to your application, record sample downloads and send occasional product updates only where you asked for them (stated at the gate, with an unsubscribe in every email), issue and validate licence keys, ask each trial user once, about halfway through the trial, what one missing thing they would add (that email carries its own unsubscribe), write each trial user a personal note from Ryan (see Anthropic below), and understand in aggregate how the site is used, including whether an ad we paid for led to a download or a trial. We don’t use your information to target ads at you, and we don’t build advertising profiles.

Who else is involved

  • Anthropic— in two ways. In the app, only if you enable the AI features, and only under your own API key, as described above; we are not a party to that exchange. Separately, when you start a trial with your email address, we send details from your contact record (your name, the domain of your email address but never the address itself, your company, website, job title, how you found us, when you signed up, and a short record of your trial and enquiries with us) to Anthropic’s Claude, which looks up public information about your company and your job title on the web and drafts a personal note from Ryan. Ryan reads every note before anything is sent, and nothing is sent automatically. The draft and those research notes are kept with your contact record.
  • Cloudflare — hosts this site, stores our analytics and licence databases, and keeps the request records described under Server logs above.
  • Web3Forms — delivers design-partner form submissions, sample-download email addresses and network-rack interest form submissions (what you wrote, your email and company) to our inbox, where they stay until answered.
  • Paddle — our merchant of record for checkout and billing. Paddle handles your payment details, tax, and receipts directly; we don’t receive or store your card information.
  • Resend— delivers trial, licence-key and trial feedback emails, and receives the recipient address and the message content to do so. It also delivers our own internal alerts about licence emails that bounced or failed, which include the customer’s email address.
  • U.S. Geological Survey— only if you use the seismic lookup in the application, and then only the location of the job site’s ZIP-code centre, as described above, plus your IP address as with any website, under its own policies.
  • Apollo.io — runs the company-identification script described above and matches visits against its business database, under Apollo’s own privacy policy.
  • Google — if we are running ads, the Google tag reports conversions (sample download, trial request) back to Google Ads, under Google’s privacy policy.

We don’t sell personal information.

Cookies

We set two cookies of our own: fc3d_vid identifies your browser to this site for a year so we can recognise a return visit and connect a trial request or purchase to the visit that led to it, and fc3d_sid groups one visit’s pages for 30 minutes. Neither is shared with anyone. Four third-party scripts also set cookies. Paddle’s checkout script loads when you open our pricing page — not only when you start a checkout — and it may set its own cookies at that point under Paddle’s privacy policy. Apollo.io’s company-identification script, described above, may likewise set cookies or similar identifiers to recognize returning visits, under Apollo’s privacy policy. The Google tag, when an ads campaign is running, may set cookies to attribute a download or trial request to an ad click, with ad personalization turned off. All three are governed by their own terms.

How long we keep it

Site information is kept as long as needed for what it was collected for — application details until we’ve responded and followed up, a download-gate email until you unsubscribe. Licence and billing records are kept for as long as we operate the licensing service — including expired trials, so the same address gets the same key back — unless you ask us to delete yours. Usage milestones shared by the application are deleted after 400 days. Raw analytics records (page requests, page views, clicks) are deleted after 90 days; a per-visitor summary (first and latest campaign source, page count, human-or-automated classification, and the email address if you requested a trial or the sample package) is kept while we operate the site. Contact records from the download gate, trial requests and design-partner applications are kept until you ask us to delete them or unsubscribe; asking us covers both that record and the address held in the visitor summary. Your project data is on your computer and governed by your own retention, not ours.

Your choices

Email support@floorcast3d.com to access, correct, or delete personal information we hold about you, or to unsubscribe. We’ll handle your request within any period the law requires, and sooner where we can. Depending on where you live you may have additional rights over your personal information — ask and we’ll tell you what we hold. Sending the Global Privacy Control signal from your browser stops our own request log, our cookies, the page analytics, including for a browser that picked up one of our cookies before you turned the signal on (Cloudflare’s seven-day request records, described above, still apply). Blocking or clearing cookies for floorcast3d.com also stops the page analytics. The site works either way.

Children’s privacy

FloorCast3D is a professional tool, is not directed at children under 16, and we don’t knowingly collect information from them.

Changes to this policy

As FloorCast3D evolves, we may update this policy. We’ll update the date above when we do, and give notice of material changes.

Contact

Questions about this policy? Email support@floorcast3d.com · RD Apex Software LLC