Demo Pine Terms of Service

Effective date: July 31, 2026 · Last updated: July 31, 2026 · Version 1.0

These Terms of Service (the "Terms") are a binding contract between you and RyanTech LLC, a South Carolina limited liability company doing business as Demo Pine ("Demo Pine," "we," "us," or "our"). They govern your access to and use of the Demo Pine websites at demopine.com, the hosted application at app.demopine.com, the legacy media domain at media.demopine.com (no longer used to serve new media — see Section 12.1), the Demo Pine Capture Chrome extension, our APIs, and everything else we make available (together, the "Service").

Please read Section 30 carefully. It requires most disputes to be resolved by binding individual arbitration, waives your right to a jury trial, and waives your right to participate in a class action. You may opt out of arbitration within 30 days — see Section 30.8 for exactly how.

A note on what this document is. The plain-English summaries in the shaded quote blocks are provided to help you read the Terms. They are not part of the agreement and do not change the numbered sections, which control.

Prior versions of these Terms are archived at https://demopine.com/terms/archive.

1. Agreement to these Terms

1.1 Acceptance. You accept these Terms when you affirmatively agree to them — by checking the box or clicking the button presented at account creation, at first sign-in, or on the first-run screen we present to accounts provisioned by an identity provider — and by then accessing or using the Service. We record the date, time, and version of the Terms you accepted, and we keep an archive of prior versions at https://demopine.com/terms/archive so either of us can establish which version applied at a given time. If you do not agree, do not use the Service.

1.2 Who "you" means. If you use the Service on your own behalf, "you" means you personally. If you use the Service on behalf of a company, employer, client, or other organization, "you" means both you and that organization, and you represent that you have authority to bind it (see Section 3.4). In these Terms, "Customer" means the organization or individual that controls a Workspace and is responsible for the fees for it.

1.3 Other documents that form part of this agreement. Our Privacy Policy, our Data Processing Addendum, the Acceptable Use Policy in Section 11, and any order form, statement of work, or master services agreement signed by both parties are incorporated into these Terms by reference. If you buy through a signed order form or MSA, see Section 28.4 on which document wins.

1.4 Accounts created for you. If your employer or another organization connects single sign-on (SSO) or SCIM directory provisioning to a Workspace, an account may be created for you and added to that Workspace without you visiting Demo Pine first. If your account was created for you this way, we will ask you to review and accept these Terms the first time you sign in, and your 30-day arbitration opt-out period under Section 30.8 runs from that date. Your organization — not Demo Pine — controls that account and the data in that Workspace.

2. Definitions

3. Eligibility, age, and authority to bind

3.1 Age to contract. You must be at least 18 years old, or the age of majority where you live if that is higher, to create an account or enter into these Terms.

3.2 Children. The Service is a business tool. It is not directed to children, and we do not knowingly collect personal information from children under 13, as defined by the Children's Online Privacy Protection Act, or from children under the applicable age of digital consent under Article 8 of the GDPR (16, or a lower age between 13 and 16 where a Member State has set one). If we learn that we hold an account or personal information belonging to a child below the applicable threshold, we will delete it promptly. A parent or guardian who believes we hold their child's information may contact [email protected] and we will delete it and confirm.

3.3 Capacity and law. You may not use the Service if you are barred from doing so under applicable law, or if we have previously terminated your account for cause.

3.4 Authority. If you accept these Terms on behalf of an organization — including by paying with a company card, signing up with a work email, inviting colleagues, or configuring SSO or SCIM — you represent and warrant that you are authorized to bind that organization, and "you" includes that organization. If you do not have that authority, do not create the Workspace or commit it to a paid plan.

3.5 Not for regulated data by default. The Service is a general-purpose product-demo tool. It is not designed, marketed, or certified for the storage or processing of protected health information under HIPAA, cardholder data subject to PCI DSS, government classified information, or the personal data of children. Do not put such data into the Service unless we have agreed otherwise in a signed writing. See Section 11.3.

4. Accounts and account security

4.1 Accurate information. You agree to provide accurate account information and to keep it current.

4.2 We do not currently verify email addresses — please read.

⚠️ Demo Pine does not currently require email-address verification for password sign-ups. A person can create an account using an email address they do not control. Because a Workspace invitation can be accepted by any signed-in account whose email address matches the invited address (Section 5.6), you should confirm out of band — in your own chat, ticketing, or HR system — that the person who accepted an invitation is the person you meant to invite, before you put sensitive captures into a shared Workspace. We disclose this here rather than leave you to discover it.

4.3 Credentials. You are responsible for all activity under your account. Keep your password confidential, use a unique password, and do not share credentials. Passwords must meet the strength requirements enforced at sign-up and password change.

4.4 Notify us. Tell us promptly at [email protected] if you suspect unauthorized access to your account or Workspace. Resetting your password signs out your other sessions.

4.5 API tokens and keys. SCIM bearer tokens, and any other credential we issue, are shown once and must be stored securely by you. You are responsible for everything done with them until you revoke them. If you supply your own third-party API key (see Section 13.4), you are responsible for it and for any charges your provider bills you.

4.6 One person per account. Accounts are for individuals. Do not create an account for a person who has not agreed to these Terms, except through the SSO/SCIM paths described in Section 1.4, where the Customer takes responsibility for its personnel.

5. Workspaces, roles, seats, and membership

5.1 The Workspace controls the data. Demos, media, analytics, leads, brand kits, billing records, and membership belong to the Workspace, and the Customer that controls that Workspace decides how they are used. As between a Member and the Customer, the Customer controls. If you are a Member of an employer's Workspace, your employer administers that Workspace and can see, edit, export, and delete what is in it. What happens to a Member's demos when that Member deletes their Demo Pine account is described in Section 5.8.

5.2 Roles. Workspaces have four roles, in ascending order of capability:

⚠️ Role selection requires the Team plan or above. On the Free and Pro plans, every person you invite joins as an editor and occupies a billable seat; the viewer, admin, and owner roles cannot be assigned, and existing members' roles cannot be changed. This means that on Pro there is no such thing as a free read-only member — everyone you add is charged. If you need free viewers, you need Team.

5.3 What Members can see. Access is scoped to the Workspace, not to the author. Any Member of a Workspace — including a read-only viewer, on plans where that role exists — can see every demo in that Workspace, including all captured screenshots, screen recordings, and HTML captures; can download a full export bundle containing that media; can see every other Member's name, email address, and pending invitations; and can see the Workspace's billing records, including invoice and receipt links and the card brand and last four digits of the payment method on file. On plans with full analytics, Members can also read and export the contact details submitted to lead-capture forms. Do not put anything into a shared Workspace that you are not willing to share with everyone in it.

5.4 Seats. A seat is derived automatically from membership — it is never a number you type in. Your seat count is exactly the number of owner, admin, and editor memberships in the Workspace. Viewer memberships are free and are never counted as seats, but they can only be created on plans that include roles and permissions (Team and above). Changing someone's role changes your seat count and may change your bill (Section 6.6).

5.5 Seat ceilings. Each plan has a maximum number of seats it will grow to. Once a Workspace reaches its ceiling, further invitations, role promotions, and SCIM-provisioned memberships will be refused until you upgrade. Memberships created automatically on a first single-sign-on login are not subject to this check; if they take you past your seat ceiling, we will bill the additional seats or ask you to upgrade.

5.6 Invitations. Only an admin or owner may invite a Member. Invitations are sent by email, expire after 7 days, and can be accepted only by a signed-in account whose email address exactly matches the invited address (subject to Section 4.2).

By inviting someone, you represent that you have a relationship with that person that makes the invitation appropriate and lawful, and that you are authorized to give us their email address for this purpose.

When you send an invitation, you are the sender and initiator of that message for the purposes of the CAN-SPAM Act and equivalent law, and we transmit it at your direction as your service provider. You represent that you have the consent or relationship required by applicable law to send it, including express or implied consent under Canada's Anti-Spam Legislation where the recipient is in Canada, and a lawful basis under the GDPR and ePrivacy rules where the recipient is in the EEA or UK. Invitation emails identify you by name and identify your Workspace, and identify Demo Pine as the service transmitting them. You must not use invitations for marketing, prospecting, or any purpose other than adding a person to your Workspace. A recipient who does not want further invitations may write to [email protected] and we will suppress their address. We may rate-limit or disable invitations from a Workspace that generates complaints.

5.7 When a Member leaves. Removing a Member from a Workspace — whether manually or by SCIM deprovisioning — removes that person's access to the Workspace. It does not delete their Demo Pine account, and it does not delete demos they created. Those demos remain in the Workspace.

5.8 What account deletion does to a Workspace — please read.

✅ Deleting a Demo Pine account no longer deletes the demos that account created in a shared Workspace. When someone deletes their account, we handle each of their Workspaces separately: - A Workspace shared with at least one other Member. Nothing that belongs to the Workspace is destroyed. The demos that person authored, the media attached to them, the Share Links minted from them, and the Workspace's shared brand kit are reassigned to the Workspace's owner and stay in the Workspace. If the leaver was the owner, we promote a successor first — the most senior remaining Member, with ties broken by who joined earliest. The leaver's membership is removed and the seat count is re-synced. Their personal, unshared brand preset is deleted with their account. - A Workspace where they are the only Member. That Workspace is theirs alone, so the entire Workspace is deleted, taking its demos, media, brand kits, analytics events, and lead records with it. This is what makes account deletion a real erasure rather than a rename. We will refuse to delete an account while a Workspace that is solely that person's still has a live paid subscription — active, trialing, past due, or unpaid. Deleting the Workspace does not cancel the subscription with our payment processor, so we stop rather than leave you paying for something that no longer exists. Cancel on the Billing page first, then delete the account (Sections 6.12 and 22.1). We cannot recover a deleted Workspace or a deleted demo. Export anything you need to keep before you delete. A duplicate made by another Member is a separate copy and is not affected either way.

5.9 Workspace disputes. If there is a dispute over who controls a Workspace, we may — but are not required to — suspend the Workspace, require documentation of authority, or defer to the account listed as owner. We are not obligated to arbitrate between you and your colleagues, employer, contractor, or client.

6. Plans, pricing, and billing

6.1 Plans and prices. Prices are in US dollars. The current plans are:

6.2 What each plan includes. The functional differences between plans are set out below. The commitments in this table are contractual — Section 28.4(5) applies only to materials outside these Terms.

* We do not apply a fixed monthly allowance on paid plans. We may throttle generation for a Workspace exceeding 5,000 generations in any 30-day period, or generating at a rate inconsistent with human authoring, and we will contact you before doing so except where the load threatens Service stability. See Section 13.3.

** "Priority support" means we target a first response within one business day. That is a target, not a guarantee, and is not a service-level agreement.

*** No service-level agreement applies unless one is expressly provided in an order form or MSA signed by both parties. See Section 25.2.

† The player shows a "Made with Demo Pine" badge unless the Workspace's plan includes its removal. This is derived from the plan, not from a setting — there is no checkbox to switch the badge off, and it is re-derived from the Workspace's live entitlements each time a demo is viewed rather than frozen into the published copy. So a demo published while you were on a paid plan starts showing the badge again, on the next view, if the subscription ends or downgrades; and a demo shared without signing in always shows it (Section 12.5). See Section 7.2.

6.3 Self-serve checkout. Pro and Team are available through self-serve checkout. Enterprise is sales-led and is provisioned against a signed contract — contact [email protected]. Only an admin or owner may commit a Workspace to a charge.

6.4 Payment processing. Payments are processed by Stripe. When you check out, you enter your card details directly into Stripe's hosted or embedded checkout. Demo Pine never receives or stores your full card number.

We store the billing records Stripe returns to us — amounts, dates, invoice and receipt links, and the card brand and last four digits — so we can show you a billing history. We also retain the raw payment-processor event records behind those entries as an audit trail. Those records may include your billing name, email address, and billing address, and they are kept for accounting, tax, and dispute-resolution purposes, including after your account is closed (see Sections 23.3 and 23.4). Your use of Stripe is subject to Stripe's own terms and privacy policy. You authorize us and Stripe to charge your payment method for all amounts due.

6.5 Automatic renewal — please read.

🔁 YOUR SUBSCRIPTION RENEWS AUTOMATICALLY. Unless you cancel first, your Pro or Team subscription automatically renews at the end of each billing period — every month for monthly plans, every year for annual plans — and the payment method on file will be charged automatically at the then-current rate for your plan and seat count, plus applicable taxes. You may cancel at any time, with no cancellation fee, from the Billing page in the app (app.demopine.com/billing, reachable from your account menu) or through the Stripe customer portal linked there. Cancelling stops the next renewal; it does not end your current paid period.

6.5.1 Pre-purchase disclosure and consent. Before we take your first payment, we present the automatic-renewal terms in a clear and conspicuous disclosure adjacent to the purchase button, obtain your affirmative consent to those terms separately from any other terms, and email you an acknowledgment you can retain that includes the auto-renewal terms, the cancellation policy, and how to cancel.

6.5.2 Renewal reminders. For any subscription with a term of one year or longer, we will send a renewal reminder to the Workspace's billing contact between 15 and 45 days before each renewal, stating the renewal date, the amount that will be charged, the seat count it is based on, and a direct link to cancel. For monthly subscriptions, we send a receipt after each charge showing the same information.

6.5.3 Cancellation is self-service. Cancelling requires no phone call, no email, and no conversation with us. It is available in the same medium in which you subscribed.

6.6 Seat changes and proration. Your bill follows your seat count automatically.

• Seats increase (you invite a Member, or promote a viewer to editor or above): the prorated difference for the remainder of the current billing period is calculated at once and billed on your next invoice. We do not take a separate immediate charge.
• Seats decrease (you remove a Member, or demote them to viewer): the lower seat count takes effect at your next renewal. No credit or refund is issued for the period you have already paid for.
• On annual Team plans, an additional seat added mid-term is charged the prorated portion of the $468 annual seat price for the remainder of the term, on your next invoice.

6.7 Changing plans and intervals. You can switch between monthly and annual billing, and between Pro and Team, at any time from the Billing page. Upgrades are prorated and billed on your next invoice; downgrades take effect at your next renewal. Annual billing is a 12-month commitment billed up front.

6.8 Taxes. Prices are exclusive of taxes. You are responsible for all sales, use, VAT, GST, and similar taxes and duties, excluding taxes on our net income. Where we are required to collect tax, we will calculate and add it — at checkout where our payment processor supports it for your jurisdiction, or on your invoice. You remain responsible for any tax we do not collect. If you are exempt, provide valid documentation before the charge; we will not refund tax already remitted.

6.9 Failed payments and the dunning grace period. If a charge fails, Stripe will retry it according to its standard schedule. Your Workspace keeps full paid access for 14 days measured from the first failed payment, so an expired card does not immediately break your live demos. After that 14-day grace period, the Workspace degrades to Free-plan limits: paid features stop working, but demos that are already published stay published — we do not break a public link you have already put in an email. Access is restored when payment succeeds. We may terminate the subscription if payment remains outstanding.

6.10 Price changes. We may change our prices. For an existing paid subscription, we will give you at least 30 days' notice by email to the Workspace's billing contact or by prominent in-app notice before a price change takes effect, and the new price will apply at your next renewal. If you do not accept the new price, cancel before that renewal date. Changes to the Free plan are governed by Section 7.3.

6.11 Refunds — please read.

💵 FEES ARE NON-REFUNDABLE. Except where a refund is required by applicable law or by Section 6.11.1, all fees are non-refundable and all payments are final. This includes fees for partial billing periods, unused seats, unused AI credits, features you did not use, and periods during which you did not access the Service. You may cancel at any time. Cancellation stops the next renewal and your paid access continues through the end of the period you have already paid for. We do not issue pro-rata refunds for cancellation, downgrade, seat reduction, suspension for cause, or termination for cause. We may, at our sole discretion and without setting a precedent, issue a credit or refund in an individual case.

6.11.1 The exceptions. Section 6.11 does not apply to, and you are entitled to the prepaid refund described in, each of the following:

1. Section 22.1a — you terminate for our uncured material breach;
2. Section 22.3 — we discontinue the Service for a paid Workspace mid-term other than for cause;
3. Section 32.3 — you reject a material adverse change to these Terms;
4. Section 16.4 — you reasonably object to a new sub-processor and we cannot offer an alternative;
5. Section 33.6 — a force majeure event prevents performance for more than 30 consecutive days;
6. Section 29.1 — the EEA/UK consumer right of withdrawal;
7. Section 27.3 — our IP-indemnity remedy;
8. any refund required by applicable law.

6.12 How cancellation actually works. Cancelling sets your subscription to end at the close of the current paid period. There is no mid-period cancellation — you keep what you paid for. You can reverse a pending cancellation at any time before that date from the Billing page. When the subscription ends, the Workspace reverts to the Free plan and its limits: your existing published demos stay published and keep working, but you lose access to paid features, and you will not be able to publish additional demos until your total published count is back within the Free limit of 3. Demos that stay published begin showing the Demo Pine attribution badge again on the next view (Section 7.2).

If you also intend to delete your Demo Pine account, cancel first. We refuse an account deletion while a Workspace that is solely yours still has a live subscription — active, trialing, past due, or unpaid — because deleting the Workspace does not cancel the subscription with our payment processor. See Sections 5.8 and 22.1.

6.13 Billing questions and card disputes. If you believe you have been billed in error, contact us at [email protected] within 60 days of the charge and we will investigate in good faith and respond within 10 business days. Contacting us first is usually faster than a chargeback, and it does not affect any right you have to dispute a charge with your card issuer, which we do not limit or discourage. If a chargeback is filed, we may pause new charges on the Workspace while the dispute is resolved; we will not disable your published demos or delete your data because of a pending dispute. If a chargeback is resolved in our favor and the amount remains unpaid, Section 6.14 applies.

6.14 Collection. Overdue amounts may accrue interest at 1.5% per month, or the maximum rate permitted by law if lower. The prevailing party in any action or arbitration to collect or dispute amounts due is entitled to recover its reasonable costs and attorneys' fees, to the extent permitted by applicable law. This right runs to both parties equally.

7. The Free plan

7.1 What it is. The Free plan costs nothing, requires no credit card, and is limited to 3 concurrently published demos, 1 seat, 200 AI generations per month, and analytics covering only the most recent 30 days. Free-plan demos do not include custom branding, HTML clone capture, branching flows, CSV export, or role selection (Section 5.2).

7.2 Attribution. Demos published on the Free plan carry a "Made with Demo Pine" badge in the player. The badge is derived from the Workspace's plan at the moment a demo is viewed; there is no setting that turns it off, and a demo shared without signing in always carries it. You may not remove, obscure, or circumvent that attribution while on the Free plan, including by modifying the published payload, by proxying the player, or by any technical means.

7.3 We may change or discontinue it. The Free plan is provided as a convenience and is not sold. We may change its limits, meter it, restrict it, or discontinue it entirely at any time. If we make a material adverse change to the Free plan or discontinue it, we will give at least 30 days' notice by email or in-app so you can export your demos or upgrade.

7.4 No warranty or support commitment. The Free plan is provided strictly "as is," with no availability commitment and no support commitment. Sections 25 and 26 apply with full force.

7.5 Fair use. We may limit or suspend a Free account that we reasonably determine is being used to evade paid limits — for example, by creating multiple Workspaces or accounts to exceed the published-demo cap or the seat cap, or by using the anonymous share path described in Section 12.5 to publish beyond your plan's limits.

8. Trials, discounts, and promotional codes

8.1 The Pro trial. We currently offer a 14-day free trial of the Pro plan when you start a Pro subscription through self-serve checkout. A payment method is collected at signup.

Your trial ends 14 days after it starts. Unless you cancel before then, we will charge your payment method $29 per seat (monthly billing) or $288 per seat (annual billing), plus applicable tax, on that date, and the subscription continues as a paid Pro subscription. We will email you a reminder at least 3 days before the trial converts. You can cancel at any time during the trial from the Billing page (app.demopine.com/billing). There is no trial on the Team plan.

8.2 One trial per Workspace. Trials are limited to one per Workspace and one per Customer. We may withdraw or shorten a trial, or refuse a trial, at our discretion, including where we reasonably believe the trial is being abused.

8.3 Trial content. Anything you build during a trial is Customer Content and remains subject to these Terms. If you do not convert, the Workspace reverts to the Free plan and Free-plan limits apply to new publishing — including the 3-published-demo cap (Section 6.12).

8.4 Discounts and promotion codes. We may offer promotional codes, including startup and nonprofit discounts. Codes are single-use unless stated otherwise, are not redeemable for cash, may not be combined unless we say so, and may be revoked if we determine they were obtained or applied improperly. A discount applies for the period stated; unless we state otherwise, renewals are at the standard rate.

9. Customer Content and the license you grant us

9.1 You own your content. As between you and Demo Pine, you own all Customer Content, and you retain all rights in it. We claim no ownership.

9.2 The license we need. You grant Demo Pine a non-exclusive, worldwide, royalty-free, sublicensable (only to our hosting, storage, content-delivery, email, payment, and AI providers, and only for the purposes below) license to host, store, copy, back up, transmit, reformat, re-encode, resize, index, cache, and display Customer Content, and — only when you publish it — to make it publicly accessible through a Share Link. This license exists solely so that we can operate, provide, secure, troubleshoot, and support the Service for you. It does not permit us to use your content to market Demo Pine, and we will not do so without your separate written permission.

9.3 Duration. This license lasts as long as we host the relevant Customer Content and ends when the content is deleted from the Service, subject to three practical limits you should know about:

• Backups and logs. Deleted content may persist in our providers' backups, error logs, and audit records for a limited period until those are overwritten in the ordinary course.
• Share Links. Unpublishing a demo revokes the Share Links minted from it, and so does deleting the demo; the published payload is then purged from storage. A record of the revoked code is kept as a tombstone so the code is not reissued while that record exists; the records themselves are cleared on the retention schedule in Section 23.3. See Section 12.4.
• The retention schedule. Some categories of data are deleted on a fixed clock whether or not you ask us to, and some — including invoices and payment-processor records — are kept beyond the deletion of your content. See Section 23.3.

9.4 We do not review your content. We do not pre-screen, validate, moderate, or verify Customer Content, and we have no obligation to. Demo steps, overlay text, brand kits, and imported bundles are stored as you supply them without server-side content validation. We do not apply automated content-moderation tooling to Customer Content; we act on notices and on our own detection of Acceptable Use Policy violations. You are solely responsible for Customer Content and for the consequences of publishing it.

9.5 We may remove content. We may remove or disable access to Customer Content that we reasonably believe violates these Terms, violates law, infringes a third party's rights, or creates risk or liability for us or for other users. Where practicable and lawful, we will tell you, and where Section 29.2 applies we will give you a statement of reasons.

9.6 Storage and size limits. The Service enforces technical limits, including a 2 MB limit on a demo's structured data (its steps and settings), a 25 MB limit on a published share payload, and a 500 MB limit on import and export bundles, plus a limit on the size of an individual upload. A demo containing a large number of full-resolution screenshots can exceed the 25 MB share cap and fail to publish. We may change these limits. Extremely large imports may fail; that is a technical constraint, not a service failure.

10. Your representations about what you capture

This section matters more in Demo Pine than in most products, because the Service records real screens.

10.1 You have the rights. You represent and warrant that, for all Customer Content, you have all rights, licenses, consents, and permissions necessary to capture it, upload it, store it in the Service, and — if you publish it — make it publicly available, and that doing so does not violate any law, contract, terms of service, confidentiality obligation, or third party's intellectual property, privacy, or publicity rights.

10.2 Screen capture records everything on screen. The Demo Pine Capture extension records the visible contents of the tab you are recording — screenshots taken on each click, optional tab video and tab audio, a copy of the page's HTML, and information about the elements you interact with, which can include text you have typed into form fields. Nothing is automatically redacted, masked, or blurred. If a customer record, an email inbox, an internal admin tool, a credential field, a notification, or a spreadsheet is on screen, it is captured.

Captured media files are stored in a private bucket and are served only through short-lived signed URLs, whether or not you publish the demo — but a signed URL is a bearer token for its lifetime, and URLs we issued before this changed are still plain public URLs. Read Section 12.1 before you decide what to record. You are solely responsible for what is on your screen when you record.

10.3 Third-party personal data. If Customer Content contains personal data about anyone other than you — your customers, your employees, your prospects, or people who submit a lead-capture form on your demo — you are the controller of that data and we are your processor. You represent and warrant that you have a lawful basis for that processing, that you have given any notice and obtained any consent required by law, and that you are entitled to instruct us to process it. Use the blur and redaction tools, or use synthetic data, before you capture.

10.4 Lead-capture forms. If you enable a lead-capture form on a demo, you — not Demo Pine — are responsible for the notice and consent presented to the person filling it in, for the lawful basis for collecting their name, email, and company, and for how you use those details afterward. You must not use lead capture to collect any category of data prohibited by Section 11.3.

The player shows the person a baseline notice above the submit button — that what they enter is sent to Demo Pine and stored for the company that created the demo, that the company decides how it is used, and a link to the relevant section of our Privacy Policy. That notice is a factual disclosure about where the data goes. It is not your privacy notice and it does not obtain consent on your behalf, and it does not reduce your obligations under this Section. Submissions are stored in the Workspace, not against the author, and are collected whether or not the demo is published. On plans that include full analytics, they are readable and exportable by any Member of that Workspace, down to a read-only viewer (Section 5.3).

10.5 Other people's products. Demo Pine is commonly used to record software the recorder does not own. That is a decision you make and a risk you take. You are responsible for complying with the terms of service, license, and confidentiality obligations attaching to any product, site, or system you record, and for any trademark, trade dress, or copyright implications of showing another company's interface.

10.6 We rely on this. Sections 10.1 through 10.5 are material to our agreement to provide the Service, and are backed by your indemnity in Section 27.

11. Acceptable Use Policy

This Acceptable Use Policy applies to everyone who uses the Service, including your Members and anyone acting through your account. Violating it is a material breach of these Terms.

11.1 Content and rights. You must not:

1. capture, upload, publish, or distribute content you do not have the right to capture, upload, publish, or distribute;
2. infringe any copyright, trademark, patent, trade secret, moral right, right of publicity, or other intellectual property or proprietary right;
3. record or publish another party's confidential, proprietary, or trade-secret information without authorization;
4. record or publish a third party's product, system, or website where doing so violates that party's terms of service, license, or an agreement you are bound by;
5. remove, obscure, or circumvent Demo Pine attribution while on a plan that requires it, or circumvent any plan limit, entitlement check, metering, or access control — including by using the anonymous share path (Section 12.5) to publish beyond your plan's limits. Paid cosmetics, including removal of the attribution badge, are now stripped from an anonymous share automatically (Section 12.5); attempting to defeat that stripping is itself a breach of this item.

11.2 Privacy and personal data. You must not:

1. capture, store, or publish personal data about any person without a lawful basis and any notice or consent the law requires;
2. capture or publish another person's credentials, authentication codes, security questions, API keys, or session tokens;
3. use lead capture, analytics, or any other feature to build profiles of, track, or surveil individuals in a way that violates law;
4. enable lead capture without giving the people who fill it in accurate information about who receives their details and why.

11.3 Regulated and sensitive data. You must not put any of the following into the Service — whether by capture, upload, import, or lead-capture form — unless we have agreed in a signed writing:

1. protected health information subject to HIPAA or comparable health-privacy law;
2. consumer health data as defined by the Washington My Health My Data Act, Nevada SB 370, or comparable state law, including inferences about a person's health status, diagnoses, treatments, medications, reproductive or gender-affirming care, or precise location near a facility providing healthcare services;
3. payment card numbers, full magnetic-stripe data, CVV/CVC values, or other cardholder data subject to PCI DSS;
4. bank account, routing, or other financial account numbers;
5. government-issued identifiers such as Social Security, passport, or national ID numbers;
6. biometric identifiers, genetic information, precise geolocation of identifiable individuals, or special-category data under GDPR Article 9;
7. personal information of a child below the applicable age of digital consent in the child's jurisdiction, where you do not hold verifiable parental consent covering that processing;
8. classified, export-controlled, or ITAR-controlled information.

11.4 Security and integrity. You must not:

1. upload, host, link to, or distribute malware, ransomware, spyware, or any malicious or destructive code;
2. probe, scan, or test the vulnerability of the Service, or breach or circumvent any authentication, rate limit, entitlement gate, or security measure, except under a written authorization from us;
3. access another Workspace's data, or attempt to enumerate, guess, or brute-force Share Link codes, media URLs, invitation tokens, or API tokens;
4. interfere with or disrupt the Service, including by generating load designed to degrade it, or by evading rate limits;
5. reverse engineer, decompile, or disassemble any part of the Service, or attempt to derive its source code, except to the extent that restriction is unenforceable under applicable law;
6. use our Confidential Information, or access obtained under these Terms, to develop a product or service that is substantially similar to or competitive with the Service; or publish a benchmark or performance comparison of the Service that is materially inaccurate, that was not produced using the Service's documented functionality under normal conditions, or that we have not been given a reasonable opportunity to review for factual accuracy at least ten business days before publication. We will not unreasonably withhold consent, and nothing in this item prevents good-faith factual comparison of publicly available features and pricing.

11.5 Deception, abuse, and unlawful use. You must not use the Service to:

1. phish, spoof, or impersonate any person or organization, or misrepresent your affiliation with anyone — including by building a demo that imitates another company's login page, bank, or account portal in order to deceive;
2. create fake or misleading records, receipts, statements, invoices, credentials, or reviews presented as genuine;
3. run a scam, fraud, or deceptive commercial practice, or facilitate one;
4. send spam or unsolicited bulk email, including by abusing the invitation feature;
5. publish content that is defamatory, harassing, threatening, hateful, or that promotes violence or self-harm;
6. publish sexually explicit material, or content that sexualizes minors in any way;
7. distribute content that is illegal in the jurisdictions where it is made available, or that violates export, sanctions, or anti-corruption law.

11.6 The brand scanner. You must not:

1. use the brand scanner against a website you do not own or are not authorized to scan — other than the automatic scan of your own email domain that the Service performs when you create a brand kit, which you authorize by signing up with that address (see Section 15.1);
2. use the scanner as a general-purpose crawler, scraper, or data-harvesting tool;
3. use the scanner in violation of the target site's terms of service (see Section 15.3 on robots directives);
4. attempt to use the scanner to reach a host you are not authorized to reach, including internal, private, loopback, or link-local network addresses, or to circumvent its rate limits;
5. use logos, marks, or images retrieved by the scanner in a way you are not licensed to.

11.7 The extension. You must not use the Demo Pine Capture extension to record any page you are not authorized to record, including another person's account, another organization's internal systems, or a page you have accessed without permission.

11.8 Automation and volume. You must not use bots, scrapers, or automated means to access the Service other than through documented interfaces, or generate volumes of API calls, AI generations, uploads, or analytics events that are disproportionate to normal use of a product-demo tool.

11.9 Enforcement. We may investigate suspected violations, remove or disable content, throttle or suspend accounts or Workspaces, and terminate for cause under Section 22. Where Section 29.2 applies, we will give a statement of reasons. We may report unlawful activity to law enforcement. Report violations to [email protected].

12. Publishing, share links, and public access

12.1 What "private" means here — please read. A demo is not listed, indexed, or playable as a demo outside your Workspace until you publish it, and the media files behind it are no longer served from a public domain.

🔐 Media files are served by signed URLs that expire. Screenshots, screen recordings, audio, and HTML captures are stored in a private bucket. Every read goes through a URL we sign for the requester, and that URL stops working one (1) hour after we issue it; the app refreshes URLs before they expire as you work. Stored files are marked private, and the API responses that carry signed URLs are returned with cache-control: private, no-store, so browsers and intermediaries do not keep copies of them. A published demo never fetches this bucket at all — publishing embeds the media bytes directly into the published payload. Two limits you should understand. 1. A signed URL is still a bearer token for its lifetime. Anyone who obtains one within its one-hour window — from a browser's network tab, a HAR file, a proxy log, an extension, or a shared screen — can fetch that one file until it expires. It is a short window, not a permission check on the person using it. 2. URLs issued before this change are still public and non-expiring. Media URLs previously handed out on the public media domain (media.demopine.com) remain readable until we detach that domain at our content-delivery provider. That is an operational step we have not yet completed, and it is a deployment action rather than a code change. Until we complete it, treat any media URL already in circulation as permanently live. Use the blur and redaction tools before you capture, or capture synthetic data. Do not capture anything you could not tolerate becoming public.

12.2 Publishing. Publishing a demo creates a Share Link at app.demopine.com/s/<code>.

🔗 A Share Link is a public URL. Anyone who has it can view the demo. There is no password, no email gate, no domain restriction, and no view limit, and a link created from a signed-in Workspace does not time out on its own for as long as the demo stays published. A link created without signing in is capped at 180 days — see Section 12.5. The only protection is that the 12-character code is hard to guess. If the link is forwarded, pasted into a chat, posted on a website, or leaked through a browser referrer header, anyone who receives it can open the demo and see every screenshot, recording, and HTML capture inside it. You can take a link down at any time. Unpublishing or deleting the demo revokes it immediately, and revoked links are permanently dead — see Section 12.4. Revocation is the control here; the absence of an automatic timer is not. Share pages are not currently blocked from search engines. A Share Link that appears anywhere public may be crawled, indexed, and cached by search engines and other services outside our control. Do not publish a demo containing anything you are not willing to make public.

12.3 You are responsible for what you publish. We are not responsible for the consequences of your decision to publish, for who obtains a Share Link, or for what anyone does with a published demo. Publishing is an act of publication by you.

12.4 Taking a demo down.

✅ Unpublishing a demo revokes its Share Links — and so does deleting the demo. Either action marks every Share Link minted from that demo as revoked in the same database transaction that unpublishes or deletes it, so there is no moment at which the demo is gone but a link is still live. The published payload is then purged from storage. You no longer need to unpublish before deleting. A revoked link is dead immediately and permanently. When someone opens a Share Link, we check the link's record before we read any stored copy, so a revoked, expired, or unknown code returns "This demo is no longer available" even if a stored copy survived a failed cleanup. The same revocation runs on every path by which a demo can disappear — including deletion of the Workspace or of a Demo Pine account — because it is enforced at the database level rather than only in the code that handles a delete request. This also reaches a Share Link created without signing in that was minted from the demo you deleted. Revoked codes are kept as tombstones so that a retired code is never handed out a second time and an old link can never end up playing a different demo. The tombstones themselves are removed on the schedule in Section 23.3. A backstop, not the mechanism. If you ever find a published copy still reachable after you unpublished or deleted it, email [email protected] with the full /s/<code> URL and we will disable it within one (1) business day and confirm in writing. This commitment is in addition to, and does not limit, your rights under data-protection law.

12.5 Anonymous shares.

⚠️ A Share Link created without signing in still cannot be managed or revoked by you from the app. The Service permits a Share Link to be created without an account. Because such a link is attached to no account and no Workspace, creating an account later, or deleting an account, does not reach it. The one self-service path that does reach it is Section 12.4: if the link was minted from a demo that you later delete from a Workspace, the delete revokes it. Two things now bound how long an unreachable anonymous link lives. A hard 180-day cap applies to every Share Link created without an account, after which the link and its stored payload are removed — see the retention schedule in Section 23.3, including the disclosure that the job enforcing it currently runs in dry-run mode and deletes nothing yet. And if you need one taken down sooner, email [email protected] with the full /s/<code> URL and we will remove it within one (1) business day.

Anyone creating an anonymous share is bound by these Terms, including the Acceptable Use Policy. Anonymous shares are not subject to the plan check on how many demos you may publish at once; using them to publish beyond your plan's limits violates Section 11.1(5). Paid cosmetics are stripped from an anonymous share when it is created — the attribution badge is forced on, and a custom accent color and custom logo are removed — so an anonymous demo always carries the Demo Pine badge. We may remove anonymous shares at any time, for any reason or no reason.

12.6 Viewers and viewer analytics. People who open your Share Link are your audience, not our customers. Playback generates analytics for you as described in our Privacy Policy.

Demo Pine's viewer analytics do not set cookies and do not store any persistent or cross-demo identifier on a viewer's device. A playback session identifier is generated in memory and is not written to cookies or browser storage; no viewer IP address is stored with analytics; the only contextual fields recorded are a coarse device class, the host name of the referring page, and a country code supplied by our content-delivery provider. This means the analytics we provide by default do not store or access information on the viewer's terminal equipment in the way that triggers the consent requirement under the ePrivacy Directive or PECR.

If you add your own tracking, embed our player in a page that sets cookies, or enable a lead-capture form, you are responsible for any notice and consent those viewers are owed. Lead-capture forms collect personal data directly from the viewer and always require you to provide notice and any consent the law requires.

13. AI features

13.1 What the AI features do. Demo Pine offers AI-assisted copywriting — step names, tooltips, captions, and rewrites. When you use the built-in AI, the text you supply and, for image-aware modes, the relevant demo screenshot are transmitted to our third-party model provider to generate a response.

We do not retain your prompts, the screenshot, or the generated output on our systems. We retain only metering records: the Workspace and the user who made the request, the mode, the model, the token counts, and the timestamp. Our model provider is named in the sub-processor list referenced in Section 16.1; that provider may retain inputs for a limited period for abuse monitoring, as described there.

13.2 AI output is not guaranteed — please read.

🤖 AI output may be wrong. Generated text can be inaccurate, incomplete, misleading, biased, out of date, or unsuitable for your purpose, and identical or similar output may be generated for other users. You are solely responsible for reviewing, editing, verifying, and approving any AI output before you use or publish it. Do not rely on AI output as legal, financial, medical, or professional advice. AI features are provided without warranty of any kind, and Sections 25 and 26 apply to them in full.

13.3 Credits and metering. On the Free plan, AI generations are metered at 200 credits per month, reset on the Workspace's monthly metering window; one generation costs one credit. A credit is reserved when a generation starts and is returned automatically if the generation fails or is declined. Paid plans are not metered against a fixed allowance, subject to the fair-use threshold in the footnote to Section 6.2 — we may throttle, queue, or suspend AI access where consumption is automated, abusive, or extraordinary, or where our model provider limits us. Credits have no cash value, do not roll over, and are not refundable.

13.4 Bring-your-own-key. You may optionally supply your own model-provider API key. This is an optional convenience feature and is treated as a Beta feature under Section 17. If you use it:

• your key is stored in your own browser's local storage, in plain text, and is never sent to Demo Pine's servers;
• your requests, including any screenshots, go directly from your browser to your provider, never through us;
• your agreement with that provider governs that traffic, including how they handle and retain your content and what they charge you;
• we have no visibility into, control over, or responsibility for those requests, their content, their cost, or their output.

⚠️ You acknowledge that storing a credential in browser local storage carries material risk, including that any script running on the page, any browser extension with access to this site, and anyone with access to your browser profile or device can read it. We recommend you use a key scoped to the minimum permissions your provider allows, set a spending cap with your provider, and rotate it regularly. You are solely responsible for all charges your provider bills you. To the maximum extent permitted by law, we have no liability arising from your use of the bring-your-own-key path, and this exclusion is a condition of our making the feature available.

13.5 No training on your content. We do not use Customer Content to train models. Our built-in AI feature is provided through a commercial model-provider API whose terms, as of the Last-updated date at the top of this document, do not permit the provider to train on inputs and outputs submitted through it. We will update this Section if that changes. If we change providers under Section 13.6, we will use only a provider under equivalent terms, and we will update the sub-processor list before the change takes effect. This commitment does not extend to the bring-your-own-key path, where your own provider agreement controls.

13.6 Model changes. We may change, replace, or discontinue the underlying model or the AI features at any time, subject to Sections 13.5 and 16.4.

13.7 AI transparency. Where the EU AI Act or comparable law applies to your use, you are responsible for disclosing to your viewers that content in your demo was generated or materially modified using AI, where that disclosure is required of you as a deployer. We will make available any machine-readable marking of AI-generated output that we are required to provide as a downstream provider.

14. The Demo Pine Capture Chrome extension

14.1 License. Subject to these Terms, we grant you a limited, revocable, non-exclusive, non-transferable, non-sublicensable license to install and use the Demo Pine Capture extension on browsers you control, solely to create demos in the Service. All rights not expressly granted are reserved. You may not modify, redistribute, repackage, or reverse engineer the extension except as Section 11.4(22) allows.

14.2 Chrome Web Store terms also apply. If you install the extension from the Chrome Web Store, Google's terms and the Chrome Web Store's terms apply to that distribution in addition to these Terms. Google is not a party to these Terms and has no responsibility for the extension.

14.3 What it can access. The extension requests broad browser permissions — including access to all URLs, tab information, scripting, and tab capture — because you may need to record your product on any domain. This means the extension is technically capable of reading the URL and title of your tabs and capturing the visible contents of any page you record. Use it only on pages you are authorized to record (Section 11.7).

14.4 Where captures go. The extension makes no network requests of its own and sends nothing to any third party. However, when you stop a recording, the extension opens the Demo Pine app and hands the capture over automatically, and — if you are signed in — the capture is uploaded to our hosted storage without a separate confirmation step. Assume that stopping a recording uploads what you recorded. The destination application URL is user-configurable in the extension; if you change it, your captures are handed to whatever origin you configure, and you are responsible for that choice.

14.5 Updates. The extension may update automatically. We may change or discontinue it, or any of its features, at any time.

15. The brand scanner

15.1 What it does. When you supply a website URL — or when a URL is derived automatically from your email domain (for example, signing up as [email protected] produces https://acme.com) — the Service fetches that website from our servers and reads its publicly available HTML, stylesheets, scripts, and images in order to extract colors and logo candidates for your brand kit. It follows redirects and may make a limited number of additional requests for stylesheets, script bundles, and common logo paths on the same site. Our servers' requests will appear in the target website's logs.

If you do not want us to scan your email domain, skip the brand-kit step or clear the URL before scanning.

15.2 Your responsibility. You represent that you own the site you scan or are authorized to scan it, and that you are entitled to use any logo, mark, color, or asset the scanner retrieves. See Section 11.6. The scanner does not evaluate whether a retrieved logo is licensed to you; that is your responsibility.

15.3 What the scanner does not do. So that you can assess it accurately: the scanner sends a desktop browser user-agent string carrying the identifier DemoPineBrandScanner; it does not currently evaluate robots.txt or robots meta directives; it does not execute scripts on the target site; and it applies size and time limits to each fetch. We disclose this rather than claim behavior the software does not implement.

15.4 No IP license. Nothing the scanner retrieves grants you any right in a third party's trademarks, logos, or copyrighted material.

16. Third-party services and sub-processors

16.1 Providers we use. The Service depends on third-party providers for application hosting, database, object storage, content delivery, payments, transactional email, federated sign-in, and AI. A current list of the sub-processors that process Customer Content, and the categories of data each receives, is maintained in our Privacy Policy and at https://demopine.com/subprocessors.

16.2 General authorization. You give us general written authorization to engage the sub-processors on that list. We remain responsible for our sub-processors' performance of our obligations under these Terms and the DPA.

16.3 Notice of changes. We will give at least 30 days' notice before adding or replacing a sub-processor that processes Customer Content, by email to Workspace owners and by an update to the sub-processor page, where you can subscribe to change notifications.

16.4 Your right to object. If you reasonably object to a new sub-processor on data-protection grounds within that 30-day period, we will work with you in good faith to offer an alternative. If we cannot, you may terminate the affected subscription and we will refund the prepaid fees allocable to the remainder of your then-current term, calculated on a straight-line daily basis. This is an exception to Section 6.11.

16.5 Services you connect. If you connect your own identity provider, directory, or other third-party service to a Workspace, you are responsible for that service, for the data it sends us, and for your agreement with that provider. That provider is your sub-processor, not ours.

16.6 Third-party sites and content. The Service may link to or interoperate with third-party websites and services. We do not control them, do not endorse them, and are not responsible for them. Your dealings with them are between you and them.

17. Beta and early-access features

We may offer features labeled beta, preview, early access, experimental, or similar — including the bring-your-own-key AI path (Section 13.4). Beta features are provided "as is" and "as available," without any warranty, support obligation, or availability commitment, may be changed or withdrawn at any time without notice, may lose data, and are excluded from any service-level commitment. Do not use a beta feature for anything you cannot afford to lose. If we designate a beta feature as confidential, Section 19 applies to it.

18. Privacy, data protection, and security

18.1 Privacy Policy. Our Privacy Policy describes what personal data we collect, how we use it, who we share it with, and what choices you have. It is part of these Terms.

18.2 Roles. For account data — your name, email, session records (which include the IP address and browser user agent of a signed-in session), billing contact, and usage — Demo Pine is the controller. For Customer Content and the data inside it — captured screens, HTML captures, demo viewer analytics, lead submissions, and Member directory records pushed to us by your identity provider or directory — you are the controller and Demo Pine is your processor, processing on your documented instructions.

18.3 Data Processing Addendum — automatic, no signature required. Our Data Processing Addendum at https://demopine.com/dpa is incorporated into these Terms and applies automatically, without signature, to all processing of Customer Content where you are subject to the GDPR, UK GDPR, Swiss FADP, or a US state privacy law. It includes:

• the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914, Module Two, controller-to-processor);
• the UK International Data Transfer Addendum (version B1.0); and
• the Swiss addendum,

each of which takes effect automatically for transfers from those jurisdictions. The DPA carries the content required by GDPR Article 28(3), including subject matter and duration, nature and purpose, types of personal data and categories of data subjects, processing only on documented instructions, confidentiality undertakings, Article 32 security measures, sub-processor terms, assistance with data-subject requests and with Articles 32–36, deletion or return at the end of the term, and audit and information rights. If you require a countersigned copy, request one at [email protected].

18.4 US state privacy — service provider terms. For personal information subject to the CCPA/CPRA or a comparable US state privacy law, you are the business or controller and we are the service provider or processor. We will: process personal information only to perform the services specified in these Terms and your order, and for no other purpose; not sell or share personal information as those terms are defined by the CCPA/CPRA; not retain, use, or disclose personal information outside the direct business relationship with you or for any commercial purpose other than the specified business purposes; not combine personal information received from you with personal information received from another source, except as permitted by Cal. Civ. Code § 1798.140(ag)(1) and applicable regulations; comply with the obligations applicable to service providers and provide the same level of privacy protection required of you; notify you promptly if we determine we can no longer meet these obligations; and permit you to take reasonable and appropriate steps to stop and remediate unauthorized use. We certify that we understand and will comply with these restrictions. We do not sell or share personal information.

18.5 Data subject requests. If a demo viewer, lead submitter, or other individual asks us to access or delete data that is inside your Workspace, we will, where lawful, refer them to you and assist you in responding, rather than acting unilaterally. You are responsible for responding as controller.

18.6 Security. We use reasonable technical and organizational measures appropriate to a service of this size — including passwords stored only as salted hashes, server-side password-strength enforcement, encrypted transport, workspace-scoped access controls, hashed-only storage of SCIM and invitation tokens, and revocation of all other sessions on password reset. We maintain a written information security program and review it at least annually.

We do not currently hold SOC 2, ISO 27001, HIPAA, or PCI DSS certification, and we make no representation that we do.

Two facts we disclose here so you can decide what to put into the Service. First, we do not currently verify email addresses at sign-up (Section 4.2). Second, media files are stored in a private bucket and served only by signed URLs that expire after one hour — but media URLs issued before that change are still public and non-expiring, and remain so until we detach the public media domain at our content-delivery provider, which we have not yet done (Section 12.1). No system is perfectly secure, and we do not guarantee that the Service cannot be compromised.

18.7 Security incidents. If we become aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, or unauthorized disclosure of or access to Customer Content, we will notify the affected Workspace owners and billing contacts without undue delay and in any event within 72 hours of becoming aware. Our notice will describe the nature of the incident, the categories and approximate volume of data and individuals affected so far as known, the likely consequences, the measures we have taken or propose to take, and a contact point. We will provide reasonable assistance so you can meet your own notification obligations. We will not delay notice because an investigation is incomplete, and our notice is not an admission of fault.

18.8 Government and legal requests. If we receive a subpoena, warrant, court order, or other legal or governmental demand for Customer Content, we will notify the affected Workspace owner before disclosing, and give you a reasonable opportunity to seek protective relief, unless we are legally prohibited from doing so or we reasonably believe there is a risk of death or serious physical harm. Where prohibited, we will seek a waiver of the prohibition and will notify you as soon as we lawfully can. We will review each demand for validity and scope, will disclose only the narrowest set of data responsive to a valid demand, and will challenge demands we reasonably consider unlawful, overbroad, or inconsistent with the GDPR or the Standard Contractual Clauses. We will redirect requests directed at Customer Content to you where we lawfully can.

18.9 Data in your browser. Some data is stored on your own device — including local copies of demos and captured media in your browser's storage, your brand kit, your theme preference, and any model-provider API key you supply. That local data is not cleared when you sign out or delete your account. You control it and can clear it through your browser's settings.

19. Confidentiality

19.1 What is confidential. "Confidential Information" means non-public information disclosed by one party to the other that is designated as confidential, or that a reasonable person would understand to be confidential given its nature and the circumstances. Your Customer Content is your Confidential Information. Our non-public product, roadmap, and security information, and the terms of any order form, are our Confidential Information.

19.2 Obligations. Each party will use the other's Confidential Information only to perform under these Terms, will protect it with at least reasonable care, and will disclose it only to personnel, Affiliates, and subcontractors who need it and who are bound by confidentiality obligations no less protective than these.

19.3 Exclusions. These obligations do not apply to information that is or becomes public through no fault of the recipient, was rightfully known to the recipient before disclosure, is rightfully received from a third party without restriction, or is independently developed without use of the Confidential Information.

19.4 Compelled disclosure. A party may disclose Confidential Information where legally compelled, provided it gives prompt notice where lawful (see Section 18.8) and reasonable assistance in seeking protective treatment.

19.5 Duration. These obligations survive for three years after termination, and indefinitely for information that qualifies as a trade secret.

20. Feedback

If you send us ideas, suggestions, feature requests, or other feedback, you grant us a perpetual, irrevocable, worldwide, royalty-free, sublicensable license to use it for any purpose without obligation, attribution, or compensation. Do not send us feedback you consider confidential or proprietary; feedback is excluded from Section 19.

21. Our intellectual property

21.1 We own the Service. The Service — including the application, the extension, the player, our source code, designs, Documentation, and the "Demo Pine," "DemoPine," and RyanTech marks and logos — is owned by RyanTech LLC and is protected by intellectual property law. Except for the limited rights expressly granted in these Terms, you receive no rights in it.

21.2 Your license to use it. Subject to these Terms and your payment of applicable fees, we grant you a limited, revocable, non-exclusive, non-transferable, non-sublicensable right to access and use the Service for your internal business purposes during your subscription term.

21.3 Our marks. You may not use our name, logos, or marks without our prior written permission, except to accurately refer to the Service, and except for attribution required under Section 7.2.

21.4 Aggregated data. You instruct us, as part of your documented instructions under Section 18.2, to generate aggregated and de-identified statistics from Service usage — for example counts of demos published, playback rates, and feature adoption — and to use them to operate, secure, troubleshoot, analyze, and improve the Service. We generate this data only where the aggregation is applied to the exclusion of any personal data, using measures that reasonably prevent reidentification. We will not attempt to reidentify it, will contractually obligate any recipient to the same, and will never publish it in a form that identifies you, your Members, your viewers, or your Customer Content. We do not derive statistics from the contents of your screen captures, HTML captures, audio, or lead submissions.

22. Suspension and termination

22.1 Termination by you. You may stop using the Service at any time. To cancel a paid subscription, use the Billing page (app.demopine.com/billing; Section 6.5). To delete your account entirely, use the Danger Zone on the Account page — read Section 5.8 first for what that does to a Workspace you share and to a Workspace that is solely yours. We will refuse the deletion while a Workspace that is solely yours still has a live paid subscription; cancel on the Billing page first (Section 6.12).

22.1a Termination by you for cause. You may terminate your subscription immediately on written notice if we materially breach these Terms and fail to cure the breach within 30 days after you notify us at [email protected]. If you terminate under this Section, we will refund the prepaid fees allocable to the remainder of your then-current term, calculated on a straight-line daily basis. This is an exception to Section 6.11.

22.2 Termination and suspension by us for cause. We may suspend or terminate your access to all or part of the Service, immediately and without prior notice where we reasonably consider it necessary, if:

1. you materially breach these Terms, including the Acceptable Use Policy;
2. your payment is more than 30 days overdue after the grace period in Section 6.9;
3. your use creates a security, legal, or operational risk to us, to other users, or to third parties;
4. we are required to do so by law, court order, or a governmental or regulatory authority;
5. you are, or become, subject to sanctions or are located in an embargoed jurisdiction (Section 33.9);
6. you are a repeat infringer under Section 24.6;
7. you use the Service in a way that materially disrupts it.

Where the breach is curable and immediate action is not required, we will give you notice and a reasonable opportunity to cure. A pending card dispute is not a ground for suspension or termination (Section 6.13). Where Section 29.2 applies, we will give a statement of reasons.

22.3 Termination by us for convenience. We may terminate a Free account, or discontinue the Service generally, on 30 days' notice. If we discontinue the Service for a paid Workspace mid-term other than for cause, we will refund the unused prepaid portion of the current term, which is your sole remedy for that discontinuation. This is an exception to Section 6.11.

22.4 Effect of termination. On termination, your right to access the Service ends immediately, subject to the export window in Section 23.1. Any fees already incurred remain payable and, subject to Section 6.11.1, are not refunded. The provisions listed in Section 33.13 survive.

23. What happens to your data after termination

23.1 Export window. After a paid subscription ends or is terminated for any reason, we will keep your Customer Content available for export for 30 days, during which you may retrieve it. We will provide this export window even where we terminated your account for cause, except where providing it would violate applicable law, a court order, or sanctions obligations, or where the content itself is unlawful — in which case we will export everything we lawfully can. If we suspended your access before termination, we will restore export-only access for that 30-day period on request. Export before you delete anything — we cannot recover deleted content. Note that the retention schedule in Section 23.3 runs independently of this window: a category that has reached its period is deleted on schedule whether or not you have exported it.

23.2 How to export. The Service provides per-demo export of a bundle containing the demo and all of its media, and CSV export of analytics events and lead records on plans that include CSV export. There is no single "download everything about my account" archive today. If you need one, contact [email protected] and we will assemble it manually within a reasonable time and, for customers covered by Section 29.3, within the timescales that Section requires.

23.3 The retention schedule. We retain Customer Content until you delete it or we delete it. In addition, we operate a published retention schedule: a sweeper that runs daily at 03:20 UTC and removes data in each category below once it passes the stated age, measured from the clock named in the table. It writes an audit record for every run once it is out of dry-run.

⚠️ The sweeper currently ships in dry-run mode. It counts what it would remove, reports that to our application logs, and deletes nothing. No audit record is written until we switch it out of dry-run. It begins deleting only when we switch it out of dry-run. Until then, read the periods below as our commitment about what we will delete and when, not as a description of deletions that have already occurred. We disclose this rather than describe the finished state.

Four notes on that table.

1. The payment-processor row is a redaction, not a deletion. We overwrite the stored webhook payload — which is what holds a billing contact's name, email address, and billing address — but keep the record itself, because it is the idempotency key that stops an old webhook being replayed against your account.
2. The AI-metering rows are two steps. At 90 days the record's link to a named person is removed; the org-level counter survives for billing disputes until the 400-day deletion.
3. The Free plan's 30-day analytics window (Section 6.2) is a display limit, not a retention limit. A Workspace that upgrades still sees its earlier history, up to the 400-day period above.
4. The two rows marked "Off" ship disabled and delete nothing until we deliberately enable them. Enabling the invoice and payment row is an accounting decision, not an engineering one.

Deletion is not instantaneous, and deleted data may persist in our providers' backups and logs for a limited period until those are overwritten in the ordinary course. Some records are retained regardless of the above — see Section 23.4. We may change these periods; a change is published in this Section.

23.4 What we keep. Notwithstanding deletion, we retain records we are required or entitled to keep, including billing and tax records, invoices, payment records, raw payment-processor event records (which may include your billing name, email address, and billing address), and records needed to establish, exercise, or defend legal claims. Password-reset and similar verification records tied to your user are now deleted when your account is deleted, together with any verification record that has already expired. Workspace invitations are records of the Workspace rather than of your account, so an invitation you sent is not removed by your account deletion; it is removed 90 days after it is accepted, revoked, or expires, under Section 23.3. Our Privacy Policy describes this in detail, including the categories of data that survive account deletion. Where you exercise an erasure right, we satisfy it by deleting or de-identifying the personal data we hold about you, not by destroying the Customer's business records.

23.5 Anonymous shares. A Share Link created without an account is not reachable by account deletion or by any other self-service deletion path, unless it was minted from a demo you later delete from a Workspace (Section 12.4). It is otherwise bounded only by the 180-day cap in Section 23.3 — subject to the dry-run disclosure there — and by our removing it on request. See Section 12.5; email [email protected] to have one removed.

23.6 Local copies. Deleting your account does not remove local copies stored in your own browser (Section 18.9), and does not remove copies your Members or viewers have downloaded.

23.7 Duplicated content. If another Member duplicated your demo, that duplicate is a separate copy owned by the Workspace and is not removed when your original or your account is deleted.

24. Copyright and DMCA policy

24.1 Our policy. We respect intellectual property rights and respond to valid notices under the Digital Millennium Copyright Act, 17 U.S.C. § 512.

24.2 Designated agent. Our designated agent to receive notifications of claimed infringement is registered with the United States Copyright Office in the DMCA Designated Agent Directory at https://dmca.copyright.gov, under RyanTech LLC, doing business as DemoPine. Send notices to:

DMCA Designated Agent
RyanTech LLC (d/b/a DemoPine / Demo Pine)
2764 Pleasant Road, Suite A #599, Fort Mill, SC 29708, USA Email: [email protected]

This designation is also published at demopine.com/dmca, as 17 U.S.C. § 512(c)(2) requires it to be available through the service itself.

24.3 What a notice must contain. To be effective under 17 U.S.C. § 512(c)(3), your notice must include:

1. a physical or electronic signature of the copyright owner or a person authorized to act on their behalf;
2. identification of the copyrighted work claimed to have been infringed;
3. identification of the material claimed to be infringing and information reasonably sufficient to let us locate it — for a Demo Pine demo, please include the full Share Link URL;
4. your contact information, including address, telephone number, and email address;
5. a statement that you have a good-faith belief that the use is not authorized by the copyright owner, its agent, or the law;
6. a statement, made under penalty of perjury, that the information in the notice is accurate and that you are the copyright owner or authorized to act on the owner's behalf.

24.4 Misrepresentation. Under 17 U.S.C. § 512(f), anyone who knowingly materially misrepresents that material is infringing, or was removed by mistake, may be liable for damages. Consider consulting a lawyer before sending a notice.

24.5 Counter-notice. If your content was removed and you believe that was a mistake or misidentification, you may send a counter-notice to the agent above containing: your signature; identification of the removed material and where it appeared; a statement under penalty of perjury that you have a good-faith belief the removal resulted from mistake or misidentification; your name, address, and telephone number; and a statement that you consent to the jurisdiction of the federal district court for the district in which your address is located — or, if your address is outside the United States, the District of South Carolina — and that you will accept service of process from the complaining party.

24.6 Repeat infringers. We maintain and reasonably implement a policy of terminating, in appropriate circumstances, the accounts of repeat infringers. We record each notice we act on against the account that published the material. An account that accumulates three separate instances of material removed in response to a valid, uncontested notice within any twelve-month period will be terminated, and we may terminate sooner where the infringement is flagrant. We also accommodate standard technical measures as defined in 17 U.S.C. § 512(i)(2).

24.7 Notice to you, and forwarding of counter-notices. When we remove or disable material in response to a notice, we will promptly notify the account that published it and provide a copy of the notice. If we receive a valid counter-notice, we will promptly forward a copy to the complaining party and inform them that we will restore the material in 10–14 business days unless they notify us that they have filed an action seeking a court order.

25. Disclaimers

25.1 As is.

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE," WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED BY LAW, RYANTECH LLC AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESS, IMPLIED, STATUTORY, AND OTHERWISE, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, QUIET ENJOYMENT, ACCURACY, AND NON-INFRINGEMENT, AND ANY WARRANTIES ARISING FROM COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

25.2 No availability commitment. We do not commit to any level of uptime, availability, or performance, and we do not offer a service-level agreement or service credits, except where an Enterprise order form or MSA signed by both parties expressly provides one. The Service may be unavailable for maintenance, upgrades, provider outages, or reasons outside our control.

25.3 Specifically, we do not warrant that: the Service will be uninterrupted, timely, secure, or error-free; defects will be corrected; the Service or its servers are free of harmful components; results obtained from the Service will be accurate or reliable; AI output will be correct or fit for your purpose; Customer Content will not be lost or corrupted; or that a Share Link or a media URL will remain unavailable to anyone you did not intend to give it to.

25.4 Your responsibility to back up. Maintain your own copies of anything you cannot afford to lose. Export important demos regularly. We are not a backup service.

25.5 No professional advice. Nothing in the Service or its output is legal, financial, tax, medical, or other professional advice.

25.6 Statutory rights. Some jurisdictions do not allow the exclusion of certain warranties. To the extent an exclusion above is prohibited, it does not apply to you and the remaining exclusions still apply. Nothing in these Terms limits any non-waivable statutory right you have as a consumer.

26. Limitation of liability

26.1 Exclusion of indirect damages.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, RYANTECH LLC AND ITS OFFICERS, MEMBERS, EMPLOYEES, CONTRACTORS, AND SUPPLIERS WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, GOODWILL, BUSINESS OPPORTUNITY, OR ANTICIPATED SAVINGS, OR FOR ANY LOSS, CORRUPTION, OR UNAUTHORIZED DISCLOSURE OF DATA OR CONTENT, OR FOR BUSINESS INTERRUPTION OR COST OF SUBSTITUTE SERVICES — WHETHER BASED IN CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, OR ANY OTHER THEORY, AND EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

26.2 Cap on total liability.

OUR TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THESE TERMS OR THE SERVICE WILL NOT EXCEED THE GREATER OF (A) THE TOTAL FEES YOU ACTUALLY PAID US FOR THE SERVICE IN THE TWELVE (12) MONTHS IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM, OR (B) ONE HUNDRED US DOLLARS ($100). IF YOU USE THE SERVICE ON THE FREE PLAN, OUR TOTAL AGGREGATE LIABILITY WILL NOT EXCEED ONE HUNDRED US DOLLARS ($100).

26.3 What is not capped. Nothing in this Section limits liability that cannot be limited by law, including liability for fraud, fraudulent misrepresentation, death or personal injury caused by negligence, or gross negligence or willful misconduct. The caps in this Section do not apply to your payment obligations under Section 6, or to either party's indemnification obligations under Section 27 — except that our liability under the IP indemnity in Section 27.3 is capped at three (3) times the fees you paid us in the twelve (12) months preceding the claim.

26.4 Allocation of risk. The disclaimers in Section 25 and the limitations in this Section 26 are a fundamental part of the bargain between us and are reflected in our pricing. They apply even if a limited remedy fails of its essential purpose.

26.5 Time limit on claims. To the fullest extent permitted by law, any claim arising out of or relating to these Terms or the Service must be brought within one (1) year after the claim arose, or it is permanently barred. This limitation does not apply to any claim for which applicable law prohibits a contractually shortened limitations period, to claims under a statute providing its own non-waivable limitations period, or where you are a consumer resident in a jurisdiction that does not permit shortening. The period is tolled as provided in Section 30.1.

26.6 Statutory rights. Some jurisdictions do not allow the exclusion or limitation of certain damages. To the extent a limitation above is prohibited, it does not apply to you and the remaining limitations still apply.

27. Indemnification

27.1 Your indemnity. You will defend, indemnify, and hold harmless RyanTech LLC and its officers, members, employees, contractors, and agents from and against any third-party claim, demand, suit, proceeding, investigation, loss, liability, damage, fine, penalty, cost, or expense (including reasonable attorneys' fees) arising out of or relating to:

1. your Customer Content, including anything captured in a screenshot, screen recording, audio recording, or HTML capture;
2. your publication of a demo, or anyone's access to a Share Link or media URL you created;
3. your breach of these Terms, including the Acceptable Use Policy and the representations in Section 10;
4. your violation of any law or of any third party's intellectual property, privacy, publicity, confidentiality, or contractual rights;
5. any claim by, or regulatory proceeding concerning, a person whose personal data appears in your Customer Content, who submitted a lead-capture form on your demo, or who received an invitation you sent (including under CAN-SPAM, CASL, or the ePrivacy rules);
6. any claim by a third party whose product, website, or system you recorded or scanned;
7. your use of the bring-your-own-key AI path (Section 13.4);
8. any dispute between you and your Members, employer, contractor, client, or identity-provider administrator.

27.2 Consumers. If you are an individual using the Service for personal, family, or household purposes, Section 27.1 applies only to the extent permitted by applicable law, is limited to third-party claims arising from your Customer Content, your publication of a demo, or your intentional or negligent breach of these Terms, and does not require you to indemnify us for our own negligence or misconduct. Nothing in this Section limits any non-waivable statutory right you have as a consumer.

27.3 Our indemnity. We will defend you against any third-party claim alleging that the Service, as provided by us and used in accordance with these Terms, infringes that third party's United States patent, copyright, or trademark, or misappropriates its trade secret, and we will pay damages and costs finally awarded or agreed in settlement. This does not apply to claims arising from Customer Content, from your combination of the Service with anything we did not supply, from your modification of the Service, from use after we notify you to stop, or from Beta features. If the Service becomes, or we believe may become, subject to such a claim, we may procure the right to continue using it, modify it to be non-infringing, or terminate the affected subscription and refund prepaid unused fees. This Section states our entire liability and your exclusive remedy for third-party intellectual property claims, and is subject to the cap in Section 26.3.

27.4 Process. The indemnified party will promptly notify the indemnifying party of any claim; a failure to do so relieves the indemnifying party of its obligations only to the extent it is materially prejudiced. The indemnifying party has control of the defense with counsel reasonably acceptable to the other party, and the indemnified party will cooperate at the indemnifying party's expense. Neither party may settle a claim in a way that imposes any obligation or admission on the other without that party's prior written consent. The indemnified party may participate in the defense with its own counsel at its own expense.

28. Enterprise, SSO, SCIM, and order of precedence

28.1 Enterprise plans. Enterprise is sold through a signed contract, not self-serve checkout. Enterprise entitlements — including SAML single sign-on, SCIM 2.0 directory provisioning, security review, and any service-level commitment — are provisioned by us against that contract.

28.2 SSO. If you configure SAML single sign-on for a Workspace, you are responsible for your identity provider, its configuration, the certificates you upload, and the accuracy and lawfulness of the identity assertions it sends us. If you enable enforcement, password sign-in is refused for the email domains you claim. You represent and warrant that you are entitled to claim those domains. We do not currently verify domain control by DNS or any other automated means, so this representation is the only control on a domain claim; a false claim is a material breach. We may revoke a domain claim if we receive a credible competing claim, and will notify the affected Workspace owners. A first SSO sign-in automatically creates a Demo Pine account and a Workspace membership for the asserted user, and is not subject to the seat ceiling check (Section 5.5).

28.3 SCIM. If you connect a SCIM directory, you are responsible for your directory, for the SCIM bearer tokens you generate, and for the lawfulness of the personnel records you push to us. SCIM deprovisioning removes a person's membership in your Workspace. It does not delete their Demo Pine account or the demos they authored. To have a personal account deleted, the account holder must delete it (Section 22.1) — and should first read Section 5.8 — or you may request assistance at [email protected].

28.4 Order of precedence. If there is a conflict between documents, the following order controls, from highest to lowest:

1. a signed order form, master services agreement, or enterprise agreement between you and RyanTech LLC;
2. a signed data processing addendum, on the subject matter it covers;
3. the Data Processing Addendum at https://demopine.com/dpa, on the subject matter it covers;
4. these Terms;
5. the Privacy Policy;
6. any other Documentation, help content, or marketing material.

Marketing pages, feature comparison tables outside these Terms, blog posts, and help articles are not contractual commitments and do not modify these Terms. The feature table in Section 6.2 is part of these Terms and is contractual.

29. Regional terms

These terms apply in addition to the rest of these Terms where they are relevant to you. Where they conflict with another Section, they control for the customers they cover.

29.1 Consumers in the EEA and the United Kingdom — right of withdrawal

If you are a consumer resident in the EEA or the UK, you have the right to withdraw from your subscription within 14 days of entering into it, without giving a reason. To withdraw, tell us clearly at [email protected] — you may use the model withdrawal form at https://demopine.com/withdrawal, but you do not have to. If you withdraw, we will refund all payments received from you within 14 days using the same payment method.

By starting your subscription, you expressly request that we begin providing the Service immediately, and you acknowledge that you lose the right of withdrawal once the Service has been fully performed, and that if you withdraw after performance has begun you must pay an amount proportionate to what has been supplied up to the point of withdrawal. Nothing in Section 6.11 limits this right or any other mandatory statutory right you have as a consumer.

29.2 European Union — Digital Services Act

Points of contact. For EU Member State authorities, the European Commission, and the Board, our single point of contact is [email protected], in English. For recipients of the Service, our point of contact is [email protected].

Legal representative. Our designated legal representative in the Union under Article 13 of Regulation (EU) 2022/2065 is [[EU_REPRESENTATIVE]]. The same representative acts as our EU representative under Article 27 of the GDPR.

Notice and action. Anyone may notify us of content they consider illegal at [email protected], giving a sufficiently substantiated explanation of why it is illegal, the exact URL, their name and email address (not required for suspected child sexual abuse material or certain other offences), and a statement of good-faith belief that the information is accurate and complete. We will confirm receipt, decide in a timely, diligent, non-arbitrary, and objective manner, and inform the notifier of our decision and the redress available.

Statement of reasons. If we remove or disable Customer Content, suspend a Share Link, or suspend or terminate an account, we will give the affected user a statement of reasons identifying what was affected, the legal or contractual ground relied on, the facts relied on, whether automated means were used, and the redress available — including our internal complaints route at [email protected], out-of-court dispute settlement, and judicial remedy.

Moderation. We do not use automated content-moderation tooling on Customer Content. We act on notices and on our own detection of Acceptable Use Policy violations.

29.3 European Union — switching and egress (Data Act)

If you are established in the European Union, this Section applies and prevails over Section 23 to the extent of any conflict. You may terminate on 30 days' notice. On termination or on request, we will provide a 30-day transitional period, extendable once by written request for a proportionate further period, during which we will maintain your access and assist you in exporting all Customer Content and the exportable data generated by your use of the Service, in a structured, commonly used, and machine-readable format, at no charge. We will provide reasonable technical assistance and documentation to support migration to another provider or to your own environment, and we will not impose contractual, technical, or commercial obstacles to switching. At the end of the transitional period we will erase your Customer Content, subject to Section 23.4.

29.4 Consumers generally

Nothing in these Terms excludes or limits any right you have under mandatory consumer-protection law in your country of residence, including any right to bring proceedings in your local courts.

30. Dispute resolution and arbitration

⚖️ PLEASE READ THIS SECTION CAREFULLY. IT AFFECTS YOUR LEGAL RIGHTS. It requires most disputes to be resolved by binding individual arbitration rather than in court, waives your right to a jury trial, and waives your right to bring or participate in a class action or class arbitration. You can opt out within 30 days — Section 30.8 tells you exactly how.

30.1 Informal resolution first. Before starting an arbitration or a lawsuit, you agree to try to resolve the dispute informally. Send a written Notice of Dispute to [email protected] or by mail to the address in Section 34 — either channel is sufficient — describing the dispute, the relief you want, and your account email address. We will do the same by email to your account address. If a Notice omits required information, the receiving party will say so within 10 business days and the sender may cure; a Notice is not ineffective because of a non-material defect. Both parties agree to negotiate in good faith for 60 days from receipt, and either party may proceed sooner if the other declines to engage. This step is a condition precedent to filing, and all applicable limitations periods, including Section 26.5, are tolled from the date the Notice is sent until 30 days after the negotiation period ends.

30.2 Agreement to arbitrate. If informal resolution does not succeed, you and RyanTech LLC agree that any dispute, claim, or controversy arising out of or relating to these Terms or the Service — including their formation, interpretation, breach, termination, validity, or enforceability — will be resolved exclusively by final and binding individual arbitration, and not in court, except as provided in Sections 30.5 and 30.6. This agreement to arbitrate is governed by the Federal Arbitration Act, 9 U.S.C. § 1 et seq.

This agreement to arbitrate applies to claims you bring against RyanTech LLC and against its Affiliates, officers, members, employees, contractors, agents, and suppliers, each of whom is an intended third-party beneficiary of this Section 30, and to claims arising before you accepted these Terms as well as after your account ends.

30.3 Rules and administrator. The arbitration will be administered by the American Arbitration Association (AAA) under its rules then in effect:

• if you are using the Service primarily for personal, family, or household purposes, the AAA Consumer Arbitration Rules apply;
• otherwise, the AAA Commercial Arbitration Rules apply.

The rules are available at adr.org. We have registered this arbitration agreement on the AAA Consumer Clause Registry. If the AAA is unavailable or unwilling to administer the arbitration consistent with this Section, the parties will agree on a substitute administrator or, failing agreement, a court of competent jurisdiction will appoint one.

30.4 Procedure. The arbitration will be before a single arbitrator. The seat of arbitration is South Carolina. Hearings will be conducted by telephone, videoconference, or on documents where the applicable rules permit; if an in-person hearing is required, it will take place in the South Carolina county in which RyanTech LLC maintains its principal place of business, or another mutually agreed location. The arbitrator has exclusive authority to resolve all disputes about the interpretation, applicability, enforceability, and scope of this arbitration agreement, except that a court has exclusive authority to decide the enforceability of the class-action waiver in Section 30.7. The arbitrator may award any relief a court could award to that individual claimant, and the award is final and binding and may be entered in any court of competent jurisdiction.

Filing, administrative, and arbitrator fees are governed by the applicable AAA rules. In any arbitration, each party bears its own attorneys' fees except where the applicable rules or governing law provide otherwise, in which case they are available to either party on the same terms — including under Section 6.14.

30.4a Consumer arbitration costs. If you are a consumer and your claim is for $25,000 or less:

• we will pay all AAA filing, administrative, and arbitrator fees in excess of the amount you would pay to file the same claim in the state court where you live, unless the arbitrator determines your claim was frivolous or brought for an improper purpose under the standards of Federal Rule of Civil Procedure 11(b);
• we will not seek our attorneys' fees or costs from you unless the arbitrator makes that same finding; and
• you may elect to have the arbitration conducted solely on documents, by telephone, or by videoconference, at your option.

30.5 Small-claims carve-out. Either party may bring an individual claim in small-claims court in a court of competent jurisdiction, instead of arbitration, so long as the claim remains in that court, is brought on an individual (non-class, non-representative) basis, and is within that court's jurisdictional limits.

30.6 Injunctive relief carve-out. Either party may seek temporary or preliminary injunctive relief in a court of competent jurisdiction to prevent actual or threatened infringement, misappropriation, or violation of its intellectual property rights, its Confidential Information, or the Acceptable Use Policy, without first proceeding to arbitration and without waiving this Section.

30.7 Class-action and class-arbitration waiver.

YOU AND RYANTECH LLC AGREE THAT EACH MAY BRING CLAIMS AGAINST THE OTHER ONLY IN AN INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS, COLLECTIVE, CONSOLIDATED, PRIVATE ATTORNEY GENERAL, OR REPRESENTATIVE PROCEEDING. The arbitrator may not consolidate more than one person's claims and may not preside over any form of class or representative proceeding. If this waiver is found unenforceable as to a particular claim or request for relief, that claim or request must be severed and brought in court, and the remaining claims proceed in arbitration.

30.8 Your right to opt out of arbitration — 30 days.

You may opt out of Section 30 (arbitration and the class waiver) and it will not apply to you. To opt out, send written notice within 30 days of the date you first accept these Terms. Include: (a) your full name; (b) the email address on your Demo Pine account; (c) the words "I opt out of the Demo Pine arbitration agreement." Send it by email to [email protected] with the subject line "Arbitration Opt-Out," or by mail to:
RyanTech LLC — Arbitration Opt-Out 2764 Pleasant Road, Suite A #599, Fort Mill, SC 29708, USA If you are unsure of the date you first accepted these Terms, email [email protected] and we will tell you; we will treat a good-faith opt-out sent within 30 days of our response as timely. Opting out is free and will not affect your account or your use of the Service in any way. If you opt out, disputes are resolved in court under Section 31. If you do not opt out within 30 days, Section 30 applies. Your opt-out applies only to Section 30; the rest of these Terms still apply.

30.9 Jury-trial waiver.

TO THE EXTENT ANY DISPUTE PROCEEDS IN COURT RATHER THAN ARBITRATION — INCLUDING IF YOU OPT OUT UNDER SECTION 30.8, IF A CLAIM IS SEVERED UNDER SECTION 30.7, OR UNDER THE CARVE-OUTS IN SECTIONS 30.5 AND 30.6 — YOU AND RYANTECH LLC EACH KNOWINGLY AND VOLUNTARILY WAIVE ANY RIGHT TO A TRIAL BY JURY.

30.10 Mass filings. If 25 or more demands for arbitration raising substantially similar claims are filed against us by, or with the coordination of, the same counsel or organization, the AAA Mass Arbitration Supplementary Rules and the corresponding AAA fee schedule then in effect will apply, including any process appointing a global mediator or process arbitrator. All applicable limitations periods are tolled for claims awaiting their turn under those rules. Nothing in this Section prevents either party from agreeing to a bellwether process or from electing small-claims court under Section 30.5.

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

31. Governing law and venue

31.1 Governing law. These Terms and any dispute arising out of or relating to them or the Service are governed by the laws of the State of South Carolina, USA, without regard to its conflict-of-laws rules, except that the Federal Arbitration Act governs Section 30. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

31.2 Venue. For any dispute not subject to arbitration — including claims brought after a valid opt-out, claims severed under Section 30.7, and the carve-outs in Sections 30.5 and 30.6 — you and RyanTech LLC consent to the exclusive jurisdiction and venue of the state and federal courts located in South Carolina, and each party waives any objection to that venue on grounds of inconvenient forum.

31.3 Consumer rights. If you are a consumer resident in a jurisdiction whose law entitles you to bring proceedings in your local courts or to the protection of mandatory local consumer law, nothing in this Section deprives you of that right.

32. Changes to these Terms

32.1 We may update these Terms. We will post the updated version at https://demopine.com/terms with a new version number and effective date, and we retain prior versions at https://demopine.com/terms/archive so you can see what applied when.

32.2 Notice of material changes. For changes that materially and adversely affect your rights, we will give at least 30 days' notice before they take effect, by email to your account address or by prominent in-app notice.

32.3 Your right to reject a material change. If we make a change that materially and adversely affects your rights, you may reject it by notifying us at [email protected] before its effective date. If you reject it, your subscription will continue under the prior version of these Terms until the end of your then-current term and will not auto-renew — or you may terminate immediately, and we will refund the prepaid fees allocable to the remainder of your term on a straight-line daily basis. This is an exception to Section 6.11. Continued use after the effective date without rejecting the change means you accept it.

32.4 No retroactive effect. We will not apply any change retroactively to a dispute that arose before its effective date.

32.5 Changes to arbitration. If we make a material change to Section 30, you may reject that change by sending us notice in the manner described in Section 30.8 within 30 days of the change taking effect, in which case the version of Section 30 in effect immediately before the change continues to apply between us.

33. General terms

33.1 Entire agreement. These Terms, together with the Privacy Policy, the DPA, and any signed order form or MSA, are the entire agreement between you and RyanTech LLC about the Service, and supersede all prior or contemporaneous understandings, proposals, marketing statements, and communications on that subject.

33.2 Severability. If any provision is held unenforceable, it will be modified to the minimum extent necessary to make it enforceable, or severed if it cannot be, and the rest of these Terms remain in full force. Section 30.7 has its own severability rule, which controls for that provision.

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

33.4 Assignment. Neither party may assign or transfer these Terms or any rights under them without the other party's prior written consent, which will not be unreasonably withheld; provided that either party may assign these Terms in their entirety, on notice and without consent, to a successor in connection with a merger, acquisition, reorganization, or sale of all or substantially all of its assets, so long as the assignee assumes all obligations. Any attempted assignment in breach of this Section is void. These Terms bind and benefit the parties' permitted successors and assigns.

33.5 Independent contractors. The parties are independent contractors. Nothing in these Terms creates a partnership, joint venture, agency, franchise, or employment relationship.

33.6 Force majeure. Neither party is liable for any delay or failure to perform (other than a payment obligation) caused by events beyond its reasonable control, including acts of God, natural disaster, fire, flood, epidemic or pandemic, war, terrorism, civil unrest, labor dispute, governmental action, internet or telecommunications failure, denial-of-service attack, or the failure or unavailability of a third-party hosting, storage, payment, email, or AI provider. If a force majeure event prevents performance for more than 30 consecutive days, either party may terminate the affected subscription on written notice, and we will refund the prepaid fees allocable to the period of non-performance and the remainder of the term.

33.7 Notices. We may give you notice by email to the address on your account, by notice in the Service, or by posting to demopine.com. Notice is effective when sent or posted. You must give us notice by email to [email protected] and, for formal legal notices, also by mail to 2764 Pleasant Road, Suite A #599, Fort Mill, SC 29708, USA.

33.8 Third-party beneficiaries. There are no third-party beneficiaries of these Terms, except that our Affiliates, officers, members, employees, contractors, and suppliers are intended beneficiaries of Sections 25, 26, 27, and 30.

33.9 Export controls and sanctions. You represent that you are not located in, ordinarily resident in, or organized under the laws of any country or region subject to comprehensive US embargo or sanctions, and that you are not listed on any US government restricted-party list (including OFAC's Specially Designated Nationals list) or owned or controlled by any such party. You agree to comply with all applicable export-control, sanctions, and anti-corruption laws, including the US Export Administration Regulations and the Foreign Corrupt Practices Act, and not to make the Service available to any prohibited person or for any prohibited end use.

33.10 US government users. The Service is a "commercial product" and "commercial computer software" as defined in FAR 2.101 and DFARS 227.7202. Government users acquire only the rights granted to all other users under these Terms, consistent with FAR 12.212 and DFARS 227.7202-1 through 227.7202-4.

33.11 Language. These Terms are written in English. Any translation is provided for convenience only; the English version controls.

33.12 Headings and interpretation. Headings are for convenience only. "Including" means "including without limitation." References to days mean calendar days unless stated otherwise.

33.13 Survival. Sections 2, 5.8, 6.11, 6.13, 6.14, 9.1, 9.3, 10, 12.3, 13.4, 18, 19, 20, 21, 23, 24, 25, 26, 27, 28.4, 30, 31, and 33, and any other provision that by its nature should survive termination, survive termination of these Terms and of your account.

33.14 Electronic records and signatures. You consent to receive these Terms, the Privacy Policy, the DPA, billing and auto-renewal disclosures, receipts, notices, and other communications electronically, by email to your account address or by posting in the Service, and you agree that electronic records and signatures satisfy any requirement that such records be in writing or signed. To view and retain these records you need a device with internet access, a current browser, and the ability to receive email and open PDFs. You may withdraw this consent, or request paper copies, by writing to [email protected]; withdrawing consent may mean we can no longer provide the Service to you. Tell us if your email address changes.

34. How to contact us

RyanTech LLC (d/b/a Demo Pine) A South Carolina limited liability company 2764 Pleasant Road, Suite A #599, Fort Mill, SC 29708, USA

Terms of Service: https://demopine.com/terms · Privacy Policy: https://demopine.com/privacy · Data Processing Addendum: https://demopine.com/dpa · Sub-processors: https://demopine.com/subprocessors

Effective date: July 31, 2026 · Last updated: July 31, 2026 · Version 1.0