ZexirAI · Subscription & Billing

Know what renews, when, and why.

This policy covers plan pricing, automatic renewal, usage limits, payment processing, upgrades, cancellation, failed payments, taxes, refunds, and billing disputes for ZexirAI subscriptions.

At a glance: Paid plans renew for the billing interval shown at checkout until canceled. Scheduling cancellation normally keeps paid access active through the current period and stops the next renewal.

1. Scope and agreement

This Subscription and Billing Policy applies when you purchase or manage a paid ZexirAI plan through the website, application, Stripe-hosted tools, or another checkout that links to this policy. It supplements the Terms of Service. If checkout clearly states a different billing interval, price, trial, promotional period, or cancellation term, that transaction-specific disclosure controls for that purchase.

“Subscription” means recurring access to a paid plan. “Billing period” means the monthly or other interval displayed before you confirm payment. “Account holder” means the ZexirAI user whose account receives access. “Payment method” means a card or other method accepted by the payment processor. “Processor” means Stripe or another payment provider identified at checkout.

By confirming a purchase, you represent that the billing information is accurate, you are authorized to use the payment method, and you authorize recurring charges described at checkout and in this policy. If you purchase for an organization or another user, you represent that you have authority to do so and understand that payment does not by itself determine ownership of an account.

2. Free and paid plans

ZexirAI may offer Free, Lite, Go, Plus, Super, Pro, Ultra, business, promotional, or other plans. Names, prices, included features, model access, usage multipliers, storage, response speed, context, project tools, and availability may change over time. The plan page and checkout show the current offer that applies to a new purchase. A feature shown in marketing may still be subject to technical compatibility, fair-use controls, regional availability, or a staged rollout.

Paid access is licensed to the account, not purchased as a perpetual software copy. A higher tier may include more capacity or model access without guaranteeing uninterrupted or unlimited use. “Everything in” another tier means the generally available feature set, subject to the same limits and any provider or regional restrictions. Business features may remain unavailable until explicitly launched and purchased.

Free access can be limited, changed, or withdrawn, subject to applicable law. Free quotas, promotional credits, and unused message capacity have no cash value, are not transferable, and do not roll over unless the offer expressly says they do. A paid plan does not include charges imposed independently by your mobile carrier, bank, card issuer, internet provider, tax authority, or a connected third-party service.

3. Checkout and payment processing

ZexirAI uses Stripe for secure subscription checkout and billing management. Stripe collects and processes payment-card details, billing name, address, payment authentication, fraud signals, and related transaction data under its own privacy and service terms. ZexirAI receives identifiers and status information needed to associate the resulting customer and subscription with your account. The application is not designed to store full card numbers entered through Stripe’s payment form.

Review the plan name, recurring amount, currency, billing interval, taxes, and renewal disclosure before confirming. Prices are generally displayed in U.S. dollars unless the checkout states another currency. Your bank or issuer may apply currency conversion, foreign transaction, authorization, or other fees that ZexirAI does not control. A temporary authorization can appear before a final charge and may take time to disappear if checkout is not completed.

Checkout may require a verified ZexirAI login so access is attached to the correct account. Do not complete payment while signed in to another person’s account. If the checkout page closes or returns an unclear result, inspect the plan status and payment account before trying again to avoid duplicate attempts. Contact support with the approximate time, amount, account email, and non-sensitive transaction reference; never send a full card number or security code.

4. Automatic renewal and authorization

A paid subscription automatically renews at the end of each billing period until canceled. By purchasing, you authorize the Processor to charge the payment method for the plan price, applicable taxes, and any plan change you expressly approve. The renewal date is based on the original subscription start or a later billing adjustment made by the Processor. Calendar differences, time zones, and payment retries can affect the displayed time.

You are responsible for canceling before the next charge if you do not want the subscription to renew. Do not rely solely on a calendar reminder or the absence of a marketing email. The current subscription status and billing-period end shown in ZexirAI or the billing portal are the relevant account controls, although status synchronization can briefly lag after a processor event.

Renewal continues even if you do not use all available capacity, do not sign in, remove an app, clear browser data, stop using a particular model, or delete local files. Those actions do not communicate cancellation to the Processor. Only the cancellation control, a confirmed processor action, or support confirmation stops future renewal.

5. Usage, storage, and service limits

Plan capacity can be expressed as messages, tokens, credits, storage, file size, project usage, model availability, context length, rate, concurrency, or a multiplier relative to the Free plan. Limits may reset over a stated period and may differ by model or feature because providers have different costs and technical constraints. A message can consume different resources based on length, attachments, tools, reasoning level, search, image generation, or project work.

Usage displays are operational estimates and can lag. We may apply reasonable controls to protect availability, prevent automated abuse, and distribute capacity fairly. “Unlimited” language, if ever offered, is subject to the Acceptable Use Policy, reasonable technical limits, and protection against excessive automated or resale activity unless checkout expressly guarantees a defined quantity.

Reaching a limit may pause access to a model or feature until reset, offer a fallback, reduce throughput, or require an upgrade. It does not automatically produce a refund. Provider outages, safety restrictions, or incompatible attachments can also make a feature unavailable even when quota remains. Keep independent copies of important work; a subscription is not a guaranteed archival or backup service.

6. Upgrades, downgrades, and plan changes

When you upgrade an active subscription through the plan controls, the change may take effect immediately. Stripe may calculate a prorated credit for the unused portion of the current plan and a prorated charge for the higher plan, and may invoice the net amount immediately. The preview or confirmation interface should be reviewed before approval. Taxes, prior credits, and processor calculations can cause the final amount to differ from a simple price subtraction.

An upgrade can cancel a previously scheduled end-of-period cancellation and continue automatic renewal on the new plan. If payment for an immediate upgrade is incomplete or fails, access may remain on the earlier plan, enter a temporary state, or be restricted until the Processor confirms payment. Do not assume a button click completed the change; confirm the plan displayed in the account.

Self-service downgrades may not be available through the same control. You may need to cancel renewal and select a different plan after the current period, or use a Stripe billing portal option when offered. A downgrade can reduce capacity, storage allowance, or feature access. Export or reduce stored material before the lower limit takes effect. We will not intentionally delete active content solely because of an immediate plan change without a reasonable handling process, but over-limit storage may become read-only or subject to later removal under posted rules.

7. Cancellation and resumption

You may schedule cancellation using the subscription controls on the plans page or another billing-management control offered in the Service. The account should show that cancellation is scheduled and that access remains active until the current billing period ends. If the status does not change, retry once, inspect the hosted billing portal if available, or contact support before the renewal date. Keep the confirmation or screenshot.

Scheduling cancellation normally stops the next renewal rather than ending paid access immediately. You may continue using included features through the paid period, subject to ordinary limits. No prorated refund is automatically issued for unused time after cancellation unless applicable law or a written offer requires one. At period end, the account ordinarily moves to the Free plan and higher-tier capacity or features stop.

Before the period ends, a “Continue plan” or resume control may remove the scheduled cancellation. Resuming restores automatic renewal for the current plan, and the payment method can be charged at the next renewal. Review the updated status after resuming. Deleting an account and canceling a subscription are different operations; resolve the subscription before account closure to avoid ambiguity. App deletion, logout, inactivity, or an email request without confirmation is not by itself a completed cancellation.

8. Failed, reversed, or disputed payments

A payment may fail because of insufficient funds, an expired card, issuer controls, address mismatch, authentication requirements, network problems, fraud screening, or a Processor decision. Stripe or the issuer may retry a renewal. During a retry period, access may continue temporarily, become limited, or end. Update the payment method through a trusted billing portal rather than sending card details to support.

If a charge is reversed, refunded, or disputed, we may remove the related paid access and preserve records needed to resolve the transaction. Abusing chargebacks to retain service without payment, using a payment method without authorization, or repeatedly creating accounts to avoid an unpaid balance can result in suspension. A good-faith billing dispute will not be treated as abuse merely because you contact the issuer, but contacting us first often allows faster correction.

Bank statements may use a processor or merchant descriptor that differs slightly from the product name. Before reporting fraud, compare the amount and date to the account’s subscription. If the charge is genuinely unauthorized, secure the ZexirAI account and email account, contact the issuer, and notify support so we can investigate associated access.

9. Taxes, invoices, and records

Displayed prices may exclude sales, use, value-added, goods-and-services, withholding, or similar taxes unless checkout says they are included. The Processor may calculate taxes based on billing information, payment location, service classification, and legal requirements. You are responsible for taxes and government charges associated with the purchase other than taxes imposed on ZexirAI’s net income.

Provide accurate billing name and address information. An organization that needs an invoice, tax identifier, exemption, or business record should enter it through the available billing portal before the charge when possible. We cannot guarantee retroactive changes that the Processor or tax rules do not support. You remain responsible for determining the accounting and tax treatment of a purchase.

Receipts and invoices may be available from Stripe, email, or the billing portal. Retain them for your records. Subscription status displayed in ZexirAI is not a tax invoice and may show only limited transaction information.

10. Refunds and service credits

Except where applicable law requires otherwise or a specific offer states a refund right, subscription charges are non-refundable and we do not provide automatic prorated refunds for partial periods, unused capacity, forgetting to cancel, dissatisfaction with a model response, or a temporary interruption. This rule does not limit non-waivable consumer rights or our ability to correct a duplicate, erroneous, or unauthorized charge.

Submit a refund request promptly after discovering the issue. Include the account email, charge date, amount, plan, reason, and a safe transaction reference. Do not include full card data. We may verify use of the subscription, cancellation status, prior refunds, processor records, and whether the issue was within ZexirAI’s control. A request does not guarantee approval.

If we issue a refund, it normally returns through the original payment method and timing depends on Stripe and the financial institution. A pending refund can take several business days or longer to appear. Service credits, if offered, are not cash, are non-transferable, may expire, and apply only to the account and purpose stated.

11. Billing errors and disputes

Review charges and account status regularly. Contact us as soon as reasonably possible if a plan, amount, renewal, cancellation, tax, duplicate charge, or refund appears wrong. Describe the expected result and attach a redacted receipt or screenshot if useful. We may coordinate with Stripe and may ask you to confirm control of the ZexirAI account and payment relationship.

Do not email passwords, authentication codes, full card numbers, bank credentials, or unredacted identity documents. Support may request only limited details such as card brand and last four digits when needed. Messages from an unfamiliar sender asking for payment outside the normal checkout should be treated as suspicious.

If informal review does not resolve the issue, the dispute provisions of the Terms apply, along with any rights available from your issuer or consumer law. Nothing in this policy requires you to waive a mandatory right to challenge an unauthorized or incorrect charge.

12. Price and policy changes

We may change plan prices, names, limits, or included features prospectively as provider costs, capabilities, demand, taxes, and the product change. New prices apply immediately to new purchases unless stated otherwise. For an existing recurring subscription, a changed renewal price will take effect only after notice required by applicable law and any required consent or cancellation opportunity.

If you do not agree to a future price, cancel before the first renewal at that price. Continuing the subscription after the effective renewal constitutes acceptance where the law permits. We may move a discontinued plan to a reasonably comparable offering, allow the current term to expire, or provide another legally appropriate option. Material changes to this policy receive notice when required.

13. Billing contact

For billing questions, contact mail@zexiry.com from the email associated with the account when possible. Provide the plan, approximate date and amount, a redacted receipt or processor reference, and the result you expected. For card authorization or posting timing, your financial institution may also need to help.

This policy is a product billing agreement, not tax, accounting, or financial advice. Organizations and users with specialized procurement, invoicing, regulatory, or data-processing requirements should obtain a separate written agreement before purchase rather than assuming the consumer checkout supplies those terms.

1. Plan Selection: detailed guidance

This section explains how the policy applies to plan selection. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on plan selection, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to plan selection. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns plan selection, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of plan selection as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

2. Free Access: detailed guidance

This section explains how the policy applies to free access. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on free access, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to free access. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns free access, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of free access as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

3. Trial Offers: detailed guidance

This section explains how the policy applies to trial offers. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on trial offers, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to trial offers. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns trial offers, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of trial offers as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

4. Subscription Activation: detailed guidance

This section explains how the policy applies to subscription activation. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on subscription activation, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to subscription activation. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns subscription activation, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of subscription activation as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

5. Renewal Timing: detailed guidance

This section explains how the policy applies to renewal timing. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on renewal timing, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to renewal timing. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns renewal timing, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of renewal timing as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

6. Monthly Billing: detailed guidance

This section explains how the policy applies to monthly billing. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on monthly billing, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to monthly billing. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns monthly billing, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of monthly billing as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

7. Annual Billing: detailed guidance

This section explains how the policy applies to annual billing. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on annual billing, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to annual billing. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns annual billing, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of annual billing as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

8. Usage Allowances: detailed guidance

This section explains how the policy applies to usage allowances. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on usage allowances, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to usage allowances. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns usage allowances, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of usage allowances as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

9. Feature Availability: detailed guidance

This section explains how the policy applies to feature availability. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on feature availability, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to feature availability. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns feature availability, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of feature availability as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

10. Plan Upgrades: detailed guidance

This section explains how the policy applies to plan upgrades. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on plan upgrades, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to plan upgrades. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns plan upgrades, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of plan upgrades as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

11. Plan Downgrades: detailed guidance

This section explains how the policy applies to plan downgrades. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on plan downgrades, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to plan downgrades. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns plan downgrades, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of plan downgrades as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

12. Cancellation: detailed guidance

This section explains how the policy applies to cancellation. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on cancellation, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to cancellation. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns cancellation, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of cancellation as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

13. Expiration: detailed guidance

This section explains how the policy applies to expiration. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on expiration, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to expiration. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns expiration, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of expiration as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.

14. Payment Authorization: detailed guidance

This section explains how the policy applies to payment authorization. The governing principle is that a user should understand the feature, use only the access and information reasonably needed for the task, and keep qualified human judgment in control whenever an action may affect another person. Product labels, examples, interface text, and automated notices illustrate ordinary operation; they do not replace the specific facts, laws, contracts, professional duties, or provider terms that apply in a particular situation.

Before relying on payment authorization, review the requested purpose, the sensitivity of the information involved, the people who may be affected, and the consequences of an error. Use the least sensitive input that can complete the task. Confirm names, dates, amounts, permissions, sources, and destinations before sending, publishing, purchasing, deleting, or connecting anything. If a result appears incomplete, inconsistent, unusually confident, or outside the expected context, pause and verify it through an independent and authoritative source.

ZexirAI may apply technical limits, safety checks, rate controls, account verification, logging, provider routing, and human review to support this policy in relation to payment authorization. These measures reduce risk but cannot identify every mistake or misuse. A control that does not block an action is not approval, legal advice, a guarantee of accuracy, or a waiver. Users remain responsible for instructions they provide, content they choose to keep, actions they authorize, and the final use of any output.

When an exception, dispute, or unexpected result concerns payment authorization, preserve the minimum information needed to understand what happened: the approximate time, affected account, feature used, relevant settings, safe transaction or request identifiers, and a concise description of the expected and actual behavior. Remove passwords, one-time codes, full payment details, unrelated personal records, and confidential material. Contact support promptly when delay could increase harm, and use emergency or official reporting channels when the situation requires them.

We review the operation of payment authorization as the Service, models, providers, security threats, and legal requirements change. We may clarify instructions, adjust safeguards, restrict a capability, or request additional verification. Material policy changes receive notice when required. Existing non-waivable rights continue to apply. If this detailed guidance conflicts with a more specific section of this policy, the more specific section controls for that issue; the Terms and applicable law control the overall relationship.