Privacy, explained.
Last updated .
This notice covers the InspectDay website and the InspectDay apps: what they collect and why, and the choices you have.
Who we are
InspectDay is operated by MakerStudio Software LLC, a limited liability company registered in Wyoming, United States, at 30 North Gould Street, Sheridan, WY 82801. For privacy questions or requests, email team@inspectday.com.
This website
You can read every page without creating an account. The table below lists everything the website stores or sends.
What this website stores or sends
| Data | Purpose | Storage and retention | Your choices |
|---|---|---|---|
| Form fields before you send them | Write an enquiry to the InspectDay team | Your entries stay in the form on this page; the site does not save them in your browser. Until you send the form, clear the fields or leave the page. | Clear the fields or leave the page |
| Enquiries | Reply to your questions about InspectDay, and measure which of our ads bring enquiries | Your name, work email, company, number of inspectors and message are sent to InspectDay and stored with Netlify Forms. Our spam sorter uses TypeSafe’s jev to judge submissions, Resend to email genuine enquiries to our team inbox, and Discord to post genuine enquiries to our team’s private channel. Contact-field values are not sent to analytics. With ad measurement on, ad click identifiers from your arrival links are also held in your browser. Every held click identifier is included with your enquiry, along with the time we first saw each non-Google identifier and your answer where you allowed ad measurement. Your enquiry also includes where you first arrived, held in your browser with the click identifiers: the page you landed on with click identifiers removed, the site that referred you, by domain, where it was outside inspectday.com, and the campaign details. We upload genuine enquiries that carry a Google Ads click identifier to Google Ads, to measure our ads. The upload holds that identifier, the enquiry’s time and any ad measurement answer it carried, and nothing else from your enquiry. Allowing analytics does not turn ad measurement on. Kept while we follow up on your enquiry. Click identifiers and your first arrival held in your browser expire at submission or after at most 90 days, counted for Google Ads identifiers from your latest Google ad arrival, for each other identifier from when we first saw its value, and for your first arrival from that arrival. | Email team@inspectday.com to have an enquiry deleted from our records. An upload to Google Ads can’t be withdrawn. To keep an enquiry out of it, turn ad measurement off in Analytics choices at the bottom of any page, or send Global Privacy Control, before you send the form |
| Started sign-ups | Measure which ads bring people who start signing up | With ad measurement on, pressing Get started sends every held ad click identifier to InspectDay’s server on Netlify, with the time of the press and which Get started on the page you pressed. Non-Google identifiers include the time we first saw them. Where you allowed ad measurement, the press also carries that answer. We upload the started sign-ups to Google Ads to measure our ads. A cookie, inspectday_start, on inspectday.com marks that you have started, so later presses send nothing more. The click identifiers, the first-seen times for non-Google identifiers, the press time, which Get started you pressed and the answer are kept for 60 days. The cookie expires after 60 days. | Turn ad measurement off in Analytics choices at the bottom of any page, or send Global Privacy Control, before you press Get started |
| Demo bookings | Measure which ads bring people who book a demo | What you enter to book, such as your name and email, goes to our booking calendar at book.makerstudio.io; this website does not keep it. When the booking opens on /demo/, the site passes it every held ad click identifier, with the time we first saw each non-Google identifier, your ad measurement answer where there is one, and, with analytics on, your visitor identifier. When you book with a click identifier passed, InspectDay’s server on Netlify stores the booking’s id and time with those click identifiers, first-seen times and answer, and your email only as a SHA-256 hash, never your name, your email itself or the meeting times; records the booking in PostHog, under your visitor identifier where the booking carries it; and uploads the booking with the hashed email to Google Ads to measure our ads. A booking with no click identifier is not kept or recorded by this website. Nothing is stored in your browser for a booking. The booking’s id and time, its click identifiers, first-seen times, answer and hashed email are kept for 60 days. The PostHog record is kept under our PostHog retention settings. The booking calendar deletes your booking, with your name and email and those of any guests you add, 28 days after the call is cancelled or has taken place. The call’s event on our host’s Google Calendar keeps them until the host deletes it. To have them deleted sooner, ask at /contact/; deleting the event also cancels a call not yet held. | Before you book, turn ad measurement off in Analytics choices at the bottom of any page, or send Global Privacy Control, to keep click identifiers out of the booking, so this website keeps nothing of it, and turn analytics off to keep your visitor identifier out. Cancelling the call does not remove a booking already recorded, and an upload to Google Ads can’t be withdrawn |
| Analytics | Count page views, clicks on Get started and receipt-page visits, see which pages and ad campaigns bring visitors, and see which parts of a page are read: time on the page, how far down you scrolled, which sections came into view and where on the page you clicked | With analytics on: a visitor identifier and where you first and last came from (campaign details such as utm_source, the referring site and the landing page, with ad click identifiers included only when ad measurement is also on) in your browser storage and in cookies on inspectday.com that the InspectDay app reads when you sign up, to link this visit to your new account. Events are sent to PostHog in the US through inspectday.com. Click positions are page coordinates only, without what was clicked or anything you typed. Events also carry your browser’s user agent (browser, version and operating system) so automated traffic such as crawlers can be told apart from people. In the EEA, the UK, Switzerland and unknown countries, nothing is stored until you allow it; elsewhere analytics is on by default. Campaign details expire after 90 days. The visitor identifier stays until you turn analytics off or clear your browser storage. Events sent to PostHog are kept under our PostHog retention settings. | Use Analytics choices at the bottom of any page, or send Global Privacy Control. Turning analytics off deletes the identifier, campaign details and cookie from this browser |
| Anonymous counts | Count visits from people who have not turned analytics on | Nothing on your device and no identifier. Page views, clicks on Get started and receipt-page visits are sent to PostHog, which groups them with a daily-changing code calculated from your IP address and browser and does not keep the IP address. Kept under our PostHog retention settings; the daily code cannot be linked to you or across days. | These counts carry no identifier, so there is nothing to withdraw from your browser |
| Your privacy choices | Remember whether you allowed or declined analytics and ad measurement | Allowed or declined for each, in your browser storage on this site. If you decline both, this is the only thing stored. Until you change your choice or clear your browser storage. | Use Analytics choices at the bottom of any page |
| Requests to the web server | Deliver pages and protect the site | Our hosting provider, Netlify, receives network details such as your IP address, browser and the page you requested. Kept by Netlify under its own log retention. | Needed to load any page; separate from analytics |
Analytics and ad measurement
This website asks about two things, each on its own: analytics, to see which pages bring visitors and what they read, and ad measurement, to see which of our ads bring people who sign up or send an enquiry. How it asks depends on where you are:
- In the European Economic Area, the United Kingdom and Switzerland, and when your country is unknown, we ask first. Until you allow one, nothing is stored on your device for it.
- Everywhere else, both are on by default. You can turn either off at any time with Analytics choices at the bottom of every page.
- If your browser sends a Global Privacy Control signal, we treat it as turning both off, wherever you are.
With analytics on, the website stores a visitor identifier on your device. It also stores for 90 days where you first came from and where you last came from: the campaign details, the referring site and the page you landed on. With ad measurement on as well, these details include ad click identifiers. It reports page views, clicks on Get started and receipt-page visits to PostHog, our analytics provider in the US, through inspectday.com. It also reports how a page is read: time on the page, how far down you scrolled, which sections came into view, and where on the page you clicked, as coordinates only, without what was clicked or anything you typed. If you then sign up, the InspectDay app reads the identifier and campaign details from cookies on inspectday.com so we can see which visit led to the account.
With analytics off, we still count page views, clicks on Get started and receipt-page visits, but anonymously. Nothing is stored on your device and no identifier is sent. PostHog groups the counts using a code it calculates on its servers from your IP address and browser, which changes every day, and it does not keep your IP address. These counts cannot be linked to you or across days.
With ad measurement on, the website keeps ad click identifiers from your arrivals in your browser. They stay until you send an enquiry, and for at most 90 days, counted for Google Ads identifiers from your latest Google ad arrival and for each other identifier from when we first saw its value. Every held click identifier is included with an enquiry you send, each non-Google identifier with the time we first saw it. We upload genuine enquiries that carry a Google Ads click identifier to Google Ads, to count the enquiries our ads bring. The upload holds that identifier, the enquiry's time and any ad measurement answer it carried, and nothing else from your enquiry. An upload can't be withdrawn. All held click identifiers are carried on links to the InspectDay app, each non-Google identifier with the time we first saw it. With them, the website keeps in your browser where you first arrived: the page you landed on, with click identifiers removed, the site that referred you, by domain, where it was outside inspectday.com, and the campaign details. A later visit doesn't replace it. It is kept with the click identifiers, until you send an enquiry and for at most 90 days from that arrival. Links to the InspectDay app carry it, and an enquiry you send includes it. The first time you press Get started, every held click identifier goes to InspectDay's server on Netlify with the press time. Non-Google identifiers also carry the time we first saw them. We upload the started sign-ups to Google Ads to count the sign-ups our ads bring. A cookie, inspectday_start, marks that you have started, so later presses send nothing more. Where you allowed ad measurement, your enquiry, links to the InspectDay app and your press on Get started also carry that answer.
With ad measurement off, the website keeps no click identifier or first arrival for it, includes neither with an enquiry or on links to the InspectDay app, and records nothing when you press Get started.
Page addresses are reported without their query strings. Campaign parameters are the exception. Sites that referred you are reported by domain only. We do not record your session or anything you type, and no ad network's script or cookie runs on this website.
Withdrawing with Analytics choices deletes the identifier, campaign details and cookie from your browser and keeps analytics off on later visits. Turning ad measurement off deletes the click identifiers and first arrival kept for it and keeps ad measurement off on later visits.
The InspectDay apps
The InspectDay web and mobile apps store your account and organization details, and the inspections, findings, recommended actions, photos and reports your team creates.
Reports can be shared in two ways. Anyone with a direct report link can open that report. A report shared by email asks the recipient for a one-time passcode.
The mobile app keeps some inspection data on your device so you can keep working with a weak connection, and sends your changes when it reconnects.
Analytics and screen recordings in the apps
The InspectDay apps send usage events to PostHog, our analytics provider in the US, so we can see how the apps are used and find problems. Once you sign in, these events are linked to your account.
- The web app reports the pages you open and when you leave them, your clicks with the text of what you clicked, form submissions, clicks that do nothing, and errors. With them it sends your name, email address, role and organization.
- The mobile app reports events such as signing in, creating an inspection, previewing and sharing a report, and syncing your changes. With them it sends your role and organization.
Screen recordings help us find and fix problems:
- The web app records every page, including sign-in, sign-up and reports opened from a shared link. What you type into form fields is hidden.
- The iPhone and iPad app records only if you allow it. The app asks first, and you can change your choice at any time in the Settings app under InspectDay, Session recording.
- The Android app records whenever it is open.
Recordings show the screens as you saw them, so they can include client details, property addresses, findings, notes and photos. Recordings are stored with PostHog in the US.
Google Firebase receives crash reports from the mobile app so we can fix crashes. The mobile apps also send their usage events to Firebase.
Service providers
We use these providers to run InspectDay:
- Fly.io hosts the InspectDay apps and their database.
- Cloudflare hosts the web app, relays its requests to Fly.io, and serves the Android download.
- jsDelivr delivers the web app's interface files to your browser.
- Bunny.net stores photos and other media files.
- Stripe processes subscription payments. We do not store card details.
- Google and Apple provide sign-in, if you choose to use them.
- An email delivery provider sends sign-in codes and report emails.
- ElevenLabs receives the voice notes you record in the apps and turns them into text.
- Netlify hosts this website and stores contact-form enquiries.
- TypeSafe provides jev to judge contact-form submissions.
- Resend sends genuine enquiries by email to our team inbox.
- Discord receives a copy of genuine enquiries in our team's private channel.
- PostHog provides website and app analytics and app screen recordings, as described under Analytics and Analytics and screen recordings in the apps.
- Google Ads receives the enquiries and started sign-ups we upload, to measure our ads.
- Google Firebase receives crash reports from the mobile app, and usage events from the mobile apps.
Keeping and deleting data
We keep your account and inspection data while your account is open. When an account or organization is deleted, its records are removed from the app. Photos and other media files may stay in storage for a time after the records that used them are deleted, and backups can keep earlier copies until they are replaced. Billing records are kept as long as accounting and tax rules require.
Read how to close your account for the steps.
Your rights
You can ask us for a copy of your personal information, or ask us to correct or delete it, by emailing team@inspectday.com. We may need to confirm your identity first. If you are in the European Union or the United Kingdom, you also have rights under data protection law, including the right to object and the right to complain to your data protection authority.