PRONE
Website Terms and App Use Policy
Updated 19 November 2026
These terms cover the PRONE website. The app use policy describes the rules intended for the desktop release. The terms supplied with the app will identify the operator, the support contact, and the conditions for that release.
1. About these terms
1.1 Website scope
These terms apply to the PRONE website, including its product information, documentation, and release announcements. PRONE is the product name used on this website. Details identifying the operator and the appropriate support contact will be supplied with the desktop release.
1.2 Desktop policy
The desktop provisions below describe the use restrictions intended for the app. The terms supplied with the software will identify which provisions apply to that release. Posting this policy on the website does not create an account, record acceptance, or enforce restrictions inside the app.
1.3 Other terms
A release, a third-party component, or a future online service may have additional terms. Those terms will identify the product or component they cover. Mandatory legal rights take precedence where applicable.
1.4 Defined terms
A model is software or model data used to generate a response. A module is an optional component that adds a tool, connection, or workflow. A release is a particular version of the desktop app and the documentation distributed with it.
1.5 Product boundaries
Website access, the desktop app, an optional module, and a hosted service are separate parts of PRONE. A term about one part applies to another only where the wording or the applicable release terms say so.
1.6 Authority to act
If you accept terms on behalf of an organization, check that you have authority to do so. Access through a work device or email address does not itself establish that authority.
1.7 Reading related notices
Review the applicable privacy notice, release notes, component licence, and permission prompts together with these terms. A permission prompt describes a particular action and does not replace the privacy notice or licence.
2. Product information and availability
2.1 Pre-release descriptions
Descriptions of features, examples, screenshots, modules, and workflows explain what is planned or illustrate how local AI can work. Confirm what is included with the specific version you receive. Release dates and model support may change before launch.
2.2 Compatibility
Whether a release runs on your device may depend on the operating system, processor, memory, graphics hardware, storage, and configuration. Check the published requirements for the version and model you intend to use.
2.3 Release channels
Use the official release source listed on the PRONE website when a download is available. Check that the installer matches your device and verify its publisher or checksum where one is supplied.
2.4 Updates and discontinued components
Review release notes and keep backups before changing versions, models, or modules. Where an update changes compatibility, consult the release notes for migration or rollback instructions if those are available. Your statutory remedies continue to apply.
2.5 Preview builds
If an experimental build is offered, check its release notes for known limitations and supported uses. Use copies of important files when testing migration or experimental features.
2.6 Storage and resources
Allow room for installers, extracted model files, caches, temporary files, and backups. Closing a window may not stop a background task. Check the process status before moving model files or shutting down.
2.7 Interrupted installation
If an installer stops partway through, consult the documented recovery process before deleting files or installing a second copy. Preserve error details and keep a separate copy of any data you need.
2.8 Uninstalling
When uninstall instructions are available, check whether they cover model files, preferences, local history, and caches separately. Removing desktop software does not itself close an online account or remove copies held by another service.
2.9 Release authenticity
Do not enter sign-in details into installers or support pages reached through unofficial messages. If a copy or update appears unexpected, compare its source with the release page before running it.
2.10 Compatibility after updates
An operating system, driver, or module update may affect a previously working setup. Check version requirements and back up settings before replacing dependencies or converting files.
3. Accounts and access
3.1 Desktop accounts
A PRONE account is planned for desktop use. The release terms will explain registration, sign-in, recovery, and whether local features remain available when the device is offline. The current website does not provide PRONE account registration.
3.2 Credentials
Keep your sign-in and recovery methods under your control. Use the official account flow for verification and recovery. Contact support through the published channel if you suspect an account was accessed without your permission.
3.3 Acceptance and continued access
When acceptance is required, PRONE will show the applicable version before you decide. After reasonable notice of a material change, PRONE may require you to select “I agree” to continue using the affected account or desktop features from the date stated in the notice, where permitted by law. Silence or continued use will not count as acceptance. If you decline or have yet to accept, access to the affected features may be paused. Any applicable rights to retrieve data, cancel, receive a refund, or seek another remedy remain available.
3.4 Restricted access
Where access controls are available, they may be used to respond to suspected account compromise, unlawful use, or a material breach of the applicable use rules. The affected user should receive the reason and a route to dispute the restriction where practical and permitted by law.
3.5 Account eligibility
Before registering, check the age, regional, and eligibility requirements published for the service. If a parent, guardian, or organization must authorize use, obtain that authorization before creating or using an account.
3.6 Registration and correction
If registration becomes available, provide accurate information required for sign-in and account recovery. Keep recovery information current and correct mistakes through the available account settings or support channel.
3.7 Lost access
If you lose a device or recovery method, use the official recovery process. Support may need to verify that you control the account before changing recovery information. Never send passwords or one-time login codes in support messages.
3.8 Shared devices
Sign out when you finish on a device other people can access. Check whether that device retains separately stored model files, outputs, or local history before handing it to someone else.
3.9 Offline access
Desktop sign-in is planned. The initial release will specify whether sign-in requires internet access, what continues offline after sign-in, and what happens when verification expires. Do not assume an account requirement means prompts are sent to a server.
3.10 Closing an account
When accounts launch, the applicable settings or support instructions will explain how to request closure. Before closing, retrieve any material you need where export is available. The privacy notice will describe retention and deletion for account data.
3.11 Separate permissions
Account acceptance does not grant permission to access every model, connect every provider, or process someone else's files. Those actions may require their own permission, entitlement, or separate agreement.
3.12 Sign-in methods and regional availability
Email and Google sign-in are planned. Launch markets, eligibility, and supported sign-in methods will be confirmed before registration. Website language availability does not determine account eligibility. If Google sign-in is offered, Google handles authentication and the PRONE privacy notice will explain what account information PRONE receives.
4. Acceptable use
4.1 Lawful authority
Use PRONE only for tasks you are legally authorized to perform. Obtain the necessary permissions before processing another person's information, using their files, or acting on a system you do not control.
4.2 Unauthorized access and malware
Do not use PRONE to compromise accounts or devices, steal credentials, distribute malware, bypass access restrictions, or interfere with systems without authorization.
4.3 Fraud, abuse, and exploitation
Do not use PRONE for fraud, deceptive impersonation, unlawful surveillance, stalking, harassment, threats, or exploitation of children. Do not use it to facilitate violence or unlawfully obtain, disclose, or distribute private information.
4.4 Consequential decisions
Do not rely solely on automated outputs when making decisions that materially affect another person. Use qualified human review where appropriate and comply with any legal requirements that apply to your decision.
4.5 Use by an organization
If you use PRONE for work or on an organization's device, follow its policies and authority limits. Confirm which material can be processed and which integrations you may enable before using them.
4.6 Spam and manipulation
Do not use PRONE to send unlawful bulk messages, create deceptive reviews or endorsements, or bypass the controls of a platform on which you publish generated material.
4.7 Confidentiality and rights
Do not use PRONE to publish trade secrets or confidential records without authority. Follow relevant restrictions on copying, redistribution, and disclosure, including any obligations to protect personal information.
4.8 Safety controls
Do not disable protective controls in order to carry out a prohibited use. Authorized configuration and maintenance remain subject to the applicable documentation and your permissions.
4.9 Automated actions
Where a module can send messages, modify records, or start a process, verify the destination, scope, and authorization before it acts. Use review steps before actions that are difficult to reverse.
4.10 Reporting misuse
When an official reporting channel is available, include enough detail to locate the issue. Share only the material needed to investigate and avoid redistributing harmful or private content.
5. Prompts, files, and outputs
5.1 Permission to use inputs
Check that you have the rights and permissions needed to use prompts, documents, code, and other material you provide. Confidentiality obligations and restrictions on sharing may apply even when processing takes place on your own device.
5.2 Quality of outputs
Model responses may contain incorrect facts, fabricated citations, insecure code, or misleading omissions. Check important statements against reliable sources and review any changes before acting on them.
5.3 Professional judgment
Outputs are general information and can be unsuitable for a specific situation. Consult a suitably qualified person before depending on an output for medical, legal, financial, or safety decisions.
5.4 Generated code and instructions
Read generated commands and scripts before executing them. Check what they may install, modify, delete, or transmit. Test changes in an appropriate environment and keep backups of data you need to recover.
5.5 Output rights and publication
Check applicable law and the relevant model or module licence before publishing or selling generated material. An output may resemble existing work or contain material that requires attribution or permission.
5.6 Incomplete context
A model can omit earlier text, overlook content buried in an attachment, or rely only on an excerpt. Verify which input was processed before relying on a summary or comparison.
5.7 Files and imported text
Imported documents, pages, and messages may contain misleading instructions. Treat them as untrusted input and review proposed actions independently, especially if an enabled module can access other data.
5.8 Citations and calculations
Check quotations against the original source and recompute important figures independently. Formatting, confident wording, or links in a response do not establish accuracy.
5.9 Version differences
Results may vary with the model, version, settings, hardware, and context. If reproducibility matters, keep a record of the configuration and source material as permitted by your obligations.
5.10 Edits and backups
Keep original copies before accepting batch edits, file conversions, or generated changes. Check that names, references, and formatting survived the conversion before discarding originals.
5.11 Human review before sharing
Review generated material for confidential data, factual errors, and permissions before sharing it. If law or the receiving service requires disclosure of AI assistance, provide it.
6. Models, modules, and integrations
6.1 Availability and licensing
The supported model and module catalogues will be released once confirmed. Third-party components may be governed by separate licences with conditions on attribution, redistribution, or commercial use.
6.2 Permissions
Review each component's source and requested access before enabling it. In particular, check whether it can read files, run commands, connect to another service, or make changes on your behalf.
6.3 External services
A component that connects to an external provider may send information to that provider. Examine its settings, terms, and privacy notice to understand which information is sent and what options you have.
6.4 Component changes
A third-party provider may update, withdraw, or change the terms of its component. Review compatibility and licensing before upgrading or depending on a specific feature.
6.5 Component source and version
Record where a component came from and which version you installed if you expect to troubleshoot or reproduce a workflow. Check that its publisher and download source match the documentation.
6.6 Scope of access
Where a component offers scoped permissions, grant only the files, folders, tools, or network destinations needed for the task. Review permissions again after an update or a change in ownership.
6.7 Removing a module
Disabling or removing a component may stop future activity but may not revoke a token or remove data already transferred. Check the connected provider's settings to revoke access and manage copies where available.
6.8 External charges
A connected provider may apply its own billing, quotas, or rate limits. Check the provider's billing terms before enabling a connection or repeating automated requests.
6.9 Licence conditions
A component's licence may distinguish personal, research, commercial, and redistribution uses. Review attribution and notice requirements before sharing a copy or packaging the component with other software.
7. Local and hosted processing
7.1 Local processing
Local inference means the model runs on your device. Features such as downloading a model, signing in, or using an external integration may still require a network connection.
7.2 Potential hosted features
PRONE may offer hosted AI in the future. Before any hosted feature becomes available, its documentation will describe when requests leave your device, what data the service processes, and which settings or choices are available.
7.3 Privacy information
A privacy notice for accounts or hosted processing should explain who operates the service, what information is collected, the purposes for using it, whom it is shared with, and how users can exercise applicable rights. This section describes the planned distinction between local and hosted processing.
7.4 Sensitive material
Before entering confidential, personal, or regulated material, check your authority and whether the selected mode and components are suitable. Review network and permission settings when the distinction between device processing and remote processing matters.
7.5 Choosing a processing mode
Before submitting sensitive material, verify the selected model, execution location, and enabled integrations. If a release supports both local and hosted processing, consult its documentation for switching modes and how failures are handled.
7.6 Local copies and backups
Local files may be copied by operating system backups, synchronization tools, or other software you configure. Check where your prompt history, outputs, caches, and exports are stored before sharing a device or deleting a file.
7.7 Account data and prompt data
Information used for account access may be handled separately from prompts and outputs. The notice for the relevant release will identify the actual information categories and purposes.
7.8 Logs and diagnostics
Before sharing diagnostic files, check for usernames, file paths, tokens, prompts, and personal information. Use the documented channel and send only the excerpts needed to explain the problem.
7.9 Retention and transfers
Any applicable account or hosted-service notice will describe retention, disclosures, and relevant international transfers based on the service actually offered. Local processing by itself gives no information about the retention practices of an external service.
7.10 Privacy requests
Use the privacy contact supplied for the relevant service to ask about access, correction, deletion, or other applicable rights. The operator may need to verify your identity before releasing or changing information.
7.11 Local storage and online account services
PRONE is designed to store local-mode prompts, files, and responses on your computer. Account services and optional online features have separate data flows. The applicable release documentation and privacy notice will identify what is stored locally, what leaves the device, and the available settings.
8. Consumer rights, warranties, and liability
8.1 Mandatory protections
Nothing in these terms excludes, restricts, or modifies rights, remedies, guarantees, or liabilities that cannot lawfully be excluded, restricted, or modified. Where Australian Consumer Law or other mandatory consumer protections apply, those rights continue to apply.
8.2 Availability and performance
Subject to applicable law and any express commitments for a release, PRONE does not guarantee uninterrupted operation, compatibility with every configuration, or that a response will be accurate or suitable for a particular task.
8.3 Limitation of liability
To the extent permitted by applicable law, the operator's liability for indirect or consequential loss arising from use of the website or software is limited. This clause does not exclude remedies, compensation, or any other liability that applicable law protects.
8.4 Remedies
The remedies available for a particular issue depend on the circumstances and applicable law. These terms do not prevent you from seeking a remedy, reporting a concern to a regulator, or bringing a claim before a court or tribunal with jurisdiction.
8.5 Express commitments
Review the commitments that accompany the specific release or service. General information about limitations does not override a warranty or promise that applies to your purchase or use under law.
8.6 Failures and interruptions
Interruption may come from a device fault, an unavailable provider, a model error, or a service issue. Document what happened before changing configuration. Any applicable entitlement to repair, replacement, refund, or other remedy depends on the circumstances and law.
8.7 Mitigating loss
If an issue could cause further harm, stop the affected task where practical, preserve relevant evidence, and use backups or other reasonable recovery steps. This does not reduce rights or remedies that cannot lawfully be restricted.
8.8 Rights in your jurisdiction
Mandatory protections can differ by jurisdiction. Nothing here requires you to give up a forum, right to complain, or remedy that the law makes available to you.
9. Support, disputes, and changes
9.1 Reporting an issue
Once support details are published, include the version, device and operating system, steps to reproduce the issue, and the result you expected. Remove credentials and unrelated personal data before sharing logs or screenshots.
9.2 Raising a dispute
You may use the published operator contact to raise a concern. Keep a copy of your report and relevant records. Contacting the operator does not remove any right to seek help from a regulator, court, or tribunal.
9.3 Changes to the website terms
The date above identifies this version of the website terms. Future revisions will be published with an updated date. Changes to desktop or account terms will be communicated through the applicable release or account flow where required.
9.4 If a clause cannot apply
If part of these terms is unenforceable in a particular situation, the remaining parts continue to apply to the extent permitted by law. Mandatory protections in the relevant jurisdiction continue to apply.
9.5 Support reports
Include the time of the event, the exact error, and whether the issue happens with a different model or clean configuration if you have already checked. Do not take risky steps to reproduce an issue solely for a report.
9.6 Security reports
If a reported issue may expose private data or credentials, limit further access and use the published contact when available. Share only what is needed to describe the issue and avoid publishing affected users' information.
9.7 Which version applies
Once you accept revised terms, they replace the prior version for future use of the affected features from the later of your acceptance date and the stated effective date. The prior version still applies to earlier use and events where relevant. An update does not erase accrued rights, obligations, or claims, or affect provisions that lawfully continue after the earlier terms end. The account or app flow will identify the version presented for acceptance.
9.8 Language and accessibility
If a term, permission prompt, or support instruction is unclear, request clarification through the published contact when available. Any mandatory language or accessibility requirements that apply continue to apply.