Inscendo: Privacy Policy

Effective Date: October 14, 2026 Version: 1.16 (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.) Version 1.15 (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.) Version 1.14 (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.) Version 1.13 (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.) Version 1.12 (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.) Version 1.11 (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.) Version 1.10 (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.) Version 1.9 (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.) Version 1.8 (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)

This Privacy Policy describes how Inscendo Automation Inc. ("Inscendo," "we," "us") collects, uses, and discloses personal information in connection with the Inscendo service (the "Service"). The Service is offered exclusively to U.S.-based businesses and is not directed to users outside the United States.

This Privacy Policy applies to:

• visitors of any Inscendo-operated marketing or product website, including any alternate front-door domain that routes to the Service, including people who contact us, request a demo or a consultation, or apply to our partner program without holding an account (§ 2.11);
• account holders and authorized users of the Service ("Subscribers" or "Customers"); and
• individuals whose information Subscribers submit to the Service in their own capacity as data controllers (covered separately in § 12 below: for those individuals, the Subscriber's privacy notice, not this Policy, is the controlling document).

If you are an end-user of a service or application built by a Subscriber on top of the Service, this Policy does not govern your relationship with that Subscriber. Please refer to that Subscriber's own privacy notice.

---

1. Trademark and Domain Notice

Each domain Inscendo operates is used solely as a network-infrastructure address on which the Service is hosted. The product offered through the Service is branded Inscendo. Inscendo is not affiliated with, sponsored by, or endorsed by any other company that may use a similar name. See the Trademark Notice at https://inscendoiq.com/legal/trademark.

2. Information We Collect

2.1 Account information

When you or your organization registers for the Service, we collect: name, business email, billing address, payment method (handled by Stripe, we receive a tokenized reference, not full card data), tenant/organization name, role, password (hashed), and any optional profile data you provide.

Mobile number (optional). Registration offers a mobile number field, and you can add, change, or remove a number later in your account settings. Providing it is optional and you can complete registration and use the Service without it. Where you enter one, we ask for your consent to receive account security messages at it and keep a record of that consent (§ 5). We store the number and, when you verify it, a one-time verification code in hashed form together with the time it was sent, the time it was verified, and a record of the send for rate-limiting and abuse-prevention purposes (which includes the number, the purpose of the message, a hashed form of the requesting IP address, and when the code was used). When you change a verified number, the new number is held beside it, unused, until you verify it. We use a mobile number you provide to verify that the number is yours and to send you the one-time sign-in, verification, and password-reset codes you ask for, by text message or, when you ask for one, by an automated call that reads the code aloud. If you are the account owner of an organization that starts a paid subscription, we also keep the number in our own customer record of that subscription (§ 4.8), and a member of our team may call you at it about setting up and using that subscription; you can ask us at any time not to call you at it. We use it for nothing else. To deliver a code, we give our code-delivery provider (§ 4.1) the number, the code, and whether to text or call, and, once you enter the code, the fact that it was used; the provider delivers codes on our behalf and for no other purpose. If you reset your password using a texted code, we record when, and sign-in by texted code is paused on your account for a period afterwards as a protection against account takeover; your other sign-in methods keep working. We do not use this account mobile number for marketing, by text message or by call, and we do not sell or share it. We send it no text message other than the codes you ask for, unless you separately agree to receive our text messages through a form (§ 2.11; Terms of Service § 9A). Marketing text messages are sent only where you have separately opted in through a form (§ 2.11). You may remove it from your account at any time.

Passkeys. If you choose to create a passkey, the credential itself is generated and held on your own device. What we receive and store is the public half of that credential and the material needed to verify it: a credential identifier, the public key, a user handle, a signature counter, an authenticator model identifier, transport hints, whether the credential is backed up by your device platform, an optional label you set, and timestamps of creation and last use. We also keep a durable record of when a passkey was added or removed from your account, which survives deletion of the credential itself so the account's security history remains auditable. We never receive your fingerprint, face scan, device PIN, or any other biometric or knowledge factor — those stay on your device and are used by the device to unlock the credential locally. See § 2.10.

2.2 Service-usage information

We process activity associated with your account in two ways, with different retention.

• Operational and diagnostic telemetry, timestamps, IP address, browser and device characteristics, tool-invocation metadata, and security-relevant events, is retained on a rolling basis for up to thirty (30) days, except where extended retention is required for security investigation or legal hold. We apply automated secret-redaction to this telemetry. Copies held in routine backups are deleted within the backup-retention window stated in § 5.
• Authentication-event records. For each sign-in, sign-up, verification and password event we keep 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. For a sign-up, these events include each step of our sign-up page that you reach, including opening the form and a submission that the page or the Service refused, and the record also notes the reason it was refused (for example, which required item was missing), the partner referral code it was made with (§ 2.7), if any, and which sign-up form was used. When the sign-up page itself reports a step, it never sends the email address you typed: at most it sends a one-way hash of that address, computed in your browser. We use these records to detect credential abuse across sessions, and to find out why a sign-up or sign-in did not complete when you or your organization asks us for help. These records never contain a password, a one-time code, a token, your name, your company name or your phone number, and are retained for up to ninety (90) days, except where extended retention is required for security investigation or legal hold.
• Your conversation history and agent session records, including the AI prompts you submit, the AI Outputs returned, the inputs and outputs of tool calls, the configurations you create (capsules, widgets, automations, skills), and web-page content the Browser Companion observes during a session, are stored as part of your tenant so the Service functions and you can review past activity. These records are retained for as long as your account is active and are deleted in accordance with the retention schedule in § 5, not on the thirty-day telemetry schedule.

Important: what these records contain and how we redact. Your conversation history and session records include the literal text of your prompts, the AI's responses, the inputs we send to and the outputs we receive from tool calls, and any web-page content the Browser Companion observes. We apply automated secret-redaction to strip credentials we can recognize (API keys, bearer tokens, database connection-string passwords). We do NOT apply automated redaction of other personal information. Names, email addresses, phone numbers, postal addresses, government identifiers, financial account numbers, free-text health information, and any other personal information present in your prompts or in pages the Companion observes will be stored in these records and may be accessible to authorized Inscendo personnel for security, debugging, and abuse-investigation purposes. If you process information about your own customers, employees, or end-users through the Service, you should not place sensitive personal information about those individuals in agent inputs unless you have accepted this retention and have a lawful basis for that processing under your own privacy notice.

2.3 Customer Configurations

The capsules, widgets, automations, skills, and code you build on the Service are stored in your tenant. We may access them as needed to operate the Service, support you, investigate AUP violations, or comply with law.

2.4 Browser Companion data

If you install the optional Inscendo Browser Companion Chrome extension, while it is attached to a tab we receive: the URL of the active tab, a snapshot of the tab's contents, screenshots, console-log messages, network-request metadata and bodies, and the results of JavaScript the agent evaluates. The extension's sensitive-field sensor automatically detaches the agent when password and payment-card fields are detected; this is a heuristic and is not a guarantee. The sensor detects standard password, one-time-code, and payment-card fields. Custom-built, non-standard, or programmatically-rendered input fields may NOT be detected. The Companion may attach to, observe, and transmit data from a page that contains your credentials, one-time codes, payment-card data, or other sensitive information before the sensor triggers, or if the sensor fails to recognize the field type. You should not rely on the sensor as a guarantee that sensitive data will be excluded from what is sent to Inscendo and to the AI model provider. Browser Companion data is transmitted to our servers and to our AI model provider for processing as part of providing the Service. See the Browser Companion Consent EULA for details.

Saved logins. A user may choose to save a username and password (and similar sign-in values) for a third-party website, so that the Browser Companion can sign in to that website for them. Saving a login is optional and is done by the user. The values are stored encrypted in the user's organization's own workspace vault, together with a label, the website addresses the login may be used on, and the names of its fields. When the user asks Inscendo IQ to sign in to one of those websites, the Browser Companion fetches the values directly from our servers and types them into the page; Inscendo IQ sees only the label and field names, never the values, and the values are not sent to our AI model provider. While the values are being typed, the Companion is not observing the page for Inscendo IQ. A saved login is used only on the website addresses it was saved for.

2.5 Communications data

Where you configure outbound communications (SMS, email, voice, or chat) through providers you connect, we transmit message content and recipient identifiers through those providers on your behalf. The providers handle the underlying telecom delivery; we do not store message bodies beyond what is required to operate the Service and to honor your retention configuration.

2.6 Inferred and derived data

We generate inferred and derived data about Service usage, including embeddings, similarity scores, billing and usage metrics, and aggregated analytics.

2.7 Cookies and similar technologies

We use cookies and similar technologies for: authentication, security, fraud prevention, load balancing, preference storage, crediting the partner who referred you, and analytics. We use the analytics providers listed in our Sub-Processor List. Our website and the Service load typefaces from Google Fonts; when a page does, your browser requests them from Google, which receives your IP address, your browser's characteristics and the address of our website, but no information about your account or your content. We do not "sell" or "share" personal information for cross-context behavioral advertising (see § 3.1 and § 10.2); because there is no sale or sharing to opt out of, no action is required to give effect to a Global Privacy Control (GPC) or similar browser opt-out signal, and we do not currently process such signals automatically. We do not display a GDPR-style consent banner because the Service is not directed to EEA / UK / CH residents.

Partner referral links. If you open a partner's referral link, your browser stores the code of that link and the time you opened it, using browser storage on our website. It stores nothing about you. For thirty (30) days, a sign-up or a demo booking you make from that browser, including after you have browsed elsewhere on our website, is credited to that partner (§ 2.11, § 4.7). Opening a different partner's link replaces it. It is cleared when you sign up with it or when we find at sign-up that the link is no longer valid, it is not used after thirty days, and you can clear it at any time by clearing your browser's stored data for our website.

Demo booking details. When you book a demo or consultation on our website, your browser keeps the name, work email address, company name and phone number you entered, and none of your other answers, using browser storage on our website, so that our sign-up form can open with them filled in. They stay in your browser and are not sent to us unless you submit the sign-up form yourself. Our sign-up form uses them only within twenty-four (24) hours of your booking, and removes them from your browser when you sign up, when you clear them on that form, or when it finds them older than that. You can also remove them at once with the "Don't keep them" link shown after you book, or by clearing your browser's stored data for our website.

2.8 Information from third parties

We may receive limited information from third parties: payment processors (Stripe, payment confirmation, dispute notices), authentication providers (where you sign in via OAuth), enterprise integrations you authorize, threat-intelligence and fraud-prevention vendors, and our AI model provider's safety-monitoring systems.

2.9 Billing and usage data

When you fund your account, we collect and retain: wallet purchase history, transaction amounts and dates, tokenized payment-method references received from Stripe (we do not receive or store full card data), refund and chargeback records, and per-tenant aggregate token-consumption metrics organized by date and by AI model. Billing data is retained for the period required by U.S. tax, accounting, and recordkeeping law (typically seven years) and is not subject to the rolling thirty-day log retention described in § 2.2.

2.10 What we do not knowingly collect

• Personal information of any individual under 18.
• Personal data of any individual located in the European Economic Area, the United Kingdom, Switzerland, China, Russia, Brazil, or any jurisdiction whose data-protection law would impose extraterritorial obligations on us.
• Protected Health Information regulated under HIPAA (we do not currently offer a BAA).
• Cardholder Data subject to PCI-DSS (Stripe handles card data; we receive tokens).
• Biometric identifiers regulated under BIPA, CUBI, or analogous law. This remains true where you sign in with a passkey. A passkey is unlocked on your own device by whatever method that device uses, which may be a fingerprint or face scan. That check happens entirely on the device and its result is not transmitted to us. We receive only a public key and the non-biometric metadata listed in § 2.1, from which no biometric identifier can be derived.
• Sensitive Personal Information as defined under applicable U.S. state privacy law.

If we become aware that we have inadvertently collected information of any of these categories, we will delete it as soon as reasonably practicable.

2.11 Enquiry, consultation, demo, and partner intake information

This section describes information you give us before, or without ever, holding an account: when you use a contact form on our website, request a product demonstration, book an Inscendo IQ Expert consultation, or complete a partner or distributor intake form.

What we collect. Your name, work email address, company, and role; a phone number if you choose to give one; what you tell us about your business, the systems you use today, and what you are trying to solve; your answers to any structured questions the form asks; which meeting you booked and when; and the identifier in a personalized link you followed, where the form was sent to you individually, so we can attach your answers to the right conversation; and, if you arrived through a partner's referral link (§ 2.7), that link's code, which we record with your booking and with any agreement you acknowledge on the form, so the partner who introduced you can be credited.

Records of agreements you accept. Where a form asks you to acknowledge an agreement, such as our Mutual Confidentiality and Non-Disclosure Agreement, we record that you acknowledged it, the version and effective date of the document, a cryptographic fingerprint of the exact text that was displayed to you, and the time of your acknowledgment. We keep the fingerprint so that we can later show what you were shown, not merely that you agreed.

Why we collect it. To respond to what you asked, to prepare for and hold the meeting you booked, to keep a record of the conversation, and to evaluate a potential partnership (§ 3(h)).

Where it is held. In our own systems, including a workspace we operate for ourselves on the Service, which is how we run our own sales and partner pipeline. We disclose it to the Sub-Processors listed in our Sub-Processor List who help us operate those systems and to the providers that carry our team's email, calls and meetings (§ 4.1), and to nobody else. We do not Sell or Share it (§ 3.1, § 10.2).

SMS opt-in status. Where a form includes SMS consent checkboxes, we also record which category or categories of text messages you consented to receive and when. SMS consent is not shared with third parties. We do not sell, rent, or share your SMS opt-in status or the phone number you provided for SMS with any third party or affiliate for that party's own purposes, including marketing or SMS/text marketing purposes. The only recipients are the service providers that transmit or process these messages on our behalf, under contracts limiting them to that purpose (§ 4.1). This SMS opt-in status, and the phone number associated with it, are used only to operate our SMS program as described in the Terms of Service. The categories, the messages each one covers, and how to stop them are set out in § 9A of the Terms of Service at https://inscendoiq.com/legal/terms#sms-terms.

Marketing is separate. Any invitation to receive occasional updates from us is a separate, unticked choice. Declining it has no effect on whether we respond to you, prepare for your meeting, or consider your partnership application.

Please do not send us sensitive information. These forms ask only the questions above. Do not include government identification numbers, dates of birth, health information, payment card or bank details, credentials, or information about protected characteristics, in a form, a message, or a screen share. See § 2.10 and, for consultations, the Mutual NDA at https://inscendoiq.com/legal/mutual-nda.

How long we keep it. See § 5.

3. How We Use Information

We use information for:

(a) Service operation: providing, maintaining, supporting, securing, and billing the Service; processing your prompts and tool calls; transmitting outbound communications you authorize; routing data to and from third-party integrations you configure;

(b) Service improvement: analyzing aggregated, de-identified usage to improve features, performance, and reliability;

(c) Security and abuse prevention: detecting and investigating suspected violations of the Acceptable Use Policy or AI Code of Conduct, fraud prevention, and incident response. This may include automated log analysis and limited human review of logs;

(d) Communications: sending account, transactional, and Service notifications, and (with separate consent) marketing communications;

(e) Compliance and legal: complying with applicable law, responding to lawful requests from authorities, enforcing our agreements, and exercising or defending legal claims;

(f) AI provider operation: transmitting prompts, configurations, and Browser Companion data to our AI model provider under that provider's commercial terms, and, from November 12, 2026, sending text to our AI decision-model provider, through its AI gateway, so that it can classify, rank, score, or screen that text (§ 3.1, § 4.1);

(g) Aggregate analytics: creating aggregated, anonymized, or de-identified data, which we may use, retain, and share for any lawful purpose (including benchmarking and research). Such data is not reasonably linkable to you.

(h) Enquiries, demonstrations, consultations, and partner discussions: responding to what you ask us; preparing for, holding, and following up on a meeting you booked; keeping a record of that conversation; evaluating a potential partner or distributor relationship; and retaining proof of any agreement you acknowledged in the course of it (§ 2.11).

3.1 What we will not do

• We will not Sell or Share (in the CCPA sense, including for cross-context behavioral advertising) your personal information.
• We will not use Customer Data, prompts, or AI Output to train, fine-tune, or evaluate generalized or "foundation" AI models. We do not offer an in-product "training" setting because such training does not occur; if we ever introduce a program that uses your data to improve AI models, it will be optional and presented to you separately for your express agreement. Our AI model provider's commercial-tier agreement with us prohibits training on data sent through our API. That commitment and that agreement cover information we send to our provider. They do not cover information that a third-party AI application your organization connects to the Service under its own subscription with that application's provider (§ 4.5) receives at your organization's direction: whether that provider keeps that information or uses it to train models is governed by your organization's own terms and settings with that provider. From November 12, 2026, text from our typed-decision features is also sent to our AI decision-model provider (TypeSafe AI) through the AI gateway that routes requests to it (Vercel). We request zero data retention on every such request: under those providers' published terms, the gateway deletes the request once it completes, the decision model keeps it no longer than needed to produce its answer except where its legal obligations require, and neither uses it to train models, although a provider may keep a request it flags for abuse or safety review under its own policies. Either provider may process a request outside the United States (Data Processing Addendum § 11.2). We never send either of them text from a workspace whose AI Security setting is Sealed, or whose setting cannot be determined.
• We will not use account contact information for unrelated marketing without separate, unbundled consent.

4. Disclosures

4.1 Sub-Processors and service providers

We disclose information to sub-processors/service providers who process information on our behalf under contracts that limit their use to the purposes we specify. The current Sub-Processor List is at https://inscendoiq.com/trust/subprocessors and includes: our AI model and embedding providers, TypeSafe AI (AI decision model for our typed-decision features, reached through Vercel; it states that it hosts its service in the United States, but may process a request outside the United States; from November 12, 2026), Vercel (AI gateway that routes those requests to TypeSafe AI and may process a request outside the United States, from November 12, 2026), Microsoft Azure, Backblaze (off-site immutable backup storage, United States), our transactional email providers, Twilio (delivery of the one-time sign-in, verification, and password-reset codes you ask for, by text message or automated voice call, United States), Stripe, Cloudflare, GitHub, and GoDaddy. For our own sales, onboarding, and customer communications (§ 2.11, § 4.8), our team also uses business email, calendar, and telephone service providers, currently Microsoft (Microsoft 365), RingCentral, and Postmark, which receive the contact details and content needed to deliver an email, place or receive a call or text message, or schedule a meeting.

4.2 To Customers (B2B context)

If you are an authorized user, your activity is visible to your organization's administrators. If you use the Service through a third party that has invited you, that third party may receive your activity data.

4.3 Legal requirements

We may disclose information when required by law or when we believe in good faith that disclosure is necessary to (a) comply with legal process, (b) protect Inscendo's or others' rights, property, or safety, (c) investigate fraud or AUP violations, or (d) defend against legal claims.

4.4 Business transactions

If we are involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction. We will use reasonable efforts to notify customers and to require the receiving party to honor commitments materially equivalent to this Policy.

4.5 With your direction

We disclose information to third parties when you direct us to (e.g., when you configure an integration, install a capsule, or invite a collaborator). This includes when an account administrator of your organization connects 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: the information that application requests from your organization's account is sent to it at your organization's direction, as the connecting user, and is then held by that provider under your organization's own agreement with it, not under our agreement with our AI model provider (§ 3.1).

4.6 Aggregated and de-identified data

We may share aggregated or de-identified data freely.

4.7 To the partner who referred your organization

If your organization registers through a partner's referral link, including a link your browser remembered under § 2.7, that partner is told the name of the company that registered. In its partner account, the partner can also see when the company registered, whether its workspace is active, and whether it pays for Inscendo Premium, because the partner's commission depends on it. We do not give the partner any other account information, any personal information about the people who use the account, or any Customer Data. Our sign-up page ordinarily names the partner before you register. A demo booking credited to a partner under § 2.11 is not disclosed to the partner.

4.8 Our own customer record of a paid subscription

When your organization starts a paid subscription, including when a free trial converts to a paid one, we keep a record of it in a workspace we operate for ourselves on the Service, the same workspace in which we run our own sales and partner pipeline (§ 2.11), so that our team can welcome you, help you set up, and support your account. The record holds your organization's name and account identifier; the account owner's name, email address and, if the owner has given one, account mobile number (§ 2.1); whether the account owner chose to receive product updates and promotions from us; which categories of our text messages (§ 2.11) the account owner has agreed to or withdrawn from, and when, so that we text the account owner only in the categories agreed to; the plan, its status, the first payment and the next renewal date; any partner referral code your organization signed up through and that partner's name (§ 4.7); and a reference to any demo or consultation booked with us (§ 2.11). If we already hold a contact record for the account owner from an enquiry or booking, the two are joined. Members of our team who have chosen to be alerted are emailed a summary when the record is created.

We use this record to welcome and onboard your organization, including calling the account owner about setting up and using the subscription, and to support and bill your account. We send marketing email from it only if the account owner chose to receive product updates and promotions, and every marketing email carries an unsubscribe link (§ 7). We do not send text messages to the account mobile number from it unless the account owner has separately agreed to receive our text messages (§ 2.1, § 2.11). The record is disclosed only to the Sub-Processors and service providers that operate our systems and carry our team's email, calls and meetings (§ 4.1), and to nobody else. It is not Sold or Shared (§ 3.1, § 10.2). How long we keep it is in § 5.

We also keep a record in the same workspace when your organization starts a free trial of a paid plan, and update it if the trial is extended, so that our team can help you during the trial. It holds your organization's name and account identifier, the account owner's name and email address, whether the account owner chose to receive product updates and promotions from us, and the trial's start and end dates. It is used, disclosed and protected in the same way as the record of a paid subscription above, and we send marketing email from it only if the account owner chose to receive product updates and promotions.

5. Retention

We retain personal information for as long as necessary to provide the Service, comply with legal obligations, resolve disputes, and enforce agreements. Specifically:

• Account information: for the life of the account plus a reasonable post-termination wind-down period.
• A mobile number you provide: for the life of the account, or until you remove it, whichever is first. A new number waiting to be verified is held only until you verify it, replace it, or remove your number. One-time codes are stored hashed and expire shortly after they are sent; the send record kept for rate-limiting and abuse prevention (§ 2.1) is retained on a rolling basis for up to thirty (30) days. The time of your last password reset by text is kept with the number and removed with it. The record of your consent to account security messages is kept under the last entry in this list.
• Passkey credentials: for as long as the passkey exists on your account. Deleting a passkey deletes the stored public key and its metadata. The record that a passkey was added or removed is retained with the account's security history so that history stays complete.
• Operational and diagnostic telemetry logs: up to thirty (30) days. Copies held in routine backups are deleted within the backup-retention window stated in the Backups entry below.
• Authentication-event records (§ 2.2): up to ninety (90) days.
• Conversation history, agent session records, Customer Data, and Customer Configurations: retained for the life of the account; on termination, per the MSA: thirty (30)-day post-termination retention, then deletion subject to backup-retention windows of up to ninety (90) additional days and to legal holds. Ninety days is a ceiling, not an estimate: any off-site backup copy we keep is written once, is kept for a fixed period of no more than ninety (90) days from the date it is written, and cannot be deleted earlier by anyone, including us.
• Backups. Our databases and files are copied into encrypted backups automatically. Each backup 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, whether on your request, on account deletion, or under a retention period above, may remain in those copies until they expire. We do not restore it to live use except to recover the Service after a failure.
• Saved logins (§ 2.4): until the user deletes the saved login or the workspace is deleted, subject to the Backups entry above.
• Billing records: as required by tax and accounting law (typically seven years).
• Marketing-consent records: as required to demonstrate compliance.
• Enquiry, consultation, demo, and partner intake records (§ 2.11): twenty-four (24) months from our last contact with you, after which they are deleted on a recurring schedule. If the enquiry becomes an account, the resulting account information is retained under the account line above instead. If you ask us to delete an enquiry sooner, we will.
• Our own customer record of a paid subscription or of a free trial (§ 4.8): for the life of the account plus a reasonable post-termination wind-down period, then deleted. A contact record we held for the account owner from an enquiry or booking before the subscription began (§ 2.11) is then kept under the entry above instead, without what the subscription record added to it.
• Records that you acknowledged an agreement (the document, its version, the fingerprint of the text shown, the time, and, for an SMS consent, the phone number it was given for and which category or categories of messages it covered): retained for as long as we may need to demonstrate that acknowledgment and to enforce or defend that agreement. This deliberately outlasts both the twenty-four-month enquiry window above and the account itself, because a confidentiality obligation survives the relationship that created it. It is the one category we keep after an account is deleted.

Even after you request deletion, we may retain limited information for as long as necessary to comply with law, satisfy tax and recordkeeping obligations, resolve disputes, prevent fraud and abuse, enforce our agreements, and honor legal holds.

6. Security

We maintain administrative, technical, and physical safeguards described in our Master Subscription Agreement and Data Processing Addendum, including encryption in transit and at rest, logical separation of tenants, access controls, regular platform and dependency updates, and incident-response procedures. Logical separation reduces but does not eliminate cross-tenant risk, and no security program eliminates all risk. You are responsible for credential security and for using available controls.

7. Your Choices

You may:

• Update or correct your account information via in-product settings or by contacting support@inscendoiq.com.
• Delete your account by contacting support@inscendoiq.com.
• Export your Customer Data by requesting it at support@inscendoiq.com, and via any in-product export tools we make available.
• Opt out of marketing communications via the unsubscribe link in any marketing email.
• Configure the Browser Companion: pause it, detach it from a tab, or uninstall it from Chrome.
• Rely on our standing policy that we do not use your data to train foundation AI models (see § 3.1); there is no toggle to set because such training does not occur.

8. Children

The Service is for businesses and is not directed to users under 18. We do not knowingly collect information from anyone under 18. If we learn we have collected information from anyone under 18, we will delete it. Do not use the Service if you are under 18. Customer is contractually prohibited from collecting information from individuals under 18 through the Service (MSA § 3.2(h); AUP § 1.7(e)).

9. Geographic Scope

The Service is intended only for businesses and individuals located in the United States. We do not target, market, advertise, or solicit users outside the United States. If you are located in the EEA, the United Kingdom, Switzerland, China, Russia, Brazil, or any other jurisdiction whose data-protection law would impose extraterritorial obligations on us, please do not use the Service. We use, and/or reserve the right to use, technical measures (including edge-based geographic restrictions) to limit access from outside the United States, and we reserve the right to terminate any account that violates the U.S.-only eligibility requirement.

10. California Privacy Notice

This section is provided to address the California Consumer Privacy Act, as amended by the California Privacy Rights Act, and applicable regulations (collectively "CCPA"), and applies to California consumers irrespective of whether Inscendo would be a covered "Business" by reference to revenue and consumer thresholds. Definitions in this § 10 follow the CCPA.

10.1 Categories collected (last 12 months)

Category (Cal. Civ. Code § 1798.140)	Collected?	Source	Disclosed for a business purpose to
Identifiers (name, email, IP, account ID, optional mobile number, a phone number you give us on a form, SMS opt-in status, passkey credential identifier and public key)	Yes	You / your employer / you as a website visitor, prospect, or prospective partner (§ 2.11)	Sub-Processors; the service providers that carry our own team's email, calls and meetings (§ 4.1)
Customer records (Cal. Civ. Code § 1798.80)	Yes	You / your employer / you as a website visitor, prospect, or prospective partner (§ 2.11)	Sub-Processors
Commercial information (transactions; what you tell us about the systems you use and what you are trying to solve)	Yes	You / your employer / you as a prospect or prospective partner (§ 2.11)	Sub-Processors; the partner who referred your organization, limited to the company name, registration date, workspace status and whether it pays for Premium (§ 4.7)
Internet/electronic activity	Yes	Your interactions	Sub-Processors
Geolocation (IP-derived, coarse)	Yes	Your interactions	Sub-Processors
Audio, electronic, visual (browser screenshots, voice via integrations)	Limited	Your use of the Browser Companion or voice integrations	Sub-Processors
Professional / employment information (job title, role, size of the team you manage)	Yes	You / you as a prospect or prospective partner (§ 2.11)	Sub-Processors
Inferences	Yes	Derived	Sub-Processors
Sensitive Personal Information	No (Service is contractually prohibited from processing)	—	—

Phone number and SMS opt-in status. Where a form offers SMS consent (§ 2.11), the Identifiers we collect include the phone number you give and a record of which category or categories of text messages you consented to and when. Both are collected from you, are used only to operate our SMS program, and are not Sold or Shared and not disclosed to any third party or affiliate for that party's own purposes, including marketing or SMS/text marketing purposes (§ 10.2).

Account mobile number. Your account mobile number, and the record of your consent to account security messages at it (§ 2.1), are collected from you and used to verify the number and to deliver the codes you ask for and, if you are the account owner of an organization with a paid subscription, for our own customer record of it and for our team to call you about setting up and using that subscription (§ 4.8). They are disclosed only to the provider that delivers the codes and to the service providers that carry our team's calls (§ 4.1), are never used for marketing, and are not Sold or Shared (§ 10.2).

Customer-connected AI applications. Where an account administrator of your organization connects a third-party AI application to the organization's account under the organization's own subscription (§ 4.5), the categories above that the application requests are disclosed to that application at your organization's direction. That is a disclosure your organization directs, not a Sale or Sharing (§ 10.2).

10.2 Sales / Sharing

We do not Sell or Share personal information for cross-context behavioral advertising or any other purpose. Because we do not Sell or Share, there is nothing for a Global Privacy Control signal to opt out of; we do not currently process such signals automatically.

10.3 Your rights

California consumers have the right to:

• Know what personal information we have collected, used, disclosed, and (if applicable) sold or shared.
• Delete personal information, subject to legal exceptions.
• Correct inaccurate personal information.
• Limit use of Sensitive Personal Information (we do not process SPI).
• Opt out of Sale and Sharing, not applicable, because we do not Sell or Share personal information.
• Non-discrimination for exercising privacy rights.

10.4 How to exercise

Submit a request via support@inscendoiq.com. We will verify identity using reasonable means proportionate to the request. We will respond within forty-five (45) days, with one extension where permitted. Authorized agents are accepted with written authorization and verification.

10.5 Notice at Collection

The categories above are collected for the purposes set out in § 3 of this Policy. We retain each category as set out in § 5. Sensitive Personal Information is not knowingly collected.

This notice is given at or before collection on every form that collects personal information, including the contact, demonstration, consultation, and partner intake forms described in § 2.11. Those forms collect Identifiers, Customer records, Commercial information, and Professional / employment information; they are collected for the purpose in § 3(h); they are retained for twenty-four (24) months from our last contact with you, except for a record that you acknowledged an agreement, which is retained for as long as that agreement may need to be demonstrated or enforced (§ 5). Where a form offers SMS consent, the Identifiers collected also include the phone number you give and your SMS opt-in status, both retained as set out in § 5. They are not Sold or Shared.

11. Other State Privacy Notices

Residents of Texas, Virginia, Colorado, Connecticut, Utah, Oregon, Montana, Iowa, Indiana, Tennessee, Delaware, New Hampshire, New Jersey, Maryland, Minnesota, Rhode Island, Kentucky, and other U.S. states with comprehensive privacy laws may have rights to access, delete, correct, port, and opt out of certain processing under their state law. Submit requests via support@inscendoiq.com. We will respond consistent with the timelines set by each applicable state law. Texas-resident requests are handled under the Texas Data Privacy and Security Act.

12. Privacy of End-User Data Submitted by Subscribers

When a Subscriber uses the Service to process the personal information of its own customers, employees, contractors, or other end-users, the Subscriber, not Inscendo, is the controller / Business with respect to that information. Inscendo acts as the Service Provider / Processor / Sub-Processor under the Data Processing Addendum.

This Privacy Policy does not apply to such end-users' personal information. End-users should refer to the relevant Subscriber's own privacy notice. Inscendo is not in a position to respond to data-subject rights requests from end-users; please direct such requests to the Subscriber that controls your data.

13. Changes to this Policy

We may update this Policy from time to time. Material changes will be communicated by posting the updated Policy and, where required by law, notifying you. The "Effective Date" at the top reflects the most recent revision.

14. Contact

• Privacy and security incidents: support@inscendoiq.com
• Mail: Inscendo Automation Inc., 24900 Pitkin Rd, Ste 210, Spring, TX 77386, USA, Attn: Privacy

[End of Privacy Policy]