← All guides

ALACTIC COMMUNICATION 24/7

Alactic Communications Privacy Policy

How the Communications app and web workspace handle personal data, permissions, AI, purchases and deletion requests.

ALACTIC COMMUNICATIONS · WEB & ANDROID

Last updated: 23 October 2026. This Privacy Policy explains how Alactic Communications handles personal data in its Android app, listed as Alactic (io.alactic.communications), web workspace, connected WhatsApp features and related AC7 guides. It covers the India and United Kingdom editions. Separate Alactic products have their own privacy information.

You choose which optional features to use. Importing contacts, enabling AI or sending a campaign involves processing the information needed for that feature. Reading this policy is not consent to receive marketing messages.

1. Who is responsible for your information?

Alactic Inc is the developer identified for the Alactic mobile app on Google Play. The service entities are Alactic Enterprises Private Limited for India subscriptions and Alactic Inc for the United Kingdom edition. Your order or payment receipt identifies the contracting seller and payment provider; a store purchase does not change the privacy contact below.

Alactic Enterprises Private Limited

Registered corporate address: 297/9 Old Railway Road, Shivpuri Sector-7, Sadar Bazar, Gurugram, Haryana 122001, India.

Operational address: Office No. 434, 4th Floor, VSR 114, Dwarka Expressway, Sector 114, Bajghera, Gurugram, Haryana 122017, India.

Alactic Inc

131 Continental Dr, Suite 305, Newark, Delaware 19713, United States.

Privacy and account support for both editions: support@alacticai.com.

We determine how account administration, billing, support and service-security data are used. For customer contacts, messages and other records a business puts into its workspace, that business normally determines the purposes of processing and we process the data to provide its chosen services and follow its instructions. Its own privacy notice also applies. If you are that business’s customer, you can contact the business or ask us to help route your request.

2. Information we collect

Data depends on your account, permissions and the features you use.
InformationExamples and sourceWhy it is used
Account and workspaceName, login ID, email where supplied, phone number, company name, team role, invitations and account verification records.Create and secure accounts, identify your workspace, manage access and provide support. Owner phone signup and invited team-member email login collect different required fields.
Authentication and connectionsPassword verification records, session tokens, verification challenges and authorisations for your connected WhatsApp business account.Authenticate users, prevent misuse and operate the integrations you connect. Do not send your password or one-time codes to support.
Contacts and customer recordsSelected device contacts, imported files, names, phone numbers, email addresses, companies, labels, notes, enquiries and permission or opt-out evidence.Maintain your business address book, manage audiences and follow-ups, apply messaging preferences and avoid duplicate records.
Messages and mediaIncoming and outgoing WhatsApp messages, templates, images, audio, video, documents, profile photos and other files you or your contacts provide.Deliver conversations, display history to authorised teammates and run the campaigns or workflows you configure.
Messaging and business metadataBusiness profile details, connected number and account identifiers, recipient lists, assignments, delivery/read/failure events, campaign schedules, account quality and available billing information.Operate the connection, show delivery outcomes, coordinate the team and provide reporting or cost estimates.
AI and automation contentPrompts, relevant conversation context, business knowledge, uploaded content, generated replies, proposed actions, confirmations and usage measurements.Generate and test replies, follow your business configuration, perform supported actions and enforce usage allowances.
Team callsCaller and business numbers, call direction, assigned teammate, connection status and timestamps. Temporary connection information is used to establish audio.Connect calls, check calling permission, avoid duplicate dialling and troubleshoot failed connections. Team-call records are retained for up to 30 days. This feature does not record call audio.
Purchases and subscriptionsPayment references, purchase tokens, plan and product identifiers, subscription state and expiry, invoice information and refund records.Verify purchases, provide paid access, prevent fraud and meet accounting requirements. Google Play processes the payment instrument for Play purchases; we do not receive your full card number from Play.
Technical, device and activity dataIP address, request/error information, device or browser information, installation and push-notification identifiers, sign-in events, presence and actions within a workspace.Secure and maintain the service, deliver notifications, diagnose failures and show team activity to authorised workspace users. Network providers also receive technical connection data.
Support and reportsSupport messages, deletion requests, attachments and AI responses you choose to report, together with the account and ticket reference.Investigate issues, respond to privacy requests and review reported AI content.

Workspace administrators, teammates, connected providers and the people messaging a business may supply information about you. The service does not depend solely on data typed into the mobile app.

3. Android permissions and your choices

  • Contacts: device access is optional and requested for importing contacts. The import flow lets you select and review contacts before sending the selected records to your workspace. Denying this permission does not prevent signing in or using records already in the workspace.
  • Notifications: you can allow or disable notifications in Android settings. Push services receive installation or delivery identifiers. Depending on your settings, notifications can show account information or message previews on a device’s lock screen.
  • Files and media: you select supported attachments or import files through the device picker. Content you choose to upload is sent to the service and, where needed, messaging or AI providers. Incoming media can also be stored with the conversation.
  • Microphone: supported team-calling releases request microphone access when you choose to make or answer a WhatsApp call. Audio is transmitted through the calling connection to the other participant; Alactic does not record team calls. Denying access prevents calls but does not prevent messaging. During the foreground calling pilot, leaving the Calls screen or backgrounding the app stops the call.
  • Location and camera: this application does not request device location or camera access. You can select existing photos or audio through the device picker. IP addresses still reach network services.

Revoking a device permission stops further access through that permission. It does not erase previously imported records; use the relevant workspace controls or the deletion request route for those records.

4. How and why we use information

We use information to provide accounts and the features you request, support users, secure the service, verify payments, investigate misuse and meet legal obligations. We use service and usage records to maintain reliability and understand whether features work. The current app does not contain an advertising network or use customer conversations to target advertisements.

Where UK data-protection law applies to processing for which we are a controller, the relevant grounds are performance of a contract with you or steps you request before a contract; legitimate interests in providing a secure, reliable business service and administering business relationships; legal obligations such as accounting and responding to lawful requests; and consent where required for a particular optional use. An organisation using our service must separately establish the lawful grounds for its customer data and messages.

Device permission, accepting service terms and permission to send marketing messages serve different purposes. Withdrawal of consent does not affect processing that was lawful before withdrawal or processing based on another applicable ground.

5. WhatsApp and shared workspaces

Connecting a business account allows Alactic to exchange the relevant account, template, profile, message and delivery information with Meta/WhatsApp. We store and process conversation data to provide the team inbox and related functions. Do not assume that messages are inaccessible to Alactic, your authorised teammates or the providers needed to operate these business features.

Workspace administrators control team membership and permissions. Authorised users may see shared customer records, conversations, assignments and activity information. Review team access before placing confidential information into the workspace.

The business is responsible for its messaging purpose, customer notices and permission evidence. A template approval, an import or a contact’s earlier reply does not establish permission for every campaign. Deleting an Alactic record cannot recall a message already delivered to its recipient or erase a recipient’s own copy.

6. Alactic ACID and AI features

When you test AI, ask AI Manager for help or enable supported AI replies, the service processes the prompt and the relevant business knowledge, conversation history and action context needed to respond. This can include personal information in a customer’s message or in the records you supply.

ACID uses Cloudflare AI infrastructure. Separately configured legacy AI integrations may use OpenAI when enabled for that integration. These providers process the input needed for the configured feature. We retain conversation, configuration and usage records where needed for history, operation, support and allowance tracking; using AI is not an assurance of zero retention.

Do not include unnecessary confidential or sensitive information in knowledge files, prompts or reports. Review outputs and use human oversight for consequential decisions. You can pause supported AI or automation features and continue handling conversations manually.

Reporting a response sends the selected response and the explanation you submit to Alactic support. You can review and remove private details from the report before sending it.

7. Who receives information?

Access and disclosure depend on the feature used. Recipients include:

  • Your authorised workspace users and intended message recipients, as part of the actions and access your organisation enables.
  • Meta/WhatsApp, for business onboarding, account/profile management, templates, sending and receiving messages, and delivery information.
  • Cloudflare, for services such as security challenges and ACID AI processing; and any separately enabled legacy AI provider described above.
  • Google/Firebase, for mobile push delivery and related installation identifiers; Google Play for app distribution and purchases; and cloud infrastructure used for service backups.
  • Hosting, storage, communications and support providers, including infrastructure used to run the application, store media, deliver service emails and handle support. Access is limited to the purpose of the service they provide.
  • Payment providers, such as Google Play for app purchases and Razorpay or Stripe where available for a website purchase. The provider shown at checkout also has its own privacy information.
  • Professional advisers, authorities or other parties where necessary, to meet a legal obligation, investigate fraud, protect rights or handle a business transfer with appropriate protections and notices.

We do not sell personal information or provide customer contact lists to advertising networks. Transfers necessary to deliver a requested service still occur. A provider’s own services may be subject to its separate terms and privacy policy.

8. Storage, international processing and security

Information is processed on service infrastructure and by the providers needed for your selected features, rather than only on your phone. Processing may take place in India, the United States and other countries where the relevant infrastructure or support provider operates. Choosing the UK or India edition is not a promise that all data stays in that country.

Where applicable law requires protections for an international transfer, those requirements apply to the transfer, including an appropriate legal mechanism and safeguards. Contact support for the provider and transfer information relevant to your workspace or a required data-processing agreement. We do not claim a data-residency certification or an adequacy status merely because this policy is published.

Measures used by the service include authenticated workspace access, permission checks, HTTPS connections and protected credentials. Access to operational systems is restricted. No service can guarantee absolute security. Keep account credentials private, use appropriate device security and report suspected unauthorised access promptly.

9. How long we keep information

We keep information only for its service purpose or a necessary legal, security or dispute-related purpose. An active account’s customer records, conversation history, knowledge, settings and support history can remain while needed to provide the workspace. Uninstalling the app, logging out or a subscription expiring does not itself request deletion.

Retention and deletion rules
RecordRetention approach
Account and associated personal dataFollowing a verified deletion request, we complete deletion or irreversible anonymisation from active systems within 30 days, except the limited records described below. We explain any retained categories and reason.
Workspace contentWe remove the content covered by an authorised workspace-deletion request within the same 30-day period. When an individual leaves a shared workspace, records the business is independently entitled or required to keep may remain for that purpose; access and identifying account links are addressed as part of the request.
BackupsDeleted data is removed through backup expiry or deletion within 90 days of deletion from active systems. During that interval it is restricted to recovery and necessary security purposes. If a backup is restored, deletion requests must be reapplied before the restored data returns to ordinary use.
Verification and temporary recordsVerification challenges expire when their security purpose ends. Other temporary delivery or workflow records expire according to the feature’s retention settings. These are not permanent archives of your account.
Team presencePresence-session records use a 90-day retention window. Separate records needed for security or a dispute can have a different justified retention period.
Billing, fraud prevention and disputesWe may retain the necessary transaction, invoice, security, request-handling or dispute evidence for the applicable legal retention period or until the relevant investigation or claim is resolved. The period depends on the record and jurisdiction; retained data is restricted to that purpose, rather than kept for continued marketing or ordinary account use.

Our deletion commitment covers data under our control, including deletion instructions to service providers where applicable. Independent records held by a payment provider, Meta or a message recipient are subject to that party’s obligations. Where a specific law requires a different deadline or a lawful exception applies, we explain it in the request response.

10. Delete your account or request removal of data

You do not need to reinstall the app or sign in to submit a request. Visit our account and data deletion page or email support@alacticai.com with the subject “Alactic Communications account deletion”. Include your login ID or account phone/email and workspace name so we can locate the correct account.

In the app, open Workspace → Account settings → Request account deletion and submit the support request. We verify ownership using information proportionate to the request and confirm its scope and outcome. Requesting deletion is not an immediate automatic wipe, and any identity check must not be used to prevent a valid request.

You can also request correction, export or deletion of specific personal data without closing the whole account, subject to applicable rights and shared-workspace responsibilities. Account deletion does not itself cancel a Google Play subscription; manage that separately in Play. Cancellation is not a condition for submitting a privacy request.

11. Your rights and privacy requests

Depending on applicable law, you may request access, correction, erasure, restriction or portability of your personal data; object to certain processing; or withdraw consent where processing relies on it. Rights can have lawful exceptions. We respond within the applicable legal timeframe and explain any justified refusal or extension.

Email support@alacticai.com. Include enough information to identify the account or conversation concerned. Do not include passwords, one-time codes, full card details or unnecessary identity documents. We may ask for proportionate verification through a secure route.

If the relevant data belongs to a business’s customer workspace, we may refer the request to that business and assist it. You may complain to the competent data-protection authority where applicable. UK individuals can contact the Information Commissioner’s Office. India rights and complaint mechanisms apply to the extent the relevant legal provisions are in force and applicable.

12. Cookies, local storage and linked pages

The app and web workspace use session or local storage for authentication, security, saved settings and drafts. Cloudflare security challenges and connected services can also use technical storage or identifiers. Public AC7 policy pages do not require an account or a purchase to read.

Browser controls can clear or block storage, but doing so can sign you out or prevent a feature from working. Links to Meta, Google Play, payment providers or another website open services with their own privacy notices. This policy does not give those services permission to use your data for unrelated purposes.

13. Children and sensitive information

Alactic Communications is a business tool intended for adult account holders and authorised business users, not a service directed at children. If you believe a child has supplied personal data without the necessary authority, contact support so we can investigate and take appropriate action.

Do not upload unnecessary health information, financial secrets, government identifiers or other sensitive information. A business handling such data remains responsible for the additional notices, lawful grounds, safeguards and permissions required for its use.

14. Changes and contact

We publish changes with an updated date and provide additional notice when required for a material change. A new purpose requiring consent will not be justified merely by editing this page.

For privacy, deletion or processing questions, email support@alacticai.com or write to the relevant Alactic address in section 1. Include “Communications privacy” and your edition so the request can be routed correctly.