Who we are and our roles

Telp is an Artifision product. The service provider is Artifision, a sole proprietor registered in Serbia. Registration number: 68411556. Tax ID: 115497218. Registered address: Cara Lazara 42, sprat 3, stan 26, 32102 Čačak, Srbija. Privacy contact: [email protected].

Artifision is the controller for data processed for the Telp website, accounts, sales, support, security and platform administration. When a user or organization connects a channel and uses Telp for conversations with its customers, that user or organization normally determines the purpose and legal basis, while Artifision processes data on their behalf as a processor under the agreement and instructions.

Data we process

  • Account and customer data: name, email and phone number, company name where applicable, role, language, settings, permissions, authentication data and billing contact details.
  • Conversation and CRM data: messages, attachments, images, voice messages, contacts, lead data, summaries, statuses, handoff notes, operator replies and activity history.
  • Voice calls: status, duration, participants, technical events, transcripts when requested and recordings where recording is enabled, permitted and the caller has received the required notice or provided consent.
  • AI and automation data: agent instructions, assigned knowledge, knowledge-search queries, tool calls, structured input and output, confirmation cards, webhook results, errors, audit records and usage data.
  • Billing and subscription data: Paddle customer and transaction identifiers, selected plan, subscription and payment status, currency, amount, tax, invoice number, billing dates, refund or adjustment status and data needed for transaction support and reconciliation.
  • Shopify billing for Telp: the connected store identity and address, subscription and purchase identifiers, selected plan, amount, currency, billing interval, approval and subscription status, and access dates.
  • Technical and security data: IP address, browser, device, URL, request time, logs, rate-limit data, security events, session and CSRF data.

Paddle payments

For purchases billed through Paddle, Paddle acts as Merchant of Record and separately processes data required for checkout, payment collection, tax, fraud prevention, payment documents, the customer portal and refunds. Paddle may collect name, email, billing address, tax information, payment-method details, device data and other transaction data under its own privacy notice.

Telp receives limited customer, subscription, transaction, invoice, tax and payment-status data from Paddle to activate the plan, display billing history, provide support and reconcile a refund or dispute. Telp does not receive or store the complete payment-card number or its security code.

Paddle Privacy Notice

Shopify billing for Telp

When a company uses Shopify billing, Telp sends Shopify the details needed to approve the selected plan or an available top-up and receives purchase identifiers, price, currency, billing interval and status. We associate these records with the correct company and store to activate and maintain access, show subscription status, process cancellation and provide support.

Shopify separately processes payment and billing data under its own privacy policy. Telp does not receive or store the complete payment-card number or its security code from this flow. This is billing for the company’s use of Telp; purchases made by its customers in the store are described separately below.

Shopify Privacy Policy

Facebook, Messenger, Instagram and WhatsApp

When a business connects a Meta channel, we may process the Facebook Page ID and name, Page tasks and permissions, Instagram professional account ID, app-scoped ID, username and account type, WhatsApp Business Account ID, phone number ID, display number and business name, together with connection and webhook subscription status.

For messages, we may receive app-scoped sender and recipient identifiers, content, timestamp, message ID, replies, reactions, attachments or media IDs. We use this data to route the event to the correct tenant and conversation, display it in the inbox and send a response through the same channel.

OAuth and Page/WhatsApp access tokens are used server-side only to connect accounts, verify subscriptions and send messages. They are stored encrypted and are not sent to the widget, an operator browser or the AI model. Meta also processes data under its own terms and privacy policy.

Purchases in a connected Shopify store

When a business enables purchases through its connected store, Telp prepares a cart from the confirmed product selection. The customer confirms delivery, the final total and payment in the store. This flow does not collect payment-card numbers or security codes in Telp.

For customer service, we retain the verified order reference, purchased items, total, currency and payment status at confirmation. We use an available phone number to associate the purchase with a contact; if no phone is available, we use an available email. When first and last name are available from the shipping address, we use them as the CRM contact name and record their source because they may belong to the package recipient. This flow does not retrieve the full shipping address or customer profile.

Temporary checkout links and purchase-checking data are stored encrypted for at most 24 hours after preparation. Tracking then stops. Confirmed purchases remain with their conversation under the conversation retention rules. Purchase status and results may form part of AI response context; checkout secrets and the separate buyer-data snapshot are excluded from model-facing tool results.

Access and deletion requests are scoped to the store and the source of each data copy, including purchase records, derived copies and related notes. Independent data from other connected channels or stores is preserved. Authorized business users can download a prepared export to respond to the customer request.

When Shopify requests deletion of store data, we remove its authorized catalog data, promotions, purchase-draft items and store access credentials. We cancel open drafts and retain the historical status and purchase-attempt relationship for finished drafts. Additional review of remaining purchase copies does not delay this removal. Conversations, historical product cards, independent CRM data and billing records remain under their retention rules; purchase data and derived copies remain subject to source-scoped deletion. A separately selected public catalog may remain available.

When customer transfer is active, name, email and phone confirmed through the store’s chat or voice conversation can be added to Shopify Customers. Empty fields of an existing customer can be filled automatically; differing existing values require an authorized company member’s review. We do not infer marketing consent from a conversation. After an erasure request, we retain a minimal protected identity record to prevent older submissions from being sent again. This record contains no readable name, email or phone and remains until related retained contacts, possible older sources and unfinished processing or reviews no longer exist. A new confirmed submission can require a separate authorization while that protection remains. This protection is included in the applicable access and privacy review process.

Gmail connection and Google data

When you connect Gmail, Telp requests permission to verify your Google account identity and email address, read messages and send replies from the connected mailbox. Google’s read permission covers the mailbox; your Inbox or label selection in Telp determines which new messages enter conversations. Telp may read a message before checking its labels to apply that selection. Earlier messages in the same thread, including sent replies, may be retrieved as context.

We process the connected account’s address and identifier, senders and recipients, subject, text, message time, labels, message and thread identifiers, and whether an attachment is present. Telp stores imported conversations, replies, associated contacts and information needed to maintain the connection and sending status. This email feature processes text; attachment content is not used for autonomous AI processing.

We use this data to show conversations to the authorized team and provide AI replies and approved tools according to agent and channel settings. When AI is enabled, relevant conversation text and information needed for the response are sent to the selected AI service provider. Data needed for an approved action may be sent to a system connected by the business. Hosting and other service providers process data to deliver these features. We do not receive your Google password; mailbox access credentials are stored encrypted and are not sent to the AI model.

Our use and transfer of Google data follow the Google API Services User Data Policy and Google Workspace policies, including Limited Use requirements. We do not sell Google data or use it for advertising, creditworthiness assessments, or training or improving general-purpose AI models. Our staff’s access to content is limited to your explicit consent for specific data, security needs or legal obligations.

You can disconnect in Telp’s Email channel settings, which stops new access through that connection. When the last Telp connection for the same Gmail account is disconnected or deleted, including through company deletion, we automatically request access revocation from Google. If revocation is incomplete, processing stays stopped, we show the status and provide a retry action; required credentials remain encrypted only to complete revocation and are then deleted. Other retained connections for the same account continue working. Pausing AI does not revoke access. You can also remove access in your Google Account settings. Disconnecting or revoking access does not delete conversations and contacts already stored in Telp. They remain subject to this policy’s retention periods; an authorized user can delete a conversation, and the instructions below explain how to request deletion of other associated data. Deleting a Telp copy does not delete the original message in Gmail.

Connecting ChatGPT and Claude

A company member can connect their Telp account to ChatGPT (OpenAI) or Claude (Anthropic). The connection starts only after they sign in to Telp and approve access on a Telp screen. It covers the companies where they are an active member, and only within their role in each of them.

When the member asks that app for something in Telp, Telp sends it the data needed for that request: agents and their instructions, channels, knowledge documents, message and WhatsApp templates, integrations and store promotions, CRM settings, tools and the company profile. Telp does not send it customer conversations, messages or contacts, or passwords, keys and tokens. Members enter keys only on a Telp page.

OpenAI or Anthropic then processes that data under its own terms and privacy policy, as a recipient the member chose. Whether conversations are used to improve their models depends on the member's settings with that provider.

Telp keeps the connection details: which app is connected, when access was approved and when it was last used. Access tokens expire, and we delete expired ones regularly. Changes made through the app are recorded in the company activity log.

You can revoke access on the My account page, under Connected AI apps. Telp also ends it when the account is blocked or deleted. When a member leaves a company or their role changes, the app gets only what the new role allows from the next request on.

Sources of data

  • Directly from you when you create an account, complete a form, send a message or attachment, or participate in a call.
  • From the business using Telp and its authorized users, agents, knowledge, tools and connected systems.
  • From connected channels and providers, including Paddle, Shopify, Meta, Telegram, AI providers, audio infrastructure, email, CRMs, webhooks and automation services.
  • Automatically through security, audit, billing and technical logs generated while the service operates.

Why we use data

  • To provide accounts, connect channels, receive and send messages and operate a unified inbox.
  • To let an AI agent respond, search assigned knowledge, use approved tools and hand a conversation to an operator.
  • To execute confirmed business actions and connect Telp to systems selected by the business.
  • To retain recordings and operational records where configured, permitted and necessary.
  • To maintain tenant isolation, prevent abuse, troubleshoot errors, measure usage and improve reliability.
  • To manage plans, subscriptions, transactions, access to the relevant billing details, payment support, refund requests and reconciliation with Paddle or Shopify records, according to the company’s billing method.
  • To meet contractual, accounting, tax, security and other legal obligations.

AI processing and automated decisions

Relevant conversation context, instructions, knowledge-search results and approved tool definitions may be sent to the selected AI provider to generate a response or tool call. Secret keys and technical credentials are not part of the AI prompt.

Telp should not be used for decisions producing legal or similarly significant effects without appropriate human review. The business using Telp decides when an operator, validation or written action confirmation is required.

Cookies and similar technologies

Telp uses necessary session, authentication and CSRF cookies, including the Telp session and XSRF token, so sign-in, forms and request protection work. Hosting and security providers such as Cloudflare may set necessary cookies to prevent abuse and maintain the service.

The conversation widget uses browser local storage so a visitor can continue an active conversation. When a visitor starts a conversation, the business using Telp may receive allowed campaign tags, the landing page and the external referral source. Telp removes other query parameters and fragments from that context before it is stored.

We currently do not use advertising or cross-site tracking cookies on the public legal pages. If we introduce analytics or marketing technology that requires consent, we will update this policy and present the appropriate choice before activating it.

Recipients and international transfers

We may share data with the user or organization using Telp and its authorized members, with Paddle or Shopify according to the billing method, and with hosting, database, storage, security, email, AI, voice transport, communication-channel and automation providers where required to provide the service. Data is also sent to systems explicitly connected by the user, such as a CRM, help desk, Make, n8n, a webhook, ChatGPT or Claude.

Some recipients may process data outside Serbia or the European Economic Area. Where required, we use contractual and other available safeguards and limit transfers to data needed for the relevant function. We may disclose data to competent authorities where legally required.

Retention periods

  • Meta and other channel credentials are stored encrypted while a channel is connected and are removed during deauthorization, disconnection or channel deletion. For incomplete Gmail revocation, we temporarily retain only the encrypted credentials needed to finish it, as described in the Gmail section.
  • Call recordings have an expiry date based on channel or tenant settings. The default period is up to 90 days unless configured or agreed otherwise. After expiry, the recording is deleted from storage and the recording register.
  • Conversations, messages, attachments, tool calls and audit data are kept while needed for an active account, contracted service, support, security or record keeping. An authorized user may delete a conversation, which also deletes its stored recordings and attachments.
  • Billing, tax, security and dispute records are kept for the period required by law or a legitimate business need. Residual backup copies expire through the normal backup rotation and are not used for active processing.

Your rights

Where applicable, you may request access, correction, deletion, restriction, portability or object to processing and withdraw consent. Email [email protected] and include the channel, approximate date and information needed to locate the record and verify identity. We respond without undue delay, normally within 30 days where that deadline applies.

If the business using Telp is the controller, we will forward the request or assist that business. You may lodge a complaint with the Commissioner for Information of Public Importance and Personal Data Protection in Serbia through poverenik.rs, or another competent supervisory authority.

Security

We use access controls, tenant isolation, encryption of sensitive channel tokens, server-side secrets, audit records, HTTPS and permission limits. No internet service is free of all risk, but we regularly review measures appropriate to the data and platform functions.

Children

Telp is a business platform and is not directed to children. If you believe a child's data was processed without an appropriate basis, contact us so we can investigate and act.

Changes and contact

The current version is published on this page with its revision date. We will provide notice through the service or another appropriate channel for material changes where required.

For questions, rights requests or deletion requests, email [email protected]. Controller: Artifision, Cara Lazara 42, sprat 3, stan 26, 32102 Čačak, Srbija.