Terms & Conditions
On this page
These terms govern the use of Maplith — the app at app.maplith.com, the MCP endpoint it serves, the connectors and the hosted agent — between Maplith and the organisation on whose behalf you use it ("the customer", "you"). "Maplith" and "we" mean Maplith ApS, CVR 46843290, Ørnekulsvej 15, 2920 Charlottenlund, a Danish private limited company.
These documents make up the agreement:
- these terms;
- the Data Processing Agreement ("DPA"), which prevails over these terms where they concern personal data;
- the Processing and security description ("the description"), which the DPA refers to and which says in detail how the service processes data today;
- the sub-processor list.
Section 13 says how each of them may change.
1. What Maplith is
1.1 Maplith reads export files from the systems a company already runs and builds a map of its data landscape: business objects, their fields, relations across systems, processes, metrics and findings. The map is served in the app, to an assistant in the app, and to your own AI agents over MCP. Maplith keeps metadata about your data, not copies of your records; the description says exactly what it keeps.
1.2 Optional features include connectors that fetch exports directly from a system, signals and rules that tell you when something in the map needs attention, actions your agents take within policies you set, and a hosted agent that comments on, and proposes changes to, issues in GitHub repositories you connect. The service changes and grows; section 11 covers that.
1.3 Maplith is built for businesses. It is not offered to consumers, and by using it you confirm that you do not act as a consumer.
2. Your account
2.1 By creating a workspace you confirm that you act on behalf of an organisation and have the authority to bind it to these terms.
2.2 You are responsible for the people you invite, for the roles and access you give them, and for keeping your sign-in methods secure. Sign-in uses one-time links by email or, if you choose, a Google, Microsoft or GitHub account. Any member can add two-factor authentication to their account.
2.3 Tell us at once at [email protected] if you suspect that an account or an agent key has been compromised.
3. Your data
3.1 You decide what to upload or connect, and you are responsible for having the right to do so. That includes a lawful basis for any personal data in it and, where the data concerns other people, informing them as the GDPR requires. Maplith cannot do that for you.
3.2 The DPA applies whenever your exports contain personal data. The description says which providers receive your file content and where they process it. Today that includes a model provider in the United States. What your exports contain is your decision, including special categories of personal data, data about criminal convictions and Danish CPR numbers. Maplith handles every upload the same way, so leave out what you do not want processed, or use the data-handling settings the description lists before you build (DPA clause 7.5).
3.3 Uploaded export files are deleted after the build that reads them. The map is what remains, and it may contain incidental personal data quoted from your files.
3.4 Maplith does not use your data to train models, does not use it to build another customer's map, and does not use it for its own purposes (DPA clause 7.2).
3.5 You connect only systems and repositories you are entitled to connect. The hosted agent works in private repositories only.
4. Free use
4.1 Your first map is free: no payment, no card, no subscription, and no obligation to buy anything afterwards.
4.2 Free use is bounded by fair-use caps, such as the number and size of files and scans per day, rather than by a charge. The current caps are in the documentation. Maplith may change them.
4.3 A free workspace is a real customer relationship, not a trial with an expiry date. Section 8 says what happens to a workspace no one uses.
4.4 Maplith may refuse or stop builds that appear automated, abusive or outside the intended use, and may limit the number of free maps per organisation.
5. Paid plans and payment
5.1 No paid plan is available today, and no customer is charged.
5.2 If paid plans are introduced, they are announced, with their prices, invoicing and payment terms, as a material change under section 13 before anything is charged.
6. Acceptable use
6.1 Do not try to access another customer's workspace or data, to probe or bypass access controls, or to overload the service. Rate limits apply to every agent key.
6.2 The public sandbox key is for evaluating Maplith against fictional data only.
6.3 Do not resell Maplith or offer it to third parties as your own service without a written agreement. Consultants use their clients' workspaces as members, with the roles their clients give them.
6.4 Do not use the hosted agent in repositories you do not control.
6.5 Do not upload content you do not have the right to process, or that is unlawful.
7. Agents, the assistant and automated actions
7.1 An agent key is read-only unless an admin of your workspace chooses otherwise. Choosing a policy that lets a key or an integration act — with approval, on its own, or by proposing changes — is your instruction, and the actions taken under it are yours. Maplith records them and enforces the limits you set. Maplith's hosted agent never merges a pull request. Maplith does not review the actions for you.
7.2 The in-app assistant acts as the member who uses it and sees only what that member may see. It can explain the map and propose changes. A change applies only when a member whose role allows it applies it.
7.3 The map, its findings, its metrics and the assistant's answers are produced with a language model. They can be incomplete or wrong. Where the product shows how far something can be trusted (verification rates, caveats, evidence), use that, and check before you act.
8. What happens to a workspace no one uses
8.1 A free workspace stays for as long as it is used. If no member signs in for 12 months, Maplith deletes the workspace with its map.
8.2 Before that, the workspace admins receive recurring reminders by email stating how long the workspace has been inactive and the date on which it will be deleted. Any sign-in resets the clock, and you can export the map before the date. No workspace is deleted for inactivity without those reminders.
8.3 You may ask for deletion earlier at any time, and it is carried out as the DPA describes.
9. Intellectual property
9.1 Your data stays yours: the exports you upload, the systems they come from, and everything in them remain your property and never become Maplith's. That includes the values, names, evidence and other content from your files that appear inside the map.
9.2 Maplith owns the software, the engine, the method by which maps are built, the model of how a map is structured, and all improvements to them.
9.3 The map — the structure Maplith derives (objects, fields, relations, processes, metrics and findings) in the form Maplith generates it — is owned by Maplith to the extent intellectual property rights exist in it, subject to your rights in your data under 9.1. Maplith grants you a non-exclusive, non-transferable, royalty-free licence to use the map for your own internal business purposes for as long as your workspace exists. That covers browsing it, exporting it, and serving it to your agents and to consultants working for you. You may keep and use exported copies for the same purposes without time limit after the workspace ends. You may not sell the map or provide it to third parties as a product or as part of a competing service.
9.4 Maplith uses the map only to provide the service to you, never for its own purposes, and discloses it to no one except the sub-processors that deliver the service.
9.5 Maplith may use aggregated operating statistics that identify no one, such as file counts, run durations and token counts, to operate and improve the service. Your file content and your map are never used to build another customer's map or to train models.
9.6 Feedback you give about the service may be used without obligation or attribution.
10. Confidentiality
10.1 Each party keeps confidential the other party's non-public information that it receives under these terms, uses it only to perform under these terms, and protects it with at least the care it applies to its own confidential information. For Maplith this covers your exports, your map, your connector credentials and everything Maplith learns about your business from them. For you it covers non-public information about Maplith's software and pricing.
10.2 The obligation does not apply to information that is public without a breach of these terms, that a party already held lawfully, or that a party must disclose by law or court order. In the last case, it tells the other party first where the law allows.
10.3 The obligation lasts for five years after the relationship ends and, for personal data and trade secrets, for as long as the information stays confidential.
11. Availability, support and product changes
11.1 Maplith is operated by one person and an automated setup. These terms give no uptime, response-time or support commitment. Service messages go to your account email, and support is by email at [email protected].
11.2 The service changes continuously, and release notes appear in the app. Maplith may add, change or withdraw features. A feature is withdrawn with reasonable notice, or at once where security requires it. A new feature that processes personal data does so within the DPA. The description is updated, with a changelog entry, before or when the feature goes live.
12. Warranties and liability
12.1 The service is provided as it is and as available. Maplith does not warrant that the map is complete, correct or fit for a particular decision: the model can be wrong, and the product says so where it can. The map is decision support, not advice.
12.2 While the service is provided free of charge, and to the fullest extent permitted by Danish law, Maplith is not liable for any loss arising from its use. That includes indirect and consequential loss, loss of data, loss of profit and business interruption. This exclusion does not apply to liability the law does not allow to be excluded: liability for gross negligence or wilful misconduct, liability under the Danish Product Liability Act, and the parties' liability under the DPA and Article 82 GDPR. Liability terms for paid plans, including any cap and insurance, are set before the first charge (section 5.2).
12.3 You indemnify Maplith against third-party claims, including claims by data subjects and supervisory authorities, to the extent they arise from content you uploaded or connected without the right to do so, or from your breach of section 3 or 6. Maplith tells you promptly of any such claim, lets you conduct the defence, and does not settle without your consent.
13. Changes to the agreement
13.1 Three kinds of change. Maplith may change these terms, the DPA, the description and the sub-processor list. How a change takes effect depends on its kind:
- (a) Material change — a change to these terms or the DPA that reduces your rights or raises your obligations. That includes introducing charges, adding a processing purpose outside DPA Annex II, lowering the measures in DPA Annex III, and changing liability, governing law, venue or the licence in section 9.3.
- (b) Other changes to these terms or the DPA — clarifications, corrections, and changes in your favour.
- (c) Changes to the description and the sub-processor list — governed by DPA clauses 6 and 7.7. Some take effect only after advance notice, with a right to object. None needs your acceptance.
13.2 Material changes are announced in the app and by email to the owners and admins of your organisation at least 30 days before their effective date. A material change takes effect for your organisation when an owner or admin accepts it in the app. You may accept as soon as it is announced. Until you accept, the version you accepted continues to apply. Builds that a person or an agent starts wait for acceptance. Features that need the new version stay off for your organisation. If you do not accept a material change, you may terminate under section 14 before it takes effect, without penalty. If your organisation has not accepted a material change 60 days after its effective date, Maplith may end the service under section 14.2.
13.3 A material change required by law may take effect sooner, with as much notice as the law allows. So may a change that is only in your favour.
13.4 Other changes to these terms or the DPA are announced in the app and take effect on the date stated in the announcement, which is never earlier than the announcement itself.
13.5 Records. Acceptance is recorded in the app — the version, the accepting user, the organisation and the time — and confirmed to you by email. The record, and the exact text you accepted, are available under Settings → Organisation → Legal. Every version of every document listed in the preamble is kept with its date, and the description and the sub-processor list each carry a dated changelog.
14. Term and termination
14.1 These terms apply from your first use of Maplith until terminated. You may stop using Maplith at any time. You can delete a workspace yourself under Settings → Data. For an organisation or an account, ask Maplith, and it is carried out as the DPA describes.
14.2 Maplith may terminate a free workspace with 30 days' notice by email to its admins. Maplith may suspend or terminate access at once for a breach of section 6, for non-payment once payments exist, or where the law requires it, with notice where the circumstances allow. Before a termination by Maplith takes effect you can export your map, unless the termination is for a breach that makes that inappropriate.
14.3 On termination, Maplith deletes or returns your data as the DPA describes. Sections 3, 9, 10, 12, 15 and 16 survive termination.
15. General
15.1 Entire agreement. The documents listed in the preamble are the whole agreement between us about Maplith. They replace any earlier oral or written arrangement, including any arrangement made before Maplith ApS was registered.
15.2 Assignment. You may not transfer these terms without Maplith's written consent, which is not unreasonably withheld. Maplith may transfer them to a successor of its business, with notice to you.
15.3 Force majeure. Neither party is liable for a failure caused by circumstances beyond its reasonable control. That includes outages at the providers on the sub-processor list that the party could not reasonably have prevented. Payment obligations are not excused.
15.4 Notices. Notices to Maplith go to [email protected]. Notices to you go to your organisation's contact email or, failing that, to the workspace admins' account emails.
15.5 Severability. If a provision is invalid, the rest stays in force, and the provision is replaced by a valid one that comes closest to its purpose.
15.6 No waiver. Not enforcing a provision is not a waiver of it.
15.7 Language. These terms are written in English. Where a Danish translation is provided, the English version governs.
16. Governing law and disputes
Danish law applies, without regard to its conflict-of-law rules. Disputes the parties cannot settle by negotiation go to the Danish courts, with the Copenhagen City Court (Københavns Byret) as the agreed venue of first instance. Nothing in this section prevents either party from seeking interim relief in any competent court.