Term and renewal
Unless a different term is set out in the order, in the proposal or in a Service-specific condition, Services are contracted for an indefinite term and renew automatically at the end of each billing cycle — monthly or annual, as contracted — until CLIENT requests cancellation.
Each renewal is accompanied by the corresponding invoice, made available in the dashboard and sent to the registered email address. The invoice is the notice of renewal and states the period to which it refers.
Cancellation may be requested at any time, through the dashboard or the official communication channels, and follows the "Contract Termination" section, including as to the effects on prepaid Services and on Services billed by consumption. Merely ceasing to use a Service does not amount to a cancellation request.
The Hours Plan follows the minimum term and the cancellation notice of section 2.5, and domain registration and renewal follow section 2.4.
Payment due date and confirmation
The applicable due date will be the date stated on the invoice and in CLIENT's dashboard. When necessary, the invoice will identify the applicable time or time zone.
For monthly recurring services, the due date will be calculated based on the billing day configured for the organization and will generally provide at least three calendar days between issuance and the due date. One-off invoices, adjustments, onboarding charges, cancellation charges or annual periods may have a specific payment term, as stated on the invoice.
A payment will be considered timely when the transaction has been effectively completed by the due date, according to the date and time reported by the applicable payment processor.
Scheduling a transaction, issuing a payment slip, generating a Pix code, presenting proof of a pending transaction or merely attempting a payment does not constitute settlement.
An invoice will be marked as paid after confirmation by the processor and full settlement of the outstanding balance, taking valid payments and credits into account. Partial payments will reduce the invoice balance but will not prevent the conditions applicable to the remaining amount from taking effect.
When a payment is effectively made on time but confirmation is received later due to operational processing by the payment processor or financial institution, the effective transaction date reported by the processor will be used to determine timeliness. Reactivation, release or renewal of services may, however, depend on UQBITZ receiving payment confirmation.
Billing notices and collection attempts
UQBITZ may send payment due reminders and delinquency notices by email, through CLIENT's dashboard and through other financial communication channels configured for the organization.
As a general rule, the standard communication schedule provides for:
- A reminder on the due date;
- A first overdue notice approximately three days after the due date; and
- A second overdue notice approximately seven days after the due date.
When an invoice relates to a service subject to automatic suspension, the second notice will state the scheduled suspension date whenever technically available. Invoices for services that are not subject to automatic suspension may receive the same reminders without a suspension date.
CLIENT may configure additional reminders before the due date when this feature is available in the dashboard.
When CLIENT selects and authorizes a recurring payment method, such as a saved card, UQBITZ may make the first collection attempt on the due date or within the preceding 24 hours. If the charge is declined, UQBITZ may make one additional attempt, generally approximately three days later.
UQBITZ will communicate a declined charge and may request that CLIENT update the card or select another payment method. Automatic collection attempts do not release CLIENT from the responsibility to monitor invoices and ensure timely payment.
Financial communications will be sent to the billing email stated on the invoice, to the persons configured to receive them or to the email registered for the organization, and may also be made available in the dashboard.
CLIENT must keep its contact information current and monitor the invoices available in the dashboard. Failure to read or receive a reminder due to an outdated address, full mailbox, spam filter, recipient configuration or any other circumstance beyond UQBITZ's control does not change the due date or extinguish the payment obligation.
Collection notices will be made in an informative and respectful manner, without exposing, threatening or embarrassing CLIENT.
Late-payment charges
An invoice paid in full within the three calendar days following its due date will be exempt from late-payment penalties and default interest.
The grace period in this clause does not change the original due date, prevent delinquency notices from being sent or modify the suspension or termination periods applicable to the service.
If an invoice remains wholly or partially outstanding after the grace period, UQBITZ may add the following amounts to the remaining principal balance:
- A one-time late-payment penalty of 2% (two percent), subject, when applicable, to the limit established by article 52, paragraph 1, of Brazilian Law No. 8,078/1990 (Consumer Protection Code); and
- Simple default interest of 1% (one percent) per month, calculated proportionally at 0.033% (thirty-three thousandths of one percent) per day of delay.
The interest rate is agreed under these Terms and will comply with the rules applicable to default under articles 389, 395 and 404 of Brazilian Law No. 10,406/2002 (Civil Code), as subsequently amended.
If the grace period is exceeded, interest will be calculated from the first day following the due date until effective settlement. Interest will not be compounded, and no interest will accrue on the penalty or on previously calculated interest.
Partial payments and valid credits will reduce the charge calculation base from the date on which they are confirmed. Calculations will be rounded to the smallest unit of the invoice currency.
UQBITZ will not charge a general administrative fee for issuing notices or internally processing delinquency. Extraordinary third-party costs may only be passed through when actually incurred, legally permitted and disclosed in advance in the applicable instrument.
Any waiver, reduction or negotiation of these charges by UQBITZ will be a discretionary concession and will not constitute a permanent amendment to these Terms or a waiver of the rule for other invoices.
Suspension for non-payment
If an invoice linked to an eligible recurring Service remains overdue and unpaid, UQBITZ may automatically suspend only the Services directly related to that charge after the period stated in the order, invoice, dashboard or financial notice. The standard schedule provides for suspension 30 (thirty) calendar days after the due date, although a Service-specific period may apply when disclosed to CLIENT.
Automatic suspension will only apply when the overdue and currently payable balance is at least BRL 10.00 (ten Brazilian reais), after confirmed payments and valid credits are taken into account. Partial payments that reduce the balance below this threshold will prevent automatic suspension based on that invoice while this condition remains.
Depending on the purchase and the link recorded in the invoice, this flow applies to hosting and application Services, managed databases, Google Workspace, UQBITZ Email, custom recurring Services and additional computing capacity. Manual invoices, one-off hours and domain registration or renewal do not trigger this automatic flow and remain subject to the specific conditions of the applicable Service, order or provider. The Hours Plan follows its own rule in section 2.5.
Until the effective suspension date, the Service will continue to be provided and billed according to its current cycle, and a new invoice for a later period may be issued. From suspension onward, ordinary recurring billing for periods beginning thereafter will stop, without releasing past-due amounts, charges, consumed usage, final invoices, taxes or irreducible commitments made to suppliers.
Depending on the nature and technical capabilities of the Service, suspension may restrict its operation, access, new deployments, support, renewal, administration or associated resources. Any temporary technical availability after the suspension date is merely operational tolerance and does not constitute a waiver of suspension or a guarantee of availability.
Suspension for non-payment does not entail immediate deletion of data. Retention, export and eventual deletion will follow the specific provisions of these Terms. The period between suspension and reactivation will not be included in availability or SLA credit calculations.
Termination after prolonged non-payment
If the debt that caused suspension remains payable, UQBITZ may commercially terminate only the Services directly linked to that charge after the period stated in the order, invoice, dashboard or financial notice. Under the standard schedule, milestones are counted from the invoice due date: suspension after 30 (thirty) calendar days, first termination notice after 60 (sixty) days, final notice after 75 (seventy-five) days and termination after 90 (ninety) days. For invoices subject to a transition rule, these milestones may be counted from the dunning anchor recorded in the system. Periods may vary by Service type when the applicable configuration is disclosed to CLIENT in advance.
The standard schedule provides for two dedicated notices: the first stating that termination and deletion are planned in 30 (thirty) days, and the final notice stating that they are planned in 15 (fifteen) days. Under any configuration, the final notice will be sent at least 15 (fifteen) calendar days in advance, state the planned effective date and provide payment and export instructions. If processing occurs after the configured milestone, the effective date will be extended to preserve the full minimum notice period.
While an open or under-review dispute or chargeback is linked directly to the invoice or to one of its payments, the invoice will be excluded from automated notice and termination processing. After resolution, the flow may resume according to the amount then payable, but an expired or materially outdated final notice will not authorize immediate termination: a new notice preserving the full minimum lead time will be issued when necessary.
Confirmation of full settlement before the effective date will prevent termination based on that charge, provided no other debt independently makes the same Service eligible for termination.
Automatic termination will also observe the BRL 10.00 (ten Brazilian reais) threshold established for suspension. If confirmed payments or valid credits reduce the payable balance below that amount, the Service will not be automatically terminated based on that invoice while this condition remains.
CLIENT must export required data before the stated effective date. Termination may start irreversible actions, including secure data deletion, destruction of managed databases and cancellation or deprovisioning of provider-maintained resources, with no guarantee of subsequent recovery. Hosting, applications, UQBITZ Email, custom Services and computing capacity without a proven automatic routine will be routed to service-specific operational processing; commercial termination does not represent that immediate technical deletion has occurred.
Manual invoices, one-off hours and domain registration or renewal remain outside this automatic termination flow; the Hours Plan follows its own rule in section 2.5. Invoices issued before the schedule became operational or kept outside the automated flow will follow the conditions and periods stated in the applicable order, invoice, dashboard or financial notice, without retroactive application of automatic termination. Past-due amounts, charges, consumed usage, taxes, irreducible commitments and financial or tax records are not discharged by Service termination.
Reactivation after regularization
After the invoice that caused the suspension has been fully settled and the payment processor has confirmed the payment, UQBITZ will automatically begin reactivating the Services directly linked to that charge. Reactivation may also occur under a formal regularization agreement expressly accepted by UQBITZ, subject to the limits and dates stated in that agreement.
Payment of one invoice will not reactivate Services linked exclusively to another charge. If another invoice for the same Service independently meets the suspension conditions under these Terms — including the applicable period and minimum outstanding balance — the Service may remain suspended until that debt is regularized.
UQBITZ will not impose an artificial waiting period or charge a general administrative reactivation fee. Restoration will begin after payment confirmation and will be completed as soon as technically possible. Services that depend on providers, infrastructure startup, integrity verification, health checks, DNS propagation or an equivalent procedure may require additional time, which will be communicated or updated through the available channels when relevant.
Payment does not override a suspension imposed for a reason other than non-payment, such as a violation of the Acceptable Use Policy, a security risk, a legal order, a preventive infrastructure measure or a valid administrative decision. In such cases, reactivation will also depend on resolving the corresponding cause.
When suspension has stopped ordinary recurring billing, the billing period in progress will be extended by exactly the time during which the Service remained suspended, counted from the suspension until the applicable effective commercial or technical reactivation. No ordinary recurring fees will be charged for that interval. The period actually used before the suspension, past-due amounts, charges, actual consumed usage, taxes, final invoices and previously disclosed irreducible third-party commitments remain payable.
After reactivation is completed, UQBITZ may send confirmation by email, through the dashboard or through another registered channel. A processing or reactivation-request message does not constitute confirmation of technical completion when the Service depends on an additional step.
Collection of outstanding amounts
Suspension and termination of a Service are contractual measures and do not discharge the debt. One-off invoices, one-off hours, domain registration and renewal and the other amounts that do not trigger the automatic suspension and termination schedule remain payable and follow this subsection.
Out-of-court collection. Once 30 (thirty) days have passed from the due date without payment, UQBITZ may pursue collection of the payable balance by the means allowed by law, directly or through a third party engaged by it, including protest of the instrument or debt document and listing CLIENT with a credit bureau.
Prior notice. Protest and listing with a credit bureau will be preceded by written notice to CLIENT, sent to the billing email and made available in the dashboard at least 10 (ten) calendar days in advance, stating the payable amount, the originating invoice, the measure intended and how to avoid it. Where CLIENT is a consumer, the notice will comply with article 43, paragraph 2, of Law No. 8,078/1990.
Dispute in progress. While a dispute or chargeback linked to the invoice is open or under review, or a regularization agreement is being duly performed, the measures in this subsection will not be taken as to the contested amount.
Clearing after payment. Once payment is confirmed, UQBITZ will have the credit-bureau listing removed and will provide the letter of consent required to cancel the protest within 5 (five) business days of confirmation, under article 26 of Law No. 9,492/1997 and Precedent 548 of the Superior Court of Justice.
Collection costs. The reasonable and documented costs of collection, including attorneys' fees, are borne by the party that caused the default, under articles 389, 395 and 404 of Law No. 10,406/2002. This subsection does not authorize a generic administrative fee, which the “Late-payment charges” subsection prohibits: only costs actually incurred and documented are passed on, and CLIENT is told of them.
In every case, collection will observe the prohibition on exposing, threatening or embarrassing CLIENT, under article 42 of Law No. 8,078/1990.
Annual adjustment
All services offered by UQBITZ are subject to annual adjustment, observing a minimum periodicity of 12 (twelve) months, counted from the start date of the contract for the respective Service or from the date of the last adjustment applied to it, in accordance with article 2, paragraph 1, of Law No. 10,192/2001. No Service will be adjusted before completing that period, and the adjustment will be applied to the first invoice issued after its end.
The adjustment index will preferably be the IGPM/FGV accumulated in the 12 (twelve) months prior to the application date. In the event of extinction, unavailability or distortion of the IGPM/FGV, it will be used, in this order: IPCA/IBGE, INPC/IBGE or Savings income.
CLIENT will be notified of the adjustment at least 30 (thirty) days in advance, in accordance with the procedures in the “Official Communications” section.
Adjustment of services dependent on third parties
Services whose cost depends on third-party providers or partners (hosting on third-party infrastructure, licenses, domains, professional email, among others) may be readjusted outside the annual periodicity, exclusively to pass on an increase actually applied by the respective supplier and limited to that increase. A Service whose supplier cost has not changed is not readjusted under this clause.
In these cases, CLIENT will be notified at least 15 (fifteen) days in advance, indicating the new value and the reason for the adjustment. Evidence of the increase applied by the supplier will be provided to CLIENT whenever requested.
CLIENT's disagreement with the pass-through follows the "CLIENT Disagreement" subsection of this section, and CLIENT may terminate the affected Service without a fine.
Hours Plan tariff adjustment
Hours Plan contracts priced below the current tariff floor may be adjusted, in addition to the annual adjustment, with prior notice and subject to the terms of the order, proposal or contract.
CLIENT Disagreement
If CLIENT does not agree with the adjustment applied, it may terminate the contract in accordance with the Contract Termination clause, without imposing a fine, as long as it manifests itself within 30 (thirty) days of notification of the adjustment. Until the effective date of termination, the adjusted values will prevail.
Taxes
Prices published on the website, in the dashboard, in proposals and in orders are expressed in Brazilian reais and include the taxes levied on providing the Service as at the purchase date, under the tax regime then applicable to UQBITZ. The invoice and the corresponding tax document itemize taxes where the law so requires.
Not included are taxes whose withholding or payment the law assigns to CLIENT, nor taxes, charges or fees owed to third parties by reason of the Service — notably the fees owed to the domain registry or registrar — which will be stated separately.
Change in the tax burden. The creation of a new tax, a rate increase, a change of tax base, the extinction or reduction of a tax benefit, a change of tax regime imposed by law and any other legislative change that alters the tax burden levied on the Service will be passed through to the price, upward or downward, limited to the economic effect actually verified and from the date the change takes effect. The pass-through is not an adjustment: it is not subject to the minimum periodicity of the “Annual adjustment” subsection, nor does it accumulate with it as to the same effect. This subsection covers, in particular, the effects of Constitutional Amendment No. 132/2023 and of the transition period it establishes.
CLIENT will be notified of the pass-through at least 15 (fifteen) days in advance or, where the legal change takes effect in a shorter period, as soon as UQBITZ becomes aware of it, stating the tax, the new amount and the start date. CLIENT's disagreement follows the “CLIENT Disagreement” subsection, and CLIENT may terminate the affected Service without a fine.