Terms of Service

NATEX Work, a service of NATEX AI, Inc.
Effective Date: [[OPEN-01]]
Previous versions: /legal/history
Contact: nshulman@natex.ai · NATEX AI, Inc., a Delaware corporation operated from Michigan. Registered office and address for legal notices: 16192 Coastal Highway, Lewes, DE 19958.

PLEASE READ SECTION 31 (ARBITRATION). IT REQUIRES YOU AND US TO RESOLVE DISPUTES BY INDIVIDUAL ARBITRATION, NOT IN COURT AND NOT AS A CLASS ACTION. YOU CAN OPT OUT WITHIN 30 DAYS OF ACCEPTING THESE TERMS.

The short version. This box is a plain-language summary. The numbered sections that follow are the Terms. If this box and a section differ, the section controls.

Who we are. NATEX Work is a service of NATEX AI, Inc., a Delaware corporation operated from Michigan (Section 1 (About these Terms)).

Who can use it. You must be 18 or older and reside in the United States or its territories (Section 3 (Who can use NATEX Work)).

Your Content and AI. Your Content is yours. We use it only to run the Service for you (Section 6 (Your Content)). For how AI requests work, see Section 9 (AI Features) and Section 6 (AI Features and your information) of the Privacy Policy.

NATEX does not train models on your content. We ask OpenRouter to route every AI request that uses your plan only to hosts it lists as zero-data-retention, with its zero-data-retention and no-data-collection filters on. If you choose to use your own AI account, those requests go to your provider under your terms with them. A few hosts still run short abuse checks, and web search works differently. Section 6 names them.

In the card above, "Section 6" means Section 6 (AI Features and your information) of the Privacy Policy. The hosts are named there and in Section 9.3 of these Terms.

AI can be wrong. Check facts and previews before you approve anything.

Trial and Free Plan. Every new Workspace gets a 14-day Trial. It needs no card and never charges you. The Trial has set totals: 150 AI commands, 25 deep searches, 3 Teammate runs, 3 App generations, 10 web searches, 500 integration calls, 1 mailbox, 2 connected-app connections, 1 GB of storage and 50 outbound emails, with at most 2 deep Assistant turns a day inside the 150 AI commands. When it ends, your Workspace moves to the Free Plan and nothing you made is deleted (Section S1.5 (Trial and Free Plan)).

Paid Plans. A Paid Plan renews automatically until you cancel it. Prices are on our Pricing page and at checkout (Section S1.1 (Plans and prices)). A new price applies only at your next renewal, after we email you 30 days ahead (Section S1.6 (Price changes)).

Cancel any time in one step: Settings > Billing > Cancel subscription. No call, email or reason is needed. Cancelling stops the next renewal; you keep everything you paid for until the end of the paid period, then the workspace moves to the Free plan and keeps your data.

Refunds: in full within 14 days of your first charge and within 7 days after a yearly renewal; other cases are in the refund policy. Ask at nshulman@natex.ai.

See Section S1.7 (Cancelling) and Section S1.10 (Refund Policy).

What not to put in. Don't put Protected Health Information, payment card numbers or other people's Social Security numbers into NATEX Work (Section 15 (Prohibited Data and Restricted Data)).

Disputes. Disputes go to individual arbitration, not to court or to a class action, and you can opt out within 30 days. Delaware law applies (Section 30 (Governing law and where claims are brought) and Section 31 (Arbitration and class action waiver)).

No uptime promise. We don't promise an uptime percentage and we don't offer service credits (Section 5 (The Service and how it changes)).

Changes. We give you 30 days' notice before a Material Change takes effect (Section 32 (Changes to the Terms)).

Questions. Write to nshulman@natex.ai.

0. Definitions

These definitions are used in the Terms and in the Privacy Policy. "Including" means including but not limited to.

Acceptable Use Policy or AUP: Annex A to the Terms.

Acceptance Record: The record we save each time you accept the Terms or the Privacy Policy. It holds the version of each document, the time in UTC, how you accepted (sign-up, create-account, invitation, Google sign-in, magic link or the update dialog), the page, the first 300 characters of your browser's user-agent text, a keyed hash of your IP address, whether you confirmed that you reside in the United States, and, when your network reports one, a two-letter country code. Where your browser reports it, it also holds the version of the arbitration summary that was on your screen and, for the update dialog, the one-line summary of changes that it showed. It never holds your IP address or your date of birth.

Account: Your NATEX Work profile, created after you pass the Age and Country Screen and accept the Terms. Your sign-in identity (your email address and password, Google sign-in or magic link) is held in NATEX Work's own sign-in system, which is separate from the sign-in systems of NATEX AI's other products. Your Account and the Content in your Workspaces are used only by NATEX Work.

Account Data: Personal Information we hold about you as an account holder, apart from Content: your email address, display name and avatar, your sign-in methods, the document versions you accepted, the result of the Age and Country Screen, your security settings (such as two-factor authentication), your role and last-active time in each Workspace, and your plan and billing information.

Add-On: A recurring paid extra you can add to a Paid Plan: AI Power, extra storage (100 GB each) or an extra mailbox. Each Add-On is its own Subscription with its own Billing Period and Renewal Date and is cancelled on its own.

Admin: A Member who has the admin role. The Workspace Owner is also an Admin.

Age and Country Screen: The check at sign-up and, when it is owed, at re-acceptance in which you type your month and year of birth and say where you reside. We use the answer once to decide whether you are an Eligible Person and then discard the month and year.

Agent Action: Any change made or message sent by the Assistant, a Teammate, an Automation, a Plugin, an App, or an API Key (including through the MCP Server), under an Account or a Workspace, whether or not a person clicked at that moment.

Agreement: The Terms together with the documents they incorporate: Schedule 1 (the Plan and Billing Terms), Annex A (the AUP), Annex B (the DPA) where it applies to you, the Seller Payments Terms once we publish them, and the Privacy Policy.

AI Command Pack: A one-time purchase of 600 AI commands that does not renew and starts no Subscription. It is available only on a Paid Plan.

AI Features: Every function that sends text from your Content to a Model Host, or to your Own AI Provider if you use an Own AI Account: the Assistant, search answers, the setup chat, Teammates, summaries of Call Notes, the App and Plugin builder, group planning, web search, and building Workspace Memory and answering questions from it in the "Ask your work" tab of the Ask panel (the "Make changes" tab of that panel is the Assistant). Voice input and live captions are not AI Features; your browser maker's speech service handles them.

AI Vendor: OpenRouter (when it routes a request that uses your plan) and each Model Host.

API: The NATEX Work REST API, version 1.

API Key: A secret key that begins nw_live_, belongs to one Workspace, has a scope, an optional list of allowed collections and an optional expiry date, and lets whoever holds it use the API or the MCP Server for that Workspace.

App: Software generated by the App and Plugin builder or installed from the Gallery that runs inside a Workspace in a sandboxed frame and can use only the permissions that the person who installed it approved.

Approvals: The queue where proposed changes from the Assistant, Teammates, imports and Apps wait for a person to accept or reject them.

Arbitration Agreement: The agreement in Section 31 of the Terms to resolve disputes by individual arbitration, including the class action waiver and the right to opt out.

Assistant: The conversational AI function in NATEX Work that turns your requests into proposals you can review in Approvals.

Authorized User: A Member or Guest who acts in a Workspace for a Customer, including the individual who accepts the Terms for an Organization Customer. An Authorized User who acts for an Organization Customer does not become a party to the Agreement in their own right by doing so.

Auto-Apply: An opt-in setting that an Admin can switch on for one Teammate so that the Teammate's plain create and update changes to ordinary records apply without waiting for a click. It is off by default, switching it on or off is written to the audit log, and each change can be undone.

Automation: A rule you set up in a Workspace that runs by itself when its trigger fires, such as a change to a record or a schedule.

Backup: A rolling copy of the NATEX Work database that we keep apart from the live database for recovery. We keep 14 daily copies and 8 weekly copies. A Backup holds the names and sizes of uploaded files but not the files themselves.

Backup Roll-Off Period: The 60 days after a deletion within which the last copy of the deleted information leaves every Backup.

Billing Owner: The Admin who buys a Paid Plan or an Add-On for a Workspace.

Billing Period: The month or year for which a Subscription is paid. Each Billing Period renews automatically on the Renewal Date until the Subscription is cancelled.

Business Day: A day that is not a Saturday, a Sunday or a US federal holiday.

Call: A real-time audio and video session in NATEX Work between Members, Guests and people who join from a call link. Calls run directly between participants' browsers. If the direct connection fails, a participant can open a backup room, which Google Meet or Zoom hosts if the Workspace has connected that service and which 8x8, Inc. hosts otherwise.

Call Notes: Meeting notes made from the speech recognition built into the browser of each person who adds their speech, shared as one text with everyone in the Call. Call Notes start only when every person in the Call, Guests included, has accepted. A Member can ask an AI Feature to write notes from that text. Live captions are separate: they show a person their own speech to that person only.

Connected Service: A third-party service that you connect to NATEX Work, such as Gmail, Outlook, Google Calendar, Slack, Microsoft Teams, Google Drive, OneDrive, Zoom, Salesforce, an IMAP mailbox, a calendar (ICS) feed or any other app in our catalog.

Consumer Health Data: Personal Information that identifies a person's past, present or future physical or mental health status, as state consumer health data laws define it, that a person enters about themselves, for example workout, meal, habit or journal entries. It does not include Protected Health Information.

Consumer Health Data Policy: The separate page at /legal/consumer-health-data, which is part of the Privacy Policy.

Content: Everything in or created through a Workspace, whoever puts it there: you, your Members and Guests, people who use your Public Pages or Calls, and the Connected Services you connect. It includes records, messages, files, documents, AI conversations, Workspace Memory, Output that you keep, and the copies of these kept in the command log. It does not include Account Data or Usage Data.

Controller: The party that decides why and how Personal Information is processed. It includes a "business" under US state privacy laws. We are the Controller for Account Data, billing, security, abuse, support and product-operations data. The Customer is the Controller for Content.

Counter-Notice: A notice that meets the requirements in Section 23 of the Terms, sent by a person whose Content we removed after a Notice of Claimed Infringement.

Customer: The Individual Customer or Organization Customer that holds a Workspace and, for a Paid Plan, pays for it. A Member of someone else's Workspace is not a Customer for that Workspace and has no billing rights.

Designated Agent: Our copyright agent, registered with the US Copyright Office as DMCA-1075734. Section 23 of the Terms prints the contact block exactly as registered.

Developer Features: The API, the MCP Server, API Keys and Webhooks.

DPA: The data processing addendum in Annex B to the Terms.

Effective Date: The date printed at the top of a document, on which that version takes effect.

Eligible Person: An individual who is at least 18 years old, is at least the age of majority where they reside, and resides in the Territory.

Embargoed Jurisdiction: Any place that is subject to a comprehensive US embargo, as the US Treasury's Office of Foreign Assets Control updates it.

Export: A download of data from NATEX Work: either "Download my data" (your own records as a ZIP of JSON and CSV files, with your uploaded files) or "Download workspace ZIP" (Admins only), also called the Workspace ZIP.

Extra Person: A person added to a Workspace beyond the people included in a Paid Plan, bought as a separate line on the Paid Plan's Subscription. The product calls this a "seat".

Free Plan: The plan that costs nothing, for 1 person, with small usage limits and 0.25 GB of storage. A Workspace moves to the Free Plan when a Trial ends without a purchase or when a Paid Plan ends. The Free Plan is not a Subscription and never renews.

Gallery: The shared catalog where a Member can publish an App, Plugin, theme (called a Look), template or Automation so that other Customers can install it. Only people who are signed in to an Account can see it.

Guest: A person added to a Workspace with the guest role. A Guest joins the conversations that a Member adds them to, and sees other Content only if a Member has shared it with them.

Independent Recipient: A third party that receives information because of how your browser or device works, or because of what you or your Workspace choose, and not because we engage it to process information for us. Examples: your browser maker's speech and push services, Google's STUN servers, MET Norway and the OpenStreetMap Foundation, your mail provider, the vendor of a Connected Service, the owner of a Webhook endpoint, a Third-Party Agent and an Own AI Provider. An Independent Recipient is not a Sub-processor.

Individual Customer: A natural person who creates an Account or buys a Paid Plan for themselves, for any purpose, including freelance work, study or teaching.

Integration Provider: A company we use to connect Connected Services: Composio (Sampark, Inc.) and Nango (Nango Inc).

Intimate Image Request: A request from a person shown in a non-consensual intimate image or video, or from their representative, to remove it. We remove the material within 48 hours of a valid request.

Law Enforcement Guidelines: The policy we follow for requests from governments, in Section 25 of the Privacy Policy.

Legal Hold: A duty to preserve information for a lawsuit or investigation. For our deletion jobs it also means a pause that our Staff set on a named Workspace or Account, on your written request or when the law requires it. The pause covers the deletion jobs that are tied to that Workspace or Account. It does not cover the chat and AI-history period that an Admin chose, general clean-up that is not tied to one Customer, or the Backup Roll-Off Period.

Link Tracking: An option the sender switches on for one email message. Links in that message go through our redirect so that the sender can see the time of each click. The email tells the recipient. It is off by default.

Local Mode: Using NATEX Work without an Account. Your work is stored only in your browser on your device. A page load and an error report still reach our servers.

Local-Only Mode: A setting that stops the Assistant, search and Teammates in NATEX Work from sending your Content to AI. It is different from Local Mode.

Manager: A Member role below Admin with extra rights over assignments and forms.

Material Change: A change to the Terms or the Privacy Policy that reduces your rights, changes the Arbitration Agreement, or lets us use information we already collected in a materially different way. A change of price is not a Material Change; Section S1.6 of Schedule 1 governs it. A Material Change gets 30 days' notice and your re-acceptance.

MCP Server: The Model Context Protocol server that NATEX Work exposes at the API address.

Member: A person with an Account who belongs to a Workspace, whatever their role (Workspace Owner, Admin, Manager or standard member), other than a Guest.

Model Host: A company that runs an AI model for us through OpenRouter. Today these are Microsoft (Azure), Google (Vertex AI), Amazon Web Services (Bedrock), Groq, Deep Infra, Parasail, TypeSafe AI and, for web search only, Perplexity. The Sub-processor List shows the current hosts and is generated from the same source as the Admin AI screen.

Non-User: A person whose Personal Information is in a Workspace but who has not accepted the Terms for that Workspace, such as a contact, a form respondent, a booker, an invoice payer, an email correspondent, a person who joins a Call from a link, a student, a job candidate or the recipient of a tracked link.

Notice at Collection: Section 3 of the Privacy Policy. Sign-up, create-account and first-use screens link directly to it.

Notice of Claimed Infringement: A copyright notice that has the six elements listed in Section 23 of the Terms, sent to the Designated Agent.

On-Device Storage: Information that NATEX Work saves in your browser or on your device: local storage, session storage, IndexedDB and the service-worker cache. Our code does not set cookies. The Stripe and Nango frames that open for payment and app connections may set their own.

OpenRouter: OpenRouter, Inc., through which every AI request from NATEX Work that uses your plan is routed.

Organization Customer: A company, school, nonprofit or other entity that holds a Workspace or buys a Paid Plan. The entity is the Customer and the party to the Agreement. The individual who accepts the Terms for it states that they have authority to bind it, is an Authorized User of it, and does not become a party to the Agreement in their own right by doing so.

Output: Text, code or other content that an AI Feature generates for you.

Own AI Account: An account that you hold with an Own AI Provider and connect to NATEX Work, by saving an API key or, for OpenRouter, by signing in, so that AI Features you run use that account instead of your plan. Only a Member who signs in can connect one.

Own AI Provider: Anthropic, OpenAI, Google or OpenRouter, when you connect an account with it as an Own AI Account. You chose it and you hold the agreement with it. It is an Independent Recipient. It is not a Sub-processor and it is not an AI Vendor.

Paid Plan: Solo, Team, Business or Scale, billed monthly or yearly. The Trial and the Free Plan are not Paid Plans.

Personal Information: Information that identifies, relates to or can reasonably be linked to a person, as the laws that apply define it. Where a breach notification law uses a narrower defined term, we do not use that term; our commitments in the Terms and Privacy Policy apply to a Security Incident whether or not that narrower definition is met.

Plan and Billing Terms: Schedule 1 to the Terms.

Personal Memory: Workspace Memory built for one Member from what that Member can open. Only that Member can read it.

Plugin: An installable, sandboxed extension that adds commands, automation actions, Assistant tools, widgets or settings to a Workspace.

Privacy Center: The in-product module (a module you place on a page, not a Settings page) where a person excludes collections or records from AI, switches on Local-Only Mode, flags Student Data, exports and erases records.

Privacy Policy: The NATEX Work Privacy Policy at /legal/privacy, including the Consumer Health Data Policy.

Processor: A party that processes Personal Information on a Controller's behalf. It includes a "service provider" or "contractor" under US state privacy laws. We are the Processor for Content.

Prohibited Data: Data you must not put into NATEX Work: Protected Health Information of a covered entity or business associate; payment card numbers and security codes; Social Security numbers and other government ID numbers of other people; passwords, private keys and secrets that belong to other people; other people's bank or financial account numbers; biometric identifiers; classified information and technical data controlled under the International Traffic in Arms Regulations or the Export Administration Regulations; and data about children under 13. A Seller's own payment instructions on an invoice or booking page are not Prohibited Data.

Protected Health Information or PHI: Individually identifiable health information held or sent by a HIPAA covered entity or business associate. It does not include an individual's own wellness data.

Public Page: Any page or URL that a person can open without an Account: a form, a booking page, a booking manage link, a hosted invoice, a call link, a Share Link, a public community channel, and a secret calendar feed.

Recording: A video file made from the recorder's own camera and microphone during a Call.

Refund Policy: Section S1.10 of Schedule 1: its six clauses and the rules that follow them.

Renewal Date: The date on which a Subscription renews automatically.

Repeat Infringer: An Account that has received 3 Strikes in 12 months, or 1 Strike for bad-faith or wholesale piracy.

Report: A notice, sent through the in-product "Report" control or by email, of content that a person believes breaks the AUP, the law or their rights.

Restricted Data: Data you may store on your own authority and responsibility, with no assurance from us that NATEX Work fits the rules that apply to it: education records of adult students, employment and candidate data, privileged legal material, financial institution customer information, an individual's own wellness data, and precise location.

Restricted Party: A person on a US sanctions or export denial list, or a person owned or controlled by one.

Retention Schedule: The table in Section 23 of the Privacy Policy that says how long each category of information is kept.

Rights Request: A request to use a right described in Section 26 of the Privacy Policy.

Security Incident: A breach of security that leads to the unauthorized acquisition of, access to, or loss of Content or Account Data held by us, unless, after we look into it promptly and in good faith, we conclude that it is not likely to harm anyone. For the notice to a Workspace Owner or Admin about Content (Section 21.5 of the Terms and Section B7 of Annex B), a Security Incident includes any unauthorized access to a system that holds the Content, whether or not we conclude that it is likely to harm anyone.

Sell and Share: "Sell" means to disclose Personal Information to another party for money or other valuable consideration. "Share" means to disclose Personal Information to another party for cross-context behavioral advertising. We do neither.

Seller: A Customer who uses NATEX Work to invoice, take bookings from or take payment from its own clients.

Seller Payments Terms: The terms that apply to client payments through Stripe Connect. We publish them, and you accept them, only when we turn Stripe Connect on. They are not part of the Agreement at launch.

Sensitive Personal Information: The categories of Personal Information that California law treats as sensitive and that NATEX Work handles: account log-in credentials, the contents of communications we process for you, precise geolocation, and health-related entries.

Service: NATEX Work: the web app, the installable web app, the Public Pages, the Developer Features, the Chrome extension if and when we publish it, our documentation and the marketing site at work.natex.ai.

Share Link: A URL that gives a person without an Account access to a file, folder or document.

Staff: The founder, employees and contractors of NATEX AI, Inc. who are authorized to use our admin tools or the database.

Staff Access Log: The record of Staff reading Content or Account Data through our founder dashboard: reports, copyright records, privacy requests, the customer list and Workspace views. A Workspace's Admins see the entries for their Workspace in the audit log as "NATEX staff". Direct use of the Supabase dashboard, SQL console, a database connection or the service-role key is not recorded by this log, and neither are admin screens that show no Content or Account Data.

Strike: A removal that follows a Notice of Claimed Infringement that substantially complies with Section 23, or a court finding against an Account. A Strike is cleared if a Counter-Notice results in restoration.

Student Data: Records that a teacher or Admin flags as student data, and every assignment submission.

Sub-processor: A company on the Sub-processor List that we engage to process Personal Information in providing the Service. For Content it is our Sub-processor. For Account Data it is our own Processor.

Sub-processor List: The list in Section 8 of the Privacy Policy of each Sub-processor's legal name, purpose, data, location and the date we added it.

Subscription: A Paid Plan or an Add-On, each of which is its own recurring purchase that renews automatically until you cancel it. Extra Persons are lines on a Paid Plan's Subscription.

Team Memory: Workspace Memory that an Admin switches on for a Workspace. It is built only from records that every Member except Guests can already open, and every Member except Guests can read it.

Teammate: A named AI persona (including a scheduled agent) that runs on a schedule or a trigger, can search the web and read Connected Services you allow, and leaves its proposals in Approvals.

Terms: The NATEX Work Terms of Service at /legal/terms, including Schedule 1, Annex A and Annex B.

Territory: The United States, its states, the District of Columbia and its territories (Puerto Rico, Guam, the US Virgin Islands, American Samoa, the Northern Mariana Islands and the US Minor Outlying Islands).

Third-Party Agent: An AI agent or service that holds your API Key or receives data that you route to it.

Third-Party Service: Any product, service, website or content provided by someone other than us, including Connected Services and the services of Independent Recipients.

Trash Window: The 30 days a deleted record stays recoverable before the daily sweep erases it.

Trial: The 14-day period, with no card required, that a new Workspace gets at Team level, for up to 5 people, with set total amounts of usage. Nothing is charged by the Trial. When it ends the Workspace moves to the Free Plan.

Usage Data: Technical and operational information about use of the Service that we generate: usage counters and metering records, error reports, security and rate-limit records, audit logs and the Staff Access Log. It does not include Content.

Visitor: Anyone who opens the marketing site or Local Mode without an Account.

We, us, our: NATEX AI, Inc., a Delaware corporation operated from Michigan.

Webhook: An outbound HTTPS delivery of record events to a URL you choose.

Workspace: The place that holds a Customer's Content, Members, settings and billing.

Workspace Memory: Short plain-text lines that NATEX Work builds from Content, to find the latest on a person or project, each line linked to the records it was built from. It is Personal Memory or Team Memory. Personal Memory is off until the Member turns it on, and Team Memory is off until an Admin turns it on. It is part of Content.

Workspace Owner: The Member who created the Workspace and holds the owner role.

You, your: The person or entity reading the document. For a Customer, it means the Customer. For an Organization Customer, it means the entity and not the individual who accepts or acts for it. For a Member or Guest of someone else's Workspace, it means that person.

Zero-Data-Retention Endpoint: An endpoint that OpenRouter lists as zero-data-retention, meaning one that keeps no prompts or replies beyond serving the request, subject to the exceptions stated in Section 6 of the Privacy Policy.

Part A: Terms for everyone (Sections 1 to 34)

1. About these Terms

1.1 These Terms are an agreement between you and NATEX AI, Inc. NATEX Work is a service of NATEX AI, Inc. We are NATEX AI, Inc., a Delaware corporation operated from Michigan. Registered office and address for legal notices: 16192 Coastal Highway, Lewes, DE 19958. You can reach us at nshulman@natex.ai.

1.2 The Agreement is the Terms together with the documents they incorporate. Those documents are:

• (a) Schedule 1 (Plan and Billing Terms), which applies to every purchase;
• (b) Annex A (Acceptable Use Policy), which applies to every use of the Service;
• (c) Annex B (Data Processing Addendum), where it applies to you under Section 19 (Who is responsible for personal information);
• (d) the Seller Payments Terms, only if we ever publish them and you accept them (they are not offered now); and
• (e) the Privacy Policy, which explains what we do with Personal Information. See Section 1 (Who we are and how to reach us) of the Privacy Policy.

1.3 The Terms have three layers. Part A (Sections 1 to 34) applies to everyone. Part B (Section 35 (Added protections for Individual Customers)) adds protections and procedures for Individual Customers. Part C (Section 36 (Added terms for Organization Customers) and Section 37 (Organization Customers: liability and indemnity)) adds terms for Organization Customers. If Part A and Part B differ for an Individual Customer, the term that protects the Individual Customer more applies.

1.4 If you are a person acting for yourself, you are an Individual Customer. That includes freelancers, sole proprietors, students and teachers. If you accept the Terms for a company, school, nonprofit or other entity, that entity is the Organization Customer and the party to the Agreement. You state that you have authority to bind it, and you are an Authorized User of it. You do not become a party to the Agreement in your own right by doing so (Section 36 (Added terms for Organization Customers)). Section 0 defines these terms.

1.5 If you join a Workspace that belongs to another Customer, you are a Member or a Guest of that Workspace. You buy nothing from us through it and you have no billing rights in it (Section S1.15 (Who can buy and cancel)). You accept the Terms for yourself, and Part B protects you as an Individual Customer.

1.6 If two parts of the Agreement conflict, the part that governs the subject controls:

• (a) Annex B controls how we process Personal Information in Content;
• (b) Schedule 1 controls billing, renewals, cancellation and refunds;
• (c) the AUP controls what you may do with the Service;
• (d) Section 31 (Arbitration and class action waiver) controls how disputes are resolved; and
• (e) in every other case, the numbered sections control.

For an Individual Customer, the term that protects you more applies, as Section 1.3 says.

1.7 "Including" means including but not limited to. Headings help you find things. They do not change what a section means.

1.8 The Terms are in English, and English controls. If we give you a translation or a summary in another language, the English version controls. We do not promise terms in another language or the consumer terms of another country.

2. Accepting these Terms

2.1 You accept the Terms by ticking a box that starts unticked and clicking a button that names what you are doing. We show the box on every path that creates an Account: email sign-up, Google sign-in, magic link, and your first sign-in after an invitation. The box links to the Terms, to the arbitration agreement and class action waiver in Section 31, and to the Privacy Policy. It is the only box. It reads:

I agree to the Terms of Service, including the arbitration agreement and class action waiver in Section 31, and to the Privacy Policy. I understand NATEX Work is offered only to adults who reside in the United States and is not for protected health information (PHI).

2.2 Directly under the box we show, in bold, a summary of Section 31 (Arbitration and class action waiver), with a link to the opt-out instructions. It reads:

By creating an Account you agree to resolve disputes with NATEX AI, Inc. by individual arbitration, not in court or as a class action, unless you opt out within 30 days. See Section 31 of the Terms.

The update dialog in Section 32 (Changes to the Terms) shows the same label, summary and opt-out link, and it says that your 30 days to opt out start on the day you accept the update. We record whether the summary was on screen, and its version, in your Acceptance Record. A link to the Notice at Collection sits under the summary.

2.3 If we make a change that is not a Material Change, you accept it by continuing to use the Service after it takes effect. You accept a Material Change only by the click described in Section 32 (Changes to the Terms). Continuing to use the Service is never assent to a new term of the Arbitration Agreement.

2.4 You agree to do business with us electronically. We may give you the Terms, receipts, renewal reminders, price-change notices, policy notices and any other notice that the law requires to be in writing by email to your Account address or inside the Service. When you tick the box and click the button, that is your electronic signature. It binds you as if you had signed on paper. This paragraph and Section 2.5 are the consent that the federal E-SIGN Act asks for.

2.5 You consent to receive those notices electronically on these terms:

• (a) Paper copy: you can ask for a paper copy of any notice by writing to nshulman@natex.ai. We do not charge for it.
• (b) Withdrawing consent: you can withdraw your consent at any time by writing to nshulman@natex.ai. There is no charge for withdrawing. If you do, you cannot keep a Paid Plan, because we bill and send billing notices only by email and inside the Service. We treat a withdrawal as a request to cancel your Paid Plans under Section S1.7 (Cancelling). Withdrawing does not affect anything either of us did electronically before.
• (c) What you need: you need a device with a current web browser that opens web pages and PDF files, and an email address that you can open and that can receive messages from us. Our system messages come from the sending address noreply@natex.ai. Our billing, invitation and alert emails carry nshulman@natex.ai as their Reply-To address, so your reply reaches us. Nobody reads replies to sign-in emails (the emails that confirm your address, reset your password or carry a sign-in link). To reach us, write to nshulman@natex.ai.
• (d) Updating your email address: write to nshulman@natex.ai from your current Account address.
• (e) Scope: this consent covers every notice, disclosure, receipt, agreement and other record that we provide in connection with the Service, including any that the law requires to be in writing.
• (f) Showing that you can open our records: by ticking the box you confirm that you can open this document, which is a web page, and that you can receive email at your Account address. You also show it when you open the verification link or sign-in link that we send to your Account address, or when you sign in with a Google account whose email address Google has verified.
• (g) Changes in what you need: if the hardware or software needed to open our notices changes in a way that creates a material risk that you cannot open them, we will tell you first, and you may withdraw your consent without charge.

2.6 Each time you accept the Terms or the Privacy Policy, we save an Acceptance Record. It holds the version of each document, the time in UTC, how you accepted, the page, the first 300 characters of your browser’s user-agent text, a keyed hash of your IP address (a one-way code made with a secret key that only we hold), whether you confirmed that you reside in the United States and, when your network reports one, a two-letter country code. We never save your IP address or your date of birth. We never overwrite an Acceptance Record. We keep Acceptance Records for 7 years from the day you accepted, even if you delete your Account, so that we can prove that you agreed and defend legal claims. When you delete your Account we detach the record from your name and email and keep it under an opaque identifier. Where your browser reports it, the record also holds the version of the arbitration summary that was on your screen next to the box, and the one-line summary of changes shown in an update dialog. A browser that does not report the version leaves it empty. The record never claims that a summary was shown when it was not.

2.7 You can use Local Mode from anywhere. It stores your work only in your browser on your device. A page load and an error report still reach our servers (Cloudflare and our error-report function). Using Local Mode is subject to these Terms. Creating an Account requires you to be an Eligible Person. Section 15 (On-Device Storage, Local Mode and browser requests) of the Privacy Policy says what Local Mode saves on your device.

2.8 The Terms apply to your use of the Service before you create an Account and after, including in Local Mode and as a Visitor. Section 3 (Notice at Collection) of the Privacy Policy says what we collect when you create an Account. Section 23 (Retention Schedule and deletion) of the Privacy Policy says how long we keep the Acceptance Record. Section 20 (Age, children and where you live) of the Privacy Policy describes the Age and Country Screen. Section 31 applies to you only if you have accepted it by ticking the box described in Section 2.1.

3. Who can use NATEX Work

3.1 You must be at least 18 years old and at least the age of majority where you reside, and you must reside in the United States or its territories.

3.2 NATEX Work is offered only to adults who reside in the United States and its territories. It is not directed to the European Economic Area, the United Kingdom, Switzerland or any other country. You confirm that you reside in the Territory. You may keep using your Account while you travel. If we have good reason to believe that you no longer reside in the Territory, we may suspend your Account after notice and a chance to export your data, where the law allows.

3.3 When you create an Account, and at a re-acceptance when the screen is owed, we run the Age and Country Screen. You type your month and year of birth and say where you reside. We use your answer once to decide whether you are an Eligible Person and then discard the month and year. A person counts as 18 from the first day of the month after the month of their 18th birthday. If the age of majority where you reside is higher than 18, do not create an Account until you reach it.

3.4 If you do not pass the screen, we do not create an Account for you. After an answer that shows you are under 18, the form stays closed in that browser for 24 hours. If a brand-new sign-in identity fails the screen and was created in the last 30 minutes, we delete it. If the country that your network reports is outside the Territory, we do not create the Account. Section 20 (Age, children and where you live) of the Privacy Policy gives the details.

3.5 We do not offer Accounts to minors, including school-administered Accounts, and we offer no school agreement. Teachers and schools may use NATEX Work only through Accounts held by adults.

3.6 Some people who take part in your Workspace through a Public Page or a Call, such as people who fill in a form or join a Call from a link, may be minors. You are responsible for them. You must not collect Personal Information from anyone under 13 through the Service.

3.7 If we learn that you are not an Eligible Person, we may suspend or end your Account (Section 26 (Suspension and termination)).

3.8 You may use the Service to serve your own clients, bookers, respondents and other people who are outside the Territory. If you do, you remain the Controller of their Personal Information, and you are responsible for the laws of the places where they are. NATEX Work is not designed for them and is not marketed to them. Annex B (Data Processing Addendum) applies to you as Section 19 (Who is responsible for personal information) explains.

4. Accounts, Workspaces and roles

4.1 You get an Account only after you pass the Age and Country Screen and accept the Terms. Give us accurate information, and keep your email address current. An Account is for one person. Do not share your password or your sign-in links.

4.2 You are responsible for what happens under your Account, including every Agent Action (Section 10 (Teammates, Automations and actions taken for you)). Keep your credentials secret. If you think someone else has access to your Account, write to nshulman@natex.ai promptly.

4.3 Two-factor authentication is available for your Account. You should turn it on. A Workspace may require it for its Members.

4.4 A Workspace has these roles:

• (a) The Workspace Owner created the Workspace. Only the Workspace Owner can delete it (Settings > Team > Delete this workspace).
• (b) Admins manage the Workspace, its Members and its settings. Only Admins can buy, change or cancel a Paid Plan or an Add-On, and any Admin can do so, not only the Billing Owner. The Admin who buys is the Billing Owner.
• (c) Managers have extra rights over assignments and forms.
• (d) Members use the Workspace within the rights their role gives them.
• (e) Guests join the conversations a Member adds them to, and see other Content only if a Member shares it with them.

4.5 The Workspace Owner and the Admins can see more than other Members can, including Members' AI conversations in the Workspace. Every Member except Guests can also open the records that Connected Services bring into the Workspace. Section 36 (Added terms for Organization Customers) lists what each role can see. If you are a Member of someone else's Workspace, read it. Section 17 (If you use NATEX Work through someone else's Workspace) of the Privacy Policy covers the same ground.

4.6 If a Billing Owner cannot sign in, they can write to nshulman@natex.ai from their Account address.

4.7 If you stop being a Member of a Workspace, because an Admin removes you or because you delete your Account, you lose access to it and to its Content. The records you created there stay with the Workspace (Section 20 (Export, deletion and retention)).

4.8 You can delete your Account at any time (Section 20 (Export, deletion and retention)). If you own a Workspace that has other Members who are not Guests, you must choose for each one: hand it over to a named Member, or delete it for everyone. The default is the longest-standing other Admin or, if there is none, the longest-standing Manager, and then the longest-standing Member.

4.9 NATEX Work has its own database and sign-in system, separate from NATEX AI's other products. NATEX AI uses one Stripe account and one OpenRouter account for all of its products. Your NATEX Work data is used only by NATEX Work.

5. The Service and how it changes

5.1 The Service is NATEX Work: the web app, the installable web app, the Public Pages, the Developer Features, our documentation and the marketing site at work.natex.ai. The Chrome extension becomes part of the Service only if and when we publish it.

5.2 We provide the Service as available, using commercially reasonable efforts. We do not promise any uptime percentage, and we do not offer service credits. Scheduled maintenance, and outages of hosting, AI, payment, email and Connected Service providers, are outside our control, and they are not a breach of the Agreement.

5.3 Beta features and optional Connected Services sit outside any promise we make about availability or security.

5.4 We may change or discontinue a feature. If we materially reduce the features of a Paid Plan, you can cancel within 30 days of our notice. If you choose to end your plan at once, we refund the unused part of what you prepaid, as clause 3 of the Refund Policy and Section S1.10 (Refund Policy) say. You do not need to ask for the refund.

5.5 If we discontinue the Service, we will give you at least 30 days' notice and a window to export your Content (Section 20 (Export, deletion and retention)). We will refund the unused part of what you prepaid, for time after the Service ends, as Section S1.10 (Refund Policy) says. You do not need to ask.

5.6 We help by email at nshulman@natex.ai. We do not promise support hours.

5.7 If you have difficulty reading these Terms or using the Service because of a disability, write to nshulman@natex.ai. We will give you any legal document in another format on request. Our legal documents are written as web pages with headings and landmarks, and they print. We aim to make the Service work with assistive technology. We have not certified conformance to the Web Content Accessibility Guidelines (WCAG). Report a barrier to nshulman@natex.ai. Section 30 (Contact and accessibility) of the Privacy Policy makes the same offer for the Privacy Policy.

6. Your Content

6.1 You own your Content. We do not claim ownership of it.

6.2 You give us a non-exclusive, worldwide, royalty-free license to host, store, back up, reproduce, process, transmit, display and send your Content. We may use it only:

• (a) to provide the Service to you and your Workspace, including by sending Content to Model Hosts through AI Features you use, and to Connected Services and Integration Providers you connect, at your direction;
• (b) to keep the Service secure, to detect abuse and to enforce the AUP; and
• (c) to comply with the law.

The license includes the right to let our Sub-processors do these things for us. It does not include any right to train or improve models on your Content, and we give no one that right.

6.3 The license ends when you delete the Content, except for the copies that remain for the periods described in Section 20 (Export, deletion and retention): the Trash Window, the Backup Roll-Off Period and the vendor retention listed there.

6.4 We use your Content only to provide the Service to you and your Workspace, to keep it secure, and as the law requires. We do not use your Content to train or improve AI models, for advertising, or for any purpose of our own, and we do not sell it. We keep limited operating records, such as error reports and usage counters, which the Privacy Policy describes.

6.5 You may make Content public, for example through a Public Page, a Share Link, a public community channel or a Gallery item. If you do, you give us a license to display and distribute it publicly, at your direction, for as long as you leave it public. You can end that license by deleting the Content or switching off the sharing. Caches, Backups, copies that other people already made and installed copies of Gallery items may remain for a time (Section 8 (Public Pages, links and what you share), Section 20 (Export, deletion and retention)).

6.6 You state that you have the right to put your Content into the Service and to give us the licenses in this Section. You also state that, to the best of your knowledge, your Content does not break the law or anyone's rights.

6.7 Content can carry instructions meant to manipulate AI. Section 10 (Teammates, Automations and actions taken for you) addresses that.

6.8 Usage Data is not Content. We keep and use it to run, secure and support the Service, as Section 22 (Error reports, logs and rate limits) of the Privacy Policy describes. See also Section 5 (How we use information) of the Privacy Policy.

7. Our materials, brand, feedback and open-source notices

7.1 The Service, its software, documentation and design, and our first-party templates and Looks, belong to us or our licensors. While the Agreement applies to you, we give you a limited, revocable, non-exclusive, non-transferable license to use the Service for its intended purposes and within your plan. You get no source code. You may not copy, reverse engineer or resell the Service, except where the law or an open-source license gives you that right.

7.2 NATEX Work and the NATEX Work logo are our trademarks. You may use our name only to say that you use NATEX Work. Do not suggest that we endorse or sponsor you, and do not alter the logo. A "Made with NATEX Work" line on a Public Page is a statement of fact, not a license to use our marks.

7.3 Product names are trademarks of their owners. Use here does not imply endorsement or affiliation.

7.4 If you send us feedback or a suggestion, you give us a worldwide, perpetual, irrevocable, royalty-free license to use it without obligation to you and without attribution. This is a license, not an assignment, and feedback is not Content. Crash reports and feedback text follow the Privacy Policy (Section 22 (Error reports, logs and rate limits) of the Privacy Policy).

7.5 NATEX Work includes open-source software. Its notices are at /third-party-notices.txt. We use JSZip under the MIT license and DOMPurify under the Apache License 2.0. Nothing in the Agreement limits the rights you have under an open-source license.

7.6 Weather data in NATEX Work comes from MET Norway and is licensed under CC BY 4.0 and NLOD 2.0. Place search uses data © OpenStreetMap contributors, available under the ODbL. We provide both as they are. Do not rely on them for decisions about safety. Section 7 (Who receives information) of the Privacy Policy and Section 11 (Composio, Nango and the Chrome extension) of the Privacy Policy repeat these notices.

8. Public Pages, links and what you share

8.1 Some parts of the Service are public, or can be reached by anyone who has a link. They are Public Pages (forms, booking pages, booking manage links, hosted invoices, call links, Share Links, public community channels and secret calendar feeds) and Gallery items. Anything you put there can be seen, copied and shared by the people who can reach it. Do not put anything there that you want to keep private.

8.2 A link is a bearer secret: whoever holds it can use it. Treat Public Page links, Share Links, hosted invoice links, call links and calendar feed URLs like passwords. A Share Link marked "Never expires" lasts until you revoke it. A secret calendar feed URL shows every event to whoever holds it. We ask search engines not to index Public Pages, but a person who has a link can still open it and share it.

8.3 Every Public Page except a secret calendar feed (a data file) ends with this line. {name} is the name of the Workspace or Seller. Where we do not have a name, the line says "The workspace owner".

Powered by NATEX Work · {name} controls the information you submit · Privacy

This line does not replace your own notice to people about how you handle their information (Section 18 (Your duties to the people whose data you handle)).

8.4 Anyone who has the link can read a public community channel without an Account, and anything you post in one is public. A public community channel shows its latest 50 top-level posts, with each post's text, time and a "Member" or "Webhook" label, and the channel name and topic. Only people who are signed in to an Account can open the Gallery, and they need not belong to the Workspace that published an item. An item you publish shows your user id and your Workspace id to every Customer, with the item itself, and an item may contain Personal Information that its publisher chose to include. Do not publish Personal Information about other people unless you have the right to.

8.5 Your Content may include Personal Information about Non-Users, such as contacts, form respondents, bookers, invoice payers and email correspondents. You must have the right to upload it and the consents that the law requires (Section 18 (Your duties to the people whose data you handle)).

8.6 A Non-User can ask to have information about them removed or corrected. We aim to forward the request to the Admins of the Workspace concerned within 10 Business Days, and you must honor it as the law requires. A Non-User can use the Report control where it appears, use the form at /legal/privacy-request, or write to nshulman@natex.ai and tell us which Workspace.

8.7 We do not review private Workspace Content except as Section A19 (No duty to monitor) says. We may remove public Content in good faith (Section 24 (Reporting content, and our role as a host)). Section 16 (If your information is in someone else's Workspace) of the Privacy Policy and Section 18 (Public Pages, the Gallery and community channels) of the Privacy Policy describe the same pages for the people who use them.

9. AI Features

9.1 AI Features send text from your Content to a Model Host through OpenRouter, or, if you use an Own AI Account, to your Own AI Provider. They are the Assistant, search answers, the setup chat, Teammates, summaries of Call Notes, the App and Plugin builder, group planning, web search, and building Workspace Memory and answering questions from it in the "Ask your work" tab of the Ask panel (the "Make changes" tab of that panel is the Assistant). The Assistant sends up to 45 record titles and a few fields from your records with each turn. Voice input and live captions are not AI Features. AI Features are for adults: you must be an Eligible Person to use them.

9.2 Check Output before you rely on it.

AI can be wrong. Check facts and previews before you approve anything.

Output can be wrong, incomplete or similar to Output other people get. You are responsible for checking Output before you rely on it or send it.

9.3 This is how AI requests are handled and what the filters do not cover.

NATEX Work sends AI requests that use your plan only through OpenRouter, and only to model hosts that OpenRouter lists as zero-data-retention endpoints, meaning endpoints that keep no prompts or replies beyond serving the request, apart from the exceptions below. Every such request asks OpenRouter for both of its filters (zero data retention and no data collection), so if no such host can serve a request it fails instead of going elsewhere. NATEX does not train models on your content. It sends plan requests only to hosts that OpenRouter lists as zero-data-retention endpoints, which keep no prompts or replies to train on, apart from the exceptions below. If you choose to use your own AI account, requests on that account go to your provider instead, and your provider’s terms apply to them.

Those filters do not switch off a host’s own abuse and safety systems. For the hosts we use today:

• Microsoft Azure. Microsoft runs automated abuse monitoring. When it flags a request, a sample of the prompt and the reply may be stored and read by Microsoft reviewers.
• Google Cloud Vertex AI. Google may keep a request in memory for up to 24 hours (caching) and may log prompts to check for abuse, under Google’s own terms.
• Groq. Groq may keep a request for up to 30 days while it troubleshoots an outage or investigates suspected abuse.

OpenRouter keeps request metadata (such as token counts and timing) but not the text of your prompts or replies, and it may sample a small number of prompts to assign anonymous topic categories that are not linked to your account.

We never call the endpoints run by the Chinese model makers themselves (Z.AI, DeepSeek, Moonshot, MiniMax, Alibaba, Baidu and SiliconFlow). Open-weight models from those makers, such as GLM and Qwen, run on US-based hosts.

Web search is different: a short, cleaned search phrase (links, e-mail addresses and long numbers removed, never your workspace) goes to Perplexity through OpenRouter, and Perplexity states that it does not retain or train on API data.

Voice input and live captions use your browser’s own speech recognition, run by your browser maker. Apps you connect (for example Gmail, Slack or Notion) are separate services with their own terms.

Section 6 (AI Features and your information) of the Privacy Policy says the same and gives the detail.

9.4 NATEX does not train models on your content. It sends requests that use your plan only to hosts that OpenRouter lists as zero-data-retention endpoints, which keep no prompts or replies to train on, apart from the exceptions stated in Section 6 of the Privacy Policy. If you choose to use your own AI account, requests on that account go to your provider, and your provider’s terms decide what it keeps. We do not keep a license to use your Content to train or improve models, and we do not use data from your Connected Services to train models.

9.5 Local-Only Mode stops the Assistant, search and Teammates in NATEX Work from sending your Content to AI. It does not govern calls you make through the API or Webhooks you configure.

9.6 As between you and us, you own the Output that AI Features generate for you, to the extent the law gives anyone ownership. We assign to you whatever rights we have in Output, if any, and we claim none. The law may not protect Output, and Output may be similar to Output that other people get. Output may include material that belongs to someone else. We do not promise that Output does not infringe anyone's rights, and we do not defend you against claims about Output. You are responsible for how you use Output, including any duty to disclose AI-generated material when you register a work.

9.7 You must follow the usage policies of the Model Hosts that run your requests, as they apply to your inputs and to Output. The Sub-processor List names the Model Hosts (Section 8 (Sub-processor List) of the Privacy Policy). A Model Host or OpenRouter may screen, refuse or block a request that it flags, and we may refuse a request that a Model Host refuses. We may change models and Model Hosts. We send OpenRouter's zero-data-retention and no-data-collection filters with every request, including web search, and we show the current Model Hosts on the Sub-processor List. Section 9.3 says what the filters do not cover. A new Model Host is a new Sub-processor, and Section B6 (Sub-processors) says how we give notice. This section applies to requests that use your plan. Section 9.12 covers requests on your Own AI Account.

9.8 Do not put Prohibited Data into AI Features (Section 15 (Prohibited Data and Restricted Data)). Section A13 (AI-specific rules) and Section A14 (High-risk decisions about people) set further limits on what you may do with AI Features and Output, including the use of Output to train a competing model.

9.9 An Admin or a Member can turn off collections for AI, flag records "AI never touches this", flag Student Data and switch on Local-Only Mode. These controls are in the Privacy Center and in Settings > Admin > AI, and Local-Only Mode is also a switch in Settings > Privacy. Apart from Student Data (Section 16 (Professional, regulated and government use)) and health collections, nothing is excluded from AI Features by default. Health collections start excluded in a new Workspace. Any other collection whose name suggests health information is excluded when it is first used. You can turn AI Features back on for one after you confirm a warning. For example, invoice and bank-detail collections are not excluded until someone turns them off. Teammates also skip mail, chat, credentials, subscription and payment records unless a Teammate's scope names them. Each Connected Service has an "AI-private" switch at Settings > Integrations. When it is on, NATEX Work does not sync that service into the Workspace and Teammates do not use the connection. Section 6 (AI Features and your information) of the Privacy Policy explains the real scope of each control.

9.10 Workspace Memory is optional. Personal Memory is off until you turn it on. Team Memory is off until an Admin turns it on. Memory lines are Output. They can be wrong, out of date or incomplete, so you must check the records they link to before you rely on them. Memory is built only from Content that the person it is built for can open, and the Privacy Policy says what it leaves out and who can read it (Section 6 (AI Features and your information) of the Privacy Policy). An Admin who turns on Team Memory decides, for the Workspace, that the Workspace's shared records are summarized by AI and that every Member except Guests can read the summary. The Admin must have the right to do that and must tell Members.

9.11 Memory and the "Ask your work" tab of the Ask panel share a daily budget for each Workspace. We may lower, raise or pause it, and when it is used up they pause until the next day. This is a limit on the feature and not a plan allowance, and it does not change what your plan includes. "Ask your work" answers from records the person asking can read and links each answer to them, and it says so when the records do not answer. The "Make changes" tab is the Assistant. It proposes changes and writes nothing until a person confirms, and this section does not apply to it.

9.12 You can connect an Own AI Account. When AI Features run on it, your requests go to your Own AI Provider with your key. Your agreement with that provider, including its usage policy, price and privacy terms, governs those requests. We are not a party to it, we do not control the provider, and we are not responsible for what it does with your requests, for its charges or for its outages. The commitments in Sections 9.3 and 9.4 about routing and hosts do not apply to those requests. The provider is your recipient and is not our Sub-processor (Section 7 (Who receives information) of the Privacy Policy). Requests on your Own AI Account do not use your plan's AI commands. If your account fails, runs out of credit or is refused, the rest of the request goes to our plan models. We may stop supporting a provider, or a way of signing in with it, on notice.

9.13 Before you connect an Own AI Account, you confirm that you may use the account, that its terms allow your use, and that you may send the Content you will send. In a Workspace that belongs to someone else, or one that holds other people's Personal Information, you must follow the Workspace's rules and the law about sending that information to a provider of your own. An Organization Customer is responsible for deciding which of its Members may use an Own AI Account. Its Admins cannot see which accounts Members connect, but they can switch Own AI Accounts off for the whole Workspace at Settings > AI. The change is logged, and while the switch is off no Member's key is used in that Workspace and our plan models answer. You must not use a key that is not yours or that you may not use. You are responsible for requests made with your key, and for keeping it safe. Remove a key if you think it was exposed, and delete it at your provider as well.

9.14 We keep your key only to run your requests and to test that it works, and we delete our copy when you remove it, leave the Workspace or delete your Account or the Workspace (Section 20 (Export, deletion and retention)). Deleting our copy does not cancel the key at your provider.

10. Teammates, Automations and actions taken for you

10.1 Every Agent Action under your Account or Workspace is your action, with the same effect as if you had done it yourself. That includes actions by the Assistant, a Teammate, an Automation, a Plugin, an App or an API Key, including through the MCP Server. Sending, posting, inviting, deleting and creating events through them is your act. This does not apply to an action that we caused by a defect in the Service, or that a person took with an API Key after you told us in writing that the key was lost or stolen. For anything the Assistant, a Teammate or an Automation did that you did not approve, we will help you undo it from the command log while it is still there.

10.2 Your approval is your act. When you accept a proposal in Approvals, or click a confirm button, you authorize the action. If you switch on Auto-Apply, you authorize in advance the kinds of change it covers. Small changes to your own layout, such as moving a widget or renaming a page, apply at once, and each can be undone.

10.3 This is how Auto-Apply works. Auto-Apply is off until an Admin turns it on for a Teammate.

Scheduled agents and teammates can run while you are away, but what they propose waits in the Approvals queue. The one exception is opt-in and per teammate: a workspace admin can turn on auto-apply, and that teammate’s plain create and update changes to ordinary records are then applied without waiting. Auto-apply never sends, deletes, creates automations or touches invoices, payments, members or other sensitive collections; each change shows in Approvals with an Undo, and turning it on or off is written to the audit log. It is off until an admin turns it on.

Scheduled agents pause after 7 days without their creator being active.

10.4 Teammates and scheduled agents can run while you are away. Our scheduler looks for due work every 5 minutes, and each Teammate or scheduled agent runs on its own schedule or trigger. An Automation runs on its own when its trigger fires and does not wait for you. What a Teammate or a scheduled agent proposes waits in Approvals unless Auto-Apply applies. We do not promise that an Agent Action will happen at a particular time, or at all.

10.5 Content can carry hidden instructions meant to manipulate AI, for example in an email, a web page, a file or a form answer. Review proposals before anything leaves your Workspace. Keep scopes and API Key permissions narrow. Do not give an Automation, Teammate, Plugin or API Key a permission that you would not give to a new human assistant.

10.6 When a message goes out in your name, you are the sender. You need a lawful basis to contact the recipients, and you must follow the laws that apply to you as a sender. To send from an IMAP mailbox, our servers connect to your mail provider's server. The Sub-processor List names any relay we turn on.

10.7 You are responsible for the sources that your Teammates and our fetchers read for you, including websites and feeds. Do not use them to get around an access control, a paywall or a site's technical limits. Section 6 (AI Features and your information) of the Privacy Policy describes what Teammates read and how Auto-Apply is recorded.

11. Apps, Plugins and the Gallery

11.1 You are the publisher of any App, Plugin, Automation, template or Look that you build, install, share or publish. You are responsible for it, and for the permissions you approve.

11.2 We do not review, test or endorse Apps, Plugins or Gallery items. You install and run them at your own risk, and we provide them as is. AI-written code can contain bugs, security flaws and code that belongs to someone else. Review it before you run it or publish it. Follow the license of any open-source code you use.

11.3 An App or a Plugin can use only the permissions that the person who installed it approved. Approve a network or write permission only if you understand it. An installed item with network permission sends data to the hosts it declares. Remove items that you no longer trust.

11.4 When you publish an item to the Gallery, you keep ownership of it. You give every other Customer a non-exclusive, worldwide, royalty-free license to install, run, copy within their Workspace and modify the item for their own use. You give us a license to host and display it. Unless you state another license on the item, the license is limited to use inside NATEX Work and does not allow redistribution outside it.

11.5 You confirm that, for an item you publish:

• (a) you own, or have the right to license, everything in it;
• (b) it contains no malware and makes no hidden network calls;
• (c) it contains no code under a license that conflicts with Section 11.4; and
• (d) it contains no Personal Information that you lack the right to share.

11.6 We may hide, remove, disable or force-update any Gallery item, and any installed copy of it, when we believe it is malicious, infringing, unlawful or against the AUP. This applies to people who already installed the item, and it overrides any continuing license under Section 11.4.

11.7 Section A11 (Security and malicious code) and Section A15 (Community and Gallery rules) apply to Apps, Plugins and Gallery items. A Report control appears on every Gallery item (Section 24 (Reporting content, and our role as a host)). Section 18 (Public Pages, the Gallery and community channels) of the Privacy Policy describes what the Gallery shows.

12. API, MCP Server and Webhooks

12.1 An API Key is shown once, when you create it. Keep it secret. You are responsible for everything done with it. Give each API Key the narrowest scope and the shortest list of collections that works, set an expiry date where you can, and revoke the key if you suspect misuse. We may revoke an API Key that is used to abuse the Service.

12.2 Each API Key may make 120 requests a minute. Do not spread traffic over several API Keys to get around the limit. We may throttle requests.

12.3 We will give you at least 30 days' notice before a breaking change to the API. Send security reports about the Developer Features to nshulman@natex.ai.

12.4 You own the endpoint that receives a Webhook, and you own its secret. Verify the signature on every delivery. We try each delivery up to 8 times in total over about a day, and then we stop. Payloads contain record data, so you must secure the endpoint and use the data lawfully. We do not deliver to private network addresses or to addresses that are not https.

12.5 A Third-Party Agent that holds your API Key, or that you route data to, is a recipient you chose. It is not our Sub-processor. We are not responsible for what it does with data after we deliver it, and you are responsible for the scopes you give it.

12.6 You decide which Third-Party Agents and Connected Services receive data from your Workspace, and you must have the right to send it there. Section 13 (Connected Services) sets extra limits on data that comes from Google, Microsoft and other Connected Services. Section A16 (API, MCP Server and Webhook rules) applies to the Developer Features. Section 7 (Who receives information) of the Privacy Policy lists the recipients that you choose.

12.7 Local-Only Mode does not govern calls you make through the API or Webhooks you configure (Section 9 (AI Features)).

12.8 You can create URLs that other services use to send data into your Workspace, such as community webhooks and automation hooks. Whoever holds the URL can post. You are responsible for who receives it and for the data that arrives. Anything posted that way is Content and may concern people who are not Members.

12.9 An API Key can read Workspace Memory and use "Ask your work" through the MCP Server, as the Member who created the key. That includes that Member's Personal Memory. A Third-Party Agent that holds such a key can therefore read what that Member can read. Give a key that scope only to a Third-Party Agent you trust with it. Anything a key asks to send, such as an email, a calendar event or a Plugin run, waits as a proposal in Approvals until a person accepts it, the same as a change proposed in the "Make changes" tab.

13. Connected Services

13.1 You consent, for yourself, to us and our Sub-processors accessing, processing and disclosing the contents of the mailboxes, chats, calendars and Calls that you connect, as needed to provide the features you use. By connecting a mailbox, a calendar or another Connected Service, you state that you have the right to have NATEX Work process the messages, events and files in it for you. You are responsible for telling the people whose messages, calendar entries and Calls you connect, and for getting any consent the law requires from them, so that we can process those communications to provide the features. If you are an Admin and you connect other Members' accounts, you state that you have their authority to do so.

13.2 A Connected Service is a Third-Party Service. Its own terms and privacy practices apply to it, and we are not responsible for them. We may disable a Connected Service when its provider or the law requires us to.

13.3 You state that you have authority over every mailbox, app, IMAP account, calendar (ICS) feed URL and API key that you connect, and that you will follow the provider's terms. An app password or key that you paste into the Service stays yours to scope and to revoke.

13.4 You authorize us and our Integration Providers to access a Connected Service account that you connect, and to process its content to provide the features you use, including AI Features that you invoke. For Microsoft mail and calendar, this is the express and specific permission that Microsoft's API terms require for any use beyond sync and backup. For data that comes from Google, you consent to its transfer to a Model Host for the feature you invoke. Section 9 (Google user data) of the Privacy Policy and Section 10 (Microsoft user data) of the Privacy Policy describe how we handle that data. With your connection we also create calendar events, video meetings and replies in your Google, Microsoft or Zoom account when a feature you use needs one. We also make your own changes in that account, such as moving a message to the trash or archive or deleting an event. The Assistant, Teammates and Apps cannot delete anything in a Connected Service on their own.

13.5 We do not use data from your Connected Services to train models. You may not use the Service to extract data from a Connected Service in order to train a model where that service's terms forbid it.

13.6 Composio and Nango, our Integration Providers, hold the sign-in tokens and the keys that you paste for the apps you connect. If either of them were compromised, the connected account could be exposed. Use restricted keys where an app offers them, and revoke access when you disconnect an app (Settings > Integrations).

13.7 Composio connects many of the apps you add. It can keep the content of tool calls, which can include message text, for up to 1 year, including after you disconnect an app. That is outside our deletion windows. We have not signed a separate data processing agreement with Composio. Composio's standard terms apply.

13.8 When you connect a mailbox, a calendar, Slack, Microsoft Teams, Zoom, GitHub, GitLab, Jira, Google Drive or OneDrive, NATEX Work copies what the connection brings in into the Workspace as records. They are email previews of up to 280 characters, calendar events, chat messages, Zoom meetings, issues and files. Every Member except Guests can open the calendar events, chat messages, issues, meetings and files unless the Workspace restricts them. Email previews are different: only the Member who connected the mailbox can open them, and no one else in the Workspace can, Admins included, unless that Member or an Admin switches on sharing for that mailbox. Sharing is off by default. While it is on, every Member except Guests can open that mailbox's mail and send from it, and each send still asks the sender to confirm. Connect a personal account to a Workspace only if you are comfortable with that. Section 36 (Added terms for Organization Customers) lists what each role can see.

13.9 When you disconnect an app, a mailbox or a calendar, we show you what will be deleted. Then we delete the connection at the service that holds it, the stored sign-in and what the connection brought in: synced email previews, synced calendar events that you did not edit, synced chat messages, pulled-in issues and imported files. Things you created or changed yourself, such as drafts, events you made or edited, tasks and notes, stay. Copies in Backups are gone within 60 days. Composio may still keep tool-call content for up to 1 year, and the service you connected keeps what its own terms say. A Legal Hold pauses the deletion of the items, but not the disconnect.

13.10 Section 11 (Composio, Nango and the Chrome extension) of the Privacy Policy gives the detail.

14. Email, messages and Calls

14.1 Send email through the Service only to recipients you may lawfully email. Do not use invitations, or any relay we turn on, to send bulk mail. We may rate-limit sending, suspend it and report complaints. Section 13 (Email we send) of the Privacy Policy describes the email we send.

14.2 Calls run directly between participants' browsers. Every participant's public IP address goes to Google's STUN servers and to the other participants. If the direct connection fails, a participant can open a backup room. If the Workspace has connected Google Calendar, we create a Google Calendar event with a Meet link for it. If the Workspace has connected Zoom, we create a Zoom meeting. Otherwise 8x8, Inc. hosts the room. Google, Zoom or 8x8 then receives the audio, video and display names. We do not control that room, and its host provides it on a best-effort basis. Recording and consent duties stay with the Member who hosts the Call.

14.3 Hosts and participants are responsible for the laws that apply to recording a Call and to making live captions or Call Notes of it, including laws that require every person's consent.

14.4 A Member can record a Call from the Member's own camera and microphone. Before a Recording starts, a dialog tells the recorder that everyone sees a "Recording" indicator, and the recorder confirms. Every participant sees a persistent indicator, including people who joined from a call link, and a person who joins later is alerted. The recorder should record only if everyone agreed.

14.5 A Recording goes nowhere unless the recorder chooses to save it to Files. Otherwise the recorder can download it or discard it. A Recording saved to Files is Content in the recorder's Workspace. The recorder is responsible for it, including any consent that the law requires for the voices and likenesses in it. We get no license to a Recording beyond hosting it for that Workspace, as Section 6 (Your Content) says. Voice rooms cannot record.

14.6 Call Notes start only when everyone on the Call, Guests included, accepts. A person who asks for Call Notes sends a prompt to everyone on the Call. If anyone declines, Call Notes stay off for the rest of that Call. A person who joins later pauses Call Notes until that person answers. While Call Notes run, everyone sees a "Call Notes on" indicator. A person who adds their speech sends their own microphone audio to their browser maker's speech service, and their microphone can also pick up other people's voices from speakers. A Member can ask an AI Feature to write notes from the text, which sends up to 30,000 characters of it to a Model Host. Live captions are separate and stay each person's own choice. We keep each person's answer, the text they were shown, the time, the first 300 characters of their browser's user-agent text and a keyed hash of their IP address as a record of consent for 3 years. The join screen for a Guest shows this line before the Guest asks to join:

This call may use live captions or Call Notes. A person who turns them on sends their own microphone audio to their browser maker's speech service. Other people's voices can be picked up from speakers. Call Notes only runs if everyone on the call accepts.

14.7 Today the Service does not convert speech to text on our servers, identify speakers, clone voices or generate images or video. You must not use the Service to clone a person's voice or likeness (Section A4 (Intimate images, deepfakes and likeness)).

14.8 Section 14 (Calls, Recordings and Call Notes) of the Privacy Policy gives the detail.

15. Prohibited Data and Restricted Data

15.1 Do not put Prohibited Data into NATEX Work. Do not send it to an AI Feature or through a Connected Service. Prohibited Data is:

• (a) Protected Health Information of a covered entity or business associate;
• (b) payment card numbers and security codes;
• (c) Social Security numbers and other government ID numbers of other people;
• (d) passwords, private keys and secrets that belong to other people;
• (e) other people's bank or financial account numbers;
• (f) biometric identifiers;
• (g) classified information and technical data controlled under the International Traffic in Arms Regulations or the Export Administration Regulations; and
• (h) data about children under 13.

A Seller's own payment instructions on an invoice or booking page are not Prohibited Data.

15.2 NATEX Work is not for Protected Health Information. We are not a business associate, and we do not sign business associate agreements (Section 16 (Professional, regulated and government use)).

15.3 The Integration Providers that connect your apps bar Protected Health Information, payment card data and "Special Data" on their services. Nango's terms use "Special Data" for HIPAA, PCI DSS and GLBA data. Do not send any of it through a Connected Service. This limit applies to data that travels through a Connected Service. Restricted Data that you enter directly is covered by Section 15.4.

15.4 You may store Restricted Data on your own authority and responsibility. We give no assurance that NATEX Work fits the rules that apply to it. Restricted Data is:

• (a) education records of adult students;
• (b) employment and candidate data;
• (c) privileged legal material;
• (d) financial institution customer information;
• (e) an individual's own wellness data; and
• (f) precise location.

15.5 If we find Prohibited Data, we may ask you to remove it, suspend the Workspace or the affected feature, and delete the data. We act on what we learn. We do not monitor your Workspace for Prohibited Data (Section A19 (No duty to monitor)).

15.6 Section A8 (Privacy) and Section A23 (Regulated data) repeat these limits for the AUP. Section 19 (Sensitive data) of the Privacy Policy says what we do with sensitive information.

16. Professional, regulated and government use

16.1 You are responsible for your own professional and regulatory duties when you use NATEX Work. That includes the duties of lawyers, health professionals, financial institutions, tax preparers, insurance licensees, real-estate professionals and employers. Nothing in the Service changes those duties.

16.2 We give no legal, tax, medical or financial advice. AI Features and Output are not professional advice. NATEX Work is not a health-care, therapy or crisis service. No Teammate or other AI persona holds a license, and none claims to. If you are in crisis in the United States, call or text 988. In an emergency, call 911.

16.3 We are not a law firm, we give no legal advice, and using NATEX Work does not create an attorney-client relationship. We do not promise that anything in NATEX Work is privileged or protected as attorney work product, and an AI conversation is not privileged because it is in NATEX Work. If you are a lawyer, you stay responsible for competence, confidentiality, client consent and supervision, and you decide whether AI Features are appropriate for your work and for your clients’ information.

16.4 Health: we are not a business associate, and we do not sign business associate agreements. A covered entity or business associate must not store Protected Health Information in NATEX Work. If we find Protected Health Information, we may ask you to remove it and suspend the affected Workspace or feature. If you tell us to, we will delete it without reading it.

16.5 Finance and tax: we give no assurance that NATEX Work meets the Gramm-Leach-Bliley Act, SEC Regulation S-P, state insurance data security laws or section 7216 of the Internal Revenue Code. Do not put Social Security numbers into NATEX Work. Do not send tax return information to AI Features. Section B17 (Regulated customers) lists what the DPA gives a regulated customer.

16.6 Real estate and housing: you are responsible for compliance with the Real Estate Settlement Procedures Act, fair housing law, lending law and the Fair Credit Reporting Act when you use NATEX Work.

16.7 Education: if you are a teacher or a school, you state that you have authority to enter Student Data. Everyone who holds an Account has told us that they are 18 or older. We do not claim to meet FERPA or COPPA, and we offer no school agreement. A school must not require students to connect personal accounts.

16.8 Records flagged as Student Data are excluded from the Assistant, search, Teammates and the Workspace ZIP. The Workspace ZIP leaves out Student Data other than the Admin’s own.

16.9 Employers: Section 36 (Added terms for Organization Customers) sets the duties of an Organization Customer that gives Accounts to its workers or students.

16.10 Government: NATEX Work is a commercial service. We have not assessed it for FedRAMP, StateRAMP or CJIS, and you must not put controlled unclassified information, classified information or criminal justice information into it. If you are a government entity, a term that you may not lawfully accept does not apply to you, to that extent. If the US Government acquires the Service, it is commercial computer software and a commercial service, and the Government's rights in it are limited to the rights in the Agreement. Public-records duties are yours.

16.11 NATEX Work is not a HIPAA, GLBA, FERPA, PCI or FedRAMP environment, and we make no certification claims (Section 21 (Security, confidentiality and shared responsibility)). Section 19 (Sensitive data) of the Privacy Policy and Section 20 (Age, children and where you live) of the Privacy Policy say what we do with this information.

17. Invoices, bookings and getting paid by your clients

17.1 At launch we do not process payments from your clients. Invoices and booking pages show the payment instructions you enter, such as bank details or a payment link. You are the seller to your clients, not us.

17.2 We do not verify your payment instructions. We are not a party to any payment between you and your clients, and we do not hold funds. Anyone who has an invoice link can see the payment instructions you enter. We do not charge a fee on payments between you and your clients.

17.3 You set your prices, refunds, cancellation terms and no-show terms. You are responsible for the taxes on your sales, and for following consumer-protection law and advance-payment law where you sell. Before a booker pays, tell them your cancellation, refund and no-show policies. Reminders on hosted invoices go out in your name.

17.4 You set your own invoice terms, late fees, interest and collection practices. You must follow debt-collection, usury and consumer-credit law. We do not collect debts.

17.5 NATEX Work is not an electronic-signature, identity-verification or notary service. A consent or waiver that someone gives on a form is not a verified signature. You decide whether a waiver or consent you collect is valid, and you keep your own records.

17.6 If we later offer client payments through Stripe Connect, we will publish the Seller Payments Terms, and you must accept them before you use that feature. They are not part of the Agreement now.

17.7 See also Section S1.12 (Taxes), Section S1.14 (Payment processing), Section A21 (Debt collection, consumer reports and restricted payment uses), Section A22 (Signatures and legal documents) and Section 12 (Payments and billing) of the Privacy Policy.

18. Your duties to the people whose data you handle

18.1 When your Content includes Personal Information about other people, you must have a lawful basis for handling it, and you must give the notices that the law requires.

18.2 Add your own notice about how you handle people's information to your forms, booking pages and invoices. The line we add (Section 8 (Public Pages, links and what you share)) does not replace yours. Give people the contact details of the Workspace Owner, and honor their requests.

18.3 Do not record anyone in secret. Before you record a Call, or make live captions or Call Notes of it, get the consent that the laws of every participant's place require. Some places require everyone's consent.

18.4 If you use Link Tracking, tell the recipients. We add this line to each tracked email:

This email uses link tracking: when you click a link, the time of the click is recorded for the sender. Your address, device and location are not.

We track clicks only. We do not track opens. If we cannot create the redirect, we send the email unchanged and without that line.

18.5 Follow the CAN-SPAM Act, Canada's anti-spam law and similar laws. Do not send unsolicited bulk email. The Service does not send text messages or place phone calls, and you must not use it to do so.

18.6 Do not collect Personal Information from anyone under 13. Do not use the Service for covert surveillance.

18.7 See also:

• Section B15 (Customer duties);
• Section A8 (Privacy);
• Section A10 (Spam and unsolicited messages);
• Section 16 (If your information is in someone else's Workspace) of the Privacy Policy; and
• Section 17 (If you use NATEX Work through someone else's Workspace) of the Privacy Policy.

19. Who is responsible for personal information

19.1 For Content, we are the Processor and the Customer is the Controller. We process Content on the Customer's documented instructions: the Agreement, the Customer's settings in the Service and the Customer's use of the API.

19.2 For Account Data and for billing, security, abuse, support and product-operations data, we are the Controller.

19.3 The Customer decides what Personal Information goes into its Workspace, and why.

19.4 If you use NATEX Work only for personal purposes, no other Controller decides what goes into your Workspace. We apply the rights in Section 26 (Your privacy rights) of the Privacy Policy to you directly.

19.5 Annex B (Data Processing Addendum) applies to you, with no signature, if you use the Service for business and your Content includes Personal Information about other people. That includes every Organization Customer and any Individual Customer who acts for a business. On how we process Personal Information in Content, Annex B controls.

19.6 Section 2 (Our two roles) of the Privacy Policy explains the same split for privacy purposes.

20. Export, deletion and retention

20.1 You can export your Content at any time. "Download my data" gives you your own records as a ZIP of JSON and CSV files, with the files you uploaded. You find it at Settings > Account > Download my data, and also at Settings > Data. It covers up to 50,000 records, with a limit of 8 MB per file, 40 MB of files and 3 exports per 10 minutes, and it caps AI messages and commands run at 20,000 each. It also includes your Personal Memory lines and whether memory is on, and a list of the AI accounts you connected (the provider, the last four characters of the key, the status and dates, never the key). It also includes your Acceptance Records, billing consent records, Call Notes answers, the Reports you filed and your privacy requests. An Admin can also use "Download workspace ZIP" at Settings > Admin > Data. The Workspace ZIP holds the non-deleted records of the Workspace. It leaves out private conversations that the Admin is not in and Student Data other than the Admin's own, and its manifest counts what it left out.

20.2 When you delete a record, it stays in the Trash Window for 30 days. Then the daily sweep erases it. An Admin can set chat messages, AI conversations and Teammate run records to be kept for 30 days, 90 days or 1 year (Settings > Admin > Data). A daily sweep deletes older chat messages and AI conversations for good, with no trash. Otherwise they stay until deleted. You can delete any one conversation with the Assistant ("Delete conversation" in the assistant history), or all of your AI history in a Workspace (Settings > AI > Delete all AI history), at any time. That erases the conversation from our servers at once, with its summary, its messages and the preferences that the Assistant learned from it. Records that you applied from a proposal stay. Deleting all of your AI history also deletes your Personal Memory in that Workspace and switches it off. Admins can read Members' conversations but cannot change or delete them.

20.3 You can delete your Account at Settings > Account > Delete my account. To protect you, we require that you type your sign-in email, that you signed in within the last 10 minutes, and that you give your two-factor code if two-factor authentication is on. We allow 5 attempts per 10 minutes. We remove your Stripe and Integration Provider connections first. If either removal fails, we delete nothing and you can try again.

20.4 If you own a Workspace that has other Members who are not Guests, you must choose for each one: hand it over to a named Member, or delete it for everyone. The default is the longest-standing other Admin or, if there is none, the longest-standing Manager, and then the longest-standing Member. A handed-over Workspace keeps its Paid Plan until the paid period ends, and your card stays on the Stripe customer until then. Only the Workspace Owner can delete a Workspace (Settings > Team > Delete this workspace).

20.5 Your Personal Memory and saved AI keys are deleted when you delete your Account, and your Personal Memory and keys in a Workspace are deleted when you leave it or an Admin removes you. Team Memory stays with a Workspace that continues and is deleted with the Workspace. Records you created in a Workspace that continues stay with that Workspace, and your authorship shows as "Deleted user". Chat messages stay with the conversation. We erase mail previews and private notes that you created. Calendar events and contacts that a mailbox sync created stay as Workspace records. We also delete the Gallery items you published, the calendar feeds you subscribed to, and invitations sent to your email address.

20.6 Deleting a Workspace or an Account cancels its Subscriptions at once, with no refund and no further charge. Deleting is not a request for a refund. If a refund right applies to you, take it first: use "End my plan now and get a prorated refund" in Settings > Billing, or ask under Section S1.10 (Refund Policy). Before you confirm a deletion that would cancel a prepaid Subscription, the delete screen shows the prepaid period that you would lose.

20.7 When you delete something, it leaves the live system at once or after the 30-day Trash Window. Copies in Backups are gone within 60 days. Uploaded files are not in Backups. Copies in the command log expire after 90 days. When you disconnect a Connected Service, we delete what it brought in, after showing you the list. Some information stays where our vendors keep it under their own terms: Composio can keep the content of tool calls for up to 1 year, Brevo keeps delivery logs, Stripe keeps the payment records it must keep, and Supabase and Cloudflare keep platform logs. We keep Acceptance Records, billing consent records and the records of refunds and objections for 7 years as evidence of your agreement and of what we did. The deletion audit row holds counts only, with no name, email or id, for 1,095 days. A Seller’s own Stripe account stays open when a Workspace is deleted.

20.8 We do not delete your Workspace because a Trial ends or a Paid Plan is cancelled. It moves to the Free Plan. Retention settings you choose, the 30-day Trash Window and the Free Plan’s storage limit still apply.

20.9 If we end your access for a reason that is not about your conduct, you have 30 days to export your Content, except where the reason is abuse or illegality (Section 26 (Suspension and termination)).

20.10 We handle Legal Holds as Section 22 (Government requests, civil subpoenas and Legal Holds) says. Section 23 (Retention Schedule and deletion) of the Privacy Policy lists how long we keep each category of information.

21. Security, confidentiality and shared responsibility

21.1 We use reasonable administrative, technical and physical safeguards to protect Content and Account Data. No security is absolute, and we cannot promise that no one will ever gain unauthorized access. Our safeguards include:

• (a) TLS for data in transit;
• (b) disk-level encryption at rest by our infrastructure vendors: AES-256 for the Supabase database disk, and AES-256-GCM at Cloudflare R2, with keys that the vendors manage (this does not encrypt Content inside the database from someone who has database access);
• (c) encryption of stored mailbox (IMAP) passwords and Webhook secrets in our own application, using AES-256-GCM;
• (d) storage of API Keys only as SHA-256 hashes;
• (e) separation of Workspaces by row-level security;
• (f) explicit approval for risky actions;
• (g) long random tokens in the links to Public Pages;
• (h) two-factor authentication, which a Workspace can require; and
• (i) card handling by Stripe, so that card data never reaches our servers.

21.2 We keep 14 daily and 8 weekly Backups, stored in two places, a Supabase Storage bucket and Cloudflare R2. Each Backup file is encrypted with AES-256-GCM in our own application before it is stored, and our storage vendors also encrypt their disks. We hold the key only as a server secret, kept apart from the Backups, plus one offline copy that our founder keeps. File names inside a Backup show table names.

21.3 You are responsible for securing your Members' credentials, your API Keys, your Webhook secrets and the permissions you give to Connected Services.

21.4 We make no claim that NATEX Work holds any security certification or audit report. NATEX Work is not a HIPAA, GLBA, FERPA, PCI or FedRAMP environment.

21.5 If a Security Incident affects your Content, we will tell the Workspace Owner and the Admins without undue delay and no later than 72 hours after we become aware that it happened, and we will include the information you need for your own notices. If a Security Incident affects Account Data about you, we will tell you without unreasonable delay and no later than 30 calendar days after we become aware of it, and we will notify you and regulators as the law of each affected state requires. Nothing here shortens a deadline that the law gives you or imposes on us.

21.6 Our Staff do not read your Content except to give support you ask for, to investigate security or abuse, or to comply with law. Access through our admin tools is recorded in the Staff Access Log, and your Admins can see the entries for your Workspace. Direct access to our database is limited to named, authorized Staff and is not recorded by the application. You consent to that access.

21.7 We treat Content that is not public as confidential to you, and we limit our access to it as Section 21.6 says. We are not responsible for secrecy lost through a Share Link, an API Key, a Third-Party Agent or a Connected Service, or through anything you make public (Section 8 (Public Pages, links and what you share), Section 12 (API, MCP Server and Webhooks), Section 13 (Connected Services)).

21.8 Section 21 (Security) of the Privacy Policy, Section B5 (Security measures) and Section B7 (Security Incident notice) give the detail.

22. Government requests, civil subpoenas and Legal Holds

22.1 We disclose Content only with your consent or on a warrant for Content, except for emergency disclosures and reports to the National Center for Missing and Exploited Children, as the law allows. The first exception is an emergency disclosure when someone faces danger of death or serious physical injury (18 U.S.C. § 2702). The second is a report to the National Center for Missing and Exploited Children (18 U.S.C. § 2258A). We give basic subscriber information on a subpoena and other records on a court order. Where the law allows, we direct the requester to the Workspace Owner. We tell the Workspace Owner (or, if you are an Individual Customer, you) before we disclose, unless a court order forbids notice or there is an emergency. Where an order forbids notice, we notify after it expires. Section 25 (Government requests, safety reports and copyright) of the Privacy Policy sets out the Law Enforcement Guidelines.

22.2 Requests in civil lawsuits for your Content, such as a subpoena or a discovery request, go to you and not to us. We will not give the contents of your Content to a party in a civil case unless you consent or a court order that the law allows requires it. You are responsible for keeping your own data for your legal duties, including turning off retention settings and exporting your data before anything is deleted. If you ask us in writing to pause our deletion jobs for a named Workspace, we will set a Legal Hold, which our Staff set and record. A Legal Hold does not pause the chat and AI-history period that an Admin sets, our general operational clean-up, or Backups. We keep our own records when we are told of a dispute.

22.3 Tell us promptly, at nshulman@natex.ai, if you receive legal process that affects the Service or our systems. Cooperate with us when we investigate a Security Incident.

23. Copyright

23.1 We respect intellectual property. We respond to notices of claimed copyright infringement, and we end the Accounts of Repeat Infringers. This Section is the notice of that policy to everyone who uses the Service.

23.2 Our Designated Agent is registered with the US Copyright Office as DMCA-1075734. The registration reads exactly as follows.

Margaret Alex Rabinovich Shulman (Margo), NATEX AI, 4184 Strathdale Ln, West Bloomfield Township, MI 48323-3139; 917-270-0443; nshulman@natex.ai

Registration: DMCA-1075734

Service: NATEX Work (work.natex.ai), a service of NATEX AI, Inc.

Alternate names on the registration: NATEX, NATEX AI, NATEX Work, NIX, NX-1, NX1, natex.ai, www.natex.ai, nix.natex.ai, nixapp.natex.ai, practice.natex.ai, work.natex.ai

23.3 To send a Notice of Claimed Infringement, email the Designated Agent at nshulman@natex.ai. We do not accept notices by phone. The notice must contain the six elements of 17 U.S.C. § 512(c)(3)(A):

• (a) a physical or electronic signature of a person authorized to act for the owner of the copyright;
• (b) identification of the copyrighted work that you claim was infringed;
• (c) identification of the material that you claim infringes, and information that lets us find it, such as a Gallery item id, a Share Link or a link to a channel message;
• (d) your contact information, including your address, telephone number and email address;
• (e) a statement that you believe in good faith that the use is not authorized by the copyright owner, its agent or the law; and
• (f) a statement that the information in the notice is accurate and, under penalty of perjury, that you are authorized to act for the owner.

If you knowingly misrepresent that material is infringing, you may be liable for damages under 17 U.S.C. § 512(f).

23.4 When we receive a Notice of Claimed Infringement that substantially complies with Section 23.3, we remove the material or disable access to it promptly. We tell the Customer who posted it and the Workspace Owner, and we keep a record. If a notice is missing an element, we will promptly try to contact you or take other reasonable steps to get a complete one. We may also remove material that we reasonably believe infringes, without a notice. We have no duty to monitor Content for infringement.

23.5 If we removed your Content and you believe we did so by mistake or because it was misidentified, you can send a Counter-Notice to the Designated Agent by email. It must contain the elements of 17 U.S.C. § 512(g)(3):

• (a) your physical or electronic signature;
• (b) identification of the material that we removed and of where it appeared before removal;
• (c) a statement, under penalty of perjury, that you believe in good faith that the material was removed by mistake or misidentification; and
• (d) your name, address and telephone number, a statement that you consent to the jurisdiction of the federal court for the address you give, and a statement that you will accept service of process from the person who sent the Notice of Claimed Infringement.

If you knowingly misrepresent that material was removed by mistake, you may be liable under 17 U.S.C. § 512(f).

23.6 When we receive a Counter-Notice, we send a copy to the person who sent the Notice of Claimed Infringement. We restore the material 10 to 14 Business Days after we receive the Counter-Notice, unless that person tells the Designated Agent that it has filed a court action. We may share a Notice of Claimed Infringement or a Counter-Notice with the other side.

23.7 A Strike is a removal that follows a Notice of Claimed Infringement that substantially complies with Section 23.3, or a court finding against an Account. We record each Strike in a ledger. A Strike is cleared if a Counter-Notice results in restoration. An Account that has 3 Strikes in 12 months, or 1 Strike for bad-faith or wholesale piracy, is a Repeat Infringer. We review the Account and end it. We may refuse a new Account to a Repeat Infringer.

23.8 Complaints about trademarks, trade secrets and publicity rights go to the same address. We do not promise any safe harbor for them, and we may act on them under the AUP (Section A7 (Intellectual property)).

23.9 Section 25 (Government requests, safety reports and copyright) of the Privacy Policy says how we handle the information in notices and Counter-Notices.

24. Reporting content, and our role as a host

24.1 We host Content that Customers put into the Service, and we are not the publisher of it. We may remove or restrict Content, or an Account, in good faith. We have no duty to monitor Content.

24.2 Output comes from AI Features at your request. We do not claim that the law protects us from responsibility for Output.

24.3 Anyone, including a Non-User, can send a Report. Use the Report control where it appears: on posts in public community channels, where no Account is needed, and on Gallery items, where you must be signed in. The reasons you can choose are Spam or scam, Harassment or hateful content, Illegal content, Copyright infringement, Intimate image shared without consent, Child safety and Something else. An intimate image or child safety Report is urgent: we hide the content from public view as soon as you send it, and we review it with priority. If the review dismisses the Report, we put the content back. You can add details of up to 2,000 characters and an email address. A Report about copyright needs an email address and follows Section 23 (Copyright). The Report control does not appear on Share Links or forms, so write to nshulman@natex.ai about those. We keep the reporter's email, if given, and a 400-character excerpt of what was reported, so that we can review it.

24.4 We review Reports. We may remove Content, or we may dismiss the Report. Each removal is recorded as Staff access in the audit log of the Workspace that held the Content. Section 25 (Government requests, safety reports and copyright) of the Privacy Policy says what a Report record holds and how long we keep it.

24.5 We provide a process for people shown in Content hosted on public parts of NATEX Work. If you appear in an intimate image or video that someone shared without your consent, or you represent that person, send an Intimate Image Request through the Report control (choose "Intimate image shared without consent") or by email to nshulman@natex.ai. A valid request contains:

• (a) your signature, physical or electronic;
• (b) information that lets us find the material, such as a link;
• (c) a brief statement that you believe in good faith that the image or video was published without your consent, with any information that helps us see that it was not consensual; and
• (d) your contact details.

We remove the material within 48 hours of a valid Intimate Image Request. We also make reasonable efforts to remove identical copies that we know about on the public parts of NATEX Work. We keep a record of each request and of what we did.

24.6 We report apparent child sexual abuse material to the National Center for Missing and Exploited Children, as required by law (18 U.S.C. § 2258A). We may preserve related data and disclose it without notice to you (Section A3 (Child safety)).

24.7 Section A18 (Reporting, enforcement and appeals) says what happens after a Report.

25. Acceptable Use

25.1 The Acceptable Use Policy (Annex A) is part of the Agreement. It applies to every Account, Member, Guest, Teammate, App, Plugin, Automation, API Key and Webhook.

25.2 The Workspace Owner answers for the Members of the Workspace and for the API Keys that belong to it.

25.3 Section A1 (Who this applies to) and Section A25 (What the Service does not do) say more.

26. Suspension and termination

26.1 You may stop using the Service at any time. To stop paying, cancel in one step (Section S1.7 (Cancelling)). You can also delete your Account (Section 20 (Export, deletion and retention)).

26.2 We may suspend or end your access for any of these reasons:

• (a) you breach the Agreement;
• (b) your use is a security risk to the Service or to other people;
• (c) the law requires it;
• (d) you do not pay; or
• (e) a vendor that the Service depends on requires it.

We give notice where we can. We may act at once, without notice, in child-safety, intimate-image and malware cases.

26.3 We use these steps: warn, remove Content, restrict sharing, suspend and terminate. We choose the step that fits the breach, and we may skip steps in serious cases.

26.4 You can appeal any action by email to nshulman@natex.ai within 30 days of the notice. We will review your appeal.

26.5 If we end your access for a reason that is not about your conduct, we refund the unused part of what you prepaid, as Section S1.10 (Refund Policy) says. You do not need to ask. You also have 30 days to export your Content. The export window does not apply where the reason is abuse or illegality.

26.6 We may suspend an Account that is used for unlawful tracking, surveillance or spam, or that breaches the privacy duties in Section 18 (Your duties to the people whose data you handle) or in the AUP.

26.7 If you become insolvent or file for bankruptcy, we will not rely on a right to end the Agreement because of that, where the Bankruptcy Code makes that right unenforceable. Your Content is not our asset, and we will not treat it as one.

26.8 When your Account ends, Section 20 (Export, deletion and retention) applies to your Content. The sections of the Agreement that by their nature continue after it ends, continue (Section 34 (General terms)).

27. Sanctions and export

27.1 You state that you are not a Restricted Party and that you are not in an Embargoed Jurisdiction. This statement continues for as long as you use the Service. You must not use the Service for a Restricted Party or in or for an Embargoed Jurisdiction. Tell us promptly if the statement stops being true.

27.2 Do not put into NATEX Work technical data that is controlled under the International Traffic in Arms Regulations or the Export Administration Regulations, or classified information (Section 15 (Prohibited Data and Restricted Data)).

27.3 We may suspend or end your access, and block access from a location, if we believe you have breached this Section or the law requires it.

27.4 NATEX Work is offered only in the Territory (Section 3 (Who can use NATEX Work)). An Organization Customer covers losses that arise from its breach of this Section (Section 37 (Organization Customers: liability and indemnity)). See also Section A17 (Sanctions and export). Section 20 (Age, children and where you live) of the Privacy Policy describes the country checks.

28. Disclaimer of warranties

THE SERVICE, THE AI FEATURES AND ALL OUTPUT ARE PROVIDED "AS IS" AND "AS AVAILABLE." TO THE FULLEST EXTENT THE LAW ALLOWS, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED. THAT INCLUDES ANY IMPLIED WARRANTY OF MERCHANTABILITY, ANY IMPLIED WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE AND ANY IMPLIED WARRANTY OF NON-INFRINGEMENT. WE DO NOT PROMISE THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE OR SECURE, OR THAT OUTPUT WILL BE ACCURATE OR COMPLETE. WE MAKE NO PROMISE ABOUT CONNECTED SERVICES, OTHER THIRD-PARTY SERVICES, APPS, PLUGINS OR GALLERY ITEMS.

28.1 This Section does not limit the commitments we make elsewhere in the Agreement, for example in Schedule 1, Section 21 (Security, confidentiality and shared responsibility) and Section 22 (Government requests, civil subpoenas and Legal Holds).

28.2 If a law that applies to you gives you a right that these Terms try to limit, the right applies and the limit is reduced only as far as the law requires.

29. Limitation of liability

This Section applies to Individual Customers, and to Members and Guests. Section 37 (Organization Customers: liability and indemnity) applies to Organization Customers.

TO THE EXTENT THE LAW ALLOWS, WE ARE NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE OR GOODWILL, EVEN IF WE KNEW THEY WERE POSSIBLE. OUR TOTAL LIABILITY FOR ALL CLAIMS RELATING TO THE SERVICE IS LIMITED TO THE GREATER OF $100 IN US DOLLARS AND WHAT YOU PAID US FOR THE SERVICE IN THE 12 MONTHS BEFORE THE EVENT THAT GAVE RISE TO THE CLAIM.

29.1 These limits do not apply to liability for fraud, willful misconduct, gross negligence, violation of law or personal injury, or to any other liability that the law does not allow us to limit. Nothing in this Section limits a remedy that a statute of the state where you live gives you and does not allow to be limited.

29.2 If a law that applies to you gives you a right that these Terms try to limit, the right applies and the limit is reduced only as far as the law requires.

30. Governing law and where claims are brought

30.1 Delaware law and the Federal Arbitration Act govern the Agreement and every dispute between you and us, without regard to conflict-of-laws rules. If a law that applies to you gives you a right that these Terms try to limit, the right applies and the limit is reduced only as far as the law requires. For example, the Michigan Consumer Protection Act, and every consumer protection statute of the state where you live, still apply to you.

30.2 If you are an Individual Customer, the place of any arbitration and the venue of any court action is the county where you live (or the equivalent in a territory).

30.3 If you are an Organization Customer, the state and federal courts in New Castle County, Delaware, have exclusive jurisdiction over any dispute that is not arbitrated. The Organization Customer and we consent to personal jurisdiction and venue there.

31. Arbitration and class action waiver

31.1 This Section affects your legal rights, so please read it carefully. Except for the matters in Sections 31.10 to 31.12, you and we agree to resolve every dispute between us by individual arbitration. No court will hear it, no judge or jury will decide it, and it cannot go forward as a class action. You can opt out within 30 days (Section 31.14).

31.2 This Section covers every claim and dispute between you and NATEX AI, Inc. that arises out of or relates to the Service, the Agreement or the Privacy Policy. It does not matter whether the claim is based on contract, tort, statute or anything else, or whether it arose before or after you first accepted an arbitration agreement with us. This Section does not apply to a lawsuit or arbitration that was already pending on the day you accepted it. A later change to this Section applies only as Section 32.5 says. This Section also covers a dispute with our Staff, our officers or our Sub-processors that arises from their work for us on the Service, and they may enforce this Section.

31.3 Before either of us starts an arbitration, we first try to resolve the dispute informally. Write to nshulman@natex.ai with your name, your Account email, a description of your claim and the relief you want. If we have a claim against you, we send you the same information at your Account email. The notice must be signed personally by the claimant and sent from the Account email, and one notice sent for several people does not meet this step. Each of us then has 30 days to try to resolve the dispute, and the time limit for bringing the claim stops running during those 30 days. You need not follow this step before you go to small claims court or seek the relief described in Sections 31.10 to 31.12.

31.4 The American Arbitration Association (the AAA) administers the arbitration. For an Individual Customer, the AAA Consumer Arbitration Rules and Consumer Fee Schedule apply. For an Organization Customer, the AAA Commercial Arbitration Rules apply. If it is unclear which rules apply, the AAA decides. The arbitrator may dismiss a claim that shows no individual injury.

31.5 The arbitrator decides every dispute about whether this Section applies, about its scope and about whether it is enforceable. A court decides, instead, whether an agreement to arbitrate with us was formed and which agreement controls if two agreements conflict. A court also decides whether the class action waiver in Section 31.9 is enforceable.

31.6 Hearings are by video or telephone unless a party asks for an in-person hearing. If you are an Individual Customer and you ask, we hold an in-person hearing in the county where you live (or the equivalent in a territory). For an Organization Customer, the arbitrator decides where an in-person hearing is held. For claims of $25,000 or less, the arbitrator decides on documents alone, unless a hearing is needed.

31.7 If you are an Individual Customer, the AAA Consumer Fee Schedule applies. You pay no more than the filing fee, which is $225. We pay all other AAA fees and the arbitrator's compensation. Neither of us pays the other's fees because we lose. Each of us pays our own lawyers, unless the law lets the arbitrator award fees. The arbitrator may award any relief that a court could award. For a claim of $10,000 or less, we reimburse your $225 filing fee if you ask. If you are an Organization Customer, the fee schedule of the AAA Commercial Arbitration Rules applies.

31.8 The arbitrator must follow the law and the Agreement. The award is final and binding on you and us, and a court that has jurisdiction may enter judgment on it.

Class action waiver

31.9 Subject to Section 31.10, you and we may bring claims against each other only in an individual capacity, and neither of us may act as a plaintiff or class member in any class, collective or representative proceeding. The arbitrator may not combine more than one person's claims, except as Section 31.13 allows, and may not preside over a class, collective or representative proceeding. The arbitrator may award relief only to the individual party who asks for it, and only as needed for that party's own claim. If a court decides that this waiver is unenforceable for a claim, that claim must be brought in court, and it is stayed until the individual arbitrations are finished. The rest of this Section stays in effect.

31.10 Either of us may ask a court for public injunctive relief. If a court decides that the law prevents that relief from being arbitrated, the claim stays in court. The court may stay it until the individual arbitration of the other claims is finished, to the extent the law allows a stay.

31.11 Either of us may bring an individual claim in small claims court in the county where you live (or the equivalent in a territory) instead of arbitration, if the claim qualifies.

31.12 These exceptions apply equally to you and to us. Either of us may go to court to stop the infringement or misuse of intellectual property or confidential information, and to enforce an arbitration award. Either of us may report to a government agency or cooperate with one. A copyright claimant is not a party to the Agreement. A Notice of Claimed Infringement follows Section 23 (Copyright) and the statute, outside this Section.

31.13 If 25 or more similar demands are filed by or with the same counsel, the AAA's Mass Arbitration Supplementary Rules and its Consumer Mass Arbitration Fee Schedule apply. We will not use a process that lets the result in one case bind a person who did not take part in it, and we will not limit coordinated representation by counsel. The time limit for each claimant stops running while the AAA runs a coordinated process, and a claimant may opt out of that process and proceed alone.

How to opt out

31.14 You can opt out of this Section 31. To do so, send us a written notice within 30 days after you first accept the Terms. If you accept this Section 31 for the first time through the update dialog, the 30 days start on the day you accept. Send it by email to nshulman@natex.ai or by post to NATEX AI, Inc., 16192 Coastal Highway, Lewes, DE 19958. The subject line of the email, or the heading of the letter, must read "Arbitration Opt-Out". The notice must include your name, your Account email and a statement that you opt out. Opting out affects only this Section 31. Your other rights and duties under the Agreement do not change, and a dispute that you opted out of is decided in court under Section 30 (Governing law and where claims are brought). If you opt out, you and we still agree to bring any court claim only in an individual capacity, to the extent the law allows. If we change this Section 31, you get a new 30-day opt-out (Section 32 (Changes to the Terms)).

31.15 If you are an Individual Customer, you do not waive a jury trial. If you are an Organization Customer, you and we waive any right to a jury trial in any court proceeding relating to the Agreement, to the extent the law allows. If an Organization Customer starts a court proceeding about a dispute that this Section covers, the court must stay the proceeding, not dismiss it, while the arbitration goes ahead.

31.16 Nothing in this Section stops you from speaking or writing about a dispute (Section 34 (General terms)).

32. Changes to the Terms

32.1 We may change the Terms. A Material Change is a change that reduces your rights, changes the Arbitration Agreement, or lets us use information we already collected in a materially different way. A change of price is not a Material Change (Section 32.9).

32.2 For a Material Change, we give you at least 30 days' notice. We email your Account address, with the subject line "Updated Terms of Service", and we show a notice in NATEX Work until the Effective Date. The change takes effect on the Effective Date in the notice.

32.3 On the Effective Date, the next time you load a page other than the legal pages, a dialog asks you to accept the new version. It shows a short summary of the change, links to the new documents, a box that starts unticked, and the choices "Accept and continue" and "Sign out". The dialog also links to "Download my data". It shows the label of the acceptance box, the bold summary of Section 31 (Arbitration and class action waiver) and the opt-out link. It says that your 30 days to opt out start on the day you accept the update. Declining to accept is not an opt-out; it only keeps you from using your Account. You accept a Material Change only by that click.

You do not have to accept. The dialog says so, and it has a button, "I don't accept — cancel my plan". That button opens a page where nothing is accepted and nothing in your Workspace opens. We record that you did not accept. On that page you can:

• (a) download your data ("Download my data");
• (b) if you are an Admin of a Workspace with a Paid Plan, cancel it at the end of the period you paid for ("Cancel subscription"), after which nothing is refunded;
• (c) if you are an Admin of such a Workspace, end the plan now and get a prorated refund ("End my plan now and get a prorated refund"). The amount is shown before you confirm, and Section S1.10 (Refund Policy) says how it is worked out; and
• (d) delete your Account (Section 20 (Export, deletion and retention)).

You can also cancel by writing to nshulman@natex.ai from your Account address. If you accept the update later, the choice in (c) lapses.

32.4 A change that is not a Material Change takes effect when we post it, and we add it to the version history at /legal/history.

32.5 A change to Section 31 (Arbitration and class action waiver) applies only to disputes that arise after the change takes effect. You get a new 30-day opt-out. Continuing to use the Service is never assent to a new term of the Arbitration Agreement.

32.6 If you object to a Material Change, you can cancel without accepting it. Choose "I don't accept — cancel my plan" in the update dialog, or write to nshulman@natex.ai from your Account address. You choose how your cancellation takes effect. If you end your plan now, we end your access that day and refund the unused part of what you prepaid, as Section S1.10 (Refund Policy) says. If you keep your access to the end of the paid period, you have used what you paid for and there is nothing to refund. You do not need to ask for the refund.

32.7 You can read earlier versions of the Terms, with their Effective Dates, at /legal/history.

32.8 Section 29 (Changes to this Privacy Policy) of the Privacy Policy works the same way for the Privacy Policy. Section S1.6 (Price changes) covers changes to prices.

32.9 A price change is made under Section S1.6 (Price changes). It does not need your re-acceptance. If you do not cancel before the new price applies, it applies from your next renewal.

33. Notices and electronic communications

33.1 We give you notice by email to your Account address and by notices inside the Service. A notice is effective when we send it to the email address on your Account. You are responsible for keeping that address current (Section 2 (Accepting these Terms)).

33.2 Send legal notices to us by email to nshulman@natex.ai or by post to NATEX AI, Inc., 16192 Coastal Highway, Lewes, DE 19958. A notice by email is effective when it is sent. A notice by post is effective when it is delivered. Section 31.14 sets the method for an arbitration opt-out.

33.3 Receipts, security messages, billing notices, notices about changes to the Agreement and other service messages are not marketing. You cannot opt out of them while you have an Account. We send marketing email only if you opt in. We do not send text messages (SMS). Section 13 (Email we send) of the Privacy Policy and Section 30 (Contact and accessibility) of the Privacy Policy describe the same messages and contact details.

33.4 Section 2.5 sets out your consent to receive notices electronically.

34. General terms

34.1 We do not restrict reviews, and we do not bar you from speaking about us or about a dispute. Confidentiality rules that apply in arbitration do not stop you from speaking about a dispute.

34.2 Neither of us is liable for a delay or failure caused by events beyond our reasonable control. Those include failures of hosting, cloud, AI model, payment, email, Connected Service, telecommunications and DNS providers, and widespread internet or cyber-attack disruption that we could not have prevented by maintaining reasonable security. The affected party must give notice and take reasonable steps to limit the effect. This does not excuse a payment duty, a duty to give notice of a Security Incident, or a duty to delete data.

34.3 We may assign the Agreement, and transfer Account Data to a successor, in a merger, acquisition, reorganization or sale of assets, on notice to you. You may not assign the Agreement without our written consent. The successor must honor the Privacy Policy for information collected under it (Section 28 (If our business changes hands) of the Privacy Policy).

34.4 The Agreement is the entire agreement between you and us about the Service. It replaces earlier terms about the Service.

34.5 If a court or an arbitrator finds a part of the Agreement unenforceable, the rest stays in effect. For an Organization Customer, we also apply that part as far as the law allows. Section 31.9 has its own rule for the class action waiver.

34.6 If we do not enforce a right right away, we have not given it up. A waiver is effective only if it is in writing.

34.7 The parts of the Agreement that by their nature continue after it ends, continue. They include Sections 2.6, 6.3 to 6.5, 7, 20, 21, 22, 23, 26 and 28 to 37, the clauses of Schedule 1 on refunds that are due, and Section B9 of Annex B.

34.8 Nobody other than you and us has rights under the Agreement. That includes our vendors and the Connected Services. The one exception is Section 31.2, which our Staff, officers and Sub-processors may enforce.

34.9 The Agreement does not create a partnership, a joint venture or an employment relationship between you and us.

Part B: Added protections for Individual Customers (Section 35)

35. Added protections for Individual Customers

35.1 This Part B applies to every Individual Customer. It also applies to every natural person who accepts the Terms for themselves, including a Member or a Guest of an Organization Customer's Workspace. A person who accepts the Terms only for an Organization Customer is not an Individual Customer for that acceptance.

35.2 You give us no indemnity. If you breach the Agreement, our remedies are to remove Content, to suspend or end your access, and to use the ordinary remedies that the law gives us.

35.3 No term of the Agreement shortens the time that the law gives you to bring a claim.

35.4 Your protections as an Individual Customer are spread through the Agreement. In one place, they are:

• (a) the rule in Section 1.3 that the term that protects you more applies;
• (b) the cap and the carve-outs in Section 29 (Limitation of liability);
• (c) the savings sentence in Section 30 (Governing law and where claims are brought), and the county where you live as the venue;
• (d) in Section 31 (Arbitration and class action waiver), the AAA Consumer Rules, a filing fee of no more than $225, no jury waiver, the small claims exception and the 30-day opt-out;
• (e) in Section 32 (Changes to the Terms), the rule that a change to Section 31 (Arbitration and class action waiver) applies only to later disputes and gives you a new opt-out; and
• (f) in Schedule 1, the Refund Policy (Section S1.10 (Refund Policy)) and one-step cancellation (Section S1.7 (Cancelling)).

35.5 Where Part A and this Part B differ for you, the term that protects you more applies.

Part C: Added terms for Organization Customers (Sections 36 and 37)

36. Added terms for Organization Customers

36.1 If a person accepts the Terms for an Organization Customer, that person states that they have authority to bind it, and the Organization Customer is bound by the Agreement. The person does not become a party to the Agreement in their own right by accepting for it.

36.2 An Organization Customer is responsible for its Members, its Guests and the API Keys of its Workspace, and for their compliance with the AUP.

36.3 You need to know what each role can see so that you can give your Members the notices that your law requires. Every Member of a Workspace, except Guests, can see:

• (a) who is in the Workspace, with roles and last-active times;
• (b) the Workspace's records, tasks, files and open channels;
• (c) which Connected Services are connected, with their status and account email; and
• (d) the items that Connected Services bring into the Workspace: calendar events, chat messages from Slack and Microsoft Teams, Zoom meetings, issues from GitHub, GitLab and Jira, and files from Google Drive and OneDrive, unless the Workspace restricts them; and the email previews and sent mail of a mailbox that has been shared with the Workspace (a mailbox is private to the Member who connected it until that Member or an Admin shares it, and Guests never see a shared mailbox).

Private notes, form submissions and assignment submissions are limited to their author and to Admins and Managers. The Workspace Owner and the Admins can also see:

• (e) every Member's AI conversations in the Workspace, which they can read but cannot change or delete;
• (f) the audit log of changes, including entries labelled "NATEX staff" that show our Staff's access to the Workspace; and
• (g) Exports, where the Workspace ZIP leaves out private conversations that the Admin is not in, the mail previews of other Members' mailboxes that are not shared, and Student Data other than the Admin's own.

If an Admin switches on Team Memory, every Member except Guests can also read it, and it can include mail from a mailbox that has been shared with the Workspace for as long as that mailbox stays shared. An Admin can switch a connected mailbox's sharing on or off, including a mailbox that another Member connected; each change is written to the audit log, the Member who connected the mailbox is told in NATEX Work, and sharing is off until it is switched on. Admins cannot see the email previews and sent mail of another Member's mailbox that is not shared, direct messages, group chats and private channels that they are not part of, the preferences that the Assistant has learned about a Member, a Member's Personal Memory, or the AI accounts a Member connected. An Admin can switch Own AI Accounts off for the whole Workspace (Section 9.13); until an Admin does, a Member can connect one. Presence and focus-room features show a Member's activity to other Members. Settings > Privacy shows this list inside NATEX Work, under "What your workspace admin can see". No setting hides AI conversations from Admins.

36.4 We keep AI conversations until they are deleted, unless an Admin sets 30 days, 90 days or 1 year. The Workspace Owner and the Admins can read Members’ AI conversations in their Workspace. Each person can delete the preferences the Assistant has learned about them. Only the Member who had a conversation can change or delete it.

36.5 You must give your Members the monitoring notices that your law requires. Do not require a Member to connect a personal account to the Workspace. Members should not connect personal accounts to an employer or school Workspace. Do not use Admin access to read connected personal mailboxes, and do not watch Members' AI conversations in secret.

36.6 Annex B (Data Processing Addendum) applies to you (Section 19 (Who is responsible for personal information)). Section 17 (If you use NATEX Work through someone else's Workspace) of the Privacy Policy tells your Members what Admins can see.

36.7 For an Organization Customer, a change that reduces the protection of any of the following takes effect only at your next renewal or on your written agreement:

• (a) Annex B (Data Processing Addendum);
• (b) Section 21 (Security, confidentiality and shared responsibility); or
• (c) Section 6 of the Privacy Policy, as Section B13.2 of Annex B incorporates it.

37. Organization Customers: liability and indemnity

37.1 This Section applies to Organization Customers. Our total liability to an Organization Customer for all claims relating to the Service is limited to the greater of $100 and what it paid us for the Service in the 12 months before the event that gave rise to the claim. Sections 37.3 and 37.4 change this limit.

37.2 We are not liable to an Organization Customer for indirect, incidental, special, consequential, exemplary or punitive damages, or for lost profits, revenue or goodwill, even if we knew they were possible.

37.3 For a claim that arises from a Security Incident, or from our breach of Annex B or Section 21 (Security, confidentiality and shared responsibility), our total liability is limited to the greater of two amounts. The first is 2 times what the Organization Customer paid us for the Service in the 12 months before the event. The second is $5,000. This limit applies instead of the limit in Section 37.1. The two limits are not added together.

37.4 The limits in this Section do not apply to fraud, willful misconduct, gross negligence or any liability that the law does not allow us to limit. If a law that applies to you gives you a right that these Terms try to limit, the right applies and the limit is reduced only as far as the law requires.

37.5 An Organization Customer will defend us, our Staff and our officers against claims brought by anyone else. It will also pay the damages and costs that a court or arbitrator awards, or that it agrees to in a settlement. This applies to the extent the claim arises from:

• (a) the Organization Customer's Content, or inputs that break the law or anyone's rights;
• (b) claims by people the Organization Customer serves through the Service, such as clients, bookers and people who fill in its forms;
• (c) the Organization Customer's breach of the AUP;
• (d) Agent Actions taken under the Organization Customer's Workspace or API Keys; and
• (e) losses that arise from the Organization Customer's breach of Section 27 (Sanctions and export).

This does not apply to the extent the claim arises from a defect in the Service or from our breach of the Agreement.

37.6 We must give the Organization Customer prompt notice of a claim. The Organization Customer controls the defense and settlement, and we cooperate at its cost. The Organization Customer may not settle a claim in a way that admits fault by us or imposes an obligation on us without our consent. We may take part with our own lawyers at our own cost.

37.7 We give no indemnity to an Organization Customer for a Security Incident. Our liability for it is limited by Section 37.3.

37.8 An Organization Customer waives a jury trial, as Section 31.15 says.

37.9 We will defend an Organization Customer against a claim brought by someone else that the Service itself infringes a United States patent or copyright or misappropriates a trade secret. We will pay the damages and costs that a court or arbitrator awards, or that we agree to in a settlement. This does not apply to Output, Content, Apps, Plugins, Gallery items or Connected Services, or to a claim that arises from the Organization Customer's use of the Service in breach of the Agreement. The Organization Customer must give us prompt notice, let us control the defense and settlement, and cooperate at our cost. Our liability under this paragraph counts toward the limit in Section 37.1 and is not added to it.

Schedule 1. Plan and Billing Terms

NATEX Work is sold by NATEX AI, Inc., a Delaware corporation operated from Michigan. Registered office and address for legal notices: 16192 Coastal Highway, Lewes, DE 19958. Contact: nshulman@natex.ai. Stripe processes payments for us, and we never receive your card number.

This schedule is shown to you before you pay.

This schedule is part of the Agreement. It says what you buy, how it renews, how you cancel and when we refund. If another part of the Agreement conflicts with this schedule about billing, this schedule controls.

S1.1 Plans and prices

S1.1.1 Prices are in US dollars and are before tax. Section S1.12 (Taxes) explains tax. We charge in US dollars only.

S1.1.2 The Paid Plans are Solo, Team, Business and Scale. The price of each Paid Plan, the number of people it includes and the price of an Extra Person are the prices shown on our Pricing page and at checkout. Checkout shows the price you will pay before you pay it. The prices are not part of the Terms, so a change of price is not a change to the Terms (Section S1.6 (Price changes)).

S1.1.3 You can pay monthly or yearly. A yearly Paid Plan is charged once a year, up front, at the yearly price shown on the Pricing page and at checkout.

S1.1.4 An Extra Person is a separate line on the same Subscription as the Paid Plan. Solo has no Extra Persons. We never add an Extra Person on our own. Section S1.8 (Add-Ons, Extra Persons and mid-period changes) explains how an Extra Person is added and charged.

S1.1.5 Add-Ons are recurring extras for a Paid Plan: AI Power, extra storage (100 GB each, quantity 1 to 50) and an extra mailbox (quantity 1 to 50, for Team, Business and Scale only). AI Power is priced by Paid Plan. The prices of the Add-Ons are shown on our Pricing page and at checkout.

S1.1.6 The AI Command Pack is 600 AI commands, charged once at the price shown on our Pricing page and at checkout. It does not renew. Section S1.13 (AI Command Pack) explains it.

S1.1.7 Plan, interval, Extra Person and Add-On quantity changes made in the middle of a Billing Period are prorated. Section S1.8 (Add-Ons, Extra Persons and mid-period changes) explains how.

S1.1.8 Usage limits for each Paid Plan, such as AI commands a day, searches and storage, are on the Pricing page and in Settings > Billing. They can change. AI Features that run on a Member's Own AI Account do not use the Workspace's AI commands, and that provider bills the Member, not us. Workspace Memory and the "Ask your work" tab also have a separate daily budget for each Workspace, which is not a Paid Plan allowance (Section 9.11 of the Terms). If we make a change to them that is materially worse for you, clause 3 of the Refund Policy in Section S1.10 (Refund Policy) applies.

S1.1.9 Workspaces on prices set before September 30, 2026 keep their price until a price-change notice. Section S1.6 (Price changes) explains that.

S1.2 Checkout, consent and what you agree to

S1.2.1 Before you pay, the checkout screen shows you:

• (a) what you are buying, and how many people it covers;
• (b) the price and the Billing Period;
• (c) the tax statement in Section S1.12 (Taxes);
• (d) that the purchase renews automatically until you cancel it;
• (e) the renewal term;
• (f) the date of the first renewal;
• (g) the price you will pay. The Trial needs no card and never charges you, so there is no second price that starts when the Trial ends;
• (h) how to cancel;
• (i) the Refund Policy;
• (j) the seller's name and address;
• (k) that there is no minimum commitment beyond the Billing Period you are paying for;
• (l) that tax may be added to the recurring amount, as the tax statement says; and
• (m) a link to this schedule.

Stripe Checkout repeats the price, the renewal terms, the no-minimum-commitment line, the cancel path, the tax statement, a short form of the Refund Policy, the seller's name and address, and the link, next to its pay button.

S1.2.2 For a Team plan billed monthly, the renewal sentences read as follows. A yearly purchase says "every year" in place of "every month". The date shown is an example.

Charged $69 today. Then it renews automatically every month at the then-current price ($69 today) until you cancel. First renewal: Nov 8, 2026.

Every recurring purchase also shows this line, in the disclosure, in the record we keep and in the Stripe Checkout text:

No minimum commitment beyond the period you are paying for. Cancel any time in Settings > Billing.

For an Add-On, those sentences add the following:

Each add-on and extra-seat line renews on its own and can be cancelled on its own.

For the AI Command Pack, they read as follows:

This is a one-time purchase. It does not renew and starts no subscription.

S1.2.3 You agree to automatic renewal as a separate act, in two boxes. Both boxes start unticked, and the button stays disabled until you tick both. We do not charge you until you tick both boxes and press the button. Box 1 holds only your consent to the renewal terms. For a Team plan billed monthly at $69, it reads as follows. The plan name, the Billing Period and the price change to match what you buy.

I understand that Team renews automatically every month at $69 (plus tax, if any) until I cancel, and that I can cancel any time in Settings > Billing.

Box 2 holds your agreement to the contract terms. The words "Plan and Billing Terms" link to this schedule. It reads as follows.

I agree to the Plan and Billing Terms and the refund policy.

The button next to the boxes reads "Subscribe and agree to renew automatically". The AI Command Pack has no boxes because it does not renew. Its button names the price and says that it is charged once.

S1.2.4 A change to an existing Subscription shows you the amount, the way Stripe prorates it and the renewal terms, and asks you to confirm before it applies.

S1.2.5 Before we send you to Stripe, we save a billing consent record. It holds:

• (a) your Workspace and your Account;
• (b) what you bought: the Paid Plan or Add-On, the interval, the quantity and the price;
• (c) the version of the Plan and Billing Terms (this schedule);
• (d) the exact text you saw, including the label of each box, and a SHA-256 fingerprint of that text;
• (e) your browser's user-agent text;
• (f) a keyed hash of your IP address (never the address itself) and a two-letter country code; and
• (g) the Stripe session id and the time in UTC.

If we cannot save the record, we do not charge you. We keep the record for 7 years from the purchase. It survives the deletion of your Account or Workspace, because it is evidence of the contract. Section 12 (Payments and billing) of the Privacy Policy describes the billing consent record and the billing notices.

S1.2.6 Nothing in the Agreement is meant to interfere with, contradict or undermine the consent you give at checkout. If any other part of the Agreement could be read that way, the checkout terms and this schedule control.

S1.3 Confirmation email

S1.3.1 Right after every Subscription purchase, whether a Paid Plan or an Add-On, we email every Admin of the Workspace. The email states:

• (a) what you bought and the price;
• (b) that it renews automatically, how long each renewal runs (a month or a year) and the next Renewal Date;
• (c) how to cancel, with the path and a link;
• (d) the Refund Policy;
• (e) the price-change promise in Section S1.6 (Price changes);
• (f) the tax statement in Section S1.12 (Taxes); and
• (g) who the seller is.

S1.3.2 The email is a service message. You cannot opt out of it.

S1.4 Renewals and reminders

S1.4.1 A Subscription renews automatically on its Renewal Date, for the same Billing Period and at the then-current price, until you cancel it.

S1.4.2 We email you 30 days before a yearly renewal, and once a year before a monthly plan's anniversary renewal.

S1.4.3 In detail, the reminders work like this:

• (a) For a yearly Paid Plan or a yearly Add-On, we send an email on the calendar day that is 30 days before the Renewal Date.
• (b) For a monthly Paid Plan or a monthly Add-On, we send an email once a year, 30 days before each anniversary renewal. We count the anniversary from the day the Subscription started. The email says that the Subscription keeps renewing monthly until you cancel it.
• (c) Each reminder shows the product, the price, the Renewal Date, how to cancel and a link. A reminder for a yearly renewal also shows the refund in clause 2 of the Refund Policy.

S1.4.4 After each automatic renewal of a Paid Plan, we email a renewal notice. It shows the amount, the next Renewal Date, a cancel link and the Refund Policy.

S1.4.5 We send these emails to every Admin of the Workspace. They come from noreply@natex.ai through Brevo. Replies go to nshulman@natex.ai. The footer shows the seller's name and address. These are service messages, and you cannot opt out of them. Dates in them are UTC calendar dates. Section 12 (Payments and billing) of the Privacy Policy describes the billing notices.

S1.5 Trial and Free Plan

S1.5.1 Every new Workspace gets a Trial. The Trial lasts 14 days, is for up to 5 people and works at Team level, with set total amounts of usage. It needs no card and never charges you. The Trial is not a Subscription.

S1.5.2 The total amounts for the whole Trial are:

• (a) 150 AI commands in total;
• (b) 25 deep searches;
• (c) 3 Teammate runs;
• (d) 3 App generations;
• (e) 10 web searches;
• (f) 500 integration calls;
• (g) 1 mailbox;
• (h) 2 connected-app connections;
• (i) 1 GB of storage;
• (j) 50 outbound emails; and
• (k) 2 deep Assistant turns a day, which count inside the 150 AI commands.

S1.5.3 When the Trial ends, this is what happens:

The 14-day trial needs no card and never charges you. When it ends your workspace moves to the Free plan, which costs nothing, and nothing you made is deleted. You are only ever charged after you choose a plan and confirm it.

S1.5.4 We email every Admin 5 days before the Trial ends. The email gives the end date and says that no charge happens because no card is on file. It also says that the Workspace moves to the Free Plan, that nothing is deleted, and how to choose a plan.

S1.5.5 A Paid Plan starts only when an Admin picks one and confirms the checkout disclosure in Section S1.2 (Checkout, consent and what you agree to). A Trial that ends does not turn into a Paid Plan.

S1.5.6 The Free Plan costs nothing. It is not a Subscription and never renews. It is for 1 person and has these limits:

• (a) 3 AI commands a day;
• (b) 1 App generation a month;
• (c) 3 web searches a month;
• (d) 5 deep searches a month;
• (e) 20 outbound emails a month;
• (f) 0.25 GB of storage; and
• (g) no mailbox, no connected apps and no Teammates.

S1.5.7 We do not delete your Workspace because a Trial ends or a Paid Plan is cancelled. It moves to the Free Plan. Retention settings you choose, the 30-day Trash Window and the Free Plan's storage limit still apply.

S1.5.8 Section 20 (Export, deletion and retention) and the Retention Schedule in Section 23 (Retention Schedule and deletion) of the Privacy Policy describe what is kept and for how long.

S1.6 Price changes

S1.6.1 This is what we promise about price changes:

If the price changes we email you 30 days before it applies, with the new price and how to cancel. Yearly customers keep their price until their next renewal.

S1.6.2 We send the notice to every Admin of the affected Workspace, on the day that is 30 days before the new price applies. It shows the old price and the new price, the date the new price applies, how to cancel, and the refund in clause 3 of the Refund Policy. We do not charge a new price before that date, and a new price applies only from your next renewal on or after that date. Prices are shown on our Pricing page, so a change of price is not a change to the Terms.

S1.6.3 A price increase is not a Material Change and does not need your re-acceptance. You can cancel before it applies. If you cancel within 30 days of our notice and choose to end your plan now, we refund the unused part of what you prepaid. Clause 3 of the Refund Policy and Section S1.10 (Refund Policy) say how. You do not need to ask for the refund. If you keep your access to the end of the paid period, there is nothing to refund. If you do not cancel, the new price applies from your next renewal.

S1.6.4 Workspaces on prices set before September 30, 2026 keep their price until a price-change notice reaches them. We do not publish those older prices.

S1.6.5 Section 32 (Changes to the Terms) governs changes to the rest of the Agreement. Section 32.9 says that a price change does not need your re-acceptance.

S1.7 Cancelling

S1.7.1 This is how cancelling works:

Cancel any time in one step: Settings > Billing > Cancel subscription. No call, email or reason is needed. Cancelling stops the next renewal; you keep everything you paid for until the end of the paid period, then the workspace moves to the Free plan and keeps your data.

S1.7.2 An Admin cancels in Settings > Billing. "Cancel subscription" cancels the Paid Plan. The "Cancel AI Power / storage / mailboxes" buttons cancel each Add-On. One confirmation dialog states the end date. We do not ask for a reason, show a survey or make a discount offer on the way to cancelling. Where Section S1.10.6 gives you a refund right, a second button, "End my plan now and get a prorated refund", appears beside "Cancel subscription".

S1.7.3 A cancellation takes effect at the end of the Billing Period you paid for. It does not end your access early, except where you choose to end it now and take a refund under Section S1.10.6. Cancelling does not by itself refund the current Billing Period; the Refund Policy decides that. We save the cancellation at once and email a confirmation with the end date.

S1.7.4 Cancelling the Paid Plan also stops its Add-Ons from renewing. Each Add-On ends at the end of its own Billing Period and gets its own confirmation email. You can also cancel one Add-On and keep the rest.

S1.7.5 Until the Billing Period ends, you can undo a cancellation at no charge. Use "Keep my plan", or "Keep AI Power", "Keep storage" or "Keep mailboxes" for an Add-On. We email a confirmation when you undo a cancellation.

S1.7.6 The Stripe billing portal also lets you change your payment method and see invoices. It lets an Admin cancel at the end of the Billing Period too. Both ways cancel at the end of the Billing Period.

S1.7.7 If you are the Billing Owner and cannot sign in, email nshulman@natex.ai from the Account address. We cancel it for you.

S1.7.8 "Cancel any time" means two things. You keep access until the end of the Billing Period you paid for. And the Refund Policy in Section S1.10 (Refund Policy) applies to what you paid.

S1.8 Add-Ons, Extra Persons and mid-period changes

S1.8.1 Each Add-On is its own Subscription. It has its own Renewal Date, its own reminder, its own confirmation email and its own Cancel button. This is the rule:

Each add-on and extra-seat line renews on its own and can be cancelled on its own.

S1.8.2 The Add-Ons are AI Power, extra storage of 100 GB each (quantity 1 to 50) and an extra mailbox (quantity 1 to 50, for Team, Business and Scale only). AI Power is priced by Paid Plan. Their prices are shown on our Pricing page and at checkout. Add-Ons work only on a Paid Plan.

S1.8.3 We never add an Extra Person on our own. When a Workspace is full, an invitation is refused with the message "Add a seat in Settings > Billing". An Extra Person is charged only after an Admin confirms the disclosure in Section S1.2 (Checkout, consent and what you agree to). The Extra Person is a separate line on the Paid Plan's Subscription.

S1.8.4 A change to the Paid Plan, the interval, the number of Extra Persons or the quantity of an Add-On changes the existing Subscription in place. Stripe prorates the change to the day. The amount appears on the Stripe invoice. The screen tells you so before you confirm.

S1.8.5 Your Subscription keeps renewing at the new price and quantity until you cancel it.

S1.9 Failed payments

S1.9.1 This is what happens when a renewal payment fails:

If a renewal payment fails, your paid plan keeps working while the card is retried and you can update it. We email you when it fails. If the subscription ends because payment could not be collected, the workspace moves to the Free plan and keeps your data.

S1.9.2 We set no number of days. Stripe's retry settings decide how long a Subscription stays past due. We email the Admins the first time a Paid Plan goes past due.

S1.9.3 We do not cut off paid access because you dispute a charge without telling you first.

S1.10 Refund Policy

S1.10.1 The Refund Policy has six clauses:

1. Within 14 days of your first charge for any plan or add-on, ask and we refund it in full.
2. Within 7 days after a yearly plan renews automatically, ask and we refund that renewal in full.
3. If we raise your price or make a change that is materially worse for you and you cancel within 30 days of our notice, we refund the unused part of what you prepaid, to the day.
4. An AI command pack is refunded in full if none of it is used within 14 days; once any of it is used it is not refundable.
5. Refunds go back to the original payment method within 10 Business Days of approval.
6. Other charges are not refunded, except where the law requires it. This policy does not limit any right the law gives you.

S1.10.2 How to ask:

To ask for a refund, email nshulman@natex.ai from your account address.

S1.10.3 We issue a refund under clause 1, 2 or 4 by hand, from the Stripe dashboard, after you email us. The prorated refund in Section S1.10.6 has a button: "End my plan now and get a prorated refund" in Settings > Billing. Where we end your access ourselves, we issue the refund.

S1.10.4 Deleting a Workspace or an Account is not a refund request. Deleting cancels the Subscription at once, with no refund and no further charge. If you want a refund under clause 1, 2 or 4, ask first, within the windows in those clauses. If Section S1.10.6 applies to you, use "End my plan now and get a prorated refund" before you delete.

S1.10.5 This is the one place that says how we work out a refund of prepaid, unused time. The refund is the unused part of what you prepaid, to the day. We work it out like this. Take the amount you paid for the Billing Period. Divide it by the number of days in that Billing Period. Multiply the result by the number of days left after the day on which your cancellation, our action or the end of the affected part takes effect. The day it takes effect counts as a day used. We work it out for the plan and for each Add-On, line by line, so that an Extra Person added in the middle of a Billing Period is refunded over its own days. The amount takes account of any discount and includes the tax you paid on the unused part. Clause 3 and every other section of the Agreement that promises a refund of prepaid, unused time use this amount.

S1.10.6 In these cases we refund the unused part of what you prepaid without a refund request. The amount is the one in Section S1.10.5:

• (a) you cancel within 30 days of a notice that we are raising your price or making a change that is materially worse for you, including a material reduction of your Paid Plan (clause 3, Section 5 (The Service and how it changes) and Section S1.6 (Price changes));
• (b) you object to a Material Change and cancel (Section 32 (Changes to the Terms));
• (c) we end your access for a reason that is not about your conduct, or we discontinue the Service (Section 26 (Suspension and termination) and Section 5 (The Service and how it changes));
• (d) you object to a new Sub-processor and end your plan (Section B6 (Sub-processors)); or
• (e) you cancel within 14 days after the first charge at a higher price (the refund is the unused part of that charge).

In the cases in (a), (b), (d) and (e), you choose how your cancellation takes effect. If you end your plan now, your access ends on that day and we refund the unused part of what you prepaid. In Settings > Billing, an Admin does this with the button "End my plan now and get a prorated refund". The button appears when the case in (a), (b) or (d) applies to you, and it shows the amount before you confirm. For the case in (e), or if you prefer, write to nshulman@natex.ai. If you keep your access to the end of the Billing Period, your cancellation takes effect then, you have used everything you paid for, and there is nothing to refund.

The day a refund becomes due is the day your plan ends or, in the case in (c), the day our action takes effect. We send the refund to the original payment method within 10 Business Days after that day, and we email you the amount.

S1.10.7 In every other case you ask for the refund, within the windows in clauses 1, 2 and 4, as Section S1.10.2 says.

S1.10.8 Clause 6, "Other charges are not refunded", is subject to Sections S1.10.5 to S1.10.7 and to the law.

S1.10.9 If the law gives you a refund right, or a longer window, the law applies.

S1.11 Who sells to you

S1.11.1 NATEX Work is sold by NATEX AI, Inc., a Delaware corporation operated from Michigan. Registered office and address for legal notices: 16192 Coastal Highway, Lewes, DE 19958. Contact: nshulman@natex.ai.

S1.11.2 For billing, cancellation help and refunds, write to nshulman@natex.ai.

S1.11.3 Checkout, Stripe Checkout and every billing email print this name and address.

S1.12 Taxes

S1.12.1 This is the tax statement:

Prices are in US dollars and do not include sales, use or similar taxes. Where we are required to collect tax, it is added based on your billing address and shown before you pay.

S1.12.2 Checkout requires a billing address.

S1.12.3 If you are a Seller, you charge and remit tax on your own sales to your own clients. We do not do that for you.

S1.13 AI Command Pack

S1.13.1 The AI Command Pack is 600 AI commands, at the price shown on our Pricing page and at checkout. You pay once. It does not renew and starts no Subscription. It is available only on a Paid Plan.

S1.13.2 The pack does not expire because you leave it unused. It has no cash value and you cannot transfer it. It is deleted when the Workspace is deleted.

S1.13.3 A pack is refundable only under clause 4 of the Refund Policy: in full if none of it is used within 14 days, and not at all once any of it is used.

S1.13.4 We do not sell call-minute or transcription packs.

S1.14 Payment processing

S1.14.1 Stripe processes our payments. Card details never reach NATEX Work servers, and we never receive your card number. Stripe states that it is PCI DSS Level 1. Section 12 (Payments and billing) of the Privacy Policy says what we send to Stripe.

S1.14.2 PCI DSS is a security standard set by the card brands. It is not a law.

S1.14.3 Stripe's terms and Stripe's privacy policy, at https://stripe.com/privacy, apply to the payment details you enter at Stripe.

S1.14.4 We add no surcharge for paying by card.

S1.14.5 If you think a charge is wrong, please contact us at nshulman@natex.ai before you ask your card issuer for a chargeback. We can often fix the problem faster. This request does not take away your right to dispute a charge with your card issuer.

S1.15 Who can buy and cancel

S1.15.1 Only an Admin can buy, change or cancel a Paid Plan or an Add-On. The Admin who buys is the Billing Owner.

S1.15.2 A Member or Guest of someone else's Workspace buys nothing and has no billing rights in that Workspace.

S1.15.3 If the Billing Owner cannot sign in, email nshulman@natex.ai from the Account address.

End of Schedule 1. Effective Date: [[OPEN-01]]

Annex A. Acceptable Use Policy

This policy is part of the Terms. It applies to everything you do with NATEX Work.

Use NATEX Work to run your work. Do not use it to hurt people, to break the law, or to attack systems. Each section below ends with what we may do if you break it. Section A18 (Reporting, enforcement and appeals) explains how we enforce this AUP.

A1 Who this applies to

A1.1 This AUP applies to every Account, Member, Guest, Teammate, App, Plugin, Automation, API Key and Webhook. It applies to the Content you put in, to what you do, and to the code you run.

A1.2 The Workspace Owner is responsible for the Members and for everything done under the Workspace's keys, including every API Key and Webhook.

A1.3 An Agent Action under your Account or Workspace is your action. A Third-Party Agent that holds your API Key acts under your keys. Section 10 (Teammates, Automations and actions taken for you) explains this.

A1.4 If you or anyone acting for you breaks this AUP, we may take any action in Section A18 (Reporting, enforcement and appeals).

A2 Illegal activity

A2.1 Do not use NATEX Work to commit, plan or help with anything unlawful. This includes:

• (a) fraud, scams and money laundering;
• (b) human trafficking and the exploitation of people;
• (c) buying or selling goods or services that are illegal, or that you have no license to sell, such as drugs, weapons and other regulated goods;
• (d) offering financial, legal, tax or medical services that need a license you do not hold;
• (e) unlawful gambling;
• (f) evading sanctions or export controls (Section A17 (Sanctions and export)); and
• (g) computer crime of any kind (Section A11 (Security and malicious code)).

A2.2 Do not ask an AI Feature, a Teammate, an App or a Plugin to do any of these things for you.

A2.3 If you break this section, we may remove the Content, suspend or end your Account, and report you to the authorities.

A3 Child safety

A3.1 Do not create, upload, store, share, request or link to:

• (a) child sexual abuse material of any kind, including material that is AI-generated, drawn, animated or otherwise synthetic;
• (b) any sexualized depiction of a minor, or any sexual content that involves a minor; or
• (c) grooming, solicitation or sextortion of a minor.

A3.2 Do not direct NATEX Work at people under 18. The Service is for Eligible Persons only.

A3.3 We report apparent child sexual abuse material to the National Center for Missing and Exploited Children (NCMEC), as 18 U.S.C. § 2258A requires. We may preserve and disclose related data to NCMEC and to law enforcement without telling you. We keep the reported material and the related Account Data for 1 year from the report. Section 25 (Government requests, safety reports and copyright) of the Privacy Policy says what we keep.

A3.4 If you find material like this in NATEX Work, Report it through the Report control (choose "Child safety") or by email to nshulman@natex.ai. Describe where it is. Do not send us the material itself and do not copy or forward it.

A3.5 If you break this section, we act first and explain afterward. We remove the material, end the Account, and report to NCMEC and law enforcement. We do not give a warning first.

A4 Intimate images, deepfakes and likeness

A4.1 Do not create, upload, share, store or ask for:

• (a) an intimate image or video of a real person that is shown without that person's consent, whether it is real or synthetic;
• (b) a sexual deepfake of a real person;
• (c) a deceptive imitation of a real person's voice or likeness, including voice cloning that is meant to mislead;
• (d) synthetic media that is meant to mislead people about an election, a candidate or a real person; or
• (e) content that impersonates a person, a brand or an authority.

A4.2 If you are shown in an intimate image or video that was published without your consent, you or your representative can make an Intimate Image Request. A valid request includes:

• (a) a signature (physical or electronic) of the person shown, or of their authorized representative;
• (b) enough information for us to find the material, such as the web address or the place in NATEX Work where it appears;
• (c) a brief statement that you believe in good faith that the image or video was published without your consent, with any information that helps us see that it was not consensual; and
• (d) your contact details.

A4.3 Send the request through the Report control, or by email to nshulman@natex.ai with the words "Intimate Image Request" in the subject line. You do not need an Account. We remove the material within 48 hours of a valid request, and we make reasonable efforts to remove identical copies that we know about on the public parts of NATEX Work. We keep a record of each request and of what we did. We may ask you for more information. We tell you when we have acted.

A4.4 We provide this process for people shown in Content hosted on public parts of NATEX Work. Section 25 (Government requests, safety reports and copyright) of the Privacy Policy says what we keep.

A4.5 If you break this section, we may remove the Content at once and without notice, limit or end public sharing for the Workspace, and suspend or end the Account.

A5 Violence, extremism, weapons and self-harm

A5.1 Do not use NATEX Work to:

• (a) threaten, or incite, violence against any person or group;
• (b) create, promote, recruit for or praise terrorism or violent extremism;
• (c) make, buy, sell or use weapons unlawfully, or get help with making a biological, chemical, radiological or nuclear weapon; or
• (d) encourage suicide, self-harm or an eating disorder.

A5.2 NATEX Work is not an emergency or crisis service and does not watch for danger. If someone is in immediate danger, call 911.

A5.3 If you break this section, we may remove the Content, suspend or end your Account, and tell the authorities where the law lets us.

A6 Harassment and hate

A6.1 Do not use NATEX Work to harass, bully, threaten or stalk anyone. Do not publish a person's private information, such as a home address or a private phone number, to intimidate or harm them.

A6.2 Do not post, send or promote hate speech. Do not discriminate against, or attack, people because of their race, ethnicity, national origin, religion, sex, gender identity, sexual orientation, disability, age, or any other characteristic the law protects.

A6.3 This applies to Public Pages, public community channels, Gallery items, the email and messages you send, and Calls.

A6.4 If you break this section, we may remove the Content, restrict public sharing, and suspend or end your Account.

A7 Intellectual property

A7.1 Do not use NATEX Work to infringe anyone's intellectual property. This includes:

• (a) sharing infringing, counterfeit or pirated content;
• (b) removing or falsifying copyright-management information;
• (c) getting around technical protections on a work or on access to it;
• (d) misappropriating trade secrets; and
• (e) using another person's trademark in a way that misleads people.

A7.2 We respond to copyright notices and end the Accounts of Repeat Infringers. Section 23 (Copyright) explains how to send a Notice of Claimed Infringement and a Counter-Notice, and how Strikes work.

A7.3 If you break this section, we may remove the Content and end the Account. A Repeat Infringer's Account is ended.

A8 Privacy

A8.1 Do not use NATEX Work to:

• (a) collect, upload or process Personal Information that you have no right to collect, upload or process;
• (b) record, track or monitor a person without the consent the law requires, including secret recording of a Call, covert tracking and hidden monitoring;
• (c) identify a person from a face, a voice or any other biometric identifier; or
• (d) ignore a request from a person about their Personal Information that the law requires you to honor.

A8.2 Do not put Prohibited Data into NATEX Work and do not send it to an AI Feature. Section 15 (Prohibited Data and Restricted Data) lists Prohibited Data and Restricted Data. Section 19 (Sensitive data) of the Privacy Policy says what we do with sensitive information. A Seller's own payment instructions on an invoice or booking page are not Prohibited Data. You may store Restricted Data on your own authority and responsibility. We give no assurance that NATEX Work fits the rules that apply to it.

A8.3 Some places require every person on a Call to agree before you record, caption or transcribe it. You are responsible for knowing the rules where the people on your Call are, and for getting their agreement. Section 14 (Email, messages and Calls) and Section 18 (Your duties to the people whose data you handle) say more.

A8.4 If you break this section, we may delete Content that breaks it, ask you to remove it, suspend the Account, and end the Account for serious or repeated breaches.

A9 Deception and fraud

A9.1 Do not use NATEX Work to deceive people. This includes:

• (a) phishing and scams;
• (b) impersonating a person, a brand or an authority;
• (c) writing or buying fake reviews or testimonials, including AI-generated ones;
• (d) astroturfing and other fake social proof;
• (e) misleading health, financial or legal claims;
• (f) claiming a license, credential or professional status that you do not have;
• (g) saying you are not an AI when a person sincerely asks and you are an AI; and
• (h) saying that NATEX AI, Inc. endorses you, your App or your Plugin.

A9.2 If you break this section, we may remove the Content, disable the App, Plugin, Public Page or Automation involved, and suspend or end the Account.

A10 Spam and unsolicited messages

A10.1 Do not send unsolicited bulk email, messages or invitations. Do not use purchased, rented or harvested lists. Do not harvest addresses or guess them.

A10.2 Commercial email needs accurate sender and header information, an opt-out that works and that you honor promptly, and your postal address. Say that it is an advertisement where the law requires. Anti-spam laws apply by the place where the recipient is. Examples are the CAN-SPAM Act in the United States, Canada's anti-spam law and the UK's Privacy and Electronic Communications Regulations. You answer for compliance with them.

A10.3 NATEX Work does not place phone calls or send text messages. If you use a Connected Service or another tool for texts or calls, you need the consent that the Telephone Consumer Protection Act and similar laws require. AI-generated voice calls need the recipient's prior express consent.

A10.4 Do not use NATEX Work, a connected mailbox, an invitation, or any email relay we turn on, to send mail that harms the sender reputation of the mailbox or of our own sending domain.

A10.5 If you break this section, we may rate-limit or pause your sending, suspend the Account, and report complaints to the mailbox or relay provider. Section 14 (Email, messages and Calls) applies.

A11 Security and malicious code

A11.1 Do not use NATEX Work to create, host or spread:

• (a) malware, ransomware, spyware, exploit kits or credential harvesters;
• (b) command-and-control systems or botnets;
• (c) cryptomining; or
• (d) a denial-of-service attack.

A11.2 Do not scan or probe systems you do not own. Do not try to reach another Customer's data or our systems. Do not try to get around, test or escape the sandbox or the permissions of an App or Plugin.

A11.3 An App or Plugin may call only the hosts it declares. It must not send out data it was not asked to handle. Do not use an App or Plugin to generate or distribute malicious code.

A11.4 We welcome good-faith security research. If you find a weakness, report it to nshulman@natex.ai and give us reasonable time to fix it before you publish it. Access only what you need to show the problem, do not harm other people's data, and do not disrupt the Service.

A11.5 If you break this section, we may disable the App, Plugin, API Key or Webhook, remove the Content, suspend or end the Account, and tell the authorities.

A12 Automated access and scraping

A12.1 Do not scrape NATEX Work, or any Third-Party Service, in breach of its terms.

A12.2 Do not use a Teammate, an Automation, an App or a Plugin to get around rate limits, CAPTCHAs, paywalls, robots.txt files or other access controls.

A12.3 Do not resell or sublicense access to the API, and do not build a competing service from it. Do not use several API Keys to avoid a rate limit.

A12.4 Do not stress-test the Service without our written permission.

A12.5 If you break this section, we may throttle or revoke API Keys, disable Automations, Apps and Plugins, and suspend or end the Account.

A13 AI-specific rules

A13.1 Your requests and the Output are also subject to the usage policy of each Model Host that serves them, and to the usage policy of the company that makes the model. You must follow them as they apply to inputs and to Output. We may refuse a request that a Model Host would refuse. A Model Host may screen a flagged request. Section 9 (AI Features) explains this.

A13.2 Without our written permission, do not:

• (a) jailbreak an AI Feature, or use prompt injection against us or against other people;
• (b) try to extract system prompts or model weights, or to get around a safety filter;
• (c) use Output or the Service to build, train or improve an AI model that competes with the Service (follow the usage policy of each Model Host as Section 9.7 says);
• (d) create an AI persona that claims to be a licensed professional, such as a doctor, lawyer or therapist, or that claims to be a real person;
• (e) present an AI Feature as therapy or crisis counselling, or present its Output as professional medical, legal, financial or tax advice; and
• (f) mass-generate content for spam, disinformation or manipulation.

A13.3 Do not send Prohibited Data to an AI Feature. Our permission does not change this.

A13.4 If you break this section, we may limit or turn off AI Features for your Account or Workspace, revoke API Keys, and suspend or end the Account.

A14 High-risk decisions about people

A14.1 Do not use AI Features, Teammates or Output to make, or to materially influence, a decision about a person's employment, hiring, promotion, discipline, housing, credit, insurance, education eligibility, public benefits, legal status or health care. The one exception is a decision that a qualified human reviews in a meaningful way and has the authority to change.

A14.2 You are the deployer of any decision you make. You give the notices the law requires. Where a Model Host's usage policy requires it, tell the affected people that AI was involved. NATEX Work does not provide bias audits or adverse-action notices.

A14.3 Do not use NATEX Work for emotion recognition, social scoring or biometric categorization of people.

A14.4 We do not market AI ranking or scoring of people, and NATEX Work does not score or rank candidates, leads or students.

A14.5 If you break this section, we may limit or turn off AI Features for your Account or Workspace, and suspend or end the Account.

A15 Community and Gallery rules

A15.1 Public community channels and Gallery items must follow this AUP.

A15.2 If you publish an item to the Gallery, you must own it or have a license to publish it, and you must state the license. Do not publish an item that:

• (a) misleads people about what it does;
• (b) asks for permissions it does not need;
• (c) hides a network call; or
• (d) contains third-party code that you may not redistribute.

A15.3 Do not publish a recording or the likeness of a person without their permission. Do not publish Personal Information about a person without the right to do so.

A15.4 Do not publish in bulk or by deception. This includes keyword stuffing, self-promotion spam and brigading.

A15.5 A person who moderates a public channel must apply this AUP and must send illegal content to us.

A15.6 Report is on every public item, including every post in a public community channel and every Gallery item. Section 18 (Public Pages, the Gallery and community channels) of the Privacy Policy describes what the Gallery shows.

A15.7 If you break this section, we may hide, remove or disable the item, disable or force-update installed copies of an App or Plugin, restrict your public sharing, and suspend or end the Account.

A16 API, MCP Server and Webhook rules

A16.1 This section restates Section 12 (API, MCP Server and Webhooks) in brief.

A16.2 API Keys:

• (a) Keep each API Key secret. You are responsible for everything done with it.
• (b) Give each API Key the narrowest scope and the narrowest collection allowlist that works.
• (c) Revoke a key at once if you suspect it has leaked.
• (d) The limit is 120 requests a minute for each key. Do not shard your traffic across keys to avoid it.

A16.3 Third-Party Agents:

• (a) You decide which Third-Party Agents get your Content. You must have the right to send it there.
• (b) Content can carry hostile instructions that try to steer an agent. Do not give a key the external or admin scope unless you accept that the agent can act, and send messages, as you.

A16.4 Webhooks:

• (a) You own the receiving endpoint and its signing secret. Keep the secret safe and verify each signature.
• (b) A delivery contains record data. You are responsible for the security of the endpoint and for the lawful use of the data.
• (c) We try each delivery up to 8 times in total over about a day, and then we stop. We do not deliver to private addresses or to addresses that are not https.

A16.5 We give at least 30 days' notice before a breaking change to the API.

A16.6 Do not resell or sublicense access to the API (Section A12 (Automated access and scraping)). Report security problems to nshulman@natex.ai (Section A11 (Security and malicious code)).

A16.7 If you break this section, we may revoke API Keys, disable Webhooks, and suspend or end the Account.

A17 Sanctions and export

A17.1 Do not use NATEX Work if you are a Restricted Party, if you act for a Restricted Party, or if you are in an Embargoed Jurisdiction. Section 27 (Sanctions and export) has the full statement and is part of the Agreement.

A17.2 Do not put technical data into NATEX Work that is controlled under the International Traffic in Arms Regulations or the Export Administration Regulations. Do not put in classified information.

A17.3 NATEX Work is offered only in the Territory. If the country that your network reports is outside the Territory, we do not create the Account. Section 20 (Age, children and where you live) of the Privacy Policy describes the country checks.

A17.4 If you break this section, we may suspend or end your Account and block access by location.

A18 Reporting, enforcement and appeals

A18.1 How to Report. Use the Report control on a public community post or a Gallery item. The reasons are: Spam or scam; Harassment or hateful content; Illegal content; Copyright infringement; Intimate image shared without consent; Child safety; and Something else. You can add details of up to 2,000 characters and an email address. Choose "Copyright infringement" only for a copyright notice, and give an email address. Section 23 (Copyright) explains the process. If you have no Account, or the content is not on a public community post or a Gallery item, email nshulman@natex.ai. Section 24 (Reporting content, and our role as a host) explains our role as a host.

A18.2 Intimate Image Requests. We process a valid Intimate Image Request as Section A4 (Intimate images, deepfakes and likeness) describes. We remove the material within 48 hours of a valid request.

A18.3 What we may do. After a Report, or when we otherwise learn of a breach, we may:

• (a) ask for more information;
• (b) remove or hide Content;
• (c) disable a Gallery item or an installed App or Plugin;
• (d) restrict public sharing for a Workspace;
• (e) limit or turn off AI Features, or throttle or revoke API Keys;
• (f) warn you;
• (g) suspend or end an Account or a Workspace; and
• (h) report to law enforcement or to NCMEC.

A18.4 Urgent cases come first. For child sexual abuse material, intimate images, malware and imminent harm, we act first and explain afterward. A Report for an intimate image or child safety hides the content from public view at once until we review it. A review that dismisses the Report puts it back.

A18.5 Notice and appeal. Where the law allows, we tell the Customer what we did and why. We give no notice where law enforcement or safety requires silence. You can appeal once. Email nshulman@natex.ai within 30 days of the notice of the action. Say what you want us to reconsider and why. We review the appeal and tell you the result.

A18.6 Repeat violations. We may end the Account of a person who breaks this AUP repeatedly. We end the Account of a Repeat Infringer as Section 23 (Copyright) describes.

A18.7 Records. We keep a Report record until we review it and then for 3 years after the review. We keep copyright notices, Counter-Notices and our Strike ledger for 3 years after we resolve them. We keep material reported to NCMEC, and the related Account Data, for 1 year from the report. We preserve data when the law requires it. Section 25 (Government requests, safety reports and copyright) of the Privacy Policy has the details.

A18.8 Provider-driven action. If OpenRouter, a Model Host, an Integration Provider or another provider requires us to restrict a use, we may do so, and we may restrict your access to the affected feature.

A18.9 Remedies are cumulative. Taking one action does not stop us from taking another.

A19 No duty to monitor

A19.1 We do not have to monitor Content, and we do not review private Workspace Content except to answer a Report, to protect security or to comply with law. Section 21 (Security, confidentiality and shared responsibility) describes our limits on Staff access.

A19.2 Nothing in this AUP obliges us to take any action or to refrain from any action. We may act, or decline to act, in our discretion. Our remedies are cumulative. The reservations in Section 24 (Reporting content, and our role as a host) apply.

A20 Changes to this policy

A20.1 This AUP is dated. The Effective Date at the end shows which version you are reading, and earlier versions are at /legal/history.

A20.2 A Material Change to this AUP gets 30 days' notice and your re-acceptance, as Section 32 (Changes to the Terms) describes.

A21 Debt collection, consumer reports and restricted payment uses

A21.1 Do not use NATEX Work to collect debts owed to other people. Do not send a message that falsely suggests that a third-party collector is writing. Reminders and invoice messages go out in your own name.

A21.2 NATEX Work is not a consumer reporting agency. We provide no consumer reports. Do not use NATEX Work, or Output from it, to make a decision that needs notices under the Fair Credit Reporting Act, such as a decision about employment, housing, credit or insurance eligibility.

A21.3 The payment features of NATEX Work rely on Stripe. Stripe bars some businesses and restricts others. Do not use a payment feature of NATEX Work for a business that Stripe prohibits, or that Stripe restricts without Stripe's written approval. Examples are adult content, gambling, multi-level marketing, debt collection, cryptocurrency, counterfeit goods, and others on Stripe's lists.

A21.4 If you break this section, we may disable the feature involved, remove Content, and suspend or end the Account.

A22 Signatures and legal documents

A22.1 NATEX Work is not an electronic-signature service, an identity-verification service or a notary service.

A22.2 A consent or acknowledgment collected through a form is not a verified signature. You decide whether a waiver or a consent that you collect is valid, and you keep your own records.

A22.3 Do not use NATEX Work for documents that the federal E-SIGN Act excludes, or that need a wet-ink or notarized signature.

A22.4 If you break this section, we may remove the Content or the form, and suspend the Account if the use is unlawful.

A23 Regulated data

A23.1 Do not put Protected Health Information into NATEX Work if you are a covered entity or a business associate. We are not a business associate and we sign no business associate agreements.

A23.2 Do not put controlled unclassified information, classified information or criminal justice information into NATEX Work. NATEX Work is not assessed for the systems and rules that cover them.

A23.3 Section 15 (Prohibited Data and Restricted Data) and Section 16 (Professional, regulated and government use) say more, including what we may do if we find data that we do not accept. Section 19 (Sensitive data) of the Privacy Policy says what we do with sensitive information.

A23.4 If you break this section, we may ask you to remove the data, suspend the Account, and delete the data on your instruction without reading it.

A24 Workplace and personal accounts

A24.1 Do not use NATEX Work for covert surveillance of employees.

A24.2 Do not require anyone to hand over access to a personal internet account, such as a personal mailbox or calendar, as a condition of work or study.

A24.3 If you are an Organization Customer, Section 36 (Added terms for Organization Customers) lists the notices you give your Members.

A24.4 If you break this section, we may suspend the Account and remove the connection or the Content involved.

A25 What the Service does not do

A25.1 NATEX Work does not run server-side speech-to-text, speaker identification or voice cloning. It does not generate images or video. It does not identify people from biometrics.

A25.2 Voice input, live captions and Call Notes use your browser maker's speech service, not a service we run.

A25.3 We will not add any of these features until we complete a legal review and update this AUP.

End of Annex A. Effective Date: [[OPEN-01]]

Annex B. Data Processing Addendum

This DPA is part of the Terms. It applies when we process Personal Information in your Content on your behalf.

It applies to you automatically, with no signature, if you use the Service for a business and your Content holds Personal Information about other people. Every Organization Customer is covered. An Individual Customer is covered when acting for a business. Section 19 (Who is responsible for personal information) explains who is covered. An Individual Customer who uses NATEX Work only for personal purposes is not covered by this DPA. Section 26 (Your privacy rights) of the Privacy Policy applies to that Customer directly.

The parties are NATEX AI, Inc. (we) and the Customer (you). If this DPA conflicts with another part of the Agreement about how we process Personal Information in Content, this DPA controls. Section B16 (Liability and precedence) sets the limit on liability.

B1 Parties, roles, subject matter

B1.1 For Personal Information in Content, you are the Controller and we are your Processor. The word Processor includes a "service provider" or "contractor" under US state privacy laws, and we are one for Content.

B1.2 For Account Data, billing, security, abuse, support and product-operations data, we are the Controller. Section 2 (Our two roles) of the Privacy Policy describes that use. This DPA does not apply to it.

B1.3 You decide what Content to put into NATEX Work and why. You are responsible for the lawful basis for it and for the notices to the people it concerns (Section B15 (Customer duties)).

B1.4 The subject matter is the Service we provide to you. The nature of the processing is storing, syncing, searching, displaying, transmitting, backing up and deleting your Content. It also includes sending text from your Content to AI Features and to Connected Services at your direction, and sending the messages you ask us to send. The purposes are the business purposes in Section B3 (Service provider terms under US state privacy law). The duration is the time we hold your Content, which is the term of the Agreement plus the periods in Section B9 (Return and deletion).

B1.5 The types of Personal Information and the people it concerns are in Annex B-1 at the end of this DPA.

B2 Instructions

B2.1 We process Personal Information in Content only on your documented instructions. Your documented instructions are:

• (a) the Agreement, including this DPA;
• (b) the settings you and your Admins choose in NATEX Work, such as AI exclusions, Local-Only Mode and retention settings;
• (c) your use of the Service, including the API, the MCP Server, Webhooks and every Agent Action under your Account or your Workspace's keys; and
• (d) written instructions you send to nshulman@natex.ai that are consistent with the Agreement.

B2.2 A Third-Party Agent that holds your API Key is a recipient you chose. What you route to it is your instruction. Section 12 (API, MCP Server and Webhooks) says more.

B2.3 If we believe that an instruction breaks the law, we tell you and may stop acting on it until you confirm it or change it.

B2.4 If the law requires us to process Personal Information in Content in another way, we tell you before we do, unless the law forbids us to tell you.

B3 Service provider terms under US state privacy law

B3.1 This section applies to Personal Information in Content that the California Consumer Privacy Act covers. It also applies to the similar laws of other states.

B3.2 You disclose Personal Information to us only for the limited and specified business purposes in this section:

• (a) to host, store, sync, search, display, transmit and delete your Content;
• (b) to process your Content as you direct, through AI Features and Connected Services you use, and to send the messages you ask us to send;
• (c) to back up and recover the Service;
• (d) to keep the Service and your Content secure, and to detect and prevent abuse and fraud;
• (e) to give support that you ask for; and
• (f) to comply with law.

B3.3 We do not "sell" Personal Information in Content. We do not "share" it for cross-context behavioral advertising. These words have the meanings that the California Consumer Privacy Act gives them.

B3.4 We do not retain, use or disclose Personal Information in Content for any purpose other than the business purposes in paragraph B3.2. That includes any commercial purpose of our own. We do not retain, use or disclose it outside our direct business relationship with you.

B3.5 We do not combine Personal Information in Content with Personal Information that we receive from other sources or collect from our own interactions with people, except as the law lets a "service provider" do. This is the statement about our infrastructure:

NATEX Work has its own database and sign-in system, separate from NATEX AI's other products. NATEX AI uses one Stripe account and one OpenRouter account for all of its products. Your NATEX Work data is used only by NATEX Work.

B3.6 We will comply with the obligations that the California Consumer Privacy Act places on a "service provider". We will give Personal Information in Content the same level of privacy protection that the law requires of you as a business.

B3.7 You may take reasonable and appropriate steps to confirm that we use Personal Information in Content in a way that is consistent with your obligations. You may do this at least once every 12 months. Section B10 (Audit and information) explains how.

B3.8 We will tell you without undue delay if we decide that we can no longer meet our obligations under this section or under the law.

B3.9 If you reasonably believe that we are using Personal Information in Content without authorization, you may take reasonable and appropriate steps to stop it and to remediate it. Tell us at nshulman@natex.ai and we will work with you.

B3.10 We help you respond to requests from people about their Personal Information in Content, as Section B8 (Assistance) says.

B3.11 We use each Sub-processor under that Sub-processor's published terms and, where it offers them, its data processing terms. For Model Hosts, which we reach through OpenRouter, the terms we rely on are OpenRouter's terms for Model Hosts. We have no separate contract with an individual Model Host or with Perplexity. We have not signed a data processing agreement with Composio, so we do not represent that Composio is bound by every term of this Section B3. If you cannot accept that for particular data, do not connect a Connected Service that uses Composio. Section B6 (Sub-processors) describes this further.

B3.12 You will tell us about any consumer request that we must act on for Content, and give us the information we need to act on it.

B4 Processor contract terms in other states

B4.1 We limit access to Personal Information in Content to Staff who need it to provide the Service, and each of them is bound by a duty of confidentiality.

B4.2 At your direction, we delete Personal Information in Content or return it to you when the Agreement ends, as Section B9 (Return and deletion) describes.

B4.3 On your reasonable request, we give you the information needed to show that we meet this DPA. Section B10 (Audit and information) explains the limits.

B4.4 We allow a reasonable assessment of our processing once every 12 months, or we give you a report from a qualified independent assessor instead, as Section B10 (Audit and information) describes.

B4.5 We use each Sub-processor under its published terms, as Section B6 (Sub-processors) explains and as Section B3.11 states for Model Hosts, Perplexity and Composio. We pass on the obligations in this DPA to the extent each Sub-processor's published terms allow.

B5 Security measures

B5.1 We use reasonable administrative, technical and physical safeguards for Content. No security is absolute. These are the measures we use. We promise no others.

• (a) Encryption in transit. We use TLS to protect data in transit.
• (b) Encryption at rest by our vendors. Supabase encrypts its disks with AES-256. Cloudflare R2 encrypts stored objects with AES-256-GCM, with keys that Cloudflare manages. This is disk-level encryption. It does not encrypt Content inside the database from someone who has database access.
• (c) Encryption in our application. We encrypt stored mailbox (IMAP) passwords and Webhook secrets with AES-256-GCM in our own code.
• (d) API Keys. We store only a SHA-256 hash of each API Key.
• (e) Workspace isolation. Row-level security separates Workspaces from each other in the database.
• (f) Approval gates. Risky actions need explicit approval. Section 10 (Teammates, Automations and actions taken for you) explains Approvals and Auto-Apply.
• (g) Public Pages. Public Pages use long random tokens.
• (h) Sign-in controls. Two-factor authentication is available. A Workspace may require it.
• (i) Card data. Card data never reaches our servers. Stripe handles it.
• (j) Backups. Each Backup file is encrypted with AES-256-GCM in our own application before it is stored, and our storage vendors also encrypt their disks. We hold the key only as a server secret, kept apart from the Backups, plus one offline copy that our founder keeps. File names inside a Backup show table names.
• (k) Staff access. The next paragraph states our limits on Staff access.

B5.2 Our Staff do not read your Content except to give support you ask for, to investigate security or abuse, or to comply with law. Access through our admin tools is recorded in the Staff Access Log, and your Admins can see the entries for your Workspace. Direct access to our database is limited to named, authorized Staff and is not recorded by the application.

B5.3 You secure your Members' credentials, API Keys, Webhook secrets and Connected Service permissions. Section 21 (Security, confidentiality and shared responsibility) says more. Section 21 (Security) of the Privacy Policy says the same in plain words.

B5.4 We make no promise of any compliance certification. NATEX Work is not a HIPAA, GLBA, FERPA, PCI or FedRAMP environment.

B5.5 Annex B-2 (Security measures) is this section.

B6 Sub-processors

B6.1 You give us a general authorization to use the Sub-processors on the Sub-processor List. The list is in Section 8 (Sub-processor List) of the Privacy Policy. This section does not copy it.

B6.2 This is how we change the list:

We publish the Sub-processor List with each Sub-processor’s legal name, what it does, the data it handles, where it processes that data and the date we added it. We give the Workspace Owner and the Admins an in-app notice in Settings > Privacy at least 30 days before a new Sub-processor starts to process Content. When we do not choose the change ourselves, for example because a Sub-processor changes its own vendors, we give notice as soon as we reasonably can, normally 30 days. If you object within 30 days of the notice, an Admin records the objection in Settings > Privacy with "Object to this Sub-processor". You may then end your plan, and we will refund the unused part of what you prepaid, as Section S1.10 (Refund Policy) of the Plan and Billing Terms describes. We also work with you on any data-protection concern.

B6.3 Section S1.10 (Refund Policy) of Schedule 1 says how we work out and pay a refund under paragraph B6.2, and that you do not need to ask.

B6.4 We use each Sub-processor under that Sub-processor's published terms and, where it offers them, its data processing terms. Paragraph B3.11 of Section B3 (Service provider terms under US state privacy law) says where there is no separate contract. We pass on the protections in this DPA to the extent that those terms allow. The Sub-processor List shows where a Sub-processor acts only under its standard terms. We are responsible for the acts and omissions of our Sub-processors on Content as we are for our own, subject to Section B16 (Liability and precedence).

B6.5 Connected Services need special care. Composio (Sampark, Inc.) and Nango (Nango Inc) are Integration Providers. We use them only when you connect a Connected Service that needs them.

Composio connects many of the apps you add. It can keep the content of tool calls, which can include message text, for up to 1 year, including after you disconnect an app. That is outside our deletion windows.

We have not signed a separate data processing agreement with Composio. Composio's standard terms apply. Nango Inc holds tokens and pasted keys and proxies requests for the Connected Services it serves. If you cannot accept this for particular data, do not connect a Connected Service that uses Composio or Nango for that data.

B6.6 An Independent Recipient is not a Sub-processor. Section 7 (Who receives information) of the Privacy Policy lists them. A Third-Party Agent that holds your API Key is a recipient you chose and is not our Sub-processor (Section 12 (API, MCP Server and Webhooks)).

B7 Security Incident notice

B7.1 If a Security Incident affects your Content, we will tell the Workspace Owner and the Admins without undue delay and no later than 72 hours after we become aware that it happened, and we will include the information you need for your own notices. Nothing here shortens a deadline that the law gives you or imposes on us.

B7.2 To the extent we know it, the notice describes:

• (a) what happened and when;
• (b) the kinds of Content and the approximate number of Workspaces and records affected;
• (c) the likely consequences;
• (d) what we have done and will do to contain the problem and to reduce harm; and
• (e) how to reach us about it, at nshulman@natex.ai.

B7.3 If we do not yet know all of this, we give you what we have and add the rest as we learn it.

B7.4 We cooperate with you in investigating the Security Incident and in preparing your notices to regulators and to the people affected. You decide whether and how to notify your own contacts, subject to your legal duties. Section 21 (Security) of the Privacy Policy says the same in plain words.

B8 Assistance

B8.1 We help you meet your duties to respond to requests from people about their Personal Information in Content. Your Admins already have these tools: Export, the ability to edit and delete records, and the Privacy Center. Section 20 (Export, deletion and retention) lists the paths.

B8.2 If a Non-User asks us for something about Content in your Workspace, we aim to forward the request to the Workspace's Admins within 10 Business Days. A Non-User can also use the form at /legal/privacy-request. You answer it, and we help you do so.

B8.3 We help you with your security duties, your Security Incident notices (Section B7 (Security Incident notice)), and your data-protection impact assessments or risk assessments, by giving you the information about the Service that we have.

B8.4 If your request needs effort beyond the features of the Service and ordinary support, we may charge a reasonable fee based on our actual cost. We tell you the amount before we do the work.

B9 Return and deletion

B9.1 During the term, you can export your Content at any time. A Member can use Settings > Account > Download my data. An Admin can use Settings > Admin > Data > Download workspace ZIP. The Export limits in Section 20 (Export, deletion and retention) apply.

B9.1A When a Member leaves or is removed, we delete that Member's Personal Memory and saved AI keys for the Workspace. Team Memory is deleted when an Admin turns it off and with the Workspace. Team Memory is part of the Workspace ZIP that an Admin downloads. Personal Memory is not; a Member downloads it with Download my data.

B9.2 If we end your access for a reason other than abuse or illegality, you have 30 days after the termination to export your Content. Section 26 (Suspension and termination) applies.

B9.3 At your choice, we delete or return your Content. Return means an Export. The Workspace Owner can delete a Workspace at Settings > Team > Delete this workspace. After the Agreement ends, you can also ask us in writing at nshulman@natex.ai to delete the Workspace. When the 30 days in paragraph B9.2 have passed, we may delete the Workspace without being asked. On request, we confirm the deletion in writing.

B9.4 This is what deletion means:

When you delete something, it leaves the live system at once or after the 30-day Trash Window. Copies in Backups are gone within 60 days. Uploaded files are not in Backups. Copies in the command log expire after 90 days. When you disconnect a Connected Service, we delete what it brought in, after showing you the list. Some information stays where our vendors keep it under their own terms: Composio can keep the content of tool calls for up to 1 year, Brevo keeps delivery logs, Stripe keeps the payment records it must keep, and Supabase and Cloudflare keep platform logs. We keep Acceptance Records, billing consent records and the records of refunds and objections for 7 years as evidence of your agreement and of what we did. The deletion audit row holds counts only, with no name, email or id, for 1,095 days. A Seller’s own Stripe account stays open when a Workspace is deleted.

B9.5 A Backup is a rolling copy of the database that we keep apart from the live database for recovery. We keep 14 daily copies and 8 weekly copies. A Backup holds the names and sizes of uploaded files but not the files. The Backup Roll-Off Period is 60 days. We cannot take Content out of a Backup before the Backup rolls off.

B9.6 We keep records that the law requires us to keep, and the records that the Retention Schedule in Section 23 (Retention Schedule and deletion) of the Privacy Policy lists.

B9.7 Section 22 (Government requests, civil subpoenas and Legal Holds) explains how to ask us to pause our deletion jobs for a named Workspace.

B10 Audit and information

B10.1 We are a small company, and audits must fit that. They must be proportionate to the size of our business and to the risk.

B10.2 Once every 12 months, you can ask us for a written summary of our security measures and for answers to a reasonable security questionnaire. We give you both.

B10.3 If we obtain an independent audit or assessment report that covers the Service, we give you a copy on request, under confidentiality.

B10.4 Once every 12 months, on 30 days' notice, you or an assessor you appoint may assess our processing of your Content by reviewing documents and interviewing our Staff, at your cost, including our reasonable time at our actual cost. Instead, we may give you a report from a qualified independent assessor. The assessment takes place during business hours without disturbing the Service. It does not reach other Customers' data or our vendors' systems. You and your assessor keep what you learn confidential.

B10.5 We cannot give you audit rights over our Sub-processors. Where their terms let us, we share the reports and security information we receive from them.

B11 Transfers

B11.1 NATEX Work is offered only in the Territory. This is the region statement:

Most processing happens in the United States. Some Model Hosts and other Sub-processors may process information elsewhere, and we do not promise that it stays in the United States.

B11.2 You may be a business that serves people located outside the United States. If you need the Standard Contractual Clauses of the European Commission (Modules 2 and 3) or the UK Addendum to them for Personal Information in your Content, ask us at nshulman@natex.ai. We will enter into them with you.

B11.3 If a transfer mechanism that we or a Sub-processor rely on lapses or is held invalid, we and you will work together in good faith to use another lawful mechanism. If none is available, we will stop the transfer that depends on it.

B12 Government requests

B12.1 If a government asks us for your Content, we follow the Law Enforcement Guidelines in Section 25 (Government requests, safety reports and copyright) of the Privacy Policy.

B12.2 We disclose Content only with your consent or on a warrant for Content, except for emergency disclosures and reports to the National Center for Missing and Exploited Children, as the law allows. We give basic subscriber information on a subpoena and other records on a court order. We point the requester to you. Where the law allows, we tell you before we disclose anything, unless a court order forbids notice or there is an emergency, and we tell you after an order expires.

B12.3 We may challenge or narrow a request that is overbroad or defective.

B12.4 We cannot promise that data is beyond US legal process because it is hosted abroad.

B13 AI terms

B13.1 This is our commitment on training:

NATEX does not train models on your content. It sends requests that use your plan only to hosts that OpenRouter lists as zero-data-retention endpoints, which keep no prompts or replies to train on, apart from the exceptions stated in Section 6 of the Privacy Policy. If you choose to use your own AI account, requests on that account go to your provider, and your provider’s terms decide what it keeps. We do not keep a license to use your Content to train or improve models, and we do not use data from your Connected Services to train models.

B13.2 This is how AI requests are routed:

NATEX Work sends AI requests that use your plan only through OpenRouter, and only to model hosts that OpenRouter lists as zero-data-retention endpoints, meaning endpoints that keep no prompts or replies beyond serving the request, apart from the exceptions below. Every such request asks OpenRouter for both of its filters (zero data retention and no data collection), so if no such host can serve a request it fails instead of going elsewhere. NATEX does not train models on your content. It sends plan requests only to hosts that OpenRouter lists as zero-data-retention endpoints, which keep no prompts or replies to train on, apart from the exceptions below. If you choose to use your own AI account, requests on that account go to your provider instead, and your provider’s terms apply to them.

Those filters do not switch off a Model Host's own abuse and safety systems. Section 6 (AI Features and your information) of the Privacy Policy names the hosts that may keep or review a request, and for how long, and that statement is part of this DPA.

B13.3 Web search is different:

Web search is different: a short, cleaned search phrase (links, e-mail addresses and long numbers removed, never your workspace) goes to Perplexity through OpenRouter, and Perplexity states that it does not retain or train on API data.

B13.3A Two optional features change this. Workspace Memory is built only if a Member (Personal Memory) or an Admin (Team Memory) turns it on, only from Content the person it is built for can open, and it is part of Content under this DPA. If a Member connects an Own AI Account, that Member's requests go to the Own AI Provider the Member chose. That provider is not our Sub-processor. We send the Content to it on the instruction of the Authorized User who connected it, and the Customer is responsible for that instruction as it is for a Third-Party Agent (Section 12 (API, MCP Server and Webhooks) and Section 9.13). Admins cannot see a Member's Own AI Account, but an Admin can switch Own AI Accounts off for the whole Workspace, and while that switch is off we send no Content of that Workspace to an Own AI Provider. Group planning that involves more than one Member is always written by our plan models. We have no data processing terms with an Own AI Provider for you.

B13.4 Collections that are turned off for AI (by an Admin or a Member, or by default for health collections), records flagged "AI never touches this", and Student Data are removed on our servers from the Assistant, search and Teammates. This is the rule for Local-Only Mode:

Local-Only Mode stops the Assistant, search and Teammates in NATEX Work from sending your Content to AI. It does not govern calls you make through the API or Webhooks you configure.

B13.5 You decide which collections to exclude. Section 9 (AI Features) and Section 16 (Professional, regulated and government use) apply.

B14 Excluded data

B14.1 This DPA does not cover Prohibited Data. You must not put Prohibited Data into NATEX Work or send it to an AI Feature.

B14.2 NATEX Work is not for Protected Health Information, and we sign no business associate agreements. It is not for payment card numbers or security codes.

B14.3 If we find data like this, we may ask you to remove it, suspend the Account, and delete it on your instruction without reading it. Section 15 (Prohibited Data and Restricted Data) and Section 16 (Professional, regulated and government use) apply.

B14.4 A Seller's own payment instructions on an invoice or booking page are not Prohibited Data. Restricted Data may be in your Content. This DPA covers it as Content, but we give no assurance that NATEX Work fits the rules that apply to it.

B15 Customer duties

B15.1 You are responsible for:

• (a) the lawful basis for the Personal Information you put into NATEX Work, and the notices the law requires you to give the people it concerns;
• (b) giving us only lawful instructions;
• (c) the consents the law requires for recording, captioning, transcribing and AI processing of Calls and other Content; and
• (d) a notice about how you handle information on your forms, booking pages, invoices and other Public Pages. The line we add to a Public Page does not replace your notice.

B15.2 You give the people in your Content the Workspace owner's contact details and you honor their requests.

B15.3 Section 18 (Your duties to the people whose data you handle) says more.

B16 Liability and precedence

B16.1 Our liability under this DPA is subject to the limits in the Terms. For an Individual Customer, that is the cap in Section 29 (Limitation of liability). For an Organization Customer, it is the cap and the data-protection limit in Section 37 (Organization Customers: liability and indemnity), as Section 37.3 sets it.

B16.2 We give no uncapped indemnity for data. Nothing in this DPA limits a liability that the law forbids limiting.

B16.3 On how we process Personal Information in Content, this DPA prevails over the Terms. For billing, Schedule 1 controls. For conduct, the AUP controls. For disputes, Section 31 (Arbitration and class action waiver) controls.

B17 Regulated customers

B17.1 If you are a financial institution, an investment adviser, a tax preparer or an insurance licensee, Section B5 (Security measures) and Section B7 (Security Incident notice) are the contract terms you need to oversee us as an outside vendor. The 72-hour notice in Section B7 (Security Incident notice) is the notice period for a Security Incident that affects your Content.

B17.2 We give no assurance that you or we comply with the Gramm-Leach-Bliley Act, Regulation S-P, state insurance data security laws or Internal Revenue Code section 7216. You remain responsible for your own regulatory duties. Section 16 (Professional, regulated and government use) says more.

B18 How the DPA takes effect

B18.1 This DPA is part of the Agreement by reference. It takes effect on the day you accept the Terms, or on the day you begin to use the Service for a business, whichever is later. You do not sign it. The Acceptance Record is the record of your acceptance.

B18.2 This DPA is also published as its own page at /legal/dpa, and its earlier versions are at /legal/history.

B18.3 If you are on the Business or Scale Paid Plan and want a countersigned copy, email nshulman@natex.ai. We will sign it.

Annex B-1. Details of processing

Annex B-2. Security measures

The security measures are those in Section B5 (Security measures). Annex B-2 is that section.

End of Annex B. Effective Date: [[OPEN-01]]