Website information / Updated 22 October 2026
Privacy policy
Information connected with browsing, a locally prepared journey brief and any later communication you choose to send.
1. The operator and a privacy enquiry
The company identified for this publication is TRANSPONTEIO TRANSPORTES E SERVICOS S.A., CNPJ 22.253.389/0001-10. Its registered address is RUA LENINE LUEDY, 48, BELVEDERE, PEDRA AZUL - MG, 39970-000, Brazil. A question about personal information can be prepared through the Contact page using the published enquiry address. Identify the interaction and the record or category involved, so the issue can be directed appropriately. A browser provider or email service may have a separate role and separate privacy conditions; this notice does not represent those providers as departments of the transport company.
2. Keep the journey brief proportionate
The initial form requests a name, reply email, service category and free-text message, with an optional company field. A useful transport brief contains the route, date and approximate passenger number. It does not require a complete passenger manifest. Avoid including passport numbers, identification copies, banking details or medical histories in a general enquiry. The form does not offer an attachment field or request a telephone number. Later information requirements should be explained in relation to the actual service.
3. Previewing a draft inside the browser
Typing into the fields does not submit a transport request to a server-side inbox. The local script validates the fields and builds an on-page preview. You can edit the form and prepare another preview before deciding what to do with it. The authored code does not retain those fields in browser storage. Someone who can see or operate your device may still be able to read the visible form, so use a suitable device for the sensitivity of the message.
4. Choosing to use your email application
The optional email link encodes the prepared message and asks your own application to open a draft. That application and its provider may process or save the text according to your account settings. Sending is a separate choice there; the website does not confirm delivery or receipt. Once a message reaches a recipient, that recipient’s handling is distinct from local preparation. Closing the website cannot recall a sent email or erase a draft already saved by an independent email service.
5. Requests needed to display the pages
Your device requests page files, photographs, scripts and fonts from the hosting and delivery infrastructure. Those requests can involve an IP address, browser characteristics, requested addresses and timestamps. Such information can be used to deliver content, investigate failures and protect the service. It is different from the route details typed into a form that has not been sent. The technical information visible to a provider depends on the request and its actual configuration.
6. Storage and technical service features
The authored pages do not create a marketing cookie, signed-in session or localStorage record of your journey enquiry. Browser caching can keep downloaded website resources. Cloudflare and the hosting provider may use security controls, request logs, email-address protection or performance diagnostics at the infrastructure layer. Inspect browser settings and applicable provider controls for those functions. Clearing cached resources does not remove a message from an email account, and stopping an optional feature does not eliminate the basic network requests needed to load a page.
7. Why information can be used
A message you choose to send can be relevant to answering a transport question, preparing a proposal or discussing service requirements. A confirmed agreement may require further records to organise performance, handle payments or meet legal duties. Technical logs support service delivery and security. The lawful basis depends on the particular processing and applicable rules, including requested pre-contract steps, contractual performance, legal duties or permitted legitimate interests. Any separate consent-based activity should explain the purpose and the choice at the point it is proposed.
8. Organisers and other passengers
When acting for a group, describe the service requirement without exposing everyone’s personal details. The authority to arrange a journey is not necessarily permission to disclose unrelated personal information. Where a confirmed service needs a passenger list or accessibility information, establish the purpose, recipient and suitable channel first. For children, an adult organiser should involve the appropriate parent or guardian and avoid placing identifying details in the general form. A concern about a child’s information can be raised through Contact.
9. Recipients and service partners
Personnel dealing with a journey enquiry may need the information relevant to that request. Communications providers, hosting or administration services may also have a role under their actual arrangements. A confirmed trip can involve additional parties identified for that service, and legal obligations can require disclosure to a competent authority. Do not infer a recipient list from the presence of a bus photograph. Ask about the recipients associated with your own interaction before sending material whose handling is especially important to you.
10. Locations of technical processing
A registered Brazilian company address does not mean every internet request or email record is processed at that address. Delivery networks and communications providers may operate systems in different locations. The actual provider arrangements and applicable transfer rules determine any required safeguards. If the processing location affects your decision to share further information, ask about the relevant record and service beforehand. Following an external link can create a separate interaction with its destination, governed by that provider’s practices.
11. How retention is considered
An unanswered general question, an active quotation and a confirmed transport agreement can have different recordkeeping needs. Relevant factors include whether the enquiry remains active, contractual documentation, tax or other legal requirements, and the need to address complaints or security incidents. No single fixed retention period is asserted here for all categories. Ask for the period or criteria applicable to the record in your interaction. A legitimate deletion request may need to be considered alongside lawful retention obligations.
12. Choices and requests about a record
Depending on the applicable law, you may have rights to access, correction, deletion, restriction, objection or other appropriate measures. Explain the record and requested outcome without supplying unnecessary identity documents. Proportionate verification may be needed to avoid revealing information to the wrong person. The law determines applicable response periods and exceptions. A request made through a local draft has not reached the business until it is actually delivered through the chosen communication channel.
13. Safe communication and suspected problems
Use an appropriate channel for confidential operational or passenger information. Never place banking passwords, authentication codes or full payment credentials in the general message. If information appears misdirected, identify the interaction and nature of the problem without circulating the sensitive contents again unnecessarily. No browser, network or email service is risk-free. Security precautions and provider controls should be considered in relation to the actual information, rather than assuming that a website form is a protected passenger-record system.
14. Updates and continuing concerns
This notice reflects the website functions described on the publication date. Changes to a feature or the handling of a confirmed service can require additional information at the relevant interaction. An updated page does not by itself authorise a materially different use of existing information where notice, a lawful basis or consent is required. Keep the version relevant to your interaction if useful. A concern can also be raised with a competent supervisory authority or other available process under the applicable rules.