Terms of Use

The agreement between you and Primordio LLC governing your use of the Primordio Documentation Generator.

How this document fits with your other agreements

This document governs the Primordio Documentation Generator — this product, and nothing else.

It does not supersede, amend, replace, or waive any separate written agreement you have with Primordio LLC — a master services agreement, statement of work, order form, non-disclosure agreement, data processing addendum, business associate agreement, or anything similar. If you hold one, it continues to govern its own subject matter exactly as written.

It also does not replace the policies published on primordio.com, the Primordio LLC company website. Those cover that website.

Each of these agreements stands on its own and must be reviewed and accepted on its own. Nothing here is acceptance of those, and accepting those is not acceptance of this.

Order of precedence

Any signed written agreement with Primordio LLC — controls over everything below it, as to its own subject matter.
These product terms and this product’s privacy notice — the Terms of Use, Privacy Policy, Cookie Policy, Data Processing Addendum and Support & Policies — control for this product.
The primordio.com terms and policies — cover that website.

Not sure which agreement applies to you? Ask us at contact@primordio.com before you rely on an answer.

Version: 3.2
Last updated: September 30, 2026
Effective: October 1, 2026

Version 3.2 — Last updated September 30, 2026 — Effective October 1, 2026

These Terms of Use (“Terms”) are a binding contract between you and Primordio LLC, a Delaware limited liability company (“Primordio,” “we,” “us,” or “our”), governing your access to and use of the Primordio Documentation Generator, our websites, APIs, documentation, the Primordio desktop application for macOS (the “Desktop Application,” Section 5A), and any related services (together, the “Service”).

1. Acceptance of these Terms

1.1 How you accept. You accept these Terms by checking the box next to a statement that you agree to them and then clicking the button that completes account creation or sign-in, or by clicking any other control we present that is labeled to indicate that clicking it constitutes agreement to these Terms. We record when you accept, and which version was in force at that time.

1.2 If you do not agree. Do not check the box, and do not access or use the Service. You may read these Terms, the Privacy Policy, the Cookie Policy, and the Support & Policies page in full at any time while you have access to the Service, at /terms, /privacy, /cookies, and /support. If you want to read any of them before you have an account, or you have lost access and need a copy, email contact@primordio.com and we will send you the current text at no charge.

1.3 Authority. If you accept these Terms on behalf of a company, organization, or other legal entity, you represent and warrant that you are authorized to bind that entity, and “you” means both you individually and that entity. Where an entity is bound, that entity and each of its Authorized Users are jointly and severally responsible for all activity in its workspaces.

1.4 Renewed acceptance. We may require you to accept a revised version of these Terms before continuing to use the Service, as described in Section 2.

1.5 Order of precedence. These Terms govern this product. They do not supersede, amend, replace, or waive any separate written agreement you have with us — a master services agreement, statement of work, order form, non-disclosure agreement, data processing addendum, business associate agreement, or anything similar — and they do not replace the terms and policies published on the Primordio company website, which cover that website. Each of those agreements stands on its own and must be reviewed and accepted on its own. Nothing here is acceptance of those, and accepting those is not acceptance of this.

Where two of them genuinely conflict, this is the order that resolves it:

Any signed written agreement with Primordio LLC — controls over everything below it, as to its own subject matter.
These Terms and this product’s other policies — the Privacy Policy, Cookie Policy, Data Processing Addendum, Support & Policies, and the plan and quota documentation published on our pricing page — control for this product.
The Primordio company website’s terms and policies — cover that website.

The Data Processing Addendum applies automatically to every customer and does not require a signature; where it conflicts with these Terms as to its own subject matter, it controls.

1.6 What these Terms do not cover. Paid engagements and professional services are governed by a separate signed agreement. Nothing on this site, in the Service, in our documentation, or in any pricing, feature, roadmap, or marketing material forms part of such an agreement, constitutes an offer capable of acceptance, or amends terms already agreed between us. A statement of work, professional services agreement, or order form is formed only when both parties sign it.

2. Changes to these Terms

2.1 Prospective effect only. We may revise these Terms. Any revision applies only to your use of the Service after the revision takes effect. No revision applies to any claim that has already accrued, to any claim either party has already asserted, or to any dispute for which a Notice of Dispute has been sent under Section 17.2.

2.2 Notice. For any material revision we will give you at least 30 days’ advance notice, by email to the address on your account and by notice inside the Service. The notice will identify the new version, state its effective date, and link to the full text and to a summary of what changed. We will give this notice whether or not any law requires it.

2.3 How a revision takes effect. A material revision takes effect only when you accept it through the in-product prompt described in Section 1.1. If you do not accept, you may continue to use the Service under the version you last accepted until the end of your then-current billing period, after which we may suspend your access to features that require compute. Non-material revisions — corrections, clarifications, and changes required by law — take effect on posting.

2.4 Your right to leave. If you do not wish to accept a material revision, you may terminate your subscription before its effective date and we will refund the unused portion of any prepaid fees on a pro-rata basis. This right is a material part of the consideration for these Terms.

2.5 Section 17 is excluded from unilateral revision. We will not revise Section 17 (Dispute Resolution) as it applies to you except by your affirmative acceptance of a new version under Section 2.3. A revision to Section 17 never applies retroactively to any claim, accrued or known.

3. Eligibility and territory

3.1 Age. You must be at least 18 years old and able to form a binding contract. The Service is not directed to and may not be used by anyone under 18.

3.2 United States only. The Service is offered from and intended solely for use within the United States. We do not offer the Service to, and you may not use it from, the European Economic Area, the United Kingdom, or Switzerland. We have not undertaken the obligations of the EU or UK General Data Protection Regulation or the EU AI Act, and we make no representation that the Service satisfies them. If you access the Service from outside the United States you do so on your own initiative and are responsible for compliance with local law.

3.3 Sanctions and export. You represent that you are not located in, organized under the laws of, or ordinarily resident in any country or territory subject to comprehensive U.S. sanctions, that you are not on any U.S. government restricted-party list, and that you will not use the Service in violation of U.S. export control or sanctions law.

3.4 Private beta, and beta or pre-release features. The Service is currently offered as a private, invitation-only beta, and we may from time to time label a particular feature “beta,” “preview,” “early access,” or “experimental.” For the Service while it is in private beta, and for any feature so labeled at any time:

(a) access is revocable at any time, in whole or in part, with or without notice, and we may change, limit, condition, or withdraw the feature entirely;

(b) it is provided without warranty of any kind — Section 13 applies in full;

© there is no service level agreement, and no uptime, availability, performance, backup, retention, or data-durability commitment of any kind, and none is implied by any figure, dashboard, or status page;

(d) you must not rely on it in production, and must not use it as the sole basis for any decision that could cause financial loss, legal exposure, or harm to any person;

(e) non-public features, interfaces, and documentation you see through it are our confidential information under Section 16; and

(f) you may not benchmark it, or publish any performance, evaluation, or comparison result about it, without our prior written consent; and

(g) we may restrict access by geographic region within the United States, and we use the approximate location our hosting provider derives from your network address to enforce that restriction. A request refused on that basis is not a breach by us and is not a service failure.

The Desktop Application is offered under this Section. It is a beta feature; we may require you to install a particular minimum version to keep using it; and we may withdraw it, change it, or stop supporting any kind of target it records — Mac applications, local web applications, or the iOS Simulator — at any time.

Where this Section conflicts with any other provision of these Terms as to a beta or pre-release feature, this Section controls.

4. Accounts, workspaces, and Authorized Users

4.1 Accounts. Authentication is provided through our identity provider. You must provide accurate registration information and keep it current, including a working email address — Section 11 depends on it.

4.2 Credentials and API keys. You must safeguard your account credentials and API keys. An API key grants the rights of a workspace owner (personal keys) or administrator (organization keys). API keys are not scoped or limited by permission. Notify us at contact@primordio.com immediately if you learn of unauthorized access.

4.3 Workspaces and roles. Content, verified domains, quotas, and billing are scoped to a workspace. Workspace administrators and owners can add and remove members, verify and remove domains, and delete content — including content created by other members. If you join an organization workspace, the organization controls that workspace and everything in it, and may access, modify, export, or permanently delete anything you create there.

4.4 Authorized Users. You are responsible for ensuring that everyone you permit to use your workspaces (“Authorized Users”) complies with these Terms. Their acts and omissions are treated as your own.

5. Site verification and your authorization to automate

This Section is fundamental. The Service drives an automated web browser against websites and applications that we do not own or control. The Desktop Application goes further: it drives real applications on your own Mac. Section 5A adds to this Section for that case, and every representation in this Section applies to a target you record with the Desktop Application as it applies to a verified domain.

5.1 Verification proves control, not permission. Before the Service will run against a domain, you must prove control of that domain by publishing a DNS TXT record we specify. Passing this check does not establish that you are legally authorized to automate the site, and we do not and cannot verify that you are. It is a technical gate, not a legal one.

5.2 Your representation — full and proper permission, for every system, every time. For every domain you verify and every run you initiate, you represent, warrant, and covenant on a continuing basis that:

(a) you have the legal right to authorize automated access to, automated interaction with, and screen recording of the target system by a third-party service. That right must rest on one of three bases: you are the owner-operator of the target system; you hold current written authorization from its owner; or you act as an authorized agent within the scope of that agency. Where the Service asks you to identify which of these applies, you must answer truthfully, and we keep your answer with the domain record;

(b) where the target system is hosted, operated, or provided by a third party — including any software-as-a-service platform, website builder, managed host, marketplace, or white-labeled application — you hold whatever authorization that provider’s terms require for automated access and screen recording, in addition to your own. Verifying a domain you control does not, by itself, give you permission that the platform behind it has not given. If the platform’s terms prohibit automated access, recording, or reproduction of its interface, you may not use the Service against it, whatever your own authorization;

© your use of the Service against that system does not violate its terms of service, acceptable use policy, robots directives, contractual restrictions, or any applicable law, including the Computer Fraud and Abuse Act, state computer-crime and unauthorized-access statutes, wiretap and recording statutes, and anti-circumvention law;

(d) you have obtained every consent and given every notice required for us to process any personal information appearing on the screens the Service records;

(e) you are not using the Service against a system belonging to a competitor, a third party without its knowledge, or any system you have been asked or ordered to stop accessing; and

(f) you have the right to have the target system’s screens — its interface, text, images, logos, and the data it displays — reproduced, stored, and distributed as part of the videos, screenshots, and written guides the Service generates. Access permission and content permission are different rights, and you must hold both. You are solely responsible for whether the generated output may be published, shared, or used commercially.

Every run approval renews this representation. When you approve a run, you make each representation in this Section again, as of that moment, for that system. The Service asks you to confirm this explicitly, in a short attestation, before it will start a run from the review gate or restart one from a stage — and it records that you did: the statements you confirmed, the version of these Terms in force, who you are, when, and the network address and browser you used, together with the results of the checks it ran before starting (Section 6.4(f) and Section 5.3). That record is kept with the run and delivered beside its output. If you cannot make every one of these representations for a system, do not verify it and do not run against it. The safest way to make all of them true is to record a demonstration copy of your system populated with made-up data; our documentation explains how.

5.3 You must keep this true. If your authorization for a verified domain lapses, is revoked, or is disputed, or if your technical control of the domain changes, you must stop running against it and remove the domain from your workspace immediately. We may require you to re-verify a domain at any time — including after a DNS change, an account change, a complaint, or suspicious activity — and may suspend runs against it until you do.

5.4 No investigation duty. We have no obligation to investigate, and disclaim any duty to determine, whether you are authorized to automate a given system. We rely entirely on your representations in this Section, and we retain a record of them. We may nonetheless, at our discretion, ask you for evidence of your authorization for a particular system and decline to run against it until you provide it.

5.5 If a site owner objects, or ownership is disputed. If the operator of a target system objects to automated access, or if anyone disputes your authority over a verified domain, we may block that system across the Service for all customers and freeze runs against the domain while we look into it — without first deciding who is right, without notice to you, and without liability. We may keep the freeze in place until the dispute is resolved to our reasonable satisfaction, and we may ask you for evidence of your authority as a condition of lifting it. We publish an abuse contact at contact@primordio.com for this purpose.

5.6 Consequences. Breach of this Section is a material breach. We may immediately suspend or terminate access, remove content, revoke domain verifications, disable or delete generated output, preserve records reasonably necessary to investigate, and cooperate with any lawful investigation or complaint. Section 14 applies to any claim arising from your automation of any system.

5.7 Verification scope. Verifying a registrable domain covers that domain and all subdomains, and the verification is shared across your workspace. You are responsible for the consequences of that scope, including runs initiated by other members of your workspace against any covered host. Verification does not extend to any other domain, including a domain a target system redirects or links to; the Service blocks the automation browser from navigating to any host outside the verified allow-list for a run, and you may not attempt to defeat that block or use a redirect, DNS change, or any other technique to cause a run to reach an unverified host.

5.8 Verification integrity. You may not obtain, keep, or use a domain verification by any means other than your own lawful control of that domain’s DNS. That includes obtaining it through unauthorized access to a DNS account or registrar, a compromised or borrowed account, social engineering, a lapsed or hijacked domain, temporary control you were not entitled to, or any other deceptive means. Holding a valid verification while lacking legal authority to direct runs against the domain is itself a material breach, whether or not the verification was obtained honestly. We may revoke any verification we reasonably believe was obtained or is being held in breach of this Section, cancel runs, disable or delete the output of those runs, and suspend or terminate your account.

5A. The Desktop Application and Local Automation

5A.1 What the Desktop Application does. The Desktop Application is software you install on a Mac. When you direct it to, it finds, operates, and records software running on that Mac in order to produce a demonstration: (a) applications installed on the Mac; (b) web applications served from the same Mac at a loopback address (localhost, 127.0.0.1, or [::1]), which it opens in a separate recording browser; and © iPhone applications running in Apple’s iOS Simulator on that Mac. We call this “Local Automation,” and we call each of those a “target.” Local Automation happens on a real computer, in real applications, with your own mouse, keyboard, and clipboard, and it has real effects. When a tutorial is narrated, each recorded step waits for its spoken line — the action happens near the end of the line — so a narrated recording runs more slowly than the steps alone. Unless you turn the rehearsal off for a tutorial, the Desktop Application performs its steps twice — once without recording, to find every control and settle any question, and once while recording — so anything a step changes is changed twice, and your cleanup steps are what undo it.

The Desktop Application is offered for macOS on Apple silicon only. It does not connect to a physical iPhone, it does not record web applications served from any other computer, and it does not automate anything we have not expressly designated as a supported target.

5A.2 Your authorization for every Local Automation. Every time you start, approve, continue, or restart a Local Automation, you represent, warrant, and covenant that:

(a) you own or control the Mac on which the Desktop Application runs, or hold the express authorization of its owner or administrator to install and use the Desktop Application there and to grant it every permission you grant;

(b) you own, operate, or are expressly authorized to automate and record every target involved — the application, the local web application, the Simulator application, and every account, document, file, and dataset the recording touches — and hold whatever permission the target’s developer, publisher, licensor, or platform requires for automated operation and screen recording, in addition to your own;

© you have authority to direct each action the tutorial asks the Desktop Application to perform, and no owner, provider, employer, administrator, or other person entitled to do so has told you to stop or has prohibited it;

(d) you hold every right needed for the target’s interface, text, images, logos, and data — and anything else visible in the recorded window — to be recorded, reproduced, stored, and distributed in the videos, images, and guides the Service produces, and you have obtained every consent and given every notice required for any personal information that will appear;

(e) your automation and recording comply with the target’s license, terms of use, acceptable-use and developer terms, your employer’s and organization’s policies, and applicable law, including the Computer Fraud and Abuse Act, state computer-crime and unauthorized-access statutes, wiretap and recording statutes, and anti-circumvention law; and

(f) you have read the tutorial’s steps and understand what they will do.

Technical ability to operate or record an application is not legal authority to do so, and a permission granted to the Desktop Application by macOS is not authorization from anyone. We do not investigate, and do not warrant, that you hold the authority you represent. Before every recording the Desktop Application asks you to confirm these statements in a short attestation and records that you did — the statements you confirmed, the version of these Terms in force, who you are, and when — with the recording on your Mac, and sends us a receipt of it: the recording’s identifier, the statements’ hashes, the versions in force and accepted, the time, the app version, the kind of target, and the run’s settings, and nothing else, which we keep. Your acceptance of these policies in the Desktop Application is recorded with your account in the same way. If you cannot make every one of them for a target, do not record it. The safest way to make them true is to record a demonstration copy of the application, populated with made-up data, in a dedicated demonstration account.

5A.3 Loopback means this Mac, and nothing else. The Desktop Application records web applications only at a loopback address on the same Mac and blocks the recording browser from leaving that address during a run. That support exists so that you can demonstrate software you are developing, testing, or running on your own Mac. You may not use it, directly or indirectly, to reach or operate any other system. Without our express written authorization you may not use a proxy, relay, tunnel, port forward, reverse proxy, container or virtual-machine port mapping, hosts-file or DNS change, redirect, embedded resource, alias, or any similar technique to cause an address that appears local to communicate with, or control, a system on your network or anywhere else; and you may not direct a Local Automation at a router, network-management interface, cloud-metadata service, password manager, credential store, keychain, endpoint-security or device-management product, or any other administrative or security service merely because your Mac can reach it. Passing the Desktop Application’s address check is a technical result, not authorization, and an attempt to defeat that check is a breach whether or not it succeeds.

5A.4 macOS permissions. To perform Local Automation the Desktop Application needs two permissions that macOS asks you to grant: Accessibility (to read and operate the controls of other applications) and Screen & System Audio Recording (to record the window). Recording an iPhone application additionally requires Xcode, the iOS Simulator runtime, and the automation tooling that our documentation names, which you install and license yourself. The Desktop Application does not ask for Local Network, Files & Folders, Automation (Apple Events), or administrator access, and must not be run from an administrator or root session to make anything work.

You decide whether to grant a permission and are responsible for understanding its scope. A macOS permission is broader than any one recording: Accessibility and Screen Recording permit the Desktop Application to read and operate every application on the Mac, not only the target you chose. Granting a permission is not authorization from us, from macOS, or from anyone else to use the Service against material you otherwise lack permission to operate or record. You may revoke a permission at any time in System Settings; the Desktop Application will then stop working in whole or in part, and that is not a defect or a breach by us. You must not modify macOS, disable its protections, weaken its security settings, or grant elevated access to make an unsupported use work.

5A.5 Least privilege. Run the Desktop Application as an ordinary user, with only the permissions in Section 5A.4, on a Mac and in an account set aside for demonstrations where reasonably possible. You assume the additional risk created by any elevated privilege you choose to grant.

5A.6 Local Automation can take the wrong action. Local Automation relies on the names and structure that applications expose through macOS accessibility, on what is visible on screen, on timing, on the state of the application, and on a plan written in plain English — any of which can be incomplete, ambiguous, stale, or changed without notice by the application’s publisher. The Desktop Application may therefore: (a) identify the wrong control; (b) click, type into, select, open, close, save, overwrite, move, rename, or delete the wrong thing; © act in a different window or application than you expected; (d) enter text into the wrong field, or paste it where the cursor happens to be; (e) be thrown off by a notification, dialog, pop-up, update, focus change, display change, or delay; (f) repeat an action, including by performing a step in the rehearsal and again in the recording; (g) fail to perform an action, or perform it after the application has changed; (h) use its best guess of the control where you have chosen that mode for a tutorial; or (i) otherwise behave differently from the plan or from an earlier run. When the Desktop Application cannot tell which control a step means, it may ask you, and it may show a model a picture of the window (Section 6.3); neither is a warranty that it will choose correctly. You acknowledge that any of these can have irreversible effects.

5A.7 Use demonstration environments, and keep backups. The Desktop Application exists to make demonstrations; it is not a tool for administering production systems. Use a disposable, test, staging, or demonstration copy of the application, populated with made-up or non-sensitive data, wherever reasonably possible. You are responsible for backing up — or being able to recreate — any document, file, project, repository, database, Simulator, configuration, or account state that a Local Automation could affect, and for closing unrelated applications, turning off notifications, and clearing the screen of anything you do not want recorded. Do not use the Desktop Application where an unexpected click, keystroke, paste, submission, overwrite, or deletion could cause material financial loss, legal consequences, bodily harm, a security compromise, or the loss of anything irreplaceable. We are not a backup or recovery service and have no obligation to restore your Mac, your files, an application’s state, a Simulator, or any third-party system.

5A.8 Consequential actions. Unless we expressly support a specific use in writing, you must not use Local Automation to complete or authorize an action that has significant legal, financial, security, or operational consequences — for example transferring money or digital assets; making a purchase; executing a trade; signing or accepting an agreement; filing a government or regulatory submission; publishing, deploying, or modifying production software or infrastructure; deleting production data; adding, removing, or changing the privileges of users; changing passwords, recovery methods, authentication, or security settings; disabling security software; issuing refunds; or sending mass communications. If a demonstration must show such a workflow, use a sandbox, mock, or demonstration environment, or stop the tutorial before the action takes effect.

5A.9 You supervise; you can stop it. You remain responsible for watching a Local Automation and for stopping it if it behaves unexpectedly. The Desktop Application provides a Stop control and ends a run when the pointer is moved into a corner of the screen; the mouse, keyboard, and clipboard remain yours during a run, so touching them changes what the run does. Do not leave a run unattended where a reasonable person would know that an unexpected action could cause material harm. Every confirmation, question, refusal, blocked target, permission check, or other safeguard the Desktop Application provides is an additional precaution — not a warranty that an unsafe, destructive, unauthorized, or unintended action will always be detected or prevented.

5A.10 The iOS Simulator. Where you record an iPhone application: (a) you are responsible for obtaining and complying with Apple’s Xcode and SDK agreements and every other license that governs the Simulator, the tooling, and the application; (b) you may record only applications and content you are entitled to build or install, run, automate, record, and reproduce; © you may not use the Service to circumvent code signing, provisioning, entitlements, authentication, digital-rights management, licensing, or any other technical restriction of Apple’s or of an application’s publisher; (d) the Simulator is not a physical device — appearance, performance, permissions, hardware features, notifications, networking, authentication, and input can all differ — and a demonstration recorded in the Simulator is not evidence of how the application behaves on a physical iPhone; and (e) you are responsible for validating any demonstration against the environment your audience will actually use. Primordio is independent of Apple, Google, and every other operating-system, tooling, browser, and application provider; their names and marks belong to them.

5A.11 Consequences. Breach of this Section is a material breach, and Sections 5.6, 14, and 15 apply. We may disable the Desktop Application, invalidate a version of it, require you to update it, refuse a category of target, or suspend your account, immediately and without liability, where we reasonably believe its use presents a legal, security, privacy, platform-compliance, abuse, or operational risk — before we have determined conclusively whether a breach occurred.

6. Your Content, run inputs, and credentials

6.1 Your Content. “Your Content” means everything you submit to or generate through the Service — site URLs, instructions, descriptions, plans, run inputs, uploaded logos, the tutorials you write in the Desktop Application, and the videos, captions, transcripts, written guides, screenshots, recordings, and storyboards produced from them, whether they are stored with us or on your Mac. As between you and us, you own Your Content.

6.2 License to us. You grant us a worldwide, non-exclusive, royalty-free license to host, store, copy, transmit, display, reproduce, modify, and otherwise process Your Content solely as necessary to operate, secure, support, and improve the Service, to enforce these Terms, and to comply with law. The license ends when Your Content is deleted, except for copies in routine backups, in aggregated or de-identified form, or as required by law. Content the Desktop Application keeps on your Mac and never sends us is not hosted, stored, or processed by us; this license reaches it only when, and to the extent that, it is sent to us.

6.3 No sale, no model training. We do not sell Your Content. We do not use Your Content to train our own models, and we have not opted in to any program that would permit our AI providers to train on it. We will use only AI providers, and only configurations of those providers, whose published terms state that data we submit and output we receive are not used to train or improve the provider’s models absent an opt-in we have not given; if a provider changes that position, we will stop using it, or change to a configuration that preserves it, before continuing to process Your Content through it. Those providers’ handling of data submitted through their interfaces is otherwise governed by their own terms, which are summarized in the Privacy Policy. We do not send run input values or saved inputs to any AI provider. What we send is text — your written steps, notes, clarification answers, and the narration to be spoken — and, where a step’s control cannot be found by its words, an image of the screen being recorded: in the Desktop Application today, one picture of the window being recorded with the likely controls numbered on it, sent together with the step’s words, your words for the control, and the names of the numbered controls, unless you have turned that feature off in Settings › Privacy. When a Desktop Application tutorial is narrated, its steps’ words (with input placeholders such as {{EMAIL}}, never their values or the text a step types), their targets and notes, and any spoken lines you wrote are sent to write the narration, and each line is sent to be spoken; the narration comes back to your Mac and we keep no copy of it. An image sent to an AI provider is subject to the same rule as text: the provider may not train on it, and we keep no copy of it. The Privacy Policy states exactly what is sent, when, and what such an image can contain. We may extend the use of images to other parts of the Service — for example to find a control in a cloud run — and the Privacy Policy will say so before we begin. Anything visible on the screen when such an image is taken may be in it, which is one more reason to record demonstration data only (Section 6.5).

6.4 Run inputs and credentials — read this before you type a password.

The Service accepts “run inputs” — values you supply that are typed into the target system during a run, which may include usernames and passwords. You agree that:

(a) you will use only credentials for a dedicated test, staging, or demonstration account created specifically for use with the Service, and not credentials for any production system or for any account with administrative, financial, or elevated privileges;

(b) you are entitled to create, hold, and share those credentials, and sharing them with us does not breach the terms governing that account;

(d) you will not submit any government-issued identifier, payment card number, financial account number, or authentication factor for a financial account; and

(e) you will not submit credentials for, and will not run against, any system that creates, receives, maintains, or transmits Protected Health Information as defined at 45 C.F.R. § 160.103, payment card data subject to PCI DSS, nonpublic personal information subject to the Gramm-Leach-Bliley Act, education records subject to FERPA, biometric identifiers, or precise geolocation — unless we have first signed a written addendum with you covering that category. We have not signed one unless you hold a countersigned copy. Section 3.5 of the Data Processing Addendum states the same prohibition and lists the categories in full.

(f) run inputs are the only place a credential may go. You will not put a password, API key, token, session cookie, one-time code, recovery code, or any other authentication secret into a step instruction, tutorial title or description, section heading, note, clarification answer, site URL, support or contact message, or any other field of the Service. Those fields are not credential-storage mechanisms: instructions, notes, and clarification answers are sent to our AI provider, stored in the plan and narration, and may be spoken aloud in the generated video; URLs appear in logs; support messages are stored in our mailbox. Our secret handling — masking, redaction, erasure at the end of a run — applies to run inputs only. If you put a credential anywhere else, you must revoke or rotate it immediately. When you approve a run, the Service scans those fields for credential-shaped text and will not start until you have reviewed what it found; that scan matches patterns, and we do not warrant that it will detect every credential placed in an unsupported field. We may delete content we believe contains one.

Saved inputs. The Service lets you save a run input on a tutorial so that it is supplied automatically on every later run. A saved input is stored as entered until you remove it or delete the tutorial. It is not erased when a run finishes. Everything in (a) through (f) applies to a saved input with more force, because the value outlives the run. Saving is a convenience for demonstration accounts; the Service is not a credential vault, and you must not treat it as one.

Run inputs in the Desktop Application. The Desktop Application asks for run input values when a recording starts and uses them on your Mac; they are not sent to us. A value whose input name reads as a secret is never written to the recording’s files or logs and is not shown in captions; other values appear in the captions of the video, by design. Typing into a Mac application is done through the clipboard, whose previous contents are put back afterwards. Everything in (a) through (f) applies to a Desktop Application run. The credential-shaped-text scan described in (f) is performed for cloud runs; the Desktop Application does not currently scan the text of a tutorial before recording, so what you write in a desktop tutorial’s steps, notes, and answers is entirely your responsibility.

The Privacy Policy describes how run inputs are handled, including a limitation you should read: redaction does not apply to images. You assume all risk arising from any credential or value you submit or save in breach of this Section, and Section 14 applies.

6.5 What is on screen becomes part of the output, permanently. A run records the target system as it appears at that moment. Anything visible — real customer names, records, messages, account data — is permanently embedded in the resulting video and screenshots. In the Desktop Application the recorded window is a window on your own Mac, and it may show notifications, window and document titles, account names, file names and paths, tabs, messages, dialogs, and content from other parts of the application that you did not mean to show; and the same window is what a model sees when the Desktop Application asks one (Section 6.3). You are solely responsible for ensuring the target displays only data you are entitled to have recorded, stored, reproduced, and shown to our AI provider. You must not point the Service at screens displaying third-party personal data. We strongly recommend running only against systems populated with synthetic demonstration data, with notifications off and unrelated applications closed.

6.6 Recording and consent. You represent that you have authority to consent, on behalf of every party whose communications or screen content the Service captures, to the recording of that content. You acknowledge that some jurisdictions — Pennsylvania among them — require the consent of all parties to a recorded communication, and that you, not we, are responsible for obtaining any consent required in the jurisdictions where you and the people whose data appears on screen are located.

6.7 AI-generated output — read this before you publish anything. The Service uses large language models to plan runs and write narration, and a text-to-speech model to synthesize that narration into audio. This is what the product does, so be clear about what it means:

(a) Output is probabilistic, not deterministic. It is generated by a statistical model predicting likely continuations, not by a system that knows whether what it produces is true.

(b) Output may be inaccurate, incomplete, outdated, or confidently wrong. A fluent, authoritative-sounding answer carries no more assurance of correctness than a hesitant one, and the Service gives no signal that distinguishes the two.

© The same input may not produce the same output twice. Identical instructions run again may yield different steps, different narration, or a different result. Do not treat any output as reproducible, and do not rely on a previous run as evidence of what a future one will do.

(d) It is a starting point for human judgement and never a substitute for it. You are responsible for reviewing and validating every generated plan, video, transcript, and guide before you rely on it, publish it, or give it to anyone else. You must review every generated plan before running it.

(e) It is not professional advice. Nothing the Service produces is legal, financial, tax, accounting, medical, safety, engineering, or other professional advice, and it must not be presented or relied on as any of those. It must not be used to produce instructions where an error could cause bodily injury, financial loss, or legal harm without independent verification by a qualified person.

(f) It may not be unique, and we do not warrant that it is yours to use. Narration, plans, and written guides generated for you may resemble or match those generated for other customers from similar instructions. Section 6.1 gives you what we have in Your Content; it does not, and cannot, give you rights in the target system’s interface, text, images, logos, or data that appear in the output, or in any third-party material the model reproduces. Whether you may publish, share, or commercially use a given output is a question of the rights you hold (Section 5.2(f)) and is yours alone to answer. We do not warrant that any output is original, protectable by copyright, or free of third-party claims.

The narration in videos produced by the Service is generated by an AI voice. It is not a recording of a human voice. We include a disclosure of this in the videos we produce. You must not remove, obscure, or alter that disclosure, and you must not represent to anyone that the narration was recorded by a person.

6.8 The Desktop Application is not a vault, and your Mac is in scope. The Desktop Application is not a password manager, credential vault, secrets manager, or key store. Unless a field is one we expressly identify as a run input, you must not place a password, API key, private key, access or refresh token, session cookie, one-time code, recovery code, signing certificate, encryption key, connection string, or other authentication secret into a tutorial’s steps, titles, notes, section headings, clarification answers, file names, or any other field of the Desktop Application — those fields are kept on your Mac in the tutorial, may be sent with a model request under Section 6.3, and are not redacted. Any credential used in a Local Automation must belong to a dedicated demonstration, development, test, or staging account with no more privilege than the demonstration needs; never a production, administrative, financial, recovery, password-manager, or signing credential. The restrictions on Sensitive Data in Section 6.4(e) and in Section 3.5 of the Data Processing Addendum apply to everything visible on the Mac during a recording. If a credential is exposed through a recording, an image, a log, or generated output, treat it as compromised and rotate it at once.

7. Acceptable use

You will not, and will not permit any Authorized User or third party to:

(a) use the Service against any system you have not verified, or for which you cannot make every representation in Section 5.2 — including any system whose platform, host, or provider prohibits automated access or recording, and any system whose screens you are not entitled to reproduce and distribute in generated content;

(a-1) use the Service to record, or to generate content depicting, any person, account, message, record, or data that you are not permitted to record, reproduce, and publish — whether the restriction comes from the law, from the rights of the person or organization concerned, or from the terms of the system displaying it;

(b) use the Service to test, probe, scan, stress, or attempt to defeat the security, rate limits, bot detection, CAPTCHA, or access controls of any system, whether or not you own it;

(b-1) cause or attempt to cause a run to reach any host outside the verified domain — by redirect, DNS change, link, embedded content, or otherwise — or any private, internal, loopback, link-local, or cloud-metadata network address, or any of our own infrastructure other than the interfaces we document — except a loopback address on your own Mac that the Desktop Application records under Section 5A.3;

(b-2) obtain, keep, or use a domain verification in breach of Section 5.8;

(c-1) use the Service, this site, or any of their content or output to train, fine-tune, pre-train, distill, evaluate, benchmark, ground, retrieve into, or otherwise develop or improve any machine-learning or artificial-intelligence model, without our prior written permission. This applies whether the content is obtained through the interface, the API, a crawler, an export, or a third party, and it applies to output generated for you as well as to our own text, documentation, and designs;

(d) create content that is unlawful, defamatory, harassing, deceptive, or infringing, or that depicts a real person without authorization;

(e) impersonate any person or entity, or misrepresent your affiliation or authorization;

(f) reverse engineer, decompile, disassemble, or attempt to derive the source code, models, or prompts of the Service, except where that restriction is unenforceable by law;

(g) resell, sublicense, rent, or provide the Service to third parties as a service bureau, or build a competing product using the Service;

(h) circumvent quotas, metering, rate limits, verification, billing, or usage enforcement, including by creating multiple accounts;

(i) upload or transmit malware, or use the Service to stage an attack against any system;

(j) interfere with or unreasonably burden the Service or its infrastructure, or access it by automated means other than our documented API;

(k) remove, obscure, or alter any attribution, watermark, provenance metadata, or AI disclosure we include in generated output; or

(l) use the Service in violation of any law or of any third party’s rights.

For the Desktop Application, you will additionally not:

(m) bypass, disable, interfere with, deceive, or evade any target check, address check, blocked application or category, permission check, confirmation, attestation, question, rate limit, licence check, minimum-version requirement, or other safeguard the Desktop Application or the Service implements;

(n) alter DNS, a hosts file, proxy or routing settings, an application’s bundle identifier, process name, window title, or accessibility metadata, a Simulator’s configuration, or any other technical information for the purpose of misleading the Desktop Application about what it is operating or recording;

(o) modify, patch, hook, inject into, tamper with, or replace the Desktop Application, its automation helper, its recording browser, or any component, or run a modified copy, for the purpose of expanding its authority or defeating a restriction;

(p) use prompt injection, adversarial or hidden instructions, encoded commands, synthetic interface elements, or any similar technique to cause a model or automation component to ignore a safeguard or perform an action the Service prohibits;

(q) bypass or attempt to bypass macOS privacy and security controls, code signing, notarization, application sandboxing, Simulator provisioning or entitlements, or any authentication, anti-bot, CAPTCHA, or other security mechanism of any system;

® use the Service to obtain credentials, session data, keys, tokens, personal information, or confidential information you are not authorized to obtain, or to operate a password manager, keychain, credential store, security product, device-management or backup system, financial application, or cryptocurrency wallet in order to extract or change what it protects;

(s) use Local Automation for malware, ransomware, credential theft, persistence, surveillance, unauthorized remote control, data exfiltration, destructive activity, spam, fraud, or the compromise of any system;

(t) conceal, alter, destroy, forge, or interfere with any attestation, run record, log, or other record the Desktop Application or the Service keeps in order to investigate misuse;

(u) continue a Local Automation after we, a target’s owner or provider, your employer, an administrator, or another authorized person has told you to stop; or

(v) do indirectly — through another application, script, agent, Simulator, local service, proxy, or intermediary — anything these Terms prohibit you from doing directly.

An attempted violation of this Section is a violation, whether or not it succeeds. The Desktop Application refuses some categories of application as targets and records each refusal, each blocked address, and each blocked click in its log; we may ask you for that log when investigating a complaint.

We may investigate suspected violations and may remove content or suspend access without prior notice where we reasonably believe it necessary to protect the Service, our users, or a third party.

8. Plans, billing, automatic renewal, and cancellation

8.1 Paid service. The Service is offered on paid subscription plans. There is no free tier. Plan features, quotas, and prices are published on our pricing page and incorporated into these Terms.

8.2 Automatic renewal — read this before you subscribe. Subscriptions renew automatically until you cancel. At the end of each billing period we charge the payment method on file the then-current price for another period of the same length, without further action by you. Before you purchase we show you the renewal interval and the price that will recur, and your renewal date is shown in your account under Billing at any time.

8.2.1 Trials. We do not currently offer a free trial. If we offer one in the future, it will require a valid payment method and will convert automatically into a paid subscription at the end of the trial period unless you cancel before it ends — and we will tell you, before you provide payment information, the length of the trial, the date it converts, the amount that will be charged, and how to cancel, and we will send a reminder before conversion.

8.3 Billing. Subscriptions are billed in advance through our billing and payment processors on a recurring basis until cancelled. You authorize us and our processors to charge your payment method on each renewal at the then-current price. Fees are in U.S. dollars and exclusive of taxes; you are responsible for all applicable taxes other than taxes on our net income.

8.4 Refunds. Except as stated in Section 2.4 and Section 8.4.1, and except where required by law, fees are non-refundable, including for partial billing periods, unused quota, downgrades, suspensions, or terminations for cause. Periods are not pro-rated when a subscription is cancelled part-way through. Quota does not roll over.

8.4.1 Billing errors we always correct. The Section above is not a licence to keep money we should not have taken. We will always correct, and refund where appropriate, a duplicate charge, a charge taken after a valid cancellation, a charge at the wrong amount or on the wrong plan, and a charge resulting from unauthorized use of a payment method. Tell us at contact@primordio.com or through the support contact form and we will put it right.

8.4.2 Rights you cannot waive. Nothing in Section 8.4 limits any right or remedy you have under law that cannot be waived by agreement, and any provision that would do so is severed as to that law only.

8.4.3 Where the detail lives. The full billing, renewal, cancellation, refund, chargeback, and export terms are on the Support & Policies page and form part of these Terms.

8.5 Metering. Usage is metered per workspace against your plan’s quotas, using our systems, and those measurements are final absent manifest error. Desktop Application recordings are metered against the workspace chosen for their tutorial, as builds in the web application are: the first recording of a tutorial in a workspace uses one tutorial credit when it starts, and every recording that completes uses video minutes equal to its finished length, rounded up to whole minutes. A recording does not start when the workspace’s credits (for a tutorial’s first recording) or minutes are exhausted. A recording made while your Mac cannot reach us is metered when the Desktop Application next reaches us, and you must not prevent that report from being sent. When a quota is exhausted the Service may refuse further compute until the next billing period or an upgrade. Failed payment may result in a grace period followed by loss of access to compute features.

8.6 Cancellation. You may cancel at any time, from your account settings, without contacting anyone and without giving a reason. Cancelling stops the next renewal. Access continues to the end of the period you have already paid for, and cancellation takes effect at that point; it then stops future billing and your ability to create, run, rerun, and generate. Cancellation does not delete your content. Section 11 governs what happens to it afterward, and gives you an export window and advance notice before anything is deleted.

8.7 Price changes. We may change prices on at least 30 days’ notice by email before the start of a renewal term. A price change takes effect only at your next renewal — never part-way through a period you have already paid for. Continued use after the change takes effect is acceptance of the new price; if you do not want it, cancel before the renewal date under Section 8.6.

8.8 Failed payments. If a charge fails we retry it and tell you by email before your access is affected, and we allow a grace period in which you can update your payment method. Section 15 governs suspension if payment is not completed.

8.9 Chargebacks. If you believe a charge is wrong, contact us first — Section 8.4.1 exists precisely so that you do not need a chargeback to get a billing error corrected, and we will respond within the time stated on the Support & Policies page. If a chargeback is opened we respond to your bank with our transaction records, and we may suspend access to the affected workspace while the chargeback is open. Fees remain payable while a dispute is pending unless we agree otherwise.

9. Intellectual property and attribution

9.1 Our rights. The Service and all software, models, prompts, designs, documentation, and trademarks we provide are owned by us or our licensors. We grant you a limited, non-exclusive, non-transferable, revocable license to access and use the Service during your subscription in accordance with these Terms, including to install and run the Desktop Application on Macs you own or control, for use with your account, in object-code form only. You may not copy the Desktop Application except for backup, distribute it, or make it available to anyone outside your workspace, and Section 7(f) and 7(o) apply to it. The Desktop Application checks its licence with us periodically and may stop working when it cannot, when your plan ends, or when you sign in on another Mac; it is licensed for use on one Mac per person at a time. All rights not expressly granted are reserved.

9.2 Attribution and provenance. Generated written guides include an attribution line identifying the tool that produced them, and generated audio and video may carry provenance metadata or watermarks applied by us or our providers. You may not remove, obscure, or alter any of these, and you grant us the right to include them in output delivered to you.

9.3 Trademarks. Nothing here grants you any right to use our names, logos, or trademarks without our prior written consent.

9.4 Copyright complaints. If you believe content on the Service infringes your copyright, send a notice meeting 17 U.S.C. § 512©(3) to contact@primordio.com. We may terminate the accounts of repeat infringers.

10. Feedback

If you send us suggestions, ideas, bug reports, or other feedback, you grant us a perpetual, irrevocable, worldwide, royalty-free, fully paid license to use and exploit it for any purpose without attribution or compensation.

11. Data retention, inactivity, and deletion

11.1 While your account is active. We retain Your Content for as long as you maintain your account, subject to your plan’s storage quota and version limits. A successful rerun may automatically remove the oldest retained version of a tutorial once your plan’s version cap is reached.

11.2 We never delete content while you are paying. So long as your workspace has an active paid subscription in good standing, we will not delete Your Content under this Section, however long it has been since anyone signed in.

11.3 Export window after cancellation. If your subscription ends — by cancellation, expiry, non-payment beyond any grace period, or a trial that does not convert — your content remains available to view and download for at least 30 days afterward. Nothing is deleted under Section 11.4 during that window.

11.4 Inactivity deletion. After the export window in Section 11.3, we may permanently delete Your Content — videos, captions, transcripts, written guides, screenshots, storyboards, and associated metadata — once your workspace has been Inactive for 60 consecutive days.

A workspace is “Inactive” when, for 60 consecutive days, both:

(a) no Authorized User has signed in to it or made an authenticated API request to it; and

(b) it has no active paid subscription in good standing.

11.5 Notice before deletion — we will tell you. Before deleting anything under Section 11.4, we will send at least two notices: one approximately 30 days before, and one approximately 7 days before, the deletion date. Each notice will go to the email address on your account and to the billing contact on file, will state the deletion date, and will include a working link to export your content. We will keep a record of every notice we send.

We commit to attempting this notice; we cannot warrant delivery to an email address that is out of date, blocked, or abandoned. Keeping a current email address on your account is your responsibility, and so is keeping your own copies of anything you want to preserve. The Service provides export and download functions for exactly this purpose.

11.6 We will not delete content that is in dispute. We will not delete Your Content under Section 11.4 while, to our knowledge, the workspace is subject to a litigation hold or preservation demand, has a disputed charge or pending refund, or has an open support ticket about the account.

11.7 Deletion is permanent. Content deleted under this Section, or by you or a workspace administrator, cannot be recovered. We have no obligation to maintain backups of Your Content for your benefit or to restore deleted content.

11.8 Other deletion. We may also delete content and terminate accounts where required by law, where necessary to protect the Service or a third party, or following termination under Section 15.

11.9 Content on your Mac. Tutorials, recordings, images, and logs the Desktop Application keeps on your Mac are under your control, not ours: we cannot see, export, or delete them, deleting your workspace or account does not delete them, and uninstalling the Desktop Application does not delete them either — the Privacy Policy names the folder. Keeping or removing them is your responsibility.

11.10 What survives. Usage, metering, billing, subscription-consent, privacy-request, audit, and security records may be retained after content deletion, for the periods and purposes described in the Privacy Policy. Deletion of Your Content does not relieve you of any payment obligation accrued before it.

12. Third-party services and links

The Service depends on third parties for authentication, hosting, storage, compute, database, artificial intelligence, email delivery, our company mailbox, bot detection, and payment processing, and your target system is itself a third-party system as to us. We are not responsible for third-party services, their availability, security, acts, or omissions, or any change they make that affects the Service. Your use of a third-party service may be subject to that party’s own terms. The providers we use are named in Section 5.3 of the Privacy Policy.

Software on your Mac. Local Automation depends on macOS and its accessibility and screen-recording frameworks, on the applications you record, on Xcode, the iOS Simulator and the automation tooling for iPhone recording, and on the recording browser (Google Chrome where it is installed, or a copy of Chrome for Testing the Desktop Application downloads once at your request) — none of which we make or control. Their publishers may change interfaces, accessibility names, permissions, security controls, license terms, or compatibility at any time, and an update to any of them may make a previously working tutorial fail or behave differently. That is not a defect in the Service, and we do not warrant continued compatibility with any version of any of them.

Links. The Service and our documentation may link to sites and resources we do not control. A link is not an endorsement, and we are not responsible for the content, accuracy, practices, or availability of anything on the other side of it. Following a link is at your own risk and subject to that site’s own terms and privacy policy.

13. Disclaimers and limitation of liability

13.1 AS IS. TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICE AND ALL OUTPUT ARE PROVIDED “AS IS” AND “AS AVAILABLE,” WITHOUT WARRANTY OF ANY KIND. WE DISCLAIM ALL WARRANTIES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, QUIET ENJOYMENT, ACCURACY, AND NON-INFRINGEMENT, AND ANY WARRANTY ARISING FROM COURSE OF DEALING OR USAGE OF TRADE.

13.2 Specific disclaimers. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, SECURE, OR ERROR-FREE; THAT ANY RUN WILL SUCCEED OR PRODUCE ACCURATE OUTPUT; THAT ANY OUTPUT WILL BE UNIQUE, ORIGINAL, OR FREE OF THIRD-PARTY RIGHTS; THAT DOMAIN VERIFICATION ESTABLISHES ANY LEGAL OWNERSHIP OR AUTHORITY; THAT A CREDENTIAL PLACED IN AN UNSUPPORTED FIELD WILL BE DETECTED OR REDACTED; THAT AUTOMATED INTERACTION WITH YOUR SYSTEM WILL NOT CREATE, MODIFY, OR DELETE DATA ON IT; THAT CONTENT WILL BE PRESERVED OR RECOVERABLE; OR THAT DEFECTS WILL BE CORRECTED. YOU ACKNOWLEDGE THAT A RUN CAUSES REAL SOFTWARE — A BROWSER IN OUR CLOUD, OR, WITH THE DESKTOP APPLICATION, APPLICATIONS ON YOUR OWN MAC — TO PERFORM REAL ACTIONS ON A REAL SYSTEM, AND THAT THOSE ACTIONS MAY HAVE IRREVERSIBLE EFFECTS.

13.2A Desktop Application. WITHOUT LIMITING THE REST OF THIS SECTION, WE DO NOT WARRANT THAT THE DESKTOP APPLICATION OR ANY LOCAL AUTOMATION WILL IDENTIFY THE CORRECT WINDOW, APPLICATION, CONTROL, FILE, OR TARGET; WILL NOT CLICK, TYPE INTO, PASTE INTO, OPEN, CLOSE, MOVE, RENAME, OVERWRITE, MODIFY, SUBMIT, OR DELETE THE WRONG THING; WILL NOT CHANGE APPLICATION, ACCOUNT, FILE, SETTING, CONFIGURATION, SIMULATOR, OR CLIPBOARD STATE; WILL DETECT EVERY CREDENTIAL, SECRET, SENSITIVE VALUE, DESTRUCTIVE ACTION, CONSEQUENTIAL ACTION, OR UNSAFE CONDITION; WILL STOP BEFORE AN IRREVERSIBLE ACTION; WILL ASK YOU, OR ASK A MODEL, BEFORE ACTING, OR WILL ACT CORRECTLY AFTER DOING SO; WILL PERFORM A STEP ONCE RATHER THAN TWICE; WILL PRESERVE YOUR FILES, DOCUMENTS, APPLICATION STATE, SIMULATOR STATE, LOCAL DATA, OR CONFIGURATION; WILL BE COMPATIBLE WITH ANY VERSION OF MACOS, ANY APPLICATION, ANY DISPLAY CONFIGURATION, ANY ACCESSIBILITY IMPLEMENTATION, XCODE, OR THE SIMULATOR; WILL CAUSE THE SIMULATOR TO BEHAVE AS A PHYSICAL DEVICE WOULD; OR WILL PREVENT ANY APPLICATION FROM RESPONDING TO AN AUTOMATED ACTION IN AN UNEXPECTED OR DESTRUCTIVE WAY. YOU ARE RESPONSIBLE FOR MAINTAINING BACKUPS, USING DEMONSTRATION ENVIRONMENTS, REVIEWING EVERY TUTORIAL BEFORE RECORDING IT, WATCHING EACH RUN, AND DECIDING WHETHER YOUR MAC AND THE TARGET ARE SUITABLE FOR AUTOMATION.

13.3 EXCLUSION OF DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY WILL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, GOODWILL, BUSINESS OPPORTUNITY, DATA, OR CONTENT; ANY COST OF SUBSTITUTE SERVICES; ANY BUSINESS INTERRUPTION; OR ANY DAMAGE TO OR UNAUTHORIZED CHANGE IN ANY SYSTEM THE SERVICE INTERACTS WITH — WHETHER IN CONTRACT, TORT, STRICT LIABILITY, OR OTHERWISE, AND WHETHER OR NOT ADVISED OF THE POSSIBILITY. FOR THE DESKTOP APPLICATION THIS INCLUDES, TO THE MAXIMUM EXTENT PERMITTED BY LAW, ANY LOSS, CORRUPTION, ALTERATION, DESTRUCTION, DISCLOSURE, OR UNAVAILABILITY OF FILES, DOCUMENTS, REPOSITORIES, DATABASES, APPLICATION DATA, SIMULATOR OR DEVICE DATA, CONFIGURATION, CREDENTIALS, SETTINGS, OPERATING-SYSTEM STATE, CLIPBOARD CONTENTS, OR THIRD-PARTY SYSTEM DATA ON OR REACHABLE FROM YOUR MAC; THE COST OF RESTORING, RECONFIGURING, REINSTALLING, REBUILDING, OR RECREATING ANY OF THEM, OF INCIDENT RESPONSE, OR OF ROTATING CREDENTIALS; AND ANY LOSS ARISING FROM A TRANSACTION, COMMUNICATION, PUBLICATION, DEPLOYMENT, ACCOUNT CHANGE, PERMISSION CHANGE, OR SECURITY CHANGE MADE THROUGH LOCAL AUTOMATION. THIS DOES NOT APPLY TO YOUR PAYMENT OBLIGATIONS OR YOUR OBLIGATIONS UNDER SECTIONS 5, 5A, 6, 7, OR 14.

13.4 GENERAL CAP. SUBJECT TO SECTIONS 13.5 AND 13.6, OUR TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THESE TERMS OR THE SERVICE WILL NOT EXCEED THE GREATER OF (A) THE TOTAL AMOUNTS YOU PAID US IN THE TWELVE MONTHS IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM, OR (B) ONE THOUSAND U.S. DOLLARS ($1,000).

13.5 ENHANCED CAP FOR SECURITY AND CONFIDENTIALITY. FOR CLAIMS ARISING FROM OUR BREACH OF SECTION 16 (CONFIDENTIALITY) OR FROM A FAILURE OF OUR SECURITY OBLIGATIONS THAT RESULTS IN UNAUTHORIZED ACCESS TO OR DISCLOSURE OF YOUR CONTENT, OUR TOTAL AGGREGATE LIABILITY WILL NOT EXCEED THREE TIMES THE AMOUNT IN SECTION 13.4.

13.6 What these limits do not touch. Nothing in this Section limits or excludes any liability that cannot be limited or excluded by law, including liability for fraud, fraudulent misrepresentation, gross negligence, or willful misconduct. Nothing in these Terms waives, limits, or purports to limit any right or remedy under the California Consumer Privacy Act or any other statute that voids contractual limitations on its remedies, and any provision that would do so is severed as to that statute only.

13.7 Basis of the bargain. The disclaimers, exclusions, and caps in this Section are a fundamental basis of the bargain and are reflected in the price of the Service. They apply even if a limited remedy fails of its essential purpose.

13.8 Jurisdictional limits. Some jurisdictions do not allow certain exclusions or limitations. In those jurisdictions this Section applies only to the fullest extent permitted.

14. Indemnification

You will defend, indemnify, and hold harmless Primordio and its members, managers, officers, employees, contractors, and agents from any claims, demands, actions, investigations, proceedings, damages, losses, liabilities, fines, penalties, settlements, and expenses (including reasonable attorneys’ fees) arising out of or relating to:

(a) your access to, automation of, recording of, or interaction with any system, including any claim by a system’s owner, by a platform or host on which it runs, or by a regulator, that such access was unauthorized;

(b) Your Content, including any personal information, confidential information, or third-party intellectual property captured in a run or embedded in output;

(c-1) any domain verification you obtained or held in breach of Section 5.8, and any output generated under it;

(d) your breach of these Terms or of any representation or warranty in them;

(e) your violation of any law or the rights of any third party; or

(f) any dispute between you and an Authorized User, a workspace member, or your organization;

(g) your installation, configuration, permissioning, or use of the Desktop Application, and any Local Automation you start, approve, continue, or restart, including every action the Desktop Application performs because of the tutorial, configuration, permissions, environment, or target you supplied or controlled;

(h) any application, local web application, Simulator application, account, file, document, or other target you direct the Desktop Application to operate or record, and any claim by its owner, publisher, provider, platform, licensor, or by a regulator, that the operation or recording was unauthorized;

(i) your failure to obtain any authorization, license, consent, or notice required from the owner, publisher, provider, administrator, employer, user, or other rights holder of a target, or from any individual whose information appeared in a recorded window;

(j) any credential, secret, Sensitive Data, confidential information, or third-party content exposed through your Mac, a target, a recording, an image sent to an AI provider, or generated output;

(k) your use of macOS, Xcode, the iOS Simulator, a browser, an application, or any other third-party software or service in breach of its terms;

(l) any attempt to bypass, defeat, or mislead a safeguard of the Desktop Application, the Service, macOS, or a third party, and any breach of Sections 5A or 7(m) through 7(v); or

(m) any loss, change, or unavailability of data or systems on or reachable from your Mac, or any transaction, communication, publication, deployment, or account, permission, or security change, made through Local Automation.

Your obligations under this Section are not subject to the caps in Section 13. We will notify you of any claim and may assume exclusive control of its defense and settlement at your expense. You will not settle any claim in a way that imposes an obligation or admission on us without our prior written consent. This Section survives termination.

15. Suspension and termination

15.1 By you. You may stop using the Service at any time and cancel under Section 8.6.

15.2 By us. We may suspend or terminate your access, in whole or in part, immediately and without liability, if we reasonably believe that you have breached these Terms; that your use creates a security, legal, or operational risk; that a system owner or authority has objected to your use; that your payment has failed; or that we are required to act by law. Where practicable and lawful we will give notice. For the Desktop Application we may also, on the same grounds and with the same immediacy, disable its functionality in whole or in part, invalidate a version of it, require an update before it will work again, refuse a category of target, or revoke its licence — before determining conclusively whether a breach occurred — and doing so in good faith to protect the Service, a user, a third party, or a system creates no liability on our part.

15.3 Discontinuation. We may modify, suspend, or discontinue the Service or any feature. If we discontinue the Service entirely we will make reasonable efforts to give at least 30 days’ notice and an opportunity to export Your Content.

15.4 Effect. On termination your license ends, accrued fees become due, and Section 11 governs Your Content — including the export window in Section 11.3 and the notices in Section 11.5. Sections 5.4, 5.6, 5.8, 5A.2, 5A.3, 5A.11, 6, 9, 10, 11, 12, 13, 14, 16, 17, and 18 survive.

16. Confidentiality and publicity

16.1 Each party will protect the other’s non-public information with at least reasonable care and use it only as necessary under these Terms. This does not apply to information that is public through no fault of the recipient, independently developed, rightfully received from a third party, or required to be disclosed by law.

16.2 We may identify you as a customer and use your name and logo in customer lists and marketing materials, unless you tell us in writing at contact@primordio.com that you object.

17. Dispute resolution

PLEASE READ THIS SECTION CAREFULLY. IT AFFECTS YOUR LEGAL RIGHTS, INCLUDING YOUR RIGHT TO SUE IN COURT AND TO HAVE A JURY HEAR YOUR CLAIMS.

17.1 What this Section covers. This Section applies to any dispute, claim, or controversy arising out of or relating to these Terms or to your use, payment for, or our provision of the Service. It does not extend to any other product, service, or dealing between us.

17.2 Informal resolution first. Before starting an arbitration or other proceeding, the complaining party must send a written Notice of Dispute — to contact@primordio.com if you are complaining, or to the email on your account if we are — describing the dispute, the relief sought, and the account involved. The parties will then try in good faith to resolve it for 60 days. The applicable limitations period is tolled during this time. Neither party may commence arbitration before the 60 days expire.

17.3 Agreement to arbitrate. Except as provided in Sections 17.5, 17.6, and 17.10, you and Primordio agree that any dispute within Section 17.1 will be resolved by final and binding individual arbitration, not in court. The Federal Arbitration Act governs the interpretation and enforcement of this Section.

17.4 Rules and forum. Arbitration will be administered by the American Arbitration Association under its Consumer Arbitration Rules if you are an individual using the Service for personal, family, or household purposes, and otherwise under its Commercial Arbitration Rules, in each case as those rules exist when the demand is filed. Where the AAA’s rules and this Section conflict, the AAA’s rules control. If the AAA will not administer the dispute, the parties will agree on a substitute administrator, and failing agreement either party may bring the dispute in the courts identified in Section 18.2.

Arbitration is before a single arbitrator. Proceedings are remote by default — conducted by telephone, by video conference, or on written submissions alone — unless the arbitrator orders otherwise. You will never be required to travel to arbitrate. If an in-person hearing is genuinely necessary it will be held in the State of Delaware, except that you may instead elect to have it held where you live.

17.5 Delegation. You and Primordio expressly agree that the arbitrator, and not any court, has exclusive authority to resolve all threshold questions — including whether this Section applies, whether it is valid or enforceable, whether a particular claim is within its scope, and whether any condition precedent has been satisfied. This delegation is severable from the rest of this Section, and is not narrowed by any other provision of these Terms, by the exceptions in Sections 17.6 or 17.10, or by the severability provisions in Section 18.7. The only exception is Section 17.7, which by law and by agreement a court decides.

17.6 Sexual harassment and sexual assault claims are excluded. Consistent with 9 U.S.C. §§ 401–402, this Section does not apply to any dispute alleging conduct constituting sexual harassment or sexual assault, at the election of the person alleging it, and whether that statute applies is for a court rather than an arbitrator to decide.

17.7 Class action waiver. YOU AND PRIMORDIO AGREE THAT EACH MAY BRING CLAIMS ONLY IN AN INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY CLASS, COLLECTIVE, CONSOLIDATED, OR REPRESENTATIVE PROCEEDING. The arbitrator may not preside over any class or representative proceeding, and may award relief only to the individual party seeking it. A court, not an arbitrator, decides whether this Section 17.7 is enforceable.

Class arbitration is not available. You and Primordio have not agreed to arbitrate on a class basis, and nothing in these Terms or in any rules incorporated by them should be read as consent to it.

If a court holds this Section 17.7 unenforceable as to a particular claim or request for relief, that claim or request — and only that claim or request — is severed from arbitration and may be brought in the courts identified in Section 18.2. The remainder of this Section 17 continues to apply to all other claims.

17.8 Other exceptions. Either party may bring an individual claim in small claims court if it qualifies and stays there, and either party may seek injunctive or equitable relief in court to protect intellectual property, confidential information, or against unauthorized access to the Service. Doing so waives nothing else.

17.9 30-day opt-out. You may opt out of this Section 17 by emailing contact@primordio.com with the subject line “Arbitration Opt-Out” within 30 days after you first accept these Terms, giving your name and the email address on your account. One email is enough — you never have to opt out again, including when we publish a new version of these Terms. Opting out affects nothing else and does not change your access to the Service in any way. If you opt out, Section 18.2 governs your disputes.

17.10 California consumers. If you are a California resident who acquired the Service primarily for personal, family, or household purposes, then notwithstanding anything else in these Terms: you may require that any claim arising in California be arbitrated or litigated in California and governed by California substantive law, and you may elect to have any dispute that qualifies for small claims court adjudicated there instead. To make either election, tell us at contact@primordio.com. We will not oppose it.

17.11 Jury trial waiver. TO THE EXTENT ANY DISPUTE PROCEEDS IN COURT, YOU AND PRIMORDIO EACH KNOWINGLY AND VOLUNTARILY WAIVE ANY RIGHT TO A TRIAL BY JURY.

17.12 Survival. This Section survives termination of these Terms and of your account.

18. General

18.1 Governing law. These Terms are governed by the laws of the State of Delaware, without regard to its conflict-of-laws rules, and, as to Section 17, by the Federal Arbitration Act. This Section is subject to Section 17.10 and to any other law that gives a consumer a non-waivable right to the application of their home state’s law. The U.N. Convention on Contracts for the International Sale of Goods does not apply.

18.2 Venue. Subject to Sections 17 and 17.10, the exclusive venue for any action is the state and federal courts located in the State of Delaware, and each party consents to personal jurisdiction and venue there.

18.3 Time limit for claims. Any claim arising out of or relating to these Terms or the Service must be commenced within one (1) year after it accrues, or it is permanently barred — except that this period does not apply where the law of your state prohibits or restricts shortening the limitations period, in which case the shortest period that state permits applies instead, and this sentence never operates to shorten a period below what the law allows. This Section is independent of Section 17, and its unenforceability in any jurisdiction does not affect Section 17.

18.4 Assignment. You may not assign these Terms without our prior written consent; any attempt is void. We may assign freely, including in a merger, acquisition, reorganization, or sale of assets.

18.5 Notices. Notice under these Terms is given by email. We give notice to the address on your account, and may additionally give it inside the Service or by posting on our website; you give notice to contact@primordio.com.

A notice sent by email is effective on the day it is sent, if sent before 5:00 p.m. in the sender’s local time on a business day, and otherwise on the next business day — unless the sender receives an automated non-delivery or rejection report for it, in which case that notice is not effective and the sender must resend it by another means we have on file. Keeping a current email address on your account is your responsibility, and a notice we send to the address on your account is effective even if you no longer read it.

Where this Section conflicts with Section 17.2 (Notice of Dispute) or Section 11.5 (deletion notices) as to their own subject matter, those Sections control.

18.6 Force majeure. Neither party is liable for delay or failure to perform (other than a payment obligation) caused by events beyond its reasonable control.

18.7 Severability. If any provision of these Terms is held invalid or unenforceable, it will be limited or severed to the minimum extent necessary and the remaining provisions will remain in full force and effect. The parties intend that every provision be severable, and that no provision’s invalidity cause any other provision — and in particular no provision of Section 17 other than as stated in Section 17.7 — to fail. Section 17.7 governs the consequence of its own unenforceability.

18.8 No waiver. Our failure to enforce a provision is not a waiver. A waiver is effective only in writing and signed by us.

18.9 No third-party beneficiaries. These Terms create no rights in any third party, except that the indemnified parties in Section 14 may enforce that Section.

18.10 Relationship. The parties are independent contractors. Nothing creates a partnership, joint venture, agency, or employment relationship.

18.11 U.S. government users. The Service is “commercial computer software” under FAR 12.212 and DFARS 227.7202. Government use, reproduction, and disclosure are governed solely by these Terms.

18.12 Interpretation. Headings are for convenience only. “Including” means “including without limitation.” These Terms will not be construed against either party as drafter.

18.13 Entire agreement — scoped to this product, and subordinate to any signed agreement. These Terms, with the Privacy Policy, Cookie Policy, Data Processing Addendum, and Support & Policies page, are the entire agreement between you and Primordio as to this product, and supersede all prior and contemporaneous understandings about this product.

This Section is expressly subject to Section 1.5 and does not displace, merge, integrate, or supersede any signed written agreement between you and Primordio, including any master services agreement, statement of work, order form, non-disclosure agreement, data processing addendum, or business associate agreement, nor the terms and policies published on the Primordio company website. Where this Section and Section 1.5 conflict, Section 1.5 controls.

Contact

Primordio LLC, a Delaware limited liability company Email: contact@primordio.com

Notices under Section 17.2, arbitration opt-outs under Section 17.9, and California elections under Section 17.10 may all be sent to that address.

A postal address for formal service is available on request by email, and notices requiring a physical address may also be sent to our registered agent for service of process in Delaware.

For billing, cancellation, refunds, and support, see Support & Policies or write to us through the support contact form.