Meta & WhatsApp Privacy Policy
AI Cloud Solutions Inc · AICSOL Business Messaging
Effective date: October 7, 2026
Last updated: October 7, 2026
1. Scope and development status
AI Cloud Solutions Inc ("AICSOL," "we," "us," or "our") is developing AICSOL Business Messaging, a business messaging integration for the Meta WhatsApp Business Platform.
The service is in development. This notice covers information handled through its authorized development, testing, account connection and review activities, and related support and privacy inquiries. Descriptions of an enabled integration or workflow apply only when that function is used; they do not mean every planned feature is available. We will update this notice before introducing materially different processing or a production service with additional data practices.
This is the privacy notice for AICSOL's Meta and WhatsApp integration. It does not replace the privacy notice of a business you contact or the separate notices of Meta and WhatsApp. It does not represent Meta approval or endorsement of AICSOL.
Privacy contact: surya@aicsol.com. This mailbox is monitored for privacy and deletion requests.
Company: AI Cloud Solutions Inc
Address: 44 Wood Ave, Building 1, Suite 1F, Mansfield, MA 02048, United States
Business telephone: +1 (508) 578-8912
2. Our role
For inquiries, development-participant administration and support correspondence addressed to AICSOL, we determine why and how that information is handled.
When a business authorizes our integration, we handle its messaging and integration information on its instructions for that business's authorized purpose. The business remains responsible for its customer relationship, the content of its messages, its privacy notices and the permissions needed to contact people. Where applicable, AICSOL acts as its processor or service provider.
An administrator's authorization to connect a Meta account is separate from an individual's permission to receive messages. This privacy policy itself is not consent to marketing.
3. Information involved
We limit collection to information relevant to the particular authorized connection, test or request. Depending on the permissions granted and functions used, this can include:
| Information | Examples and source | Purpose |
|---|---|---|
| Business and participant contact details | Names, work email, business details and support correspondence supplied by administrators or participants | Coordinate authorized access, testing and support |
| Meta and WhatsApp account information | Authorized business portfolio and WhatsApp Business Account identifiers, phone-number identifiers, business profiles, templates, permission and connection status received through Meta | Connect the business account and operate or test the authorized integration |
| Integration credentials | Access tokens and other connection credentials issued through authorized integration processes | Authenticate permitted API requests; these are not requested in privacy-request emails |
| Messaging and form information | Sender and recipient numbers, contact names, message text, replies, and attachments or WhatsApp Flow responses where those functions are used | Send, receive, route and test the requested business interaction |
| Technical and delivery information | Message identifiers, timestamps, delivery status, API errors and relevant troubleshooting records | Diagnose integration issues and protect the service |
| Privacy and support requests | Contact information, the request itself and proportionate verification information supplied to us | Locate records, respond and document the outcome |
Use synthetic or minimal test information wherever possible. Do not submit unnecessary sensitive information, passwords, full payment-card numbers, financial-account credentials or government identification documents through a test conversation or support request.
Connecting a business account does not grant access to a person's unrelated private WhatsApp conversations. The information available depends on the business integration and its authorized permissions.
4. How we use information
We use information to establish authorized connections, develop and verify the requested messaging functionality, manage templates and enabled workflows, investigate delivery or technical problems, answer support inquiries and handle privacy requests. Development and troubleshooting must remain limited to the purpose for which the business or participant supplied or authorized the information.
We do not sell or license Meta Platform Data. We do not use one business's Platform Data for another business's activities, unrelated advertising or unrelated profiling. Access to a business's information is limited to people and providers who need it for that business's authorized service or a permitted legal obligation.
5. Automation and AI
An enabled workflow may route a message, collect a form response or send a configured reply. Participants should contact the relevant business or AICSOL when a result needs clarification or human assistance.
This development-stage notice does not authorize using customer conversations or other Meta Platform Data to train general-purpose AI models. Adding an AI provider or a new AI processing purpose requires an assessment of applicable platform restrictions, appropriate provider arrangements and an updated disclosure before that processing begins. No provider-specific training, human-review or retention guarantee is made by this notice.
6. Providers and disclosures
The following services are relevant to this notice:
- Amazon Web Services (AWS): infrastructure used for development of AICSOL Business Messaging and processing associated with the authorized application functions.
- Meta and WhatsApp: the business-account connection, platform APIs and message transport. Their own terms and privacy notices govern their separate activities.
- Cloudflare: hosting and delivery of the public aicsol.com website and these policy pages. Website requests involve technical information such as IP address and request metadata; this website hosting is distinct from the AWS messaging application.
- Microsoft 365: AICSOL's business email, including correspondence sent to the privacy mailbox.
Information can also be available to the authorizing business and its permitted staff. A client's additional integration or provider receives information only where the client directs it for a permitted, disclosed purpose. Providers acting for AICSOL may process information only for the services requested and subject to applicable restrictions. We may disclose information where legally required; such disclosure must remain consistent with applicable obligations.
We do not publish account credentials or conversation records on these policy pages. You may contact us for information about providers relevant to your particular interaction.
7. Retention criteria
Retention depends on the record and the purpose for which it was obtained. The following criteria govern this development-stage service; this notice does not claim that a fixed production retention schedule or automatic deletion timer has been implemented.
| Record | Retention criterion |
|---|---|
| Test messages, attachments, contacts and Flow responses | Only while necessary for the authorized test or resolution of a specific related issue; delete when that purpose ends or an applicable deletion obligation arises |
| Account identifiers and connection credentials | While needed for the authorized connection; stop using revoked access and remove credentials that are no longer needed |
| Delivery, troubleshooting and security records | Only while necessary to resolve the associated issue, investigate a security event or meet a specific applicable obligation; minimize identifiable content |
| Support and privacy-request correspondence | While needed to handle the request and maintain necessary evidence of its resolution or a legal obligation |
| Copies and backups under our control | Included in the deletion assessment; a backup is not a separate justification for indefinite retention or reuse of deleted information |
We act promptly on deletion requests from individuals, client businesses and Meta. We remove Platform Data as soon as reasonably possible when it is no longer needed for a permitted purpose, the relevant service ends, the applicable account is closed, or deletion is otherwise required. If particular information must be retained by law, we restrict it to that requirement and remove it when the requirement ends.
For a deletion request, we assess relevant active storage, attachments, logs and any backup copies and explain the applicable completion steps and any permitted limitation. Where providers hold information on our behalf, we address those copies with the provider. We do not treat a request as complete merely because an integration has been disconnected.
Meta, the client business and message recipients may hold independent copies under their own policies. AICSOL's deletion does not automatically delete those independent copies.
8. Your choices and privacy requests
You can request access, correction or deletion by emailing surya@aicsol.com. You do not need an AICSOL account. Use the subject Privacy request — AICSOL Business Messaging, or follow our Meta data-deletion instructions.
Provide the business or test account involved, the phone number or email used, an approximate interaction date and what you want us to do. Do not include passwords, access tokens or unnecessary documents. We may ask for proportionate information to verify your authority over the records.
We handle requests manually through the monitored mailbox, coordinate with the client where we act on its instructions, and explain the outcome or any permitted refusal. We respond within applicable legal deadlines and act promptly as required for Meta Platform Data. You can contact the business directly as well; this does not prevent you from contacting AICSOL.
Depending on your location and the applicable law, you may also be entitled to a copy of your information, to object to or restrict processing, withdraw consent, or complain to a privacy regulator. Withdrawal does not affect processing that was lawful before it occurred.
To stop messages, contact the relevant business or use WhatsApp's block and report controls. This notice does not promise an automatic STOP-keyword mechanism. Business administrators can revoke the integration's access through the relevant Meta business settings; stored-data deletion is a separate request.
9. Security and processing locations
The public policy pages use HTTPS. Protecting integration credentials, limiting access and keeping each business's information within its authorized context are requirements for our handling of Platform Data. Please report a suspected exposure or vulnerability to surya@aicsol.com; do not include secrets in the initial report. No system can guarantee absolute security.
AICSOL is based in the United States. Processing locations depend on the configured infrastructure and the relevant provider or business. This notice does not promise a particular AWS region or country-specific data residency. Contact us for information relevant to your interaction. Where a cross-border transfer requires safeguards under applicable law, those safeguards must be established before the transfer; this notice alone does not establish them.
10. Website technologies and children
These policy pages contain no application analytics scripts, advertising pixels or embedded messaging forms. The hosting provider still processes technical requests to deliver and protect the pages. Following a link to another service subjects that visit to the destination's practices. This Meta-specific notice is not a complete cookie inventory for every other AICSOL product or website feature.
The development integration is intended for authorized business representatives and test participants. Do not submit children's information or unnecessary sensitive records for testing. If such information has been submitted inappropriately, contact the privacy mailbox so we can investigate and address it with the relevant business.
11. Changes and contact
We will revise this notice when the integration or its data practices change, update the date above, and provide additional notice or seek permission where required. A new processing purpose is not authorized simply by continued use of the service.
For questions, privacy requests or security reports, contact surya@aicsol.com or write to AI Cloud Solutions Inc at the address in Section 1.