Privacy policy
Last updated: October 17, 2026
Effective 17 October 2026. A wholesale parts question may be sent by a buyer, an employee or someone enquiring for another business. This policy separates the contact information involved in that conversation from the technical observations made when a browser visits christianobornemanusa.online. It also explains how to ask about records that are actually held.
1. The business named in a data request
CHRISTIANO BORNEMANN LTDA, CNPJ 00.264.922/0001-06, is the Brazilian business presented as Christiano Bornemann on this website. Its registered address is RUA IMACULADA CONCEICAO, 1776, PRADO VELHO, CURITIBA - PR, 80215-182, Brazil. Its registered activity is wholesale trade in new parts and accessories for motor vehicles. Use this identity when directing a question about information associated with the business. The English presentation is for reading these pages in English; it does not identify a separate United States operator or a foreign branch.
2. A visit does not require a trade account
The website does not register buyers, verify trade eligibility, issue customer numbers or retain an online purchase history. You may read the business information and enquiry guide without supplying contact details. There is no checkout, card entry or file-upload function. An explanation about part references and quantities is not a request to provide customer lists, invoices or confidential procurement records. A browser visit nevertheless involves technical connections, including the Cloudflare services described later in this policy.
3. Choose the information appropriate to the question
The forms ask for a name, an email address and a message, with an optional phone number. The separate request page also offers a city or area field and may display a part reference passed through a request link. For an initial discussion, a component reference, general vehicle application, quantity and question are usually sufficient. A quantity requirement does not require you to disclose who your own customer is or provide their registration documents. If you correspond for an organization, use contact details you are entitled to share.
4. The point at which a draft becomes correspondence
Entering the fields does not deposit them in a website enquiry database. The form composes a mailto request on the device and asks the configured email application to prepare a message to [email protected]. It has no sending backend. You control the next step: check the destination, edit the proposed contents and decide whether to send. Opening the application is not an acknowledgement by the business, and an on-page draft notice cannot establish receipt.
Your email software can keep or synchronize a draft according to its settings, even before it is sent. Sending brings the relevant mail providers into the process. This website setup has not provisioned the displayed mailbox or tested delivery to it. Do not assume that an unacknowledged message has arrived. For correspondence that needs an independent delivery record, address a written request to the registered business instead. Removing an unsent draft is handled by your mail software, not by this page.
5. Separate product information from personal records
Part numbers and unit quantities do not necessarily identify a person on their own, but a message may link them to a named employee, buyer or vehicle owner. Keep the initial description focused on the commercial question. Avoid passwords, full payment credentials, identity scans, private vehicle documents and information about unrelated individuals. The form cannot receive attachments. If supporting records become necessary during a later conversation, establish their purpose and an appropriate means of providing them before disclosing them.
6. Cloudflare visits, performance and network diagnostics
The hosting and delivery infrastructure receives technical requests when the site is opened. Cloudflare also adds an Insights beacon to collect information about visits and page-loading performance. Network Error Logging, signalled through NEL and Report-To headers, enables supporting browsers to report network failures for diagnosis. These are delivery and diagnostic mechanisms, not the form submission route. Their operation is separate from the name, reply address and message you type into a form.
Connection requests and diagnostic reporting can involve information about the browser, requested resources and network operation. This policy does not claim an exhaustive field list, a particular storage country or a fixed retention period for those services. Keep private information out of URLs: a part description in a query string can become part of a requested page address. Visit measurement is not evidence that a trade enquiry was received, read or accepted.
7. Local scripts, browser controls and other applications
The authored enquiry scripts do not write form contents to cookies, local storage or session storage. This does not mean that a visit produces no technical records: the infrastructure described above operates separately. There is no page control that turns off Cloudflare delivery telemetry. Your browser provides site-data and security controls, whose effect depends on its capabilities and settings. Completing an enquiry does not enroll you in a promotional mailing list.
The site supplies its own fonts and decorative resources and does not embed a map, video player, social feed or customer-login widget. Cloudflare can add its delivery resource to the public response. Your chosen email application is another service with its own draft, permission and synchronization controls. This policy does not change the terms or settings of that application, and closing this website does not necessarily remove a draft already opened there.
8. Purposes depend on the record that exists
If a message reaches the business, the relevant purpose may be to understand an item requirement, clarify quantity or application details and answer the sender. Technical records serve website operation, performance measurement, fault diagnosis and protection against misuse. The legal basis must fit the processing that occurs, rather than being inferred from a generic acceptance of this notice. Depending on the circumstances, requested pre-contractual steps, a legal obligation or a justified operational interest may be relevant. This explanation does not authorize unrelated reuse of a buyer’s correspondence.
9. Service recipients and the lifespan of records
Hosting and Cloudflare participate in delivering these pages. Mail services participate in the draft, transport or receipt steps they actually handle. Such infrastructure may operate across national borders; no exclusively Brazilian storage location is promised here. There is no integration in the form that forwards its entries to an advertising platform. Questions about recipients, international processing and retention should identify the interaction concerned.
A text field still open on a device, a saved email draft, a received letter and a technical log can have different lifespans. The website has no customer database to erase, and no universal retention period is specified for those separate records. You may ask whether information is retained, for what reason and under which criteria. Clearing browser history does not delete a provider’s logs, while deleting a sent email does not retrieve a copy already delivered elsewhere.
10. Rights relating to personal information
When the LGPD applies, you may ask for confirmation of processing, access, correction and information about sharing. Other rights can include anonymization, restriction or deletion of unnecessary or unlawfully processed information, portability under applicable rules, and withdrawal of consent where consent is the basis. Legal exceptions may affect a particular request. These rights concern personal information actually processed, rather than a presumed record created by an unsent draft. The ANPD provides official guidance and a route for raising unresolved data-protection concerns.
11. How to identify and document a privacy concern
Write to CHRISTIANO BORNEMANN LTDA at RUA IMACULADA CONCEICAO, 1776, PRADO VELHO, CURITIBA - PR, 80215-182, Brazil, marking the correspondence “Privacy”. Explain the approximate date, whether the interaction was a website visit or correspondence, the information concerned and the action sought. Include a suitable reply route, but only the identifying details needed to locate the matter. If further identity evidence is necessary, confirm a suitable channel first. Keep your own copy and relevant delivery record; the untested email destination should not be your only evidence for a formal request.
12. Security precautions and future changes
A parent or guardian should manage an enquiry if a child would otherwise disclose personal information. Use an account and device you control, and check a proposed email before sending. No website or email channel can guarantee complete security. If you accidentally share another person’s information, describe the incident through the contact route without unnecessarily repeating the sensitive content. The date identifies this version. New collection features would require a description of their actual behavior; a later wording change does not itself permit an unrelated use of earlier correspondence.