Studio End User Licence Agreement¶
Effective date: November 5, 2026
This End User Licence Agreement ("EULA") governs use of the proprietary Zensical Studio application ("Studio" or the "Software"), including its Free, Pro and Team editions. It is an agreement with Zensical LLC, 30 N Gould St Ste N, Sheridan, WY 82801, United States ("Zensical", "we" or "us"). Zensical may be contacted at hello@zensical.org.
By expressly accepting this EULA before first use, you agree to its terms. If you accept on behalf of an organisation, you must have authority to bind it. An individual accepting the rules for their own use does not thereby assume an organisation's purchase or payment obligations.
1. Scope and applicable documents¶
1.1 This EULA governs the proprietary Studio application. Independently licensed editor integrations and Open Source components remain governed by their own licences, including the MIT licence where applicable. This EULA does not restrict rights those licences grant.
1.2 The Service Terms additionally govern Zensical Accounts and paid purchases, including Orders, payment, protected prices, cancellation, refunds and common commercial matters. Their definitions of Account, Customer and Order apply to those relationships. Studio Free requires neither an Account nor acceptance of the Service Terms solely to use the Software.
1.3 Studio does not itself include Spark membership, a Spark support entitlement or a Private service. Those rights require the applicable offer or Order and the Spark Service Terms. The Privacy Policy explains personal-data processing separately from software-licence acceptance and optional consent.
1.4 For paid access, the Service Terms' subject-specific precedence rule applies. This EULA governs software permissions and use; an Order states the purchased edition, named recipient, seat quantity and period. A price or quantity alone does not vary liability or other legal provisions. An express written variation governs the standard provision it identifies.
2. Licence and editions¶
2.1 Subject to this EULA and the applicable access rights, Zensical grants a limited, non-exclusive licence to install and use Studio for private and professional work, including commercial work. The licence permits the copies described in section 6. It transfers no ownership of the Software. Zensical and its licensors retain all rights in the proprietary Software not expressly granted by this EULA.
Free¶
2.2 Studio Free may be used without signing in or activating a device. Accounts, Spark membership and purchases require users to be at least eighteen and have the required legal capacity under the Service Terms.
2.3 A younger person may use account-free Studio Free where they have the legal capacity or parental or guardian permission required by applicable law. Any required guardian acceptance must be obtained before use. This permission does not authorise a minor to create an Account or make a paid purchase.
Pro¶
2.4 Studio Pro is licensed to one named individual and linked to that individual's personal Account for the applicable access period. It is personal and non-transferable. An employer or another buyer may pay for or reimburse Pro, but payment confers no ownership, administration or reassignment rights on that buyer in respect of the individual's licence.
Team¶
2.5 Studio Team seats belong to the organisation and are assigned to named individuals. An authorised organisation owner or administrator may assign and reassign purchased seats to accepted members who are employees or contractors working for that organisation. Each person shall use their own Account. Seat sharing and resale are prohibited.
2.6 Administration or billing authority alone does not grant a Studio seat. The applicable Order identifies the organisation served and any expressly included recipient organisations. A separate buyer does not obtain a recipient's licence-administration rights merely by paying for its purchase.
2.7 The accepted offer defines the included capabilities. A roadmap or announcement does not add an unpurchased feature or delivery commitment, without limiting anything included in the accepted offer.
3. Device registrations and remote use¶
3.1 Each named user may maintain two current device registrations for paid Studio, unless Zensical expressly grants a higher allowance. Both registrations belong to that user; they do not permit two people to share a licence. Free requires no device registration.
3.2 A separately registered environment running paid Studio counts toward the allowance, including a workstation, laptop, remote development host or virtual machine. Multiple editor windows using Studio in the same registered environment share its registration.
An editor that only connects to Studio running elsewhere does not use an additional registration. If paid Studio also runs locally, that local environment requires its own registration.
3.3 You may deactivate a registration through your Account and activate a replacement. An extended offline token does not reserve its old registration until expiry or require support approval for replacement.
Deactivation stops new validation under that registration. An already issued token may remain technically usable while disconnected until its original expiry.
3.4 Remote execution is permitted for the named user's work in an environment they or the served organisation control. Remote execution confers no shared-user licence or right to provide Studio as a service to unrelated users. Permission to run remotely does not guarantee compatibility with every editor, host or virtualisation arrangement.
4. Activation and offline access¶
4.1 Paid capabilities require a valid personal entitlement or Team assignment and account-linked activation. Authorisation is bound to the registered environment and has a stated expiry. It does not extend a purchased or trial period.
Ordinary offline access¶
4.2 Pro and Team ordinarily allow up to seven days of offline use after successful validation, ending sooner if the applicable access period ends. A failed connection does not extend the authorisation. A device must successfully validate again to obtain a fresh ordinary token.
Extended Team access¶
4.3 An organisation owner or authorised administrator may expressly enable extended offline tokens during an existing annual paid Team subscription period. The approved Team-trial exception in section 5.3 also applies. Once enabled, assigned members may obtain tokens for their own registered environments without separate approval for each issuance or replacement. Billing authority alone does not grant this control. The option is unavailable to Pro and monthly paid Team subscriptions.
4.4 An extended token expires no later than the end of the current annual paid Team period or, for an approved Team trial, the confirmed trial expiry. It grants no future unpaid renewal period. No separate enterprise purchase is required. Team air-gapped use may obtain and transfer its device-bound authorisation through a connected system; the target environment need not connect to Zensical itself.
Renewal requires a new token for the renewed period. Existing disconnected tokens do not renew themselves.
4.5 Disabling the option stops new extended-token issuance. Ordinary authorisation remains available while the assignment is valid. Deactivating a device or ending a Team assignment stops new issuance or refresh under that registration or assignment.
These actions cannot shorten a token already held by a disconnected device. Replacement tokens remain bounded by the same applicable period; old and replacement tokens may overlap technically. The two-device rule concerns current registrations and does not promise immediate revocation of every offline copy.
4.6 Continued technical usability of a token does not extend an expired or revoked right. The former user's permission under a reassigned Team seat ends when the assignment ends. The former user shall cease use of the paid capabilities under that assignment, subject to any independently valid licence.
4.7 Extended tokens follow the same refund policy as other paid access. Enabling or issuing one is not a separate waiver of statutory, merchant or agreed refund rights. Its offline-revocation limits do not excuse an applicable refund or other continuing contractual obligation.
5. Trials¶
5.1 The applicable trial offer or confirmation specifies the capabilities, start, expiry and organisation seat allowance. Individual Studio trials and Spark reading trials are separate. Each person ordinarily receives one individual Studio trial; additional Accounts, email addresses or organisation memberships do not reset eligibility.
5.2 Organisation Team trials require Zensical's approval. An unlimited-seat evaluation means named users within the approved organisation may participate without a fixed trial seat-count cap. It does not permit shared Accounts, resale or use by unrelated organisations. Extensions and exceptional repeat organisation trials require Zensical's express approval and a confirmed expiry.
5.3 Trial use follows the same named-user, two-device and activation rules as normal use. Ordinary offline tokens expire no later than the trial's end. An approved Team trial may use the organisation-controlled extended-token option, also capped at trial expiry. Individual trials retain ordinary offline validity. An approved extension permits new tokens to the revised end; it does not change a token already held by a disconnected device.
5.4 Zensical may conduct proportionate trial-eligibility checks. The trial offer describes the eligibility requirements and a route to request review. You shall not misrepresent eligibility or evade trial limits. A newly created Zensical Account does not, of itself, disqualify an otherwise eligible applicant.
5.5 Trials require no payment card and do not create an automatic paid subscription. Paid continuation requires a separate accepted purchase. An organisation's authorised buyer chooses the paid seat quantity and price; trial participants do not automatically become billable seats. At expiry, the trial capabilities end while Studio Free and independently valid paid access remain available.
6. Copies and internal distribution¶
6.1 You may make unmodified copies of Studio for installation, backup and otherwise authorised use. An organisation may distribute those copies internally, including through an internal package repository or transfer into an air-gapped environment, for its authorised employees and contractors.
6.2 You shall retain the applicable copyright and licence notices with those copies and make this EULA available to their users. Each paid user requires their own valid personal entitlement or named Team assignment and must comply with the registration rules. Possession of an executable grants no paid access.
6.3 This permission does not include public distribution of the proprietary executable, resale, sublicensing or sharing Accounts, credentials or personal activation tokens. Independently licensed editor integrations and Open Source components retain their own copying and distribution permissions.
7. Project files and data¶
7.1 You and the relevant rights holders retain ownership of your projects and files. Use of Studio grants Zensical no ownership or promotional licence over them. Studio processes MkDocs and Zensical projects in your development environment, including a user-controlled remote host. Normal use does not upload, store or retain project files at Zensical.
7.2 Project material you deliberately submit for support or a bug report is handled under that channel's applicable terms. Submitting it is separate from local Studio use. Paid expiry does not change your files' ownership or give Zensical custody of them.
7.3 Paid activation, validation and executable delivery process the information needed for those purposes, separately from project contents. This includes account/licence associations and registered-environment information for paid access, and compatibility information such as operating system and version, architecture, and editor and version for delivery. The Privacy Policy explains the actual fields, purposes, recipients and retention. Download and update servers may receive your IP address and technical request details even when you use Studio Free without an Account.
7.4 Optional usage analytics or automatic crash reporting, if offered, are disabled by default and require a separate, reversible opt-in. Declining or withdrawing that opt-in does not reduce product functionality. Zensical shall exclude project contents, file paths and credentials from optional automatic reports. Acceptance of this EULA is not consent to optional reporting.
8. Restrictions and licence review¶
8.1 Except as permitted by this EULA, another applicable licence or law, you shall not:
- modify, adapt, decompile, disassemble or reverse engineer the proprietary Software, or attempt to derive its source code;
- bypass paid-feature controls, falsify licence eligibility, share a named licence or use another person's credentials or token;
- sell, publicly redistribute, sublicense or provide shared access to the proprietary Software outside the permissions granted here; or
- use Studio unlawfully or remove its copyright and licence notices.
8.2 These restrictions do not limit mandatory rights concerning interoperability, observation, testing or backup, or permissions granted for Open Source components. They do not prevent modifying an MIT-licensed editor integration, using the agreed optional-reporting controls or replacing devices as permitted.
8.3 Zensical may review limited Account, entitlement, registration and token-issuance history for suspected licence misuse, as disclosed in the Privacy Policy. Permitted device replacement and outstanding offline-token overlap are not by themselves proof of misuse. Before imposing a licence-enforcement suspension, Zensical shall conduct a human review of the evidence and provide you with an opportunity to explain. Proportionate urgent security or legally required protective action remains separate under the Service Terms where applicable.
9. Updates and support¶
9.1 Ordinary fixes target the latest supported Studio release. You may need to update to receive a fix. Zensical does not generally undertake to provide backports or maintenance of an older release unless expressly agreed. A valid offline token permits licensed use for its applicable period; it does not purchase maintenance of a frozen release.
9.2 The availability of a newer version does not by itself revoke valid licensed or offline access. Zensical does not undertake to correct every defect or provide a particular release schedule or compatibility with every future operating-system or editor version.
Updates to third-party editors, operating systems or dependencies may affect Studio's operation. Zensical shall use reasonable efforts to investigate and remedy resulting compatibility issues promptly, but does not guarantee immediate restoration of compatibility. Express purchased commitments and mandatory remedies remain applicable.
9.3 Studio alone includes no Spark response-time commitment or customer-specific development. Contractual product support follows the applicable Spark service and Spark Service Terms; business email is not a parallel product-support channel. Public bug reports and voluntary feedback may be submitted through Zensical's published channels without creating a contractual response or resolution commitment. The reasonable-efforts obligation under section 9.2 remains applicable.
10. Expiry and termination¶
10.1 Upon expiry of paid or trial access, the corresponding paid capabilities cease; Studio Free remains available under this EULA. Removal of a Team assignment does not cancel the person's Account, personal Pro licence or another valid assignment. Reassigning a seat makes it available to its new assignee without waiting for the former user's offline tokens to expire.
10.2 Cancelling paid renewal preserves access through the applicable paid period, subject to the Service Terms. A refund or early ending affects access as specified under those Terms; it does not automatically end unrelated rights. Your existing project files remain yours and available independently of Studio.
10.3 For a material breach of this EULA that is capable of remedy, Zensical may terminate the affected licence if you fail to remedy it within fourteen calendar days following written notice identifying the breach. An irremediable breach or repeated serious breaches may justify termination without a further correction period, subject to proportionate action, human review and mandatory law. Protective action is distinct from final termination.
10.4 Paid-service termination, Zensical's material breach, applicable refunds and planned retirement are governed by the Service Terms, including their correction and notice periods. Ordinary paid expiry is distinct from termination of the Software licence for breach. If a proprietary Software licence is terminated, you shall cease the affected use and remove copies no longer authorised under any valid licence. This does not require deleting your projects or independently licensed Open Source components.
10.5 You may cease use of Studio at any time. Uninstallation does not, of itself, cancel a paid subscription; cancellation requires the applicable cancellation route. Ownership, applicable restrictions, liability and other provisions intended to continue survive termination subject to their stated limits and mandatory law.
11. Warranties and responsibility for files¶
11.1 Except for Zensical's express contractual commitments and warranties required by law, Studio is provided on an "as is" and "as available" basis. To the extent permitted by law, Zensical disclaims all other warranties, including implied warranties of merchantability and fitness for a particular purpose. Zensical does not warrant uninterrupted or error-free operation, correction of every defect or freedom from data loss.
11.2 You are responsible for appropriate backups and version control of your project files and for reviewing changes before relying on them. This provision does not exclude any remedy available under mandatory law or an express commitment. Open Source warranties and exclusions remain subject to the relevant component licences.
12. Liability¶
12.1 The limitations in this section do not apply to liability that cannot lawfully be limited, including fraud, fraudulent misrepresentation and death or personal injury caused by negligence where those protections apply. Mandatory consumer rights remain unaffected.
12.2 Subject to section 12.1, Zensical is not liable for indirect or consequential loss, lost profits, revenue, business opportunities, anticipated savings, or loss or corruption of data. This provision does not exclude an express refund or repayment obligation. In relation to consumers, these exclusions do not remove a right to recover foreseeable loss caused by Zensical's breach where such exclusion would be unlawful or unfair.
12.3 Zensical's aggregate liability for claims relating to affected Studio access is limited to the fees actually paid for that access during the twelve months immediately preceding the event giving rise to the claim. Related claims arising from the same event or series of related events share that limit.
12.4 Payments through Polar and payments by an authorised buyer on a recipient's behalf count toward the relevant fees. The reference is the Customer's product fees, excluding separately itemised sales tax or VAT and deducting refunds of those fees completed before the event giving rise to the claim. Merchant and processing charges are not deducted. Later refunds do not reduce the limit fixed at that event. There is no fixed minimum. If no relevant fees remain after that calculation, including account-free Free use, the limit is zero except where applicable law requires otherwise.
12.5 This is the same limit as section 13 of the Service Terms where those Terms apply. Claims under both documents do not create separate allowances or duplicate recovery. A mandatory rule or an expressly agreed variation prevails. The cap does not reduce any refund, overpayment or other Customer balance that Zensical is required to repay. Zensical undertakes no voluntary defence or indemnity against third-party intellectual-property claims under this EULA.
13. Changes to this EULA¶
13.1 Updated versions must state their effective date. Material changes affecting an active paid subscription follow section 14 of the Service Terms, including its notice, eligible-renewal and authorised earlier-acceptance rules. No change authorises a higher price without the explicit consent those Terms require or displaces an existing purchased commitment.
13.2 For account-free use of Studio Free, Zensical shall present a revised EULA for acceptance before use under that version. The EULA is available to read offline, and acceptance of its applicable version is remembered locally without an Account or online acceptance check. A software patch alone does not require acceptance again where the applicable EULA has not changed.
13.3 Changes do not apply retrospectively to disputes that arose before their effective date. Software-licence acceptance remains separate from optional reporting consent and any required acceptance for a paid purchase.
14. General provisions¶
14.1 This EULA is governed by Wyoming law and applicable United States federal law, excluding their conflict-of-law rules. Wyoming courts have exclusive jurisdiction, except where mandatory law provides another right or forum. A consumer retains the mandatory protections applicable to them and any right to bring proceedings in a competent court where they live. This EULA contains no arbitration agreement or class-action waiver.
14.2 If a provision is unenforceable, the remaining provisions continue to the extent permitted by law. A failure to enforce a provision does not waive its later enforcement.
14.3 This EULA and, where applicable, the accepted Order and Service Terms govern the Software rights they address, subject to expressly agreed variations and independently applicable licences. Mandatory rights remain unaffected.