Privacy policy
Last updated: October 22, 2026
How this project-enquiry website handles page requests, locally prepared drafts and information you decide to send.
1. Start with the relevant organisation
This English-language website is published by ADS CONSTRUCOES E ELTRICA LTDA. Its registered address and CNPJ appear in About. The commercial pages describe the separate Lance Marketing Digital source agency. This notice addresses the website edition and its enquiry route; it does not assert that the publisher controls a client account, marketing database or message already held by Lance. Identify the particular interaction and organisation when asking who holds a record or can respond to a privacy request.
2. A project brief begins with a few fields
The shared request page asks for a name, reply email, message and optional contact or area details displayed beside the fields. A service selected from a page may appear as the topic of the request. Explain the business question at an introductory level, such as a website objective, intended audience or an automation requirement. The site has no file uploader, client login, account-authorisation screen or checkout. An ordinary enquiry is not permission to inspect a customer database or an advertising account.
3. Prepare, inspect and decide whether to send
The contact mechanism runs in the page to compose an email draft. The action does not post the field contents to a website form server. You can inspect the recipient and message in your own email application before deciding to send. A draft appearing on screen is evidence of local preparation only; it is not proof of mailbox delivery, a support ticket or acceptance of a project. Your chosen email provider may retain drafts and sent messages under its own service arrangements.
4. Keep account access outside an initial enquiry
An advertising password, API token, customer list, CRM export or payment credential does not belong in the project message. A preliminary explanation normally needs none of those materials. If a later project needs access or data, establish the supplier, purpose, permissions, necessary scope and appropriate transfer method first. Do not include information about your customers merely because you are discussing a marketing service. If you are acting for a business, consider whether you are authorised to disclose the information you intend to send.
5. Infrastructure sees resource requests
Cloudflare delivers and protects the public website; its origin uses cPanel hosting. A browser requests HTML, images, styles and locally hosted fonts from that infrastructure. Those requests can include an IP address, browser characteristics, a resource address and timing, and providers may keep operational or security records. This technical exchange occurs when loading the site and is separate from entering text in the form. It does not show that a project enquiry was sent or that the publisher has access to an advertising profile.
6. Service descriptions are not installed trackers
Pages discuss GA4, Meta pixel, Google Ads, CRM tools and AI systems as possible project services. Mentioning a product in the copy does not activate an account connection or authorise its use with your data. The published contact workflow does not subscribe you to promotional messages or export your draft into a CRM. Browser and infrastructure storage should be assessed separately from these service descriptions. Review browser controls and the policies of any external destination you choose to open.
7. Links and named source profiles
The source agency’s review, certification, professional-network or map references may lead to other providers. Opening such a destination can disclose request information to that provider, which handles the visit under its own policies. A named founder or client review is content attribution, not a transfer of your contact details to that individual. Before supplying information on another website, check its address and responsible organisation. Locally served fonts and images do not themselves require a visit to the source agency’s website.
8. A sent message can become a separate record
If you choose to send an enquiry and a recipient receives it, that recipient may use the message to understand and respond to the question. Subsequent project administration can involve different information and purposes, which should be explained for the actual engagement. The relevant legal basis depends on the activity and applicable law, including requested pre-contract steps, agreement performance or legal duties where appropriate. Browsing this site does not imply consent to unrelated remarketing or grant a blanket right to reuse your message in public material.
9. Retention, recipients and international processing
A browser draft, your email provider’s copy, infrastructure logs and a recipient’s correspondence are different records. Their locations, access arrangements and retention criteria depend on the services and actual interaction. An active project, a legal recordkeeping duty or a dispute may affect how long a relevant record is kept. This page does not invent an unconfirmed deletion period or country of storage. Ask about the specific record and responsible provider if retention or transfer safeguards matter before you disclose additional material.
10. Requests, security concerns and revisions
Depending on applicable law, a person may seek access, correction, deletion, processing information, objection or withdrawal of consent where consent applies. Explain which enquiry or record is concerned and the result you are requesting, without sending identity documents unsolicited. Proportionate verification and lawful exceptions may apply. No email or network service is risk-free; report a suspected misdirection to the relevant recipient without circulating confidential content again. The notice date identifies this edition, while available rights and regulatory complaint routes remain unaffected.