Skip to content
FloorCast3D

Privacy Policy

Last updated: August 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 stay 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 server of any kind, not even a local one, and your project data never leaves your computer. (Versions before 2.0 showed their interface in your web browser through a small server reachable only from your own machine.) 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.

One more piece of network traffic, so the list is complete. At most once a day the application asks floorcast3d.com whether a newer version has been released. That tells us your computer’s IP address and the time of the request, the same as visiting this page does; it sends nothing about you or your projects. 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.

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, nothing is ever sent.

This website: what we collect

  • Design-partner applications — the name, company, email address, timeline, and message you submit on the /partners form.
  • Sample-file downloads — the email address you enter at the download gate. 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, 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, automatically records standard request data (IP address, browser user-agent, timestamps, pages requested) for security and reliability.
  • Cookieless analytics — if enabled, we use GoatCounter to count page views in aggregate. It doesn’t use cookies, doesn’t fingerprint devices, and doesn’t build a profile of you individually.
  • 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.
  • CRM and lead tracking — HubSpot’s script loads so we can tell which pages a visitor read, and when you request a trial we store your email address in our CRM (HubSpot) together with that visit history, so we can follow up usefully. It may set cookies; it does not load on the post-checkout or account pages.

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, 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 — 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.
  • Cloudflare — hosts this site and sees standard server logs.
  • Web3Forms — delivers design-partner form submissions and sample-download email addresses to our inbox.
  • 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 and licence-key emails, and receives the recipient address and the message content to do so.
  • GoatCounter — if enabled, provides cookieless, aggregate analytics.
  • 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.
  • HubSpot — our CRM. Receives trial request email addresses and the page-visit analytics described above, under HubSpot’s privacy policy.

We don’t sell personal information.

Cookies

We don’t set cookies of our own for tracking or advertising, and our page-view analytics are cookieless. Four third-party scripts are the exceptions. 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. HubSpot’s script sets the hubspotutk cookie and related analytics cookies to recognize returning visits and connect them to a trial request. All four 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. 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.

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