Zevol Product Policy

1. What Zevol provides

Zevol is the app-building workspace within Zexir. You describe an idea, receive generated code and a preview, and continue refining the app through chats inside its project folder. This policy supplements the Terms of Service, Privacy Policy, Acceptable Use Policy, and AI Accuracy & Reliance Policy. It applies to builds, revisions, previews, saved app files, and actions requested through conversation.

A feature shown in a design example is not a promise that every build will support it. Available models, usage allowances, file sizes, integrations, and publishing options depend on the current product, your plan, and connected services. A successful preview is not a certification of security, legal compliance, accessibility, or suitability for your business.

2. Your instructions and materials

Provide only content, designs, files, data, and credentials you are entitled to use. Describe intended users, important restrictions, and the behavior you need. Avoid placing passwords, private keys, payment information, real customer records, or sensitive personal information in prompts or generated frontend code. Use fictitious data while prototyping.

You remain responsible for requirements and final decisions. If you ask for an app that collects personal information, accepts payment, sends messages, or makes decisions about people, review those flows separately before release. Zevol does not automatically establish your business policies, professional permissions, data-processing agreements, or rights to third-party content.

3. Projects and saved conversations

An app folder can contain multiple chats and generated files. Saved project information may include instructions, file contents, build results, questions, revisions, and activity records. It is processed under the Privacy Policy and associated with the account that owns the project. Keep your own copies of important source and business records.

Renaming or archiving a chat changes its organization; it does not necessarily remove the app files or related build records. Removing a project from Zevol does not automatically remove copies you exported, an app deployed on a hosting provider, a registered domain, or records held by an external service. Manage those resources separately.

4. Generated code and previews

Generated code can contain defects, inaccessible interactions, unsafe dependencies, inaccurate text, and placeholder behavior. Review navigation, forms, authentication, error handling, and mobile layouts. A display-only mockup must not be presented to users as a working payment, login, booking, or data-saving system.

A preview may run scripts and contact third-party resources included in the code. Do not enter live secrets or use it to process regulated information. Preview isolation reduces some risks but is not a complete security audit. Downloads, external links, and connected-service actions can have consequences outside the preview.

5. Testing and AI review

AI review and build checks can identify some problems and suggest revisions. They cannot prove that an app works in every browser, withstands attack, or satisfies all requirements. A claim that a check passed should be understood only for the check actually run; an AI prediction that code should work is not an executed test.

Before making an app public, test representative inputs, failure cases, permissions, persistence, and dependencies. Use qualified review when the app handles confidential information, money, health, legal matters, or other high-impact functions. Do not rely on a generated assurance as a substitute for evidence.

6. Pausing, stopping, and retries

Pause and stop controls affect work managed by Zevol. A request already sent to a model or an external service may finish despite a pause, cancellation, or lost browser connection. These controls do not undo a published message, completed deployment, or domain registration.

If an action is interrupted, inspect the saved project and the external service before repeating it. An uncertain purchase or deployment may require reconciliation instead of a new request. Repeated generation may consume usage even when the result is incomplete; the Billing Policy and displayed plan rules govern charges.

7. Publishing and external actions

Creating an app and making it public are separate steps. Publishing requires a configured deployment connection and explicit approval in the release flow. A domain purchase requires the exact quote, registration details, and approval shown at checkout. Describing an idea or pressing Enter to generate code does not by itself authorize a domain charge.

The Deployments, Domains & Receipts Policy describes publication, pricing, uncertain results, renewals, and receipts. Connected accounts remain subject to their providers’ terms and limits. Never instruct Zevol to act on another person’s resources without authority.

8. Operating your finished app

You are responsible for the app you choose to release, including its content, data collection, disclosures, access controls, customer support, and ongoing maintenance. Changes to hosting, dependencies, browser behavior, or provider APIs may affect an app after it was generated.

Zevol does not automatically monitor every deployed app or keep it updated unless a feature expressly provides that service. Maintain backups and a way to disable an unsafe release. Report defects with a safe project identifier and reproduction steps to mail@zexiry.com; do not send secrets or customer datasets.

Clarification, source files and personal knowledge

When an important ambiguity prevents Zevol from safely completing a request, the conversation can pause for a question. Suggested answers are optional; you may type your own answer. Zevol continues the saved task after receiving a valid answer. Clarifying a product decision is not approval for an unspecified purchase, public release or message to a connected account.

The code control switches between the private preview and the app's saved source files. Downloading code exports those files as a ZIP archive. The export contains project source, not Zevol account credentials or an export of your chat history. Downloading a ZIP does not deploy it, license third-party assets beyond their existing terms, or guarantee that the app will run in every environment. Review dependencies and required services before running it elsewhere.

Personal knowledge is an account-specific Markdown document named knowledgeforuser.md. With memory enabled, supported saved requests can be reviewed to extract explicit preferences and enduring facts. The owner can inspect, edit, download and reset the document in Personal memory. AI formatting organizes a submitted edit; it can make mistakes, so review the saved version. The knowledge percentage describes processed versus pending saved information, not certainty about a person, comprehensive understanding or training of a separate model.

Private chats and device-local chats are excluded from automatic knowledge learning. Disabling memory prevents its use in subsequent requests. Learned knowledge is separate from a source chat and remains until edited or reset; deleting a chat alone does not guarantee deletion of facts already saved in the knowledge document. Resetting clears the document and excludes older conversations from future recall. Personal knowledge never grants permission to publish, buy, post or send.

Project settings apply to the selected app. Website addresses and publication are governed by the Deployments, Domains & Receipts Policy. Folder, chat and account ownership checks apply to source access, settings and exports. Do not upload material you lack permission to use or ask Zevol to bypass another user's access controls.

Related policies and contact

For related responsibilities, see our Acceptable Use, AI Accuracy & Reliance, Account & Security, and Subscription & Billing policies. Contact mail@zexiry.com for questions about this supplement.