Vertile

Vertile.ai / Legal

Tokenless Terms of Service

Policies and terms presented as clear, readable source documents.

Document
Tokenless terms

Effective date: 27 July 2026
Last updated: 27 July 2026

Tokenless is a product of Vertile AI Pty Ltd (ABN 11 688 480 499) ("Vertile AI", "Vertile", "we", "us", or "our"). These Terms of Service ("Terms") govern your download, installation, and use of the Tokenless command-line tool, user-installed local daemon, managed Playwright browser profiles, and related local components (together, "Tokenless").

These Terms are intended to be read with:

If these Terms conflict with the Vertile AI Terms of Service about how you may use Tokenless, these Terms control. If they conflict with a privacy policy about personal information Vertile holds, the relevant privacy policy controls. AI provider terms are separate contracts between you and those providers.

Tokenless is an independent tool. It is not made by, affiliated with, endorsed by, or officially supported by any AI provider whose website it can operate.

BY INSTALLING, ACCESSING, OR USING TOKENLESS, YOU AGREE TO THESE TERMS. If you do not agree, do not install or use Tokenless.

1. Plain-language summary

  • Tokenless lets local agents and tools route suitable work through supported AI provider websites using Playwright on your device, then returns the visible result to your local workflow.
  • Tokenless runs locally. Vertile does not operate a hosted Tokenless relay or AI service that receives your prompts, provider-page content, files, responses, managed browser profiles, or provider credentials.
  • A future Tokenless release may report a numeric estimate of tokens saved. This minimal telemetry will not contain prompts, responses, files, page content, URLs, account information, or persistent user or device identifiers.
  • You remain responsible for your provider accounts, compliance with provider terms, and anything you submit through provider websites.
  • Providers may treat automation differently from manual use. Tokenless does not promise that providers will allow, tolerate, or continue to support this use.
  • You must not use Tokenless to steal credentials, bypass provider security checks, call private provider APIs, or submit information you are not authorised to use.
  • Support is discretionary unless we agree otherwise in writing. Features may break when providers change their websites.

2. Definitions

  • Local Runtime means the user-installed Tokenless command-line tool, local daemon, Playwright worker, job database, managed browser profiles, and related local components.
  • Managed Browser Profile means a separate browser profile created or imported for Tokenless and stored on your device.
  • Provider means a third-party AI service whose web interface Tokenless can operate. Current documentation identifies supported and experimental Providers.
  • Provider Account means your account, subscription, guest session, or login with a Provider.
  • Visible-session automation means Tokenless operating a Provider's visible website through a Managed Browser Profile using Playwright and visible page controls, without using a private Provider API.
  • Savings Telemetry means the future minimal telemetry described in the Tokenless Privacy Policy: a numeric aggregate estimate, calculated locally, of tokens saved through Tokenless use.
  • Your Content means prompts, instructions, context, files, and other content you submit through Tokenless, together with responses returned to your local workflow.
  • You means the individual using Tokenless and, if you use Tokenless for an organisation, that organisation as well, provided you have authority to bind it.

3. Eligibility and authority

You must be at least 18 years old and meet the age and eligibility rules of the Providers you select. If you use Tokenless on behalf of an organisation, you represent that you have authority to bind that organisation to these Terms and that your organisation's policies allow this use.

4. Licence to use Tokenless

Subject to these Terms, Vertile grants you a limited, non-exclusive, non-transferable, revocable licence to install and use Tokenless for your personal or internal business purposes.

Open-source components remain under their applicable licences. Where an open-source licence conflicts with these Terms for a component, the open-source licence controls for that component. These Terms still govern Vertile branding and any proprietary services or materials unless an applicable licence expressly provides otherwise.

Except as permitted by law or an applicable open-source licence, you must not:

  • sell, rent, or sublicense Tokenless as a hosted service operated by you for third parties without our written agreement;
  • remove proprietary notices from proprietary materials; or
  • misrepresent Tokenless as an official product of any Provider.

5. Relationship to Providers

Tokenless submits prompts and intentionally selected context or files through the normal HTTPS website of the Provider you selected. The Provider handles that information under its own terms, privacy policy, settings, and retention rules. Vertile does not control Provider products, policies, retention, rate limits, CAPTCHAs, model availability, user-interface changes, or enforcement actions.

Your compliance obligation. You are solely responsible for reviewing and complying with the terms, policies, subscription rules, and usage limits of each Provider you use with Tokenless. These Terms do not modify any Provider agreement and do not grant you rights against a Provider. If a Provider's rules are unclear, restrictive, or change without notice, that risk sits with you, not Vertile.

No compliance warranty. Vertile does not warrant that using Tokenless complies with a Provider's terms. Automation of a Provider website, even when limited to visible actions, may be restricted or prohibited by a Provider or may lead to warnings, rate limits, feature loss, account suspension, or termination. You accept that risk, including loss of Provider Account access or paid subscriptions. Vertile is not liable for Provider enforcement actions except to the extent liability cannot be excluded under applicable law.

Not a Provider API client. Tokenless is not a private Provider API client and must not be used to extract authentication material, call private Provider backend APIs, or silently fall back to a paid Provider API.

Experimental dependency. Visible-session automation depends on Provider websites that Providers may change at any time without notice to Vertile. Temporary or permanent breakage is expected from time to time and is not, by itself, a breach of these Terms by Vertile.

6. Acceptable use

6.1 Permitted use

You may use Tokenless only:

  • for its disclosed purpose of routing suitable work from local agents or tools through supported Provider websites and returning visible results to the local workflow;
  • on Provider and trusted sign-in origins allowed by Tokenless's local provider configuration;
  • with a Local Runtime that you explicitly install and configure on a device you control; and
  • in a manner consistent with applicable law, these Terms, your organisation's policies, and the Provider terms that apply to you.

6.2 Prohibited use

You must not use Tokenless to:

  • violate applicable law or infringe another person's rights;
  • knowingly violate a Provider's terms, policies, rate limits, subscription rules, or anti-automation rules that apply to you, or continue using Tokenless with a Provider after that Provider has notified you that such use is prohibited;
  • export, steal, exfiltrate, print, log, or expose browser cookies, passwords, browser-storage authentication values, hidden authorisation headers, or other Provider credentials;
  • inspect Provider network traffic or call private Provider backend APIs;
  • bypass Provider sign-in, CAPTCHA, bot checks, human confirmation dialogs, rate limits, paywalls, consent steps, or permission gates;
  • use Tokenless on websites outside approved Provider or trusted sign-in origins;
  • submit prompts, files, or context containing personal information, confidential information, trade secrets, or third-party data that you are not authorised to use or disclose;
  • use Tokenless in employment or client work in breach of your employer's or client's policies;
  • spam, harass, commit fraud, generate malware, or assist others in doing so through Provider websites;
  • reverse engineer Tokenless to defeat security controls, except to the extent permitted by law or an applicable open-source licence; or
  • redistribute Tokenless in a way that falsely implies Provider endorsement or Vertile sponsorship of unlawful use.

Nothing in Section 6.2 requires Vertile to interpret Provider terms for you. Section 5's risk allocation still applies where Provider rules are ambiguous.

6.3 Consequences

If you breach this Section 6, we may refuse support, suspend distribution or update channels we control, terminate the licence in Section 4, and pursue other remedies available by law. Provider enforcement against your Provider Account is between you and the Provider.

7. Local software, profiles, security, and support

You install and run the Local Runtime on systems you control. Tokenless typically stores state under its home directory, which defaults to ~/.tokenless. This state may include configuration, a local daemon authentication token, a job database, prompts and results, logs, snapshots, temporary staged attachments, Managed Browser Profiles, and Provider sign-in state.

Tokenless may offer an optional import flow that, with your explicit action, copies selected supported Provider sign-in records from a local Chrome or Brave profile into a separate Managed Browser Profile. Import does not modify the source profile. You are responsible for choosing the source profile and securing any imported Managed Browser Profile.

You are responsible for:

  • securing your device, browser profiles, Provider Accounts, and local Tokenless files;
  • reviewing requested actions, selected files, and visible Provider confirmations;
  • verifying that Tokenless packages or installers come from a channel you trust;
  • using available profile and deletion controls when local state is no longer needed; and
  • understanding that a compromised device can undermine local security controls.

Tokenless uses separate Managed Browser Profiles, provider-scoped navigation rules, local file permissions, integrity-checked attachment staging, loopback-oriented daemon communication, and authenticated local operations as described in the Tokenless Privacy Policy. No measure eliminates all risk.

Vertile may publish updates. You are responsible for installing updates you choose to apply. Tokenless may contact the public package registry to check for available versions. Breaking changes in Provider websites may stop Tokenless from working until you update or until we publish a fix.

Unless we agree otherwise in writing, support, documentation, and community assistance are provided at Vertile's discretion without a service-level commitment.

8. Content, outputs, telemetry, and intellectual property

As between you and Vertile, you retain your rights in Your Content. Providers may have their own ownership, licence, and usage rules for inputs and outputs under your Provider Account; Vertile does not control those rules.

Vertile and its licensors own Tokenless, excluding Your Content and open-source components under their licences, including its branding and documentation. These Terms do not transfer ownership of Tokenless to you.

Vertile does not claim a licence to use Your Content for AI model training, advertising, or profiling. Your Content remains on your device or with Providers as described in the Tokenless Privacy Policy, except information you deliberately send to Vertile.

Tokenless does not currently send product telemetry. If Savings Telemetry is enabled in a future release, you authorise Tokenless to transmit the locally calculated numeric savings estimate described in the Tokenless Privacy Policy. Savings Telemetry will not include Your Content, AI communications, Provider-page content, files, paths, URLs, Provider account information, authentication data, local job records, or a persistent user or device identifier. Relevant product documentation or settings will provide a way to disable future transmissions.

Savings figures are estimates. Vertile does not warrant that a reported number exactly measures tokens, fees, API quota, or financial savings.

If you provide suggestions or feedback about Tokenless, you grant Vertile a perpetual, irrevocable, worldwide, royalty-free licence to use and incorporate that feedback into our products without restriction or obligation to you. Feedback does not include Your Content processed only by the Local Runtime.

9. Fees

Tokenless may be offered free of charge, under open-source licences, or under paid plans described separately. Any fees for paid Vertile offerings are governed by the Vertile AI Terms of Service or a separate written order unless a Tokenless-specific pricing page states otherwise. If Tokenless is free for you, the liability floor in Section 11 still applies.

Provider subscriptions, API plans, data charges, and other third-party fees are separate from any Tokenless fee. You are responsible for charges imposed by third parties.

10. Disclaimers

To the maximum extent permitted by law, Tokenless is provided "as is" and "as available", without warranties of any kind, whether express, implied, or statutory, including merchantability, fitness for a particular purpose, and non-infringement.

Without limiting the above, Vertile does not warrant that:

  • Tokenless will be uninterrupted, error-free, secure, or compatible with every Provider website, browser version, operating system, or local environment;
  • Providers will permit automation, continue to expose the same controls, or refrain from enforcing their terms against your Provider Account;
  • responses returned from a Provider website will be accurate, complete, lawful, or fit for your purpose;
  • local storage under the Tokenless home directory or a Managed Browser Profile will be free from loss, corruption, or unauthorised access; or
  • estimated token-savings figures will be exact or will correspond to a particular monetary saving.

AI-generated outputs may include errors and may not reflect current laws, security practices, or best practices. You are responsible for reviewing outputs before relying on them.

11. Limitation of liability

To the maximum extent permitted by law:

  • Vertile will not be liable for indirect, consequential, special, exemplary, or punitive damages, or for loss of profits, revenue, goodwill, data, Provider Account access, Provider subscriptions, or Provider-held conversations, arising from or related to Tokenless or these Terms.
  • Vertile's total aggregate liability arising out of or relating to Tokenless or these Terms is limited to the greater of: (a) the fees you paid to Vertile specifically for Tokenless in the 12 months immediately before the event giving rise to the claim; and (b) AUD $100.

Nothing in these Terms excludes, restricts, or modifies any consumer guarantee, right, or remedy you may have under the Australian Consumer Law that cannot be excluded, restricted, or modified. If the Australian Consumer Law requires a different remedy for a failure of a consumer guarantee, that remedy applies to the extent required.

12. Indemnity

You agree to indemnify and hold harmless Vertile from and against third-party claims, losses, damages, liabilities, and expenses, including reasonable legal fees, arising from:

  • your use of Tokenless in breach of these Terms or applicable law;
  • your breach of Provider terms or third-party rights;
  • Your Content, including claims that you lacked authority to submit it; or
  • your violation of employer or client policies when using Tokenless,

except to the extent caused by Vertile's breach of these Terms or negligence. This indemnity does not require you to indemnify Vertile for Vertile's own failure to describe Tokenless's data practices accurately.

13. Suspension, termination, and deletion

You may stop using Tokenless at any time by stopping or uninstalling the Local Runtime and deleting Tokenless local state.

We may suspend distribution, disable update or telemetry services we control, refuse support, or terminate the licence in Section 4 if we reasonably believe you have breached these Terms, your use poses a security risk, or we are required to do so by law or a distribution platform.

Termination does not delete Provider-held conversations or automatically wipe local files. Use the controls described in the Tokenless Privacy Policy to remove local data. Sections that by their nature should survive, including Sections 5, 8, 10, 11, 12, 15, and 16, survive termination.

14. Changes to these Terms

We may update these Terms when Tokenless features, distribution channels, data practices, or legal requirements change. We will publish updated Terms at this URL and change the effective or last-updated date as appropriate.

Where a change materially affects your rights or obligations, we will provide additional notice where practical and where required by law before the changed terms apply to continued use.

If you do not agree to an update, stop using Tokenless and uninstall the Local Runtime. Continued use after a stated effective date constitutes acceptance of the updated Terms, except where applicable law requires a different form of acceptance.

15. Governing law and venue

These Terms are governed by the laws of South Australia and the Commonwealth of Australia. You submit to the non-exclusive jurisdiction of the courts of South Australia.

16. Miscellaneous

  • Entire agreement. These Terms, together with the Tokenless Privacy Policy for data-handling disclosures, are the entire agreement between you and Vertile regarding Tokenless unless we agree otherwise in writing. They do not replace Provider agreements or applicable open-source licences.
  • Severability. If any part of these Terms is held invalid, the remaining parts remain in effect.
  • No waiver. A failure to enforce a provision is not a waiver.
  • Assignment. You may not assign these Terms without our prior written consent. We may assign them as part of a corporate restructure, merger, acquisition, or sale of assets.
  • Open-source. Nothing in these Terms limits rights you have under applicable open-source licences for Tokenless components.
  • No third-party beneficiaries. These Terms do not create rights for Providers or other third parties, except that Vertile's indemnified parties may enforce Section 12.
  • Language. If we provide a translation, the English version controls unless applicable law requires otherwise.

17. Contact