Privacy Policy
Last updated: 5 October 2026
IGCDM is an Instagram automation and customer-conversation tool operated by Mohamed Elashram. This policy explains the information handled when a business connects Instagram, enables website chat, or connects its own Telegram bot.
Information we handle
We receive the connected Instagram account identifier and access token through Meta's authorization flow. For configured posts, we may process post identifiers, comments, commenter identifiers and usernames, message delivery outcomes, and related activity needed to run and troubleshoot automations. We also keep limited security and operational logs.
If a business enables website chat, we store the visitor's chat messages, team replies, and conversation status for that business workspace. The chat frame stores a random session token and any unsent message locally in the visitor's browser so the conversation can continue after a reload; the server stores only a hash of the token. We use limited request-rate data to protect the chat from abuse.
If a business connects a Telegram bot, we store its bot identifier, username, encrypted bot token, private-chat identifiers, incoming text, team replies, delivery state, and event identifiers used to prevent duplicate processing. The bot token is not returned to the browser after connection. Telegram processes those messages under its own policies. IGCDM does not use this integration for unsolicited bulk messages.
Business knowledge, optional AI testing and channel replies
Businesses may store facts, prices, FAQs, source text and approved knowledge revisions in their own workspace. Exact FAQ tests do not use an AI provider. Where the platform has activated AI testing, each test requires your confirmation to send the test question and selected relevant approved business information to Cloudflare Workers AI to generate an answer. Do not include passwords, tokens or private customer records. A saved website address alone does not cause an AI model to browse that website.
Application audit logs record the test outcome and knowledge revision, not the test question, answer or business facts. Short-lived usage counters limit AI attempts. Test responses are shown in your browser but are not saved as chat messages by this feature. Cloudflare processes AI inputs and outputs under its Workers AI data-use terms. This feature uses approved knowledge as reference; it does not fine-tune a model. AI answers can be incorrect and should be reviewed against their sources.
Where channel AI is available, workspace owners must separately authorize each channel. Remaining incoming text enquiries and selected relevant approved business facts may then be sent to Cloudflare for answering. Exact matching FAQs do not require an AI call. No previous inbox history is supplied to the model. Customer messages and outgoing replies are stored in the workspace inbox; pending replies are temporarily stored in a delivery outbox, and cleared after processing. Activity records contain outcome metadata, not question bodies or model evidence. Human takeover, exhausted limits and uncertain delivery stop automated continuation. Disabling a channel or editing its approved knowledge prevents further dispatch; already transmitted requests cannot be recalled. Businesses are responsible for explaining this processing in their own customer privacy notices.
How we use it
We use this information to identify comments matching an account owner's chosen keywords, send the configured public reply and eligible private reply, show delivery history, prevent duplicate replies, maintain the connection, and protect the service. We do not sell personal information.
Storage and access
IGCDM runs on Cloudflare infrastructure. Access tokens are encrypted before storage and are not returned to the browser. Customer access is restricted to their workspace. Service operators administer approvals and may access information for authorized support and maintenance. Meta processes Instagram information under its own policies when IGCDM uses its official API.
Accounts and approval
We store your signup email, workspace name, salted password hash, approval status and usage counters. Session tokens are stored as hashes and expire after 12 hours. During the private beta, the operator verifies email ownership directly before approving access; automated verification email is not enabled. Account recovery links are issued only after identity verification and expire after 30 minutes.
Retention and deletion
We retain workspace, chat and delivery records while your workspace is active, including identifiers needed to prevent duplicate sends. Website visitors can clear the local chat token and unsent draft using their browser's site-data controls. Webhook diagnostic records are scheduled for removal after 30 days. Expired sessions and recovery links are periodically removed. Customers can disconnect Instagram in Settings, disconnect Telegram in Channels, or delete their workspace from the dashboard using their current password. Backup copies may remain for the infrastructure provider's recovery retention period. For assistance, see our data-deletion instructions.
Contact
Questions or privacy requests: Hello@mohamedElashram.com.