Terms of Service

These Terms of Service ("Terms") govern the use of the hosted termynl service. termynl is operated by HODY, based in Maryland, USA ("termynl", "we", "us"). By creating or joining a workspace, starting a trial, or using the service, you agree to these Terms. The Privacy Policy and the Acceptable Use Policy are part of these Terms.

1. Who may use termynl

• termynl is a service for organizations. If you accept these Terms for an organization, you confirm that you have authority to bind it. In that case "Customer" means that organization.
• You must be at least 18 years old to accept these Terms for a Customer, and at least 16 years old to use the service.
• Access is currently by invitation, or by signing in with an address on a domain a workspace has verified.

2. Definitions

• Service: the hosted termynl application, API and MCP endpoint that we operate.
• Workspace: a Customer's tenant in the Service.
• User: anyone with access to a Workspace, in the role of owner, admin, member or guest.
• Customer Content: everything Users create, upload or import into a Workspace, including tasks, issues, projects, docs, comments, views, files and AI conversations.
• Connected Service: a third-party account or service a User or admin connects, such as Google, Microsoft, GitHub (code hosting), Notion, an S3-compatible bucket, an AI provider account, a Firecrawl account whose key an admin adds for web access, or an MCP client.
• Self-Hosted Software: the single-tenant termynl build that an organization runs on its own infrastructure.

3. The Service

• termynl provides teams, tasks, issues, projects, docs, saved views, the Tyn assistant and MCP access.
• The email, calendar, chat and calls modules are paused and not available. Data stored by them before the pause is handled as the Privacy Policy describes.
• We develop termynl continuously and may add, change or remove features. We will not make a change that materially reduces the core functionality of a paid subscription during its current billing period without notice.
• Features we mark as preview, beta or "coming soon" are provided as they are and may change or be withdrawn.

4. Accounts, roles and administration

• Workspace roles are owner, admin, member and guest. Owners and admins manage membership, roles, join rules, storage, models and billing.
• Admins can let people join through email invitations, verified domains, a Google Workspace or Microsoft Entra group gate, and SCIM provisioning. The group gate can deactivate members automatically when they leave a chosen group. Admins are responsible for configuring these rules.
• Guests see only the teams and projects explicitly shared with them. People on the Workspace's own verified domain cannot be guests.
• Owners and admins can require two-factor authentication for every User of the Workspace, choose the allowed methods and how long a device stays trusted, and reset a User's two-factor authentication (which signs that User out everywhere and disconnects their apps). Admins can reset members and guests; only owners can reset admins; only another owner can reset an owner; nobody can reset their own. Each reset is recorded in the Workspace's audit log and the User is emailed.
• Single sign-on. Admins can connect the Workspace to the Customer's own identity provider (SAML or OpenID Connect) and can require that Users sign in only that way. The Customer is responsible for its identity provider: its configuration, its security, who it lets sign in, when it removes people and how it protects their accounts. We rely on what the identity provider tells us. A person the Customer's identity provider signs in, with an address on a verified domain of the Workspace, gets access to the Workspace as the Customer has set it up, and we are not responsible for access the Customer's identity provider grants. We are also not responsible for a Workspace being unreachable because the Customer's identity provider is down or wrongly configured. To prevent a lock-out, owners can still sign in with an emailed link plus termynl two-factor sign-in while Require SSO is on (a "break-glass" sign-in). Customers should keep at least two owners with two-factor sign-in set up and should not share them. On request, and where a Customer cannot reach any owner, we may turn Require SSO off for the Workspace after verifying the request, and we will tell the Workspace's owners.
• The Customer is responsible for its Users' activity in the Workspace and for keeping its sign-in methods secure. Tell us promptly at hello@termynl.com if you suspect unauthorized access.
• Workspace ownership can be transferred to another member. The sole owner of a Workspace that has other members must transfer ownership before deleting their own account.

5. Trial, fees and billing

• Price. termynl costs $35 per user per month. Every active member, admin and owner is a paid seat. Guests are free, up to 5 guests per paid seat.
• Trial. New subscriptions start with a 14-day free trial. A payment method is collected at checkout. The subscription converts to paid at the end of the trial unless it is canceled before then.
• Renewal. Subscriptions renew monthly until canceled.
• Adding seats. An added seat is prorated onto the next invoice.
• Changing seats. An owner can change paid seats in the app (Admin settings → workspace data), down to the number of active members (and at least one seat per five guests). When an admin adds someone and no seat is free, the app shows the seat price and a seat is added only after the admin confirms the purchase. Automatic adds (domain or group sign-ups when the Workspace's policy allows it, and SCIM when an owner turns on automatic seat changes) add seats only within the Workspace's monthly limit; otherwise the new member waits for an admin to approve the extra seat. When an admin removes or deactivates someone, they choose whether to keep or drop that seat; with automatic seat changes on, a SCIM deactivation drops one. Reductions apply at once and the unused time is credited on the next invoice.
• AI allowance. Each user gets one monthly allowance of AI usage that covers every provider and model on termynl's accounts. AI runs use termynl's own provider accounts while a person's included usage lasts; after that, a workspace's own provider key is used, under the workspace's agreement with that provider. Without such a key, models on termynl's accounts are unavailable to that user until their next monthly cycle. Usage on termynl's accounts counts against the allowance at the model provider's list price plus 20%. Runs on the Customer's own AI provider key are not billed by termynl and do not count against the allowance; the provider bills the Customer directly.
• AI during the trial. A trial runs only the basic model of each provider, on any key, with no voice, image or video.
• Payments. Stripe processes payments. termynl does not receive or store card numbers. Owners and admins manage payment methods and cancellation in the Stripe billing portal.
• Cancellation. Cancellation takes effect at the end of the current billing period.
• Taxes. Prices exclude taxes. The Customer is responsible for applicable taxes, which we may collect where required.
• Price changes. We will give owners at least 30 days' notice of a price increase. It applies from the next billing period after the notice period.
• Discounts. We may offer promotion codes, discounts or complimentary licenses at our discretion.
• Refunds. Fees are non-refundable except where required by law.
• Non-payment. If a payment fails, the Workspace stays available while Stripe retries the payment. If the subscription is then canceled or expires, the Workspace is blocked until a subscription is active again, and is deleted 60 days after the subscription ended (section 13). We may also suspend a Workspace whose fees are overdue after notice to its owners.

6. Customer Content

• The Customer owns its Customer Content. We claim no ownership of it.
• The Customer grants us a limited, worldwide, non-exclusive license to host, store, copy, index, transmit, display and process Customer Content only as needed to provide, secure and support the Service. This includes sending it to our sub-processors and to the Connected Services the Customer enables, as described in the Privacy Policy.
• We do not use Customer Content for advertising, and we do not train AI models on it.
• The Customer is responsible for its Customer Content. It confirms that it has the rights and any legal basis needed to put that content, including personal data and content brought in from Obsidian vaults, Notion exports or a connected Notion workspace, into termynl.
• termynl is not designed for protected health information, payment card data or other regulated data that requires special agreements. We do not sign HIPAA business associate agreements.

7. Privacy and data protection

We process personal data as described in the Privacy Policy. For Customer Content, we act as the Customer's processor. Customers that need a data processing agreement can request one at hello@termynl.com.

8. Connected Services and file storage

• When a User or admin connects a Connected Service, they authorize termynl to access it within the permissions they grant, and only to provide the Service. The Connected Service's own terms apply to it, and we are not responsible for its availability, security or changes.
• File storage. A workspace admin chooses where attachment files are stored: Google Drive, OneDrive or an S3-compatible bucket. The file bytes live in the Customer's own storage account. The Customer is responsible for that account, including its availability, access, retention and backups. If the connection is removed or the account becomes unavailable, attached files may stop opening in termynl.
• Audit log streaming. A workspace admin can send the workspace's audit log to destinations the Customer configures (a web address, an S3-compatible bucket or a syslog server). The Customer chooses and is responsible for those destinations, including who can read what they receive, their security and retention, and any credentials it gives us for them. Delivery is at least once and may be delayed or paused when a destination is unavailable; entries waiting beyond the stated limits may be dropped. The audit log in the Service remains the record.
• Meeting content. When a User brings meeting notes, transcripts, attendee names or recording links into termynl from Zoom or Google Meet (by hand or automatically), the Customer and that User are responsible for having the right to do so, including any notice to and consent from the people in the meeting that the law or the Customer's own policies require. termynl brings in only what the User can open in their own Zoom or Google account.
• GitHub (code hosting). The Customer authorizes termynl to receive data from the GitHub accounts and repositories its admins connect, through termynl's GitHub App, and only to provide the Service. termynl only reads from GitHub and does not change anything in it, with one exception: when an admin disconnects in termynl, termynl asks GitHub to uninstall its app from that account. That request is best effort; if GitHub does not confirm it, an owner of the GitHub account removes the app in GitHub. Agent labels (which coding agent likely opened a pull request) are estimates made from public signals and termynl's records, shown with their confidence, and may be wrong. They are on by default. The Customer is responsible for how it uses them, and an admin can turn their display off (stored work-start records are kept). GitHub's availability and changes are outside termynl's control. For a self-hosted server, the Customer registers and controls its own GitHub App.
• Drive. Each User connects their own Google or Microsoft account. The Customer and its Users are responsible for the files they link and for choosing to share them. Sharing uses the User's own account and is subject to the provider's and the Customer's own sharing rules; termynl reports a refusal and never tries another way (no public links, no guest invitations). For OneDrive and SharePoint, termynl shares only with people who have connected their own OneDrive in the same Microsoft organization as the person sharing; everyone else is reported as outside the organization. termynl only adds view access and never removes anyone's access in a drive, so removing access there is the Customer's job, including after a person leaves an item or the workspace and after the workspace is deleted. A linked file's name is shown to everyone who can see the item. Provider availability and changes (for example Microsoft retiring its "Shared with me" list, which termynl replaces with search) are outside termynl's control.
• We do not delete files from the Customer's storage account when a subscription ends, except as the Customer instructs. When an admin moves files between storage backends, originals are deleted only after each copy is verified.

9. AI features

• AI features are optional. Workspace admins choose which models are available.
• Tyn and connected MCP apps act as the User who uses or authorized them, with that User's permissions and, for apps, within the scopes granted. Their changes are made in that User's name and attributed in activity ("name via Tyn", "via" the app). After Tyn reads text written by someone else, risky changes wait for the User to apply them; this is a safeguard, not a guarantee that every change Tyn makes was reviewed.
• AI output can be wrong, incomplete or unsuitable. Review it before relying on it. The Customer is responsible for the actions its Users ask Tyn or connected apps to take.
• Voice, dictation, read aloud and recorded notes. These features send the audio you speak or record, and text to be read aloud, to Google's Gemini API, as our sub-processor when we run it on our account and under the Customer's own terms with Google when the Customer's own key is used (see the Privacy Policy). They are not available in a trial or to guests. Notes, summaries, action items and transcripts written by AI can be wrong, miss things or attribute words to the wrong speaker. Check them before you rely on them, and especially before you act on an action item.
• Recording other people. The Customer and each User who records are responsible for telling everyone present and for getting any consent the law requires before recording a conversation, a meeting or a call, including in places where everyone must agree. The confirmation the app asks for before a recording starts is a reminder, not legal advice and not a substitute for that consent. The Customer decides whether the question is shown, and whether recordings are kept.
• Web access. Tyn's web access is off by default; a workspace admin turns it on, and each User can turn it off for themselves. It is not available in a trial or to guests. Answers that use the web can be wrong, out of date or based on unreliable pages; check the sources before you rely on them. After Tyn uses the web in an answer, Tyn holds every change it would make until a User applies it. The Customer is responsible for its own Firecrawl account and API key, for Firecrawl's charges and terms, and for the pages its Users have Tyn read, save as docs or crawl, including having the right to copy them. We are not responsible for third-party websites, their content, or Firecrawl's service. Answers grounded with Google Search are shown with Google's search suggestions and their text is removed from saved chats after two years, as the Privacy Policy describes. That removal does not reach exports or backups the Customer has already made, which the Customer is responsible for.
• If the Customer uses its own AI provider key, the Customer's agreement with that provider governs the provider's processing and charges.
• Use of AI features must also follow the AI provider's usage policies, as the Acceptable Use Policy describes.

10. Acceptable use and suspension

Users must follow the Acceptable Use Policy. We may suspend access to all or part of the Service, immediately if necessary, if we reasonably believe that:

• a User has violated these Terms or the Acceptable Use Policy;
• use of the Service threatens its security or other customers;
• fees are overdue, as described in section 5; or
• suspension is required by law.

Where practical, we will notify the Workspace owners first and restore access once the issue is resolved.

11. Intellectual property

• We own the Service, including its software, design and documentation, except Customer Content and third-party components. These Terms grant no rights to it beyond using the Service as they describe.
• If you send us feedback or suggestions, we may use them without obligation to you.
• Self-Hosted Software is provided under the license that accompanies it, not under these Terms. An organization running it is responsible for its own installation and data, and we are not its service provider or processor. The multi-tenant, billing and operator components of the hosted Service are proprietary and not part of the Self-Hosted Software.

12. Confidentiality

Each party will protect the other's non-public information that it receives in connection with the Service, using at least reasonable care. It will use that information only to perform under these Terms and disclose it only to people who need it for that purpose and are bound by similar duties, or as required by law. Customer Content is the Customer's confidential information.

13. Term, termination and your data

• These Terms apply while the Customer uses the Service. The Customer may stop at any time by canceling its subscription.
• We may terminate the Customer's access for material breach that is not cured within 30 days after notice. We may terminate immediately for serious violations of the Acceptable Use Policy or where the law requires.
• While a subscription is active, and for 30 days after it ends, workspace admins can export the Customer Content themselves in the app (JSON and files). The Customer can also retrieve it through the API and MCP tools while the subscription is active. Sixty days after a subscription ends, the Workspace and its Customer Content are deleted automatically unless a paid subscription is started again first.
• We delete Customer Content as described in the Privacy Policy. Files in the Customer's own storage account stay there.
• Sections that by their nature should survive termination do so, including fees owed, Customer Content, confidentiality, disclaimers, limitation of liability, indemnification and governing law.

14. Disclaimers

Each party confirms that it has the authority to enter into these Terms. Except as expressly stated in these Terms, the Service is provided "as is" and "as available". To the extent the law allows, we disclaim all other warranties, express or implied, including merchantability, fitness for a particular purpose, title and non-infringement. We do not promise that the Service will be uninterrupted, error-free or free of harmful components, or that AI output will be accurate. We do not currently offer a service-level agreement.

15. Limitation of liability

To the extent the law allows:

• Neither party is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue or data, even if it was advised of the possibility.
• Each party's total liability arising out of or relating to these Terms is limited to the fees the Customer paid for the Service in the 12 months before the event giving rise to the claim.

These limits do not apply to the Customer's obligation to pay fees, to either party's indemnification obligations, or to liability that cannot be limited by law.

16. Indemnification

The Customer will defend and indemnify us against third-party claims arising from its Customer Content, from its Users' violation of these Terms or the Acceptable Use Policy, or from its use of Connected Services in breach of their terms. This includes the resulting damages and reasonable legal costs.

17. Governing law and disputes

• These Terms are governed by the laws of the State of Maryland, USA, without regard to its conflict-of-laws rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.
• Any dispute arising out of or relating to these Terms or the Service will be brought exclusively in the state or federal courts located in Maryland. Each party consents to their jurisdiction.
• Nothing in these Terms removes rights you have under mandatory laws of your country of residence that cannot be waived by contract, including those of the European Union and its member states and the United Kingdom.

18. Changes to these Terms

We may update these Terms. For material changes, we will notify Workspace owners by email or in the app at least 30 days before the change takes effect, unless a change is required sooner by law. Continued use after that date means acceptance. If the Customer does not agree, it may cancel before the change takes effect.

19. General

• Assignment: neither party may assign these Terms without the other's consent, except to a successor in a merger, acquisition or sale of substantially all related assets.
• Force majeure: neither party is liable for delays or failures caused by events beyond its reasonable control. This does not excuse payment obligations.
• Export and sanctions: the Customer will not use the Service in violation of U.S. export controls or sanctions, or make it available to sanctioned persons or countries.
• Notices: we send notices to Workspace owners' email addresses or in the app. Notices to us go to hello@termynl.com.
• Relationship: the parties are independent contractors.
• Entire agreement: these Terms, with the policies they reference and any signed order form or data processing agreement, are the entire agreement on this subject.
• Severability and waiver: if a provision is unenforceable, the rest remains in effect. Not enforcing a provision is not a waiver.

20. Contact

HODY, operator of termynl, Maryland, USA · hello@termynl.com

Privacy Policy · Acceptable Use Policy · ← back to termynl