Privacy
How I use your contact information.
If you contact Hunter Web Apps, I use the details to understand what you need. Then I decide whether I can help and reply.
I don’t use your details for marketing.
Last updated: July 21, 2026
What you provide
What the form asks for.
The form requires your name and email. You must also describe what you are building or fixing and why now.
It also requires your role in the decision so I know how to reply. Sending the form asks me to review your message and respond.
Optional fields cover your organization, preferred working arrangement, timing, budget or hourly rate, contract details, how you found me, and any other context you want to add.
The form may record the page that sent you to Contact, the broad source, referring domain, campaign labels, and case studies opened during this browser session.
The case-study history contains case labels only.
The site does not copy your form-entered name, email, organization, message, or other free text into these tracking fields.
Do not put personal or project details in campaign URLs.
Each draft gets a random token so a retry does not create a duplicate. The token contains no name, email, or message text.
It never appears in site analytics or a URL. The form clears it after the server confirms acceptance or when you send changed text as a new message.
Do not send passwords, access keys, credentials, production data, protected client information, or other sensitive material.
How I use it
I use your message to reply and keep a business record if we work together.
Review and reply
I read your message and decide whether I can help. I may ask for more detail, suggest a call when useful, or say it isn’t a fit.
Keep the form safe
Google reCAPTCHA Enterprise checks a one-time submission token and related technical signals for abuse risk.
Hunter Web Services uses the requesting network address to enforce a short request limit.
What site analytics excludes
Site measurement does not include contact details, organization names, free text, exact budget choices, retry tokens, or message identifiers.
Site measurement
On the production site, Google Analytics and Microsoft Clarity are on by default. You can turn them off in this browser.
Cloudflare Web Analytics
Cloudflare Web Analytics is always on. It shows me aggregate page traffic and browser performance.
Cloudflare Web Analytics is designed to measure this without cookies or cross-site tracking.
Cloudflare processes the limited technical request and performance data needed for those aggregate reports. It does not receive your contact-form answers.
Google Analytics
On the production site, Google Analytics loads by default through a same-origin Cloudflare gateway unless this browser has opted out.
It may set first-party cookies named _ga and _ga_* to distinguish browser visits.
While Google Analytics is on, the site grants consent signals for analytics storage, advertising storage, advertising user data, and advertising personalization.
Google Signals and advertising personalization are also on so I can understand acquisition and audience performance. The intended retention period for event-level data is 14 months.
Once per day, the production property exports sanitized event data and pseudonymous active-user data to a Hunter Web Apps Google Cloud BigQuery dataset for longer-term analysis.
Streaming export and mobile-app advertising identifiers are off. The export also excludes form answers and direct identifiers.
What Google Analytics records
The site sends one sanitized page view. It also reports a few actions on the site.
Those events cover selecting a call to action or proof item, starting or attempting the inquiry form, a broad validation or delivery result, and confirmed inquiry acceptance.
They may include the page category, link placement, broad inquiry intent, proof or service label, source family, and campaign parameters such as UTM source, medium, campaign, and content.
URLs sent to Google Analytics do not include query strings or fragments. The site reduces each referrer to a valid external host.
The site sends only event fields from a fixed list. It sends no names, email addresses, organizations, form answers, free text, retry tokens, message identifiers, or error text.
Microsoft Clarity heatmaps and session replay
Microsoft Clarity loads by default on the production site. It creates aggregate click and scroll heatmaps, usability patterns, and reconstructed session replays.
It records clicks, scrolling, pointer movement, page rendering, device and browser details, sanitized page locations, and referring information.
Before Clarity loads, the site removes the URL fragment and every query field except validated campaign, advertising-click, and internal-source labels. Rejected values never reach Clarity.
Clarity is connected to the production Google Analytics property so I can compare acquisition reporting with observed site behavior.
Before Clarity uploads replay content, the site masks the entire inquiry form, including its error and delivery-status regions.
Clarity does not receive the name, email, organization, selections, free text, hidden attribution fields, security token, or retry identifier in the form.
The site does not send Clarity a custom user ID or use contact information to identify a visitor.
When site analytics is on, Clarity may use first-party cookies such as _clck and _clsk.
It may also use Microsoft cookies and similar technologies to connect page views and provide analytics and advertising measurement.
Google Consent Mode sends the same analytics and advertising-storage choice to Clarity. Microsoft processes this data as described in the Microsoft Privacy Statement.
Clarity playback data is ordinarily retained for 30 days.
Aggregate click and heatmap data, and sessions that are labeled or favorited, may be retained for up to 9 months.
Your analytics choice
The site does not open an automatic analytics banner.
At any time, select Analytics choices in the footer, then choose Opt out to stop Google Analytics measurement and Microsoft Clarity in this browser.
The site stores your choice in this browser’s local storage.
Opting out updates Google Consent Mode to denied and deletes this site’s visible _ga, _ga_*, _clck, and _clsk cookies.
If either service was active, the page reloads after you opt out. Later pages do not configure or send Google Analytics measurement and do not load Clarity.
Cloudflare may still insert the inert same-origin gateway script. You can turn measurement back on through the same control or clear site data in your browser.
This choice does not disable Cloudflare’s always-on, cookie-free aggregate traffic and performance measurement.
Processing and retention
Who handles your message, and how long do I keep it?
Direct email
Google Workspace routes email sent to Hunter Web Apps. I use that mailbox to read and answer your message. Your email service also processes it.
How long I keep direct email
I keep direct email only as long as needed to review and answer your message, unless the conversation becomes an active business or legal record.
You may request deletion where applicable.
Web form
The site uses Google reCAPTCHA Enterprise for abuse scoring.
When you submit the form, its details go to the Hunter Web Services API hosted on Microsoft Azure App Service.
The API checks the request. Azure Service Bus accepts the delivery job only after those checks pass.
A worker uses Twilio SendGrid to send the confirmation to you and BCC the Hunter Web Apps Google Workspace mailbox.
The form does not send the inquiry to a CRM.
How long form inquiries are kept
The delivered inquiry and reply thread follow the same mailbox retention described for direct email.
Temporary queue copies are used for delivery and are not the long-term inquiry record.
Limited operational logs may retain request status, timing, a retry token, and abuse-check results. Site measurement does not record the inquiry message.
Confirmation state
After the backend accepts an inquiry, this browser stores a same-tab acceptance marker for up to ten minutes so the next page can report success.
The marker holds the acceptance time and limited labels for inquiry intent and source. It does not hold your name, email, retry token, or inquiry text.
The browser removes the marker when the next page reads it.
Your choices
You do not have to use the form.
You may use a recruiter, marketplace, delivery partner, referral thread, or direct email instead. If a conversation is already underway, keep using that thread.
Your email service and the Hunter Web Apps mailbox service both process email.
You may ask what contact information Hunter Web Apps holds about you, or request correction or deletion where applicable, through the contact form.