Amobit website and services
The policy covers the public website, unified account, modules, and customer integrations.
Personal data processing policy
This policy explains what data Amobit processes on amobit.io and in Amobit ID, VPOS.am, AI Agents and Amobit Chats.
Updated: 25 September 2026 · 2026-09-25-r2
The policy covers the public website, unified account, modules, and customer integrations.
For Amobit-owned data we act as controller; for customer workflows we may process data on customer instructions.
Data categories depend on the connected service, agreement, customer settings, and integrations.
Use this address for privacy questions, legal details, or data requests.
Data categories
Amobit processes the minimum data needed to answer requests, provide access, handle billing, support services, run integrations, and protect the platform.
On amobit.io we may process name, phone, email, company, team size, message, source URL, referrer, UTM parameters, IP address, user agent, and consent choices.
In id.amobit.io we process user identifiers, email, login events, organization membership, roles, billing profiles, invoices, entitlements, and provisioning events.
Connected services may process payment events, messages, prompts, AI outputs and the operational data required by customer-configured integrations.
APIs, webhooks, and customer integrations may create audit logs, diagnostic events, request metadata, error reports, and support correspondence.
Document priority
Mandatory law prevails. A signed agreement prevails in its expressly agreed scope; specific processing instructions govern data processing. Orders and invoices specify product, quantity, period and price, but do not expand processing purposes or remove safeguards. Correspondence changes terms only by express agreement of authorised representatives. An invoice does not override notices to data subjects.
2. Controller and party roles
For the public website, Amobit-owned accounts, support, invoices, and service security, Gulian Digital LLC normally acts as a personal data controller. For customer chat, AI, payment and integration workflows, it may act as a processor or technical contractor within the agreed contract scope.
Gulian Digital LLC is the Armenian operator of Amobit services unless a signed customer document defines a more specific role for a particular workflow.
3. Purposes
We process data to answer requests, run demos, register and protect accounts, activate modules, issue invoices, process payments, handle support, maintain integrations, investigate errors, and prevent abuse.
In product and integration work, processing is tied to the configured workflow: CRM deal, order, payment, chat, ad report, AI scenario, ERP task, or API event. Amobit should not receive broad exports or unnecessary personal data without a real need.
4. Website and contact forms
When a user submits a form or contacts the team, we may process name, email, phone, company, position, team size, message text, selected product, language, UTM parameters, referrer, source URL, IP address, user agent, and follow-up communication history.
This data is used to respond, prepare commercial context, assign responsibility, prevent duplicates, protect from spam, analyze channel performance, and keep support context.
5. Amobit ID
In id.amobit.io we may process email, name, organization, company legal name, roles, membership, sign-in events, OTP and login-link events, SSO tokens, billing profiles, invoices, ledger entries, subscription status, module entitlements, and provisioning logs.
This data is needed for service access, permission separation, access recovery, invoicing, module activation, SSO context handoff, and investigation of disputed operations.
6. VPOS and payments
For VPOS.am we may process merchant data, invoice data, order data, amount, currency, payment status, transaction identifiers, callback and webhook events, technical logs, payer details received from a payment provider, and reconciliation data.
Amobit should not store full card numbers, CVV/CVC, or other payment secrets where payment is handled by a bank, acquirer, or payment provider. Such data is processed by the relevant payment provider under its own rules.
7. AI services
In ai.amobit.io we may process prompts, AI outputs, conversation history, system instructions, knowledge sources, attachments, task status, quality ratings, tool calls, integration events, and agent action logs.
The customer should not send special categories of personal data, payment secrets, trade secrets, or children data into AI scenarios unless this is explicitly agreed and needed for an approved scenario with additional safeguards.
8. Chats
In chats.amobit.io we may process messages, customer names or nicknames, contacts, channel IDs, attachments, dialog status, operators, internal notes, queues, SLA labels, timestamps, routing, and integration events.
If the customer connects a messenger, social network, telephony, website, or CRM, data may move between those systems according to customer settings, access rights, and the relevant platform terms.
9. Sharing and providers
To operate the website and services, we may use hosting, domains, email, SMS/OTP, analytics, payments, banks, CRM, messengers, ad platforms, AI providers, logging, monitoring, backups, development, and support providers.
Providers receive only the data needed for their role. If a customer connects a third-party platform, data may move to or from that platform according to customer settings and the platform terms.
Retention and processing end
Before processing, the order or settings specify periods for audio, original and processed transcripts, AI results, messages and attachments. Software defaults do not prove deletion is operational in every profile. If no period is shown, agree it through info@amobit.io before supplying the data. Missing configuration does not authorise indefinite retention.
Backup expiry and security-log periods are specified separately. Accounting and legally required records are retained for applicable periods with restricted use. A legal hold records its basis, scope and review. At instruction end, return or deletion is agreed; restoring a backup must not restart processing of previously excluded data.
11. Cookies and analytics
The website and services may use cookies, local storage, session storage, and similar technologies for security, session handling, language, forms, abuse protection, SSO, billing, user settings, and diagnostics.
Analytics and advertising tools load only where configured and permitted by user consent or another applicable basis. Users can limit cookies in the browser, but some service features may not work correctly without technical storage.
12. Rights and requests
To process a request, we may need to confirm identity and identify the account, organization, service, request, payment, integration, or specific processing context. The response may depend on the Amobit role: controller, processor on customer instructions, or technical contractor.
Some records cannot be deleted immediately where they are needed for accounting, payments, security, anti-fraud, dispute resolution, contract performance, rights protection, or legal compliance.
13. Policy changes
Amobit may update this policy when new modules launch, infrastructure changes, providers are connected, laws change, contract models change, or actual data processing processes change.
The current version is published on this page. Material changes that require separate notice or consent are handled through the website, service interface, email, agreement, or another applicable channel.
Updated: 25 September 2026
CRM, telephony, messages, audio, transcripts and AI outputs are subject to the annex “CRM, telephony and AI data processing instructions” to the offer. An organisation’s assurance of lawful grounds differs from an individual call participant’s consent. The customer ensures grounds and notices; Amobit fulfils the instructions and its own data protection duties.
Speech recognition and AI providers receive only data needed for the agreed scenario. Current recipients, countries and retention periods can be requested before processing at info@amobit.io. Currency, language and product region do not establish data residency. International transfer requirements are assessed separately.
Restrictions on specific data or withdrawal of a processing ground must be reported through available settings or info@amobit.io. Identify the company and record; do not send passwords or a full recording unnecessarily. Processing and deletion take account of individual rights, applicable law, instruction duration and mandatory retention of certain records.
Processing safeguards and assistance
Amobit limits staff access to authorised tasks, ensures confidentiality and applicable safeguards. Support access is limited to what is necessary. Contractors act within instructions and applicable protection obligations; material changes to recipients and transfers are communicated before applying them to customer data.
Amobit notifies the customer without undue delay of a discovered security breach affecting instructed processing, provides known facts and updates its findings. Statutory authority and data-subject notification deadlines apply to each party according to its role.
Send access, correction, restriction, export and deletion requests to info@amobit.io. Identity and authority are checked; Amobit assists the customer within applicable legal deadlines. Organisation-data requests are routed to the responsible customer without waiving Amobit’s own duties. Completion evidence, safeguards information and reasonable verification are agreed without exposing others’ data or secrets.
Providers, countries and training
Before transfer, identify the actual recipient, legal entity, purpose, data categories, processing countries, retention and international-transfer basis for the source. Brand names are not a complete verified register. Order-specific details are available through info@amobit.io. Currency and language do not establish residency.
Google Gemini and OpenAI may be used on agreed routes; this does not mean every provider receives all data. Training, logging and retention depend on the API, service tier and settings. No training does not mean zero retention. Amobit does not train its own public models on customer content; changing that purpose requires separate agreement. Confidential data may not be sent to a provider mode that prohibits it.
Revisions and languages
Revision ID: 2026-09-25-r2. The previous revision is preserved at /legal-archive/2026-09-25-r1/ as ru-offerta.html, en-offerta.html and hy-offerta.html, with corresponding policy files. New terms do not create retrospective consent. RU, EN and HY are intended to have the same scope. Translation discrepancies do not automatically expand duties and require resolution by agreement; mandatory law prevails.
Company details
Gulian Digital LLC is the single operator of the website, Amobit services and contractual relationships. The company is registered and operates under the laws of the Republic of Armenia.
Republic of Armenia
Single operator of amobit.io, Amobit services, billing, implementation and technical support.
Rights and controls
Some records may need to be retained for billing, payments, security, legal requirements, fraud prevention, audit, or service continuity.
Identify the request, account, organization, payment, service, or integration that your request relates to.
Send corrections if contact, account, billing, payment, or organization details are outdated.
We will remove eligible data or explain why a record must be retained.
Customer administrators should manage members, roles, API access, channels, retention periods, and end-user rights.
Use the security/support channel for technical incidents, suspected leaks, or access compromise.