Last updated 2026-11-09
Privacy Policy
01Data and access before implementation
Before connecting, we agree on the data involved, access permissions and processing terms, taking Uzbekistan’s legal requirements into account. We are also introducing a protective layer that masks personal data in text requests sent to external AI services. We document the available safeguards separately for each project.
External AI services and infrastructure may process data to carry out tasks.
02Instagram dashboard sign-in
After sign-in, the browser stores a secure session cookie instead of the dashboard access key. The server session lasts up to 12 hours, or up to 30 days if you choose to remember this device. Signing out on this device or revoking the access key ends its access.
03Business quick review
If you choose a quick review from azimai or NOIB, we ask you to confirm your Telegram account in our Support bot before the interview. We store your Telegram ID, display name and username if available, consent, entry brand and language, conversation text, answers, result map and short brief to deliver the result and discuss your task. This is not a marketing subscription.
The website copy is stored in Upstash for 90 days after the last save. The result is accessible only after signing in with the same Telegram account. A short result is sent through Telegram; its delivery and further discussion use our Support agent. We use ElevenLabs for the interview, including voice processing when you choose voice. Telegram and AI providers process data under their own terms and retention settings. We do not store a separate audio file on our website.
The quick-review page does not load session recording or send conversation text or contact details to website analytics. We count fixed stages of the review without these details. To request deletion of your website record, contact hello@azimai.uz or our Support bot.
04Client cabinet
The client cabinet (azimai.uz/app/cabinet and the Telegram mini app) is a closed area where a client and our team run the tasks of the client's project. Only a person who has been given access to a project can sign in. We store the Telegram ID and name of each person with access, project stages, task and comment texts, due dates and completion marks. Cabinet data is stored in Upstash (region: Frankfurt, Germany); the website runs on Vercel.
The cabinet assistant answers through the API of Anthropic PBC (the Claude model); this processing takes place in the United States. A request contains the question, the last few turns of the conversation and the names of the projects, stages and tasks this person sees in the cabinet, with their statuses and due dates. We do not send the person's Telegram ID or name. We write tasks without personal data; if a task text does contain personal data, it is sent together with that text. If Anthropic is unavailable, the answer is prepared by a model on our own server or taken from our materials. The assistant's conversation history is kept on the website for 30 days.
Usage log. To support clients and improve the cabinet we keep a log of its use: bot start and sign-ins, visits and their duration, pages opened, actions, connections of an AI service through MCP and the tools it called, and device type. Message, task and comment texts are not written to the log. The log is visible only to our team and is deleted 90 days after the person's last activity in the cabinet.
05Who we are
The azimai.uz service ("we", "us") is provided by NOIB LLC (OOO "NOIB"), taxpayer identification number (TIN) 313 380 383, registered address: Samarqand Darvoza ko'chasi 2B-uy, 51-xonadon, Qoratosh MFY, Shaykhantakhur district, Tashkent, Uzbekistan. NOIB LLC (OOO "NOIB") is the data controller for the data described in this policy, except where stated otherwise below.
We build and deploy AI agents that work inside Telegram and, when a client connects it, inside Instagram Direct. Contact: via the links in the site footer (Telegram / Instagram / LinkedIn).
06What this policy covers
This policy applies to the website azimai.uz, to the AI agents we deploy for clients, to the client cabinet, and to the Instagram connection service at azimai.uz/connect/instagram (the "Instagram Connector").
07Data we collect on the website
Contact details you submit in forms (name, phone, Telegram username, company) — to answer your request.
Technical data: IP address, browser, pages visited — via analytics tools listed on the site, used in aggregate to improve the site.
If you sign in with Telegram, your Telegram user id and display name — to show you member-only content.
08Instagram Connector: what we receive from Meta
When a business connects its Instagram professional account through Business Login for Instagram, Meta shares with us: the account ID and username, an access token, and — via webhooks — the messages, comments and related events that the account receives (sender ID, text, attachments' URLs, timestamps).
We request only the permissions needed for the service: instagram_business_basic (account identity), instagram_business_manage_messages (receive and answer Direct messages), instagram_business_manage_comments (see and reply to comments), instagram_business_manage_insights (the account's own statistics: reach, views, followers — shown to the business in its dashboard), instagram_business_content_publish (publish posts on the business's behalf when it asks its agent to or presses “Publish” in its dashboard). We never ask for the account password.
09Instagram Connector: how we use it
Messages and comments are forwarded, within seconds, to the client's own server where the client's AI agent runs. The agent drafts and sends replies on behalf of the business, and hands the conversation to a human operator when needed.
Replies are drafted by an AI model from Anthropic (Claude): to prepare a reply, the text of the conversation is processed by this provider. Training on this data is turned off in our Anthropic account settings.
The business's own operators can also reply from the azimai.uz dashboard: people the business owner has given a personal dashboard key. Such a reply is sent through the Instagram API on behalf of the business and is marked in the dashboard as sent by that operator.
We use the data solely to provide this service to the business that connected the account. We do not sell it, do not use it for advertising, do not build advertising or cross-business profiles of the people who write to the business (the conversation stage and source described below are visible only to the business the person is talking to), and do not share it with third parties other than the infrastructure providers below.
Replies are sent only within the messaging window allowed by Meta's policies; the agent stops when a human operator joins the conversation.
10Where the data is stored and for how long
On our platform (azimai.uz, hosted on Vercel; key-value storage on Upstash) we store: the account ID and username, the access token (encrypted with AES-256-GCM), the client's server address, delivery statistics, and — only if the client's server is temporarily unavailable — a short queue of undelivered events, which is emptied as soon as delivery succeeds.
Conversation view in the client's dashboard. So that the business owner can see its conversations and numbers in one place, we keep a copy of the Direct messages and comments of the connected account. The text of every message is encrypted at rest with AES-256-GCM (the same scheme and key handling as the access token); alongside it we keep the writer's Instagram ID, the public profile name and username (when Meta sends them with the message, or when we look them up as described below), the time and the direction of each message, and when the person read the business's reply (Meta's read receipt). We do not copy attachments — only how many there were. Limits: the last 200 messages per conversation and the last 500 conversations per account.
Retention: 30 days. Each conversation is stored with an expiry set in the storage itself and disappears automatically 30 days after its last message — there is nothing to forget to clean up. Nobody on our side writes into a client's conversations; replies come from the client's agent or from the client's own operators (see above).
Team inbox. When the business works with operators in the dashboard, we also keep: who is responsible for a conversation, operators' shifts, notes for colleagues and follow-up tasks (their text is encrypted like message text), the order stage and loss reason the operator marked, and a customer card — a phone number if the customer left one (encrypted) and tags. All of this belongs to the conversation and is erased with it 30 days after the last message; completed tasks are kept for 7 days. For each operator we count replies and response times — no message content.
Conversation path. For each conversation we also keep where it started (a Direct message, a reply to a story, or a comment — with the trigger word and the post) and how far it has progressed through the business's own sales stages (for example "replied", "read the reply", "request", "paid"). The business defines these stages in its agent's settings; the agent marks them, and two of them ("replied" and "read") we derive from Meta's events. A short note the agent may attach to a stage is encrypted like message text. Purpose: so the business owner can see which channels and replies lead to requests. It is kept with the conversation and disappears with it — 30 days after the last message.
Name, username and profile photo. If Meta does not include them with a message, we request them once through the Instagram API with the connected account's token (Meta returns them only for people who have themselves written to the business). We do not copy the photo: we keep Meta's link, which stops working by itself within a few days.
Comments. The business's agent tells us about comments under its posts (the text arrives with phone numbers and other contacts already masked and at most 200 characters long), which trigger word it matched, and whether the person got a public reply and a private reply. The text is encrypted like message text; comments are kept for 30 days, at most the last 500 per account. Aggregated counts by trigger word contain no personal data.
A client may switch this copy off at any time — we then store no conversations, stages, sources or comments for that account at all, and what was already stored is erased at the moment of switching off.
On the client's server the message history is stored by the client as part of its customer relationship records. The client is the controller of that data; we act on the client's instructions.
Account statistics (aggregated numbers about the business's own account and posts, shown in its dashboard) are cached on our platform for up to a few hours to respect Meta's rate limits; they contain no data about individual people. For posts published from the dashboard we keep a short log (time, the dashboard key used, the post link and the first 120 characters of the caption) — the last 20 entries per account.
The access token is refreshed automatically and is deleted when the connection is removed.
11How to delete your data
Business (account owner): remove the app in Instagram → Settings → Apps and websites, or ask us to disconnect. Meta then sends us a deauthorization and/or data deletion request; on our platform we immediately delete the token, the account record, any queued events and the whole stored conversation history — together with conversation stages, sources, agent notes, comments and the team inbox data (notes, tasks, customer cards) — and provide a confirmation code with a status page. Deletion is irreversible: there is no archive to restore from.
Copies on the client's own server (where its agent runs) are controlled by the client, and our platform does not erase them; we forward the request to the client.
Person who wrote to a business: contact that business directly — it controls the conversation history; or contact us and we will forward the request to the client and confirm.
You can also email or message us via the footer links; we respond within 30 days.
12Security
Access tokens, the text of stored messages and comments and the agent's stage notes are encrypted at rest; webhook traffic is verified by cryptographic signatures (Meta's X-Hub-Signature-256 on the way in, our own HMAC on the way to the client's server and on the events the client's agent sends back to us); all connections use HTTPS; secrets are stored in environment variables and never in source code.
13Third-party processors
Meta Platforms (Instagram API), Anthropic PBC, USA (Claude — the AI model that drafts replies and answers in the client cabinet via API; training on our data is turned off), Vercel (hosting), Upstash (storage, Frankfurt region for the client cabinet), Telegram (notifications and sign-in). Each processes data under its own terms.
14Changes
We may update this policy; the date of the last update is shown at the top (2026-11-09). Material changes to the Instagram Connector sections will be announced to connected clients.