Features & integrations

1.1Features these terms cover

The specific provisions below apply only to features the customer enables and supplement the Terms of Service, Order and DPA for processing on behalf. The services described here are ready. Listing a feature does not mean it is available in every plan or country, and publishing this document neither opens public registration nor automatically enables a feature in your account. Function, permissions, fees, limits and applicable documents are disclosed before binding activation.

1.2Authority to activate

Anyone connecting a service or adding a feature must have account authority and permission for the relevant data and actions. Agency activation may require its client's or external-service owner's approval. Accepting general terms does not authorize a paid upgrade or new permission beyond disclosed scope; material changes follow Terms of Service notice and termination rules.

1.3Integrations covered by these terms

These rules cover enabled integrations with Stripe and PayPal; Meta, including Facebook, Instagram, Messenger and WhatsApp; Telegram Bot API; Google, including Calendar and Meet; Microsoft Graph and Teams; Zoom; and other offered connections. Each software library need not be listed as a contracting party, but the relevant provider, permissions, costs and data processing are identified before activation. Listing a brand establishes neither its endorsement or commercial partnership nor availability of every feature.

2.1Connecting through Thrive Connector

Utajir's same legal entity operates Thrive Connector for integrations and white-label connections. The name or domain may appear during external-provider authorization. The journey must identify the intended service and account, data and permissions with correct legal links; the connector name does not create a contract with another company of that name.

2.2Tokens and revocation

Keep connection keys and tokens confidential and grant only the permissions needed by parties and functions you authorize. We use or automatically refresh access tokens only while authorization remains valid and within its scope; after expiry or revocation, access is re-established only with valid new authorization. If exposure is suspected, revoke or replace keys through available controls and notify us without sending the token in support. The connection notice explains disconnection effects on imported data and queued tasks.

3.1Disclosed purpose and Limited Use

When a Google integration is enabled, we request the minimum permissions necessary for the disclosed function and explain access, use, storage and sharing. Use and transfer of information received from Google APIs comply with the Google API Services User Data Policy, including Limited Use requirements where applicable. Operator identity, privacy links and requested scopes match the authorization screen; mentioning the integration does not claim Google approval of an app, domain or scope.

3.2Restricted uses

Data covered by Limited Use must not be used for advertising, data sale, creditworthiness or lending decisions, or general-model training where prohibited, including covered derivatives. Human access or onward transfer is permitted only within a valid policy exception and as necessary, with specific consent where required. Google Sign-In or account-data access must not be used for primarily child-directed apps contrary to provider restrictions. Service-specific requirements apply in addition to these rules.

4.1Keys and scope

Access keys are limited to authorized functions and accounts. Keep them out of public content, limit contractor permissions and revoke them when no longer needed or suspected exposed. API access does not authorize extracting others' data, evading plan limits or testing systems without permission.

4.2Versions and event delivery

Follow disclosed limits and versions; we give appropriate notice of material changes under the Agreement. Events may repeat, be delayed or arrive out of order, so configure deduplication, request verification and failure monitoring under documentation. We do not promise exactly-once delivery or perpetual version compatibility without an express commitment, while remaining responsible for reasonable care in our integration.

5.1Messaging permission and sender identity

For email, SMS and WhatsApp, verify appropriate permission or lawful basis for the channel, purpose and sender and required registration or templates where applicable. Identify your business truthfully, keep permission evidence and honor opt-outs and suppression lists. Permission does not transfer between companies or channels merely because the contact is the same or accounts share an Agency.

5.2Charges, delivery and restrictions

Unit prices, allowances and provider fees are disclosed before paid use, including charged attempts if applicable. Sending does not guarantee acceptance, delivery or reading, and providers may restrict channels for quality or rule violations. We explain known reasons and remediation or appeal routes and support our integration issues, without promising to reverse decisions outside our authority or removing rights for our own errors.

5.3Delivery providers and account model

We use Emailit and Amazon SES for email according to the account or function. Enabled SMS, voice and number services use Twilio and may operate through the platform account and subaccounts with usage charged by Utajir. WhatsApp connects directly through Meta WhatsApp Cloud API under relevant business-account, template and quality rules. We distinguish faults and charges we handle from carrier or provider decisions. A provider must not be used for activity its terms prohibit; availability of a campaign tool does not itself authorize cold outreach.

6.1Calling and recording

If voice features are offered, customers verify calling, marketing, recording and transcription rules in relevant countries, including who must be notified or consent. Activating recording does not automatically make it lawful. Data categories, provider, retention and permissions must be identified, and recording stopped if required conditions are absent.

6.2Numbers and emergency use

Numbers and their porting, recovery and cancellation follow provider and country rules and the subscriber's actual rights, with subscription-end effects disclosed beforehand. Do not rely on an unverified voice feature for emergency access; emergency support and limits must be disclosed and tested before any promise. This page does not establish a launched calling service or an Utajir telecommunications licence.

7.1Inputs and outputs

Send AI only inputs you are authorized to use for the purpose. Input and output rights follow the Terms of Service ownership section, law and provider licences. Output may be inaccurate or similar to others' output; exclusivity or copyright protection is not guaranteed. Review facts, rights and suitability before publication or use.

7.2Data and sensitive decisions

Provider, purpose, retention and human review are identified before relevant use; authorization to deliver the feature does not extend to general-model training on customer content under the Terms of Service limits. Do not use it for decisions affecting rights, health or safety without express support and required safeguards, or to commit a person without authority. Automated interaction is disclosed where law or service context requires.

For an AI conversation or synthetic-content function, we disclose interaction with an automated system where required and provide required technical content marking within our role. The publisher of outputs provides disclosures required for its use, such as identifying manipulated content that could mislead people about a real person or event. Required disclosures or markings must not be removed, and the tool must not be used for impersonation. Duties depend on function, party role and applicable law.

8.1Action-execution limits

When configuring a workflow or agent, specify events, data, accounts, permitted actions, spending limits and required approvals. Test with suitable data before operation, especially for messages, publishing, record changes or authorized financial instructions. Permission for one action does not include changing its destination, amount or beneficiary beyond scope.

8.2Monitoring and stopping

Monitor execution, repetitions and errors and stop the workflow or revoke permissions when unintended behavior appears. External actions may already have executed and may not reverse on stopping, so their effects require handling with the relevant party. Platform design faults are not automatically assigned to the customer; cause, permissions and records inform responsibility under the Agreement.

9.1Stores, courses and memberships

The seller identifies itself and product terms, prices, taxes, delivery or access duration, renewal, cancellation and refunds before purchase. It is responsible for content rights, licences, fulfilment and buyer complaints, including minors' protections when targeted. Building a page with Utajir or collecting through a partner does not automatically make us the product seller.

9.2Buyer access and content

Download, course or membership access terms and use or sharing limits must be clear. A technical or financial dispute with another party does not remove mandatory buyer rights; buyer data and contributions must be protected. Assisted descriptions, tax information and reports do not replace verification of actual seller obligations.

10.1Integration and payment contract

Utajir provides a technical integration with a payment account you open and contract for directly with its provider, such as Stripe or PayPal when connected. Functions vary by provider and approved permissions. Ravinto is an independent payment service that is ready for use, with a separate payment account and agreement with its provider. Its expanded integration supports account creation, bank linking and verification with the provider, while Utajir displays balances and transactions, submits withdrawal requests and supports refund and dispute interactions within your permissions. We neither own the payment account nor hold its funds; the actual operator, contract and common-ownership relationship are disclosed before the connection is activated.

10.2Instructions, statuses and responsibilities

The payment provider handles business and payment-account acceptance, verification, closure, settlement, reserves, holds, processing fees, and execution of withdrawals, refunds and disputes under its agreement. Direct those matters to it. Report faults in Utajir’s display, transmission of an authorized request or data handling to contact@utajir.com. A balance or withdrawal button in Utajir does not guarantee execution or timing. Dedicated access for our customers or common ownership does not remove provider control or merge the contracts; provider identity, terms and ownership relationship are disclosed before connection.

11.1Domains, renewal and transfer

Identify the domain rights holder, registration details and authorized administrator and review renewal pricing, term and registrar and registry rules. Connecting a domain does not automatically transfer ownership to Utajir or an Agency. Keep contact details current and monitor expiry notices. Authorized transfers follow actual domain rules; recovery is not guaranteed after rights expire or another person registers the name.

11.2Hosting, WordPress and plugins

The plan defines hosting, backup and support scope and whether WordPress sites or plugins carry separate charges. Themes and plugins remain subject to their licences, security and compatibility requirements; update and backup duties follow the agreed service. Hosting does not imply recoverable backups for every item or indefinite retention. The schedule and domain or service expiry effects must be established before reliance.

11.3Domain acceptance and brand protection

Domain connection requires authority to use it and compliance with the misleading-domain and name rules in the Terms of Service and Acceptable Use Policy. Registering a domain neither obliges us to accept it on the platform nor proves that it does not infringe a mark. We review objections to refusal. A domain or account may be suspended or terminated where the Terms’ grounds and procedures are met; ownership of the domain does not transfer to us.

12.1Calendars and bookings

The calendar owner authorizes reading, creating or changing appointments as needed and controls what invitees see and who may share details. Time zones, synchronization delays or conflicts can affect bookings; verify important appointments and configure reminders under lawful permission. Connecting one calendar does not automatically authorize every user calendar.

12.2Meetings and external services

A meeting or booking may require an external service with its own terms, provider and data handling. Transfers, embeds and fees are disclosed before activation and tracking choices respected. Disconnecting synchronization stops later updates within scope but may not remove an invitation or appointment already sent; cancellation or amendment must be made with the proper service.

13.1Defined beta use

A beta feature is clearly labeled before use, with purpose, duration, limits, any fees and suitability for real data explained. It may change or end without a guaranteed final release. Beta status does not remove confidentiality, data protection or non-excludable rights, or permit undisclosed paid testing.

13.2Provider or function changes

A provider or function change is assessed for data, permissions, cost and compatibility effects. We notify the customer and follow the subprocessor process where applicable. Expanded scope requires new authority, with alternatives, exit and retrieval under the Terms of Service for material reduction. Old connection consent does not cover unrelated new processing.

14.1Disconnecting and stopping the flow

An authorized party may revoke provider authorization or use available disconnection controls. Subsequent access and synchronization stop within revocation scope, potentially stopping dependent tasks or reports; review linked automation. Exposure may also require provider-side token revocation, and removing an interface item is not sufficient evidence that every permission has been invalidated.

14.2Copies and contracts after disconnection

Data imported into Utajir follows its purpose, deletion instructions and the DPA, while provider copies follow its rules and roles. Disconnection alone does not terminate an external subscription, erase amounts due or reverse completed actions. To end a service or delete its data as well, the customer uses the appropriate route with the relevant party, preserving legal rights.

15.1Tool function and signature validity

The enabled function supports creating and sending documents, collecting signatures and retaining available signing evidence. Parties, content and signatory authority arise from the transaction itself; use of the tool does not make us a party to your customer contract. A template or AI suggestion is neither legal advice nor a guarantee of validity in every country. Check identity, consent, witness, notarization and signature-type requirements before use for a transaction requiring special formalities.

15.2Evidence, copies and exclusions

Give the signer an opportunity to read the final version and obtain a copy, and retain the signed version and available timing and consent record. Do not represent a document changed after signing as the accepted version; a material amendment needs fresh agreement. We do not claim to supply a qualified signature, trust certificate or notarization unless expressly offered through a service meeting its requirements. Do not rely on the tool alone for a document requiring an unsupported formality. Signing data follows applicable privacy, processing and retention terms.

16.1Generation, preview and publication

Previewing a generated application differs from publishing it publicly and operating it continuously. The offer specifies resources, limits, charges and the scope of file and data storage, backup and export for the enabled function. Utajir manages the runtime service; AI-generated code does not itself create a relationship with a separate SaaS provider. Code and content rights follow incorporated-material licences and the ownership and AI terms, without a guarantee of exclusivity or absence of third-party rights.

16.2Application responsibility and safe operation

Review the application’s functions, permissions, outputs and notices before publication. Do not embed secrets in public code or collect data without a lawful basis. We apply appropriate access and resource isolation to the environment we manage; bypassing isolation, mining, malware and unauthorized resource use are prohibited. A risky application may be restricted under suspension procedures, respecting export, deletion and affected persons’ rights. Code generation does not remove the owner’s business responsibilities or our responsibilities for operating the runtime.