Alactic privacy centre

Your information. A clearer picture.

One central privacy notice for Alactic’s websites and business products, with specific details for the services you choose.

Updated 29 October 2026 · Communications · CRM · ACID · Voice · AGI

Business products

The data needed for your chosen workspace and features.

Shared responsibility

Your organisation controls its business records and team permissions.

A route to help

Contact support to access, correct or request deletion of information.

1. One notice across Alactic products

This notice explains how Alactic handles personal information across alactic.io, Alactic Communications (web and the Alactic Android app, io.alactic.communications), Alactic CRM, Alactic ACID, Alactic Voice, Alactic AGI and related support and documentation. The information processed depends on the product, deployment, permissions and features you use. Visiting a website does not enable every product or connect your accounts.

Product-specific notices, permissions and contractual data-processing terms provide additional detail. The Communications and Android notice at ac7.io/privacy/ and account-deletion instructions remain available. A customer-managed Azure deployment has a different storage boundary from an Alactic-hosted workspace; this notice does not claim that all Alactic data stays in your Azure subscription.

Reading this notice is not consent to marketing. The service contract, device permissions, AI feature choices and permission to message your customers are separate matters.

2. Who is responsible

Alactic Enterprises Private Limited serves India subscriptions. Its registered corporate address is 297/9 Old Railway Road, Shivpuri Sector-7, Sadar Bazar, Gurugram, Haryana 122001, India. Its operational address is Office No. 434, 4th Floor, VSR 114, Dwarka Expressway, Sector 114, Bajghera, Gurugram, Haryana 122017, India.

Alactic Inc is the developer identified for the Alactic app and the service entity for the UK edition. Its address is 131 Continental Dr, Suite 305, Newark, Delaware 19713, United States. Your order, contract or receipt identifies your contracting entity. Both entities use support@alacticai.com for privacy requests.

For account administration, billing, support and service security, we determine the purposes of processing. For customer records and content a business places in a workspace, that business normally determines why the information is processed; Alactic processes it to provide the chosen service and follow the business’s instructions. If you are a customer of that business, its own privacy notice also applies. Contact it directly or ask us to help route a request.

3. What information is processed

Account and workspace information includes names, login identifiers, phone numbers, email where provided, company information, team roles, invitations, authentication and verification records, session information and connected-account authorisations.

Business records can include contacts, leads, enquiries, sales stages, notes, tasks, appointments, documents, selected imports, business knowledge, consent or opt-out evidence, and the customer information your organisation chooses to enter. Sources include you, authorised teammates, connected services and people communicating with your business.

Communications data can include messages, templates, images, voice notes, other attachments, business profiles, account and phone-number identifiers, audiences, schedules, assignments and delivery, read or failure events. Call data depends on whether you use human team calling or an AI voice feature.

Service data includes IP and browser/device information, installation and notification identifiers, sign-in and workspace activity, diagnostic logs, usage measurements, purchase references, subscription state, invoices and support or deletion requests. Payment providers process payment instruments; we receive transaction and entitlement information needed to provide the service, rather than full card details from Google Play.

4. Purposes and applicable grounds

We use information to create and secure accounts, provide the selected products and connections, deliver messages and workflows, show history and reports, verify subscriptions, respond to support, investigate misuse, maintain reliability and meet applicable legal obligations.

Where UK data-protection law applies to our controller activities, relevant grounds include performing a contract or taking requested steps before a contract; legitimate interests in secure and reliable business services, support and business administration; legal obligations such as accounting; and consent where required for an optional use. You may object to processing based on legitimate interests where applicable. Your business must establish its own appropriate grounds for the customer data it supplies.

Where consent is required, it can be withdrawn for the relevant use. Withdrawal does not undo prior lawful processing or remove an independent legal requirement to retain particular records. We provide feature and privacy choices in accordance with the law that applies to the service and person concerned.

5. Shared workspaces and messaging

Workspace administrators manage membership and access. Authorised teammates may see customer records, conversations, assignments and activity within their permissions. Data is not automatically shared between unrelated customer workspaces simply because products have a common Alactic brand.

Connecting WhatsApp allows information needed for onboarding, account and profile management, templates, messages and delivery events to be exchanged with Meta. Business messaging history is processed to operate the team inbox and connected functions; it should not be assumed to be inaccessible to your authorised users or the providers operating the service.

The business controls the purpose of its campaigns and is responsible for customer notices and permission evidence. Importing a contact or receiving template approval does not establish permission for every use. Deleting an Alactic record cannot recall a delivered message or remove a recipient’s independent copy.

6. ACID and other AI features

When you use ACID, AI Manager, AI testing or another enabled AI integration, prompts and the relevant business knowledge, conversation context, attachments and action information are processed to provide the requested response or workflow. Personal data in those inputs may be processed too. Generated outputs, action reviews, confirmations and usage records can be retained with the workspace.

ACID uses Cloudflare AI infrastructure. A separately configured integration may use OpenAI or another provider identified for that feature. Speech generation and transcription can use ElevenLabs where enabled. Providers receive the input needed for the selected feature; using AI is not a promise of zero retention or processing only on your device.

Supply only the information needed for the task and review AI outputs before relying on them. AI can be inaccurate. Consequential actions and decisions need appropriate human oversight. Ask support for the provider and processing information applicable to your deployment before supplying sensitive business or personal data.

A response report includes the response and explanation you choose to submit for investigation. This notice does not grant blanket permission to repurpose private customer records into public examples or a general model-training dataset; a new use requires an appropriate purpose, notice and legal basis.

7. Voice notes, AI calls and human calls

Voice-note features process uploaded or received audio to transcribe it and, where requested or configured, generate a spoken reply. The transcript, relevant workspace context and generated speech may pass through the AI and speech services needed for that request.

Human team calling uses microphone audio to connect the participants and records connection metadata such as numbers, direction, status and timestamps. The current Communications team-calling feature does not record call audio; its call records have a retention period of up to 30 days.

AI voice experiences have different processing needs: audio is processed for a live interaction, and recordings, transcripts or summaries may be stored where that feature and its configuration enable them. Do not assume the team-calling no-recording statement also applies to AI voice. The business deploying a voice experience is responsible for required caller information and permissions. Contact support for the settings and retention applicable to the particular voice deployment.

8. Permissions, cookies and local storage

The Android app requests permissions for relevant optional functions, such as selected contact imports, notifications and the microphone for supported calls. Selected files and media are uploaded when you choose to provide them. Denying a permission can prevent its associated function without requiring all other functions to stop. The Communications Android notice gives the release-specific details.

Web workspaces use browser storage or similar mechanisms for authentication, security and preferences. Security services and connected providers can use their own technical identifiers. Public website resources can be delivered by hosting or content-delivery services, which receive connection information such as IP addresses.

Non-essential tracking, if introduced, requires the applicable notice and choice before use where required by law. Browser controls can remove or block stored information, but this may sign you out or reset preferences. External links open services governed by their own privacy information.

9. Providers and other recipients

Recipients depend on the selected service. They can include authorised workspace users and intended message recipients; Meta/WhatsApp for business messaging and calling; Cloudflare for infrastructure, security and ACID inference; OpenAI for separately configured AI integrations; ElevenLabs for enabled speech or AI voice processing; Microsoft Azure for applicable AGI deployments; Google/Firebase for app delivery, notifications and related services; and hosting, storage, email and support providers.

Google Play, Razorpay, Stripe or another payment provider shown at checkout handles the relevant purchase. Payment, messaging and independently operated services may also process information under their own notices.

Information may also be disclosed where necessary to professional advisers, authorities, parties handling fraud or legal claims, or parties to a business transfer with appropriate protections. We do not sell personal information or supply customer contact lists to advertising networks. Contact support for provider details relevant to your contract or deployment.

10. Hosting, transfers and security

Alactic-hosted services process information on service infrastructure, not only on your device. Processing may occur in India, the United States and other countries used by the relevant providers. Selecting the India or UK edition does not itself guarantee local-only data residency.

For a customer-managed AGI deployment, the customer controls its configured cloud resources; account, licensing and support records or an enabled external integration can still involve Alactic or other providers. The deployment settings and contract define that boundary.

Applicable international-transfer requirements, including safeguards and an appropriate transfer mechanism where required, apply to the processing. Contact support for the relevant details or data-processing terms. Measures used by the services include authenticated access, workspace permissions, HTTPS and restricted operational access. No online service can guarantee absolute security.

11. Retention and deletion

Account information, business records, messages, knowledge and configuration remain while needed for an active service and its stated purposes. Logging out, uninstalling an app or letting a subscription expire does not itself request deletion. A customer-managed deployment’s resource retention is also controlled by the customer’s cloud settings.

For a verified deletion request covering data under our control, we complete deletion or irreversible anonymisation from active systems within 30 days, subject to lawful exceptions. Deleted data is removed from backups within 90 days of deletion from active systems. During that interval, backup data is restricted to recovery and necessary security uses; deletion requests must be reapplied if a backup is restored.

Some transaction, invoice, security, fraud-prevention, request-handling or dispute records may need to remain for the applicable legal period or until a relevant claim is resolved. We explain the retained categories and reason. When a person leaves a shared workspace, business records the organisation is independently entitled or required to keep may remain, while account access and identifying links are addressed.

Deletion cannot remove independent records held by a message recipient, Meta, a payment provider or another party acting for its own purposes. Product notices describe additional feature-specific periods, including Communications call and presence records.

12. Your requests and rights

Email support@alacticai.com with the product, workspace and account identifier relevant to your request. You can ask for access, correction, deletion or information about processing. Depending on the law that applies, rights can also include portability, restriction, objection, consent withdrawal and complaints to the relevant authority. These rights are subject to applicable conditions and lawful exceptions.

You do not need to sign in or reinstall the app to request deletion. Communications users may also use ac7.io/account-deletion/ or the in-app account-deletion request. We may use proportionate checks to verify ownership and authority, particularly for shared workspaces. Do not send passwords, one-time codes or unnecessary identity documents.

For a request concerning a business’s customer records, contact that business as the organisation controlling their use. We can help route the request and assist within our role. UK users may raise a concern with the Information Commissioner’s Office. Other users may contact the applicable supervisory or grievance authority available under their local law. We respond within applicable legal deadlines and explain any permitted extension.

13. Children and sensitive information

Alactic’s business products are intended for business users, not services directed at children. Do not create an account if you do not meet the applicable age and authority requirements. If you believe a child has provided personal information improperly, contact support so it can be investigated.

Avoid unnecessary sensitive information in messages, prompts, uploads and support requests. Businesses handling regulated or sensitive records must confirm that their contract, deployment, permissions and legal grounds support the intended use before uploading them.

14. Updates and contact

We update this notice when products, processing or legal requirements change. Material changes are communicated through an appropriate service channel where required. The updated date identifies this version; a new purpose of processing requires appropriate notice and any required choices.

Privacy and account support: support@alacticai.com. Include “Alactic privacy”, the product and your region so the request can be routed to the correct team. Postal addresses appear in section 2.