Most SaaS and outsourcing contracts signed with a Montenegrin counterparty are a foreign template with the counterparty's name typed into it. That works for most of the document. It stops working in four places: the governing law clause, the forum clause, the IP assignment, and the data processing annex. Each of those is answered partly by Montenegrin law no matter what the template says, and in each case the default is not what the template assumes.
This page is about those four clauses, with the provisions that decide them. It assumes you are the company signing — a foreign buyer engaging a Montenegrin development shop, a vendor selling software into Montenegro, or a group papering services between its own entities.
Clause 1 — governing law: broad autonomy, with one hard edge
Montenegro's conflict rules sit in the Zakon o međunarodnom privatnom pravu (Private International Law Act), Sl. list CG 1/2014, with corrections at 6/2014 and 11/2014, an amendment at 14/2014 and a further change by another statute at 47/2015. It is a close transposition of the European approach, and Article 38 gives you what you expect: the contract is governed by the law the parties choose; the choice must be express or appear clearly from the contract's terms or the circumstances; it may cover the whole contract or only part of it; and it can be changed at any time.
The hard edge is Article 38(3). Where all the other elements of the situation at the time of the choice are connected to one state and the parties choose the law of a different state, the choice cannot exclude the mandatory rules of that first state. A Montenegrin customer, a Montenegrin supplier, performance in Montenegro and payment in euro to a Montenegrin account is not made an English-law contract by an English-law clause; it is a Montenegrin contract with an English-law overlay that stops where Montenegrin mandatory rules begin.
If you say nothing, Article 39(1)(2) decides it: a contract for the provision of services is governed by the law of the state of the service provider's habitual residence. So silence favours the Montenegrin development shop and disfavours the foreign SaaS vendor — in each case the provider's own law. Article 39(2) falls back to characteristic performance where the list does not fit, and Article 39(3) lets a manifestly closer connection displace the result.
One limit applies whether or not you drafted carefully. Under Article 42, a consumer contract is governed by the law of the consumer's habitual residence where the trader carries on business in, or directs activity to, that state and the contract falls within that activity — and a choice of another law cannot deprive the consumer of the protection of mandatory rules that would otherwise apply. If you sell a subscription product to individuals in Montenegro, your governing law clause does not fully displace Montenegrin consumer protection.
Clause 2 — forum: allowed, exclusive by default, and easy to lose
Article 104 permits the parties, in matters they may freely dispose of, to agree on the jurisdiction of a foreign court for an existing or future dispute from a defined legal relationship, provided there is no exclusive jurisdiction of a Montenegrin court. Article 107 confines exclusive jurisdiction to cases expressly prescribed by law, so an ordinary IT contract is not caught — unlike a contract about Montenegrin real estate, where Article 119 reserves rights in rem and leases to the Montenegrin courts.
Two features of Article 104 and its neighbours change how the clause should be drafted.
The foreign court's jurisdiction is exclusive by default. Article 104(2) provides that jurisdiction agreed under Article 104(1) is exclusive unless the parties have agreed otherwise. Under many templates a bare "the courts of X shall have jurisdiction" is read as non-exclusive; in Montenegro the default runs the other way. If you wanted the option of suing in Montenegro where the assets are, say so expressly.
A click-through clause can satisfy the form requirement. Article 105 requires the agreement to be concluded or confirmed in writing, in a form matching practices established between the parties, or in international trade in a form matching a widely known and regularly observed usage. And Article 105(2) deems the agreement to be in writing where it is concluded by electronic communication means that provide a durable record of it. Online terms are therefore not automatically defective on form — provided your systems actually retain the record.
You can submit by accident. Under Article 106, jurisdiction of a Montenegrin court can be established by the defendant's consent, and consent is deemed given if the defendant files a defence or an objection to a payment order, or takes part in argument at the preparatory or first main hearing without contesting jurisdiction, or files a counterclaim. If your Montenegrin entity is sued and local counsel answers on the merits, the forum clause has been spent.
Finally, the flip side: Article 123 gives the Montenegrin courts jurisdiction in contractual disputes where the obligation was or should have been performed in Montenegro, and for services deems that to be the place where the services were or should have been provided. And Article 124 protects consumers domiciled in Montenegro: they may sue the trader there, the trader may sue them only there, and a jurisdiction clause departs from that only if concluded after the dispute arose, or if it gives the consumer additional forums, or if both parties were domiciled in the same state at the time of contracting.
The enforcement test that decides whether the forum clause was worth anything
A judgment from your chosen court has no effect in Montenegro until it is recognised. Article 141 says so, Article 142 requires a certificate of finality, and Articles 143 to 147 set the refusal grounds: breach of the right of defence, exclusive Montenegrin jurisdiction, res judicata, and public policy. There is no general reciprocity requirement — reciprocity appears only in Article 140, on exemption from litigation costs.
The one to read before signing is Article 145. It refuses recognition where the foreign court's jurisdiction rested on a basis that Montenegrin rules do not recognise — a check on exorbitant jurisdiction that operates even where the parties agreed to that court. The practical test at signature is whether you can name the connection between the dispute and the chosen forum in terms a Montenegrin court would recognise. A clause pointing at a jurisdiction with no connection to either party or to performance is worth less than it looks.
That is why the dispute clause is often better solved by arbitration than by a foreign court, and why the analysis differs — we set out that comparison, including Montenegro's reservations to the 1958 New York Convention, in our note on arbitration or court in a Montenegrin contract. The commercial reservation matters here: a business-to-business software contract will normally qualify, which is precisely the reason arbitration works better for IT contracts than for consumer-facing ones.
Clause 3 — IP: the sweep-up assignment does less than you think
Montenegro's Zakon o autorskom i srodnim pravima, Sl. list CG 37/2011, 53/2016, 145/2021 and 48/2024, allocates ownership by category, and the categories do not behave alike.
| What was created | Default ownership | Reverts? |
|---|---|---|
| Computer program, in employment or under a commissioning contract (Art. 115) | Employer or commissioning party, unlimited and exclusive | No |
| Database or collective work, in employment (Art. 101(2)) | Employer, unlimited and exclusive | No |
| Any other work created in employment (Art. 100) | Employer, exclusive — but only for five years from completion | Yes, to the author |
| Any other work commissioned from a contractor | Only what the assignment clause actually specifies | n/a |
Three consequences follow.
The code is the easy part. Article 115 vests all economic and other rights in a computer program in the employer or the commissioning party, unlimited and exclusive, unless otherwise agreed — and it covers commissioned work, not only employment. For the software itself, Montenegrin law is more generous to the buyer than many assume.
Everything around the code is the risk. Article 100 deems a work created in employment assigned to the employer for five years from completion, after which Article 100(2) has the rights revert to the author, who under Article 100(3) must re-assign on request against appropriate remuneration. UI artwork, documentation, training material, marketing copy and design assets produced by a Montenegrin team therefore have a clock on them that the source code does not.
A one-line assignment is not enough. Article 74 of the copyright act requires an assignment to specify the right assigned, whether it is exclusive or non-exclusive, the territory, the period, and whether it may be further assigned. Article 75 then construes strictly: assigning one economic right does not carry the others; assigning the reproduction right does not include digital fixation under Article 21 of that act; and assigning a right does not include the remuneration rights under Articles 34, 36 and 37 of that act — in each case unless the Act or the contract says otherwise. A common-law "all right, title and interest" sweep is not how this statute reads a contract.
There is a cross-border twist that catches groups with Montenegrin engineers. Under the Private International Law Act, Article 35 refers the existence, validity, scope, ownership, transferability, duration and infringement of copyright to the law of the state where protection is sought, and Article 36 provides that the law governing the employment contract also governs who holds an intellectual property right whose subject matter arose within that employment. So who owns your Montenegrin developers' output is decided by their employment law and by the law of the place of protection — not by the governing law clause in the master services agreement. Fixing the MSA does not reach either layer; the employment contracts and the local assignment do.
Clause 4 — the data annex is not a formality here
Two provisions turn the data processing annex from boilerplate into a gating item. Under Article 16 of the data protection act, the controller may entrust processing to a processor only by a written contract governing their mutual rights and obligations and in particular the processor's duty to act on instructions, only to a processor that meets the conditions for technical, staffing and organisational protection measures, and the processor must destroy or return the data after processing.
Then Article 74(1)(5) of the same act makes it a misdemeanour for a controller to entrust processing to a processor that is not registered for the activity of personal data processing, or that does not meet those protection conditions. That registration requirement has no GDPR analogue and it is a question to resolve before signing an offshore processing arrangement, not after.
The transfer layer sits on top. Article 41(3) of the data protection act treats a transfer made in order to entrust processing operations as requiring the supervisory authority's consent, carving out only transfers to the EU, the EEA and adequacy-listed states — a narrower carve-out than the nine exemptions that answer the general rule. We set out that tension, and what to do about it, in our note on cross-border data transfers, and the filing mechanics in what a foreign company must actually file.
One clause in your standard terms is void
If you license software into Montenegro, check the reverse-engineering language. Article 113(2) of the copyright act entitles a person lawfully entitled to use the program, without the author's permission, to make one back-up copy where needed for use, and to observe, study and test the functioning of the program to determine the ideas and principles underlying it. Article 114 permits decompilation for interoperability, on stated conditions. Both articles end the same way: contractual provisions restricting those rights, or contrary to them, are null and void (Articles 113(4) and 114(4)).
A blanket "the customer shall not decompile, disassemble or reverse engineer the software under any circumstances" is therefore unenforceable in Montenegro to the extent it cuts across those provisions. It is not fatal to the contract, but it is worth knowing that the clause you are relying on does not do what it says.
Before the next template goes out
Four checks, in order. Name the governing law and ask whether Article 38(3) leaves it intact for this deal. Make the forum clause say whether it is exclusive, and be able to name the connection that Article 145 will look for. Split the IP clause by category, specify the five elements Article 74 requires, and put the assignment in the employment contracts as well as the MSA. And treat the data annex as a licensing question, not a schedule.
If you are negotiating or reviewing a SaaS, development or outsourcing contract with a Montenegrin party, send us the draft, the employment or contractor templates behind it, and the data flow, and we will tell you which clauses survive contact with Montenegrin law and which need rewriting. This work sits in our IT and technology practice, alongside AI and data protection. The regime behind the data annex is in why Montenegro is not a GDPR country; if the counterparty entity is still being formed, start with company formation in Montenegro.
Statutory references are to the Zakon o međunarodnom privatnom pravu as promulgated on 23 December 2013 and published in Sl. list CG 1/2014, read together with the correction in Sl. list CG 6/2014; the gazette chain reported for that law also includes 11/2014, 14/2014 and 47/2015, which we have not separately checked against the articles cited here. Copyright references are to the consolidated Zakon o autorskom i srodnim pravima (Sl. list CG 37/2011, 53/2016, 145/2021, 48/2024) and data protection references to the consolidated Zakon o zaštiti podataka o ličnosti (Sl. list CG 079/08, 070/09, 044/12, 022/17, 077/24). Read on 25 August 2026. Translations are ours. General information on Montenegrin law, not advice on a specific contract.
