Legal

Pushfy Platform Terms of Use

This English text is a courtesy translation. In case of any divergence, the Portuguese version prevails and is the legally binding one.

Pushfy Platform Terms of Use

Version 2.0 | Updated on October 29, 2026

These Terms of Use govern access to the Pushfy platform and the contracting of its electronic communication features, including through systems integration, under the prepaid and postpaid models. The Customer must read the full document and the commercial terms presented before completing acceptance or making a purchase.

Conditions that deserve your attention

Billing corresponds to the billable event specified for each channel. The processing and forwarding of a message may give rise to a charge even without delivery, reading or a response by the recipient, as set forth in section 6. Under the prepaid model, amounts are paid in advance and consumed according to usage; under the postpaid model, authorized consumption is calculated and billed afterwards. The validity of credits, packages, monthly fees and minimum commitments depends on the conditions expressly presented at the time of contracting.

The Customer is responsible for the lawful origin of the contacts, for the content of the messages, for the necessary permissions and for the configuration of its users and integrations. Pushfy may block campaigns or suspend access in the cases set forth in section 20. The rules on cancellation and refunds are set forth in sections 21 and 22; the limitation of liability is set forth in section 28. Rights that the law prohibits from being limited remain preserved.

CREDITS AND SUBSCRIPTIONS. Monetary credits, unit packages, subscription allowances and financial guarantees are distinct in nature. Purchasing one-off credits does not activate a subscription or automatic top-up. The conditions of validity and any expiration must be disclosed before the purchase; absent an expressly contracted validity period, paid balance does not expire merely due to inactivity.

DATA AND USE OF CHANNELS. The Customer must demonstrate the lawfulness of its contact lists and obtain the permissions required by each channel. Authorization to use a contact for a given purpose does not automatically permit another campaign. Features mentioned in this document form part of the service only when actually made available and contracted.

LIABILITY. In business contracts that allow for limitation, the exclusions of damages and the indemnification cap set forth in section 28 apply, together with their exceptions. This cap does not replace the refund of balance or of undue charges and does not exclude liabilities that the law prohibits from being limited.

SUMMARY

  1. 1 Identification and scope
  2. 2 Definitions
  3. 3 Formation of the agreement and applicable documents
  4. 4 Registration and account management
  5. 5 License and features
  6. 6 Processing and consumption criteria
  7. 7 Specific conditions for channels and campaigns
  8. 8 APIs automations scheduling and webhooks
  9. 9 Permitted use and abuse prevention
  10. 10 Operational obligations of the Customer
  11. 11 Agencies integrators resale and multiple accounts
  12. 12 Optional features tests migrations and specific projects
  13. 13 Prices and common contracting conditions
  14. 14 Prepaid model
  15. 15 Postpaid model
  16. 16 Payments and billing disputes
  17. 17 Dependence on third parties and channel rules
  18. 18 Operation and support
  19. 19 Investigation of abuse complaints and legal requests
  20. 20 Suspension and protective measures
  21. 21 Term and termination
  22. 22 Balance settlement and refunds
  23. 23 Intellectual property
  24. 24 Confidentiality
  25. 25 Data protection and allocation of roles
  26. 26 Rules for processing on behalf of the Customer
  27. 27 Security and retention of information
  28. 28 Liability and its limits
  29. 29 Indemnification for acts of the Customer
  30. 30 Amendments and communications
  31. 31 General provisions and dispute resolution
  32. 32 Declaration of electronic acceptance

FULL TEXT OF THE TERMS

1 IDENTIFICATION AND SCOPE

1.1. Pushfy is made available by OMNILINK TECNOLOGIA E COMUNICAÇÃO LTDA, registered with the CNPJ under No. 65.889.259/0001-80, headquartered at Alameda Rio Negro, nº 503, Sala 2020, Barueri, São Paulo, CEP 06454-000, referred to as “Pushfy” in these Terms.

1.2. These Terms apply to all Customers and Users of the platform, subject to the services actually contracted and the specific conditions validly agreed upon. The identification of the Customer and of its representative shall be that provided at registration and in the contracting records.

1.3. The platform is intended for professional and business use. Individuals may contract only if they are over 18 years of age, legally capable and accepted at registration. The declared business purpose does not exclude the application of the Brazilian Consumer Protection Code when its legal requirements are met.

1.4. The official electronic channels for support, contractual service and privacy shall be identified on the platform and in its contracting environment. Cancellation requests or complaints may also be submitted through the customer service channel published outside the authenticated area, including when access has been blocked.

2 DEFINITIONS

2.1. “Customer” is the individual or legal entity that holds the contract and is responsible for the account. “User” is the natural person authorized to access the platform on behalf of the Customer, including administrators, employees and service providers. “Recipient” is the person to whom a communication is addressed.

2.2. “Platform” comprises the Pushfy interfaces, APIs, documentation and features made available to the Customer. “API” is the integration interface between systems. “Credentials” include passwords, API keys, tokens and other means of authentication.

2.3. “Request” is the request for an operation sent to the platform. “Billable event” is the operation or unit of consumption that gives rise to a charge under these Terms and the channel conditions. A request may contain multiple recipients or generate more than one billable unit.

2.4. “Commercial Terms” are the plan, order, proposal, price table or offer that the Customer accepts and that identifies the services, prices, billing units, payment model and other conditions applicable to the contract.

2.5. “Paid credits” represent amounts actually paid for future use of the services. “Promotional credits” are free bonuses or benefits. “Package” is the advance purchase of a specified quantity of units or capacity, with its own characteristics expressly disclosed.

2.6. “Channel providers” are carriers, gateways, communication platforms and other suppliers that take part in the forwarding and delivery of communications. “Customer Data” comprises the contacts, content, files and other information entered or processed at the Customer's instruction.

2.7. For the purposes of these Terms, the account administrator is the User authorized to manage access and settings, according to the available permissions; an administrator is not necessarily the same as the legal representative of the legal entity. Pushfy may require the involvement of the legal representative for acts that go beyond operational management.

2.8. Available balance corresponds to the amount released for new operations after applicable reserves and adjustments. Postpaid limit corresponds to the consumption exposure accepted by Pushfy and not to credit already paid. Allowance is the quantity of units or capacity included in a plan, in accordance with its usage rules.

2.9. Unless specifically indicated otherwise or a different legal rule applies, the days provided for in these Terms are calendar days. When expressly qualified as business days, these shall mean banking business days in the place of payment for financial obligations and working days in the place of performance for all other obligations. The expiration of a statutory period shall follow the relevant rule.

3 FORMATION OF THE AGREEMENT AND APPLICABLE DOCUMENTS

3.1. The contract is formed when the Customer expresses its express agreement to these Terms through an affirmative action on the platform or by another reliable electronic means, after having had access to their content. A mere visit to the website does not imply the contracting of paid services.

3.2. When accepting on behalf of a legal entity, the representative declares that he or she has sufficient powers to bind it. Pushfy may request proof of such powers and additional confirmation for postpaid contracting, change of ownership or higher-risk operations.

3.3. Acceptance of these Terms does not, by itself, contract all products, does not automatically enable the postpaid model and does not authorize undisclosed recurring charges. Additional purchases, plans and features depend on the corresponding contracting by an authorized person.

3.4. The contractual relationship comprises the accepted Commercial Terms, amendments and specific annexes made available before their contracting. The technical documentation governs the operation of the features, without creating hidden prices, penalties or contractual restrictions. The Privacy Policy describes the processing of personal data under Pushfy's responsibility and must be accessible before acceptance.

3.5. In the event of conflict, mandatory legal rules shall prevail; followed by the specific agreement or amendment expressly agreed between the parties; the Commercial Terms, as to their subject matter; and these Terms. A specific data processing agreement shall prevail on that subject. Third-party conditions bind the respective channels within the limits disclosed and legally applicable.

3.6. These Terms do not automatically revoke specific agreements already entered into with the Customer. Any change to negotiated conditions requires the mechanism provided for in the applicable instrument or the express agreement of the parties.

3.7. Pushfy may record the accepted version, its content or integrity identifier, date and time, account, identification of the representative, IP address and other proportionate evidence of authentication and expression of intent. The Customer shall have access to a storable copy of the Terms and of the contracting conditions.

3.8. The parties accept electronic means of proof of authorship and integrity as provided under Brazilian law, including article 10, § 2, of Provisional Measure No. 2,200-2/2001. This does not prevent a well-founded challenge on grounds of fraud, error, lack of authority or tampering. Any judicial enforcement depends on compliance with the legal requirements for the constitution of the enforceable instrument and of the obligation.

3.9. Before completing a purchase, plan activation or onerous commercial change, the Customer shall have the opportunity to review the essential elements presented and to correct the data entered in the respective flow. The confirmation of the contract shall make it possible to identify the Customer, the subject matter, the accepted conditions and the expression of intent that gave rise to it. Supplementary authentication records, confirmation through a registered channel and validation of powers may be requested according to the risk, without this authorizing excessive data collection. The documents of the transaction shall be considered as a whole; no unilaterally produced record shall be declared absolute or incontestable proof.

4 REGISTRATION AND ACCOUNT MANAGEMENT

4.1. The Customer must provide true, complete and up-to-date information, including registration, tax, billing and contact data, and prove its identity, activity and representation when requested on justified grounds.

4.2. Pushfy may review the registration, refuse the contract or condition activation upon verification of documents, payment capacity, lawfulness of the activity and channel requirements. The review shall comply with data protection legislation and does not authorize unlawful discrimination.

4.3. The Customer shall grant each User only the access necessary, review permissions, revoke access of departed persons and prevent the improper sharing of credentials. The use of additional authentication may be required according to the risk and the available resources.

4.4. Operations carried out by duly authorized Users and integrations bind the Customer within the limits of the permissions granted. The Customer is liable for unauthorized access resulting from security failures attributable to it; this rule does not transfer to the Customer liability for a failure attributable to Pushfy.

4.5. If there is suspicion that credentials have been compromised, the Customer shall interrupt the affected integrations where possible, change or revoke the credentials and notify Pushfy immediately. The parties shall cooperate to contain the event and investigate the operations involved.

4.6. Accounts may not be sold, assigned or transferred without Pushfy's consent. A change of ownership is subject to review and does not automatically transfer balances, credit limits or commercial terms.

4.7. Agencies, integrators and service providers operating for third parties shall disclose this status when requested, hold the necessary powers and authorizations and identify those responsible for the campaigns. Sub-accounts, resale or offering of the platform to third parties depend on express enablement. The contracting Customer remains responsible for the operations and payments under its account.

4.8. The Customer shall designate and keep up to date at least one contact responsible for account administration and for contractual communications. Administrator status, possession of a credential, payment of an invoice or control of an e-mail domain do not, in isolation, transfer contractual ownership of the account or of the Customer Data. The replacement of an administrator does not amount to an assignment of the agreement and may require proof of the Customer's representation.

4.9. Access recovery, change of the main contact and replacement of the representative may depend on proportionate verification of identity and powers, including through corporate documents or other reliable evidence. In the event of conflicting instructions or well-founded doubt as to representation, Pushfy may temporarily restrict the affected operations while it requests clarification, preserving the data and rights that are legally enforceable. Pushfy shall not decide corporate or ownership disputes between interested parties; it shall abide by the proven representation and by the decisions of competent authorities. The inability to access an old e-mail account shall not, by itself, prevent the review of other reliable means of proof.

5 LICENSE AND FEATURES

5.1. During the term of the contract and subject to compliance with the applicable obligations, Pushfy grants the Customer a limited, non-exclusive, non-transferable and non-sublicensable license to access and use the platform for its authorized activities.

5.2. The platform allows the processing and forwarding of electronic communication requests, including SMS, RCS, voice, WhatsApp and other channels that are actually made available and contracted, through its own interfaces, data upload or API integration.

5.3. Access to a channel depends on technical and commercial availability, registration or sender approval, provider rules and any specific integrations. The mention of a channel in these Terms does not guarantee that it is offered to all accounts or locations.

5.4. Pushfy acts as a provider of the technology platform for processing and intermediation. It does not operate the networks of telecommunications providers nor control the recipients' devices. This delimitation does not exclude obligations assigned to Pushfy by law or by the services it actually provides.

5.5. Query, reporting, automation, webhook, scheduling and export features shall be offered in accordance with the applicable plan and documentation. Custom development, consulting, operation of campaigns by the supplier and dedicated support require specific contracting.

5.6. Test or experimental features shall be identified as such and may have their own limits. Their use does not authorize the entry of data without a legal basis nor exclude legal security duties. Their conversion into a paid service depends on prior disclosure and contracting.

6 PROCESSING AND CONSUMPTION CRITERIA

6.1. The Customer defines recipients, content, channel, parameters, scheduling and integrations. Before confirming the send, it shall review this information, the applicable price and the consumption estimate, when available.

6.2. Unless a specific criterion has been expressly disclosed and accepted, the billable event consists of the valid processing and the effective forwarding of the request to the gateway or channel provider, evidenced by a transaction identifier or equivalent technical record. The mere receipt of an API call, without the execution of such event, does not give rise to a message charge.

6.3. After the billable event has occurred, the charge may be due even if the message is not delivered, received, read or answered, including due to filters, unavailability of the recipient or channel restrictions. If the offer adopts billing per delivery or per another outcome, the expressly contracted event shall prevail.

6.4. Requests rejected before the billable event due to validation errors, lack of balance or internal blocking shall not be charged as forwarded messages. Any standalone validation or lookup services shall be charged only if contracted separately and at a price disclosed in advance.

6.5. The billing unit may be a message, recipient, segment, category, session, voice interval or other event defined in the Commercial Terms. In SMS, the length and encoding of the text may generate multiple segments, each billable according to the applicable price table. A campaign or a visually single message does not necessarily equal a single billed unit.

6.6. RCS or WhatsApp categories, voice billing, call attempts, rounding, media and other particularities shall follow the channel rules disclosed before use. Reclassifications by third parties that affect consumption must be demonstrable and result from previously disclosed criteria, without the retroactive creation of an unknown rate.

6.7. Resends, alternative routes and automatic channel switching may give rise to additional charges only when requested by the Customer or enabled by it under known conditions. Duplicates caused exclusively by a Pushfy defect shall be corrected at no additional charge. Duplicates originating from independent requests by the Customer may be billed if actually processed.

6.8. The Customer must implement retry controls, failure handling and processing confirmation in accordance with the API documentation. The absence or delay of a response does not, by itself, mean that the request was not processed.

6.9. Status reports and notifications reflect Pushfy's own records and information from channel providers, and may be subject to delays, updates or limitations. Send or delivery status does not prove reading, the identity of the person who received it, the recipient's consent or the legal validity of a notice.

6.10. Cancellation of a campaign only reaches operations that can still be technically interrupted. Requests already forwarded and billable events that have already occurred remain subject to charges. Scheduling does not guarantee execution at an exact time and depends on the technical and financial requirements at the time of processing.

7 SPECIFIC CONDITIONS FOR CHANNELS AND CAMPAIGNS

7.1. Each channel and feature shall be governed by the accepted Commercial Terms, by the technical documentation made available, and by the rules applicable to the respective provider. The description of a feature in these Terms does not make it available to the account, nor does it waive the need for contracting, configuration, eligibility, or approval. Features intended exclusively for sending do not include receiving, handling replies, or automatic opt-out management, unless expressly offered.

7.2. When necessary to activate the contracted service, the Customer authorizes Pushfy to transmit the relevant documents and materials to the provider and to perform the technical configuration acts expressly requested. This authorization is limited to the performance of the contract and does not transfer ownership of trademarks, accounts, or data, nor does it permit the contracting of additional products on the Customer's behalf without authorization.

7.3. The Customer shall demonstrate its right to use the names, trademarks, numbers, domains, images, and other identifiers presented to recipients. Numbers or identifiers made available on a temporary or shared basis do not become the property of the Customer. Exclusivity, maintenance, portability, migration, or reservation depend on the nature of the resource, the provider's rules, legally guaranteed rights, and the conditions expressly contracted.

7.4. Enablement of accounts, senders, agents, message templates, and business segments may depend on review by the provider. The Customer shall provide truthful information and respond to relevant requests. Submission for review does not constitute approval, and Pushfy does not guarantee the timing or outcome of a third party's decision. Implementation or review costs shall be due only when previously disclosed, accepted, and related to activities actually performed.

7.5. International destinations may be used only when enabled. The Customer shall verify country codes, rates, local restrictions, and required permissions, including with respect to advertising and data protection. A telephone code, declared location, or billing address does not, on its own, prove the recipient's current location.

7.6. SMS consumption may vary according to the encoding, characters, length, and technical splitting of the content. Emojis, special characters, personalization, and links may change the number of segments. The Customer shall check the final content of each variation; simulators are estimates, unless expressly committed otherwise, and billing shall follow the previously disclosed segmentation criteria and the events actually processed.

7.7. For SMS, the way the sender is displayed, the concatenation of segments, the arrangement of messages, and the ability to reply depend on the contracted service, the network, and the device. The Customer shall not assume that all recipients will see the same presentation, nor advertise a number that cannot receive replies as if it were a customer service channel. Substantial changes to content at Pushfy's initiative require authorization, except for necessary technical adaptations previously described.

7.8. RCS operation depends on agent enablement and on the compatibility of the recipient's device, application, and network. Buttons, media, cards, and other elements may not be available in all environments. Capability checks, when offered, indicate technical conditions at the time of the check and do not guarantee subsequent availability or authorization to make contact.

7.9. For RCS agent enablement, the Customer shall provide correct business identity, brand materials, agent purpose, and contact information. Brand verification and launch on networks depend on the provider's applicable process. Material changes to brand, purpose, or operation may require a new review before use. A sender verification badge is not equivalent to legal approval of the offers or content sent.

7.10. On WhatsApp, when contracted, the Customer shall obtain and demonstrate the permissions required by the channel, maintain an accurate business profile, and comply with requests to stop communications, including those received outside the application. The Customer's acceptance of these Terms does not constitute authorization by recipients to receive messages.

7.11. On the WhatsApp channel, when contracted, the Customer shall comply with the approved templates, categories, and conditions applicable to initiating and continuing conversations, in the cases established by the provider. Template approval does not authorize use for a different purpose or for unlawful content. Templates may be re-evaluated, paused, or rejected by the provider. If automation is used, the Customer shall offer the customer service paths required by the channel.

7.12. Complaints, blocking by recipients, and policy violations may result in limitation or suspension by the provider. Pushfy may require adjustments and interrupt the affected operations. Cooperation in a request for review does not guarantee reinstatement. Neither party may circumvent restrictions by artificially switching accounts, senders, or channels.

7.13. The Customer shall handle opt-out requests and equivalent signals originating from the interfaces, replies, and events made available by the channels. For RCS, such handling shall take into account events for stopping non-essential messages, when offered. Reactivation requires a valid expression of consent for the corresponding purpose; the contact's continued presence in the contact list or a customer service reply does not, by itself, constitute new promotional authorization.

7.14. The operational allocation of opt-out management shall follow the contracted feature. When such management is the Customer's responsibility, it shall synchronize its suppression lists with all sending sources and prevent re-inclusion through import, automation, or integration. When Pushfy expressly assumes a given control, it shall perform it as contracted. The absence of an automated tool does not waive compliance with the recipient's preference.

7.15. The Customer shall keep contact lists up to date, correct invalid contacts, and suspend communications upon indications of a change in subscriber, reassignment of the number to another person, recipient error, or revocation of permission. Portability, the technical validity of a number, or a delivery status does not prove that the number still belongs to the person originally registered.

7.16. Voice features depend on contracting and shall comply with applicable rules on caller identification, calling hours, blocking, advertising, and call volume. Answering by voicemail, equipment, or a third party may generate the billable event described in the offer. Call recording, transcription, and analysis shall form part of the service only when expressly made available and contracted, and the Customer shall be responsible for defining the relevant purpose, legal basis, notices, and permissions, without prejudice to Pushfy's own obligations.

7.17. When using the service for one-time codes, authentication, or time-sensitive alerts, the Customer shall define validity periods, attempt limits, fraud protection, and fallback mechanisms appropriate to the risk. Transmission of the code does not prove identity nor prevent fraud, interception, or a change in the number's subscriber. There is no guarantee of delivery within the code's validity period, unless expressly committed, nor any authorization to use the platform as the sole means of emergency communication.

7.18. Alternative routing, retry attempts, and channel switching depend on authorized configuration and known commercial criteria. The Customer shall verify the permission required for each channel and define send conditions compatible with the purpose of the message. The absence of immediate confirmation does not demonstrate definitive failure; resend logic shall take into account late confirmations and the available duplicate controls. An error attributable exclusively to Pushfy does not authorize an additional charge.

7.19. The Customer is responsible for the lawfulness, usage rights, and security of the files, pages, and destinations it designates, including after redirects. It is prohibited to change the destination to content that is unlawful, misleading, or incompatible with the originally authorized message. Shortened links, tracking, and file hosting shall be provided only when available in the contracted service, subject to the disclosed duration and access limits.

7.20. Where tracking is used, the Customer shall provide recipients with the required transparency and comply with data protection legislation. Opens, clicks, and visits may reflect automated security mechanisms, content previews, or third-party actions. These indicators do not, on their own, prove human reading, identity, contractual acceptance, conversion, or campaign effectiveness.

7.21. Legally authorized activities may be refused by a channel whose policy does not permit certain content, segments, or purposes. Approval of registration by Pushfy does not waive eligibility with the provider. The Customer shall verify the permitted channel before purchasing a restricted-use product; Pushfy shall disclose relevant restrictions of which it is aware and that affect the contracted offer.

7.22. For the corresponding channels, the official reference policies include the WhatsApp Business Messaging Policy, at https://business.whatsapp.com/policy, and the RCS for Business Acceptable Use Policy, at https://developers.google.com/business-communications/rcs-business-messaging/terms-and-policies/aup. Pushfy will identify other relevant rules applicable to the offer. Mandatory provider updates shall be handled in accordance with the provisions of these Terms on information, amendment, and termination, without retroactive charges or suppression of legal rights.

8 APIS AUTOMATIONS SCHEDULING AND WEBHOOKS

8.1. The Customer shall use the API in accordance with the applicable documentation, protect secrets and credentials, restrict permissions, and avoid their exposure in public code, unrestricted-access applications, links, or insecure logs. API access does not authorize the use of internal interfaces, access engineering, or querying of data from other accounts. Integration addresses and permissions shall be reviewed after changes in staff, vendors, or systems.

8.2. A technical acceptance response may indicate only that a request was received or placed into processing, according to the documented status. A connection failure or lack of response does not necessarily mean that the operation did not occur. The Customer shall use the identifiers, queries, and idempotency mechanisms actually made available, handle duplicates, and limit retries, without assuming a guarantee of single execution when it is not part of the contracted specification.

8.3. When contracted or made available, webhooks shall depend on an accessible, secure endpoint correctly configured by the Customer. Events may be repeated, delayed, or received out of order, according to the documented architecture. The Customer shall verify authenticity through the mechanisms offered, handle repeated events, and protect its endpoint. Pushfy shall perform the delivery and notification attempts provided for in the applicable documentation; unlimited retention or reprocessing shall not be presumed.

8.4. The Customer shall respect documented limits on frequency, volume, size, and concurrency, implement progressive backoff for retries, and prevent automated loops between systems. Pushfy may limit requests that are excessive or that pose a risk, subject to the rules on suspension and notice. Receipt of response data does not authorize its use for incompatible purposes, improper profile enrichment, or exposure of recipients' information.

8.5. The Customer shall verify the time zone, date, validity period, and recurrence criteria of sends. Queues, traffic limitations, checks, and unavailability may change the time of processing. If necessary, the Customer shall configure a maximum useful life for the message according to the available features. Editing a scheduled send does not modify operations already forwarded nor guarantee their withdrawal from external networks.

8.6. The Customer shall review field mapping, formats, encoding, duplicates, and variable substitution rules before authorizing campaigns. An incorrect variable may change the recipient, the meaning of the communication, its length, or consumption. Import files and segmentations created by the Customer constitute its processing and sending instructions; previews and tests do not waive review of the final content.

8.7. The Customer shall point callbacks and integrations to environments it is authorized to use and prevent them from being used to probe, access, or harm internal or third-party systems. Configuration of an external address does not authorize Pushfy to access resources beyond what is necessary for the contracted integration. Technical network restrictions and accepted formats shall be disclosed in the applicable documentation.

8.8. Received messages, when that functionality is part of the contract, may contain content produced by third parties. The Customer shall validate such content before using it as an automated command in its own systems, prevent improper code execution, and limit the actions that may be triggered by a reply. Transmission of content through the platform does not constitute an instruction from Pushfy to perform external actions.

8.9. When enabling recurring automations, the Customer shall define the purpose, triggers, stop conditions, and available frequency or consumption limits. Duplicate events in the source system, circular rules, or configuration changes under its control may cause new send requests; billing shall depend on authorized and actually performed events, without prejudice to the correction of any Pushfy failure.

8.10. Technical logs may use UTC or another disclosed standard, while the interface may display local time. The Customer shall verify the time zone associated with each scheduled send and take into account legal changes in time. This difference in presentation does not alter the expressly contracted commercial period nor authorize accelerating the due date of obligations.

8.11. Pushfy may deactivate a compromised credential, limit an insecure endpoint, or require an update necessary for security, subject to proportionality and appropriate notice. Credential replacement shall preserve, where possible, the information necessary to reconcile prior operations. Authenticated access does not authorize use contrary to the permissions, the Agreement, or the law.

9 PERMITTED USE AND ABUSE PREVENTION

9.1. The Customer shall use the platform for lawful purposes compatible with the rights of recipients, with these Terms, and with the rules of the channels used.

9.2. Fraud, phishing, impersonation or sender spoofing, dissemination of malicious code, sexual exploitation, threats, harassment, unlawful discrimination, infringement of intellectual property, improper disclosure of personal data, and any content or activity prohibited by law are forbidden.

9.3. It is prohibited to send communications without the required legal basis and permissions, use unlawfully obtained lists, collect contacts by illegal means, or continue promotional campaigns against a valid objection or opt-out. The public availability of a contact does not waive the analysis of the lawfulness of its use.

9.4. The Customer shall properly identify the sender and provide a functional opt-out mechanism when required. It shall respect recipients' preferences, keep suppression lists up to date, and prevent their automatic re-inclusion. Transactional messages may not be used to disguise advertising or circumvent blocks.

9.5. The Customer shall comply with limits on frequency, calling hours, do-not-contact registries, telemarketing rules, and call identification, when applicable to the activity, the channel, and the recipient's location. Pushfy may require proof of authorizations and of the origin of contacts before releasing or maintaining campaigns.

9.6. Regulated activities, such as betting, financial services, healthcare, and electoral advertising, depend on the specific applicable licenses, authorizations, and requirements. The Customer is responsible for its regulatory compliance, the appropriateness of its advertising, and the protection of restricted audiences. Contracting with Pushfy does not constitute certification or regulatory authorization.

9.7. It is prohibited to circumvent consumption limits, anti-fraud mechanisms, anti-spam filters, recipient restrictions, or channel policies; use third-party identities or accounts without authorization; exploit vulnerabilities; overload systems; or conduct invasive testing without prior written authorization.

9.8. Pushfy may analyze signs of abuse and information strictly necessary for security, the provision of the services, or compliance with the law, subject to confidentiality and the relevant legal bases. Pushfy assumes no general obligation to review all campaigns in advance, and any review does not release the Customer from liability for its conduct.

9.9. Suspected misuse may be reported through the official customer service channels. Pushfy may request information, restrict content, and preserve evidence, observing necessity, proportionality, and the legal grounds for access and sharing.

9.10. It is prohibited to induce the recipient, by deceptive means, to disclose a password, authentication code, private key, or financial information; to simulate official communications of an entity without authorization; or to conceal the true party responsible for an offer, charge, or campaign. Legitimate authentication communications shall depend on configuration and flows compatible with their purpose.

9.11. The Customer may not send campaigns intended to publicly expose debts, embarrass recipients, exploit the vulnerability of minors, or disclose sensitive information without a legal basis. Rules on offers, debt collection, advertising, and consumer protection shall be observed according to the activity and the audience reached.

9.12. It is prohibited to use the platform to locate people, infer personal data, or test numbers and credentials in bulk without a legitimate purpose and appropriate authorization. Contact validation tools, when contracted, do not authorize unlawful enrichment of contact lists nor prove identity or consent.

10 OPERATIONAL OBLIGATIONS OF THE CUSTOMER

10.1. The Customer is responsible for the accuracy of recipients, for the rights to the content and trademarks used, for the offers and promises contained in messages, and for serving its own customers. It shall retain proportionate evidence of the legal basis, authorizations, and opt-out requests for the period necessary to fulfill its obligations.

10.2. The Customer is responsible for maintaining compatible connectivity, equipment, and systems, protecting its environments and webhooks, testing integrations, and monitoring alerts, reports, consumption, and balance. Alerts made available by Pushfy are auxiliary and do not replace these controls.

10.3. The Customer shall observe published technical limits, use supported API versions, and plan for adaptations communicated by Pushfy. Inconsistent data or misconfigured integrations may cause rejections, repeated sends, or additional consumption attributable to the Customer.

10.4. The Customer shall not use the platform as the sole means of communication for emergencies, for operations whose failure could cause harm to life, or in situations where the law requires a specific form of notification. It is the Customer's responsibility to assess the suitability of the channel and maintain alternatives when necessary.

10.5. The Customer shall export and retain the records it needs for its business within the disclosed availability periods. The platform does not constitute a permanent archiving or evidentiary custody service, unless expressly contracted.

10.6. The Customer shall retain information about the approved campaign version, its purpose, audience, and relevant authorizations, in proportion to the risk and applicable obligations. Use of an imported file does not waive verification of variable fields, duplicate contacts, and the content that will actually be presented to each recipient.

11 AGENCIES INTEGRATORS RESALE AND MULTIPLE ACCOUNTS

11.1. Use for the benefit of third parties requires the Customer to correctly identify who contracts with Pushfy, who pays for the services, and who is responsible for the campaigns and for decisions regarding the data. The creation of a sub-account does not automatically make its user or beneficiary a direct contracting party of Pushfy.

11.2. Where authorized, the management of multiple brands or customers must respect the separation of permissions, contact lists, and credentials made available by the Platform. The Customer may not share with one of its customers the contacts, reports, or secrets of another without the relevant legal basis and authorization.

11.3. A Customer that contracts in its own name to serve third parties will remain obligated to pay for the consumption authorized in its account, even if it does not receive payment from its customers. Commercial disputes between the Customer and the beneficiary of the campaign do not suspend legitimate obligations toward Pushfy.

11.4. Agencies and integrators may not promise, on behalf of Pushfy, guarantees of delivery, availability, certifications, indemnities, or conditions that Pushfy has not expressly undertaken. Commercial promotion must properly identify the supplier and comply with the authorizations for use of the brand.

11.5. Resale, offering under the Customer's own brand, and making access available to third parties will depend on specific authorization and commercial rules. Where authorized, they must preserve the use restrictions, the rights of recipients, and the security obligations; there will be no implied license to sublicense and no territorial exclusivity.

11.6. The Customer must obtain from its customers and Users the authorizations necessary for operating the channels, accessing external accounts, and the processing of personal data by the contracted chain. The Customer may not present these Terms as evidence of the recipients' consent or as a substitute for the agreement it must enter into with the data controller.

11.7. The termination of the relationship between the Customer and one of its customers or service providers does not automatically transfer ownership of the Pushfy account, the credits, or the agreements. Migration of an account, sender, or asset belonging to a third party will depend on proof of the rights involved and on the technical and contractual possibilities of the channel, with prior obligations preserved.

11.8. Where technically available, limits and reports per sub-account are internal management tools. The allocation of balance to a sub-account does not constitute a deposit in favor of a different person nor change the debtor toward Pushfy, unless expressly contracted. Expressly guaranteed spending limits will be respected.

11.9. The Customer will immediately report the loss of authority to operate on behalf of a third party and will cease the affected operations. Pushfy may suspend access related to a dispute over representation or ownership, in a proportionate manner, until it verifies the documents and adopts a secure solution, without deciding corporate or commercial disputes that depend on a competent authority.

12 OPTIONAL FEATURES TESTS MIGRATIONS AND SPECIFIC PROJECTS

12.1. The rules of this section apply only to features actually made available and contracted. Their description does not mean that they are part of all plans, that they are currently available, or that they will be developed by Pushfy.

12.2. Free trials, demonstrations, and staging environments may have limited duration, volume, recipients, or functions, which will be disclosed before use. The Customer may not create artificial registrations, false identities, or successive accounts to circumvent these conditions. The end of a trial does not imply a paid subscription without a corresponding contract.

12.3. The Customer must distinguish the test environment from the production environment. When a test involves actual forwarding to recipients or paid consumption, this condition will be disclosed; tests performed in production will be subject to the applicable billable events and prices. Fictitious or anonymized data should be preferred in staging when the use of real data is not necessary.

12.4. Import, cleansing, and migration of data will depend on the formats, limits, and scope disclosed. The Customer must keep a copy of the source data, validate samples, and check the result before deleting prior sources or starting campaigns. Validation obligations do not exclude Pushfy's liability for errors in any migration activity it has undertaken.

12.5. Implementation, custom development, assisted integration, training, or managed operation must specify deliverables, responsibilities, dependencies, schedule, price, and completion criteria in a specific contract. Requests outside the scope will depend on assessment and additional agreement; the provision of the standard license does not include unrestricted allocation of personnel.

12.6. When the execution of a project depends on access, information, approval, or action by the Customer, a delay in that dependency may justify a proportionate rescheduling, which will be disclosed and documented. Pushfy may not attribute to the Customer any delay arising from its own obligation or from a dependency that was not previously communicated.

12.7. If operational support from Pushfy is contracted for the preparation of campaigns, the Customer must approve content, recipients, scheduling, and budget through the agreed procedure. The provision of support does not transfer the decision on the lawfulness of the contact list or the offer, but Pushfy will be liable for compliance with the instructions it accepts and for acts under its responsibility.

12.8. If features for automated generation, classification, or suggestion of content are offered, the Customer must review the results before using them. These features may produce inaccuracies or inappropriate content and do not replace human review or authorization for the use of data. The contract must clarify the involvement of third parties and the relevant additional processing.

12.9. Personal data and confidential content processed on the Customer's instructions may not be used to train general-purpose models based solely on these Terms. Additional processing of this nature will depend on a specific definition of purpose, legal basis, transparency, and, where necessary, separate authorization, without overriding the rights of data subjects.

12.10. The use of automated features does not authorize fraud, deceptive impersonation, decisions prohibited by law, or sending content without review when such review is necessary. Pushfy may restrict the affected feature in the event of abuse, in accordance with the suspension and review rules set forth in this document.

13 PRICES AND COMMON CONTRACTING CONDITIONS

13.1. Prices, currency, itemized taxes, channels, billing units, discounts, monthly fees, implementation, and other charges will be presented before contracting. Unless expressly stated otherwise, amounts are in Brazilian reais. The billing of any item depends on a provision that has been disclosed and accepted.

13.2. An allowance, minimum consumption, minimum term, automatic renewal, or volume commitment will exist only when expressly provided for in the accepted Commercial Terms, with identification of its effects and of any early termination cost. The mere creation of an account does not impose minimum consumption.

13.3. The Customer may contract different models for different products or accounts, provided they are enabled. Switching between prepaid and postpaid depends on Pushfy's acceptance and on defining the treatment of existing balances and obligations. There will be no automatic extension of financial credit upon exhaustion of the prepaid balance.

13.4. New prices for future use will be communicated at least 30 days in advance, except for a more favorable period or a fixed price validly contracted. The Customer may cease new purchases or terminate the affected service before the change, subject to the treatment of the balance set forth in section 22.

13.5. Mandatory legal changes or requirements imposed by providers that demand implementation within a shorter period will be communicated as soon as they become known, together with their reasons and effects. Pushfy may suspend new operations on the affected channel until the new conditions are presented and accepted, instead of imposing retroactive charges.

13.6. Packages already purchased with a defined quantity and price will be honored during their validity period. Monetary credits will be consumed at the rates in effect at the time of the billable event, after the appropriate communication; they do not represent a guarantee of a fixed quantity of messages. There will be no retroactive price change on consumption that has already occurred.

13.7. Periodic price adjustments, when provided for, will observe the legally permitted frequency and the expressly contracted index. Volume-based discounts may only be revised in accordance with previously accepted criteria, without hidden penalties.

13.8. Before completing each purchase, the Customer must have access to a summary that allows it to verify the beneficiary account, the product, the model, the quantity or capacity, the total price, and the billing conditions. When there is a limitation by channel, destination, or category, it will be part of that summary or of the conditions linked to it. The Customer may correct the data before confirmation. Confirmation of receipt of an order does not equal credit approval or settlement of payment, and any pending item will be identified. Subsequent corrections that change price, product, or quantity will depend on new consent, without prejudice to the rights arising from a binding offer.

13.9. In recurring plans, the contract will identify the start and end of each cycle, the renewal frequency, and which components pay for access, reserved capacity, allowance, or excess consumption. Subscription amounts and usage-based amounts may coexist when this structure is expressly provided for. The statement will allow these components to be identified, including when one of them is charged in advance and another is calculated afterward. The mere purchase of one-off credits will not be treated as enrollment in a recurring subscription.

13.10. The start of billing for a subscription, implementation, or reserved capacity will follow the milestone disclosed in the contract. When it depends on activation by Pushfy, it will not be brought forward to a period in which the feature is unavailable due to a fact attributable to Pushfy. If the feature is already available and its use depends solely on a previously disclosed action by the Customer, the absence of that action will not automatically postpone billing for the expressly contracted availability or capacity. Pushfy must communicate the identified impediment and the necessary action, and may not bill as completed an implementation activity that it has not yet performed.

13.11. An allowance linked to a subscription cycle pays for the possibility of use within the contracted limits and period and will not be confused with a monetary top-up balance. Any accumulation, carryover to another cycle, use on other channels, or conversion into credits will depend on an express provision. Non-use by the Customer does not give rise to an automatic refund of the subscription for a feature actually made available, subject to the cancellation rules, failures attributable to Pushfy, and mandatory rights. Exhaustion of the allowance does not authorize paid overages if their contracting has not been previously permitted by the Customer.

13.12. Plan changes must indicate when they take effect and how the current subscription, the allowance, the features used, the credit balance, and any minimum term will be treated. Proportional or supplementary billing for an increase in capacity will depend on a demonstration of the calculation and on acceptance. A plan downgrade will not retroactively reduce rights already acquired nor create a penalty that was not contracted. When a downgrade eliminates a feature necessary for existing campaigns or integrations, the Customer will receive sufficient information to decide on their maintenance, adaptation, or cancellation.

13.13. Temporary discounts, coupons, and benefits conditioned on volume or model will have eligibility criteria, duration, scope, and stacking rules disclosed before their use. The end of a benefit may not give rise to a retroactive charge of the difference on consumption duly carried out under its conditions. A discount granted in exchange for a specific commitment may only give rise to a clawback in the event and according to the calculation previously accepted, proportionately and without duplication with another penalty. Initial disclosure of the price after the benefit does not exclude renewal or change notices that are required.

13.14. Mandatory tax withholdings must comply with the law and be accompanied by the relevant receipts. The issuance or correction of a tax document will not permit the unilateral change of the contracting party's identity or the transfer of an expense to a third party. A tax change affecting the price must be handled in accordance with the law and the rules on commercial changes, without charging taxes that are not owed or that are duplicated.

14 PREPAID MODEL

14.1. Under the prepaid model, the Customer purchases credits or packages before consumption. Use depends on confirmation of payment, the relevant anti-fraud checks, and the balance being made available. A receipt for a payment request does not equal financial settlement.

14.2. Each billable event will debit the corresponding balance. Pushfy may reserve balance for operations requested or in processing and will release any reservation that is not converted into due consumption. The statement will distinguish, where applicable, available balance, reservations, consumption, paid credits, and bonuses.

14.3. In the absence of sufficient available balance, new operations may be rejected, interrupted, or remain pending only if this possibility has been disclosed. A top-up does not imply automatic resumption of expired or canceled campaigns, unless a setting has been expressly enabled by the Customer.

14.4. Differences arising from segmentation or reconciliation of events already authorized may be adjusted with a demonstration of the records. The prepaid model does not authorize new operations without coverage: any negative balance must be linked to consumption previously requested under known criteria and may be offset against subsequent top-ups or charged separately.

14.5. The validity of paid credits or packages must be stated prominently in the accepted offer, with a clear expiration date or criterion. In the absence of express information on validity in the contract, paid credits do not expire through the mere passage of time or account inactivity. No period will be applied retroactively to an existing balance.

14.6. Where a validity period is contracted, Pushfy will disclose the batches and their expiration dates, will consume first the credits with the nearest expiration date, and will send notice at least 30 days in advance, or at the time of purchase when the period itself is shorter. Failure to give notice will prevent expiration until the applicable notice period has been fulfilled. A failure attributable to Pushfy that prevents use will extend the validity by the affected period.

14.7. The consequence of expiration, including any loss of the right of use, must be expressly disclosed in the offer and will be applied only to the extent permitted by law. The purchase of a new batch does not automatically renew the validity of previous ones. The cases of mandatory refund or refund provided for in these Terms remain preserved.

14.8. Credits are contractual rights to use services, bear no financial return, and are not intended for transfers between users, withdrawals, or circulation as a means of payment. Refunds will follow section 22. Transfers between accounts will only be permitted upon express authorization and verification of ownership.

14.9. Promotional credits will have rules and validity disclosed upon granting, will not be converted into cash, and may be canceled for proven fraud, duplication, or breach of the promotion's conditions. Their cancellation will not affect credits actually paid for without a separate basis.

14.10. Automatic top-up depends on express activation by the Customer, with indication of the trigger, amount, frequency or recurrence limit, and payment method. The Customer may deactivate it for future operations; deactivation does not undo top-ups already confirmed or legitimate debits. General acceptance of these Terms does not activate automatic top-up.

14.11. Credits or packages linked to a particular channel, product, destination, category, or reference currency will only be used within the scope for which they were purchased. Pushfy will identify this linkage and the applicable order of consumption among eligible balances, preserving the expiration priority provided for in these Terms. There will be no automatic conversion of units between channels or of a package into monetary balance by arbitrary equivalence. A conversion authorized by the Customer will depend on presentation of the rate, the effects on quantity and validity, and any financial difference.

14.12. The unit price may use decimal places beyond those of the local currency when necessary for per-event pricing. The calculation precision, the minimum unit, and the timing of rounding will be disclosed in the price table or commercial documentation accessible before use. The statement may present consolidated amounts but must allow the calculation to be verified. Per-operation roundings will not be accumulated so as to result in a charge higher than the disclosed criterion, and a rounded visual update of the balance will not change the accounting balance actually calculated.

14.13. The Customer must use its own payment method or one that it is legitimately authorized to use. Payment made by a third party does not, in and of itself, change the ownership of the account, the identity of the contracting party, or the ownership of the data, nor does it grant the payer access to the Platform or the right to direct campaigns. Pushfy may request proportionate proof of the origin and authorization of the payment when there is a material discrepancy, respecting data protection. Refunds will follow the original payment method and the checks provided for in these Terms, without presuming that any third-party payer may dispose of the Customer's data or account.

14.14. Duplicate payments, payments made with incomplete identification, or payments received after the cancellation or due date of an order will be reconciled upon proof and actual confirmation of receipt. The same amount received will not be counted more than once, without preventing the joint settlement of expressly identified purchases or obligations, and a financial duplication will not be converted into an additional purchase without the Customer's confirmation. Once an overpayment is identified, Pushfy will present the appropriate treatment of refund or credit chosen by the Customer, without imposing a new purchase. Amounts sent to a recipient other than the one officially indicated will depend on recovery from whoever received them, without prejudice to the liability of whoever caused the incorrect indication.

14.15. The automatic top-up authorization must allow identification of the authorized financial limit and maximum frequency, in addition to the balance trigger. Simultaneous requests or delayed balance updates will not expand this authorization. While a top-up is pending confirmation, a new attempt that could result in an additional purchase must respect the configured limits and duplication controls; the same payment transaction may not be recorded as multiple top-ups. The confirmation will identify the amount and the transaction, and changes to the limit or trigger will depend on action by an authorized User.

14.16. Refusal or unavailability of the automatic top-up payment method does not constitute authorization to use another payment method that has not been enabled, to exceed the accepted limit, or to convert the account to postpaid. Any new attempts will observe the conditions of the authorization and may not produce duplicate payments. Pushfy will communicate the failure through an available means and will apply the block or pending status provided for insufficient balance. Updating a card or the late release of a payment will not reactivate a top-up authorization that the Customer has already disabled; the treatment of a transaction already initiated will be identified separately.

15 POSTPAID MODEL

15.1. The postpaid model depends on Pushfy's express approval, a registration review, and the definition of the Commercial Terms. Pushfy may request documents, a specific guarantee, or advance payment of amounts. No representative or User assumes a personal guarantee by the mere acceptance of these Terms.

15.2. In the absence of a specific condition, consumption will be calculated per calendar month, from the first to the last day, according to Brasília time, and payment will be due on the 10th day of the following month. If the due date falls on a day without banking business at the place of payment, it will be extended to the next business day.

15.3. Pushfy will make available a statement with the consumption items, prices, and amount due. Tax documents will be issued in accordance with applicable law. Unless otherwise agreed, the statement will be made available within 3 business days of closing; a delay attributable to Pushfy will ensure at least 5 business days between its availability and the due date, if necessary to preserve that interval.

15.4. Credit or consumption limits may be defined per account, channel, or period. Upon reaching the limit, Pushfy may block new operations. Ordinary reductions will be communicated in advance; objective situations of fraud, default, or material deterioration of risk may justify an immediate reduction, with communication as soon as possible.

15.5. The credit limit is a control mechanism and does not represent a free allowance. Unless a hard cap is contracted, there may be a difference due to simultaneous operations or operations already authorized and in processing, which are demonstrable and calculated according to the accepted criteria. Pushfy will not use this condition to disregard a spending limit expressly guaranteed to the Customer.

15.6. Termination, blocking, or reduction of the limit does not extinguish the obligation to pay for billable events that have already occurred. Consumption reported late by the provider may be included in a supplementary statement, identified by period and accompanied by information allowing its verification, without duplicate billing.

15.7. A change of model must record the account and products covered, the cutoff date and time, the new invoicing criteria, and the treatment of campaigns in processing. Events occurring before the cutoff will be calculated under the condition that applied to them, and subsequent events will follow the enabled model, without double billing. The existence of pending orders, reservations, or information not yet reconciled will be identified in the settlement. The change does not constitute novation, discharge, or waiver of amounts legitimately owed, nor does it authorize reactivating previously canceled operations.

15.8. When changing from prepaid to postpaid, the remaining paid balance will not be extinguished: it will be kept for eligible consumption, offset against compatible invoicing, or refunded, according to the alternative expressly defined and the rules of these Terms. When changing from postpaid to prepaid, new operations will depend on available balance from the cutoff onward, and prior consumption will remain subject to the corresponding invoicing. The change will not automatically accelerate the due date of prior installments or invoices, unless validly agreed otherwise in a specific arrangement. Promotional balances and benefits linked to a model will receive the previously disclosed treatment, without affecting credits actually paid for by mere change of plan.

15.9. A guarantee, security deposit, or financial security instrument will depend on a specific contract, identifying the guarantor, amount or limit, obligations covered, duration, release requirements, and enforcement conditions. The guarantee will not be confused with credit available for sending nor will it automatically increase the consumption limit. General acceptance of the Platform does not constitute a surety, aval, personal guarantee, or authorization for unlimited debit. The existence of a guarantee does not exempt Pushfy from demonstrating the guaranteed obligation and complying with the legal and contractual procedures for its use.

15.10. The use of a guarantee must be communicated with a breakdown of the debt satisfied, the amount used, and the remaining balance, observing the cases in which notice must precede enforcement. Replenishment, renewal, or replacement of a guarantee will only be required under previously agreed conditions, with a compatible period for regularization. Its absence may limit future operations under the contracted terms, but will not authorize duplicate collection of a debt already satisfied. Once the guaranteed obligations have ended, the uncommitted portion will be released within the period established in the instrument and without indefinite retention for generic risks.

16 PAYMENTS AND BILLING DISPUTES

16.1. The Customer must pay through the methods made available at the time of contracting and keep billing information up to date. Failure to receive an e-mail does not exempt the Customer from paying an obligation whose statement is accessible, without prejudice to the correction of information failures attributable to Pushfy.

16.2. Discrepancies should preferably be reported within 10 calendar days of the statement or invoice being made available, indicating the items and the reasons. This period facilitates review and does not extinguish legal rights, does not make records incontestable, and does not prevent the correction of an error subsequently demonstrated.

16.3. The undisputed portion must be paid on the due date. In the event of a substantiated dispute, Pushfy will review the records and respond within 10 business days, or will provide a justification and a reasonable additional period if it depends on a third party. Where consumer protection law applies, a response will be provided within 5 days, without prejudice to the justified continuation of the review and to other legal deadlines. There will be no suspension for nonpayment, protest, or negative credit listing based solely on the portion under good-faith review until the substantiated response, except where there is documented evidence of abuse.

16.4. Amounts charged improperly will be corrected by reversal, refund, or credit, as chosen by the Customer when an alternative is available, subject to legal rights and deadlines. If the dispute is unfounded, the balance will become payable upon presentation of a statement and a period of at least 5 business days for payment; charges on the portion legitimately withheld during the review will not be imposed for that interval.

16.5. Unjustified late payment subjects the overdue amount to a 2% late fee, simple interest of 1% per month calculated pro rata by days of delay, and monetary adjustment by the IPCA index, from the due date, within the limits permitted by law. There will be no accumulation with another charge having the same purpose for the same period.

16.6. Pushfy may pursue out-of-court or judicial collection and resort to protest or reporting to credit default registries when the legal requirements are met, observing the required notices. Collection costs will only be charged to the Customer if legitimate, reasonable, and proven, in accordance with the law or a court order, without an automatic percentage of attorneys' fees for mere late payment.

16.7. A payment dispute with the financial institution does not automatically extinguish a legitimate debt. Pushfy may reverse credits from a transaction that is actually canceled or not settled and charge for consumption already carried out, upon review. Filing a good-faith dispute will not, in and of itself, be treated as fraud nor give rise to duplicate recovery.

16.8. Payment of a purchase in installments consists of the distribution of payment of the total contracted amount and will not be confused with a subscription renewed with each installment. The contract will state whether the credit or package will be made available in full after approval of the installment plan or in proportion to actual payments. Interest, surcharges, and conditions of the payment method will be presented before confirmation, identifying who is responsible for charging them. The cancellation of a future subscription does not, in and of itself, undo a prior purchase duly made, and the refund or cancellation of that purchase will follow its own grounds and the rules of section 22.

16.9. Payments identified for a particular invoice, top-up, account, or product will be applied to the corresponding obligation. Their allocation to another obligation will depend on specific authorization or on a valid offset provided for in the contract, with information in the statement. Pushfy will not use amounts from one legal entity to pay the debt of another merely because they belong to the same economic group, share Users, or have a common administrator, except in a case provided by law or under valid contractual authorization. The settlement of the same account upon termination will remain subject to the specific rules of section 22.

16.10. The opening of a payment dispute or chargeback may justify a temporary hold only on the credits or amounts linked to the affected transaction and not yet definitively reconciled, when necessary to prevent the use of a payment subject to reversal. The measure will be distinguished from a definitive reversal and from billing for consumption already carried out. Once settlement without reversal is confirmed, the hold will be released; once the reversal is confirmed, only the corresponding credits will be written off, with any legitimate consumption left uncovered being calculated separately. The portion unrelated to the transaction will not be withheld on this ground, except for another concrete and demonstrable cause.

17 THIRD-PARTY DEPENDENCY AND CHANNEL RULES

17.1. The delivery of communications depends on networks, providers, filters, content policies, number availability, devices, and recipients' decisions. Delivery, read, and conversion rates, latency, and commercial results are not guaranteed, unless there is an express specific commitment.

17.2. Numbers, identifiers, senders, brands, message templates, and accounts may depend on approval and maintenance before third parties. The Customer shall hold the necessary rights and authorizations, comply with the channel's requirements, and bear the consequences of violations attributable to it.

17.3. Pushfy may replace suppliers or routes to maintain operations, while preserving the essential conditions, the data protection rules, and the contracted restrictions. Such a change does not authorize any irregular international transfer, unlawful reduction of protection, or unauthorized billing for an additional channel.

17.4. Services integrated and contracted directly by the Customer with third parties are governed by their own instruments. Pushfy is not liable for failures exclusively attributable to such services. Pushfy's own engagement of suppliers does not eliminate the liabilities that the law assigns to it for its own conduct and for persons under its responsibility.

17.5. Suspensions or terminations imposed by providers may affect specific channels. Pushfy will communicate the known effects, cooperate toward an appropriate solution, and apply the termination and refund rules to any service that cannot continue, without promising the reversal of any decision that depends on a third party.

18 OPERATION AND SUPPORT

18.1. Pushfy shall make the contracted resources available, process the authorized operations, maintain the relevant records, and exercise technical diligence compatible with the nature of the service. The absence of a delivery guarantee does not exclude the duty to correctly perform the activities under its responsibility.

18.2. Support will be provided through the channels and during the hours indicated for the plan. A response time is not equivalent to a resolution time. Continuous support, minimum availability, service levels, and compensation credits depend on specific contracting and, when provided for, will be honored.

18.3. Pushfy may perform preventive, corrective, or evolutionary maintenance. Scheduled interventions with relevant impact will be communicated with reasonable advance notice; urgent security or continuity measures may take place without prior notice, with subsequent information whenever possible.

18.4. Features and versions may evolve. The withdrawal of an essential functionality of a contracted service or an incompatible API change will be communicated at least 30 days in advance, whenever technically possible, together with migration guidance. Urgent legal or security situations may require a shorter period. If the change materially renders the contracted service unfeasible, the alternatives and refunds set forth in section 22 apply.

18.5. Estimates, informational materials, and test results do not constitute a guarantee of performance in all environments. Objective information in the accepted offer and Pushfy's written commitments remain binding under the law.

18.6. Support that depends on access to the Customer's environment or data will be limited to the scope necessary for the request and to the authorized means. The Customer shall not send personal passwords or permanent credentials to support; when necessary and technically available, temporary access or dedicated authorization mechanisms may be used. Authorization to investigate a problem does not permit unrestricted access to campaigns, systems, or accounts unrelated to the support request. Containment actions necessary for security or legal compliance will rest on their own legal basis and observe the applicable limits.

18.7. The Customer shall provide support with sufficient information to reproduce the problem, such as the operation identifier, time, channel, and a description of the observed behavior, without providing excessive data. Pushfy may prioritize incidents according to severity and impact, request relevant tests, and distinguish its own failure from a usage question or an external integration defect. Support does not include legal advice or regulatory validation of the campaign, unless specifically and compatibly contracted.

19 INVESTIGATION OF ABUSE REPORTS AND LEGAL REQUESTS

19.1. Pushfy may receive reports from recipients, rights holders, channel providers, and authorities concerning campaigns, content, or accounts. The investigation will take into account the severity, urgency, consistency of the evidence, and the applicable legal duties, without presuming that every report is true.

19.2. The report shall identify, to the extent possible, the content or operation in question, the channel, the approximate date, the reason, and elements that allow it to be located. The absence of any element does not prevent measures that are legally mandatory or necessary in the face of an identifiable risk. Pushfy will not require disproportionate data in order to receive a report.

19.3. The Customer shall cooperate with justified requests for clarification, providing, where relevant, sender identification, the origin of the contact list, usage permissions, evidence of consent or another legal basis, and proof of licenses. The request will indicate its subject matter and a deadline compatible with the risk, and may be fulfilled through extracts, samples, or documents with unnecessary data redacted.

19.4. While investigating a consistent indication, Pushfy may pause a campaign, restrict volume, disable credentials, withhold new operations, or suspend the affected channel in accordance with the contractual protection rules. These measures do not represent a definitive acknowledgment of a violation and will be reviewed when the cause is clarified or ceases.

19.5. The Customer may submit clarifications and request a review through the official channels. Pushfy will evaluate the additional elements and report its conclusion or the possible actions, subject to legal and security limitations. A decision by an external provider that is outside Pushfy's authority cannot be reversed by a unilateral guarantee from Pushfy.

19.6. Pushfy may preserve specific records necessary for the investigation, the exercise of rights, or compliance with a valid order, with restricted access and for a justifiable period. Such preservation does not grant unrestricted access to the content of communications and does not authorize the indiscriminate retention of the Customer's entire contact list.

19.7. Requests from authorities will be analyzed as to their authenticity, competence, legal basis, and scope. Pushfy will provide only the data it may legitimately disclose and will adopt the legally required measures, subject to matters reserved to judicial authority and to applicable confidentiality. Informal requests from third parties do not replace the legal requirements for access.

19.8. When legally permitted and without prejudicing an investigation or risk containment, the Customer will be informed of any measure that materially affects its account or its data. The duty to communicate does not require disclosing detection techniques, information about other customers, or the protected identity of reporting parties.

19.9. No provision obliges Pushfy to execute an unlawful instruction, to allow an irregular campaign to continue, or to challenge every valid order on the Customer's behalf. The Customer may exercise its own means of defense, and extraordinary technical cooperation will depend on a previously agreed scope and conditions, without conditioning compliance with an urgent legal duty on payment.

19.10. The willful use of the reporting channel to harm third parties, conceal fraud, or improperly obtain data is prohibited. Liability for an abusive report depends on demonstration of the legal requirements, preserving the right to submit a report in good faith and to request protection or review.

20 SUSPENSION AND PROTECTIVE MEASURES

20.1. Pushfy may suspend a campaign, channel, credential, or account, to the extent necessary, in the event of consistent indications of fraud or unlawful use, security risk, abuse of resources, serious violation of channel rules, an order from an authority, or an urgent need to contain damage.

20.2. For non-payment, suspension may occur after a delay of more than 5 calendar days and prior notice to the Customer with an opportunity to cure. Insufficient balance in the prepaid model and reaching a consumption limit permit the blocking of the corresponding new operations, regardless of that period. The safeguards of section 16 apply to the portion disputed in good faith.

20.3. For curable violations without urgent risk, Pushfy will notify the Customer and grant at least 5 business days for correction, or a period compatible with the nature of the problem. Serious non-compliance, recurrence, or the impossibility of cure may justify termination.

20.4. The notice will identify the reason and the applicable measures, subject to legal restrictions, investigative confidentiality, or information whose disclosure would compromise security. Pushfy will make available a channel for review of the measure and will analyze the clarifications submitted.

20.5. During the suspension, new operations covered by the block will not be processed. Prior consumption and the charges for resources actually maintained at the Customer's request or by express provision of the contract remain due. There will be no billing for fictitious consumption or for any service that ceased to be provided due to a failure attributable to Pushfy.

20.6. Suspension does not entail the automatic loss of paid credits, the confiscation of data, or authorization for the indefinite retention of amounts. Reinstatement may depend on correction of the cause, payment of amounts due, and proportionate security checks or provider approval.

21 TERM AND TERMINATION

21.1. These Terms are in effect from acceptance and for as long as there is an active account or pending obligations. Unless a specific term is contracted, the relationship is for an indefinite period. A minimum commitment period or plan renewal depends on express information in the Commercial Terms.

21.2. The Customer may request termination through the means made available on the Platform or through official customer service. The request shall generate a confirmation or ticket number and identify the effective termination date. Uninstalling an integration, inactivity, or stopping sends does not, by itself, cancel a contracted recurring plan.

21.3. In the absence of an accepted specific term, cancellation prevents further renewals from its receipt and allows the Customer to choose to stop using the service immediately or to keep using it until the end of the period already paid. Consumption already authorized and resources the Customer chooses to keep until that date will be calculated normally.

21.4. If a minimum commitment period has been validly contracted, any early exit charge shall be clearly provided for, be proportionate to the benefit granted and to the remaining period, and observe legal limits. There will be no generic penalty for canceling an account without a specific commitment.

21.5. Pushfy may terminate the contract for convenience upon 30 days' notice, subject to any different contractual or legal period, ensuring financial settlement and a reasonable opportunity for export. Termination for violation will follow section 20. Either party may terminate the contract for material breach by the other, after a cure period where applicable.

21.6. Upon termination, the licenses and new operations cease, the relevant credentials will be revoked, and pending consumption will be calculated. The Customer shall cancel integrations and scheduling under its control. The provisions on payment, refund, confidentiality, data protection, intellectual property, and liability survive for the period in which they apply.

21.7. For 30 days after termination, Pushfy will make available a reasonable means of requesting the export of Customer Data that still exists and is exportable, in an available format, after verification of ownership. Technical, security, or legal restrictions may change the form of delivery, without overriding rights guaranteed by law. The export window does not represent a guarantee of retention of records whose regular retention period has already ended.

21.8. The cancellation request will identify whether it covers the entire account or only a subscription, channel, number, resource, or contracted unit. Partial cancellation will not automatically terminate independent services that the Customer has chosen to keep. Before the request is confirmed, the known effects on bundled benefits, integrations, allowances, and dependent resources shall be disclosed, as well as the remaining charges that legitimately apply. The technical impossibility of maintaining an essential component on its own shall be explained and will not authorize continued billing for a service that cannot be provided.

21.9. The termination confirmation shall identify the treatment of automatic renewals and top-ups associated with the canceled service, of scheduled sends, and of requests still pending. After the effective termination date, new integration attempts will not renew the contract or reactivate payment authorization, and reopening will depend on a request from an authorized person. Requests made after the revocation of credentials will be rejected in accordance with the documentation, without being billed as messages merely because they were received. Prior operations that can no longer be stopped will remain subject to the contracted consumption criterion and to the final statement.

21.10. The contractual export will comprise Customer Data that exists, is legitimately accessible, and is technically exportable in the service used. It does not include the assignment of source code, algorithms, internal credentials, architecture, data of other customers, or third-party information whose delivery is prohibited. Custom formatting, reconstruction of data already deleted, assisted migration, and integration with the destination system will depend on feasibility and specific contracting, without restricting legal rights of access or portability. Pushfy will not require settlement of a debt in order to fulfill a data subject's right or any other delivery required by law.

21.11. A request for the export or sharing of data shall identify the authorized representative, the requested scope, and the recipient of the delivery. Pushfy may require additional confirmation when the request involves the entire contact list, a new recipient, or a relevant change of contact details. The designation of a User or service provider as account administrator does not, by itself, authorize that person to receive the data in their own name after their powers have ended. After delivery to the legitimately designated recipient, the Customer shall be responsible for ensuring the protection and lawful use of the copy under its control, without excluding liability for a failure attributable to Pushfy in the delivery.

21.12. Inactivity may give rise to a communication for updating registration information or a proposal for administrative termination, but will not automatically extinguish paid balance or export rights. If Pushfy decides to terminate an inactive account for convenience, it will observe the notice and settlement provided for in this section. The deactivation of a free account with no balance will also be preceded by reasonable notice when there is data whose retention or export is contractually owed, subject to legally justified urgent measures.

22 BALANCE SETTLEMENT AND REFUNDS

22.1. Amounts relating to correctly executed billable events will not be refunded merely because the message did not achieve a commercial result, a read, or a delivery not contractually guaranteed. Corrections for failures attributable to Pushfy, undue charges, and other legal rights will be preserved.

22.2. Upon termination, a settlement will be made between paid credits that are still valid and unconsumed, released reserves, and obligations that are due and demonstrated. For purposes of this settlement, the Customer also authorizes the deduction of consumption actually incurred whose original due date would fall later, provided that it is itemized in the termination statement. Promotional credits are not part of the refund. The existence of a pending dispute or reconciliation does not authorize the retention of amounts greater than the portion justifiably in dispute or reserved for identified events.

22.3. Except for a valid specific condition clearly accepted for a package or reserved capacity, the paid balance that is still valid and unconsumed will be refunded at the Customer's request, less only legitimate obligations and non-recoverable external payment costs that have been previously disclosed and substantiated. Validity will be determined in accordance with clauses 14.5 to 14.7, without prejudice to mandatory refunds. There will be no generic administrative fee or automatic retention of the entire balance.

22.4. Specific non-refund conditions for business withdrawal may only reach the portion linked to a benefit, service, or capacity actually contracted and made available, to a proportionate extent permitted by law. They do not exclude refunds for breach attributable to Pushfy, undue charges, discontinuation without an equivalent alternative, or any mandatory consumer right.

22.5. If Pushfy terminates for convenience, permanently discontinues a paid service, or changes an essential condition in a way that renders its use unfeasible and the Customer does not accept an equivalent alternative, Pushfy will refund the unused paid balance and the prepaid portion of services not rendered, without a cancellation fee or deduction of payment costs. The same rule applies to an exit motivated by a rate increase on monetary balance not yet consumed, requested before the increase takes effect.

22.6. Contractual refunds will be processed within 30 calendar days of the request and of receipt of the data strictly necessary to confirm ownership, through a means compatible with the original payment. Pushfy will report the processing and any external period of the financial institution. More favorable legal periods and procedures prevail.

22.7. Where the Brazilian Consumer Protection Code applies, the right of withdrawal within 7 days, counted as provided in art. 49, is guaranteed for contracts covered by that provision. The request may be made electronically, with confirmation of receipt and immediate return of the amounts, monetarily adjusted, as provided by law; the 30-day contractual period of the preceding clause does not apply to this right. Acceptance, the purchase of credits, or the start of use do not constitute an automatic waiver of this right. The deduction and non-refund rules of this section do not restrict mandatory legal rights.

22.8. No refund will be paid to a third party unrelated to the contract without adequate justification and verification. Retention for fraud investigation shall be substantiated, limited to the affected amount and to the period necessary for the investigation or for compliance with a legal order, with information provided to the Customer when permitted.

22.9. If an amount is justifiably reserved for reconciliation upon termination, the statement will identify the events, the substantiated estimate, the reason the matter is pending, and the estimated completion date. The reserve will be reviewed as new information arises and released to the extent it is no longer necessary. The abstract possibility of future billing, a third-party penalty, or a complaint without concrete elements does not authorize retention of the entire balance. The undisputed portion to be refunded will observe the applicable period, even if another portion remains under review, and the retention may not be extended indefinitely merely because of a lack of response from a supplier.

22.10. The refund of a partially used package or of a discounted purchase will take into account the price actually paid and the criterion for allocating value among its components disclosed at the time of contracting. In the absence of a specific criterion, a verifiable proportion between the remaining eligible units and the paid units of the same package will be used, without converting free bonuses into cash. Pushfy will not retroactively reprice units already consumed at the standalone rate in order to reduce the refund, except for an expressly agreed, valid, and proportionate recovery of benefits. Reserved capacity products will be calculated in a manner compatible with their nature and with clause 22.4, without artificially equating them to message units.

22.11. The refund shall identify the purchase or installment to which it refers and any reversals, offsets, or chargebacks already made on the same amount. In an installment purchase, the reversal order will reflect the amount actually refundable and the treatment adopted by the payment method, avoiding duplicate refunds or continued charges on an installment already canceled. If the original method does not allow a refund, the parties will use a secure alternative after confirmation of ownership and recording of the substitute payment. The need to reconcile the payment method does not authorize reducing the right to a refund or overriding a mandatory legal period.

23 INTELLECTUAL PROPERTY

23.1. The Platform, its code, architecture, interfaces, documentation, trademarks and other technological elements belong to Pushfy or its licensors. Contracting the services does not transfer ownership or grant access to the source code.

23.2. It is prohibited to copy, distribute, sublicense, commercialize, modify or exploit the Platform beyond the authorization granted, to remove ownership notices, to access unauthorized areas or to carry out reverse engineering in violation of the law. Regular integration through the API and legally non-waivable rights remain preserved.

23.3. The Customer retains the rights to its content and data and grants Pushfy a limited authorization to host, technically reproduce, transmit and process them to the extent necessary for the performance of the Agreement and compliance with the law. This authorization does not permit the commercialization of contact lists or the use of campaign content in Pushfy’s own advertising.

23.4. The use of the Customer’s name, trademark or logo by Pushfy as a commercial reference depends on specific authorization. Identification of the sender in the channels themselves and in operational documents may occur when necessary for the contracted service.

23.5. Voluntary suggestions for improvement may be used by Pushfy without remuneration, provided that this does not transfer rights over confidential information, personal data or third-party materials. Submitting a suggestion does not authorize disclosure of trade secrets.

23.6. The Customer may not use restricted documentation, third-party credentials or information obtained through improper access to reproduce protected components of the Platform, extract trade secrets or allow unauthorized access by competitors. This prohibition does not prevent lawful competition, independent development or duly authorized integration.

23.7. Third-party libraries, connectors and components may be subject to their own licenses as identified in their documentation. Pushfy’s license does not alter the rights and obligations under those licenses, nor does it grant the Customer powers over assets that depend on authorization from the respective owner.

24 CONFIDENTIALITY

24.1. Each party shall protect the other party’s non-public information to which it has access by reason of the contracting, including credentials, campaign content, contact lists, non-public commercial terms, restricted documentation and technical or strategic information.

24.2. Confidential information shall be used solely to perform the contracted services, exercise rights or comply with the law. Access shall be restricted to persons who need to know it and are subject to compatible confidentiality duties, with proportionate protective measures.

24.3. The obligation does not cover information that is demonstrably public without breach, legitimately known prior to receipt, lawfully obtained from a third party without restriction or independently developed. Mandatory disclosure shall be limited to what is necessary, with prior notice to the other party where permitted.

24.4. Confidentiality shall survive for 5 years after termination. Trade secrets shall remain protected for as long as they retain that nature, and personal data and credentials shall be subject to protection for the legally applicable period, even after that term.

25 DATA PROTECTION AND ALLOCATION OF ROLES

25.1. The parties shall comply with the Brazilian General Data Protection Law (LGPD), the Brazilian Internet Civil Framework (Marco Civil da Internet) and other applicable rules. The role of controller or processor shall be determined by the decisions actually made in each processing operation, and not merely by the contractual designation.

25.2. With respect to the contacts, content and campaigns defined by the Customer, the Customer acts, as a rule, as controller, and Pushfy as processor, to the extent that it processes data according to the Customer’s instructions. If the Customer acts as a processor on behalf of a third party, it must be authorized to engage Pushfy and to transmit lawful instructions from the competent controller.

25.3. Pushfy may act as controller in processing operations whose purposes it determines, such as registration management, authentication, billing, tax obligations, fraud prevention, security and defense of rights, in accordance with the legal bases and information in the Privacy Policy. Each party shall be responsible for responding to data subjects and for other obligations in the processing operations under its responsibility.

25.4. The Customer shall define and document appropriate legal bases, provide information to data subjects and obtain consent when required. This contractual acceptance does not replace consent or any other legal basis necessary for processing recipients’ data and does not constitute a general authorization for any use of personal data.

25.5. The Customer shall limit data to what is necessary and avoid entering sensitive data, data of children or adolescents and high-risk information in free-text fields or messages, unless the service is suitable and there is a legal basis and appropriate safeguards. Processing that requires specific configuration or agreement shall depend on its implementation before sending.

25.6. The Privacy Policy may not unilaterally expand the use of Customer Data processed under instruction. The Customer may discontinue future instructions or terminate the contracting, without preventing processing necessary for compliance with a legal obligation or the regular exercise of rights.

25.7. When the Customer relies on consent or on an authorization required by the channel, it shall retain evidence that makes it possible to link the expression of will to the data subject, the purpose, the sender and the time it was obtained, without presuming that authorization given to a third party or for another purpose covers the current campaign. List changes, imports and integrations shall respect valid opt-out requests and restrictions already identified. Proof may be requested to an extent proportionate to the campaign under investigation, safeguarding data that is not necessary for the analysis.

25.8. When providing files, screenshots, message samples or records for support, demonstration or dispute purposes, the Customer shall limit the material to what is necessary and conceal personal data and secrets unrelated to the request, whenever feasible. Pushfy shall use such material for the purpose for which it was provided and for related legal obligations, subject to the roles actually performed. Sending a sample does not authorize the commercial exploitation of the corresponding contact list or access to the remainder of the Customer’s systems.

26 RULES FOR PROCESSING ON BEHALF OF THE CUSTOMER

26.1. Processing by Pushfy as processor has as its purpose the performance of the contracted communications and functionalities during the relationship and for the period necessary for orderly termination. It may include receiving, organizing, storing, consulting, transmitting, logging events, making reports available and deleting data.

26.2. Data subjects may include recipients, customers, employees and representatives of the Customer. The data may include name, telephone number, channel identifiers, content provided, campaign parameters, times, status and other elements strictly necessary for the functionalities used. Additional categories shall depend on lawful and compatible use by the Customer.

26.3. These Terms, the Commercial Terms, the configurations and regular requests constitute the Customer’s documented instructions. Pushfy shall not use data processed as processor for incompatible purposes of its own, nor expand the scope by unilateral decision. An apparently unlawful instruction may be suspended, with notice and a request for clarification.

26.4. The Customer authorizes the engagement of sub-processors necessary for hosting, infrastructure, support and processing, subject to compatible data protection and confidentiality obligations. Pushfy shall make available, through an official channel, up-to-date information on relevant sub-processors, their functions and the countries of processing. Providers that autonomously determine purposes may act as independent controllers, according to their actual activity.

26.5. The addition or material replacement of a sub-processor shall be communicated with reasonable advance notice, whenever possible. The Customer may submit a reasoned data protection objection within 10 calendar days of the communication. The parties shall seek a feasible solution; if none exists, the Customer may terminate the affected service without penalty for that reason, with settlement of unused amounts. Urgent security measures may precede the notice.

26.6. International transfers shall only take place with a valid mechanism provided for in the LGPD and in the regulations of the ANPD (Brazilian Data Protection Authority), including appropriate contractual clauses, an adequacy decision or another effectively applicable legal ground. Acceptance of these Terms is not treated as general consent of all data subjects to international transfers.

26.7. Pushfy shall assist the Customer, reasonably and within its role, in responding to data subject requests, impact assessments and requests from authorities. Requests received directly by Pushfy as processor shall be forwarded to the Customer, except where Pushfy has its own obligation to respond or is legally prevented from doing so.

26.8. Upon a reasoned request, Pushfy shall provide reasonable information to demonstrate compliance with processing obligations. Additional audits, when necessary, shall be coordinated in advance, with proportionate scope, confidentiality and access, without exposing data of other customers or compromising security. Legal rights of inspection shall not be restricted.

26.9. Costs of extraordinary support or audits requested by the Customer shall depend on a prior quote and agreement. No charge shall be made to remedy a breach attributable to Pushfy, nor shall compliance with an urgent legal obligation be conditioned on payment of a quote.

26.10. Additional processing instructions shall be submitted by an authorized person, identify their subject matter and respect the contracted functionalities and the law. Pushfy may request clarification regarding instructions that are incomplete, incompatible or that involve significant risk. Development, data conversion, architecture changes or processing substantially different from what was contracted shall depend on a feasibility assessment and prior adjustment of scope and price, where applicable. This requirement shall not condition compliance with Pushfy’s own legal obligation, a mandatory urgent measure or the remedy of a breach attributable to Pushfy.

26.11. Responding to a request for access, correction, deletion or portability may require proportionate verification of the identity of the requester, of their representation and of the scope of the request, in order to prevent improper disclosure or alteration of data. Documents that are excessive or irrelevant to such verification shall not be required. When acting as processor, Pushfy shall follow lawful instructions from the competent controller, without preventing any action directly imposed on it by law. Verification does not authorize charging the data subject for the regular exercise of their rights or extending a legal deadline for mere administrative convenience.

26.12. The authorization to subcontract does not permit a sub-processor to use the data for purposes of its own that are incompatible with the service, nor does it transfer to the Customer the management of the suppliers chosen by Pushfy. Pushfy shall require that access by its personnel and sub-processors to data processed on its behalf observe functional need, applicable instructions and confidentiality and security duties. The liability of each agent shall follow its actual conduct and the law; the mere designation of a third party as independent shall not exclude liability that the law attributes to Pushfy.

26.13. When an international transfer is based on the ANPD’s standard contractual clauses, the exporter and importer involved shall adopt them in full and complete the required information, in accordance with the regulations in force. The reference to such clauses in these Terms does not replace their formalization in the relevant instrument, nor does it, on its own, prove the lawfulness of a transfer. Legally required information about the agents, purposes, countries and applicable safeguards shall be made available through the appropriate channels, safeguarding protected secrets and the rights of data subjects.

27 SECURITY AND RETENTION OF INFORMATION

27.1. Each party shall adopt technical and administrative measures proportionate to the nature of the data and the risks, including access control, credential management, protection of communications and incident response procedures, to the extent of its responsibilities. No system is immune to incidents, but this does not exclude the duty of prevention and diligence.

27.2. Upon becoming aware of an incident involving data processed on behalf of the Customer, Pushfy shall notify the Customer without undue delay, with the information then available and in time to allow the controller to fulfill its legal duties. The initial notice shall not depend on the conclusion of the investigation and may be supplemented.

27.3. The incident notice shall indicate, as known, the nature of the event, the categories of data and data subjects affected, the risks, the containment measures and a contact for follow-up. The parties shall cooperate to preserve evidence, mitigate damage and prevent improper disclosure of security information.

27.4. Each controller shall make the notifications to the ANPD and to data subjects that are incumbent upon it, within the legal and regulatory deadlines. The other party’s cooperation does not automatically transfer this obligation, nor does it prevent action required directly by law or by a competent authority.

27.5. Data and records shall be retained for the time necessary for the purposes disclosed, the performance of the Agreement, legal obligations and the regular exercise of rights. Application access logs shall be kept for the applicable legal period, including the 6-month period under art. 15 of the Marco Civil when its requirements are met; this period does not constitute a promise to store the entire content of messages.

27.6. Operational availability periods for messages, files, reports and exports shall be disclosed on the Platform or in the documentation. Reductions affecting existing data shall be communicated with reasonable advance notice to allow export, except where required for legal or security reasons.

27.7. Once processing under the Customer’s instruction has ended and export arrangements have been completed, the data shall be deleted or anonymized, except for lawful and necessary retention. Backup copies subject to an overwrite cycle shall remain protected and without ordinary operational use until their deletion, in accordance with the disclosed retention policy. Data retained for a lawful purpose of Pushfy’s own shall be subject to Pushfy’s obligations as controller.

27.8. Statistical information may only be used in aggregated and effectively anonymized form, without reasonable identification of data subjects or disclosure of the Customer’s confidential information. Pseudonymization or the mere removal of the name does not, in itself, amount to anonymization.

27.9. The Customer shall maintain a contact capable of receiving urgent security communications and shall inform Pushfy, without undue delay, of any compromise of an account, integration or environment under its responsibility that may affect the Platform or the data processed on it. The communication shall include the available elements useful for containment, avoiding the transmission of sensitive data, credentials or unnecessary full content through an inappropriate channel. The lack of complete information shall not prevent the initial communication nor waive its supplementation when relevant new elements become known.

27.10. Notification of an incident, adoption of preventive measures or cooperation with its investigation do not, in themselves, constitute an admission of fault, causation or an obligation to indemnify. The investigation shall take into account the facts, the records and the responsibility of each agent. This rule does not authorize delaying mandatory communications, omitting legally required information or conditioning cooperation on the waiver of rights, the signing of a release or the advance payment of disputed expenses.

27.11. Technical information made available for the investigation of an incident may be limited, masked or organized so as to protect data of other customers, credentials, security secrets and materials subject to confidentiality. Relevant reports or extracts may be used when sufficient for the purpose. A request for investigation does not authorize direct access to the infrastructure, indiscriminate collection of records, penetration testing or exploitation of vulnerabilities without specific authorization. These measures may not be invoked to prevent access or inspection guaranteed by law or by a competent order.

27.12. If data is restored from backup copies for operational recovery, each party shall, within the scope under its control, reapply the restrictions, exclusions and opt-out preferences that remain relevant before resuming ordinary use. Restoration does not authorize reusing a contact list that has lost its legal basis, reactivating a canceled campaign or reinstating withdrawn consent. This provision does not represent the contracting of individual file recovery, a specific restore point or a guarantee of full recovery of data not covered by the contracted service.

28 LIABILITY AND ITS LIMITS

28.1. Each party is liable for proven damages arising from a breach attributable to it, subject to causation, applicable law and validly established limits. The injured party shall take reasonable measures to prevent the damage from worsening.

28.2. Pushfy is not liable for an unsuccessful result arising exclusively from content or data provided by the Customer, improper configuration of the Customer's systems, a security failure in an environment under the Customer's responsibility, refusal by the recipient, or an external event that constitutes a legal ground for exclusion of liability. The mere involvement of a third party is not sufficient to exclude Pushfy's legal liability.

28.3. In business relationships in which limitation is lawful, loss of profits, loss of business opportunity, indirect damages and loss of expected revenue arising from the use or unavailability of the platform are excluded. This exclusion does not apply where the law requires the corresponding compensation or in the cases expressly reserved below.

28.4. In those same relationships, and subject to the exceptions in this section, Pushfy's liability for damages for the same event or for a directly related series of events shall be limited, in the aggregate, to the amount of the services actually paid or owed by the Customer in the 12 months preceding the first event that gave rise to the respective claim. For more recent engagements, the period actually elapsed shall be considered. Top-ups not yet consumed are not included in the remuneration considered in this calculation. If there was no remuneration in the period, the monetary cap in this clause does not apply; the other valid legal and contractual criteria for determining liability remain in effect.

28.5. The limit does not extend to the return of balance, the reversal of an improper charge or the refund of a service not rendered; damages arising from willful misconduct, fraud or gross negligence by Pushfy; damages to life or physical integrity; or liabilities whose exclusion or limitation is prohibited by law. It does not limit the rights of data subjects, the powers of authorities or mandatory legal liability toward third parties.

28.6. With respect to confidentiality and data protection, any limitations between the parties shall apply only to the extent legally permitted, without excluding duties of security, cooperation, mandatory legal compensation or liability for the acts of persons under a party's responsibility.

28.7. Service credits provided for in a service level agreement do not exclude legally mandatory compensation, any applicable refund or the exceptions above. There shall be no double compensation for the same loss that has actually been redressed.

28.8. Acts of God or force majeure shall exclude liability only to the extent permitted by law and with respect to their unavoidable effects. The affected party shall give notice of the event when possible and take reasonable continuity and mitigation measures. A foreseeable failure that should have been avoided through the required diligence shall not automatically be treated as force majeure.

28.9. Where validly applicable, the contractual liability cap shall apply in the aggregate to claims by the same Customer arising from the same event or from a directly related series of events, without multiplication by reason of the number of campaigns, invoices, Users, legal grounds or requests made. This rule does not artificially aggregate independent facts, does not extend the cap to situations already excluded from its application and does not restrict the autonomous rights of data subjects or of third parties not subject to the limitation. Refunds and the other exceptions provided for in these Terms remain outside the cap within the established limits.

28.10. The Customer's duty to maintain copies, controls and alternative routes does not constitute an automatic release of Pushfy. In determining any loss, the causal contribution of each party, the mitigation measures reasonably required and the liabilities that the law does not permit to be excluded shall be taken into account.

29 INDEMNIFICATION FOR ACTS OF THE CUSTOMER

29.1. The Customer shall reimburse Pushfy for actual and proven losses arising from third-party claims caused by unlawful content, unauthorized use of data, infringement of rights, fraud or any other violation attributable to the Customer, its Users or persons under its responsibility.

29.2. The reimbursement may include judgments, previously approved settlements and reasonable defense expenses, in proportion to the Customer's involvement in the event. It shall not cover any portion arising from an act or omission of Pushfy, its employees or suppliers under its responsibility, nor any penalty whose pass-through is prohibited by law.

29.3. Pushfy shall give notice of the claim within a reasonable time, make relevant information available and allow the Customer to participate in the defense. A settlement that imposes an obligation or an acknowledgment of liability on the Customer requires the Customer's consent, which may not be unreasonably withheld in the face of a reasonable and substantiated solution.

29.4. No party shall be entitled to automatic indemnification without demonstrating the fact, the attribution and the amount, except for validly agreed penalty clauses, within legal limits. Specific fines shall be enforceable only when expressly provided for in a valid engagement, subject to proportionality, legal limits and the prohibition of duplication on the same ground.

29.5. Charges or penalties imposed by channel providers may be passed through to the Customer only if they arise from a violation provably attributable to the Customer, are based on applicable rules previously disclosed and are demonstrated by Pushfy. The pass-through shall comply with legal limits, may not include a hidden punitive margin and may not cover any portion caused by Pushfy's own conduct.

29.6. If a claim or proceeding requires urgent action before the Customer responds, the affected party may take reasonable steps to protect rights and prevent the situation from worsening, giving notice thereof as soon as possible. Urgency does not dispense with the consent required under clause 29.3 to enter into a settlement that imposes an obligation or an acknowledgment of liability on the other party, nor does it eliminate the need to demonstrate the reasonableness of the costs claimed.

30 AMENDMENTS AND NOTICES

30.1. Pushfy may update these Terms to reflect legal, technical or commercial changes. The new version shall be identified by date and version number and shall remain available for consultation. Amendments shall not have retroactive effect on services and rights already established.

30.2. Material changes that expand obligations, create significant restrictions or alter rights shall be notified at least 30 days in advance, unless a legal or security requirement is incompatible with that period, in which case it shall be explained. Pushfy shall request new acceptance when the change depends on contractual consent, before applying the new terms to the Customer.

30.3. The mere update of the text on the website does not prove acceptance of a new obligation. If the Customer does not agree with a change that depends on acceptance, the Customer may refrain from contracting future operations and terminate the affected service, with the applicable financial settlement. Specific agreements shall be respected in accordance with their amendment mechanisms.

30.4. Operational, security, billing and contractual amendment notices shall be given through the platform or through the registered contacts, with records of sending or availability. Pushfy may use more than one means for relevant notices. Notices that require a specific form by law or by contract shall comply with that requirement.

30.5. The Customer shall keep its contacts up to date and check relevant notices. Necessary contractual communication does not amount to authorization for optional advertising by Pushfy, the preferences and legal bases for which shall be handled separately.

31 GENERAL PROVISIONS AND DISPUTE RESOLUTION

31.1. The parties are independent. These Terms do not create a partnership, agency, franchise, employment relationship or joint and several liability not provided for by law or in an express engagement. A User who represents a legal entity does not become a personal debtor or guarantor merely by accepting on its behalf.

31.2. The parties shall comply with the anti-corruption, anti-fraud and anti-money laundering laws applicable to their activities. They may not offer undue advantages, conceal unlawful funds or use the engagement to enable prohibited conduct.

31.3. Pushfy may assign legitimate receivables and transfer its contractual position in a corporate reorganization or transfer of the operation, upon notice, preservation of obligations and respect for data protection and the Customer's rights. A change that causes material harm to the contracted terms shall permit termination without penalty for that reason and settlement of the applicable balance.

31.4. Occasional tolerance does not constitute a waiver or permanent amendment. The invalidity of one provision does not affect the others where they can survive. Ambiguities and adhesion clauses shall be interpreted in accordance with the legal rules, including those protecting the adhering party where applicable.

31.5. Brazilian law governs the engagement. The parties may seek a resolution through official customer support and, by mutual agreement, mediation, without preventing urgent measures, the exercise of rights or access to the competent bodies. These Terms do not impose mandatory arbitration by mere acceptance on the platform.

31.6. For business disputes, the venue of the Judicial District of Barueri, State of São Paulo, is chosen, as it corresponds to the supplier's headquarters, subject to mandatory legal jurisdiction and cases in which the choice of venue is invalid or abusive. Where consumer protection applies, the legally guaranteed venue is preserved, including that of the consumer's domicile.

31.7. No purchase order, internal rule or condition printed on a unilateral document of the Customer shall automatically modify these Terms. Its incorporation shall depend on Pushfy's express acceptance by an authorized person, without excluding legal obligations or binding terms of the offer.

31.8. The Portuguese text shall be the contractual reference, unless otherwise expressly agreed. Translations may facilitate understanding, but shall not reduce mandatory rights or prevail over the version actually accepted where this would contravene applicable law.

31.9. Summaries, frequently asked questions and support explanations help in understanding the service. They may not be used to conceal a contractual restriction or contradict binding information in the offer. Significant changes to price, scope or liability shall follow the contracting and update procedures set forth in this document.

31.10. Contractual deadlines for reporting a failure, disputing a charge or requesting information are intended to organize the investigation and do not alter legal statutes of limitation or forfeiture periods, nor do they create irrevocable acceptance of a charge or a waiver of a mandatory right. Delay in reporting may be taken into account only to the extent that it has demonstrably contributed to worsening the damage or impairing its mitigation, in accordance with the law. The exercise of a right or the filing of a good-faith complaint does not, in itself, constitute a breach of contract.

32 ELECTRONIC ACCEPTANCE DECLARATION

32.1. By checking the consent box and confirming acceptance, the representative declares: “I have read and accept the Pushfy Platform Terms of Use, in the version presented, and I have had access to the Privacy Policy. I declare that I am the contracting party or that I have the authority to represent the Customer identified in the registration. I am aware of the consumption and billing criteria, the rules on credits and cancellation, the grounds for suspension and the limits of liability described in these Terms.”

32.2. Acceptance of the Terms shall be recorded separately from optional advertising choices and from authorization for automatic top-up. The Commercial Terms of each purchase or plan shall be presented for separate confirmation. The Customer may retain the documents and consult the version it accepted.

32.3. The box for consent to these Terms shall be presented unchecked and shall require affirmative action by the Customer or its representative. The display of a page, silence, inactivity or automatic checking of a box shall not, in themselves, be treated as acceptance. A declaration of awareness of the Privacy Policy does not amount to consent for purposes that require specific authorization. Where consent is the applicable legal basis, obtaining it and any withdrawal shall follow a specific mechanism that is free, informed and compatible with the purpose.

32.4. Confirmation of a purchase or plan shall be linked to the version of the Terms and the corresponding Commercial Terms. The Customer shall receive a retainable electronic confirmation or access to an equivalent document identifying the transaction. Subsequent changes to the text shall not replace the historical version accepted for purposes of proving the terms of that act.

32.5. Granting operational access to a User does not automatically confer on that User the authority to accept a personal guarantee, assume obligations on behalf of another legal entity or change terms beyond the User's authorization. Pushfy may require additional acceptance from the authorized responsible person for contracting a postpaid plan, guarantees, a significant increase in limits or a change of ownership.