This document entails the privacy policy and agreement that you accept when adding Iko to a server, or as a member of such a server. This document does not supersede the Developer Terms of Service.
We try our best to avoid data collection unless absolutely necessary. The only data we collect about you is the information you provide us when you use our Service. If you delete your Discord account, the data we have tied to that account cannot be used to identify you.
We may collect additional information when participating in servers with certain Iko systems enabled. Those features are described below.
Warning
All of the below data is only stored if entered by user or given permission to. Iko won't store any data anonymously! As soon as you stop either of the system the data related to that system will be deleted.
Ticket system: Following data is stored while you use ticket systemmessage ID: message ID of ticket embed is stored and deleted as soon as the embed is deletedguild ID: guild ID is stored to fetch the category to form ticketscategory ID: category ID is stored for creating ticketschannel ID: channel ID of ticket channels is stored for bot to keep track of inactivity. Also log channel ID is stored to keep track of ticket using logsrole ID: role ID is stored of staff is stored to add to ticketmessage content: incase transcript is enabled, message content is stored in form of transcript
Welcome system: Following data is stored while you use welcome systemguild ID: guild ID is stored to keep track if welcome system is active (Only stored if active)channel ID: channel ID of welcome channel is saved to welcome the userrole ID: role ID is stored incase welcome is role assign based
Welcome DM system: Following data is stored while you use Welcome DM systemguild ID: guild ID is stored to keep track if Welcome DM is active (Only stored if active)message content: message content in the form of title , description , image , color , footer of welcome embed are stored to wish an user
Leave system: Following data is stored while you use leave systemguild ID: guild ID is stored to keep track if leave system is active (Only stored if active)channel ID: channel ID of leave channel is saved to log leaving of user
Captcha system: Following data is stored while you use captcha systemguild ID: guild ID is stored to keep track if captcha system is active (Only stored if active)role ID: role IDs are stored for roles to be assigned on captcha or server joinuser ID: when user presses captcha verify button his/her/their user ID is stored until the user is captcha verified (auto deleted after 10 minutes)message content: message content in the form of title , description , image , color , button color & button text of verify embed are stored to re-fetch captcha embed
Bump system: Following data is stored while you use bump systemguild ID: guild ID is stored to keep track if bump system is active (Only stored if active)channel ID: IDs of following channel are stored for their respective uses :log channel: for logs of bump systemother ads channel: for posting of other server adsserver AD channel: channel where server AD is present
message ID: message ID of AD is stored so to fetch the updated version of AD
Moderation system: No data is stored
Gif system: Following data is stored while you use gif systemguild ID: guild ID is stored to keep track if gif system is active (Only stored if active)
Reaction roles: Following data is stored while you use reaction role systemmessage ID: message ID of message is stored to keep track of reactionrole ID: role ID is stored to assign/remove on reaction add/removeemoji: emojis are stored to use them to add/remove roles
Role menu: Following data is stored while you use role menu systemrole IDs: role IDs are stored to assign/remove from users
Embed commands: No data is stored
Sticky messages: Following data is stored while you use sticky message systemguild ID: guild ID is stored to keep track if sticky message system is active (Only stored if active)channel ID: IDs of channel are stored for sticky messagesmessage content: message content to be posted in sticky message is stored
Join ping system: Following data is stored while you use join ping systemguild ID: guild ID is stored to keep track if join ping system is active (Only stored if active)channel ID: IDs of channel are stored for join pinging
Role ping system: Following data is stored while you use role ping systemguild ID: guild ID is stored to keep track if role ping system is active (Only stored if active)channel ID: IDs of channel are stored for role pingingrole ID: role IDs are stored for checking if a particular role is assigned
We value your trust in providing us your Personal Information, thus we are striving to use commercially acceptable means of protecting it. But remember that no method of transmission over the internet, or method of electronic storage is 100% secure and reliable, and we cannot guarantee its absolute security.
We do not collect any data from users unless provided us to by user or given permission to do so. If you do want the limited data we collect to be deleted, please contact us at our support server. Please note that participation in servers using Iko after your data is deleted will still be recorded depending on the server settings.
We may update this Privacy Policy from time to time. Changes in our Privacy Policy will be effective immediately. If you are a regular user of the bot, we recommend that you check this Privacy Policy on a regular basis. By using the bot, you consent to the collection, use and transfer of your information in accordance with this Privacy Policy. If you do not agree to this Privacy Policy, please do not use the bot.
If you have any questions or concerns about this Privacy Policy, please contact us at our support server.