Product, beta access, partnerships, and press
Use the general inbox for roadmap questions, collaboration, editorial coverage, integrations, and commercial conversations.
Best first stop for almost every institutional or product conversation.
Contact
Use the right channel and the conversation moves faster. Privacy and legal requests go to dedicated inboxes. Product, partnerships, and press start in the general inbox.
PT + EN
languages accepted in messages
primary channel at this stage
3 routes
product, privacy, and legal
Channels
The point of this page is to reduce triage. If the topic lands in the right inbox first, the answer is usually sharper.
Use the general inbox for roadmap questions, collaboration, editorial coverage, integrations, and commercial conversations.
Best first stop for almost every institutional or product conversation.
Access, correction, deletion, portability, or data-processing questions should go straight to the dedicated privacy channel.
Use this for privacy rights, policy questions, and data preferences.
Formal legal requests, terms questions, contract topics, and brand or policy matters should go to the legal inbox.
Best when the conversation needs formal review or documentation.
If your question is mostly about fit or value, the fastest path may be to create an account and see the early product flow.
Useful when you want hands-on context before opening a thread.
Checklist
The rule is simple: the more concrete the context, the lower the odds that an email thread spends three replies discovering the basics.
Say what you want to unblock instead of sending a vague “can we chat?”.
If the topic depends on market, currency, or trip type, say that up front.
Page links, screenshots, visible errors, and real deadlines help far more than abstract descriptions.
Shortcuts
Not every question needs a thread. For some topics, the fastest move is simply opening the right document.
See how Compasso handles data, legal bases, and user rights.
Review service rules, eligibility, and acceptable-use boundaries.
Understand cookie categories, controls, and preference handling.
Read the product thesis, supported travel contexts, and current build direction.
FAQ
Strong contact pages remove operational ambiguity. That is the whole point of this section.
Anything tied to privacy rights, data processing, or account data should go to contact@compassoonline.app.
Yes. This page assumes contact@compassoonline.app as the general inbox for institutional and product conversations.
Yes. The public product already operates in PT-BR and EN, so both languages make sense for inbound contact.
Open thread
When the topic needs a dedicated path, privacy and legal still keep their own channels.