Your data, your choices. Here you'll find our Privacy Policy, Terms of Use and ways to manage your account.
Last updated: 26 October 2026 · Version 2026.10.26
Looking for Malinha's privacy policy?
Our children's app has its own policy. The account, advertising and service practices for the Hey Bora Viajar app described below do not apply to Malinha.
The website heyboraviajar.com and the app Hey Bora Viajar are the responsibility of Thadeu Tavares Basbaum Schettini, Brazilian taxpayer ID (CPF) 141.124.147-90, who is responsible for decisions about personal data processing described in this policy.
For privacy, exercising your rights, support and purchase questions, write to contato@heyboraviajar.com. This is the responsible person's contact channel; you do not need an account to use it.
This policy covers the website and the app features you actually use. The app is in pre-release: availability, integrations and paid options may vary by version, platform and plan. Mentioning a feature in this policy does not mean it is already available.
02 · YOUR BROWSING
Privacy on the website
The website does not require registration and has no email capture form. You can download the free guide without providing contact details. Fonts and images are served by the website itself; the hosting infrastructure may process IP addresses, dates and times, requested pages, browser information and technical logs to deliver and protect the service.
Cookies and audience measurement
On the website, your language choice is stored for up to one year in a functional cookie, without use for advertising or audience measurement.
We use Google Analytics only after you give permission for analytics cookies. It helps us understand visits and pages viewed. You can decline without losing access to content, or change your choice using “Change analytics cookie preference” at the end of this page.
Your choice is stored in this browser. Withdrawing permission stops new analytics events and removes Analytics cookies accessible to the website; it does not retroactively erase information already received by Google. We have not installed Meta Pixel in this version. Query parameters and URL fragments are excluded from page addresses sent by our Analytics integration.
Links, downloads and support
When you open Instagram, YouTube, WhatsApp, a store or your email app, you use that service under its own rules. These channels are not embedded as feeds or automatic videos. If you send us a message, we process your contact details and its content to respond and follow up on your request.
Interactive demonstrations on the app page use examples and work only within the open page. Ticking a checklist or choosing a vote does not create an account or send those choices to the app.
03 · APP PRIVACY POLICY
Which data is used and why
Collection depends on the features used and the information you choose to enter. Account data is needed for authenticated features; photos, documents, audio, location and participation in a trip depend on your use of those functions.
Account and preferences
Your name, email, account identifier, profile photo and preferences enable authentication, participant identification, personalisation and support. Credentials are handled by the authentication service; we never ask for your password by email.
Operational sign-up counts
When enabled in the service, operational counting records new app accounts to monitor the service's operation and growth from the start of that measurement. It covers available sign-up methods and is separate from usage statistics and advanced analytics choices. Turning those options off does not stop this operational record. Signing in or adding another sign-in method to the same account does not create a new sign-up. An account does not necessarily represent one unique person.
We use daily counts and private receipts with protected identifiers to prevent duplication and handle account deletion. These receipts are not treated as anonymous data. Receipts and their classifications have a nine-day lifetime, and daily counts a 90-day lifetime; a cleanup routine handles expired records. Coverage may have delays or gaps and does not represent a historical total of all accounts that have ever existed. Confirmed test accounts and cases with insufficient classification are shown separately.
When an account is deleted, we process the removal of receipt-linked details, retaining only the minimum anti-duplication marker until its original expiry. The earlier creation is not subtracted as a negative sign-up. This processing and physical cleanup are asynchronous.
Reports are restricted to administrators and do not show lists of people, email addresses, IP addresses, locations, documents, bookings or conversations. This purpose does not enable advanced analytics or personalised prompts, or link sign-ups to offers, purchases or notifications. Data requests can be sent to contato@heyboraviajar.com, without sending a password or token.
Planning and collaboration
Destinations, dates, itineraries, bookings, flight information you enter, travellers, invitations, messages, votes and checklists help organise and share a trip. Trip content may be visible to participants according to each feature's permissions.
In Travellers, a phone number is optional. If entered, it is saved on our server with the traveller record and can be viewed by authorised trip participants. It supports group organisation and contact; it is not used for advertising. You can remove it by editing the traveller. Obtain permission before entering another person's data. This shared record is separate from personal contacts stored only on your device.
For bookings, you can record free cancellation and check-in deadlines, meeting points, arrival lead times and the booking's phone number. This data, including the number, is visible to the travel group. When a poll is decided, we store the selected option, who decided and when; the decision may create an itinerary activity or change trip dates for the whole group.
When the feature is available, you can share a link from another app to Dreams. On saving, we store only the address, a title and the category: the post's caption and content are not copied, tracking parameters are removed from the address, and neither the app nor our server opens the page.
Expenses and digital purchases
Amounts, payers, splits and receipts you add are used to organise expenses. Transaction identifiers, products, credits, subscription status and refund events help recognise and maintain purchased access. Recording an expense does not transfer money.
Each foreign-currency expense stores the exchange rate used, its date and source, or the rate you entered, and may be linked to the booking it pays for. Our server retrieves rates without sending your data to the source. Rates are a reference: your card may charge a different rate and Brazilian IOF tax.
Photos, files and documents
Files you choose, profile and moment photos, attachments, documents and their metadata are used in the feature where you upload them. Check recipients and visibility before adding your own or another person's documents.
In My Family, you can record people, expiry dates and selected files, such as a document photo, insurance PDF or visa. Records and attachments remain on your device until you enable synchronisation and backup options.
When you enable synchronisation, record data is sent to your account's private area. When you enable private backup, selected files and their metadata are also stored on our servers for recovery through the same account on another compatible device. Access is authenticated; these files are not given a public sharing link.
Linking another account to your family or adding someone to a trip does not share your private documents. Linking accounts and accepting trip participation are separate actions. The linked account's profile photo may appear to identify the person.
Disabling backup stops new uploads but does not delete files already stored on the server. Removing a backed-up attachment and deleting an account use their respective deletion flows. Copies saved or shared outside the app remain under their recipients' control. Before adding another person's documents or images, obtain the necessary permission and include only what is useful for the trip.
Location and maps
Destinations, activity coordinates and, when authorised, device location help display places and guide navigation. The operating system explains the scope of the requested permission; you can change it in your phone's settings.
When searching for places, the text entered is sent to Geoapify to suggest addresses and coordinates. If you choose a reference location, it may be sent to prioritise nearby results. The selected place may be saved in your trip planning.
To display weather forecasts and calculate activity reminder times, the app sends the trip destination's name to our server, which locates it through Geoapify and stores the result for up to 24 hours. Only the destination name is sent to Geoapify, without account or personal location data. Using the resulting point, our server requests a forecast from MET Norway, as described in “Sharing and external services”.
The “View route” button in reminders opens Apple Maps or Google Maps with only the activity's destination, to calculate a route from your current location.
Assistant and voice
When available and activated, the assistant receives your messages, relevant profile preferences and trip context, including a sample of planned activities, to generate suggestions. Saved preferences may be confirmed for each trip. Suggestions do not change your plans without confirmation. Audio submitted for transcription is also processed to convert speech to text. Avoid including passwords, card details or unnecessary documents.
AI reading
When available, AI reading turns pasted text, a screenshot, a receipt photo or a PDF of up to 3 pages into suggestions for places, bookings or expenses. Content passes through our server and is sent to OpenAI only after you permit it; for a trip, its destination, dates and currency are included. The result is a draft: nothing is saved to the trip or Dreams without your review.
We do not store the screenshot, photo or PDF: the file is used only during reading. We remove metadata such as location and device information from images before sending them. In pasted text, card numbers and Brazilian CPF numbers are replaced with “(removed)” before sending, and the result undergoes the same cleaning. Image and PDF content is sent as is; avoid unnecessary data. The server does not open links found in the content. If you choose to attach the file to a booking or expense, it is stored like any other attachment.
Technical data and interactions
Access logs, errors, app versions, account or device identifiers, notification tokens and feature interactions may be processed for operation, security, synchronisation, notification delivery and personalisation. Identifiable usage data should not be confused with anonymous data.
Statistics to improve your experience
In compatible versions, basic usage statistics are enabled by default when you sign in or create an account. They help us understand which features are used, at what times and at which trip stage, to improve the app's experience and reliability. You can disable them in the app's privacy controls without losing travel features.
Counters record usage by area, trip stage and time band, with UTC date and time and action category. Basic statistical batches do not include names, emails, account or device identifiers, destinations, document content, photos or conversations, Wi-Fi, location or family relationships. Authentication, security and operational logs follow their own practices described in this policy; we do not treat all usage information as anonymous.
Your opt-out preference is saved on this device and is not removed by clearing only the cache. Disabling stops new observations and submissions and removes pending local batches. Account deletion removes the preference and queue from this device. Already aggregated counts cannot separate one person's use for individual removal. These counters do not measure unique people, notification reading or purchases. We do not send these statistics to an analytics provider or AI model.
Advanced analytics and verified sources
Advanced analytics is a separate option, initially off, that requires your authorisation in the app. When authorised, it links defined navigation and action events to your account, such as opening a trip, saving a dream, exploring places, reviewing an import, preparing an offline copy or generating a film. It may consider trip stage, interaction times and periods of active use with the screen in the foreground. An analytics session does not equal continuous usage time. Analytics identifiers are protected; this does not make individual records anonymous.
Specific source authorisation also permits the use of verified purchase, refund, subscription status and provider notification-acceptance events. We do not collect complete payment details for this analysis. Provider acceptance does not confirm that a person received or read a notification.
Administrative reports limit data exposure and suppress small groups; reports subject to this control require at least 20 contributors. They do not display document, conversation or photo content. Withdrawing advanced analytics authorisation stops new records for that purpose and triggers revocation processing for linked records. This does not erase all operational information needed for the account to function.
These statistics do not collect Wi-Fi network names or passwords, home network information, browsing history in other apps or continuous location. The current implementation does not use device location or IP-inferred regions as variables in these statistics. Map location and technical IP processing by infrastructure and advertising are separate matters, described in their own sections.
Reminders and personalised prompts
Automatic prompts have their own controls. When you authorise them and use a compatible app version, the system may process permitted usage signals on our servers to choose an action useful for your trip stage and an appropriate time, such as continuing planning or reviewing preparations. Availability on the server does not replace your individual preference.
Reminders, personalisation and promotional communications are distinct choices. Personalised prompts respect your phone's notification permission, eligible times, a minimum 72-hour interval and a limit of two prompts per week. These limits do not apply indiscriminately to every operational trip notice. We do not guarantee a message just because a rule identified an opportunity. Offers also depend on your specific News and Offers choice.
To assess results, we distinguish sending attempts, provider acceptance and opening or actions when evidence is available. The corresponding advanced collection depends on authorisation for its purpose. We do not assume a purchase was caused by a notification simply because it happened afterwards. You can change your choices or disable prompts without deleting your account.
In versions with local learning of suggestions and timing, the last 28 days of history stay only on this device, without synchronisation or submission alongside basic counts. This feature is separate from the advanced analytics and server-side prompts described above. A local code distinguishes completed objectives without copying trip names or content. Personalisation and notification controls let you enable it, view a summary, or erase and disable this learning; if the system clears its cache, it remains off until you choose again.
We do not infer residence, work schedules, marital status or kinship, or use these signals to set individual prices. Describing a feature here does not mean it is available on every platform or version.
App authenticity (Firebase App Check)
In versions with this control, the app requests technical proof from Google Play Integrity on Android or Apple App Attest on iPhone, validated by Firebase App Check. This helps prevent tampering and abuse. The temporary proof accompanies requests and does not contain your conversations, photos or documents. This control's specific logs store counts by outcome, without storing the proof. Providers process the technical signals needed for verification under their policies.
Crash reports (Firebase Crashlytics, Google)
When the app encounters an error or closes unexpectedly, we send a technical report to find and fix the defect. It contains the error's technical trace, device model and operating system, installation identifiers and your account identifier. Before sending JavaScript error messages, the app filters emails, credentials, coordinates and long numbers. For internet addresses, it removes parameters and fragments and hides part of the path; the domain and alphabetical path segments may remain. File URI paths are replaced, but the technical trace may contain file and function names. This app filter does not apply to native crash reports collected by the Crashlytics SDK. Reports are not used for advertising and are retained for 90 days.
Local data and offline use
Personal trip contacts and “Ready to Go” choices (the trip's country and items marked “Not applicable”) stay only on your device: they are not sent to our server or group and do not transfer to another phone. Deleting a trip or account erases this data from the device; using Sign Out on this device also erases these contacts and choices. A booking's phone number, however, remains in the booking and is visible to the whole group. Family documents and files have their own synchronisation and private backup options, as described above.
Offline preparation keeps a copy of selected trip content and files on your device and, when available, a limited map area. This copy may become outdated; internet is still needed to update data and use server-dependent functions. Preparing an offline copy does not publish or share new documents.
Booking deadline alerts and reminders are scheduled on the device itself. Deadline alerts go only to the person who created the booking and do not show codes, prices or receipts, as they may appear on the lock screen.
The trip recap image and itinerary PDF are generated on your device, and the temporary file is deleted after use. The image includes only the moment photos you select, up to 3; expenses are excluded unless you enable that option, and even then only your share appears. The map does not show accommodation or your exact location. The PDF excludes booking codes and notes unless you include them. Anyone receiving the image or PDF can see its contents.
Moments and trip films
Moments may be linked to itinerary activities. Your chosen visibility determines who can view them in the app. Seeing a photo in a group does not, by itself, authorise its use in an exported film.
To use a photo posted by someone else in a film, its publisher must authorise that use. The app checks authorisation and the photo's version at the applicable preparation and export stages. The author can withdraw permission for new uses; withdrawal does not recall videos or images already exported or shared outside the app.
Film preview and generation use selected route segments, titles and media on your device. In compatible Android versions, export creates a local video file. The app does not automatically post to social networks: you choose to save or share, and the destination service handles the file under its own rules. Review the content before sharing, including names, routes and people shown in images. Features and availability vary by platform and version.
The phone's home screen widget, when available, shows the next trip activity, including its name, time and location, from a locally stored copy, without booking codes, documents or participants. Anyone looking at the phone screen can see it. Signing out or deleting the account erases that copy.
Advertising in the app
In versions with advertising enabled, free-plan accounts may receive Google AdMob ads. Test versions may show demonstration ads. In versions with advertising disabled, the ad integration is not started. Availability varies by platform, version and plan.
When this integration is used, Google may collect IP addresses, approximate location estimated from IP, device and app information, advertising or device identifiers when available and permitted, ad interactions and SDK performance and diagnostic information. This data supports ad delivery, measurement and security, including frequency limits and fraud prevention.
The current configuration requests non-personalised ads. This does not mean anonymity or no collection: technical data and identifiers may still be used for the purposes above, according to privacy choices and applicable rules. On iOS, our integration does not request ATT tracking permission or access to the IDFA advertising identifier; the publisher's first-party advertising identifier is disabled on both platforms.
We use Google's User Messaging Platform (UMP). It may present notices and choices by region, including the European Economic Area, United Kingdom, Switzerland and US states subject to specific rules. Where applicable, you can review these choices in “Ad Privacy”, beside the ad or in app Settings. Declining personalisation should not be confused with eliminating all advertising data processing.
We rely on performance of a contract and procedures you request for accounts, planning, collaboration, support and delivery of purchases. Legal obligations may require specific records. Consent underpins optional uses that require it, such as website analytics and advertising uses requiring your authorisation. Applicable advertising choices and rights to object are presented through privacy controls. Security and abuse prevention may rely on legitimate interests, respecting necessity, proportionality and your rights. A phone permission is a technical access control and does not replace assessment of the legal basis for each purpose.
Sending content to OpenAI for assistant conversations, voice message transcription and AI reading relies on your consent (Article 7, I, of Brazil's LGPD). The app asks for permission before the first submission, and you can withdraw it at any time in Profile → Privacy Policy, using “Withdraw AI permission”. Afterwards, nothing is sent without renewed permission; saved conversations remain in the app until you delete them. Firebase Crashlytics reports rely on the legitimate interest in finding and fixing app defects (Article 7, IX, of the LGPD), with 90-day retention. The filter described above applies only to JavaScript errors before submission; native reports are collected by the SDK.
Other people's data and children
The app is intended for account holders aged 18 or over. Family trips may include information about minors entered by their responsible adult. Provide only what is necessary, respect the child's or adolescent's best interests and ensure you have authority to share their data and images. Do not create accounts in children's names or submit unnecessary sensitive data. A responsible adult may send requests relating to minors through our contact channel.
04 · CONTROL ON YOUR PHONE
Permissions and access
Location: for map and navigation functions you choose to use.
Camera, photos and files: to select or capture content to upload, such as an avatar, photos, attachments and, for AI reading, screenshots, receipts and PDFs.
Microphone: for voice messages and transcription, when available.
Notifications: for app and trip communications, according to the version and your choices.
Calendar: on Android, syncing trip dates and events uses calendar access only after your authorisation. On iPhone, the app does not request Calendar access: you can export an .ics file and choose where to share or import it. This copy is not updated automatically when the trip changes; importing again may duplicate events. Review the data and destination before sharing the file.
You can deny or revoke permissions in system settings. This may limit the relevant feature. Revocation does not remove files or information already submitted; use the feature's deletion option or contact us for that data.
The device may store sessions, preferences and local content copies to support access and offline use. Protect your phone and do not share credentials. Uninstalling the app may remove local content but does not automatically close your account, delete server data or cancel a subscription.
05 · WHO MAY RECEIVE DATA
Sharing and external services
Operation may involve the following recipients, limited to the feature's purpose:
Your trip participants: information and content shared in the group. Anyone receiving an invitation code may use it to join; share it only with intended people.
Google Firebase and Google Cloud: app authentication, infrastructure, databases, files and notifications, authenticity checks with Firebase App Check and Google Play Integrity, and Firebase Crashlytics reports, which are not used for advertising, as described under “Crash reports”.
Apple App Attest: technical app authenticity checks in iPhone versions with App Check, for security and abuse prevention.
Google AdMob and the UMP messaging platform: ad delivery and measurement, fraud prevention and recording privacy choices in versions with advertising enabled, as described under “Advertising in the app”.
Apple, Google Play and RevenueCat: store billing and management of purchases, subscriptions and access rights, when enabled. These integrations use identifiers and transaction data. Complete card details are provided to the payment platform, not to fields on this website.
OpenAI: processing messages, context needed for assistance and audio for transcription and, for AI reading, pasted text, screenshots, receipt photos and PDFs of up to 3 pages, sent through our server to extract places, bookings and expenses. This happens only when the integration is enabled, you use these features and you have permitted submission to OpenAI.
Geoapify and map and navigation services: search text, reference coordinates when used and technical information needed to find and display places. Our server also queries Geoapify with the trip destination's name, without your account data, for weather forecasts and reminder time zones. When you open an external navigation app, including through “View route”, it receives the destination and its own practices also apply.
MET Norway (Norwegian Meteorological Institute): weather forecast source. Our server requests forecasts using approximate destination coordinates, accurate to around 1 km, and identifies itself as Hey Bora Viajar; no account or personal location data is sent.
European Central Bank (ECB), via Frankfurter: source of reference exchange rates. Our server downloads the day's ECB rate table through Frankfurter, without sending your amounts, expense currencies or account data. Hey Bora Viajar calculates conversions not starting in euros from those rates, and the app identifies the source.
Hostinger, Google Analytics and Kiwify: website hosting, analytics with your permission and guide checkout, respectively.
Support and authorities: people authorised to handle a request and recipients required to fulfil legal obligations or exercise legal rights.
Some providers may store or process data outside Brazil, including in the United States. International transfers must comply with the grounds and safeguards set out in the LGPD and applicable regulations. You can request information about recipients and the conditions applicable to your case through our privacy channel.
Recommendations and affiliates
Referral links may generate commissions or benefits for Hey Bora Viajar. The destination store may use identifiers and cookies to attribute the referral. Browsing, purchases, payment and delivery of external products follow the seller's terms. Check offers at their source; prices and availability may change.
Also read the policies of the services you use: Google, Apple, RevenueCat, OpenAI and Kiwify. Esses documentos complementam, sem substituir, nossa responsabilidade pelo tratamento que realizamos.
06 · RETENTION AND PROTECTION
Retention and security
Account data and content are retained as needed to provide the service and fulfil the purpose for which they were provided. When you request deletion, we assess and remove covered personal data, subject to legal exceptions and other participants' rights.
Files and your plan's storage
Online file allowances are 50 MB on Free, 1 GB on Pro and 5 GB on Agency. Photos may be optimised before upload. When usage exceeds the current allowance, new uploads are blocked; existing files remain available to view and download. Unlocked itineraries and text-based planning are not deleted for lack of space.
If the end or downgrade of a paid plan leaves files above the new allowance, you have 90 days to resolve this from the end of the paid period that caused the reduction. During this time, you can download files, remove what you no longer need, choose what to keep or adjust your plan. The storage screen shows usage and the deadline.
Notices are available in the app. Phone notifications may supplement them, depending on your permissions and service availability. Sending a notification does not prove you read it: any automatic removal requires you to acknowledge the notice in the app during the resolution period. Without acknowledgement, files are preserved for review, while new uploads remain blocked above the allowance.
After 90 days and acknowledgement of the notice, excess removal, when enabled, starts with the oldest personal files and stops once usage fits the allowance. Shared files and those marked to keep are protected, as are itineraries and planning. Choosing files to keep does not increase the storage limit; if protected content still exceeds the allowance, new uploads remain blocked.
AI conversations and technical copies
In versions supporting recovery of free introductory messages, a response is available for recovery for 7 days if the connection drops. The technical server copy stores the text, suggestions and basic trip data: trip reference, destination, dates, number of travellers, budget, currency and interests. This data may come from the context you sent. Traveller profile fields, saved preferences and the existing itinerary are removed from this copy. We do not store the question as a separate field in this record, but the response text and suggestions may repeat personal information you provided. In the live response, the profile and preferences may return to the app to continue planning and be saved in the conversation. The itinerary sample and already-known profile recovered by the app from the attempt stored on this device may also be saved in the conversation. That conversation differs from the reduced technical copy used to recover the response on the server. Later recovery and export of that technical copy retain the reduced fields described above. After this period, recovery is blocked. Content removal is handled by the automatic purge routine and may take longer; after removal, a minimal record remains to prevent a repeat of the same request from consuming another message. Account deletion also covers these records.
The technical copy used to recover a credit-based response or generation remains recoverable for 30 days. After that, recovery is blocked. The automatic purge routine removes the content and may take longer; after removal, only minimal consumption and control records remain to prevent duplicate charges. This does not delete saved conversations or activities added to the trip, which remain until deleted. This period differs from the 90 days for files above the allowance and is not a general account deletion deadline.
To recover an interrupted chat submission, the app also stores the attempt identifier, the request with submitted context and history, and the local message on the device. This copy differs from the response stored on the server. It is removed when the response is saved or the attempt is closed in the app, and when you sign out or delete the account on this device. An expired or revoked session may preserve the attempt for recovery when you sign in again. For free attempts, when checking a pending request, the app also discards the record after 7 days plus a 5-minute margin. For credit-based attempts, the local copy is removed when the query reports that server recovery has expired. Device storage failures may prevent cleanup. Signing out may prevent recovery of an unsaved response, even if the message has already been consumed. Local cleanup does not cancel server processing, resend the question or automatically refund it.
For AI reading, this 30-day copy stores the pasted text, submitted trip context and returned draft. For screenshots, photos and PDFs, it stores only type, size, page count and a file verification code, never the file itself. After 30 days, recovery is blocked; the automatic purge routine removes the content on a variable schedule. After removal, only the minimal consumption and control records described above remain.
Statistics and prompt retention periods
For operational sign-up counting, receipts and their classifications have a nine-day lifetime and daily counts a 90-day lifetime, with asynchronous physical cleanup. These periods are separate from the other usage records described below.
Local basic and advanced statistics queues accept data up to seven days old. Basic batches are separated by account and remain eligible for up to seven UTC dates; expired data is discarded on next use, and the closed app does not run this cleanup. On the server, basic counts have a configured 90-day lifetime. For advanced analytics, events have a 30-day lifetime; contributions and reports, 90 days. For prompts, events have a 30-day lifetime and applicable follow-up records, 90 days.
These periods govern expiry and cleanup routines; they do not mean instant physical deletion of every copy. Preference, revocation, security, audit and legally required records may follow their own rules. To request access, correction or deletion, use the available controls or write to contato@heyboraviajar.com, without sending a password, token or documents beyond what is needed to verify the request.
Crash reports, weather and exchange rates
Crash reports remain in Firebase Crashlytics for 90 days. A destination's location resolved by name is stored on our server for up to 24 hours, and weather forecasts for a few hours; neither is linked to your account. Reference exchange rate tables contain no personal data. The rate used in an expense stays in that record for as long as the expense exists.
Required records and security
Records needed for tax obligations, purchases, fraud prevention, handling rights and defending legal claims may be retained with restricted access for the legally required period or while the obligation or dispute justifies retention. The category, reason and applicable period for any retention must be stated in the response to the request. Backups and technical logs may have their own purge cycles; we do not promise instant deletion of all copies.
We use authentication and authorisation controls and protected communication in transit to reduce unauthorised access. No system offers absolute security. If you suspect unauthorised access, contact us and protect your credentials. We do not describe shared content as protected by end-to-end encryption.
07 · YOU HAVE A CHOICE
Your rights
Under Brazil's LGPD, you may request confirmation of processing, access, correction, information about sharing, portability where applicable, anonymisation, blocking or deletion of unnecessary, excessive or unlawfully processed data, as well as withdraw consent and request deletion of data processed on that basis, subject to legal retention exceptions. You may also object and request review of exclusively automated decisions affecting your interests, where applicable.
In the app, Profile → Settings → Export my data creates a copy of the groups of records linked to your account identified in the file. For example, it includes bookings you added, with deadlines, meeting points and phone numbers; expenses, with the exchange rate used and linked booking; poll decisions you made; and technical copies of credit-based responses, generations and AI readings not yet removed by the purge routine, including where their recovery period has ended. The technical copy of free responses remains reduced and does not include content after the 7-day recovery period. The export does not include saved Travel Assistant conversations, which you can view and delete in the app's history. Those conversations differ from the technical AI response copies included in the export. The copy also excludes photo, receipt and document files. Privately backed-up family files can be viewed through their own feature, according to the options in your version. Data that stays only on your device and that we do not receive is viewed, corrected and deleted in the app itself. To request data not included in this export, use the contact below.
Send your request to contato@heyboraviajar.com. We may request proportionate identity verification to protect the account, without requiring your password. Confirmation and access requests follow the methods and deadlines in Article 19 of the LGPD: an immediate simplified response or a complete statement within 15 days. Other requests will be handled within applicable deadlines, with updates on progress and any obstacles.
You may also petition Brazil's National Data Protection Authority and consumer protection bodies. Exercising statutory rights is free of charge.
08 · A ROUTE WITHOUT SIGNING IN
Delete an app account or data
You can request deletion of your Hey Bora Viajar account and associated data even if you cannot sign in to the app.
Use the subject “Account deletion — Hey Bora Viajar” and state that you want to delete the account and linked data. Do not send a password, complete identity document or card details in your initial message.
If you have lost access to the registered email, mention it so we can arrange suitable identity verification.
Follow the replies to confirm your identity, resolve shared trips, learn about any retention and receive confirmation of completion.
The button opens your email app. Nothing is sent automatically. You can also copy the address and write through your email service.
Deletion within the app
When available in your version, go to Profile → Settings → Delete account. Use the email channel if the option is missing or does not complete the request. You do not need to reinstall the app to request deletion.
What is covered
The request covers your profile, photo, messages, assistant conversations, AI readings, documents, personal files, preferences and account links. Trips belonging exclusively to you are covered. If you organise a trip with others, tell us whether you want to transfer organisation; we will assess removal while preserving other participants' rights.
Shared planning and expense amounts may be preserved for other travellers with identification and personal content removed where appropriate. We do not treat replacing an identifier alone as a guarantee of anonymisation. We will explain what must remain, why and for how long. Copies other people have exported or stored outside the service are not automatically deleted.
For bookings you created in shared trips, the phone number and meeting point are deleted, as are notes; deadlines and times remain with the group for planning. For expenses, the exchange rate and linked booking may remain with the amounts. For other people's polls that you decided, the decision remains valid for the group, and the decision-maker record no longer points to your account. Device-only data is erased from that device when you delete your account through the app; if requested by email, delete it in the app or uninstall the app.
Delete only some data
You can remove items within the relevant feature, when available, or request deletion of specific data by email, without closing the entire account. Describe the item or trip so we can locate it, avoiding reattaching the document you want deleted.
Accounts and subscriptions are different
Deleting your account or uninstalling the app does not cancel a store subscription. Manage cancellation in Google Play or in the App Store. We do not require you to end a paid period to exercise your rights. Before deletion, ask for guidance on purchased content, credits and any refunds.
09 · WEBSITE AND APP TERMS OF USE
Good agreements for travelling
Improving the experience and suggestions
Basic usage statistics help improve the experience and are enabled by default in compatible versions, with an option to disable them in the app. Local learning, advanced analytics and personalised prompts have their own choices; accepting these Terms does not enable them or automatically authorise offers. See data, limits and controls in the Statistics to improve your experience section of this Privacy Policy.
The operational sign-up counting is a separate purpose from those options. It begins when enabled in the service, subject to the limits and periods in its own section, and does not automatically authorise offers or notifications.
Service and eligibility
Hey Bora Viajar offers editorial content and tools for travel planning, organisation and collaboration. The app requires an account for certain features and is intended for people aged 18 or over. This page is freely accessible. Purchase terms and conditions must be available before purchase; obligations to obtain specific consents and acceptances are not replaced by simply browsing the website.
The app helps organise information; it does not issue tickets, transfer money between participants or confirm bookings merely because you entered them. Unless expressly offered otherwise, a recommendation does not constitute a booking or purchase of accommodation, transport, insurance, activities or products.
Accounts, invitations and responsible use
Provide accurate data, protect your credentials and report suspicious access. Each participant is responsible for their own actions within the law. Do not use the service for fraud, harassment, discrimination, unlawful content, infringement of third-party rights, access to others' accounts or interference with systems. Invitation codes and shared links should be sent only to intended people.
Organisers and participants must respect each trip's permissions. Consider other travellers before changing or deleting shared content. Enter another person's data only when you have authority to do so.
Shared content and zero tolerance
We do not tolerate offensive, discriminatory, harassing, threatening, sexual, spam, scam or illegal content in trip messages, comments and moments. Any trip participant can report content in the app, and the publisher is not told who reported it. We review reports within 24 hours and may remove content and suspend or close the publisher's account.
You can also block someone: their content stops appearing to you without notifying them. Organisers can remove participants, and each participant can leave a trip at any time.
Your content and our materials
You retain your rights to content you submit. You grant only the non-exclusive permission necessary to store, process and display it to provide the service and share it according to your actions and permissions. This does not authorise use of your image in advertising without specific permission.
Brands, texts, guides, original itineraries and interfaces are protected by applicable rights. Access to digital content grants personal use according to the offer, without automatic permission to resell, republish in full or distribute without authorisation. This rule does not restrict uses permitted by law.
Planning, AI and travel information
Times, prices, weather, accessibility, entry requirements and availability may change. Check official sources and providers before paying, booking or travelling. AI suggestions may contain errors and require review. The app does not replace professional advice, required documents or emergency services.
Scheduled flight times are not real-time tracking. Automatic delay, cancellation and gate alerts are not yet available. Check with the airline and airport. Use maps and routes with attention to local conditions.
Availability, suspension and liability
Features may require internet, permissions, a compatible device, synchronisation or an external service. Offline content depends on having been saved and remaining available on the device. We may perform maintenance and restrict misuse, with proportionality, communication where appropriate and a channel to contest decisions.
Uninterrupted availability or absence of faults is not guaranteed. This does not exclude the provider's statutory liabilitiesor rights to correction, repeated performance, price reduction, reimbursement or compensation where due. Third-party terms do not remove Hey Bora Viajar's own responsibilities.
Brazilian law applies, especially the LGPD and Consumer Protection Code where relevant. We do not impose waivers of rights, mandatory arbitration or a jurisdiction that prevents consumers from using the legally competent court.
10 · INFORMATION BEFORE YOU BUY
Guides, subscriptions and credits
Digital guides on the website
Guide purchases take place through Kiwify checkout. The offer page and checkout state the content, format, price, payment conditions and access. The product is digital unless expressly stated otherwise. Platform terms supplement the buyer's legal rights. For access or content problems, write to contato@heyboraviajar.com.
In-app purchases
When available, subscriptions and packages will show their price, currency, duration, benefits, limits and terms before confirmation. The price actually charged is the one displayed by the store in your region. A demonstration screen, free preview or “Coming soon” mention does not create a charge.
Subscriptions may renew automatically if stated in the accepted offer. Manage renewal and cancellation through the account used on the App Store or Google Play, observing the store's notice period. Cancellation normally prevents the next renewal and retains access until the paid period ends, unless a refund or applicable legal rule provides otherwise.
Credits and itineraries
Credits unlock content or features specified in the offer. They are not currency, investments, bank balances or a promise of cash redemption. A free preview does not mean the entire itinerary is free; the cost of unlocking the remainder must appear before confirmation.
Subscription credits are valid for their cycle and do not roll over. Separately purchased credit packs are preserved until used, subject to legitimate adjustments for refunds, fraud or chargebacks. Promotional credits may have their own rules, stated before participation. Changes must not retroactively remove rights acquired under an offer.
Assistant messages
After email confirmation, an account may use five free introductory messages, once only and without renewal. When the feature is enabled, you can voluntarily convert 1 universal credit into 10 messages. The app asks for confirmation: sending a message or requesting an itinerary does not automatically convert credits. Bonuses intended for itineraries and trips are not part of this conversion.
A conversational response uses one message; a complete itinerary uses five messages per block of up to seven days, with the cost shown before generation. Free introductory messages can also be used for this generation. Messages converted from subscription credits retain the cycle's expiry; those from separately purchased credits remain until used. Failures must not create duplicate charges. Operational limits may pause new responses; the app indicates availability before starting.
AI reading, when enabled, uses one message per reading and does not use free introductory messages. A reading that finds no places, bookings or expenses is not charged, subject to a daily limit.
Restoration, changing devices and the end of a plan
Use the app and store accounts associated with the purchase. Restoration depends on product type, verification and available options. Transfer between stores or accounts is not automatic. When a subscription ends, recurring benefits and limits may change according to the offer; previously purchased content and standalone credits must be assessed under their purchase terms and applicable rights. Contact support before deleting your account.
Withdrawal, refunds and disputes
Rights under Brazilian law remain applicable, including the statutory seven-day withdrawal right for distance purchases where relevant. The request method may vary by purchase: Apple, Google Play, Kiwify or our support. Platform operating rules do not override mandatory rights.
Send the order identifier and a description of the issue; do not send a password or full card number. Refunds or chargebacks may adjust the corresponding access and related credits, avoiding duplication and respecting the law. We do not promise automatic refunds outside statutory grounds and the offer's terms.
11 · A POLICY THAT FOLLOWS THE SERVICE
Updates and questions
This page will be reviewed when service features, purposes or terms change. The date and version appear at the beginning. Material changes should be communicated appropriately; where new consent or acceptance is needed, it will be requested. An update does not automatically authorise incompatible use of your data or an unaccepted charge.
For questions about this text, data requests, purchase problems or abuse reports, contact contato@heyboraviajar.com.