Every change to our terms.

Posted 2026-10-19 · Takes effect 2026-10-19

October 19, 2026 — first published as its own document. § 1 and § 2 restate Data Processing Addendum § 11.1 and § 11.2 as they stood in DPA version 1.10, unchanged in substance; § 2 adds the date before which the typed-decision features send nothing, which the DPA states in its Effective Date. From DPA version 1.11, DPA § 11 incorporates this Statement by reference and says how it changes.

Posted 2026-10-19 · Takes effect 2026-12-03

October 19, 2026 — § 6, § 8.1, § 11, § 12.1 and § 15. Operational detail moves out of this DPA into three documents it incorporates by reference, each with its own change process, so that a new vendor, a changed safeguard, or a new location is no longer an amendment to this DPA. § 6 now gives Inscendo general authorisation to engage Sub-Processors and names them in the Sub-Processor List at /legal/subprocessors, to which the § 6.2 table moves unchanged. The old § 6.3, under which Customer was responsible for reviewing the list, is replaced by notice: a new Sub-Processor is posted at least thirty days before it begins processing Customer Personal Information, and everyone subscribed to changes to the List is notified. New § 6.4 lets Customer object within thirty days and, if Inscendo does not resolve the objection, terminate before the Sub-Processor begins processing its information; new § 6.5 covers an emergency replacement and § 6.6 other changes to the List. § 8.1 keeps the safeguards Inscendo commits to and the restoration terms; the detail moves to the Security Measures at /legal/security-measures, and new § 8.1A says no update to them may materially decrease the overall protection of Customer Personal Information during the Subscription Term. § 11 keeps the United States commitment and the typed-decision exception; the detail moves to the Data Location Statement at /legal/data-location, and new § 11.3 says a new location outside the United States is posted thirty days ahead and notified, and may be objected to, as a new Sub-Processor is. § 12.1 follows the § 8.1 renumbering (the off-site backup copy is now § 8.1(e)). § 15 points at the monthly legal release in MSA § 15. Takes effect December 3, 2026 for Customers already bound to an earlier version (§ 15, MSA § 15.1). No Sub-Processor, role, location, or Customer obligation changes.

Posted 2026-10-19 · Takes effect 2026-10-19

October 19, 2026 — § 2.12, § 4.1, § 5 and § 13. New § 2.12 and a new § 5 entry disclose the subscription to sub-processor and data-location changes: the email address subscribed, the IP address and time of each subscribe and confirmation request, why they are kept, and for how long. § 4.1 now points at the Sub-Processor List at /legal/subprocessors, the document the Data Processing Addendum now incorporates, which names each sub-processor, its role, and its region. § 5 now says it is the Retention Schedule that the Master Subscription Agreement (§ 15.7) incorporates, and that a change shortening how long Customer Data stays available, or lengthening how long we keep personal information after it is deleted or after an account ends, is announced in a monthly legal release at least thirty days ahead. § 13 says every change is recorded in our public change log, and that a change needing notice is announced in the monthly legal release. No collection, use, disclosure, or retention period changes. Effective on posting.

Posted 2026-10-19 · Takes effect 2026-10-19

October 19, 2026 — first published as its own document. It sets out the safeguards that Data Processing Addendum § 8.1 listed through DPA version 1.10, and the tenant-separation detail in Master Subscription Agreement § 10.1 through MSA version 1.16, unchanged in substance. The telemetry and backup periods are stated in the Retention Schedule (Privacy Policy § 5), as they already were. From DPA version 1.11 and MSA version 1.17, both incorporate this document by reference.

Posted 2026-10-19 · Takes effect 2026-10-19

October 19, 2026 — first published as its own document. The table in § 1 is the table that Data Processing Addendum § 6.2 carried through DPA version 1.10, with its cross-references pointed at the documents that now hold the detail; no Sub-Processor is added, removed, or given a new role, and no region changes. From DPA version 1.11, the DPA incorporates this List by reference, and DPA § 6 says how it changes.

Posted 2026-10-19 · Takes effect 2026-12-03

October 19, 2026 — § 15 rewritten, § 10.1, the opening paragraph, and § 4.7. Legal updates are now released monthly, so that Customer is not sent a notice every time a document changes. New § 15.2 defines a Material Adverse Change: a new obligation, restriction, fee, or ground for suspension or termination that applies to Customer; a narrower commitment by Inscendo, including a security, data-location, retention, or deletion commitment; or a new purpose for which Customer Personal Information is processed. § 15.1 keeps the thirty days' notice and the termination remedy, and § 15.3 gathers every Material Adverse Change into a monthly legal release with one notice day and one effective date at least thirty days later. § 15.4 says notice goes by email to the Legal Notice Email and the account administrators, in the notice centre in the Service, and in the public change log, and that one notice may cover a whole release. § 15.5 says any other change takes effect when posted and is recorded in the change log and the notice centre, without an email. § 15.6 lets a change that law, a court, or a regulator requires take effect sooner than the next release, with notice as early as practicable. New § 15.7 incorporates four Referenced Documents by reference (the Sub-Processor List, the Security Measures, the Retention Schedule in Privacy Policy § 5, and the Data Location Statement), each with its own change process, and says this Agreement and the Data Processing Addendum control over them. § 10.1 points at the Security Measures, which now hold the tenant-separation detail, and the opening paragraph names the Referenced Documents among the documents this Agreement incorporates. § 4.7 now says that copies of telemetry held in routine backups are deleted within the backup-retention window stated in the Privacy Policy (§ 5), which describes a practice already in place and applies from the day it is posted. The other changes take effect December 3, 2026 for Customers already bound to an earlier version (§ 15.1). No fee, plan, or other Customer obligation changes.

Posted 2026-10-18 · Takes effect 2026-12-03

October 18, 2026 — § 12.1. Deletion on termination now also covers the automatic deletion of an account whose Premium has ended and was not restarted, under MSA § 4.8 as amended by MSA Version 1.16: no sooner than ninety (90) days after Premium ended, with notice to the account administrators thirty (30) and seven (7) days before, cancelled if Premium is restarted, and followed by the same grace period as a self-service deletion. No Sub-Processor, location or security measure changes.

Posted 2026-10-18 · Takes effect 2026-10-18

October 18, 2026 — § 5. The retention entries for account information, Customer Data and our own customer record now describe automatic deletion after Premium ends: where the MSA provides for it (MSA § 4.8), an account whose Premium has ended and is not restarted may be deleted no sooner than ninety (90) days after Premium ended, after emails thirty (30) and seven (7) days before and a further deletion grace period. The Customer Data entry no longer states a thirty (30)-day post-termination retention, which the MSA does not provide; it now follows MSA § 4.8. No new collection, use or disclosure.

Posted 2026-10-18 · Takes effect 2026-12-03

October 18, 2026 — what happens when Premium ends. New § 6.9C: when a Premium subscription ends, because Customer cancelled it (including during a free trial) and the period ran out, or because the payment processor closed it after the retries for a failed charge were exhausted, the account is no longer suspended; it continues in **limited mode**, on the features available without a subscription, with no included or free usage allowance, paying for usage only from the Wallet balance; at a zero balance usage pauses and access to the account remains. § 6.9A(e) and § 6.9 now say the same, and § 14.4(b) says an ended subscription is not a suspension ground; a failed charge on a subscription still in effect, and a subscription in effect with no payment method, remain suspension grounds. New § 6.9B: complimentary Premium that Inscendo grants with an agreed date on which paid Premium begins may be suspended if that date passes without a payment method and paid subscription set up, until they are; § 14.4(b) names that ground. § 4.8 adds automatic deletion: an account whose Premium has ended and is not restarted may be deleted no sooner than ninety (90) days after Premium ended, after emails thirty (30) and seven (7) days before, followed by the existing deletion grace period; restarting Premium cancels the countdown, and a failed charge still being retried does not start it. No fee or price changes.

Posted 2026-10-14 · Takes effect 2026-10-14

October 14, 2026 — § 2(i). Describes saved logins, an optional feature in which you save a username and password for a website and the Companion types them into that website's sign-in page when you ask. Discloses an existing feature; adds no obligation for you.

Posted 2026-10-14 · Takes effect 2026-10-14

October 14, 2026 — § 2.4, § 4.8 and § 5. § 2.4 now describes saved logins: if a user chooses to save a username and password for a third-party website, those values are stored encrypted in the organization's own workspace vault, the Browser Companion types them into that website's sign-in page when the user asks, and the values are never shown to Inscendo IQ or sent to our AI model provider; § 5 says they are deleted when the user deletes the saved login or the workspace is deleted. § 4.8 now says that our own customer record is also created when a free trial of a paid plan starts or is extended, holding the account owner's name and email address, the owner's choice about product updates and promotions, and the trial's start and end dates; § 5 says how long we keep it. Discloses practices of the Service; no new category of personal information is collected, and nothing is Sold or Shared.

Posted 2026-10-10 · Takes effect 2026-10-10

October 10, 2026 — § 2(h), § 5(c) and § 5(d). The sensitive-field sensor now treats a password, one-time-code, or payment-card field as sensitive when it is visible, has keyboard focus, or already holds a value, rather than whenever it is present in the page; a hidden, empty field no longer causes a detach. § 2(h) and § 5(d) also describe what happens after a detach: when no sensitive field remains, the Companion re-attaches to the same tab automatically, and Inscendo IQ may continue the task it was performing there. Consent is requested again for this version.

Posted 2026-10-10 · Takes effect 2026-11-12

October 10, 2026 — § 6.2 and § 11. This version replaces version 1.8, posted earlier the same day, and corrects what 1.8 said about where the decision model processes text. § 6.2 adds two Sub-Processors for the Service's typed-decision features, which read text the Service asks about and return only a choice, a yes/no likelihood, or a score, from November 12, 2026: Vercel Inc., whose AI gateway routes each request, and TypeSafe AI, Inc., which runs the decision model and is engaged through Vercel's gateway under Vercel's agreements with it. § 11 is split: § 11.1 keeps the United States processing and storage commitment for all other Customer Personal Information. New § 11.2 says that TypeSafe AI states that it hosts its service in the United States, but that neither provider commits to processing these requests only in the United States: the gateway may receive and process a request in data centers outside the United States, it does not pin the region in which the decision model runs, and a request a provider flags for abuse or safety review may be handled outside the United States. § 11.2 also says that every such request is made with zero data retention and neither provider trains on it, and that no text from a workspace whose AI Security setting is Sealed, or cannot be determined, is sent to either provider. Takes effect November 12, 2026 for Customers already bound to an earlier version (§ 15, MSA § 15.1). No change to roles or to any Customer obligation.

Posted 2026-10-10 · Takes effect 2026-10-10

October 10, 2026 — § 6.2 and § 11. § 6.2 adds two Sub-Processors for the Service's typed-decision features, which read text the Service asks about and return only a choice, a yes/no likelihood, or a score: TypeSafe AI, Inc., which runs the decision model in the United States, and Vercel Inc., whose AI gateway routes each request to it. § 11 is split: § 11.1 keeps the United States processing and storage commitment for all other Customer Personal Information, and new § 11.2 says that the gateway may receive and process a typed-decision request in data centers it operates outside the United States before forwarding it, that every such request is made with zero data retention and neither provider trains on it, and that no text from a workspace whose AI Security setting is Sealed, or cannot be determined, is sent to either provider. Takes effect November 12, 2026 for Customers already bound to an earlier version (§ 15, MSA § 15.1). No change to roles or to any Customer obligation.

Posted 2026-10-10 · Takes effect 2026-10-10

October 10, 2026 — § 2.7, § 3.1, § 4.1 and § 4.8. Corrects version 1.14, posted earlier the same day. TypeSafe AI states that it hosts its service in the United States, but neither it nor Vercel commits to processing typed-decision requests only in the United States, so § 3.1 and § 4.1 now say that either provider may process a request outside the United States. § 2.7 now says that our website and the Service load typefaces from Google Fonts, and what Google receives when they do. § 4.8 now also lists, in our own customer record of a paid subscription, which categories of our text messages the account owner has agreed to or withdrawn from, and when, so that we text the account owner only in the categories agreed to. No new category of personal information is collected, and nothing is Sold or Shared.

Posted 2026-10-10 · Takes effect 2026-10-10

October 10, 2026 — § 3(f), § 3.1 and § 4.1. From November 12, 2026, the Service's typed-decision features send text to TypeSafe AI, the AI decision model behind them, through Vercel's AI gateway, which routes each request to it and may process a request outside the United States before forwarding it. § 3(f), § 3.1 and § 4.1 add both. They receive that text with zero data retention and do not train on it, and neither receives text from a workspace whose AI Security setting is Sealed. No new category of personal information is collected, and nothing is Sold or Shared.

Posted 2026-10-10 · Takes effect 2026-10-10

October 10, 2026 — § 2.1, § 2.7, § 2.11, § 4.1, new § 4.8, § 5 and § 10.1. When an organization starts a paid subscription, including when a free trial converts to a paid one, we keep our own customer record of it in a workspace we operate for ourselves on the Service. New § 4.8 says what that record holds (the organization's name, the account owner's name, email address and, if given, account mobile number, the owner's choice about product updates and promotions, the plan and first payment, and any partner link), that members of our team are emailed when it is created, and what we use it for; § 5 says how long we keep it. § 2.1 now says that a member of our team may call the account owner at the account mobile number about setting up and using that subscription, and that you can ask us not to; the number is still never used for marketing, by text or by call, and we send it no text message other than the codes you ask for unless you separately agree to receive our text messages. § 4.1 and § 2.11 now name the business email, calendar and telephone providers that carry our own team's email, calls and meetings, and § 10.1 is conformed. Separately, § 2.7 says that after you book a demo or consultation on our website, your browser keeps the name, work email address, company name and phone number you entered so that our sign-up form can open with them filled in, that nothing is sent to us unless you submit that form, and that the form uses them only within twenty-four (24) hours. Nothing is Sold or Shared.

Posted 2026-10-08 · Takes effect 2026-10-08

October 8, 2026 — § 2.2. The authentication-event records we already keep for each sign-up now include each step of our sign-up page that you reach (including opening the form, and a submission that was refused) with the reason it was refused, the partner referral code it was made with, and which sign-up form was used. When the page reports a step, it sends at most a one-way hash of the email address you typed, computed in your browser, and never the address. § 2.2 now also says that we use these records to find out why a sign-up or sign-in did not complete when you or your organization asks us for help, as well as to detect credential abuse. No new category of personal information is collected, the ninety (90) day retention period is unchanged, and nothing is Sold or Shared.

Posted 2026-10-06 · Takes effect 2026-10-06

October 6, 2026 — Twilio Inc. added to the § 6.2 Sub-Processor table: it delivers the one-time sign-in, verification, and password-reset codes that Customer's authorized users ask for, by text message or automated voice call, and receives only the destination phone number, the code, the delivery channel, and whether the code was later used. Posted, with the public Sub-Processor List, before any code is sent through it (§ 6.3). No change to roles, data residency (§ 11), or any Customer obligation.

Posted 2026-10-06 · Takes effect 2026-10-06

October 6, 2026 — § 2.1, § 4.1, § 5 and § 10.1. The one-time sign-in, verification and password-reset codes you can choose to receive at your account mobile number are now delivered by Twilio, which § 4.1 adds to the Sub-Processor summary, and a code can also be read to you by an automated call when you ask for one. § 2.1 says what we give Twilio to deliver a code (the number, the code, whether to text or call, and afterwards whether the code was used), that we ask for and record your consent to these account security messages where you enter a number, that a new number is held unused until you verify it, and that after a password reset by text, sign-in by texted code is paused on the account for a period. § 5 says how long each of those is kept, and § 10.1 records the disclosure. The account mobile number is still never used for marketing, its use is narrowed to verifying it and delivering the codes you ask for, and nothing is Sold or Shared.

Posted 2026-10-06 · Takes effect 2026-10-06

October 6, 2026 — Inscendo now sends the one-time sign-in, verification, and password-reset codes a user asks for to the mobile number on that user's account, by text message or, on request, by an automated call. New § 9A.1(c) describes those **Account Security Messages**; § 9A.2 says they are sent only when asked for; § 9A.3 says they are sent at any hour, because they are not solicitations; § 9A.6 says what replying STOP to one does and how to get codes back. § 5.6 and § 12.2(b) no longer make Customer the sender of record for, or the indemnitor of, messages Inscendo itself sends to Customer's users about their own accounts. Narrows Customer obligations only; no fee, plan, or Customer obligation is added.

Posted 2026-10-06 · Takes effect 2026-11-09

October 6, 2026 — every new company now starts Premium on a free trial. New § 6.9A states its terms: a payment method is collected at signup; nothing is charged for Premium during the trial; the trial's length is the one shown at signup, and Inscendo may lengthen a particular trial but never shorten one; usage during the trial is a single allowance for the whole trial; at the trial's end the subscription converts to paid and renews monthly on that day under § 6.9, unless Customer cancels before then, in which case nothing is charged; Inscendo emails a confirmation at signup and a reminder before the first charge; one trial per company. § 6.9 now says a free trial or free period is billed at its end rather than in advance, and that while a Premium charge has failed, or while a subscription in effect has no payment method on file because Customer removed it, Inscendo may suspend access to the account (not only the subscription benefits) until a payment method is on file and the charge succeeds. § 14.4(b) adds the second case to the suspension grounds. No fee or price changes.

Posted 2026-10-02 · Takes effect 2026-10-02

October 2, 2026 — Version 1.0 was a per-company template, signed outside the Service for one named capsule, with blanks for the company, the capsule, and the licensing body. This version is the same acknowledgment made general and accepted in the Service. It covers every capsule, widget, automation, and other artifact in the company's workspace, whoever built or published it; it is accepted by checkbox, on the company's behalf, by the person who creates the company or who takes ownership of a workspace Inscendo set up for the company, and the acceptance is recorded with this document's version, effective date, and hash, the time, and the accepting person; it names no version of any other document, so it always refers to the versions in effect when it is accepted; and new § 5 states what Inscendo did when it set up a workspace before handing it over, and how the company adopts that work. §§ 1 through 4 restate, for every artifact, obligations the Master Subscription Agreement already imposes, and add none.

Posted 2026-10-02 · Takes effect 2026-10-02

October 2, 2026 — § 1.3(a) and § 3.9 pointed the reader at the signup clickwrap specification, an internal engineering document that is not published, for the attestations and the marketing opt-in a User gives at signup. Both now refer to what the User is shown and accepts on the signup screen, which is what they always meant. § 3.11(f) said the yearly reminder California law requires reaches only annual plans, and so not the monthly Premium subscription; that reading of the statute is not settled, so § 3.11(f) now says Inscendo sends whatever periodic reminder the law applying to a Consumer requires, monthly plan or not. No Consumer obligation changes and no Consumer right is narrowed.

Posted 2026-10-02 · Takes effect 2026-10-02

October 2, 2026 — Schedule A.1 and A.4(d) amended and new A.2(f). The Onboarding Package prices and Build Hours change to Launch US $500 with 2 Build Hours, Growth US $1,500 with 6, and Command US $2,500 with 10; Live Trainings and Access Windows are unchanged. New A.2(f) adds, for Growth and Command, a commitment to keep working on connecting your CRM and phone system, at no extra charge, past the package's Build Hours until they are connected, and states what that commitment covers and when it ends. Nothing else changes.

Posted 2026-09-26 · Takes effect 2026-09-26

September 26, 2026) added § 1.4, § 3A, § 3B, and Schedule A, and amended § 1.1, § 3.2 through § 3.6, § 3.8, § 9.2, § 11.1, and § 11.2: Quoted Work with a ceiling, fifteen-minute increments, statements charged no sooner than two business days after they are sent, the saved-card authorization, and the three Onboarding Packages.

Posted 2026-09-24 · Takes effect 2026-09-24

September 24, 2026 — § 1.2, § 5.3, § 5.4 and § 5.5. Registration can now be attributed through a referral link the registrant's browser remembered from a link opened in the previous thirty (30) days, as the Privacy Policy (§ 2.7) already tells registrants; § 1.2 and § 5.3 now say so, say which link wins, and say when Inscendo disregards a remembered link. § 5.4 now lists what a Partner actually sees about a Referred Customer, which is what the Privacy Policy (§ 4.7) tells the customer: more than the company name, and still no personal information. § 5.5 defines cookie-stuffing by what it does rather than by the storage technology used, and states that a registration attributed that way is not a Referred Customer. Nothing in this revision reduces commission or markup on any existing Referred Customer.

Posted 2026-09-23 · Takes effect 2026-09-23

September 23, 2026 — the telemetry paragraph now adds that telemetry copies held in routine backups are deleted within the backup-retention window stated in the Privacy Policy (§ 5). A disclosure only; the thirty-day telemetry period and the ninety-day backup ceiling are unchanged, and no Customer obligation changes. Effective on posting.

Posted 2026-09-23 · Takes effect 2026-09-23

September 23, 2026 — § 8.1(e) and § 12.2. § 8.1(e) now says that telemetry copies held in routine backups are deleted within the backup-retention window stated in the Privacy Policy (§ 5), and § 12.2 says that information Customer asks Inscendo to delete during the Subscription Term may persist in routine backups for no longer than that same window. Both point at the ninety-day ceiling Privacy Policy § 5 and § 12.1 already state; no retention period is lengthened, and no change to Sub-Processors, roles, data residency, or any Customer obligation.

Posted 2026-09-23 · Takes effect 2026-09-23

September 23, 2026 — § 2.2, § 2.7, § 2.11, § 4.7, § 5 and § 10.1. Adds a Backups entry to § 5 that says what our backups are and how long they last: our databases and files are copied into encrypted backups automatically, each copy is kept for no more than ninety (90) days from the date it is written and is then deleted, information removed from our live systems may remain in those copies until they expire, and we do not restore it to live use except to recover the Service after a failure. The telemetry entries in § 2.2 and § 5 now say that telemetry copies held in routine backups are deleted within that same window. A disclosure of how our backups already work; no retention period is lengthened, the ninety-day ceiling already stated in § 5 is unchanged, and no new use is made of any information. Separately, § 2.7, § 2.11 and new § 4.7 describe partner referral links: when you open a partner's referral link, your browser remembers that link's code, and nothing about you, for up to thirty (30) days so that a sign-up or a demo booking you make from that browser in that time is credited to the partner; the code is recorded with a demo booking and with any agreement you acknowledge on that form; and a partner who referred your organization sees your organization's name, when it registered, whether it is active, and whether it pays for Premium, and nothing else. § 10.1 records that disclosure. A disclosure of how partner referral already works; no new category of information about you is collected, and nothing is Sold or Shared.

Posted 2026-09-17 · Takes effect 2026-09-17

September 17, 2026 — § 1.9 adds two sentences: the third-party-rights review Customer already owes on generated code now expressly reaches the forms, formats, specifications, and data standards of industry standards bodies, forms publishers, and trade associations, and Customer's responsibility for that review does not change because Inscendo personnel or Inscendo as a publisher produced the code — matching MSA § 4.2A(e) and § 4.10. Takes effect with MSA Version 1.13, on October 17, 2026 for Customers already bound and on acceptance for new Customers.

Posted 2026-09-17 · Takes effect 2026-10-17

September 17, 2026 — new § 6.6, "Inscendo-Published Capsules", and one sentence added to § 1.3. Every clause of § 6 put a Capsule on *its Publisher*. Inscendo itself publishes Capsules from tenants it operates, and § 6.2 then made you a beneficiary of Inscendo's own § 4 warranties and § 9 indemnity under the Publisher Agreement — making Inscendo the vendor of the Capsules it publishes, which it is not. § 6.6 states that an Inscendo-Published Capsule is licensed to you AS-IS under MSA § 4.2A, conveys no third-party or industry licence, and is yours to operate under MSA § 4.10; the Publisher-side warranties, obligations, and indemnity do not run from Inscendo for it. § 1.3 now says in one sentence what MSA § 4.10 says in full: a Capsule in your tenant runs under your own licences and authority, whoever built or published it. Your rights against a third-party Publisher are unchanged. MSA § 4A.7 and Publisher Agreement § 1.6 state the same.

Posted 2026-09-17 · Takes effect 2026-10-17

September 17, 2026 — new § 1.6, "Inscendo-Published Capsules". § 1.5 allocated every Capsule to *its Publisher*, which is right — but Inscendo itself publishes Capsules from tenants it operates, and read literally this Agreement then made Inscendo, as Publisher, warrant under § 4 that it holds every licence a Capsule needs and indemnify installers under § 9 without cap. That converts a platform operator into a software vendor for exactly the Capsules it publishes. § 1.6 states that for an Inscendo-Published Capsule the § 4 warranties, the § 7 end-installer obligations, and the § 9 indemnity do not run from Inscendo, the Capsule is licensed AS-IS under MSA § 4.2A, and the installer operates it under MSA § 4.10. No obligation of any third-party Publisher changes, and no right an installer holds against a third-party Publisher changes. MSA § 4A.7 and Marketplace Installer Terms § 6.6 state the same.

Posted 2026-09-17 · Takes effect 2026-10-17

September 17, 2026 — every allocation of responsibility for capsule code in this Agreement was written around code built "with Inscendo IQ at Customer's or a publisher's direction". None of it addressed code that Inscendo itself wrote (an Inscendo IQ Expert building in Customer's tenant) or itself published (a Marketplace Capsule from a tenant Inscendo operates), and nothing addressed a capsule that generates or issues a form, format, or content licensed by an industry standards body — a licence the Customer may hold and Inscendo does not. This version closes those three gaps, in one direction only: **the Customer operates every artifact in its tenant, under its own authority and licences, whoever built it, and Inscendo is never the vendor of it.** § 4.10 states that rule in full. § 4.2A(a) now says Platform Code is licensed AS-IS, and new § 4.2A(e) says the licence conveys no third-party or industry licence and that Customer represents it holds any such licence its capsules require. New § 4A.7 defines an **Inscendo-Published Capsule** and states that the Publisher warranties and indemnity, and the installer's third-party-beneficiary rights, do not run from Inscendo for one; the Marketplace Publisher Agreement § 1.6 and Marketplace Installer Terms § 6.6 say the same. § 11.2 now names Platform Code, Customer Configurations and every artifact in Customer's tenant, however and by whomever authored. § 12.2(a) now reaches artifacts regardless of who authored, built or published them, and new § 12.2(k) reaches claims that a capsule used licensed forms or standards without the required licence. § 2.4 and new § 3.3(g) state that Inscendo is not a member or licensee of any standards body or forms publisher. § 14.5 adds § 4.2A and § 4.10 to survival. § 20.7 no longer contradicts § 4A.

Posted 2026-09-17 · Takes effect 2026-09-17

September 17, 2026 — § 6. Adds one optional item to what we publish: at the researcher's request, a link to their public profile on a well-known professional or security-research platform (personal websites and other addresses are not linked). The link is theirs, not ours; it is published only because they asked, it does not alter the non-endorsement statement introduced in version 1.3, and we may decline or remove a link that no longer resolves or that points at anything other than a personal profile. Adds no obligation on any researcher and publishes nothing without their request.

Posted 2026-09-16 · Takes effect 2026-09-16

September 16, 2026 — § 2.2 and § 5. Discloses the authentication-event records we keep to detect credential abuse: for each sign-in, sign-up, verification and password event we retain a one-way hash of the email address, a one-way hash of the network address, the browser and device characteristics, the outcome and the time — never a password, code or token — for up to ninety (90) days, longer than the thirty (30) days that applies to the rest of our operational telemetry. Adds a disclosure of something we now do; changes no other retention period and grants us no new use.

Posted 2026-09-16 · Takes effect 2026-09-16

September 16, 2026 — § 6. States what a listing on the acknowledgements page is and is not: an acknowledgement of a report we received and fixed, from an independent third party who is not affiliated with, employed by, or endorsed by Inscendo, and not a recommendation of their services. Adds no obligation on any researcher and narrows nothing we promised; it prevents the page being read as a partner or vendor list.

Posted 2026-09-07 · Takes effect 2026-09-07

September 7, 2026 — § 5.3 and § 5.3A(b) amended to state the one case in which a Capsule payment is refunded by Inscendo. A referral signup now collects every payment before a workspace is created; if that registration expires before every payment is collected, no workspace or Capsule installation is ever created, and the Capsule payment is cancelled and refunded on the Publisher's account on the Publisher's behalf. A disclosure in the Installer's favour; no Installer obligation is enlarged.

Posted 2026-09-07 · Takes effect 2026-09-07

September 7, 2026 — § 6.5 and § 6.7(d) amended to state the **one** refund Inscendo initiates. The Service now collects every payment in a referral signup sequence before a tenant is created; where such a registration expires before every payment has been collected, no tenant and no installation of Publisher's Capsule ever existed, and Inscendo cancels the subscription and refunds the payment on Publisher's connected account on Publisher's behalf. § 6.7(d) authorises that, and § 6.5 now carves it out of the general rule. Nothing else moves: Publisher remains merchant of record, Inscendo still never holds the funds, and no other refund, chargeback, or dispute becomes Inscendo's.

Posted 2026-09-07 · Takes effect 2026-09-07

September 7, 2026 — § 4A.4 amended. A referral signup now collects every payment before a tenant is created; if the registration expires before every payment is collected, the Marketplace Capsule payment for a Capsule that was never installed is cancelled and refunded on the publisher's account on the publisher's behalf, the one refund Inscendo initiates (Marketplace Installer Terms § 5.3). No fee, plan, or Customer obligation changes.

Posted 2026-09-02 · Takes effect 2026-09-02

September 2, 2026 — § 1.1 adds one sentence: where Customer connects a third-party AI application to the Service under Customer's own account (MSA § 4.9), the model, content policies, and data-handling terms behind that application are those of the provider Customer chose, and § 2.14 applies to that provider's requirements as well. No other change. Version 1.1: initial published text

Posted 2026-09-02 · Takes effect 2026-09-02

September 2, 2026 — § 4.3 and the customer-configured-provider paragraph of § 6.2 now cover a third-party AI application that Customer connects to the Service under Customer's own account (MSA § 4.9): Customer Personal Information that application requests is transmitted to it at Customer's direction and is thereafter processed under Customer's own agreement with that application's provider, which Customer selects; it is not an Inscendo Sub-Processor and Inscendo's foundation-model agreement in § 4.3 does not govern it. No change to the Sub-Processor table, to roles, to data residency (§ 11), or to any Customer obligation beyond those an optional connection carries. Version 1.4, August 29, 2026 — Backblaze, Inc. added to the § 6.2 Sub-Processor table as off-site immutable backup storage, United States, posted before any Customer Data is stored with it (§ 6.3); new § 8.1(j) discloses that restoration from a backup after a failure may not recover data written after the most recent recovery point and commits Inscendo to notify affected Customers of the recovery point used; § 12.1 now states that any off-site immutable backup copy is retained for a fixed period not exceeding ninety (90) days and cannot be deleted earlier by anyone, including Inscendo, so the Privacy Policy § 5 backup-retention ceiling is confirmed rather than changed. No recovery-time or recovery-point objective is promised. No change to roles, data residency (§ 11, United States only), or any Customer obligation. Version 1.3, August 6, 2026 — Cloudflare and GoDaddy sub-processor entries describe the domains generically rather than naming one; no change to the sub-processor list, its roles, or data residency

Posted 2026-09-02 · Takes effect 2026-09-02

September 2, 2026 — § 3.1 and § 4.5 describe a disclosure your organization can now direct: an account administrator may connect a third-party AI application (for example, a Claude application) to the organization's account under the organization's own subscription with that application's provider, and the information that application requests is then sent to it at your organization's direction. § 3.1 states that our no-training commitment and our provider's commercial-tier agreement with us do not cover information sent to an application your organization connects that way; § 10.1 records the disclosure. No change to what we collect, how we use it, or how long we keep it. Version 1.7, August 29, 2026: § 4.1 adds Backblaze (off-site immutable backup storage, United States) to the Sub-Processor summary, posted before any customer data is stored with it; § 5 states that the ninety-day backup-retention window is a ceiling: any off-site backup copy we keep is written once, kept for a fixed period of no more than ninety (90) days, and cannot be deleted earlier by anyone, including us. No change to what we collect, how we use it, or how long we keep it; the retention window is confirmed, not extended. Version 1.6, August 23, 2026: § 2.11 adds an express statement that SMS consent is not shared with third parties, with a service-provider carve-out; § 2.1 scopes its no-marketing sentence to the account mobile number and cross-references § 2.11; § 10.1 conformed to § 2.11. No change to what we collect, how we use it, how long we keep it, or who it is disclosed to. Version 1.5, August 18, 2026: discloses SMS opt-in status and the phone number it attaches to: new § 2.11 paragraph with a stable anchor, § 5's surviving-record parenthetical now names the consented number and message category, and § 10.1 and § 10.5 updated so the Notice at Collection stays accurate. Version 1.4, August 9, 2026: scope bullet and § 1 describe Inscendo's operating domains generically rather than naming one; the Policy's coverage is unchanged and still reaches every Inscendo-operated site. Version 1.3, August 6, 2026: describes the information we collect from people who contact us, book a demo or consultation, or apply to our partner program without holding an account, and how long we keep it; new § 2.11, new § 3(h), § 5, § 10.1 and § 10.5 updated. Version 1.2, August 4, 2026: registration now offers an optional mobile number, and passkey sign-in is available; § 2.1, § 2.10, § 5 and § 10.1 updated to describe both accurately

Posted 2026-09-02 · Takes effect 2026-09-02

September 2, 2026 — § 4.9 added and one sentence added to § 4.4. The Service now lets an account administrator connect a third-party AI application that Customer uses under Customer's own account with that application's provider, so that it can act as Inscendo IQ on Customer's tenant. § 4.9 states what that connection does: Customer Data, Customer Configurations, and AI Output the connected application requests are transmitted to it at Customer's direction; once received, that data is processed under Customer's own agreement and settings with that provider, not under Inscendo's agreement with its AI model provider; and the § 4.4 no-training requirement, DPA § 4.3, and the other protections that apply to data sent through Inscendo's commercial API tier do not reach it. § 4.4 now says the same in one sentence. A disclosure of an optional feature only; no fee, plan, or obligation changes for a Customer that does not connect an application.

Posted 2026-08-29 · Takes effect 2026-08-29

August 29, 2026 — § 11.5 added: Inscendo keeps encrypted backup copies of Customer Data and Customer Configurations, which may include an off-site immutable copy held with a Sub-Processor disclosed in DPA § 6.2; restoration from a backup after a failure returns the Service to the most recent recovery point available and Customer Data written after that point may not be recovered; Inscendo will notify Customer without undue delay of the recovery point used. A disclosure and a new Inscendo notice obligation only — no recovery-time or recovery-point objective is promised, no Customer obligation is enlarged, and § 11.2 and § 13 are unchanged.

Posted 2026-08-29 · Takes effect 2026-08-29

August 29, 2026 — § 3(e) and § 6. The trust page told researchers Inscendo would "request that prosecutors do the same", and the Policy — the binding instrument — said no such thing. New § 3(e) states it: where a third party brings a claim, or a criminal referral or prosecution arises, from activity we determined was authorized, we take reasonable steps to make the authorization known and ask the prosecuting authority to do likewise. § 6 was a single sentence promising a hall of fame; it now states that consent comes first and silence means no listing, exactly what an entry shows (chosen name, date RESOLVED, severity band, general category), and what it deliberately withholds (endpoint, component, reproduction) with the reason — a category says what you did, a location tells the next attacker where to look. Technical detail goes to a § 7.8 advisory after the fix, linked from the entry. Adds an Inscendo obligation and narrows what we publish about a researcher; no researcher obligation is enlarged.

Posted 2026-08-29 · Takes effect 2026-08-29

August 29, 2026 — § 10 restated. It reproduced the contents of our `security.txt` and carried unresolved drafting placeholders in its Expires and Hiring lines, both of which were published. The stated expiry was also wrong: the file is served with a shorter expiry than twelve months, and `Hiring` is not published at all. § 10 now describes what the file contains rather than restating its field values, and names the file as authoritative where the two disagree, so the Policy cannot drift from it again. No change to scope, safe harbor, authorized conduct, reporting address, disclosure timelines, or any commitment made to a researcher.

Posted 2026-08-25 · Takes effect 2026-08-25

August 25, 2026 — new § 3.11, covering every feature that charges a Consumer more than once: the monthly Premium subscription and automatic Wallet top-up. It states that nothing recurring is on by default, what the Consumer is told before consenting and where, the retainable receipt that acknowledges each charge and carries the renewal terms, that cancelling is available in the same place and by email, a 7-to-30-day notice before any price change, and that the annual reminder California law requires for annual plans does not reach a monthly one but will be sent if Inscendo ever offers an annual plan. § 3.11(h) additionally covers a recurring fee charged by a **Marketplace Capsule publisher** rather than by Inscendo: what Inscendo does (disclose the recurring terms before purchase, provide the uninstall cancellation, which is immediate), what the publisher owes under Publisher Agreement § 6.7, and that describing the split waives nothing against the seller. Adds Consumer-facing obligations on Inscendo only; no Consumer obligation is enlarged and no right is waived.

Posted 2026-08-25 · Takes effect 2026-08-25

August 25, 2026 — new § 5.3A, and § 5.4 restated. The Installer Terms described a paid Capsule and named the Publisher as merchant of record, but never said that a monthly Capsule **renews automatically until cancelled**, never said how to cancel it, and left the cancellation mechanism as "uninstalling ... **may** cancel the associated subscription" — which is the one sentence an installer needs to be able to rely on. § 5.3A states the recurring charge and that it continues until stopped, that uninstalling in the Service is the cancellation and needs no contact with anyone, that cancellation takes effect **immediately** and forfeits the remainder of the paid month subject to the Publisher's refund policy, that the price cannot rise while installed (Publisher Agreement § 6.1A), that receipts come from the Publisher as merchant of record (Publisher Agreement § 6.7), and what Inscendo does and does not do in the transaction. § 5.4 now states the cancellation as a fact rather than a possibility. Adds disclosure and an Inscendo-side commitment; no Installer obligation is enlarged.

Posted 2026-08-25 · Takes effect 2026-08-25

August 25, 2026 — new § 6.7. § 6.1 let Publisher set recurring fees and § 6.2 made Publisher the merchant of record, but nothing said what being the merchant of record for an *automatically renewing* charge actually requires. § 6.7 states it: a receipt after every charge including each renewal, carrying cancellation instructions, as the payment-card networks' subscription standards require of the merchant of record; keeping receipt emails enabled on the connected account, since a direct charge is receipted from **Publisher's** Stripe settings, which Inscendo does not control and cannot see; compliance with automatic-renewal and negative-option law as the seller; honouring an installer's uninstall-cancellation immediately with no re-billing, retention step, or required contact; no indirect price increase around § 6.1A; responsibility for a refund policy that addresses mid-period cancellation, since uninstalling cancels immediately; and an indemnity for Publisher's own recurring-billing conduct. Allocates to Publisher obligations that already attach to it as merchant of record; it does not move any obligation from Publisher to Inscendo, or create a new fee.

Posted 2026-08-25 · Takes effect 2026-08-25

August 25, 2026 — §§ 6.8, 6.9 and 6.10 added, and § 6.5 restated. Section 6 described a prepaid Wallet funded by discrete purchases and did not describe either recurring charge the Service actually makes: automatic Wallet top-up against a stored card, and the automatically renewing Premium subscription. § 6.8 states the auto top-up authorization, that it continues until Customer turns it off, and how to turn it off. § 6.9 states that a subscription renews automatically until cancelled, the cancellation method and its effect, and the treatment of a price change. § 6.10 is a new **Inscendo obligation**: an itemized receipt by email for every charge, and for a recurring charge a statement that it recurs and how to stop it. § 6.5's thirty-day dispute window now runs from that receipt rather than from the charge, and expressly does not limit Customer's rights under law or card-issuer rules. § 6.9 and § 6.10 are additionally scoped to say what they do NOT cover: a Marketplace Capsule subscription is sold by its publisher as merchant of record, renews and cancels under Marketplace Installer Terms § 5.3A, and is receipted by that publisher rather than by Inscendo. No fee, price, or plan changes, and no Customer obligation is enlarged.

Posted 2026-08-14 · Takes effect 2026-08-14

August 14, 2026 — new § 3.0: a Consumer is never asked to indemnify Inscendo for a loss Inscendo's own negligence caused, and the express-negligence provisions added to MSA § 12.2 for business Customers do not apply to Consumer Accounts. Narrowing only; no Consumer obligation is enlarged.

Posted 2026-08-14 · Takes effect 2026-08-14

August 14, 2026 — § 2.3(a) now states that an installed free Capsule License also survives termination of the Publisher Agreement, matching Publisher Agreement § 5.2, which is named as the controlling statement; Inscendo's deactivation power is referenced rather than left implicit. § 5.2 feedback license split into Feedback, identified customization signals, and aggregated learning, mirroring Publisher Agreement § 5.6 — unrestricted cross-product use now reaches only the aggregated, de-identified form governed by MSA § 4.5.

Posted 2026-08-14 · Takes effect 2026-08-14

August 14, 2026 — § 9.1, § 9.2 and § 9.3 added to satisfy Texas fair-notice law, on the same basis as MSA § 12.2A–C: the § 9 indemnity now states **expressly and conspicuously** that it reaches a claim alleging Inscendo's own negligence contributed, and carves out Inscendo's **sole** negligence, gross negligence, willful misconduct, fraud and unlawful conduct, with a proportionate reduction for Inscendo's allocated fault. No new category of claim was added to § 9(a)–(f).

Posted 2026-08-14 · Takes effect 2026-08-14

August 14, 2026) — § 5.10 "Independent development; no functional exclusivity" and § 5.11 "Inscendo will not intentionally clone a Capsule" added, and § 5.3(b) bounded to match: publication confers an exclusive **listing** right, never exclusivity over an industry, market, use case, workflow, feature, or capability, and similarity alone does not establish copying. § 5.6 Tribal Knowledge split into Feedback, identified customization signals, and aggregated learning — unrestricted cross-product use now reaches only the aggregated, de-identified form already governed by MSA § 4.5. § 5.2 made the single controlling statement of Capsule License survival, with Inscendo's deactivation power enumerated rather than discretionary; § 8.3 and § 11.2 restated to defer to it. § 5.12 added: Publisher bears its own investment risk, with the § 6.1A price lock, the § 5.3(b) listing right, and § 5.2 survival expressly preserved. § 6.4 no longer self-certifies Inscendo's status under any marketplace-facilitator tax statute. § 5.1 limited to its stated purposes.

Posted 2026-08-14 · Takes effect 2026-08-14

August 14, 2026 — § 12.2A, § 12.2B and § 12.2C added to satisfy Texas fair-notice law. The § 12.2 indemnity now says **expressly and conspicuously** that it reaches a claim alleging Inscendo's own negligence contributed to the loss — without which, under the Texas express-negligence doctrine (*Ethyl Corp. v. Daniel Constr. Co.*) and the conspicuousness requirement (*Dresser Indus. v. Page Petroleum*), it likely reached no such claim at all. § 12.2B carves out Inscendo's **sole** negligence, gross negligence, willful misconduct, fraud and unlawful conduct, and reduces the obligation in proportion to Inscendo's allocated fault. § 12.2C excludes Consumer Accounts entirely. Net effect is narrower in substance and enforceable in form.

Posted 2026-08-14 · Takes effect 2026-08-14

August 14, 2026) — § 16.3A added: an express delegation clause giving the arbitrator authority over questions of arbitrability, reserving to a court the enforceability of the § 16.5 class waiver and the § 16.6 Coordinated-Filing Procedure, and whether a claim falls within a § 16.7 carve-out. § 16.11 added: a conspicuous **waiver of jury trial** that reaches every claim heard in court rather than arbitration — including claims under a § 16.7 carve-out, claims severed under § 16.5 or § 16.6(h), and any claim as to which § 16 is held unenforceable — and that survives independently of the agreement to arbitrate; it does not apply where a pre-dispute jury waiver is unenforceable, or to a Consumer Account beyond what the Consumer Account Addendum permits. § 19.2 restated around a designated **Legal Notice Email**, and § 19.4 and § 19.5 added: Customer must keep contact information current and monitored, consents to electronic delivery of contractual and legal notices, and bears a notice that fails on an address Customer let go stale — with Inscendo committing to alert account administrators in-product when it knows the address is undeliverable. No change to the scope of arbitration, the § 13 liability caps, or any fee.

Posted 2026-08-13 · Takes effect 2026-08-13

August 13, 2026) — § 4A.2 restated and § 4A.6 added: a Marketplace Capsule built with Inscendo IQ at its publisher's direction remains that publisher's product and responsibility; Inscendo's ownership of Platform Code under § 4.2 is an allocation of rights rather than an assumption of responsibility for any Capsule; and Marketplace screening is best-effort only.

Posted 2026-08-13 · Takes effect 2026-08-13

August 13, 2026, in force): new § 9A "SMS/Text Messaging Terms," effective on publication: message categories, sending hours, consent and electronic signature, opt-out and revocation, consent-record retention, and related SMS program disclosures; § 9A adds no obligation to any Customer who does not opt in to text messages.

Posted 2026-08-09 · Takes effect 2026-08-09

August 9, 2026): operating-addresses line, § 19.3 and § 22.1 restated to describe Inscendo's operating domains generically rather than naming one; no change to any right, obligation, or the scope of the disclaimer. Version 1.3, also effective September 8, 2026: § 3.2(f) resale carve-out now names the **Partner Program Agreement**, published with that version; previously it referenced an unpublished "reseller program"

Posted 2026-08-06 · Takes effect 2026-08-06

August 6, 2026 — extended beyond Expert Services to every relationship in which non-public information is exchanged, including partners, distributors, resellers, referral partners and marketplace publishers; the covered purpose, the carve-outs in § 5, survival and the entire-agreement clause were widened to match, and § 5.9 was added

Posted 2026-08-06 · Takes effect 2026-08-06

August 6, 2026 — §§ 2 and 3 restated so the notice describes every domain Inscendo operates rather than naming one; no change to the scope of the disclaimer