A language choice does not establish a person’s location or permission to receive a campaign. Record the intended market and language variant separately. Use an actual preference or a reviewed audience decision rather than guessing from a surname, domain suffix or continental label.
A Portuguese version for an audience in Brazil and Spanish versions for other audiences may share a campaign objective while needing different language review, offer presentation and destination pages. Avoid one catch-all regional message when the recipient journey is materially different.
Review the entire offer in context
Give each reviewer the subject, preheader, sender identity, image copy, buttons and landing page together. Record how prices, dates and important conditions appear. If the destination page remains in another language, make that visible during review rather than discovering it after a recipient clicks.
Keep one brief for the shared objective and separate decisions for each variant. Document what the recipient should do, what a successful action means and who handles replies. A translated call to action should lead to the same understandable task, with conditions that remain accurate.
Map the systems before making a residency statement
List where contact details, message content, delivery events and replies are processed. Include the application, selected database region, sending route and any relevant support, account, logging or integration services. A location attached to one system does not automatically describe every part of the processing chain.
Brazil’s ANPD publishes an official resource on international data transfers. Use it as a starting point for the review relevant to the actual data flow. Do not assume that a European database location alone resolves the applicable transfer or local requirements. Assign that review explicitly and record the unresolved questions.
Keep the route and the total cost clear
SendMailOS supports hosted delivery and a connected own-server route. Own-server sending starts at €12/month, with no monthly platform email quota for messages actually sent through that server. The VPS is paid separately. Capacity, provider policies, warm-up, safety checks, fair-use rules and other plan limits apply.
Choose the route your team can operate, then test the real message and destination pages before launch. The brief below helps connect content ownership with data-route questions. It does not translate a message automatically, inspect your infrastructure, promise inbox placement or certify a campaign for any jurisdiction.
This worksheet stays in your browser and is not sent to SendMailOS. Use general planning notes; avoid personal data, recipient lists, passwords and API keys.
Portuguese / Spanish campaign and data-route brief
Prepare a generic content handoff and data map. Do not enter recipient names, addresses or personal message content.
Questions & answers
Does Spanish copy create one campaign that fits every South American market?
No. Review the actual language preferences, market context, offer conditions and destination pages for each intended audience.
Does the Brazil transfer resource cover every country in South America?
No. The linked ANPD resource concerns Brazil. Review other recipient markets and data flows separately with the relevant current primary guidance.
Does a database in Germany automatically settle transfer requirements?
No. Map the complete processing flow and review the applicable requirements. A database location is a factual input to that review, not a universal compliance conclusion.
Reviewed 25 October 2026. Official Brazilian starting point for transfer-mechanism review; no claim that SendMailOS has completed a particular mechanism or local approval.
Choose the sending route that fits your operations
Use hosted delivery or connect your own sending server. Compare the subscription, hosted allowance and separate server cost before deciding.