نقرأ الكتالوج ونحسب حالة المواعيد الحالية قبل عرض الصفحة.
This page explains how Mina7 handles messages and links received by its scholarship intake bot.
The bot receives messages and links voluntarily sent to it, whether you are a team member or an external participant when the public inbox is enabled, plus new posts from public channels whose administrator added the bot and a Mina7 operator approved. We may note the media type, but this version does not download files. External participation does not create a team account or grant administrative access.
We retain the minimum needed for review and deduplication: a content digest, normalized HTTPS URL pending source review, bounded public-channel excerpt, public post number where available, and review state. Known tracking and query fields that may carry session or account data are removed, and you must not submit a private or signed link. When Telegram Operations is enabled, private-message text and its numeric reply destination are stored as record-bound AES-256-GCM ciphertext for no more than 90 days and are visible only to an owner in Admin. An external participant is reduced to a keyed digest; we do not retain their name, username, phone number, or raw Telegram ID, and their message remains in the review queue without team access. To accept a team invitation, the invitee must explicitly share their account contact through Telegram's native button. The display name, username, Telegram ID, and phone number are then stored as record-bound AES-256-GCM ciphertext and revealed only to authorized owners for access administration. Typed phone numbers are not accepted. The email invitation temporarily stores a keyed email and one-time referral token and never grants automatic publishing.
We do not store the raw Telegram payload, private-message text in clear, profile photo, file identifiers, or bot token. A team member's consented identity profile is never stored in cleartext. We cannot read other Telegram chats or operate a user account; the inbox shows only messages sent directly to the bot. A redacted excerpt may be retained for an allowlisted public-channel post; private chats and channels are never added to the monitoring allowlist.
A Telegram post is only a discovery signal. We open an official link through controlled access checks, then hold any opportunity for human review. The message never becomes official evidence and no scholarship is auto-published to the catalog.
Intermediate submission details, encrypted Operations content, and email-invitation binding digests become eligible for redaction under a configured window no longer than 90 days and are processed by a bounded daily redaction cycle. The cycle clears encrypted text, reply routing, submitted URL, post identifiers, message dates, and email/account digests while retaining opaque deduplication references and audit evidence. Revoking a member redacts their conversations and blocks replies immediately; a non-displayable keyed denylist digest and opaque audit record remain for three years to prevent legacy access from being restored. Redacted details may take up to 30 days to age out of encrypted, access-restricted backups.
The bot returns a submission reference after receipt. Send that reference to Mina7 to request redaction of that submission; a verified request is completed within 30 days. The reference does not control other submissions. Do not send your account ID or bot token. An opaque audit tombstone without a raw private identity may remain for the retention period above.
We do not sell submission data. Access is limited to authorized operators and the hosting and database providers needed to run the service under access controls. The contact inbox uses Google, and service messages may be delivered through Resend as our email delivery provider. Secrets remain server-only and separate from audit data.
Include the submission reference beginning with M7TG-, and never send your account ID, bot token, or another secret.