What the forms collect
Project inquiries collect the homeowner's name and email, project city and ZIP code, the problem they are trying to solve, project stage, timing, investment readiness, and an optional project note.
An optional question asks how the homeowner found NABS. That answer is included in the inquiry email to help NABS understand which sources lead to relevant project conversations. It does not track browsing or use an analytics service.
The paid project-review request collects a name, email, city, project description, proposed construction budget, timing, and confirmation of the review price and authority to discuss the property. A source label from the review link may identify the channel, such as Instagram or Facebook. Website feedback collects a name and email, the type of website request, an optional NABS page address, and the message. These forms do not request a phone number, street address, file upload, account password, payment information, or medical information.
How NABS uses a submission
NABS uses submitted information to evaluate and reply to an inquiry, determine whether the project or request appears to fit, ask useful follow-up questions, and maintain ordinary business correspondence.
General project inquiries and website feedback are routed to the private NABS business inbox without a website database copy. Paid project-review requests are also saved in a private Cloudflare-hosted database, with the price acknowledgment, offer version, and email delivery status. This lets NABS recover a request if a notification is delayed. The review requester receives a confirmation email. The public website does not expose saved requests or the business inbox address.
Spam prevention and email delivery
Cloudflare Turnstile checks whether a submission appears to come from a person and processes technical browser and request signals for that purpose. Those signals can include the project-review page address and a validated Meta click identifier while it remains on that page. Its secret key stays on the server.
The website server temporarily uses the request IP address to limit repeated submission attempts. Project-review spam prevention stores a keyed hash of the IP address with a short-lived counter; it does not store the raw IP address in the request database. Hosting and security systems may also process technical request information, such as an IP address and browser identifier, to deliver and protect the website. NABS does not add raw request IP addresses or browser identifiers to inquiry emails or project-review records.
Resend delivers the approved message to NABS. Resend states that email content, metadata, delivery events, logs, and metrics are retained for 30 days on its Free, Pro, and Scale plans; Enterprise retention can differ. NABS does not use these messages for marketing lists.
Learn more from the providers: Cloudflare privacy and Resend data retention.
Retention and requests
NABS may keep inquiry emails and saved project-review requests while evaluating the request, corresponding with the homeowner, maintaining project records, or meeting legitimate business and legal obligations. Messages may be removed when they are no longer reasonably needed.
A person may ask NABS to review, correct, or delete information they submitted. Some records may need to be retained when a legal or business obligation applies. Use the website request path without publishing a personal phone number or email address.
Open the website request pathAnalytics and cookies
The project-review form offers an optional choice to let NABS count a successfully saved inquiry as a Lead in the existing NABS Meta Pixel. NABS code does not call a PageView event, requests that Meta's automatic configuration be disabled before Pixel initialization, and does not load Meta's measurement script for that inquiry unless the person explicitly selects the allow option.
NABS adds only the standard Lead event name and a one-way event identifier created by the NABS server. NABS does not add the person's name, email, city, budget, timing, source label, inquiry reference, project description, or other form content as event parameters. Duplicate submissions and requests labeled as owner tests are not eligible for a Lead event.
No selection, selecting “Do not send,” or withdrawing an allow choice before the event is sent means no Meta Lead event. When the allow choice is active and a new request is confirmed as saved by the server, Meta may receive ordinary technical information associated with its Pixel, such as the current and referring page, IP address, browser details, a Meta click identifier from an ad link, and information from cookies that Meta reads or sets. Before the form renders, NABS removes unrecognized query values, tracking campaign labels, duplicates, and malformed click identifiers. One bounded Meta click identifier may remain in the page address and the page's navigation data while the measurement choice and a new saved request are unresolved, so the standard browser Pixel can use it for ad attribution after permission is granted. It is removed after denial, withdrawal, ineligible or failed measurement, or the Lead dispatch attempt. NABS duplicate-prevention code stores an opaque event marker in the browser; it does not store contact or project form content for measurement.
The choice can be changed until the request is submitted and, while optional measurement is still loading, withdrawn from the success message. An event already transmitted cannot be recalled. Learn more in Meta's privacy policy.
Updates to this notice
NABS may update this notice when its forms, providers, measurement tools, or legal obligations change. The reviewed date above identifies the latest published revision.