Terms of Service

These terms govern the Allinaa website and the Allinaa Bot chatbot service. Please read section 9 (what we do not guarantee) and section 13 (limits on our liability) carefully — they decide who carries which risk.

Last updated: 17 October 2026 iGlomart LLC (Delaware, USA) Contact: info@allinaa.com

1. Who these terms are between

These Terms of Service ("Terms") are an agreement between iGlomart LLC, a Delaware limited liability company trading as Allinaa ("Allinaa", "we", "us"), and the person or organisation that uses our website or our services ("you", "Customer").

They cover:

By using the website, by signing up for Allinaa Bot on our sign-up page, by signing in to a panel, by embedding the widget, or by accepting a written offer from us, you agree to these Terms. Our Privacy Policy and Data Deletion Instructions form part of them.

If you are using the service on behalf of a company, you confirm that you are authorised to bind that company, and "you" means that company.

2. Who may use the service

3. What we provide

Allinaa Bot is a hosted AI assistant for your business. Depending on your plan it can:

There is no setup fee for the AI chatbot. You set your assistant up yourself on our sign-up page and add it to your website with our install guides, and our team helps you if you need it (see section 5.3). On Premium, bookings into a Google Calendar and leads to a Google Sheet are connected with the Allinaa team at no extra charge. Features marked Premium are available only on the Premium plan, and some depend on a third-party platform granting access to your account (see section 8).

4. Plans and published prices

The prices below are the prices published on our website at the date of these Terms. The AI chatbot prices are fixed monthly prices with no setup fee. The Localization and Lead generation prices are starting prices: the final price is agreed with you in writing before work starts. Prices are in US dollars and exclude any taxes that may apply.

ServiceStandardPremium
AI chatbot$350 per month, no setup fee$800 per month, no setup fee
Localizationfrom $300 per project: one language, reviewed by a person, adapted for local customersfrom $500 per project: up to three languages, cultural adaptation of prices, examples and tone, SEO titles and descriptions, 30 days of free updates
Lead generation$1,000 per month: 200 targeted contacts, e-mail outreach, monthly results report$1,500 per month: 500 targeted contacts, e-mail, LinkedIn and social outreach, trust-building content, weekly results report

The monthly chatbot fee starts when we activate your service in writing — not when you sign up or set your assistant up, and not when you switch it on yourself in the free trial. Additional usage or work beyond what is included is agreed with you in advance and is never billed automatically.

4.1 Free trial

5. Included allowances and limits

5.1 Standard chatbot

5.2 Premium chatbot

5.3 Support

Our target for a first response to a support request is one business day, on Standard and Premium alike. This is a service target, not a contractual service level agreement, and we do not offer an uptime guarantee or service credits.

6. Billing, taxes and refunds

7. Your obligations as a business customer

These obligations are central to the agreement. We cannot run a compliant AI assistant for you unless you meet them.

7.1 Lawful use and your end-customers

7.2 Your knowledge base and content

7.3 Accounts and access

7.4 Replies you publish

8. Connected messaging channels and provider fees

8.1 Each platform's own rules apply to you

When you connect a channel, you also enter a relationship with that platform. You must comply with that platform's terms, developer policies and messaging rules, including (as applicable) the Meta Platform Terms and WhatsApp Business Messaging Policy, the Telegram Bot Developer Terms, the Google API Services User Data Policy and YouTube Terms of Service, the LinkedIn, X, TikTok, LINE, Viber, WeChat, Discord, Slack and Microsoft Teams developer and platform terms. If a platform suspends or restricts your account, our service for that channel stops working, through no fault of ours.

YouTube. By connecting or using the YouTube comments channel, you — and the users of that channel — agree to be bound by the YouTube Terms of Service (https://www.youtube.com/t/terms). Google's handling of personal data is described in the Google Privacy Policy (https://policies.google.com/privacy). The same applies to the Google Business Profile reviews channel, which uses Google APIs under the Google API Services User Data Policy.

Meta. For Meta channels we act as a Tech Provider under the Meta Platform Terms: we process Meta Platform Data only at your direction, we act on your deletion requests, and we pass on to you any communication Meta sends us about a user's data request. The Meta app behind those channels belongs to iGlomart LLC.

8.2 You supply your own credentials

For most channels you connect your own account — your own Telegram bot token, your own mailbox, your own page or profile. You confirm you are authorised to connect that account. We store those credentials encrypted and delete them when you disconnect.

8.3 Availability is not guaranteed

A channel works only while the platform grants the necessary access. Several channels require a platform's business verification, app review, paid plan or commercial agreement, which that platform may refuse, delay, change or withdraw at any time. We do not guarantee that any particular channel will be available to you, now or in the future, and the availability of a channel is not a condition of your plan unless we have agreed it in writing for your account.

Being specific, because "available" can mean two different things: Telegram is the only channel we have run end to end against the real provider (confirmed 14 October 2026). Every other channel is built and tested, but has so far been exercised only against test doubles of the provider's API, and several additionally depend on Meta's, Google's, LinkedIn's or TikTok's review of the Allinaa app. We will confirm a channel for your account once it has been proven against the real provider; until then, treat it as planned rather than delivered.

8.4 Fees charged by the platform, not by us

Some platforms bill you directly. Those fees are yours, they are not included in our prices, and we do not mark them up or collect them. Examples, based on each platform's own published terms:

Your cabinet shows the units and categories that a provider bills to you, where the provider reports them. Where a provider does not report an amount, we show the units and the billing category and leave the amount blank rather than guess.

Some providers bill us instead (for example X charges per direct-message event). Where a channel's cost falls on us, we may require a separate written agreement, an add-on fee, or we may decline to enable that channel for your account.

8.5 Public channels need your approval

Replies to comments and reviews are never posted automatically. The assistant may draft; a person at your business approves or edits before anything is published. For LinkedIn, AI drafting is disabled entirely and replies must be written by a person, because LinkedIn's developer policy forbids AI-written replies to member content.

9. What we do not guarantee

AI answers can be wrong. The assistant generates replies automatically with a third-party AI model. It can be incomplete, outdated or simply incorrect, even when your knowledge base is correct. It can misread an image or a document. We do not warrant that any reply is accurate, complete, suitable for a purpose, or free of error.

You are responsible for the replies your chatbot gives to your customers and for anything your team or your approval publishes. You decide what information the assistant may use, you decide whether to enable automatic answering on a channel, and you can take over any conversation at any time. If an answer matters — a price, a legal statement, a health or safety question, a commitment to a customer — check it before relying on it, and tell your customers to confirm important details with a person.

In addition, and to the fullest extent permitted by law:

10. Acceptable use

You must not, and must not allow anyone else to:

We may enforce these rules by suspension (see section 15), and a serious breach may be reported to the relevant platform or authority.

11. Data protection and roles

12. Intellectual property

13. Limits on our liability

To the fullest extent permitted by law:

14. Your indemnity

You will defend and indemnify us against third-party claims, and against fines, damages and reasonable legal costs arising from them, where the claim results from:

We will tell you promptly about such a claim, let you control the defence (subject to our approval of any settlement that affects us), and cooperate reasonably at your cost.

15. Suspension and termination

16. Changes to the service and to these terms

17. Governing law and disputes

18. General

19. Contact

iGlomart LLC

Delaware, United States of America — trading as Allinaa
E-mail: info@allinaa.com
Website: https://www.allinaa.com
Product: https://bot.allinaa.com

Related pages: Privacy Policy · Data Deletion Instructions


Annex 1 — Data Processing Addendum

This Addendum forms part of the Terms and applies to every customer whose end-customers' personal data we process, without a separate signature. Where it conflicts with the rest of the Terms on the processing of that data, this Addendum wins. "Controller", "processor", "personal data", "processing", "data subject" and "personal data breach" have the meanings given in the EU General Data Protection Regulation (GDPR) and, where it applies, the UK GDPR.

A1. Roles and subject matter

A2. Our obligations as your processor

A3. International transfers

Allinaa processes the personal data in the United States, and the sub-processors listed in the Privacy Policy operate in the United States and other countries. Which safeguard is in place for which recipient — and for which recipient we do not yet hold an Article 46 mechanism of our own — is stated exactly in the Privacy Policy, section 18, and a copy of the clauses we rely on is available on request. Where you require specific transfer terms or the EU standard contractual clauses signed with us directly, write to us before you launch.

A4. Deletion and return (Article 28(3)(g))

On the end of the provision of the services, we delete or return all personal data we processed for you, at your choice, within 60 days, and delete existing copies except where law requires us to keep them — in which case we tell you which records and for how long, and we keep processing them only for that purpose. A safety copy of the database taken before a software release may still contain data until that copy is deleted; such copies are never used to answer a request, only to restore the service (Data Deletion Instructions, section 5.2). Nothing in this paragraph limits a data subject's right to erasure, which we honour whenever it is exercised.

Annex I — Details of the processing

ItemDetail
Categories of data subjectsYour customers and prospective customers who use your chatbot, message you on a connected channel, comment on your posts, review your business, send you a file, make a booking, report a problem or ask for a quote; and the members of your own team who hold an Allinaa account.
Categories of personal dataName; e-mail address; phone number; the content of chat messages, channel messages, comments and reviews; files sent, including photographs, screenshots and documents, and facts extracted from them; the public identifier and display name the platform gives us for a channel user, including a WhatsApp phone number where Meta sends one; inquiry, booking, problem report, quote and follow-up details, including the service asked about, timing, requirements and an AI-written summary; the page URL and title a website visitor was on; a time zone sent with a booking; an opaque session identifier; the stored copies of e-mails we send on your behalf; internal notes your team writes; for your team members: e-mail address, name, role, password hash, sign-in times and IP addresses in the audit log.
Special category dataNot requested, not required and not designed for. The service is not a HIPAA-compliant platform. You must not configure the chatbot to collect it, or invite your customers to send it (section 7.2). Anything that nevertheless arrives in a free-text message or a file is processed only to pass the conversation to you, and is deleted on request.
Frequency of the processingContinuous, for as long as your subscription runs.
RetentionAs set out in the Privacy Policy, section 12: file contents and raw channel payloads are deleted automatically after 30 days (LinkedIn member text after 48 hours, YouTube data after 30 days); the remaining records have no automatic deletion date today and are deleted on request within the deadlines published there, or on the fixed schedule we agree for your account.
Sub-processorsAs listed in the Privacy Policy, section 19, with the purpose and the data that can reach each one.

Annex II — Technical and organisational measures

The measures we have implemented are listed, one by one, in the Privacy Policy, section 17.1, and that list forms Annex II of this Addendum: scrypt password hashing with per-user salts and constant-time verification; tokens stored only as hashes; AES-256-GCM encryption of messaging channel credentials with per-value nonces, bound ciphertexts, key rotation and fail-closed behaviour; constant-time per-provider webhook signature verification with body and event caps; tenant isolation enforced on every management route and file path; an audit log of management, administration and authentication actions including denied attempts, without request bodies, headers or secrets; time-limited, reason-recorded support access; a platform administration token accepted only from the server itself; file type detection from content, size and quota limits, a decompression-bomb guard, image re-encoding that strips EXIF and GPS data, built-in content checks, optional ClamAV where configured, and hardened download headers in the cabinet; secret masking in logs; prompt-injection guards; idempotency; and server-side fetches pinned to public provider hosts.

The measures we have not implemented are listed just as explicitly in the Privacy Policy, section 17.2, and that list is part of Annex II too: no encryption at rest of the database or of uploaded files (only channel credentials are encrypted, and their key sits in the environment of the same server); TLS terminated in the hosting infrastructure rather than by the application, with no HSTS header and no HTTP-to-HTTPS redirect of its own; a chat API that accepts requests from any origin, because businesses embed the widget on their own sites; no automatic purge of audit records or AI usage records; and built-in file checks that are not antivirus software. If your assessment of the risk requires a measure we do not have, do not process personal data with us until we have agreed it in writing.

Back to top ↑