Privacy Policy

Our analytics and error monitoring

Internet Crafters records page paths, timestamps, page views, and clicks in our customer portal. Normal browser mode uses a random ID in session storage to connect activity within that browser session. It can include campaign labels from links, such as UTM source and campaign, but strips raw advertising click identifiers, URL queries, and fragments from page paths.

We count call-button clicks, email-link clicks, directions, submit-button clicks, and form attempts separately. A successful contact-form response, including a confirmed embedded-form callback, records a completed-form event without the answers. These actions don't prove a call connected, an email was sent, or how many different people contacted us.

Error monitoring collects error type, code location, software release, and coarse browser or operating-system information. Our collector doesn't capture form contents, error-message text, or session replay. Matching failures become grouped issues for staff review, not automatic support tickets.

Server-side crawler observation records request paths, times, response status, and user-agent information. The portal stores a keyed hash of the crawler IP address instead of the raw address. Crawler counts describe automated requests, not visits by people.

Privacy signals and reduced-data counts

When your browser sends Do Not Track or Global Privacy Control, our first-party collector switches to reduced-data counting. It sends only the page path, event type, minute-rounded time, and a separate random ID for each event to prevent duplicate processing. It doesn't use session storage, link events to a visitor, or include campaign labels, click destinations, or browser error details.

These counting requests omit cookies, credentials, and the referrer header. Our collector doesn't forward browser IP addresses or user agents into the portal. Hosting providers still receive network information needed to serve requests and can keep their own operational logs, so reduced-data counting isn't a promise that no personal data is processed anywhere.

We don't use these reduced-data counts for visitor profiles or cross-site advertising. Browser blockers can prevent collection, and we don't bypass them. For other privacy requests, use the contact details below.

Other analytics providers

This website also uses Google Analytics and, when configured, Statsig for usage analysis. Statsig can record session replay and interaction data, and these tools can use their own browser identifiers or storage. Those features are separate from our first-party collector.

We don't initialize Google Analytics or Statsig when Do Not Track or Global Privacy Control is enabled. Changing browser settings doesn't erase information already collected. Customer websites can use different tools and should describe them in their own privacy notices.

Advertising cookie and your choice

Google Ads is configured on this site, and it can set an advertising cookie. That cookie is off by default. It is set only after you agree to it, and agreeing is the only thing that turns it on.

What it does: it lets Google connect your visit to an advertising click, so we can see which ads bring people here, and it adds you to the audience we can show ads to on other sites later. Without it, we still count conversions, but Google estimates the connection to a click rather than observing it.

We ask once, in a banner at the bottom of the page. Declining changes nothing else about the site. You can change your answer at any time through the "Cookie choices" link in the footer of every page, and withdrawing takes effect immediately.

When your browser sends Do Not Track or Global Privacy Control, the advertising cookie stays off and we do not ask. A browser-level opt-out is an answer, and we treat it as one.

The advertising click that brought you here

When you arrive from one of our ads, the link carries an identifier that says which ad you clicked. We keep that identifier in your browser for 90 days, and send it with your request if you fill in the project form.

What it is for: telling which ads bring work in. Without it, a sale that started with an ad looks the same to us as one that did not, and we would be guessing about where to spend.

Where it goes: our own systems and, when we report a completed sale, Google Ads. It is stored in your browser, not in a cookie, and no other site can read it. We do not use it to show you ads, build a profile, or follow you anywhere else.

This is separate from the counting described above, which still strips these identifiers and still does not keep them. When your browser sends Do Not Track or Global Privacy Control, we do not keep the identifier at all.