Terms of Service — Emet

Effective: 2026-09-15 · Technical claims verified against the running system on 2026-08-05.

These terms govern use of Emet, the computer-assisted translation platform operated by Hesed Assessoria em Software LTDA (“Hesed”, “we”) at emet.ing and app.emet.ing (and, for organisations onboarded before the Emet domains existed, at app.hesedtranslation.com), by the organisation that has signed up for it (“Customer”, “you”) and by the people you invite.

How you accept these terms. You accept them by ticking the box at signup and creating a workspace. We record the moment you accepted and the version you accepted; if we change these terms materially we tell you before the change takes effect (§11) and ask you to accept the new version.

Who you buy from, and which document covers what. Emet is sold through Paddle, which acts as the Merchant of Record. That splits the relationship across two documents, and it is worth knowing which is which:

• Paddle's Buyer Terms cover the purchase: taking payment, issuing the invoice, sales tax and VAT, renewals and cancellations, and the statutory withdrawal rights of consumers in the EU, EEA and UK.
• These terms cover the product: what Emet does, what you may do with it, who owns what, and what we do and do not promise about it.

Where the two genuinely conflict on the mechanics of payment, Paddle's govern. Refunds and cancellation are set out in our Refund & Cancellation Policy, which sits alongside Paddle's.

If a separately signed services agreement exists between us, that agreement governs and these terms fill the gaps.

1. What the service is

Emet is a translation workspace. You upload source documents; the platform segments them, produces a first-pass AI draft of each segment, and gives your translators and reviewers an editor in which to correct and approve that draft. It maintains a translation memory and glossary for you, runs automated quality checks, tracks progress and word counts, and exports the finished work in the format you supplied.

What it is not. It is not an unattended machine-translation service. The AI produces a draft; the platform is built on the assumption that a competent human translator reads and corrects every segment. §5 says what follows from that.

2. Your account and your people

You appoint an administrator, who invites everyone else and sets their role (manager, language manager, editor, reviewer). You are responsible for who you invite and for what they do with the access you give them.

Each person gets their own account. Do not share credentials — the platform records who translated, reviewed and approved every segment, and shared logins make that record worthless to you, not to us.

Security you control: anyone may enable two-factor authentication, and your administrator may require it for everyone in your organisation. What we do on our side is described in the Privacy Policy §7, including the two things we do not yet do.

Acceptable use. What you and your people may not do with Emet is set out in the Acceptable Use Policy, which forms part of these terms. It is short, and it is the basis on which we may suspend or terminate an account under §7.

Tell us promptly if you believe an account has been compromised.

3. Who owns what

Your content stays yours. Source documents, translations, translation memory, glossaries and style guidance you create or upload (“Customer Content”) remain yours. We claim no ownership of them and no licence beyond what is needed to run the service for you: to store, process, display them to your authorised users, and to transmit segment text to the AI providers listed in Subprocessors for drafting and quality review.

Nothing crosses between customers. Your translation memory is used to suggest matches within your own organisation and never for anyone else. No other customer's memory is used to draft your work. This is enforced in software, not just promised — see Subprocessors, final section.

We do not train on your content. We do not use Customer Content to train models of our own, and we select and configure AI providers on the requirement that they do not train on it either. Both providers, not one:

• Anthropic is used under their Commercial Terms, which state that Anthropic may not train models on customer content from the services. Their API deletes inputs and outputs within 30 days by default; if their trust and safety systems flag a request, that data can be held longer — see Subprocessors §2, where the exact periods are set out rather than glossed.
• Google is used on a paid, billing-enabled account, deliberately. Under Google's terms for unpaid services, free-tier prompts and responses are used to improve Google products and may be read by human reviewers. Paid-tier terms say the opposite. This is the one place where the requirement forced a configuration change, and that change is recorded in the software's own configuration with the date and the method used to verify it.

Both providers' terms were read on 2026-09-07. Provider terms change, and this paragraph is only as good as that date.

You warrant that you hold the rights to the material you upload, including any licence needed for source texts and reference translations, and that our processing it as described will not infringe anyone's rights.

Our platform stays ours. The software, its interface, and the translation rubric and quality-check logic that drive AI output are ours. You get a non-exclusive, non-transferable right to use them for the term. You may not resell access, or copy the rubric out of the platform for use elsewhere.

4. AI processing — read this one

You acknowledge and instruct us that:

• Your source text is transmitted to third-party AI providers in the United States — Anthropic and Google. This applies to every project and every language pair, and does not depend on where you, your translators or your readers are located: your content is stored in Brazil and leaves it for this processing. What is sent per segment is listed precisely in Subprocessors §2 and §3. It is the text and the rules for translating it; it is not your organisation's name, your users' names, your file names or your commercial data.
• This includes unpublished material. If your manuscripts are confidential or embargoed, this is the paragraph to take to your own stakeholders before you upload anything. We would rather have that conversation now than after.
• AI output is a draft and can be wrong. It can mistranslate, omit, misattribute a quotation, or produce text that is fluent and false. Scripture and theological commentary raise the cost of that: an error can be doctrinally significant rather than merely awkward. Every segment is meant to be read and approved by a qualified human before delivery.
• Automated quality checks are an aid, not a guarantee. A clean quality report means our checks found nothing, not that the translation is correct.

How this is accepted, and by whom. These four points are not accepted by implication from the rest of these terms. Before your organisation can upload a document, run pre-translation or sync a resource file, one of your own administrators must accept them explicitly, once, on the organisation's behalf. We record who accepted, for which organisation, when, and which version of the text they were shown.

It is deliberately your administrator and not us. A platform administrator of ours cannot give this acknowledgement for you, even while assisting your account — an acknowledgement we gave ourselves on your behalf would be worth nothing, and we would rather have no record than a misleading one.

One acceptance covers everyone in your organisation; your translators and reviewers are not asked to make a commitment on behalf of an organisation they may not represent. We will ask again if this section's substance changes — a new AI provider being the clearest example, which is the same event that triggers the 30 days' notice in §9.

5. Quality, and the limits of what we promise

We provide the platform and the AI drafting. We do not warrant the accuracy, completeness or doctrinal soundness of any translation. Editorial responsibility for what you publish rests with you and with the translators and reviewers you appoint.

The service is provided as is. We aim for continuous availability but do not commit to an uptime figure in these terms.

If your organisation needs more than this. These are our standard terms, and they apply identically to everyone who subscribes through the website. Organisations with procurement or contractual requirements beyond them — agreed service levels among them — should talk to us at support@emet.ing before subscribing, on the Organization plan. Anything of that kind is a separate written agreement; nothing in these terms commits us to service levels by default, and the platform itself is the same one every customer uses.

We may change or improve features. If we remove something you depend on, we will give you reasonable notice.

6. Plans, payment, and what your plan includes

Payment is handled by Paddle, not by us. Paddle is the Merchant of Record (see the top of this document): they take the payment, issue your invoice, and calculate and remit the sales tax or VAT for your country. We never see or hold your card details. Prices are shown on the pricing page before you buy, and Paddle shows the tax that applies to you at checkout.

Subscriptions renew automatically each billing period until you cancel, and you can cancel at any time from Plan & usage inside the app. What happens when you cancel, and when we refund, is in the Refund & Cancellation Policy.

What a plan entitles you to. Plans are sold on three limits, and the platform enforces exactly these three and nothing else:

What counts as an "AI word". Words of source text that the AI drafts for you. Segments filled from your own translation memory or from a cited reference work cost you nothing — you are charged for the machine writing, not for the platform reusing what you already own. Usage resets on the first day of each calendar month (UTC) and is visible to your administrator month-to-date.

What happens at a limit. Nothing is deleted and nothing is billed by surprise. Reaching the seat or project limit stops you adding another until you upgrade. Exhausting the AI word allowance stops AI drafting; the rest of the platform keeps working — your team can translate, review, use translation memory, run non-AI quality checks, and export. The 14-day trial ends the same way: the workspace becomes read-only, your work stays intact and exportable, and no charge is ever triggered by a trial ending.

Overage. Where a plan is sold with metered overage above its included allowance, that is stated on the pricing page at the time of purchase and charged through Paddle. We do not enable overage silently: a plan without it stops, it does not spend.

A separate spending safeguard. Independently of your plan, your organisation has a monthly cap on what we will spend with the AI providers on your behalf, visible to your administrator with month-to-date spend. If a project would exceed it, AI drafting stops rather than running up an unbounded bill. Talk to us about raising it.

Translator and reviewer pay is between you and them — not us. You engage your own translators, reviewers and language managers, you set their per-word rates, and you pay them directly. Hesed is not their employer, client or paying agent, and has no obligation to any of them for their fees. Nothing you pay us, and nothing Paddle collects, is on their behalf.

What the platform does is the arithmetic: from the rates and pay scheme your administrator configures, it counts each person's payable words — applying your translation-memory leverage discounts and your locked-match weighting — and shows the result to you and to them. That figure is a calculation offered for your convenience. You are responsible for checking it before you pay anyone, and a dispute about what someone is owed is between you and that person.

Two consequences worth stating rather than leaving implied:

• The rates you enter are visible to the person they apply to, unless your administrator turns that disclosure off. The platform also shows each translator the pay terms of a project — the weighting grid and the locked-match policy — and can require them to accept those terms before they start work. That acceptance is recorded with a snapshot of the terms as they stood, so changing a rate later does not silently rewrite what someone agreed to.
• Changing pay settings changes what past work is worth. Payable words are computed from your current project settings, not frozen per invoice. If you alter a weighting after work is done, the figure for that work moves. Settle and record what you have paid outside the platform; it is a calculator, not a ledger.

7. Getting your data out, and ending the relationship

Any time: your administrator can download delivered files and source files from the platform directly. Individual users can export their own personal data from Security → Download my data, without asking anyone.

A whole-organisation handover export — every project, file, translation memory entry and glossary term in one archive — is self-service: your administrator requests it from Organisation settings → Your data, and downloads it from the same page when it is ready. You do not need to ask us, and there is no queue behind a person. Exports are kept for 30 days and can be requested as often as you like.

On termination: you may export your Customer Content for 30 days after termination. After that, your organisation is retired and then deleted, which removes projects, files, segments, translation memory, glossaries and user accounts from the live system. Deleted content persists in backups for up to 14 days before ageing out; we cannot remove a single record from a backup archive without destroying the backup, and 14 days is the maximum lag.

Retirement before deletion. Deletion is deliberately two-step: an organisation is first retired (reversible — sign-in stops, nothing is lost) and only then deleted (irreversible). Ask us for retirement if you want a pause rather than an ending.

Ending this agreement. Either party may terminate on 30 days' written notice. You may also simply stop by cancelling your subscription, which takes effect at the end of the period you have paid for — see the Refund & Cancellation Policy. If we terminate for convenience, we will refund a fair proportion of anything you have prepaid for a period you will not now receive.

Either party may terminate immediately if the other is in material breach of these terms and has not put it right within 30 days of being told in writing. We may terminate immediately, without that cure period, if you breach the Acceptable Use Policy, if your use is unlawful, or if you become insolvent or enter an equivalent process.

You keep the 30-day export window in either case — including where we terminate for cause. The only exception is material that would be unlawful for us to hold or to hand back. Losing a subscription should not mean losing years of translation.

Suspension is not termination. We may suspend access immediately where continued use threatens the security or integrity of the platform or of other customers. For non-payment we will not suspend you while the card is still being retried — Paddle's payment recovery runs for up to 30 days and emails you during it — and we will tell you before any suspension takes effect. A suspension does not start the 30-day export window above; that runs from termination.

8. Confidentiality

Each party will keep the other's confidential information confidential and use it only for the purposes of the agreement. Your Customer Content is your confidential information. Our platform internals — including the translation rubric — are ours.

Our obligations extend to our subprocessors, each of which is engaged under terms requiring confidentiality and security appropriate to the data they receive. What we require of them, and how far we have evidenced it rather than merely required it, is set out in Data Processing Agreement §6.

9. Data protection

Our handling of personal data is described in the Privacy Policy. For Customer Content, you are the controller (controlador) and we act as your processor (operador) on your documented instructions. The terms on which we process personal data for you — the controller and processor roles, our obligations, the subprocessor list, the international transfer basis and the breach-notification commitment — are set out in the Data Processing Agreement, which forms part of these terms and applies without either of us having to sign anything further.

We will give 30 days' notice before adding a subprocessor that receives Customer Content, and you may object.

10. Liability

Read this with §5. The allocation there is the substance: we supply the platform and the AI draft, and you and the people you appoint are responsible for what you publish. This section is what remains if that allocation is ever tested.

Editorial responsibility. You are responsible for the review and approval of every translation before publication. We are not liable for the content of any translation you publish, including any error, omission or doctrinal consequence, and whether or not an AI draft contributed to it.

Indirect loss is excluded, both ways. Neither party is liable for indirect or consequential loss, or for loss of profits, revenue, business, goodwill, anticipated savings or management time, however arising.

Loss of your content is treated differently, deliberately. We do not exclude responsibility for the cost of restoring Customer Content from backup. Holding your work safely is part of what you pay for, and a platform that disclaims losing unpublished manuscripts has disclaimed the thing that matters most about it. What is excluded is indirect loss flowing from such an event — a missed publication date, for instance.

The cap. Subject to the following paragraph, each party's total liability arising out of or in connection with these terms — whether in contract, tort (including negligence), breach of statutory duty or otherwise — is limited in aggregate to the greater of:

• (a) the fees paid or payable by you for the service in the 12 months immediately before the event giving rise to the claim; and
• (b) US$ 5,000.

What no cap covers. Nothing in these terms limits or excludes liability for: death or personal injury caused by negligence; fraud, wilful misconduct (dolo) or gross negligence (culpa grave); your obligation to pay fees properly due; either party's obligations under the Data Processing Agreement; or any other liability that cannot lawfully be limited or excluded.

And it does not apply to consumers. This limitation does not apply where the Customer is a consumidor within the meaning of the Consumer Defence Code (Lei 8.078/1990). Emet is sold to organisations, so we expect this to be rare — but we would rather say so than have the question decided later.

11. General

Governing law. These terms, and any dispute or claim arising out of or in connection with them, are governed by the laws of the Federative Republic of Brazil, without regard to its conflict-of-law rules. This does not deprive you of the protection of any mandatory rule of the country where you are established — including data-protection law, which applies to your users whatever this section says.

Forum. The courts of the Comarca de São Paulo, State of São Paulo, Brazil have exclusive jurisdiction over any dispute arising out of or in connection with these terms, and each party waives any other forum.

Arbitration, for Organization-plan customers only. Where your organisation is on the Organization plan, the parties may instead agree in writing to settle disputes by arbitration under the rules of the Centro de Arbitragem e Mediação da Câmara de Comércio Brasil-Canadá (CAM-CCBC), seated in São Paulo, conducted in English or Portuguese. We do not impose arbitration on customers who subscribe through the website: it is enforceable in most of the world under the 1958 New York Convention, which is exactly why a large customer may want it, but its cost would exceed a year's subscription for everyone else and a remedy nobody can afford to use is not a remedy.

Changes to these terms: we will notify you of material changes at least 30 days before they take effect. Continued use after that is acceptance; if you do not accept, you may terminate and export under §7.

Assignment: neither party may assign without the other's consent, except to a successor of substantially all its business.

Entire agreement: these terms, the Privacy Policy, the subprocessor list and any signed services agreement are the whole agreement between us on this subject.

12. Contact

Hesed Assessoria em Software LTDA · Rua Leroy, 119, Jd. Monsenhor Rossi, Limeira-SP, 13484-229, Brazil · CNPJ 15.025.740/0001-50 Support and contract: support@emet.ing Privacy and data-protection requests: privacy@emet.ing