Terms of service

Provider: Terranes Noro, a sole proprietorship (Einzelfirma) under Swiss law, Hauptstrasse 56, 8775 Luchsingen, canton Glarus, Switzerland, business identification number CHE-211.497.373, VAT number CHE-211.497.373 MWST — "we", "us". Customer: the organization or individual holding the account — "you". Contact: privacy@terranes.app.

---

1. Who these terms are with

An account belongs to an organization. The person who creates it is its owner and accepts these terms on the organization's behalf; if you do that for an employer, you are stating that you may bind it.

Seats are sold to businesses. Solo is the one product sold to individuals buying for private purposes, and §9 sets out the rights that apply when you buy it as a consumer. A company buying one seat is making a business purchase and carries none of §9, even though the price after tax is the same. Where §9 and any other section disagree, §9 wins for consumers — that is the effect of consumer law regardless of what a contract says, so the terms say it rather than leave it to be discovered.

You must be 18 or older to open an account.

2. The service, and what we do not promise

We provide a hosted project management service: a project repository, tasks, files, reporting, and the optional modules described on the pricing page.

We do not offer a service level agreement at any current plan level, and we would rather say so than leave it to silence. We run the service with reasonable care, we will not deliberately withhold access to your data in any billing state (§6), and beyond that we make no availability or fitness-for-purpose commitment. If an SLA is later offered, it will be a separate written commitment, not an inference from these terms.

One thing we do commit to, and state here so that it is written rather than inferred: when your organization's paid subscription starts, one migration call is included — a person from us, on a call, on your own spreadsheet, until your project is imported. One call, once per organization, at no charge, on every paid plan. It is not part of the free trial (§7). It is arranged by writing to privacy@terranes.app. We take part either as a guest of that one project, at your invitation and with the access you choose, until you remove us — or over a screen-share, with you at the keyboard. We have no other way into your account, and we have built none. It is not a service level, a response time or a support plan, and it does not change the paragraph above.

3. Plans and prices

Prices are quoted per month unless stated, in EUR and CHF as two independent price lists. They are not converted between currencies at any exchange rate: the EUR price is the EUR price and the CHF price is the CHF price. Your currency is fixed at your first invoice and cannot be changed afterwards.

You pay for the people on your team. One seat or fifty — there is no minimum and no maximum.

The fiftieth seat costs what the first one costs. There is no minimum team size, no pack you have to buy into, and no tier you have to reach. If you are one person you pay for one seat. If you grow to forty you pay for forty, at the same rate. We say this plainly because the opposite — being made to buy two, three or five seats before you can start — is the single thing customers tell us they most resent about the tools we replace.

Solo and a business seat are the same price. Solo is shown at 15 because consumer law requires a price shown to an individual to include VAT; a business seat is shown at 12 because business prices are quoted net. Once tax is applied they come to the same thing.

The billing basis is staff membership, not activity and not usage. It is never "per active user": we do not measure whether someone logged in this month, and your bill does not go up or down because they did. Guests — clients, contractors, auditors and other invited external people — are free, are never counted, and there is no cap on how many you have. There is a limit on what one guest can do, and §4 states it.

A Plus licence belongs to a person. You buy as many as you need, and an owner hands them out, moves them and takes them back. A licence you have not given to anyone is still billed — you bought it. A licence can be moved to a different person once a week; that limit exists so that a handful of licences cannot cover a whole department by rotation. Someone whose licence is taken away keeps fourteen days in which their Plus module data stays readable and exportable but not writable, and after that it stays readable and exportable indefinitely — it is never hidden and never deleted (§6). Meeting transcripts are the one exception, and it is not a licence rule: they expire on the retention clock in §8a whether or not anybody still holds a licence, because keeping a recording of several people's voices alive on the strength of a billing state would be the wrong reason to keep it. The decisions and tasks confirmed out of those meetings are ordinary project content and stay, like everything else. Each person still switches individual modules on and off for themselves at no charge.

Founding price. Organizations that subscribe while the founding window is open — it closes when 500 organizations have taken it, or on 31 March 2027, whichever happens first — pay 6 per seat per month, half the list price. It applies to every seat they hold and every seat they add later; it is monthly only, with no annual option. They keep it for as long as the subscription runs. It is not combinable with a discount code. We will not edit it, migrate it, or price it away later; that is the whole point of it.

Everything an organization buys arrives on one invoice with one billing period.

4. Why your bill changes

Your bill follows the size of your team. Adding a colleague as staff adds a seat and adds its price; removing them removes it. Inviting a guest — a client, a supplier, an auditor — never changes what you pay, however many you invite.

What a guest can do. A guest reads and comments on as many of your projects as you invite them to, free, with no limit and no time bound. A guest can also be given editing rights on up to two of your projects — enough for a contractor or a planner working on a job with you. Someone who needs to edit across more than that is working as part of your team, and we ask you to add them to it. A guest is never a project administrator, never opens a project, and never holds a Plus licence. We do not count your guests, cap them, or ask you about them.

People on your own domain. If you have verified an email domain with us, an address on it cannot be added as a guest — someone at your own company is a colleague. Your business owner can mark a specific person as genuinely external if your group shares a domain.

Adding someone never triggers a charge to your card. A seat added mid-period is prorated onto your next invoice. We do not take a payment at the moment you invite a colleague, because deciding whether to add someone to a project should not be a decision about money.

Nobody can join your organization without an owner acting. There is no way for a person to add themselves, and no domain, email address or sign-in method grants anybody membership. An owner invites, the person accepts, and the owner confirms. An earlier version of these terms described automatic joining by email domain; that no longer exists.

Every change to your seat count sends the account owners one email stating the new count and the new amount, with a link to dispute it within seven days. If you dispute it in that window we will correct the charge where it was not the result of an action on your side.

Plus licences work the other way round: they are bought and removed deliberately by an owner, and a licence you hold is billed until you remove it, whether or not anyone is using it.

5. Payment

Payment is by card through Stripe, which is our payment processor and handles all card data; we never see or store a card number. Subscriptions renew automatically for the same period until cancelled. Prices for business customers are shown net of VAT; consumer prices are shown inclusive of VAT (§9).

6. Non-payment, and what it does not do

A failed payment puts your organization into a 14-day grace period with a banner, and then into organization-wide read-only: every screen still loads, every CSV export still works, and nothing new can be created or edited. Paying restores writing immediately.

No billing state ever deletes, hides or withholds your data, and export works in every state including read-only. We treat the exit door as something that stays open, so non-payment is a restriction on writing, never a hostage-taking of what you already wrote.

The single exception in time, not in kind, is inactivity — §11.

7. Trial

The trial runs 30 days, requires no card, and includes the core product and every Plus module. From day 23 you will see a banner naming the Plus modules your organization actually uses, so the end of the trial is announced rather than sprung. When it ends without a subscription the organization becomes read-only under §6; nothing created during the trial is deleted or concealed.

8. AI narratives

Status reports may carry a narrative summary generated by an AI model. It is assistive text, generated only from the figures displayed alongside it, and nothing else in your account is used to write it. It is labelled wherever it appears, including in exports and on shared links.

You are expected to read it before you rely on it or send it to anyone, and a narrative that has never been opened in the editor cannot be shared externally. We give no warranty that a narrative is accurate. Narration is off unless somebody asks for it, on every path including scheduled reports, and the AI page explains how it works and how to keep it off.

Meeting notes are a separate and much wider use of AI, and §8a deals with them on their own rather than folding them in here.

8a. Meeting notes, recordings and consent

This section applies only if you switch on the meeting notes module. If you do not, nothing here happens.

Obtaining consent is yours, not ours. You decide which meetings are recorded or transcribed and who is in them. We hold the transcript on your instruction; we are not a party to your meetings and we are in no position to ask anybody's permission. Before a transcript is processed, a named person in your organization must confirm in the product that every participant has been informed of the recording. That confirmation is recorded against the meeting with their name, and it is a condition of use: without it the product processes nothing. Working around it — by confirming on behalf of people who were not told, for instance — is a breach of these terms and ends the module's availability to your organization.

This is a criminal matter, not only a contractual one. Recording a non-public conversation without the participants' consent is an offence in Switzerland under Art. 179ter of the Swiss Criminal Code and in Germany under § 201 StGB, and comparable provisions exist across the EU. The liability falls on the person who records. We say this plainly because the attestation above is a control, not a defence: it makes the obligation visible at the moment somebody is about to record, and it does not transfer anybody's criminal exposure to us.

Germany: your works council probably has to agree first. § 87(1)(6) BetrVG gives a works council co-determination over any technical system capable of monitoring employee behaviour or performance, and a note taker that assigns tasks to named people is inside that test whatever it is used for. If you have a Betriebsrat, get the agreement in place before you roll the module out — we publish a template you can start from, and we will hand it over on request. Austria's § 96(1)(3) ArbVG works similarly.

What we will not build, ever. There is no measurement of speaking time, no participation scoring, no meeting-frequency figure per person, and no ranking or productivity metric of any kind — in this module or anywhere in the product. This is published at /legal/what-we-track and it is a property of the product, not a setting you have to keep switched off.

What the module produces is a proposal. Decisions and action items are suggested and a person confirms them; nothing is written into your project by a model. Machine transcription is unreliable on Swiss German and other dialects — it mishears, and it sometimes invents sentences that were never said — so the confirmation step is the quality control, not a formality. We give no warranty that a transcript or a proposal is accurate, and a transcript is not a record of what was said in any evidential sense.

On Microsoft Teams we record nothing. Where your tenant produces its own transcript, we read that. Your tenant administrator can switch that access off at any time, and if they do, the module simply stops receiving transcripts.

Transcripts and audio are deleted on a clock. 90 days by default; you can shorten it, and the person who created a meeting can delete its transcript and audio at any time. The decisions and tasks that were confirmed out of a meeting survive the transcript — they are your project record, and once a person has stood behind them they no longer need the recording to be trustworthy. This deletion is deliberate and it is the one place where §6's promise that we never delete your content does not apply: it is stated retention, it is described in our retention schedule, and shortening it is in your hands while lengthening it is not.

9. If you buy Solo as a consumer

This section applies when you buy Solo as an individual, for purposes outside a trade or profession. It does not apply to anything an organization buys — including a single seat, which comes to the same price after tax and is a business purchase.

Price display. The Solo price shown to you includes VAT. Business prices — seats and Plus licences — are shown net of VAT.

Withdrawal. You have 14 days from concluding the contract to withdraw, without giving a reason. Because the service starts at once, at Checkout we ask you to expressly request that it begin immediately and to acknowledge that if you then withdraw, you pay in proportion to what you used up to the moment you told us. Both are recorded on your account. Withdrawing is a message to privacy@terranes.app; a model withdrawal form is available and no particular wording is required.

Cancellation. You can cancel from Plan & billing in at most two clicks, with no call, no email and no retention interview. After any initial term you can end the contract monthly.

Your local law survives. Nothing here removes a protection that the mandatory consumer law of your country of residence gives you.

10. Your data, ending the contract, and getting it out

Your project content is yours. As between us, you control it and we process it on your behalf; the Data Processing Agreement governs how, and it is the document that carries our privacy commitments.

Export works in every billing state, including trial, read-only and after cancellation. It is self-service and covers all of your data in CSV — we do not gate it behind a support request, because an export that needs our permission is not an exit.

When you cancel or your subscription ends, your data remains available for export for 30 days. After that it is subject to the retention schedule, and it is destroyed only in the circumstances §11 describes.

We destroy data only because somebody asked us to, and there are two ways to ask.

The first is an erasure request — yours by hand, or the automatic one in §11. It carries a 30-day cancellable window with a banner and a one-click cancel, and only then executes.

The second is purging a single file, and it is yours to use rather than ours. Archiving a file and deleting it both keep the file itself, so that either can be undone; neither frees the storage it occupies. A project admin may therefore purge a file that has already been deleted, which destroys the document itself. Purge also carries a 30-day window in which an admin can restore the file, and after that window the document is gone and we cannot recover it for you. What remains afterwards is a record that the file existed — its name, who uploaded it and when — so the project's history stays readable; the document is what goes. Only a project admin can do this, only to a file that is already deleted, and it is recorded in the project's activity log like any other administrative action. Invoices and tax records survive every erasure request because a legal obligation requires them to be kept for ten years; they sit with Stripe, not in our database. The retention schedule sets out the rest, including the honest limits: erasure cannot reach a name typed into a comment or buried inside an uploaded PDF.

11. Inactivity

An organization whose trial ended without a subscription, or which stopped paying and went read-only, has six months to come back. Any sign-in by an owner or staff member resets that clock.

We email every owner an export reminder at four months and at five. At six months the system files the same erasure request an owner would file by hand, which carries its own 30-day final notice with a cancel button. So: six months, then a 30-day final notice. Sign in at any point before it executes and nothing happens.

Personal accounts are not swept this way. An individual who holds no memberships keeps their account until they ask us to erase it.

12. Refunds

Cancelling mid-period is not refunded. The current period runs to its end and is not returned pro rata. Voluntarily deleting your account mid-period is not refunded either, for the same reason: the period is already invoiced and the deletion is your choice, not a failure of ours.

If you hold a personal Solo subscription and then join a company here, that subscription is cancelled — we close the charge before anything else happens, so you are never billed for a workspace you can no longer reach. The remainder of the period already paid for is not refunded. In practice most people never reach this: every account starts on the 30-day trial with full access and no card, so the ordinary path of signing up, working alone and then being invited into a company is free from end to end.

Two things sit outside the no-refund position. A consumer withdrawing under §9 pays only the proportional amount. And anything that looks like a billing mistake on our side — a seat charged that your own actions did not create, a double charge, a failed downgrade — we refund on request; there is no automated refund flow, deliberately, because a human reading the case is more accurate than a rule.

13. Changes to these terms and to prices

We change these terms only for a stated reason, and we tell you before we do.

Notice is 30 days, sent to the account owners, describing what changes and when it takes effect. The same 30 days apply to a change of sub-processor, which the DPA also states — the two documents deliberately carry one notice period rather than two.

If you object, you may terminate before the change takes effect and export everything under §10. Continuing to use the service after the effective date is acceptance. We do not treat silence as agreement to a change we did not tell you about.

Prices. A price change applies to a new billing period, never retroactively, and reaches you through the same 30-day notice. It does not apply to the founding price, which is permanent for whoever holds it, and it does not introduce a charge for guests, who are free and stay free.

Corrections that do not affect your rights or obligations — a typo, a clearer sentence, a new contact address — take effect when published.

14. Liability

Our total liability to you, for all claims arising in any twelve-month period, is capped at the fees you paid us in the twelve months before the event giving rise to the claim. We do not accept liability for indirect or consequential loss, lost profit, or lost data where the loss would have been prevented by your own export (§10).

That cap has a floor it cannot go under. Under Art. 100 of the Swiss Code of Obligations, an agreement excluding liability in advance for unlawful intent or gross negligence is void, and a court may also set aside an exclusion for ordinary negligence where the service is delivered under an official licence. So the cap above limits what we owe for ordinary failures; it does not limit what we owe if we act with gross negligence or intent, whatever this contract says. Mandatory consumer-law liability and liability for death or personal injury are likewise untouched. We would rather write a cap that is true than one that reads well and falls over at the first hearing.

Nothing in this section limits your rights under the DPA or under data protection law.

15. If we stop running the service

This service is built and operated by a very small company. If it stops, the reason is likelier to be us than the market, and you should know now what happens rather than find out in an email.

If we discontinue the service, you get 90 days' notice and a full export. Within that period the service stays in at least read-only condition, export stays self-service and free, we refund the unused part of any prepaid period, and we will make a reasonable effort to give you your data in a form that can be loaded elsewhere. We will not shorten this period for commercial convenience.

This is a deliberate answer to the risk that one person carries this product. It is not a promise that the service will run forever; it is a promise about how it would end.

16. Governing law and forum

These terms are governed by Swiss law, excluding its conflict-of-laws rules and the UN Convention on Contracts for the International Sale of Goods.

For business customers, the exclusive place of jurisdiction is the courts competent for our registered seat in Luchsingen, canton Glarus, Switzerland.

For consumers, that clause does not apply. Under the Lugano Convention a consumer may sue us in the courts of the country where they are domiciled, and may only be sued there; we do not ask a consumer to litigate in Switzerland and could not enforce it if we did. A consumer resident in the EU therefore keeps their home forum and the mandatory consumer law of their own country, and §9 keeps its priority.

17. The rest

If a clause is unenforceable, the remainder stands. We may assign these terms to a successor in a merger or sale of the business, and will tell you when we do. Our failure to enforce a term is not a waiver of it. The DPA, the retention schedule, the sub-processor list and the AI page form part of the agreement; where the DPA and these terms conflict on the handling of personal data, the DPA wins.