← Back to Home

Privacy Policy

Last updated: November 16, 2026 · Versión en español

Beit Building Contractors LLC ("Beit," "we," "us," or "our") respects your privacy. This policy describes information processed through this website and through the forms in our advertisements on Facebook, Instagram, and TikTok, how we use and share it, and the limits of the retention controls we operate.

Information We Process

Information you choose to submit

Forms in our advertisements on Facebook, Instagram, and TikTok

Some of our advertisements open a short form inside the app, without visiting this website. If you send one, the company that runs the app (Meta for Facebook and Instagram, or TikTok) sends us what you entered in it: your name, phone number, and email address (the app may fill these in from your profile; you can change them before sending), and your answers to the form's questions. With it come the name of the form, the campaign and the advertisement, which app you used, the identifier the company gives your form, and the time you sent it. A connector service (currently Make.com) carries the form from Meta or TikTok to our system, where it is stored and handled exactly like a request sent from this website: Sandra or Johnny receives it, and if you gave an email address you receive the same short automatic receipt. Meta and TikTok keep their own copy under their own privacy policies. We do not send them anything about you or your request in return.

Technical and operational information

Our hosting and security systems process technical request data such as IP address, User-Agent, route, timing, and security events to deliver the site, rate-limit abuse, investigate failures, and protect the service. Our optional first-party event endpoint accepts only a controlled event name and, when present, a mobile or desktop surface value from an exact allowed website origin. Application code hashes the source IP before using it as a short-lived KV rate-limit bucket and drops the event if the limiter cannot confirm that it was applied. The application reconstructs the event log entry so raw IP addresses, contact values, free-text project messages, and arbitrary or nested payload values are not written to application event logs. Hosting platforms may keep their own request metadata under their account settings and policies.

How you found us

A link can say where it was posted. If the link that brought you here carries labels about itself, such as the name of an advertisement or a campaign, or if another website or app linked to us, the site notes those labels, that website's host name, or the name of the app you opened it in (for example Instagram or TikTok), in sessionStorage for the current browser tab (or, if your browser keeps no storage, in that page's own history entry, which also ends with the tab). If you choose to send a request, they travel with it and are kept with it, so we know which notice reached you. We do not keep or pass on the click identifiers that advertising networks attach to links (for example fbclid, gclid, or ttclid): the page takes them, and the labels, out of its address as soon as it has read them, so they do not travel with your request or with a link you share. Our hosting provider may still record the address as it was first opened, as it records every page request. No advertising network's code runs on this site, and we report nothing back to one. If your browser sends a Do Not Track or Global Privacy Control signal, the site does not note or send these labels at all, and still cleans the address.

Tab-scoped form draft

While you edit a form, the site may keep a minimized rescue draft in sessionStorage for the current browser tab (on the short request page, if your browser keeps no storage, in that page's own history entry instead). On the short request page this is only which answers you tapped (for example "roof" or "as soon as possible"), so that reloading the page does not undo them; while a request could not yet be confirmed, a random reference for it, so that sending it again cannot deliver it twice; and, after you send, the time you sent, so that going back shows your confirmation instead of an empty form. Never what you typed. It is not a background submission queue. The site clears the tapped answers and the random reference after a confirmed submission or reset (the reference also as soon as you change anything), keeps the time you sent for 30 minutes and removes it when it next reads an older one, and rejects and removes any entry older than two hours when it is read. Closing the tab normally removes this storage, although browser crash-recovery or device behavior can affect when data is physically deleted. Older long-lived browser keys are removed and are not restored.

How We Use Information

Durable Submission and Failure Drafts

The website confirms a request only after our first-party KV store acknowledges both the request record and its time index. If durable storage is unavailable or not confirmed, the form asks you to retry and may open a prefilled draft in your mail application. Opening a draft does not send it. If you save or send that draft, your device and mail provider process it under their own settings and policies.

How We Share Information

We do not sell or rent personal information, use advertising trackers, or provide information to data brokers. We use service providers and recipients only for the purposes described here, including:

Optional visitor-facing booking, mapping, weather, or informational integrations may connect to an external provider when enabled or invoked. Those providers have their own privacy terms. The absence of advertising trackers does not mean the website uses no external services.

Help-First and Public Opportunities

Our private Help-First review view uses one privacy-minimized snapshot. Snapshot version 2 contains controlled request IDs, workflow and safety codes, service-area categories, flags, timestamps, and aggregate impact/capacity counts. It does not accept a person's name, phone, email, exact street address, contact permission, private request or hardship narrative, internal note, or contract value.

The snapshot may also contain official public procurement opportunities. Those records must include an official HTTPS notice and provenance, controlled project scopes and requirement indicators, capability-fit reasons, and a manual review action. The hosted view does not automatically contact anyone, rank a person by value, resolve contact information, or submit a bid. Public-record or procurement research is not treated as permission to contact a person.

Retention

These application limits do not automatically delete copies in business mailboxes, transactional email systems, Slack, Discord, HubSpot, Meta, TikTok, the connector service, hosting or security logs, backups, a visitor's mail provider, or records we must preserve for legal reasons. Those copies follow the relevant provider account settings and applicable requirements. We are responsible for configuring and deleting provider copies where we control them; we do not promise that the application TTL can delete data held independently by another provider.

Security

We use server-side validation, request limits, origin checks, exact storage acknowledgements, restricted private sessions, data minimization, security headers, and retention controls. No system is perfectly secure. Please do not place passwords, government identifiers, financial account data, medical information, or unrelated private details in the project-message field.

Your Choices

You may ask us to correct or delete contact information you submitted, or to stop non-required follow-up, by emailing beitbuilding@gmail.com or calling (407) 942-6459. We will evaluate the request under applicable law and may need to keep limited records for contracts, safety, legal obligations, dispute resolution, fraud prevention, or permanent DNC suppression.

Children

This site is not directed to children under 13, and we do not knowingly request personal information from them.

Policy and Legal Review

This disclosure should be reviewed against our actual provider configuration and operating practices whenever they change. Technical safeguards are not a legal-compliance certification. We seek qualified counsel for applicable privacy, retention, outreach, and public-record requirements.

Updates

We may update this policy when our services, providers, or legal obligations change. The current version and update date will be posted here.

Contact

Beit Building Contractors LLC
Orlando, FL
(407) 942-6459 | beitbuilding@gmail.com