Telivia
Back to home

Telivia privacy policy

Effective November 16, 2026. Version 2026-11-16

1. Scope and roles

The contracting party is Telivia LLC, a limited liability company formed in the state of Florida, United States. Legal and support contact is exclusively by email: info@telivia.ai. This policy explains processing concerning visitors, contacts, administrators and users. Business context does not make personal data anonymous.

Telivia acts as controller for its commercial relationship, accounts, its own billing, security and support. For data a business uploads to manage its operations, that business determines the purposes and Telivia processes on its behalf under the DPA. If the business is itself acting on behalf of another controller, that relationship must be documented.

The governing law is the law of the state of Florida, United States, and its courts have jurisdiction over matters that are not subject to Dominican public policy. Mandatory Dominican Republic rules, including consumer and personal data protection laws and mandatory jurisdiction, remain applicable. Other mandatory laws apply according to their scope.

2. Data that may be processed

Account and business details: name, email, role, access identifiers, business and RNC where needed.

Contracting: plan, accepted order, billing history, Stripe identifiers and payment status. Full card details are entered with Stripe rather than in a Telivia conversation.

Customer operations: contacts, business and tax documents, collections, inventory and personnel data only for enabled modules and necessary fields.

LIVIA: messages, instructions, responses, steps and approvals; business context needed to answer a query. Audio and transcripts may be processed if voice is enabled, depending on the mode.

Support and security: case details, communications, accessing person's identity, reason, timing, actions, technical logs, IP address and device details where generated by the service.

Navigation: cookies and local storage described in the cookies policy.

Sources include the person, the business inviting them or entering their data, its integrations, and providers returning access, payment or processing statuses.

3. Purposes and legal grounds

Telivia uses necessary data to provide the requested service, manage users, provide support, handle payments, secure access and comply with legal duties. Marketing and optional features require separate assessment of notice and consent or another applicable authorization. Acceptance of terms is not consent to advertising.

Each purpose needs the ground required by applicable law: informed consent where necessary, performance of the contractual relationship or statutory authorization where applicable. Legal grounds from another jurisdiction are not automatically imported into Dominican law.

Customers must inform their contacts and staff and have necessary authority to upload their data. This does not remove Telivia's own obligations.

4. Separation and support

The service uses a separate database per business and a central registry for necessary administration, plan, access, billing and counts. Database separation does not mean account data or AI queries never reach contracted service providers.

Ordinary super-admin views do not display a business's invoices, customer lists or chats. Separate support content access requires a case, reason, duration, log and owner notice. Only authorized people access content necessary to handle the case.

5. Providers and recipients

Telivia uses Vercel for hosting, Supabase for databases, WorkOS for sign-in, Stripe for payments, Anthropic/OpenAI for AI and ElevenLabs for voice when enabled. Each receives only the categories needed for its function, subject to settings and contract. Legal entities, regions and terms are set out in Annex B of the DPA and its updates notified to the customer.

Stripe may act as an independent controller for certain financial and fraud functions; providers are not assumed to be subprocessors for every activity. MSeller uses the customer's own account for fiscal processing. DGII receives the information required for that process. Other providers for background tasks, email or telephony are involved when enabled, according to Annex B of the DPA and its updates notified to the customer.

Telivia does not sell personal data or use customer data for advertising across customers or for Telivia's own general model training. This statement does not certify every provider's operation. Legal demands should be reviewed and limited to required disclosures, with notice where lawful.

6. AI and audio

Only the context needed for an authorized function is sent to AI providers. Processing may involve Anthropic or OpenAI; voice adds ElevenLabs and, where applicable, call operators. Anthropic and OpenAI describe default training exclusions for commercial services; ElevenLabs' general policy addresses training and controls. Telivia does not promise a universal training exclusion beyond what each provider's contracts and settings establish. Zero retention is not promised either.

Enabling a microphone permits processing for that feature, but does not itself authorize recording another person or placing an AI call to them. Required notices and authorizations must be obtained. Biometric identification and voice cloning are not offered as contracted SaaS features.

Call recordings are kept for no more than 90 days. The transcript is retained in the relevant record for as long as necessary for the stated purpose and as required by applicable law; it is then deleted or anonymized. Voice for new businesses is outside the initial scope.

7. Countries and transfers

Processing may occur outside the Dominican Republic, including in the United States. The countries, regions, remote access locations and entities of each provider are those set out in Annex B of the DPA and its updates notified to the customer. A separate database does not establish exclusive Dominican data residency.

Authorization and safeguards must be documented for each transfer, including under Article 80 of Law 172-13 where applicable. Accepting this policy does not authorize all transfers. A foreign DPA is not assumed to satisfy Dominican requirements by itself, and no particular international transfer mechanism is claimed to have been adopted.

8. Retention

Telivia retains each category only as needed for its purpose, the contract or applicable legal duties, according to this schedule:

Category | Period

Account, contact and support | During the relationship and, afterward, for as long as necessary for the stated purpose and as required by applicable law; then deleted or anonymized

Telivia billing and acceptance | The tax, contract and legal defense periods required by applicable law; then deleted or anonymized

Customer data and fiscal documents | According to customer instructions and the retention required by applicable law

Conversations and transcripts | For as long as necessary for the stated purpose and as required by applicable law; then deleted or anonymized, without indefinite retention

Call recordings | No more than 90 days; then deleted

Audit and security logs | For as long as necessary for the stated purpose and as required by applicable law, with restricted access and incident preservation; then deleted or anonymized

Backups and providers | For as long as necessary for the stated purpose and as required by applicable law, by rotation; then deleted or anonymized

Cancelling a plan, withdrawing marketing consent and deleting an account are different requests. Data retained by law must be restricted to that purpose and deleted when the obligation expires.

9. Rights and requests

Law 172-13 provides access, rectification, cancellation and objection rights within its scope. Requests about data controlled by a customer business go first to that business; Telivia must assist under the DPA. Requests about Telivia's own account or commercial relationship go to its privacy email info@telivia.ai.

Identity verification must be proportionate and avoid unnecessary documents. Legal limitations must be explained without removing available remedies. Commercial deadlines must not extend legal ones: the applicable requirements of Articles 8 and 12, including ten and five business days respectively, must be met. No universal portability right or immediate deletion of all tax records is asserted.

U.S. state laws must be assessed by the person's location, processing and legal thresholds. Where CCPA applies, notices, rights, contracts and mechanisms need separate review; applicability or compliance does not follow merely from LLC status.

10. Security and changes

Security measures are described in the DPA. No absolute security or Telivia certification of its own is promised. This business service is not directed to children; processing children's data requires separate assessment and is not authorized here.

Material changes are communicated with reasonable prior notice before they apply, stating their effective date, and new authorization is obtained where required by law. Questions about changes go to info@telivia.ai.

Additional bases and rights

Telivia determines purposes and means for its own account and billing data; it acts on customer instructions for business data under the DPA. Under GDPR, contractual necessity covers only necessary data of the individual contracting party; legitimate interests for business representatives require balancing and objection rights. Legal duties support required records; separate revocable consent applies where needed. Marketing is not a condition of service.

Where GDPR applies, access, correction, erasure, objection, restriction and portability are honored as applicable; consent may be withdrawn without affecting prior processing, and individuals may complain to a competent authority. Ordinary response is within one month, with lawful reasoned extensions. Law 172-13 retains its ARCO rights and applicable deadlines. This policy authorizes no solely automated decisions with legal effects. Telivia will appoint a representative or data protection officer when applicable law requires it.

Additional inventory

Depending on the services enabled, Postmark for transactional email (recipient, content, attachments), Trigger.dev for jobs (instructions, identifiers, results), Retell for calls and Chatwoot for channels are also involved. Google and Meta may receive data through expressly authorized connections and channels. Telnyx receives phone numbers and content for SMS. Chatwoot and Microsoft are involved only when enabled. MSeller receives tax documents through the customer’s own account. DGII is a statutory recipient, not a commercial subprocessor.

Supabase stores data, Vercel hosts the app, WorkOS manages identity, Stripe payments, Anthropic/OpenAI inference and ElevenLabs voice, depending on the services enabled. The entities, countries, regions, contracts, retention and onward processors of each service are those set out in Annex B of the DPA and its updates notified to the customer. Stripe may act as an independent controller for fraud and its own legal duties. Zero retention or training exclusion is not promised beyond what each provider's contracts and settings establish.

Retention and additional laws

Records subject to Dominican Tax Code article 50(h) are retained for ten years when Telivia is the obligated party; customers maintain their own tax archives. This does not justify retaining every chat or recording for ten years. Accounts remain while needed; security, support, audio and backup records are retained for as long as necessary for the stated purpose and as required by applicable law, with documented legal holds; they are then deleted or anonymized.

Laws 126-02, 358-05 and 53-07 apply according to context and do not justify indefinite evidence retention. US state laws will be assessed against thresholds and operations. Applicable sale or advertising opt-outs and mandatory privacy signals will be honored. This policy does not sell customer data. Legal and privacy contacts: info@telivia.ai; authenticated support may also route requests without unnecessary identity documents.