Updated on 15 September 2026
Who is responsible
Tá Chegando Bus is the service available at tachegandobus.com.br and in the Android and iOS apps of the same name. For privacy matters, use contato@tachegandobus.com.br or +55 11 99015-2524, also listed on the contact page.
Data you provide
If you create an account, we may process identification and profile data used at sign-in — such as name, email and photo, depending on the authentication method.
Comments, ratings, mobility surveys and messages sent through contact channels are also provided by you. Do not publish other people’s data without permission.
Technical and browsing data
The site and app may store technical information needed to operate, such as language, theme, last search, favorites on the device, browser or system type and, in some cases, session identifiers.
In the app, location is accessed only after your permission, for maps and nearby features. Camera and photos are accessed when you choose an image. You can revoke these permissions in device settings.
Cookies and similar technologies
The website may use cookies and local browser storage to remember language and theme. Google Analytics (G-HH6RJM5BJJ) measures visits after you accept analytics. In the native app, Firebase Analytics measures first opens, sessions and usage according to the statistics sharing preference in settings. Microsoft Application Insights monitors production application errors, performance and requests without identification cookies. Google AdSense and its partners may also store advertising cookies in your browser to serve and measure ads.
Details on cookie types, purposes and preference management are in the Cookie Policy.
Purpose
We process data to authenticate your account, remember preferences, show lines and maps, enable favorites, alerts, comments and ratings, understand aggregated usage, and answer support requests.
We do not sell user lists. We do not use data to create misleading content or to encourage clicks on advertising.
Third-party services actually used
Authentication may use Firebase Authentication (Google). Maps and places features use Google Maps. Google Analytics (G-HH6RJM5BJJ) measures visits after you accept analytics. In the native app, Firebase Analytics measures first opens, sessions and usage according to the statistics sharing preference in settings. Microsoft Application Insights monitors production application errors, performance and requests without identification cookies.
Mobile apps may show ads with Google AdMob, subject to platform consent. The website loads Google AdSense (publisher pub-6129391261165224), the same publisher declared in the ads.txt file. Google and its partners may use advertising cookies and identifiers to serve and measure ads, as described in the Google Privacy Policy and in the settings at myadcenter.google.com.
App stores (Google Play and App Store) and Instagram apply their own policies when you follow those links. The Web version may also use browser storage.
Sharing
We share data with the providers above as needed to run the feature (sign-in, maps, measurement or in-app ads). Public authorities receive data only if required by law.
Transit information shown in the product comes from external operational sources; that does not make those operators responsible for your account data.
Storage and retention
Local preferences stay on the device until you clear them or uninstall the app. Account data and interactions remain on platform services while the account exists or as needed for security and legal duties.
You can edit or delete your account where the feature is available in the signed-in app.
Your rights
You may request access, correction, deletion, information about sharing, and a review of cookie consent. In Brazil these requests are supported by the LGPD.
To exercise rights, write to contato@tachegandobus.com.br. We may ask you to confirm identity to prevent unauthorized access.
Changes
If data processing changes in a relevant way — for example when a new ad or measurement provider is added — this page will be updated. The revision date appears at the top of the content.