Partner Terms

Last updated: 4 November 2026

These Terms of Use (the “Terms”) govern the use of Tripomatic Travel Alerts (“Travel Alerts”), as defined in section 1. Travel Alerts is provided by Tripomatic s.r.o., with its registered seat at Za Parkem 631/14, Medlánky, 621 00 Brno, Czech Republic, registered in the Commercial Register of the Regional Court in Brno, Section C, File No. 57944, Identification No. 28274211 (“Tripomatic”, “we”, “us”).

Travel Alerts is intended for business use. This includes companies, as well as freelancers and independent developers who use Travel Alerts for their work or to build their own products. It is not intended for consumers. By requesting access, placing an order, receiving an API key or using Travel Alerts in any way, you accept these Terms on behalf of the company or organisation you represent (the “Customer”, “you”), and you confirm that you are authorised to do so. You confirm that you use Travel Alerts for the purposes of your business, trade or profession and not as a consumer. If you do not agree with these Terms, do not use Travel Alerts.

These Terms do not apply to the Tripomatic apps and website for travellers, which are governed by the general Terms of Use.

1. Definitions

• Travel Alerts means the Tripomatic Travel Alerts service and all related products we provide under these Terms, including the Travel Alerts API, webhooks and the MCP server.
• Alert means a travel advisory, warning, notice or other information about an event that may affect travel, such as severe weather, natural hazards, disease outbreaks, strikes or security incidents, as delivered through Travel Alerts.
• Alert Data means all data delivered through Travel Alerts, including Alerts, their structured fields (such as type, severity, time and area), match results, Source Content and Generated Text.
• Source means a public authority or other organisation that originally issues the information on which an Alert is based.
• Source Content means the original text, data and attribution of an Alert as published by its Source.
• Generated Text means summaries, titles, translations, ready-to-send messages and other texts that Travel Alerts creates automatically, including with the help of artificial intelligence.
• Registration means a set of locations (such as coordinates or destinations) and a time period that you register with Travel Alerts, together with your own reference identifier, so that we can send you matching Alerts by webhook.
• Plan means the subscription plan or individual offer you choose, including its price, limits and features, as set out in your Order or on our website.
• Order means an offer, order form, agreement or our written confirmation of your request (including by e-mail) that sets out your Plan and that you and we have accepted.
• Customer Application means your website, app, platform, service or internal tool in which you use Alert Data.
• End User means a person who uses your Customer Application, such as your traveller, client or employee.
• Documentation means the technical documentation of Travel Alerts that we make available to you, as updated from time to time.

2. What Travel Alerts includes

Travel Alerts collects travel-related information from Sources, processes it and delivers it to you in a structured form. Depending on your Plan, you can receive Alert Data:

• through the API, by requesting the Alerts that apply to destinations or locations you choose;
• through webhooks, by registering locations and a time period, after which we send matching new and updated Alerts to an endpoint you specify;
• through the MCP server, which lets AI assistants and agents you operate request Alert Data on your behalf.

The features, limits and languages available to you depend on your Plan. We continuously improve Travel Alerts and may add, change or remove Sources, alert types, features and fields. If a change materially reduces the functionality of your paid Plan, we will inform you in advance as described in section 12.

3. Access and API keys

We give you access to Travel Alerts once we have confirmed your Order, by issuing one or more API keys to you. You must give us accurate company, contact and billing details and inform us of any changes without undue delay. If we offer a customer account in the future, you will also be able to manage your access and details there.

API keys are confidential. You must keep them secure, use them only on your own servers or in your own systems and never place them in publicly available code, such as a mobile app or a website that End Users can inspect. You are responsible for all use of Travel Alerts made with your API keys. If you suspect that an API key has been disclosed or misused, you must inform us without undue delay at business@tripomatic.com and replace the key. We may revoke an API key that we reasonably believe has been compromised.

4. Plans, limits and fair use

Your Plan sets the limits of your use of Travel Alerts, for example the number of API requests per day, the number of active Registrations per month and the number of Generated Texts per month. The current limits of your Plan are set out in your Order.

If you exceed a limit of your Plan, we may, as described in your Plan, charge you for the additional use at the published rates, ask you to move to a higher Plan or temporarily slow down or refuse requests above the limit. You must not try to avoid the limits, for example by requesting access under different names or using several API keys for the same Customer Application.

We may apply technical rate limits to protect the stability of Travel Alerts for all customers. Details are described in the Documentation.

5. Trial

We may offer a free trial of Travel Alerts for a limited period and with limited features. We decide at our discretion whether to offer a trial and to whom. A trial is provided “as is”, without any commitment on availability or support, and may be ended by us at any time. Alert Data obtained during a trial may be used only for testing and evaluation, not in a live Customer Application, unless we agree otherwise in writing.

6. Fees and payment

You agree to pay the fees of your Plan. Unless your Order states otherwise:

• fees are stated in euros and do not include VAT or other taxes, which will be added where applicable;
• subscription fees are charged in advance for each monthly or annual billing period, and we give access to Travel Alerts only after the first payment has been received;
• fees for use above the limits of your Plan are charged after the end of the billing period in which they arose; however, if these fees reach the threshold set out in your Plan or Order during a billing period, or the amount of your monthly Plan fee where no threshold is set, we may charge them straight away;
• payments are made by the method set out in your Order or offered to you at checkout, such as by card through our payment provider or by bank transfer against an invoice;
• invoices are due within 14 days of their issue;
• fees already paid are not refundable, except where these Terms or the law provide otherwise.

If we use a payment provider that sells Travel Alerts to you as a reseller (merchant of record), the payment is made to that provider and its terms of sale also apply to the payment.

If a payment is overdue, we will remind you by e-mail. If the payment is not made within 3 business days of the reminder, we may suspend your access to Travel Alerts until all overdue amounts are paid. If you have paid late before within the previous 12 months, we may suspend your access as soon as the payment is overdue, without a further reminder. If a payment is more than 30 days overdue, we may terminate your subscription with immediate effect.

We may change the prices of Plans. A price change applies to you from your next billing period after we have informed you about it at least 30 days in advance. If you do not agree with the new price, you may cancel your subscription before the change takes effect.

7. Licence to use Alert Data

Subject to these Terms and payment of the applicable fees, we grant you, for the duration of your subscription, a non-exclusive, non-transferable and non-sublicensable right to:

• access Travel Alerts and use Alert Data in your Customer Applications, within the limits of your Plan;
• display and send Alert Data to your End Users, for example in your app, on your website, in e-mails, push notifications, messages or in answers of your AI assistant;
• store Alert Data temporarily for the purpose of providing your Customer Application, for no longer than the Alert is valid plus 30 days, unless we agree otherwise.

Unless we agree otherwise in writing, you must not:

• sell, license, rent or otherwise make Alert Data available to third parties as a standalone data product, feed or API, or in a way that allows third parties to access Alert Data in bulk;
• use Alert Data or Travel Alerts to create a product or service that competes with Travel Alerts;
• build a database or archive of Alert Data beyond the temporary storage described above;
• use Alert Data to train or fine-tune machine-learning models, other than providing Alert Data to an AI assistant as context for answering a specific request.

All rights not expressly granted to you remain with us or with the Sources.

The restrictions above apply to Alert Data as compiled, structured and generated by us, including Generated Text. They do not limit any rights you have to Source Content under the licence of its Source, which you can use as that licence allows.

8. Sources and attribution

Alerts are based on information published by Sources, which remain the owners of their content. Some Sources make their content available under licences that require attribution or set other conditions. To comply with these conditions, you agree to:

• display the attribution delivered with each Alert (as described in the Documentation), including any licence notice and link, wherever you show Source Content or Generated Text based on it to End Users, in a way that is reasonable for the medium;
• keep the notice delivered with Generated Text and translations that says they were created from, and differ from, the original Source Content;
• not change Source Content in a way that changes its meaning, and display unchanged any Source Content that the Documentation marks as not to be modified;
• not present Source Content or Generated Text as having been issued, approved or endorsed by the Source;
• not use the names or logos of Sources in a way that suggests that a Source is affiliated with or endorses you or your Customer Application;
• comply with any additional conditions for a particular Source that we make available in the Documentation, such as displaying a licence mark.

If a Source changes its conditions or stops providing its information, we may change or stop delivering the Alerts based on it. Where possible, we will inform you about such changes in advance.

9. Nature of Alerts and responsibility for their use

Travel Alerts is an information service. It is not an official warning system, an emergency service or a replacement for the instructions of public authorities. In particular:

• Alerts may be delayed, incomplete, inaccurate or out of date, for example because a Source publishes information late, changes it or is temporarily unavailable;
• matching an Alert to a location, destination or trip is an automated estimate, and an Alert may be shown for a place it does not affect, or not shown for a place it does affect;
• severity levels are our standardised interpretation of the levels used by Sources and may differ from the original classification;
• Generated Text is created automatically, including with the help of artificial intelligence, and may contain errors or omit information contained in the Source Content.

You are responsible for how you use Alert Data in your Customer Application and for the decisions you or your End Users make based on it. You must not use Travel Alerts as the only basis for decisions where errors or delays could lead to death, personal injury or serious damage. You must inform your End Users in an appropriate way that Alerts are provided for information only and that they should follow the instructions of local authorities and the original Source.

10. Webhooks

If your Plan includes webhooks, you can create Registrations and specify an HTTPS endpoint to which we send matching Alerts. You are responsible for:

• operating your endpoint securely and verifying the signature of each webhook request as described in the Documentation;
• responding to webhook requests within the time limit set in the Documentation;
• keeping your Registrations up to date, including removing Registrations you no longer need.

If your endpoint does not accept a webhook request, we will retry it as described in the Documentation. We may pause webhooks to an endpoint that repeatedly fails, and we will inform you if we do. We cannot guarantee that every webhook is delivered, and you should use the API to check for Alerts you may have missed.

11. MCP server

If your Plan includes the MCP server, you may connect it to AI assistants and agents that you operate or use for your business. You are responsible for the configuration of these assistants, for the instructions you give them and for the answers they give to your End Users, including any changes to Alert Data they make. The conditions of sections 7, 8 and 9 apply in the same way to Alert Data obtained through the MCP server, including the obligation to keep attribution where Source Content is shown.

12. Changes to Travel Alerts and the API

We may update Travel Alerts and the API at any time. We aim to keep the API backward-compatible. If we make a change that is not backward-compatible, such as removing a field or an endpoint, we will inform you at least 90 days in advance, except where a shorter period is necessary for security reasons, to comply with the law or because a Source has changed its conditions or stopped providing its information.

13. Availability and support

We aim to keep Travel Alerts available at all times and to monitor it continuously. Planned maintenance will be announced in advance where possible. Unless your Plan or Order includes a specific service level, we do not guarantee any particular availability, response time or delivery time. Where your Plan includes a service level, its terms and any remedies are described in your Plan or Order.

Support is provided by e-mail at business@tripomatic.com during business days in the Czech Republic, with the scope set out in your Plan.

14. Acceptable use

You must use Travel Alerts in accordance with these Terms, the Documentation and applicable law. You must not:

• use Travel Alerts for any unlawful purpose or in a way that infringes the rights of others;
• interfere with or disrupt Travel Alerts, including by sending excessive requests, load testing or security testing without our prior written consent;
• attempt to gain unauthorised access to Travel Alerts or to data of other customers;
• reverse engineer, decompile or try to obtain the source code of Travel Alerts, except where the law expressly permits this;
• use Travel Alerts to monitor, track or profile identifiable individuals;
• misrepresent the origin of Alert Data or remove proprietary notices from it.

15. Data protection

Travel Alerts is designed so that you do not need to send us any personal data about your End Users. A Registration should contain only your own reference identifier, locations and a time period. You must not include names, e-mail addresses, phone numbers, booking references or other information from which we could identify a person in identifiers, locations or other data you send to Travel Alerts. We recommend sending locations only as precisely as you need to receive relevant Alerts, for example the destination or the hotel area rather than an exact address.

We delete Registrations within 30 days after the end of their time period, or earlier when you delete them.

We process the personal data of your contact persons, such as the names and e-mail addresses you give us for communication and billing, as a controller in accordance with our Privacy Policy. If, despite the above, you need us to process personal data on your behalf, we will agree a data processing agreement with you before you send such data.

16. Intellectual property and feedback

Travel Alerts, the Documentation and all software, structures, compilations, Generated Text and other materials we create as part of Travel Alerts are owned by Tripomatic or its licensors and are protected by copyright, database rights and other laws. Source Content remains the property of its Sources.

If you send us suggestions or feedback about Travel Alerts, we may use them freely without any obligation to you.

Unless you tell us otherwise, we may name you as a customer of Travel Alerts and display your logo in our marketing materials.

17. Confidentiality

Each party must keep confidential any non-public information it receives from the other party in connection with Travel Alerts, such as API keys, prices in an individual Order, technical details and business information, and use it only for the purposes of these Terms. This obligation does not apply to information that is or becomes public without a breach of these Terms, that the receiving party already lawfully had, or that it must disclose by law. This obligation continues for 3 years after the end of your use of Travel Alerts.

18. Warranties

We will provide Travel Alerts with reasonable care and skill. Apart from this, and to the maximum extent permitted by law, Travel Alerts and Alert Data are provided “as is” and “as available”, and we give no other warranties, express or implied, including warranties of accuracy, completeness, timeliness, merchantability or fitness for a particular purpose. We do not control the Sources and are not responsible for the content they publish.

19. Limitation of liability

To the maximum extent permitted by law:

• we are not liable for any indirect or consequential damage, loss of profit, loss of revenue, loss of business, loss of data or damage to reputation;
• we are not liable for any damage resulting from the content of Alerts, from errors, delays or omissions of Sources, from the matching of Alerts to locations, from Generated Text or from decisions made based on Alert Data;
• our total liability arising out of or in connection with Travel Alerts and these Terms is limited to the fees you paid us for Travel Alerts in the 12 months before the event giving rise to the liability, and, where no fees were paid, to EUR 100.

Nothing in these Terms limits or excludes liability for damage caused intentionally or through gross negligence, for harm to a person’s life, health or physical integrity, or any other liability that cannot be limited or excluded under applicable law.

20. Your responsibility towards third parties

You will compensate us for any damage, costs and reasonable legal fees arising from claims of your End Users or other third parties, including Sources, that result from your Customer Application, from your breach of these Terms, in particular sections 7, 8 and 14, or from your violation of applicable law. We will inform you about such a claim without undue delay and allow you to take part in its handling.

21. Term, cancellation and termination

Your subscription continues for the billing period of your Plan and renews automatically for further periods of the same length, unless you or we cancel it. You can cancel your subscription at any time by e-mail to business@tripomatic.com; the cancellation takes effect at the end of the current billing period. An Order for a fixed term ends as set out in the Order.

We may cancel a subscription with at least 30 days’ notice, for example if we stop offering Travel Alerts. In that case, we will refund any prepaid fees for the period after Travel Alerts ends.

Either party may terminate the subscription with immediate effect by written notice if the other party materially breaches these Terms and does not remedy the breach within 14 days after being asked to do so. We may also suspend your access to Travel Alerts immediately, without prior notice, if this is necessary to prevent damage to Travel Alerts, other customers or third parties, or if you seriously breach sections 3, 7, 8 or 14. We will inform you about the suspension and its reason without undue delay.

When your subscription ends, your right to use Travel Alerts ends, your API keys stop working and your Registrations are deleted. You must stop using Alert Data and delete any stored copies within 30 days, except where you are required by law to keep them. Sections that by their nature should continue to apply, in particular sections 6, 16 to 20 and 23, remain in effect.

22. Changes to these Terms

We may update these Terms from time to time, for example to reflect changes to Travel Alerts, our Sources or applicable law. We will publish the updated Terms on this page and, if the changes are material, inform you by e-mail at least 30 days before they take effect. If you do not agree with the changes, you may cancel your subscription before they take effect. If you continue to use Travel Alerts after that date, you accept the updated Terms. Changes required by law or by a Source may take effect sooner.

23. Governing law and disputes

These Terms and all relationships arising from them are governed by the law of the Czech Republic, in particular Act No. 89/2012 Coll., the Civil Code. The United Nations Convention on Contracts for the International Sale of Goods does not apply. Because Travel Alerts is provided only for business use, the parties exclude the application of sections 1799 and 1800 of the Civil Code.

The parties will first try to resolve any dispute amicably. If they do not succeed, the dispute will be decided by the competent court in Brno, Czech Republic.

24. Final provisions

If an individual Order contains provisions that differ from these Terms, the Order takes precedence. Where the Documentation and these Terms differ, these Terms take precedence.

You may not assign your rights or obligations under these Terms to another party without our prior written consent. We may assign them to a company that takes over Travel Alerts.

If any provision of these Terms is found invalid or unenforceable, the remaining provisions remain in effect, and the invalid provision will be replaced by a valid one that comes closest to its purpose. A failure to enforce any right under these Terms does not mean a waiver of that right.

Neither party is liable for a failure to fulfil its obligations caused by events beyond its reasonable control, such as natural disasters, failures of Sources, internet or hosting providers, or actions of public authorities.

Notices under these Terms may be sent by e-mail: to us at business@tripomatic.com and to you at the e-mail address you gave us for this purpose.

Contact

If you have any questions about these Terms or Travel Alerts, write to us at business@tripomatic.com.