FAQ

Inco is anonymous to the recipient. The recipient never receives your Discord username, avatar, or snowflake ID. While Plus and Pro tiers offer subtle hints (such as Nitro status or scrambled letter fragments), they never reveal your actual account handle. Please note that the bot operator maintains operational dispatch logs for abuse deterrence and platform safety.

Inco stores only technical Discord Snowflake IDs necessary for routing direct messages, managing blocked relationships, rate limiting, and maintaining subscription tiers. Inco never logs public channel conversations and does not read messages outside its direct interactions.

Blocking is completely silent (shadow block). The sender is not informed that they were blocked, and subsequent questions sent by that author will display a mock success response but will be silently dropped without reaching your DM.

No. The 3-hour buffer remains on standby and does not deduct a single second until your very first anonymous question arrives.

Add your server or community promo keyword (e.g. #inco or inco) into your publicly visible Discord Custom Status. When Discord emits presence events, Inco detects the keyword and automatically pauses the timer countdown.

The timer immediately resumes ticking down from wherever it left off. Once the timer reaches 0, the inbox closes automatically and you receive a DM notification.

Yes! Users in supported regions can create a TrueMoney gift voucher for 49 THB (Plus) or 119 THB (Pro) and redeem the link directly using the /redeem command.

Your account safely returns to the Free tier. All question history, blocks, and user records are fully preserved.

Discord prevents bots from sending DMs to users who have disabled direct messages from server members or do not share a mutual server with the bot. The recipient must enable DMs in their privacy settings or join the Inco Mutual Hub to bridge communication.

Questions containing links, URLs, or Discord server invites are rejected automatically before dispatch. Additionally, senders are subject to a 60-second cooldown between questions.