This is a translation provided for convenience. The Azerbaijani version of this document is the governing text.

Privacy Policy

Last updated: 2026-10-29

«Greetvo» (hereinafter — the «Platform») provides businesses with two services: (a) a chatbot that automatically responds to customer messages, and (b) performance analytics for social media accounts. This document explains what data the Platform processes, in what role, and for how long.

Two different roles

Data for which we are the controller: the account information of the business (tenant) that registers on the Platform — email, organization name, login credentials, usage statistics, and billing records.

Data for which we are the processor: the data of the tenant's own customers — chat text, name, phone number, booking/order requests. The controller of this data is the tenant; we process it only to provide service to the tenant, on the tenant's instructions. We do not sell this data, do not use it for advertising, and do not use it for model training.

Bot module — what data is collected

About the person writing on the chat page or in connected messaging channels: the message text, message timestamp, channel type and the identifier within that channel (for example, a Telegram chat number or a randomly generated number for a browser session), as well as the name and phone number voluntarily provided during the conversation.

A functional cookie (name: social_visitor, duration: 1 year) is placed in your browser to keep the conversation going. It stores only a random number — it does not carry a name, phone number, or tracking information — and is sent only to the chat page. Its purpose: to prevent your previous conversation from being lost when browser storage is cleared. It is not used for advertising or cross-site tracking.

The number of requests is logged to prevent abuse. The IP address is not stored raw — it is used only in salted hash form for rate-limit calculations and is automatically deleted after 3 days. The IP address and browser "fingerprint" are not used to identify individuals.

Voice chat. If the business has enabled the "Voice chat" feature on its business card, a visitor can speak by voice with an AI assistant through the browser. The call starts only after you press the "Call" button, the microphone is used only for the duration of the call, and at the start of the call you are informed that the assistant is artificial intelligence. The audio recording is not stored. The data that is stored is: the text transcript of the conversation, the duration of the call, and the name, phone number, order, or booking request you provided during the call — these are shown to the business (the controller) in the same way as data from a written conversation.

Use of artificial intelligence (LLM)

To prepare responses, the text of the conversation and the business's knowledge base are sent to a third-party model provider (currently via OpenRouter). The provider processes the data solely to generate the response. We recommend that you do not enter identification document numbers, card details, passwords, or health information into the chat — the bot does not request such information.

During a voice chat, your voice is transmitted in real time to a third-party voice model provider (currently OpenAI) for generating the response; in this process your browser connects directly with the provider, and the audio does not pass through our server. The provider's own privacy and retention terms apply. We likewise recommend that you do not disclose identification document numbers, card details, passwords, or health information during voice chat.

Analytics module

Aggregate performance metrics for social media accounts that the tenant itself has connected: reach, impressions, engagement, follower count, and similar account/post level metrics. Lists of followers or individual profiles are not collected — this is not technically possible either, as the official APIs do not provide such access.

Security of access

Social network and messaging tokens are stored encrypted in the database (Supabase Vault). Each tenant's data is isolated at the database level (row-level security); one tenant cannot see another tenant's data.

Retention period

Conversations and contacts are retained for as long as the tenant's account remains active. Analytics metrics are retained indefinitely for historical trend purposes (platforms themselves do not provide historical data). When a tenant's account is deleted, all conversation, contact, and token data belonging to it is deleted.

Deletion of data

If you want a conversation or contact to be deleted, please first contact the business you corresponded with — it is the controller of that data. You may also write to us directly, and we will forward your request to the relevant tenant.

Meta account owners can submit a data deletion request by revoking the app's access from the Business Settings interface — this automatically triggers the /api/meta/data-deletion endpoint, and the related connection data is deleted immediately.

Children

The Platform is not intended for persons under the age of 16.

Changes

This document may be amended; the "last updated" date above reflects the current version.

Contact

For questions and data requests: mazandarov@gmail.com