Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The official documentation of RitaBot. Breaking the language barrier for thousands of people.
RitaBot is a fast, automatic Discord Translating Bot. Allowing communication across the language barrier from features like automatic-channel translation, to flag reaction translations and many more.
Rita was created because of a drive to communicate with others. Chatting platforms are awesome things and allow fast & simple communication across the entire world. However, something as simple as translating messages for others to understand can become so complicated. Across the internet, there are hundreds of translation bots but a flaw in many of them is increasing costs, changing features & overall difficulty to use.
This is where RitaBot came in. Many bots feature translations which are pricey due to hosting costs & translation costs. Rita, however, is an affordable bot & getting translations straight from the Google Translation API.
In this documentation, we'll teach you the functionalities and abilities of RitaBot
If you need help at any point join our Discord Server and someone will help you.
🗣️ Speak with others across multiple channels using the !tr group
command.
🪝 Use webhooks to send translations in a beautiful, user-like manner.
🇺🇸 🇫🇷 🇪🇸 Use flag reactions to translate any message. Simply add a reaction of the country of your choice and a translation will pop up with the languages of that country.
💪 The most powerful Translator Bot. Providing fast, automatic translation to thousands.
❤ Made with love by the Rita Dev Team
If you have any suggestions for future features feel free to join our Discord Server and add a request to #feature-request
In order to pay for translations, for both Google's API and our own Machine Learning API, RITA makes use of a subscriptions with given tiers.
The overview here explains further, and you can see how much it costs on Patreon
To install, you can follow the guide Quick setup steps
If you need help at any point join our Discord Server and someone will help you.
Command is currently disabled pending re-write.
Translates last message chain(s) in channel. A chain is a collection of messages by the same author, to keep things simple.
!tr last
!tr last [n] to [lang] from [lang]
to [lang]
- Defaults to server default language
to [lang, lang, ...]
- Translates to multiple languages
from [lang]
- Defaults to automatic detection
[n]
- Number of chains to translate, default is 1
[-n]
- Negative number means only one chain is translated
!tr last 2
!tr last to english
!tr last to english, german, french
!tr last -6 to english from german
Important Note
The bot’s default prefix is !tr (or !translate) - All commands must start with this prefix for the bot to process them. Bot must have proper permissions in all relevant channels for full functionality (read, write, react, mention, attachments, embed).
Users who wish to receive automatic translations in private must enable DMs via server privacy settings.
The bot’s default prefix is !tr
, or !translate
- All commands must start with this prefix for the bot to process them.
Important Note
RitaBot must have proper permissions in all relevant channels for full functionality (read, write, react, mention, attachments, embed, use external emojis, manage webhooks).
[prefix] + [main command] + [parameters]
For Example:
!translate help modules
!tr help modules
!tr help
If you need help at any point join our Discord Server and someone will help you.
How to make RITA running in your Discord Server
Check that your discord account is the owner of the server or an admin of the server you want RITA Bot in
Join RITA's discord server with this Discord account
Subscribe to RITA in Patreon (need email to be verified)
Invite RITA in your discord server : https://ritabot.gg/invite
With the same discord account, go into your Discord server and run !tr sub
in any of your discord server channels to activate your RITA plan.
Now you can Personalize your RITA's setting and translate a Discord chanel into another one with serveral commands. Most common use is by running !tr group
and following the instructions displayed
Information on Transaltion Commands.
All the information you need to know about subscriptions.
This project was originally released by Aziz under the MIT license. He chose to take the project private/commercial at version 0.4.2 Beta. Bobby Johnson forked the project and renamed it Louie after his dog. AlooAkbar forked Louie and added the necessary modifications for simple and free deployment of the bot using Heroku. RitaBot-Project Picked up the fork and as part of a team fixed over 200 errors and brought it in to the modern age, All would like to thank Aziz for his hard work and making these early versions OSS so that others may learn and build on his hard work to share with the community.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Here are some of the common questions that have been asked about the process.
Version History for 1.3.?
Version History for 1.2.?
If you need help at any point join our Discord Server and someone will help you.
Automatically translates any new messages in the current channel and forwards them to the target channel. Admins/mods can set forwarding to the same channel(not recommended) or other channels(recommended).
Please note that when you setup an auto command the target channel will not send back to main channel unless you tell it to
!tr channel from [lang] to [lang] for #[dest]
!tr auto to [lang] for #[same channel dest]
!tr channel from [lang] to [lang] for #[dest] filter @[role]
for [dest]
The target channel you want the translation of the from [lang]
to go to.
to [lang]
(optional)
The language to translate to, defaults to server default language if none provided.
from [lang]
The language to translate from.
filter [role] can be used to restriction translation to a specific role.
NOTE : Auto is for a single ( same channel ) translations, as photos, and Gifs, will not be duplicated or sent.
Using full language names
!tr channel from english to spanish for #target-channel
!tr auto to spanish for #current-channel
Using language short codes
!tr channel from en to es for #target-channel
!tr auto to es for #current-channel
Using Auto detection
!tr auto to ru for #current-channel
Send translations to same channel ( Not recommended for more than 3 languages )
!tr channel from english to spanish for #current-channel
!tr auto to spanish for #current-channel
Send translations to another channel in server ( Recommended )
!tr channel from english to spanish for #target-channel
!tr channel from english to spanish for #target-channel
!tr auto to spanish for #current-channel
Send translations to multiple channels in the server at once
!tr channel from english to spanish for #target-channel-es1, #target-channel-es2, #target-channel-es3, #target-channel-es4
!tr channel from english to spanish for #target-channel-es1, #target-channel-es2, #target-channel-es3, #target-channel-es4
To stop an automatic translation task, simply go the origin channel of the task and use the stop command:
!tr stop
!tr stop task [id!tr stop for [me]
!tr for [@user]
!tr stop for [#channel]
!tr stop for [all]
!tr stop for [server]
[id], ID number for the task you want to stop, run !tr tasks to get id.
for [me] - Stops translations via DM to yourself.
for [@user]
- Stops the task for user.
for [channel]
- Stops the task from the channel posted to the channel destination.
for [all] - Stops all translations in the channel its posted in.
for [server] - Stops all translations being done in your server.
Stop all automatic translations
!tr stop task [ID]
Stop a single task by running !tr task, and taking note of the ID of the item to remove.
!tr stop for [@UserID]
Stop a translation being sent to a user.
!tr stop for #target-channel
Stop all automatic translations for specific channel in server
!tr stop for all
Stop all automatic translations for the channel.
!tr stop for server
Stop all tasks in the server.
Help command for stop: !translate help stop
Help command for automatic translation: !translate help auto
.
Values wrapped in brackets [ ]
are solely for illustrative purposes to demonstrate the use of the command. Brackets are not in any command.
[lang]
values can be language names in English, native language names or ISO 639-1 codes. For example, german
de
and deutsch
will all work the same.
Messages by all bots are currently ignored to avoid loops, but we are working on different bot modes to enable bot translation.
Any message that begins with !tr
or !translate
will be determined to be a bot command and thus shall not be allowed to be translated.
Important Note
The bot’s default prefix is !tr (or !translate) - All commands must start with this prefix for the bot to process them. Bot must have proper permissions in all relevant channels for full functionality (read, write, react, mention, attachments, embed).
Groups channels using Automatic Channel Translation in a simple, easy-to-manage manner.
The group commands are interactive and require you to respond to any prompts correctly to function
!tr group
⬅ create new channel group
Respond with new group name, number of channels that should be in group, and for each channel prompt respond with channel language and ping which channel to assign
!tr group link [GROUPNAME]
⬅ link a new channel into group
Respond to prompts by pinging which channel to add and what language to assign to that channel
!tr group unlink [GROUPNAME]
⬅ delete a channel from group, opposite of group link
!tr group delete [GROUPNAME]
⬅ delete entirety of group
!tr group list
⬅ list all groups present in guild
[GROUPNAME] refers to the group name you give to the group (can check groups with !tr group list
)
There is a max of 10 channels/languages per group
Groups cannot have repeats of languages or channels. All added channels and langs must be unique and not already in the group
Languages should be in their ISO-639-1 format, list can be found here
Get to know us, we dont Bite.
I'm Artanis, the resident geek on the team. When I'm not procrastinating or playing video games (including Starcraft of course), I train and manage our Machine Learning API and models. I'm curious person at heart, and always love to learn about new things. I taught myself to code in Node as a 13 year old (at the beginning of Rita), and have since expanded to Python, Typescript, and some scripting languages such as AutoHotKey for some gaming side projects. I'll be the one to disappear into random projects only to leave them unfinished.
He looks sometimes like if he was not born in earth, but he's nice too
The funny one (when he forget he's an HR ).
Always thinking about improvement of bot from user-ends, he will always listen to your feedbacks (even if he hates writing)
The one who doesn't want to fill this section
He's shy but not that much.
Several years of Discord Administrator experience, currently a Student of History. No specific coding experience but I love to help people with Bots and Discord and have fun doing so.
I've got a good humor, so always up to have a laugh and make someone's day better. Love Mobile Gaming, which is where I came to Rita from as well.
Loving Rita for making cross language communications much easier, so have to give something to her and the team as well!
17 years experience as an sysadmin, currently working as a security consultant with focus on IAM and PAM. I Love a good challenge and making things work in ways they shouldnt.
Sarcastic 90% of the time and Love to help people make their day better!
Flag reactions work right after installing Rita, no commands are needed as long as Rita has been given the Recommend permission of Admin.
If you need help at any point join our and someone will help you.
!tr react [on/off]
!tr settings reactpersist [on/off]
!tr settings flagpersist [on/off]
react - [on/off] disabes the ablity to use flag reactions to translate.
reactpersist - [on/off] removes the translation after 60 seconds
flagpersist - [on/off] removes the flag.
Recommended to use reactpersist and flagpersist together.
The full Supported list can be found below
Important Note
The bot’s default prefix is !tr (or !translate) - All commands must start with this prefix for the bot to process them. Bot must have proper permissions in all relevant channels for full functionality (read, write, react, mention, attachments, embed).
Users who wish to receive automatic translations in private must enable DMs via server privacy settings.
If you need help at any point join our and someone will help you.
!tr stats
- Shows a summary of the Global & Server stats.
!tr stats sub
- View character usage for your subscription, and other information.
!tr stats global
- Shows a summary of Global stats, all the servers the bot is currently on.
!tr stats server
- Shows a summary of the Server stats.
!tr proc
- Shows the processor usage, CPU, Ram and Uptime of the bot.
!tr shards
- Shows the number of shards the bot is running on.
If you need help at any point join our and someone will help you.
Important Note
The bot’s default prefix is !tr (or !translate) - All commands must start with this prefix for the bot to process them. Bot must have proper permissions in all relevant channels for full functionality (read, write, react, mention, attachments, embed).
Users who wish to receive automatic translations in private must enable DMs via server privacy settings.
!tr help
- Shows RITA's help menu for all help commands.
!tr help modules
- Shows RITA's help menu for all modules.
!tr help commands
- Shows RITA's help examples for common commands. Such as Translation Commands, Information Commands, Style Commands, Misc Commands, and Debug Commands.
!tr help [command]
- Give usage info for each command.
Example: !tr help last
- will open the help menu for the command last.
!tr invite
- Creates an invite link for the bot so other can use it, i would not recommend using this command.
!tr list
- Lists all supported languages the bot can use.
!tr version
- Shows the current version of the bot.
!tr history
- Shows list of previous bot versions.
!tr history [version]
- show all the revisions made to the designated version.
** [version]
** - Version number.
!tr tasks
- Lists all current translation tasks for the channel the command is used in. This command is very useful to check what tasks you have currently set in a channel as well as easily identify if you've created an invalid translation tasks.
!tr donate oc
- Donation link for open Collective.
!tr donate github
- Donation link for GitHub.
!tr prefix [prefix]
- Sets custom bot prefix
** [prefix] - custom prefix
**
!tr id
- Shows various ID info
If you need help at any point join our and someone will help you.
Important Note
The bot’s default prefix is !tr (or !translate) - All commands must start with this prefix for the bot to process them. Bot must have proper permissions in all relevant channels for full functionality (read, write, react, mention, attachments, embed).
Users who wish to receive automatic translations in private must enable DMs via server privacy settings.
!tr this: [msg]
- Translates to default server language
!tr this to [lang]: [msg]
- detects language and translates to your to langugae
to [lang]
- Defaults to server default language
to [lang, lang, ...]
- Translates to multiple languages
from [lang]
- Defaults to automatic detection
!tr this: bonjour
!tr this to spanish: hello world
!tr this to arabic, hebrew: I love you
!tr this to de from en: how are you?
Information about subscribing to RitaBot services. Please make sure to read the entire page before proceeding with buying a subscription to clear up any possible future confusion.
If you need help at any point join our and someone will help you.
In order to subscribe to RitaBot, you must be on our . Subscriptions are role-based, meaning that Rita updates subscriptions based on which roles you have been given by the payment platform (which tier you have bought). If you leave the server, Rita will cancel your subscription at the end of a one-month period from the last subscription date, even if your subscription is still active.
For any queries you may have in regards to subscriptions, please proceed to #open-a-ticket in our .
If you're lost about the link between subscription and RITA's intallation, you can have a look at the guide
There may be times RitaBot ceases to function, in which the procedure for us will be to verify the problem and fix it as soon as possible. We are not responsible for any issues this may cause.
Furthermore, there may be times of maintenance in order to improve and exceed Rita's capabilities. In line with our , We aim for a service uptime of >80% (24 Days in a rolling 30-day period) of core functionality.
Currently, only the server owner or admin can buy a subscription for a server. Furthermore, only one server can be activated with your subscription at a time. This will be liable to change in the future as time goes on.
To activate your subscription after you have paired your Discord Account to your payment, you must run the !tr sub
command in the #activate-rita-here channel in our , after you do so follow the prompts to activate your subscription for the specific server.
In order to subscribe and maintain said subscription, you MUST be on our . If you cannot or are not, your subscription will be canceled at the end of a 1-month period from the last verification date (the last 1-month period from the subscription start where the subscription was confirmed).
In order to provide a virtually "unlimited" pricing model, we've incorporated soft limits into Rita. Essentially, each tier has X amount of chars per month that will be translated with Google. Meanwhile, all other translations will use our own Neural Machine Translation server.
While we are working hard to make our own translations as seemingless as ever, Google translations will be similar/better than ML translations simply due to Google's resources
We are working to provide clarifying examples of quality for language pairs to be as clear as possible
To clarify; all tiers are still unlimited character wise.
The only difference shall be if you've used more than the soft limit for your tier in a month, then all other translations will use our ML until month is reset.
The only difference between our plans at the moment, and for the foreseeable future is the task limit that you are restricted to. If this changes however we will let you know, You won't lose access to anything you don't already have.
A task is a singular channel setup for automatic channel translation. Tasks are simply the setup, not the usage. For example; 1 channel translating from English to French counts as a task. As you add more languages to an interconnected language setup, the task utilization increases exponentially.
You can calculate how many tasks you use for each channel by using the amount of languages (including source) you want to have for that channel in the equation x * (x-1)
Reaction translation, utilisation of tasks, or anything else do not count towards task count
Only the group
, auto
, and channel
commands contribute to task count
For support, please visit us at our If you wish to email us about payments, please use
This is a Guide on how to subscribe on Patreon
If you need help at any point join our and someone will help you.
On Patreon, you can let your fans become active participants in the work they love by offering them a monthly membership. You give them access to exclusive content, community, and insight into your creative process. In exchange, you get the freedom to do your best work, and the stability you need to build an independent creative career.
Navigate to
Select the plan that you wish to use by pressing Join
If you have an account with Patreon already, please select Log-In from the bottom of the page.
If you don't have an account, You can Sign up with Google or Facebook or you can fill in the form and select Sign Up when you are done
For those creating new accounts. Confirm your Country of Residence
NOTE: DON'T FORGET TO VERIFY YOUR EMAIL
For those paying with a card, Select that option and fill out your details to process your payment.
Selecting Pay with Card will then process through and you will receive a confirmation by email.
For those paying with PayPal, select this option, and then Pay with PayPal. You can then sign into PayPal.
Once you have signed in, confirm your payment method and then Agree and Continue
As soon as you select continue as per the previous step, the payment will process and you will get a confirmation on screen that you were sucessful.
You can now link your Discord account to your patron. Scroll down until you see Connect to Discord. You can then sign in to discord and receive your roles.
Now you have a subscription with RITA, you can link your discord to get Roles. To do this either select Connect to Discord on the confirmation page, or go to your profile:
Profile > Edit Profile > Connected Apps
Select Connect on the Discord option
Sign in as you normally would. Then select Authorise to confirm
To cancel a subscription, you will need to do this from within Pateon.
Sign into Patron
Navigate to your profile Menu
Select Manage Memberships
Locate RITA under Active Memberships
Select Edit for the RITA membership
Select Edit for Cancel Membership
Select the Cancel your Membership option
Select the black Cancel your Membership button to confirm
Your membership will now be cancelled subject to Pro-Rata. This means your membership will end at the end of the month you paid for. If you have any issues or concerns, please open a ticket in the RITA Management Server.
If you need help at any point join our and someone will help you.
Important Note
The bot’s default prefix is !tr (or !translate) - All commands must start with this prefix for the bot to process them. Bot must have proper permissions in all relevant channels for full functionality (read, write, react, mention, attachments, embed).
Users who wish to receive automatic translations in private must enable DMs via server privacy settings.
These commands are available only to admins.
This command will display a printout of your current server settings.
!tr settings
This command will allow you to set a custom prefix for RITA in your server.
!tr prefix [prefix]
!translate prefix [prefix]
This command will turn off messages from the Development team.
!tr announce [on/off]
This command will allow you to use either embed or webhook translation Styles.
!tr embed [on/off]
!tr help embed
This is embed style: This is webhook style:
This command will add a source Language marker to the translated text.
!tr settings langdetect [on/off]
This command will allow RITA to translate messages from most bots
!tr bot2bot [on/off]
!tr help bot2bot
This command will allow you to disable RITAs ability to use the everyone, here and user tags when using Webhook translation style.
!tr settings tags [Parameter]
none
- RITA won't ignore any mentions
everyone
- RITA will ignore everyone and here tags
all
- RITA will ignore all mentions
This command will turn off the ability to translate a message with Country flags.
!tr react [on/off]
These commands are to enable/disable various auto delete functions.
!tr settings menupersist [on/off]
!tr settings reactpersist [on/off]
!tr settings flagpersist [on/off]
This command will allow you to turn on debugging for RITA related errors in your server.
!tr debug [on/off]
!tr help debug
This command will reset all Settings to their default setting.
!tr settings reset
Important Note
The bot’s default prefix is !tr (or !translate) - All commands must start with this prefix for the bot to process them. Bot must have proper permissions in all relevant channels for full functionality (read, write, react, mention, attachments, embed).
Users who wish to receive automatic translations in private must enable DMs via server privacy settings.
All Plans, Prices, Limitations and Restrictions are correct at time of publication.
Subscriptions are available on . The guide is available
If you need help at any point join our and someone will help you.
Please review our S.A.L.T.S Policy for more information on Availability, Limitations and Restrictions.
If you need help at any point join our and someone will help you.
All development and support of the self-hosted version has now been discontinued
RITA is the culmination of many things, it started with a mobile game, a community of gamers, a discord server of different languages and a desire to all be understood. She is a Real-Time Translator Bot for use on Discord. She is maintained by a small group of users (that have a real life and a job), each with different backgrounds and some learning as we go. You want to learn more about Rita and what she does ? Just take a loot at the .
The mobile game itself would get old, fast. The community around it, however, is what kept us going. The one downside was we did not all speak the same language. The game we played translated our conversations for us, but Discord did not, so the server admins used a translation bot called C-3P0. This introduction is the start of the story.
There are loads of different translation bots out there, some are amazing, some are expensive, some are free but have limits, and others are just rubbish. C-3P0 checked all these boxes.
Originally called discord-translator and made by Aziz, then forked By NotMyself and renamed Louie, forked again By AlooAkbar and renamed C-3P0, its code was neglected, not maintained, left outdated and iterations made private for commercial gains.
I and a group of fellow C-3P0 users decided that collectively we could do better, plagued with crashes, API changes, relentless bugs and issues, the drive to make something better was born.
Rita’s history and various iterations each added something extra, it just needed to be brought together and molded, molded into something amazing, molded into Rita. The Real-Time Interchangeable Translating Assistant.
Then we provided for a few time a self-hosted version before making the actual version of Unified Rita as it was impossible for everyone to request the google API, to maintain all codes, to help everyone with his particular settings. And moreover, self hosting would not answer to an easy installation with an invite link. Also code was not already used in a good way (meaning, taking some code in order to add it in some exepensive ones).
There you have it, the story, dramatized and electrified for effect, but all true, of how RITA was born.
Information about the 1.2.2 Update.
If you need help at any point join our and someone will help you.
Rita now uses Discord.js V12.
Same channel translation is now working. You no longer need to have multiple channels set up, you can do it all in one channel.
Example !tr channel from english to spanish for #SameChannelMention
Will translate any English messages to Spanish in your current channel
AUTO Translate is now working, you can define the "from" language as "AUTO" and it will detect the language for you.
Example !tr auto to lang for #channel
So running !tr auto to en for #channel
will auto translate anything not in English to English for that channel.
DM Translations have been fixed and enabled, thanks to Artanis and Brozer.
You can enable this by running the following command !tr channel to de from en for @user
That will translate English messages to German for the user. Which they will receive in a DM.
Duplicate language translation bug is now fixed, meaning you can not translate English to English or French to French etc.
Various fixes to Nickname Bugs, this should now be working.
Desktop Client Gif keyboard caused error due to exclusive embed style.
google-translate-api
has been changed to RCP to reduce and mitigate the load limiter.
We have found a way to speed up the translation process, so it should be a little snappier in future.
New commands added (debug
, donate
, prefix
, help commands
, create
)
debug
Is for debug options. Examples below:
!tr debug on
- turns on debugging, creates debugging channel and webhook
!tr debug off
- turns off debugging
!tr stats debug
- prints webhook "ID" and "Token" in channel
donate
- If you would like to donate to RITA you can find the info with this command. Since RITA bot is 100% free donations are greatly appreciated to help with server costs. Examples below:
!tr donate
- Will return donation options
!tr donate github
- You can Donate at Github Sponsors
!tr donate oc
- You can Donate at Open Collective
prefix
- You can now change the prefix of your bot, you can make it whatever you want. Examples below:
!tr prefix
- Will list your current prefix. Default prefix is!tr
!tr prefix $tr
- your prefix would now be$tr
instead of!tr
!tr prefix reset
- resets your prefix back to!tr
So if you changed the prefix to$tr
you would run$tr prefix reset
help commands
- Shows a list of all available commands. Example below:
!tr help
create
- Allows you to use RITA to create a new channel. Example below:
!tr create bob
- will create a new channel named bob
Command Changed (stats global
, stats server
)
stats global
- Stat tracking of messages sent in global servers.stats server
- Stat tracking of messages sent in local server.
Command Removed (settings dbfix
, cpu
)
settings dbfix
- This is no longer needed as DB is repaired (If needed) on each startup.cpu
- It was broken and I have no idea how to fix it.
As the new variables above are stored in the DB, we have made a few changes to how these are handled and they are auto-created upon load. Meaning you no longer need to worry about them again. (If you get any error's please let us know)
Various Security vulnerabilities fixed.
Fixed various issues.
Major code changes
Dev Dependencies core to this bot, the google-translate-api
& google-translate-token
& gulp-watch
have been updated
Information about the 1.2.3 Update.
If you need help at any point join our and someone will help you.
Environment changes - MESSAGE_DEBUG
- For servers that want to show debug message content to find out what pesky message is causing that error, set this to 1. By Default it is 0. Rita global bot is also 0 and will remain that way.
With the changes to the google-translate-api
it dug up a load of new bugs, Lazarus & EDW have been hard at work fixing them, (DM Lazarus to say thank you, he will love it.)
@everyone
& @here
will now also be conveyed across channels correctly.
Emojis, roles and user pings will now function as intended. With a new system used to manage and correct them
!tr stats global
/ !tr stats server
now show message based stats, take a look.
It working so were not going to touch it. (Well Zycore wont)
Zycore broke something (alot of times) Zycore fixed it again.
All debug messages have been commented out in all files, This make the console log look so much cleaner.
Information about the 1.2.4 Update.
If you need help at any point join our and someone will help you.
Dev only Command handler has been added in to enable fast changes to command restrictions.
Lots of little things, nothing of consequence.
!tr history
shows Development History of the bot.
!tr stats server [ServerID]
shows stats for the targets server.
!tr blacklist [ServerID]
Blacklists a server (Developers Only).
!tr unblacklist [ServerID]
un-Blacklists a server (Developers Only).
!tr warn [ServerID]
Warns a server (Developers Only).
!tr unwarn [ServerID]
un-Warns a server (Developers Only).
!tr eject [ServerID]
Removes RITA from the target server (Developers Only).
!tr check [ServerID]
Checks Warn & Blacklist status of the given server.
!tr checkperms [bot/user]
checks permissions of the bot and the user for RITA compatibility.
A new column has been added to manage blacklisting and Warning, backwards compatible to all previous versions.
Once again Zycore broke something (a lot of times) Zycore fixed it again.
Help muenus update with new commands.
Help menus has been reworked, Still a work in progress but they look much better now.
Information about the 1.2.0 Update.
If you need help at any point join our and someone will help you.
No Code changes, just URL updates for New name of Bot
Published to NPM
Non code changes will be appended with Version-** from now on.
Various Spelling mistakes in ReadMe have been corrected.
Dev Dependencies core to this bot, the google-translate-api
& google-translate-token
have been updated
Setup on a Raspberry Pi instruction Section added.
gulp-watch updated dependencies. (Moved to Local Repo as it was out-of-date and full of Security Issues.)
Patch for Chinese language support.
Various Security vulnerabilities fixed.
Various commands re-activated.
Information about the 1.2.5 Update.
If you need help at any point join our and someone will help you.
db.js has had a overhaul
Database has been migrated to a larger DB, We wont be needing to do that again for a good 5 years.
Color now working in Embed on
and takes user role color.
Stop command for @user has now been fixed
Welcome message added for all new servers. System Channel is default, if not available it will pick first channel that has Write permissions.
Announcement command added, This is Restreicted to DEV ONLY.
Opt in and out commands added for announcements.
!tr settings persist [on/off]
command has been added, this will prevent bot responses from being deleted.
Validation Checks added at startup to avoid Blacklist and Stats SQL Errors
New Debug Settings for console.
MESSAGE_DEBUG
0 - Error's Only
1 - Console for all Messages
2 - Console for Translate Messages only
3 - Content of all Messages
4 - Content of Translate Messages only
5 - Commands Only
Information about the 1.2.2 Update.
If you need help at any point join our and someone will help you.
New commands added (embed, bot2bot, settings updatedb)
embed command allows you to change the type of message that is sent to the translation channel, in embed format or standard text. Standard text shows the users avatar and name instead of the bot.
bot2bot allows for messages sent from other bots, in non embedded format to be translated as well. (Due to limitation this has been implimented but is disabled for now)
As the new variables above are stored in the DB, they need new Columns to be added, as such updatedb will complete these actions.
Major code changes, new code implementations will change the DB and produce errors on first build, but this is a safe version to update to. Follow the below instructions.
Step 1: Make a pull request and update from Master branch.
Once you update the bot and it initializes you WILL get a db error, this is normal. (we are working on suppressing these)
Step 2: !t settings updatedb
This will throw another error but it will build the missing columns.
The default value for embed is on and botbot is off.
Running this multiple times will cause error to be posted to webhook chan, this is a "Value exists" error. Preventing you from destroying the DB
Step 3: Completed, and now working.
Once you have completed Step 2, the bot will have come online, but it wont have fully Initialised.
To prevent a never ending loop of errors, the VERY FIRST message or command sent on the server will Initialise the DB fully. Meaning you will have to send that message again.
Please Note Due to the first message after each restart will share the same behaviour as above.
Added in command triggers and command deletion to clean up command channels.
Custom Emoji's are now supported and will be sent with the translated message correctly, with the exception of a few languages.
DM Translation have been disabled as it has been identified they never worked as intended. they will be re-introduced in a later update.
Various Security vulnerabilities fixed.
Dev Dependencies core to this bot, the google-translate-api
& google-translate-token
& gulp-watch
have been updated
eslint
has been replaced with babel-eslint
!t settings updatebot
Has been DISABLED - This is not needed as of yet and with the similarities to the !t settings updatedb
command it may cause issues.
Deploy with Heroku Setup and integration.
Version History for 1.3.?
If you need help at any point join our and someone will help you.
Dependancy Updates
Node and NPM Updated
node is now V17.1.0
node version can be changed in package.json to any version above 16.2.0
npm is now V8.1.3
npm version can be any version above 7.20.3
DJS is version
CS same language now works
Join and leave logs can now be seperated from error logs with env variables DISCORD_ACTIVITY_WEBHOOK_ID
& DISCORD_ACTIVITY_WEBHOOK_TOKEN
Task ID added to tasks Printout
Ignore same chan translation of GIF and images
Admin
, Owner
, Dev
and Channel Manager
variables are now stored in message object
Shard command has been updated to show each shard and its stat
Add top,gg stat tracker to RITA
Profanity filter has been added - BETA MODE
Reduced DB Calls by over 50% by using db.server_obj more
db.server_obj now stores
db.server_obj[GuildId].servers[Values] - All values in the DB Servers Table at time of load are saved in the object db.server_obj[GuildId].stats[Values] - All values in the DB Stats Table at time of load are saved in the object
Local hosted users persist and react command fixed
Fixed invalid channel message
Various Permission Errors
Admin
, Owner
, Dev
and Channel Manager
variables are now stored in message object
Fixed translate for me
command
Fix the UID of the emoji reaction error
Fix Kick Command Response
Fix top.gg code in bot.js, so that if there is no token it ignores the code
Stop emoji's from translating for auto same channel translations
Strip mentions from same channel translations
!tr auto to lang for me causes error
!tr updatelink
has been added
!tr reactpersist
has been added - Reaction will auto delete after 60 seconds
!tr flagpersist
has been added - Flag emoji will be removed after 15 seconds
Task command updated, !tr tasks [#chan/me]
me
will show any tasks for the user in any channel
#chan
will target a single channel
!tr checkperms
has ben replaced with !tr check
!tr stop task [id]
has been added - Remove by ID is now possiable
!tr settings tags [all/everyone/none]
has been added, this falls in line with discord.js (This setting only applies to embed off
mode)
none
- No tags are disabled, meaning@user
,@everyone
and@here
will work
everyone
- Attention tags are, meaning only@user
will work
all
- All tags are disabled, meaning@user
,@everyone
and@here
will NOT work
!tr settings reset
Will reset all settings to the default value.
!tr settings langDetect [on/off]
Turns language detection footer on for translated messages
!tr settings updatedb [serverID]
will update the database and object if the data is incorrect
!tr stop for server
Will stop all translation task serverwide
!tr stop for server [serverID]
Will stop all translation task of target Server serverwide
!tr settings profanity [off/replace/delete]
has been added
off
- profanity words are allowed. No actions taken
replace
- Profanity words are replaced with random special characters
delete
- message is deleted and not translated
!tr tasks [user/server/channel] {ID}
has been added (Dev Only)
user
- Will get all tasks for a targeted user from the DB
server
- Will get all tasks for a targeted server from the DB
channel
- Will get all tasks for a targeted channel from the DB
!tr cache
- Will show the amount of data currently cached
data.message.server is built on every message event, Reducing the calls needed in send.js to db
db changes, the following columns have been added
reactpersist
- manages the react persist variable
flagpersist
- manages the flag persist variable
servername
- stores a local copy of the server name
servertags
- manages the server tags variable
badwords
- profanity filter
menupersist
- manages the menu persist variable
whitelisted
- NOT IN USE, Yet!
langdetect
- manages language detection footer variable
profanity
- manages profanity filter variable
ownerid
- Store the owner ID
char
- Stores the Character ammount of Total Messages
messagecount
- Counts number of messages sent
subscription
- Stores the subscription boolean variable
subscriptionlevel
- Stores the subscription level variable
subscriptiondate
- Stores the subscription date variable
subscriptionlength
- Stores the subscription length variable
subscriptionuser
- Stores the subscription user
tasklimit
- Stores the tasks limit fo the server
Help menu updated
Owner variable is now more reliable on messages
Language marker has been added to embed off and and on messages, this is controlled with !tr settings langdetect [on/off]
Error messages show Task ID
servertags and langdetect status added to the settings and check commands
Append Dev name to "Developer identity confirmed"
Dev Dependencies core to this bot, gulp-watch
have been updated
Certain statement has been converted to try statements to allow for better error handling
Information about the 1.2.6 Update.
If you need help at any point join our and someone will help you.
Sharding is now automatic, this should auto scale to the needed amount.
A Major memory leak causing rita to restart every few hours has now been fixed.
!tr announce on/off
has been fixed.
!tr settings
has been unrestricted.
!tr blacklist {ServerID}
has been fixed.
!tr channel from {lang} to {lang}
no longer defaults to a DM task.
!tr react on/off
now turns on and off flag reactions.
Added in 3 new columns ready for auto-warn and eject management
Servers will be allowed 10 Permission Errors Before a Warning
Server will be given a Maximum of 3 Warning before they are Ejected
If your server should be Ejected a second time it will be blacklisted
Sooooooo Many spelling mistakes corrected that it would be too many to list here.
Help Menu updated with new commands.
Well, my skills are SQL ANSI, PostgreSQL, Oracle Database, SQLite, Flyway (for CI/CD ), bash, .... (REDIS comming soon). And i'm confortable on Windows and Linux OS. I just have to improve my english
Task Limit
100
200
350
Soft Limit (characters)
~200k Google
~450k Google
~700k Google
Character Limit (backed by ML)
Unlimited
Unlimited
Unlimited
Version Changes for 1.3.5-?
If you need help at any point join our Discord Server and someone will help you.
Version Changes for 1.3.?-?
If you need help at any point join our Discord Server and someone will help you.
Version Changes for 1.3.?-?
Version Changes for 1.3.?-?
If you need help at any point join our Discord Server and someone will help you.
Version Changes for 1.3.?-?
Version Changes for 1.3.?-?
Version Changes for 1.3.?-?
If you need help at any point join our Discord Server and someone will help you.
Version Changes for 1.3.?-?
Version Changes for 1.3.?-?
If you need help at any point join our Discord Server and someone will help you.
Version Changes for 1.3.?-?
If you need help at any point join our Discord Server and someone will help you.
Version Changes for 1.3.?-?
If you need help at any point join our Discord Server and someone will help you.
Version Changes for 1.3.?-?
Version Changes for 1.3.?-?
If you need help at any point join our Discord Server and someone will help you.
Version Changes for 1.3.?-?
Version Changes for 1.3.?-?
If you need help at any point join our Discord Server and someone will help you.
:flag_af:
Afghanistan
Pashto
ps
:flag_ax:
Aland Islands
Swedish
sv
:flag_al:
Albania
Albanian
sq
:flag_dz:
Algeria
Arabic, French
ar, fr
:flag_as:
American Samoa
English, Samoan
en, sm
:flag_ad:
Andorra
Valencian
ca
:flag_ao:
Angola
Portuguese
pt
:flag_ai:
Anguilla
English
en
:flag_aq:
Antarctica
null
null
:flag_ag:
Antigua And Barbuda
English
en
:flag_ar:
Argentina
Spanish
es
:flag_am:
Armenia
Armenian
hy
:flag_aw:
Aruba
Dutch
nl
:flag_au:
Australia
English
en
:flag_at:
Austria
German
de
:flag_az:
Azerbaijan
Azerbaijani
az
:flag_bs:
Bahamas
English
en
:flag_bh:
Bahrain
Arabic
ar
:flag_bd:
Bangladesh
Bengali
bn
:flag_bb:
Barbados
English
en
:flag_by:
Belarus
Belarusian, Russian
be, ru
:flag_be:
Belgium
Dutch, French, German
nl, fr, de
:flag_bz:
Belize
English, Spanish
en, es
:flag_bj:
Benin
French
fr
:fag_bm:
Bermuda
English
en
:flag_bt:
Bhutan
Dzongkha
dz
:flag_bo:
Bolivia
Spanish
es
:flag_ba:
Bosnia And Herzegovina
Bosnian, Croatian, Serbian
bs, hr, sr
:flag_bw:
Botswana
English
en
:flag_bv:
Bouvet Island
Norwegian
no
:flag_br:
Brazil
Portuguese
pt
:flag_io:
British Indian Ocean Territory
English
en
:flag_bn:
Brunei Darussalam
Malay, English
ms, en
:flag_bg:
Bulgaria
Bulgarian
bg
:flag_bf:
Burkina Faso
French
fr
:flag_bi:
Burundi
French, Rundi
fr, rn
:flag_kh:
Cambodia
Central Khmer
km
:flag_cm:
Cameroon
French, English
fr, en
:flag_ca:
Canada
English, French
en, fr
:flag_cv:
Cape Verde
Portuguese
pt
:flag_ky:
Cayman Islands
English
en
:flag_cf:
Central African Republic
French, Sango
fr, sg
:flag_td:
Chad
Arabic, French
ar, fr
:flag_cl:
Chile
Spanish
es
:flag_cn:
China
Chinese
zh-cn
:flag_cx:
Christmas Island
Chinese, English, Malay
zh-cn, en, ms
:flag_cc:
Cocos (Keeling) Islands
Malay, English
ms, en
:flag_co:
Colombia
Spanish
es
:flag_km:
Comoros
Arabic, French
ar, fr
:flag_cg:
Republic of the Congo
French, Lingala
fr, ln
:flag_cd:
Democratic Republic of the Congo
French, Swahili
fr, sw
:flag_ck:
Cook Islands
English
en
:flag_cr:
Costa Rica
Spanish
es
:flag_ci:
Cote D’Ivoire
French
fr
:flag_hr:
Croatia
Croatian
hr
:flag_cu:
Cuba
Spanish
es
:flag_cy:
Cyprus
Greek, Turkish
el, tr
:flag_cz:
Czech Republic
Czech
cs
:flag_dk:
Denmark
Danish
da
:flag_dj:
Djibouti
Arabic, French
ar, fr
:flag_dm:
Dominica
English
en
:flag_do:
Dominican Republic
Spanish
es
:flag_ec:
Ecuador
Spanish
es
:flag_eg:
Egypt
Arabic
ar
:flag_sv:
El Salvador
Spanish
es
:flag_gq;
Equatorial Guinea
Spanish, French, Portuguese
es, fr, pt
:flag_er:
Eritrea
Arabic, English, Tigrinya
ar, en, ti
:flag_ee:
Estonia
Estonian
et
:flag_et:
Ethiopia
Oriya, Amharic, Somali, Tigrinya
or, am, so, ti
:flag_fk:
Falkland Islands (Malvinas)
English
en
:flag_fo:
Faroe Islands
Danish, Faroese
da, fo
:flag_fj:
Fiji
Fijian, English
fj, en
:flag_fi:
Finland
Finnish, Swedish
fi, sv
:flag_fr:
France
French
fr
:flag_gf:
French Guiana
French
fr
:flag_pf:
French Polynesia
French
fr
:flag_tf:
French Southern Territories
French
fr
:flag_ga:
Gabon
French
fr
:flag_gm:
Gambia
English
en
:flag_ge:
Georgia
Georgian
ka
:flag_de:
Germany
German
de
:flag_gh:
Ghana
English
en
:flag_gi:
Gibraltar
English, Spanish
en, es
:flag_gr:
Greece
Greek
el
:flag_gl:
Greenland
Kalaallisut, Danish
kl, da
:flag_gd:
Grenada
English
en
:flag_gp:
Guadeloupe
French
fr
:flag_gu:
Guam
English, Chamorro
en, ch
:flag_gt:
Guatemala
Spanish
es
:flag_gg:
Guernsey
English
en
:flag_gn:
Guinea
French
fr
:flag_gw:
Guinea-Bissau
Portuguese
pt
:flag_gy:
Guyana
English
en
:flag_ht:
Haiti
French
fr
:flag_hm:
Heard Island & Mcdonald Islands
null
null
:flag_va:
Holy See (Vatican City State)
Latin, Italian
la, it
:flag_hn:
Honduras
Spanish
es
:flag_hk:
Hong Kong
Chinese, English
zh-tw, en
:flag_hu:
Hungary
Hungarian
hu
:flag_is:
Iceland
Icelandic
is
:flag_in:
India
Hindi
hi
:flag_id:
Indonesia
Indonesian
id
:flag_ir:
Iran
Persian
fa
:flag_iq:
Iraq
Arabic, Kurdish
ar, ku
:flag_ie:
Ireland
English, Irish
en, ga
:flag_im:
Isle Of Man
English, Manx
en, gv
:flag_il:
Israel
Hebrew, Arabic
he, ar
:flag_it:
Italy
Italian
it
:flag_jm:
Jamaica
English
en
:flag_jp:
Japan
Japanese
ja
:flag_je:
Jersey
English
en
:flag_jo:
Jordan
Arabic
ar
:flag_kz:
Kazakhstan
Kazakh, Russian
kk, ru
:flag_ke:
Kenya
English, Swahili
en, sw
:flag_ki:
Kiribati
English
en
:flag_kr:
South Korea
Korean
ko
:flag_kw:
Kuwait
Arabic
ar
:flag_kg:
Kyrgyzstan
Kirghiz, Russian
ky, ru
:flag_la:
Lao People’s Democratic Republic
Lao
lo
:flag_lv:
Latvia
Latvian
lv
:flag_lb:
Lebanon
Arabic
ar
:flag_ls:
Lesotho
Southern Sotho, English
st, en
:flag_lr:
Liberia
English
en
:flag_ly:
Libya
Arabic
ar
:flag_li:
Liechtenstein
German
de
:flag_lt:
Lithuania
Lithuanian
lt
:flag_lu:
Luxembourg
Letzeburgesch, French, German
lb, fr, de
:flag_mo:
Macao
Chinese, Portuguese
zh-tw, pt
:flag_mk:
Macedonia
Macedonian
mk
:flag_mg:
Madagascar
Malagasy, French
mg, fr
:flag_mw:
Malawi
English
en
:flag_my:
Malaysia
Malay
ms
:flag_mv:
Maldives
Maldivian
dv
:flag_ml:
Mali
French
fr
:flag_mt:
Malta
Maltese
mt
:flag_mh:
Marshall Islands
Marshallese, English
mh, en
:flag_mq:
Martinique
French
fr
:flag_mr:
Mauritania
Arabic
ar
:flag_mu:
Mauritius
English, French
en, fr
:flag_yt:
Mayotte
French
fr
:flag_mx:
Mexico
Spanish
es
:flag_fm:
Micronesia
English
en
:flag_md:
Moldova
Romanian
ro
:flag_mc:
Monaco
French
fr
:flag_mn:
Mongolia
Mongolian
mn
:flag_me:
Montenegro
Montenegrin
cnr
:flag_ms:
Montserrat
English
en
:flag_ma:
Morocco
Arabic
ar
:flag_mz:
Mozambique
Portuguese
pt
:flag_mm:
Myanmar
Burmese
my
:flag_na:
Namibia
English
en
:flag_nr:
Nauru
Nauru
na
:flag_np:
Nepal
Nepali
ne
:flag_nl:
Netherlands
Dutch
nl
:flag_bq:
Netherlands Antilles
Dutch
nl
:flag_nc:
New Caledonia
French
fr
:flag_nz:
New Zealand
English
en
:flag_ni:
Nicaragua
Spanish
es
:flag_ne:
Niger
French
fr
:flag_ng:
Nigeria
English
en
:flag_nu:
Niue
English, Niuean
en, niu
:flag_nf:
Norfolk Island
English
en
:flag_mp:
Northern Mariana Islands
English, Chamorro, Carolinian
en, ch, cal
:flag_no:
Norway
Norwegian
no
:flag_om:
Oman
Arabic
ar
:flag_pk:
Pakistan
Urdu
ur
:flag_pw:
Palau
English, Palauan
en, pau
:flag_ps:
Palestinian Territory
Arabic
ar
:flag_pa:
Panama
Spanish
es
:flag_pg:
Papua New Guinea
English, Hiri Motu, Tok Pisin
en, ho, tpi
:flag_py:
Paraguay
Spanish, Paraguayan Guaraní
es, gug
:flag_pe:
Peru
Spanish
es
:flag_ph:
Philippines
Tagalog
tl
:flag_pn:
Pitcairn
English
en
:flag_pl:
Poland
Polish
pl
:flag_pt:
Portugal
Portuguese
pt
:flag_pr:
Puerto Rico
Spanish
es
:flag_qa:
Qatar
Arabic
ar
:flag_re:
Reunion
French
fr
:flag_ro:
Romania
Romanian
ro
:flag_ru:
Russian Federation
Russian
ru
:flag_rw:
Rwanda
Kinyarwanda, English, French, Swahili
rw, en, fr, sw
:flag_bl:
Saint Barthelemy
French
fr
:flag_sh:
Saint Helena
English
en
:flag_kn:
Saint Kitts And Nevis
English
en
:flag_lc:
Saint Lucia
English
en
:flag_sx:
Saint Martin
Dutch, French, German
nl, fr
:flag_pm:
Saint Pierre And Miquelon
French
fr
:flag_vc:
Saint Vincent And Grenadines
English
en
:flag_ws:
Samoa
Samoan, English
sm, en
:flag_sm:
San Marino
Italian
it
:flag_st:
Sao Tome and Principe
Portuguese
pt
:flag_sa:
Saudi Arabia
Arabic
ar
:flag_sn:
Senegal
French
fr
:flag_rs:
Serbia
Serbian
sr
:flag_sc:
Seychelles
English, French
en, fr
:flag_sl:
Sierra Leone
English
en
:flag_sg:
Singapore
English, Tamil, Chinese, Malay
en, ta, zh-tw, ms
:flag_sk:
Slovakia
Slovak
sk
:flag_si:
Slovenia
Slovenian
sl
:flag_sb:
Solomon Islands
English
en
:flag_so:
Somalia
Somali, Arabic
so, ar
:flag_za:
South Africa
English, Afrikaans, Southern Sotho, Xhosa, Zulu
en, af, st, xh, zu
:flag_gs:
South Georgia And Sandwich Islands
English
en
:flag_es:
Spain
Spanish
es
:flag_lk:
Sri Lanka
Sinhalese, Tamil
si, ta
:flag_sd:
Sudan
Arabic
ar
:flag_sr:
Suriname
Dutch
nl
:flag_sj:
Svalbard And Jan Mayen
Norwegian
no
:flag_sz:
Swaziland
Swati, English
ss, en
:flag_se:
Sweden
Swedish
sv
:flag_ch:
Switzerland
German, French, Italian
de, fr, it
:flag_sy:
Syrian Arab Republic
Arabic
ar
:flag_tw:
Taiwan
Chinese
zh-tw
:flag_tj:
Tajikistan
Tajik
tg
:flag_tz:
Tanzania
Swahili
sw
:flag_th:
Thailand
Thai
th
:flag_tl:
Timor-Leste
Tetum, Portuguese
tet, pt
:flag_tg:
Togo
French
fr
:flag_tk:
Tokelau
Tokelau, English
tkl, en
:flag_to:
Tonga
Tonga, English
to, en
:flag_tt:
Trinidad and Tobago
English
en
:flag_tn:
Tunisia
Arabic
ar
:flag_tr:
Turkey
Turkish
tr
:flag_tm:
Turkmenistan
Turkmen
tk
:flag_tc:
Turks and Caicos Islands
English
en
:flag_tv:
Tuvalu
Tuvalu, English
tvl, en
:flag_ug:
Uganda
English, Swahili
en, sw
:flag_ua:
Ukraine
Ukrainian
uk
:flag_ae:
United Arab Emirates
Arabic
ar
:flag_gb:
United Kingdom
English
en
:flag_us:
United States
English
en
:flag_um:
United States Outlying Islands
English
en
:flag_uy:
Uruguay
Spanish, Portuguese
es, pt
:flag_uz:
Uzbekistan
Uzbek
uz
:flag_vu:
Vanuatu
Bislama, English, French
bi, en, fr
:flag_ve:
Venezuela
Spanish
es
:flag_vn:
Vietnam
Vietnamese
vi
:flag_vg:
British Virgin Islands
English
en
:flag_vi:
Us Virgin Islands
English
en
:flag_wf:
Wallis and Futuna
French
fr
:flag_eh:
Western Sahara
Arabic
ar
:flag_ye:
Yemen
Arabic
ar
:flag_zm:
Zambia
English
en
:flag_zw:
Zimbabwe
Chichewa, English, Xhosa, Southern Sotho, Shona
ny, en, xh, st, sn
Important Annoucement Shared Via Discord
PLEASE NOTE: This Update was accurate at the time of sharing. Please refer to our Support documentation to ensure accurate and up-to-date information is known, If you have any questions or concerns please join our and someone will assist.
Update on the state of RITA 1.3.0 Public Release.
PLEASE NOTE: This Update was accurate at the time of sharing. Please refer to our Support documentation to ensure accurate and up-to-date information is known, If you have any questions or concerns please join our and someone will assist.
Important Annoucement Shared Via Discord
PLEASE NOTE: This Update was accurate at the time of sharing. Please refer to our Support documentation to ensure accurate and up-to-date information is known, If you have any questions or concerns please join our and someone will assist.
Wooooo, Rita is back, and hopfully for good. (Launch Date: 01/05/2022 00:00 GMT)
PLEASE NOTE: This Update was accurate at the time of sharing. Please refer to our Support documentation to ensure accurate and up-to-date information is known, If you have any questions or concerns please join our and someone will assist.
If you have not been following our channel, or have not read our previous we would advise you to do this. It will answer most of your questions.
For further information check out or join our .
You can do this in a few ways. You can purchase from or . For info and step by step guide check out.
Head to and type `!tr sub` to get started... What are you waiting for?.
If you cant see the Subscription category in the , you can't access the channel, or something went wrong then please and we will assist you ASAP.
If you have any other Questions join our and we will try and answer them.
Important Annoucement Shared Via Discord
PLEASE NOTE: This Update was accurate at the time of sharing. Please refer to our Support documentation to ensure accurate and up-to-date information is known, If you have any questions or concerns please join our Discord Server and someone will assist.
In Effect From: August 20, 2023 / Last updated: August 15, 2023
S.A.L.T.S Policy - Document Version 4 (In Effect August 20, 2023 > Current)
S.A.L.T.S Stands for Subscription, Activation, Limitations, Termination and Suspension Policy. This describes Our policies and procedures on how each of the aforementioned processes are handled.
By using the Service, You agree to the following processes and be subject to enforcement of them.
The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located Here.
A User subscription follows the below flows. These are different for each subscription platform.
Refer to activation steps below in Activation Section.
Subscriptions are renewed on different days depending on the platform.
Patreon
Renews monthly on the 1st of each month regardless of subscription date. E.g., subscription is purchased and payment is taken on the 09th of May. On the 1st of June payment is taken, then again on the 1st July. This continues monthly until cancelation.
These plans are the base subscription plans on offer. Costs are fixed and can not be changed. Once a user has subscribed to the plan they will remain on the plan until the subscription is cancelled. See Tier Cost Changes & Availability for More information.
TRIAL USER
FREE* 1 Month
COMING SOON
The "Reaction" Plan
$2.99
20/08/23 - Current
The "Casual" Plan
$6.99
01/06/22 - Current
The "Tinkerer" Plan
$10.99
01/06/22 - Current
The "Pro" Plan
$15.99
01/06/22 - Current
The "Ultima" Plan
$21.99
20/08/23 - Current
TRIAL USER - The TRIAL will allow a user to try RITA for a period of one (1) month, or until limits have been reached, whichever comes first. Servers are limited to 1 TRIAL Per Server - Per Users.
These plans are subject to availability and are time-limited. Costs are fixed and can not be changed. Once a user has subscribed to the plan they will remain on the plan until the subscription is cancelled. Once an offer window has passed there is not guarantee it will be available again. See Tier Cost Changes & Availability for More information.
The "Casual" Plan - Offer
$4.83
01/06/22 - Current
The "Tinkerer" Plan - Offer
$8.24
01/06/22 - Current
The "Pro" Plan - Offer
$11.19
01/06/22 - Current
These plans are retired and no longer available. Costs are fixed and can not be changed. Once a user has subscribed to the plan they will remain on the plan until the subscription is cancelled. Once an is retired it will be available again. See Tier Cost Changes & Availability for More information.
The OG "Casual" Plan
$5.99
01/05/22 - 31/05/22
The OG "Tinkerer" Plan
$9.99
01/05/22 - 31/05/22
The OG "Pro" Plan
$14.99
01/05/22 - 31/05/22
Once a User has purchased a subscription, the cost they pay will not change, unless they cancel the subscription and then re-subscribe.
Cancellation due to failed payment resulting in the cancellation of an archived or expired plan cannot be re-activated, regardless of the reason.
No notice will be given on archiving or retiring a plan or removing availability; however, We believe in an open dialect with our customers. That said, business reason depends, We will provide information in the form of an announcement when possible.
All Plans/Tiers are subject to other limitations, detailed below.
User Invites RITA to server >
User Joins RMS Server >
User selects relevant plan provided by Patreon >
User completes payment via platform
Patreon > Payment is handled by Patreon
Upon Confirmation of payment User activates Discord integration through account linking.
Guide for Patreon
Integration uses the Patreon Bot to apply relevant roles to User, a Role from Payment, Tier, and the Subscription section below are needed for RITA to work.
RITA detects role additions and adds relevant and required data to our Subscription Database
Once User has all identifying Roles they are able to see the channel #activate-rita-here.
If role addition fails or is incomplete, then it is investigated by the ADMIN team. The ADMIN team will manually validate payment completion and then apply correct roles, if necessary.
User types `!tr sub` in the above noted channel or in their own server. If they own more than one server or are admin in more than one server, then they are prompted to select the server they want to use RITA in.
RITA must be in the server before the command is run, else an error will be provided.
RITA is activated and the subscription process is completed.
User Invites RITA to server >
User types `!tr trial` in their own server.
RITA is activated and the TRIAL Activation process is completed.
Each plan has the following limitation applied.
Due to the rising cost of our Hosting, Charges to Google and Payment Processing Services, we have made changes to the character limitations applied to each plan, this will take effect on the 1st of May 2023
TRIAL USER
25
10,000 Hard Cap
Google API / ML
The "Reaction" Plan
0
100,000 Soft Cap
Google API / ML
The OG "Casual" Plan
100
200,000 Soft Cap
Google API / ML
The "Casual" Plan - Offer
100
200,000 Soft Cap
Google API / ML
The "Casual" Plan
100
200,000 Soft Cap
Google API / ML
The OG "Tinkerer" Plan
200
400,000 Soft Cap
Google API / ML
The "Tinkerer" Plan - Offer
200
400,000 Soft Cap
Google API / ML
The "Tinkerer" Plan
200
400,000 Soft Cap
Google API / ML
The OG "Pro" Plan
350
600,000 Soft Cap
Google API / ML
The "Pro" Plan - Offer
350
600,000 Soft Cap
Google API / ML
The "Pro" Plan
350
600,000 Soft Cap
Google API / ML
The "Ultima" Plan
550
800,000 Soft Cap
Google API / ML
TRIAL USER - The TRIAL will allow a user to try RITA for a period of one (1) month, or until limits have been reached, whichever comes first. Servers are limited to 1 TRIAL Per Server - Per Users. Once Limit has been reached RITA will stop functioning for translations. Users do not need to be a Member of the RMS (RITA Management Server) to use the TRIAL.
Hard Cap = not enforced to the digit but close. This is calculated by
Example from English to French: Hello -> Bonjour
(5 Characters * 1 language translation) + 5 original chars = 10 Total Chars
Exceeding Character Limit will result in bot ceasing to respond to translation requests.
Soft Cap = not enforced to the digit but close. This is calculated by
(Number of Characters in message * Number of languages translated to) + Original Char Count = Total Char Count.
Example from English to French: Hello -> Bonjour
(5 Characters * 1 language translation) + 5 original chars = 10 Total Chars
Exceeding Character Limit. Either of the following Scenarios are taken, via automation by RITA or manual intervention by a member of RMS Staff
A server exceeds the soft caps assigned to their plan
Translation Services are swapped from Implicit Google API Translation to Implicit Machine Learning API Translation for Languages we have trained and that are optimized to a high standard. See Machine Learning API for more information.
At the start of the next calendar month Implicit Google API Translation is reactivated until breach of soft cap
ML API currently has an upper bound limit of 10 million characters translated per month. This upper bond if not hard coded in to RITA, however it is checked periodically throughout the month. If a User exceeds this a custom tier cost or solution may be required, however no suspension will happen as a result of this limit.
Bulgarian
bg
1.4.0
Chinese (Simplified)
zh-CN
1.4.0
Chinese (Traditional)
zh-TW
1.4.0
Czech
cs
1.4.0
English
en
1.4.0
French
fr
1.4.0
Indonesian
id
1.4.0
Italian
it
1.4.0
Japanese
ja
1.4.0
Korean
ko
1.4.0
Portuguese
pt
1.4.0
Romanian
ro
1.4.0
Russian
ru
1.4.0
Serbian
sr
1.4.0
Ukrainian
uk
1.4.0
Vietnamese
vi
1.4.0
The Termination Process is used in conjunction with the Suspension Process and follows a pre-defined path.
AT NO POINT IN THIS PROCESS IS THE END USER ELIGIBLE FOR A REFUND. THIS PROCESS IS ONLY EXECUTED IN THE MOST SERIOUS OF CIRCUMSTANCES.
The Termination flow can only executed/started by the following RMS staff levels and is governed by a strict time frame.
Owners
Admins
Developers
A Suspension of Service can be implemented for a varying number of reasons. This is referred to as Pausing.
Pausing and resuming of service can only be conducted by the following RMS staff levels
RITA
Owners
Admins
Developers
Senior Staff
Service can be Paused under the following conditions
Detection of suspicious activity.
We cannot share what this look like to prevent anti-detection methods
Exceeding Character Limits of Tier (*When Implemented)
This could be Google API Limits or ML Limits
Suspicion that RITA is being used for SPAM or JUNK flooding
Request to Terminate by third party agencies or companies in line with our Privacy Policy and ToS.
Identification that RITA is being used for Commercial use exceeding fair and reasonable use. This is not defined and will be reviewed on a case by case basis. This does not exclude the use of RITA from commercial use.
If Service is Paused, We are not able to offer pro rata refunds for the time the service is paused, inactive or non-operational. This is in line with our Refund Policy.
Last updated: September 27, 2022
S.A.L.T.S Policy - Document Version 2 (In Effect September 27, 2022 > May 01, 2023)
S.A.L.T.S Stands for Subscription, Activation, Limitations, Termination and Suspension Policy. This describes Our policies and procedures on how each of the aforementioned processes are handled.
By using the Service, You agree to the following processes and be subject to enforcement of them.
The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located Here.
A User subscription follows the below flows. These are different for each subscription platform.
Refer to activation steps below in Activation Section.
Subscriptions are renewed on different days depending on the platform.
Ko-Fi
Renews monthly from the date subscribed. E.g., subscription is purchased and payment is taken on the 09th of May. On the 9th of June payment is taken again, then again on the 9th July. This continues monthly until cancelation.
Patreon
Renews monthly on the 1st of each month regardless of subscription date. E.g., subscription is purchased and payment is taken on the 09th of May. On the 1st of June payment is taken, then again on the 1st July. This continues monthly until cancelation.
The OG "Casual" Plan
$5.99
01/05/22 - 31/05/22
Plan Discontinued, Existing Users remain.
The "Casual" Plan
$6.99
01/06/22 - Current
Replacement Tier to [The OG "Casual" Plan]
The OG "Tinkerer" Plan
$9.99
01/05/22 - 31/05/22
Plan Discontinued, Existing Users remain.
The "Tinkerer" Plan
$10.99
01/06/22 - Current
Replacement Tier to [The OG "Tinkerer" Plan]
The OG "Pro" Plan
$14.99
01/05/22 - 31/05/22
Plan Discontinued, Existing Users remain.
The "Pro" Plan
$15.99
01/06/22 - Current
Replacement Tier to [The OG "Pro" Plan]
Once a User has purchased a subscription, the cost they pay will not change, unless they cancel the subscription and then re-subscribe.
Cancelation due to failed payment resulting in cancelation of a archived or expired plan cannot be re-activated, regardless of reason.
No notice will be given on archiving of a plan or removing availability; however, We believe in an open dialect with our customers. That said, business reason depending, We will provide information in the form of an announcement when possible.
All Plans/Tiers are subject to other limitations, detailed below.
User Invites RITA to server >
User Joins RMS Server >
User selects relevant plan provided by Ko-Fi/Patreon >
User completes payment via platform
Ko-Fi > PayPal or Stripe
Patreon > Payment is handled by Patreon
Upon Confirmation of payment User activates Discord integration through account linking.
Guide for Ko-Fi
Guide for Patreon
Integration uses the Ko-Fi and Patreon Bot to apply relevant roles to User, a Role from Payment, Tier, and the Subscription section below are needed for RITA to work.
RITA detects role additions and adds relevant and required data to our Subscription Database
Once User has all identifying Roles they are able to see the channel #activate-rita-here.
If role addition fails or is incomplete, then it is investigated by the ADMIN team. The ADMIN team will manually validate payment completion and then apply correct roles, if necessary.
User types `!tr sub` in the above noted channel or in their own server. If they own more than one server or are admin in more than one server, then they are prompted to select the server they want to use RITA in.
RITA must be in the server before the command is run, else an error will be provided.
RITA is activated and the subscription process is completed.
Each plan has the following limitation applied.
The OG "Casual" Plan
100
200,000 Soft Cap
The "Casual" Plan
100
200,000 Soft Cap
The OG "Tinkerer" Plan
200
450,000 Soft Cap
The "Tinkerer" Plan
200
450,000 Soft Cap
The OG "Pro" Plan
350
700,000 Soft Cap
The "Pro" Plan
350
700,000 Soft Cap
Soft Cap = not enforced to the digit but close. This is calculated by
(Number of Characters in message * Number of languages translated to) + Original Char Count = Total Char Count.
Example: English Message: Hello
Translated to French: Bonjour
(5 Characters * 1 language translation) + 5 original chars = 10 Total Chars
Exceeding Character Limit. Either of the following Scenarios are taken, via automation by RITA or manual intervention by a member of RMS Staff
A server exceeds the soft caps assigned to their plan
Translation Services are swapped from Implicit Google API Translation to Implicit Machine Learning API Translation
At the start of the next calandar month Implicit Google API Translation is reactivated until breach of soft cap
ML API currently has an upper bound limit of 2 million characters translated per month. If a User exceeds this a custom tier cost or solution may be required.
The Termination Process is used in conjunction with the Suspension Process and follows a pre-defined path.
AT NO POINT IN THIS PROCESS IS THE END USER ELIGIBLE FOR A REFUND. THIS PROCESS IS ONLY EXECUTED IN THE MOST SERIOUS OF CIRCUMSTANCES.
The Termination flow can only executed/started by the following RMS staff levels and is governed by a strict time frame.
Owners
Admins
Developers
A Suspension of Service can be implemented for a varying number of reasons. This is refer to as Pausing.
Pausing and resuming of service can only be conducted by the following RMS staff levels
RITA
Owners
Admins
Developers
Senior Staff
Service can be Paused under the following conditions
Detection of suspicious activity.
We cannot share what this look like to prevent anti-detection methods
Exceeding Character Limits of Tier (*When Implemented)
This could be Google API Limits or ML Limits
Suspicion that RITA is being used for SPAM or JUNK flooding
Request to Terminate by third party agencyies or companies in line with our Privacy Policy and ToS.
Identification that RITA is being used for Commercial use exceeding fair and reasonable use. This is not defined and will be reviewed on a case by case basis. This does not exclude the use of RITA from commercial use.
If Service is Paused, We are not able to offer pro rata refunds for the time the service is paused, inactive or non-operational. This is in line with our Refund Policy.
Important Annoucement Shared Via Discord
PLEASE NOTE: This Update was accurate at the time of sharing. Please refer to our Support documentation to ensure accurate and up-to-date information is known, If you have any questions or concerns please join our Discord Server and someone will assist.
The following explains new additions to our newest release of Rita (v.1.4.1) which will be released in the coming days/weeks
Ex. You use 700k characters next month with the "Casual" plan (100 tasks) - 200k of that would use google, and the other 500k characters are translated with ML. Then on renewal date, the character count resets. If you have any questions or concerns, feel free to open-a-ticket As always, thank you for using RitaBot and supporting us, - The RitaBot Team
Last updated: April 22, 2022
The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located Here.
You are strictly prohibited to use RitaBot against the ToS of discord or for illegal purposes. We are doing our best to prevent these activities, while trying to provide the best user experience as possible. If you find people or communities using RitaBot against the ToS of discord or even for illegal activities, please send us an email to dev@ritabot.gg
We (RitaBot) own and retain all rights for public available data (including but not limited to templates). We grant you the permission to use this available data for your own needs, but strictly disallow any commercial use. You therefore shall not sell, license or otherwise commercialize the data except if the permission was expressly granted to you.
RitaBot is provided as-is. There are no guarantees that it will be available in the future, and its purpose or availability may be changed at any time.
Usage Data including backups may be deleted at any time.
Any "pro" or "premium" Features are not guaranteed. They may change or be revoked at any time.
Access to all or specific Features of RitaBot may be revoked, for all or a specific user, at any time.
To operate RitaBot and in specific the Database we use requieres we save some information about You, your Discord server and the members.
Usernames & Discriminators.
Server Name & ID
Channel ID's, Role ID's and User/Owner ID's
We may also store anonymized Personal Data about you including your username, discriminator and public flags (badges) in line with our Privacy Policy. This information is only used for analytics and can not be tracked back to You.
S.A.L.T.S Stands for Subscription, Activation, Limitations, Termination and Suspension Policy. This describes Our policies and procedures on how each of the aformentioned processes are handled.
By using the Service, You agree to the following processes and be subject to enforcment of them. Please refer to S.A.L.T.S Policy for more information.
Important Annoucement Shared Via Discord
PLEASE NOTE: This Update was accurate at the time of sharing. Please refer to our Support documentation to ensure accurate and up-to-date information is known, If you have any questions or concerns please join our Discord Server and someone will assist.
Last updated: April 22, 2022
S.A.L.T.S Policy - Document Version 1 (In Effect April 22, 2022 > September 27, 2022)
S.A.L.T.S Stands for Subscription, Activation, Limitations, Termination and Suspension Policy. This describes Our policies and procedures on how each of the aforementioned processes are handled.
By using the Service, You agree to the following processes and be subject to enforcement of them.
The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located Here.
A User subscription follows the below flows. These are different for each subscription platform.
Refer to activation steps below in Activation Section.
Subscriptions are renewed on different days depending on the platform.
Ko-Fi
Renews monthly from the date subscribed. E.g., subscription is purchased and payment is taken on the 09th of May. On the 9th of June payment is taken again, then again on the 9th July. This continues monthly until cancelation.
Patreon
Renews monthly on the 1st of each month regardless of subscription date. E.g., subscription is purchased and payment is taken on the 09th of May. On the 1st of June payment is taken, then again on the 1st July. This continues monthly until cancelation.
The OG "Casual" Plan
$5.99
01/05/22 - 31/05/22
Plan Discontinued, Existing Users remain.
The "Casual" Plan
$6.99
01/06/22 - Current
Replacement Tier to [The OG "Casual" Plan]
The OG "Tinkerer" Plan
$9.99
01/05/22 - 31/05/22
Plan Discontinued, Existing Users remain.
The "Tinkerer" Plan
$10.99
01/06/22 - Current
Replacement Tier to [The OG "Tinkerer" Plan]
The OG "Pro" Plan
$14.99
01/05/22 - 31/05/22
Plan Discontinued, Existing Users remain.
The "Pro" Plan
$15.99
01/06/22 - Current
Replacement Tier to [The OG "Pro" Plan]
Once a User has purchased a subscription, the cost they pay will not change, unless they cancel the subscription and then re-subscribe.
Cancelation due to failed payment resulting in cancelation of a archived or expired plan cannot be re-activated, regardless of reason.
No notice will be given on archiving of a plan or removing availability; however, We believe in an open dialect with our customers. That said, business reason depending, We will provide information in the form of an announcement when possible.
All Plans/Tiers are subject to other limitations, detailed below.
User Invites RITA to server >
User Joins RMS Server >
User selects relevant plan provided by Ko-Fi/Patreon >
User completes payment via platform
Ko-Fi > PayPal or Stripe
Patreon > Payment is handled by Patreon
Upon Confirmation of payment User activates Discord integration through account linking.
Guide for Ko-Fi
Guide for Patreon
Integration uses the Ko-Fi and Patreon Bot to apply relevant roles to User, a Role from Payment, Tier, and the Subscription section below are needed for RITA to work.
RITA detects role additions and adds relevant and required data to our Subscription Database
Once User has all identifying Roles they are able to see the channel #activate-rita-here.
If role addition fails or is incomplete, then it is investigated by the ADMIN team. The ADMIN team will manually validate payment completion and then apply correct roles, if necessary.
User types `!tr sub` in the above noted channel or in their own server. If they own more than one server or are admin in more than one server, then they are prompted to select the server they want to use RITA in.
RITA must be in the server before the command is run, else an error will be provided.
RITA is activated and the subscription process is completed.
Content Here
The Termination Process is used in conjunction with the Suspension Process and follows a pre-defined path.
AT NO POINT IN THIS PROCESS IS THE END USER ELIGIBLE FOR A REFUND. THIS PROCESS IS ONLY EXECUTED IN THE MOST SERIOUS OF CIRCUMSTANCES.
The Termination flow can only executed/started by the following RMS staff levels and is governed by a strict time frame.
Owners
Admins
Developers
A Suspension of Service can be implemented for a varying number of reasons. This is refer to as Pausing.
Pausing and resuming of service can only be conducted by the following RMS staff levels
RITA
Owners
Admins
Developers
Senior Staff
Service can be Paused under the following conditions
Detection of suspicious activity.
We cannot share what this look like to prevent anti-detection methods
Exceeding Character Limits of Tier (*When Implemented)
This could be Google API Limits or ML Limits
Suspicion that RITA is being used for SPAM or JUNK flooding
Request to Terminate by third party agencyies or companies in line with our Privacy Policy and ToS.
Identification that RITA is being used for Commercial use exceeding fair and reasonable use. This is not defined and will be reviewed on a case by case basis. This does not exclude the use of RITA from commercial use.
If Service is Paused, We are not able to offer pro rata refunds for the time the service is paused, inactive or non-operational. This is in line with our Refund Policy.
Last updated: August 15, 2023
S.A.L.T.S Policy - Document Version 3 (In Effect May 01, 2023 > August 20, 2023)
S.A.L.T.S Stands for Subscription, Activation, Limitations, Termination and Suspension Policy. This describes Our policies and procedures on how each of the aforementioned processes are handled.
By using the Service, You agree to the following processes and be subject to enforcement of them.
The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located Here.
A User subscription follows the below flows. These are different for each subscription platform.
Refer to activation steps below in Activation Section.
Subscriptions are renewed on different days depending on the platform.
Patreon
Renews monthly on the 1st of each month regardless of subscription date. E.g., subscription is purchased and payment is taken on the 09th of May. On the 1st of June payment is taken, then again on the 1st July. This continues monthly until cancelation.
These plans are the base subscription plans on offer. Costs are fixed and can not be changed. Once a user has subscribed to the plan they will remain on the plan until the subscription is cancelled. See Tier Cost Changes & Availability for More information.
REDACTED
REDACTED
REDACTED
The "Casual" Plan
$6.99
01/06/22 - Current
The "Tinkerer" Plan
$10.99
01/06/22 - Current
The "Pro" Plan
$15.99
01/06/22 - Current
REDACTED
REDACTED
REDACTED
These plans are subject to availability and are time-limited. Costs are fixed and can not be changed. Once a user has subscribed to the plan they will remain on the plan until the subscription is cancelled. Once an offer window has passed there is not guarantee it will be available again. See Tier Cost Changes & Availability for More information.
The "Casual" Plan - Offer
$4.83
01/06/22 - Current
The "Tinkerer" Plan - Offer
$8.24
01/06/22 - Current
The "Pro" Plan - Offer
$11.19
01/06/22 - Current
These plans are retired and no longer available. Costs are fixed and can not be changed. Once a user has subscribed to the plan they will remain on the plan until the subscription is cancelled. Once an is retired it will be available again. See Tier Cost Changes & Availability for More information.
The OG "Casual" Plan
$5.99
01/05/22 - 31/05/22
The OG "Tinkerer" Plan
$9.99
01/05/22 - 31/05/22
The OG "Pro" Plan
$14.99
01/05/22 - 31/05/22
Once a User has purchased a subscription, the cost they pay will not change, unless they cancel the subscription and then re-subscribe.
Cancellation due to failed payment resulting in the cancellation of an archived or expired plan cannot be re-activated, regardless of the reason.
No notice will be given on archiving or retiring a plan or removing availability; however, We believe in an open dialect with our customers. That said, business reason depends, We will provide information in the form of an announcement when possible.
All Plans/Tiers are subject to other limitations, detailed below.
User Invites RITA to server >
User Joins RMS Server >
User selects relevant plan provided by Patreon >
User completes payment via platform
Patreon > Payment is handled by Patreon
Upon Confirmation of payment User activates Discord integration through account linking.
Guide for Patreon
Integration uses the Patreon Bot to apply relevant roles to User, a Role from Payment, Tier, and the Subscription section below are needed for RITA to work.
RITA detects role additions and adds relevant and required data to our Subscription Database
Once User has all identifying Roles they are able to see the channel #activate-rita-here.
If role addition fails or is incomplete, then it is investigated by the ADMIN team. The ADMIN team will manually validate payment completion and then apply correct roles, if necessary.
User types `!tr sub` in the above noted channel or in their own server. If they own more than one server or are admin in more than one server, then they are prompted to select the server they want to use RITA in.
RITA must be in the server before the command is run, else an error will be provided.
RITA is activated and the subscription process is completed.
Each plan has the following limitation applied.
Due to the rising cost of our Hosting, Charges to Google and Payment Processing Services, we have made changes to the character limitations applied to each plan, this will take effect on the 1st of May 2023
REDACTED
REDACTED
REDACTED
REDACTED
The OG "Casual" Plan
100
200,000 Soft Cap
Google API / ML
The "Casual" Plan - Offer
100
200,000 Soft Cap
Google API / ML
The "Casual" Plan
100
200,000 Soft Cap
Google API / ML
The OG "Tinkerer" Plan
200
400,000 Soft Cap
Google API / ML
The "Tinkerer" Plan - Offer
200
400,000 Soft Cap
Google API / ML
The "Tinkerer" Plan
200
400,000 Soft Cap
Google API / ML
The OG "Pro" Plan
350
600,000 Soft Cap
Google API / ML
The "Pro" Plan - Offer
350
600,000 Soft Cap
Google API / ML
The "Pro" Plan
350
600,000 Soft Cap
Google API / ML
REDACTED
REDACTED
REDACTED
REDACTED
Soft Cap = not enforced to the digit but close. This is calculated by
(Number of Characters in message * Number of languages translated to) + Original Char Count = Total Char Count.
Example from English to French: Hello -> Bonjour
(5 Characters * 1 language translation) + 5 original chars = 10 Total Chars
Exceeding Character Limit. Either of the following Scenarios are taken, via automation by RITA or manual intervention by a member of RMS Staff
A server exceeds the soft caps assigned to their plan
Translation Services are swapped from Implicit Google API Translation to Implicit Machine Learning API Translation for Languages we have trained and that are optimized to a high standard. See Machine Learning API for more information.
At the start of the next calendar month Implicit Google API Translation is reactivated until breach of soft cap
ML API currently has an upper bound limit of 10 million characters translated per month. This upper bond if not hard coded in to RITA, however it is checked periodically throughout the month. If a User exceeds this a custom tier cost or solution may be required, however no suspension will happen as a result of this limit.
Bulgarian
bg
1.4.0
Chinese (Simplified)
zh-CN
1.4.0
Chinese (Traditional)
zh-TW
1.4.0
Czech
cs
1.4.0
English
en
1.4.0
French
fr
1.4.0
Indonesian
id
1.4.0
Italian
it
1.4.0
Japanese
ja
1.4.0
Korean
ko
1.4.0
Portuguese
pt
1.4.0
Romanian
ro
1.4.0
Russian
ru
1.4.0
Serbian
sr
1.4.0
Ukrainian
uk
1.4.0
Vietnamese
vi
1.4.0
The Termination Process is used in conjunction with the Suspension Process and follows a pre-defined path.
AT NO POINT IN THIS PROCESS IS THE END USER ELIGIBLE FOR A REFUND. THIS PROCESS IS ONLY EXECUTED IN THE MOST SERIOUS OF CIRCUMSTANCES.
The Termination flow can only executed/started by the following RMS staff levels and is governed by a strict time frame.
Owners
Admins
Developers
A Suspension of Service can be implemented for a varying number of reasons. This is referred to as Pausing.
Pausing and resuming of service can only be conducted by the following RMS staff levels
RITA
Owners
Admins
Developers
Senior Staff
Service can be Paused under the following conditions
Detection of suspicious activity.
We cannot share what this look like to prevent anti-detection methods
Exceeding Character Limits of Tier (*When Implemented)
This could be Google API Limits or ML Limits
Suspicion that RITA is being used for SPAM or JUNK flooding
Request to Terminate by third party agencies or companies in line with our Privacy Policy and ToS.
Identification that RITA is being used for Commercial use exceeding fair and reasonable use. This is not defined and will be reviewed on a case by case basis. This does not exclude the use of RITA from commercial use.
If Service is Paused, We are not able to offer pro rata refunds for the time the service is paused, inactive or non-operational. This is in line with our Refund Policy.
Refer to the below service and their Respective TOS and Policies
Links provided are for convenience and may not be the sum of all policies and agreements that govern each end user in every region and territory. Please refer to respective services for more information and links to policies that may effect you.
Last updated: April 22, 2022
Refund Policy - Document Version 1 (In Effect April 22, 2022 > May 01, 2023)
This Refund Policy describes our policies regarding the handling of refunds in general and does not serve as a legal base, nor is it approved by professionals. It is used to lay down the foundations for any decision made upon requests. Any point listed here might be a reason for permitted initiations of any refund.
The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located Here.
Refunds for payments may be issued when the user requests it and one of the following requirements is met:
it's the first payment and the user requests a refund on the same day (Usage Exception Applies)
it's a monthly recurring payment and the user requests a refund within a three day period (Usage Exception Applies)
it's an annual recurring payment and the user requests a refund within a seven day period (Usage Exception Applies)
A major premium feature was removed and the user bought the tier specifically because of that feature
Users who subscribe via Patreon are charged as soon as you sign up. Patrons' payments are recurring on the 1st of every month after that. This mean you are charge for the month (January, February ect), not a month (30 Days) of access.
Each charge for the month gives them membership access for that month. For example,
You subscribe to RITA on the 1st January, this payment gives you access throughout the rest of January. Your next payment is 1st February then 1st March ect ect.
You subscribe to RITA on the 15th January, this payment gives you access throughout the rest of January. Your next payment is 1st February then 1st March ect ect.
Users who subscribe via Kofi are subject to recurring billing. You are charged as soon as they sign up. KOFIs' payments are recurring on the same day of every month after that. This mean you are charge for a month (30 Days), not the month (January, February ect) of access.
Each charge for the month gives them membership access for 30 days. For example,
You subscribe to RITA on the 1st January, this payment gives you access until 1st February. Your next payment is 1st February then 1st March ect ect.
You subscribe to RITA on the 15th January, this payment gives you access until 15th February. Your next payment is 15th February then 15th March ect ect.
Listed below are other possible reasons that might permit a full or prorated refund.
Any kind of unauthorized transaction that was not undertaken on your behalf but financially affects you.
A situation in which you are not successfully receiving or are unable to access promised premium features.
Service uptime of less than 80% (24 Days in a rolling 30 day period) due to maintenance, takedown, core functionality issues or other services under the direct control of RitaBot or the Rita Bot Dev Team.
All/Any of the reasons above require viable proof to be accepted as possible inquiries for the initiation of a refund.
Below listed are situations in which any kind of refund will not permit a full or prorated refund.
Any situation in which you actively or passively forgot to cancel your ongoing subscription, and it's passed the subscription exclusion timeframe listed above.
Downtime caused by 3rd Party Service Providers, Including but not limited to, Discord, Heroku, Paypal, Stripe, PebbleHost, Domain Controllers and DNS Providers.
You are a Patreon user and have had the second payment of a recurring subscription taken/renewed on the 1st of the month. As this is Defined during the purchase process, regardless of the date of the first payment you are charged for the month (January, February ect) not a month (30 Days).
Please note that all refund requests are handled on a case by case basis, however, the reasons above may prohibit responses to refund requests.
IF you have activated RITA, defined in our SALTS Policy #Activation, and have used RITA service with a Character count exceeding 10,000 Character, you will NOT be eligible for a refund under any circumstance. to see your character count type "!translate stats" in your server.
All Donations, Made on any of the accepted payment platform we use are Non-Refundable with the exceptions of,
Any kind of unauthorized transaction that was not undertaken on your behalf but financially affects you.
All/Any of the reasons above require viable proof to be accepted as possible inquiries for the initiation of a refund.
If you choose to or threaten to chargeback, we reserve the right to ban and/or blacklist you from the bot. This includes but is not limited to:
Immediate termination of service
Permanent and non reversible ban
Support requests will not be answered
Guild ID is excluded from the usage of our service indefinitely
Performing a chargeback on behalf of the payment processor your transaction was handled through, without contacting or attempting to contact RitaBot, In most situations means we can, and will, fight such cases to dispute the chargeback.
Financial Transactions and Decisions are handled by a single member of staff, Responses to such requests will be given within 72 hours, between 8 am and 9 pm GMT, Excluding bank holidays and public holidays. We still require a comprehensible explanation of the situation and never guarantee a refund, except as listed in the subscription exclusion timeframe listed above. Partial refunds might be issued for annual payments under special circumstances.
Refunds are never issued if you have broken our Terms of Service and therefore lost access to certain or all features.
If you believe your situation is viable for a refund you may wish to contact us via one of the ways listed below.
From the email address related to the Discord account that is affected if accessible. Just send us a descriptive message to payment@ritabot.gg
On our Discord support server with the Discord account that is affected if accessible.
In any private ticket/message with a staff member from the RitaBot team.
Last updated: September 27, 2022
Privacy Policy - Document Version 2 (In Effect September 27, 2022 > May 01, 2023)
This Privacy Policy describes Our policies and procedures on the collection, use and disclosure of Your information when You use the Service and tells You about Your privacy rights and how the law protects You.
We use Your Personal data to provide and improve the Service. By using the Service, You agree to the collection and use of information in accordance with this Privacy Policy.
We do not Sell or Provide any Personal Data collected, as defined below, to any 3rd Party Company.
The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located Here.
While using Our Service, We may ask You to provide Us with certain personally identifiable information that can be used to identify You and provide your access to the Service. Personally identifiable information may include, but is not limited to: Discord Account ID's, Channel ID's, Server ID's and more.
While using Our Service, We may collect anonymised translation data. This is used to train our in-house Machine Learning translation model. The data collected is comprised of the following values;
Source Language
Destination Language
Content of Message sent
Content of Message received after translation
This data cannot be linked to the source server. All identifiable values such as Guild ID, User ID, Username, Channel ID and other identifiable data found within the Discord API is not collected. This data is stored for a period of 60 days, or when the collection files (All possible Language Pairs) reach 200GB, which ever is sooner. Data is automatically overridden and non-recoverable.
As this data is anonymised it is not possible to request this data as part of a Subject Access request, more commonly known as "Request My Data".
Usage Data is collected automatically when using the Service.
Usage Data in relation to our Website may include information such as Your Device's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that You visit, the time and date of Your visit, the time spent on those pages, unique device identifiers and other diagnostic data.
When You access the Service on Discord, We may collect certain information automatically, including, but not limited to, original message language, target language, character count, and other diagnostic data.
We may also collect information that Your browser sends whenever You visit our Website.
We use Cookies and similar tracking technologies to track the activity on Our Service and store certain information. Tracking technologies used are beacons, tags, and scripts to collect and track information and to improve and analyze Our Service. The technologies We use may include:
Cookies or Browser Cookies. A cookie is a small file placed on Your Device. You can instruct Your browser to refuse all Cookies or to indicate when a Cookie is being sent. However, if You do not accept Cookies, You may not be able to use some parts of our Service. Unless you have adjusted Your browser setting so that it will refuse Cookies, our Service may use Cookies.
Flash Cookies. Certain features of our Service may use local stored objects (or Flash Cookies) to collect and store information about Your preferences or Your activity on our Service. Flash Cookies are not managed by the same browser settings as those used for Browser Cookies. For more information on how You can delete Flash Cookies, please read "Where can I change the settings for disabling, or deleting local shared objects?" available at https://helpx.adobe.com/flash-player/kb/disable-local-shared-objects-flash.html#main_Where_can_I_change_the_settings_for_disabling__or_deleting_local_shared_objects_
Web Beacons. Certain sections of our Service and our emails may contain small electronic files known as web beacons (also referred to as clear gifs, pixel tags, and single-pixel gifs) that permit the Company, for example, to count users who have visited those pages or opened an email and for other related website statistics (for example, recording the popularity of a certain section and verifying system and server integrity).
Cookies can be "Persistent" or "Session" Cookies. Persistent Cookies remain on Your personal computer or mobile device when You go offline, while Session Cookies are deleted as soon as You close Your web browser. You can learn more about cookies here: Cookies by TermsFeed Generator.
We use both Session and Persistent Cookies for the purposes set out below:
Necessary / Essential Cookies
Type: Session Cookies
Administered by: Us
Purpose: These Cookies are essential to provide You with services available through the Website and to enable You to use some of its features. They help to authenticate users and prevent fraudulent use of user accounts. Without these Cookies, the services that You have asked for cannot be provided, and We only use these Cookies to provide You with those services.
Cookies Policy / Notice Acceptance Cookies
Type: Persistent Cookies
Administered by: Us
Purpose: These Cookies identify if users have accepted the use of cookies on the Website.
Functionality Cookies
Type: Persistent Cookies
Administered by: Us
Purpose: These Cookies allow us to remember choices You make when You use the Website, such as remembering your login details or language preference. The purpose of these Cookies is to provide You with a more personal experience and to avoid You having to re-enter your preferences every time You use the Website.
For more information about the cookies we use and your choices regarding cookies, please visit our Cookies Policy or the Cookies section of our Privacy Policy.
The Company may use Personal Data for the following purposes:
To provide and maintain our Service, including to monitor the usage of our Service.
To manage Your Account: to manage Your registration as a user of the Service. The Personal Data You provide can give You access to different functionalities of the Service that are available to You as a registered user.
For the performance of a contract: the development, compliance and undertaking of the purchase contract for the products, items or services You have purchased or of any other contract with Us through the Service.
To contact You: To contact You by email, telephone calls, SMS, or other equivalent forms of electronic communication, such as a mobile application's push notifications regarding updates or informative communications related to the functionalities, products or contracted services, including the security updates, when necessary or reasonable for their implementation.
To provide You with news, special offers and general information about other goods, services and events which we offer that are similar to those that you have already purchased or enquired about unless You have opted not to receive such information.
To manage Your requests: To attend and manage Your requests to Us.
For business transfers: We may use Your information to evaluate or conduct a merger, divestiture, restructuring, reorganization, dissolution, or other sale or transfer of some or all of Our assets, whether as a going concern or as part of bankruptcy, liquidation, or similar proceeding, in which Personal Data held by Us about our Service users is among the assets transferred.
For other purposes: We may use Your information for other purposes, such as data analysis, identifying usage trends, determining the effectiveness of our promotional campaigns and to evaluate and improve our Service, products, services, marketing and your experience.
We may share Your personal information in the following situations:
With Service Providers: We may share Your personal information with Service Providers to monitor and analyze the use of our Service, to contact You.
For business transfers: We may share or transfer Your personal information in connection with, or during negotiations of, any merger, sale of Company assets, financing, or acquisition of all or a portion of Our business to another company.
With Affiliates: We may share Your information with Our affiliates, in which case we will require those affiliates to honor this Privacy Policy. Affiliates include Our parent company and any other subsidiaries, joint venture partners or other companies that We control or that are under common control with Us.
With business partners: We may share Your information with Our business partners to offer You certain products, services or promotions.
With other users: when You share personal information or otherwise interact in the public areas with other users, such information may be viewed by all users and may be publicly distributed outside.
With Your consent: We may disclose Your personal information for any other purpose with Your consent.
The Company will retain Your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use Your Personal Data to the extent necessary to comply with our legal obligations (for example, if we are required to retain your data to comply with applicable laws), resolve disputes, and enforce our legal agreements and policies.
The Company will also retain Usage Data for internal analysis purposes. Usage Data is generally retained for a shorter period of time, except when this data is used to strengthen the security or to improve the functionality of Our Service, or We are legally obligated to retain this data for longer time periods.
Your information, including Personal Data, is processed at the Company's operating offices and in any other places where the parties involved in the processing are located. It means that this information may be transferred to — and maintained on — computers located outside of Your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from Your jurisdiction.
Your consent to this Privacy Policy followed by Your submission of such information represents Your agreement to that transfer.
The Company will take all steps reasonably necessary to ensure that Your data is treated securely and in accordance with this Privacy Policy and no transfer of Your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of Your data and other personal information.
If the Company is involved in a merger, acquisition or asset sale, Your Personal Data may be transferred. We will provide notice before Your Personal Data is transferred and becomes subject to a different Privacy Policy.
Under certain circumstances, the Company may be required to disclose Your Personal Data if required to do so by law or in response to valid requests by public authorities (e.g. a court or a government agency).
The Company may disclose Your Personal Data in the good faith belief that such action is necessary to:
Comply with a legal obligation
Protect and defend the rights or property of the Company
Prevent or investigate possible wrongdoing in connection with the Service
Protect the personal safety of Users of the Service or the public
Protect against legal liability
The security of Your Personal Data is important to Us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While We strive to use commercially acceptable means to protect Your Personal Data, We cannot guarantee its absolute security.
Our Service does not address anyone under the age of 13. We do not knowingly collect personally identifiable information from anyone under the age of 13. If You are a parent or guardian and You are aware that Your child has provided Us with Personal Data, please contact Us. If We become aware that We have collected Personal Data from anyone under the age of 13 without verification of parental consent, We take steps to remove that information from Our servers.
If We need to rely on consent as a legal basis for processing Your information and Your country requires consent from a parent, We may require Your parent's consent before We collect and use that information.
Our Service may contain links to other websites that are not operated by Us. If You click on a third party link, You will be directed to that third party's site. We strongly advise You to review the Privacy Policy of every site You visit.
We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.
We may update Our Privacy Policy from time to time. We will notify You of any changes by posting the new Privacy Policy on this page.
We will let You know via a prominent notice on Our Service or Discord Announcement, prior to the change becoming effective and update the "Last updated" date at the top of this Privacy Policy.
You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.
If you have any questions about this Privacy Policy, You can contact us:
By email: dev@ritabot.gg
By visiting this page on our website: https://discord.gg/invite/7yYUWruQp6
Last updated: April 05, 2023
15/08/23 S.A.L.T.S Policy Update
Further clarification of changes can be provided upon request.
01/05/23 Privacy & S.A.L.T.S Policy Update
Change to soft Limits defined in S.A.L.T.S Policy #Limitations may constitute a Right to Exit, all cases and claims will be reviewed on case-by-case basis if raised. Accepted claims must be raised within 30 days from the dated change of policy, after which, further claims will not constitute a Right to Exit and claims will be denied.
Please email dev@ritabot.gg with details of your case/claim and we will review.
Please allow 48 hours for a response
Requesting a chargeback or refund from your payment provider will be managed under our Refund Policy
Direct or Indirect use of our Proprietary Machine Learning Translation Engine does not constitute a change in service provided, as such does not constitute a Right to Exit.
Further clarification of changes can be provided upon request.
26/09/22 Privacy & S.A.L.T.S Policy Update
Please email dev@ritabot.gg with details of your case/claim and we will review.
Please allow 48 hours for a response
Requesting a chargeback or refund from your payment provider will be managed under our Refund Policy
Further clarification of changes can be provided upon request.
Last updated: March 15, 2022
Privacy Policy - Document Version 1 (In Effect March 15, 2022 > September 27, 2022)
This Privacy Policy describes Our policies and procedures on the collection, use and disclosure of Your information when You use the Service and tells You about Your privacy rights and how the law protects You.
We use Your Personal data to provide and improve the Service. By using the Service, You agree to the collection and use of information in accordance with this Privacy Policy.
We do not Sell or Provide any Personal Data collected, as defined below, to any 3rd Party Company.
The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located Here.
While using Our Service, We may ask You to provide Us with certain personally identifiable information that can be used to identify You and provide your access to the Service. Personally identifiable information may include, but is not limited to: Discord Account ID's, Channel ID's, Server ID's and more.
Usage Data is collected automatically when using the Service.
Usage Data in relation to our Website may include information such as Your Device's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that You visit, the time and date of Your visit, the time spent on those pages, unique device identifiers and other diagnostic data.
When You access the Service on Discord, We may collect certain information automatically, including, but not limited to, original message language, target language, character count, and other diagnostic data.
We may also collect information that Your browser sends whenever You visit our Website.
We use Cookies and similar tracking technologies to track the activity on Our Service and store certain information. Tracking technologies used are beacons, tags, and scripts to collect and track information and to improve and analyze Our Service. The technologies We use may include:
Cookies or Browser Cookies. A cookie is a small file placed on Your Device. You can instruct Your browser to refuse all Cookies or to indicate when a Cookie is being sent. However, if You do not accept Cookies, You may not be able to use some parts of our Service. Unless you have adjusted Your browser setting so that it will refuse Cookies, our Service may use Cookies.
Flash Cookies. Certain features of our Service may use local stored objects (or Flash Cookies) to collect and store information about Your preferences or Your activity on our Service. Flash Cookies are not managed by the same browser settings as those used for Browser Cookies. For more information on how You can delete Flash Cookies, please read "Where can I change the settings for disabling, or deleting local shared objects?" available at https://helpx.adobe.com/flash-player/kb/disable-local-shared-objects-flash.html#main_Where_can_I_change_the_settings_for_disabling__or_deleting_local_shared_objects_
Web Beacons. Certain sections of our Service and our emails may contain small electronic files known as web beacons (also referred to as clear gifs, pixel tags, and single-pixel gifs) that permit the Company, for example, to count users who have visited those pages or opened an email and for other related website statistics (for example, recording the popularity of a certain section and verifying system and server integrity).
Cookies can be "Persistent" or "Session" Cookies. Persistent Cookies remain on Your personal computer or mobile device when You go offline, while Session Cookies are deleted as soon as You close Your web browser. You can learn more about cookies here: Cookies by TermsFeed Generator.
We use both Session and Persistent Cookies for the purposes set out below:
Necessary / Essential Cookies
Type: Session Cookies
Administered by: Us
Purpose: These Cookies are essential to provide You with services available through the Website and to enable You to use some of its features. They help to authenticate users and prevent fraudulent use of user accounts. Without these Cookies, the services that You have asked for cannot be provided, and We only use these Cookies to provide You with those services.
Cookies Policy / Notice Acceptance Cookies
Type: Persistent Cookies
Administered by: Us
Purpose: These Cookies identify if users have accepted the use of cookies on the Website.
Functionality Cookies
Type: Persistent Cookies
Administered by: Us
Purpose: These Cookies allow us to remember choices You make when You use the Website, such as remembering your login details or language preference. The purpose of these Cookies is to provide You with a more personal experience and to avoid You having to re-enter your preferences every time You use the Website.
For more information about the cookies we use and your choices regarding cookies, please visit our Cookies Policy or the Cookies section of our Privacy Policy.
The Company may use Personal Data for the following purposes:
To provide and maintain our Service, including to monitor the usage of our Service.
To manage Your Account: to manage Your registration as a user of the Service. The Personal Data You provide can give You access to different functionalities of the Service that are available to You as a registered user.
For the performance of a contract: the development, compliance and undertaking of the purchase contract for the products, items or services You have purchased or of any other contract with Us through the Service.
To contact You: To contact You by email, telephone calls, SMS, or other equivalent forms of electronic communication, such as a mobile application's push notifications regarding updates or informative communications related to the functionalities, products or contracted services, including the security updates, when necessary or reasonable for their implementation.
To provide You with news, special offers and general information about other goods, services and events which we offer that are similar to those that you have already purchased or enquired about unless You have opted not to receive such information.
To manage Your requests: To attend and manage Your requests to Us.
For business transfers: We may use Your information to evaluate or conduct a merger, divestiture, restructuring, reorganization, dissolution, or other sale or transfer of some or all of Our assets, whether as a going concern or as part of bankruptcy, liquidation, or similar proceeding, in which Personal Data held by Us about our Service users is among the assets transferred.
For other purposes: We may use Your information for other purposes, such as data analysis, identifying usage trends, determining the effectiveness of our promotional campaigns and to evaluate and improve our Service, products, services, marketing and your experience.
We may share Your personal information in the following situations:
With Service Providers: We may share Your personal information with Service Providers to monitor and analyze the use of our Service, to contact You.
For business transfers: We may share or transfer Your personal information in connection with, or during negotiations of, any merger, sale of Company assets, financing, or acquisition of all or a portion of Our business to another company.
With Affiliates: We may share Your information with Our affiliates, in which case we will require those affiliates to honor this Privacy Policy. Affiliates include Our parent company and any other subsidiaries, joint venture partners or other companies that We control or that are under common control with Us.
With business partners: We may share Your information with Our business partners to offer You certain products, services or promotions.
With other users: when You share personal information or otherwise interact in the public areas with other users, such information may be viewed by all users and may be publicly distributed outside.
With Your consent: We may disclose Your personal information for any other purpose with Your consent.
The Company will retain Your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use Your Personal Data to the extent necessary to comply with our legal obligations (for example, if we are required to retain your data to comply with applicable laws), resolve disputes, and enforce our legal agreements and policies.
The Company will also retain Usage Data for internal analysis purposes. Usage Data is generally retained for a shorter period of time, except when this data is used to strengthen the security or to improve the functionality of Our Service, or We are legally obligated to retain this data for longer time periods.
Your information, including Personal Data, is processed at the Company's operating offices and in any other places where the parties involved in the processing are located. It means that this information may be transferred to — and maintained on — computers located outside of Your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from Your jurisdiction.
Your consent to this Privacy Policy followed by Your submission of such information represents Your agreement to that transfer.
The Company will take all steps reasonably necessary to ensure that Your data is treated securely and in accordance with this Privacy Policy and no transfer of Your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of Your data and other personal information.
If the Company is involved in a merger, acquisition or asset sale, Your Personal Data may be transferred. We will provide notice before Your Personal Data is transferred and becomes subject to a different Privacy Policy.
Under certain circumstances, the Company may be required to disclose Your Personal Data if required to do so by law or in response to valid requests by public authorities (e.g. a court or a government agency).
The Company may disclose Your Personal Data in the good faith belief that such action is necessary to:
Comply with a legal obligation
Protect and defend the rights or property of the Company
Prevent or investigate possible wrongdoing in connection with the Service
Protect the personal safety of Users of the Service or the public
Protect against legal liability
The security of Your Personal Data is important to Us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While We strive to use commercially acceptable means to protect Your Personal Data, We cannot guarantee its absolute security.
Our Service does not address anyone under the age of 13. We do not knowingly collect personally identifiable information from anyone under the age of 13. If You are a parent or guardian and You are aware that Your child has provided Us with Personal Data, please contact Us. If We become aware that We have collected Personal Data from anyone under the age of 13 without verification of parental consent, We take steps to remove that information from Our servers.
If We need to rely on consent as a legal basis for processing Your information and Your country requires consent from a parent, We may require Your parent's consent before We collect and use that information.
Our Service may contain links to other websites that are not operated by Us. If You click on a third party link, You will be directed to that third party's site. We strongly advise You to review the Privacy Policy of every site You visit.
We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.
We may update Our Privacy Policy from time to time. We will notify You of any changes by posting the new Privacy Policy on this page.
We will let You know via email and/or a prominent notice on Our Service, prior to the change becoming effective and update the "Last updated" date at the top of this Privacy Policy.
You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.
If you have any questions about this Privacy Policy, You can contact us:
By email: dev@ritabot.gg
By visiting this page on our website: https://discord.gg/invite/7yYUWruQp6
The following Interpretations and Definitions apply to the following Policies
Terms of Service (TOS)
S.A.L.T.S Policy
Privacy Policy
Refund Policy
The words of which the initial letter is capitalized have meanings defined under the following conditions. The following definitions shall have the same meaning regardless of whether they appear in the singular or in plural.
For the purposes of these Terms Of Service/s:
Account means a unique account created in the service Discord used to access our Service.
BITA refers to the BETA Version of RITA. Unless otherwise stated BITA shall be bound by the same Policies, Conditions, Processes and TOS as RITA. BETA is an invite only closed testing platform used to test new functions for RITA and operated under an NDA.
Company (referred to as either "the Company", "We", "Us" or "Our" in this Agreement) refers to RitaBot.
Cookies are small files that are placed on Your computer, mobile device or any other device by a website, containing the details of Your browsing history on that website among its many uses.
Country refers to: United States, the EU, and more.
Device means any device that can access the Service such as a computer, a cellphone or a digital tablet.
Discord refers to Discord LLC's service, "Discord" (not associated with RitaBot or our Service.)
Features are defined as a single or group of functions, commands, tools or resources provided by RitaBot for use on or with our Service.
Language pairs is defined as the combination of source language and destination language of a translation request sent via our service.
ML is defined as RMT's Proprietary Machine Learning Translation Engine
Personal Data is any information that relates to an identified or identifiable individual.
Privacy Policy as defined Here.
Refund Policy as defined Here.
RitaBot, RITA/Rita, RitaBot Dev Team are all references to the Services provided.
RitaBot: The Company that owns all assets associate with RITA and her Features and Services
RITA/Rita: Is the term used to define the Discord Bot, pronouns are also used in conjunction, these are She/Her
RitaBot Dev Team: The Owners of RITA and the Development Team Associated with Her
RMT: Refers to RITA Management Team, Also known as RitaBot Dev Team.
RMS: Refers To the RITA Management Server. This is the Discord Server where RITA is managed from and where user support is provided.
S.A.L.T.S as defined Here.
Service refers to the translation services provided by RitaBot.
Service Provider means any natural or legal person who processes the data on behalf of the Company. It refers to third-party companies or individuals. employed by the Company to facilitate the Service, to provide the Service on behalf of the Company, to perform services related to the Service or to assist the Company in analyzing how the Service is used.
TOS/Terms of Service as defined Here.
Usage Data refers to data collected automatically, either generated by the use of the Service or from the Service infrastructure itself (for example, the duration of a page visit).
Website refers to RitaBot, accessible from https://ritabot.gg
You, User, They, TRIAL User, Subscriber, Subscription Owner: means the individual accessing or using the Service, or the company, or other legal entity on behalf of which such individual is accessing or using the Service, as applicable.
In Effect Fom: May 01, 2023 / Last updated: April 05, 2023
Refund Policy - Document Version 2 (In Effect May 01, 2023 > Current)
This Refund Policy describes our policies regarding the handling of refunds in general and does not serve as a legal base, nor is it approved by professionals. It is used to lay down the foundations for any decision made upon requests. Any point listed here might be a reason for permitted initiations of any refund.
The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located Here.
Refunds for payments may be issued when the user requests it and one of the following requirements is met:
it's the first payment and the user requests a refund on the same day (Usage Exception Applies)
it's a monthly recurring payment and the user requests a refund within a three day period (Usage Exception Applies)
it's an annual recurring payment and the user requests a refund within a seven day period (Usage Exception Applies)
A major premium feature was removed and the user bought the tier specifically because of that feature
Users who subscribe via Patreon are charged as soon as you sign up. Patrons' payments are recurring on the 1st of every month after that. This means you are charged for the month (January, February ect), not a month (30 Days) of access.
Each charge for the month gives them membership access for that month. For example,
You subscribe to RITA on the 1st January, this payment gives you access throughout the rest of January. Your next payment is 1st February then 1st March ect ect.
You subscribe to RITA on the 15th January, this payment gives you access throughout the rest of January. Your next payment is 1st February then 1st March ect ect.
Listed below are other possible reasons that might permit a full or prorated refund.
Any kind of unauthorized transaction that was not undertaken on your behalf but financially affects you.
A situation in which you are not successfully receiving or are unable to access promised premium features.
Service uptime of less than 80% (24 Days in a rolling 30 day period) due to maintenance, takedown, core functionality issues or other services under the direct control of RitaBot or the Rita Bot Dev Team.
All/Any of the reasons above require viable proof to be accepted as possible inquiries for the initiation of a refund.
Below listed are situations in which any kind of refund will not permit a full or prorated refund.
Any situation in which you actively or passively forgot to cancel your ongoing subscription, and it's passed the subscription exclusion timeframe listed above.
Downtime caused by 3rd Party Service Providers, Including but not limited to, Discord, Heroku, Paypal, Stripe, PebbleHost, Domain Controllers and DNS Providers.
You are a Patreon user and have had the second payment of a recurring subscription taken/renewed on the 1st of the month. As this is Defined during the purchase process, regardless of the date of the first payment you are charged for the month (January, February ect) not a month (30 Days).
Please note that all refund requests are handled on a case by case basis, however, the reasons above may prohibit responses to refund requests.
IF you have activated RITA, defined in our SALTS Policy #Activation, and have used RITA service with a Character count exceeding 10,000 Character, you will NOT be eligible for a refund under any circumstance. to see your character count type "!translate stats" in your server.
All Donations, Made on any of the accepted payment platform we use are Non-Refundable with the exceptions of,
Any kind of unauthorized transaction that was not undertaken on your behalf but financially affects you.
All/Any of the reasons above require viable proof to be accepted as possible inquiries for the initiation of a refund.
If you choose to or threaten to chargeback, we reserve the right to ban and/or blacklist you from the bot. This includes but is not limited to:
Immediate termination of service
Permanent and non reversavble ban
Support requestswill not be answered
Guild ID is excluded from the usage of our service indefinitely
Performing a chargeback on behalf of the payment processor your transaction was handled through, without contacting or attempting to contact RitaBot, In most situations means we can, and will, fight such cases to dispute the chargeback.
Financial Transactions and Decisions are handled by a single member of staff, Responses to such requests will be given within 72 hours, between 8 am and 9 pm GMT, Excluding bank holidays and public holidays. We still require a comprehensible explanation of the situation and never guarantee a refund, except as listed in the subscription exclusion timeframe listed above. Partial refunds might be issued for annual payments under special circumstances.
Refunds are never issued if you have broken our Terms of Service and therefore lost access to certain or all features.
If you believe your situation is viable for a refund you may wish to contact us via one of the ways listed below.
From the email address related to the Discord account that is affected if accessible. Just send us a descriptive message to payment@ritabot.gg
On our Discord support server with the Discord account that is affected if accessible.
In any private ticket/message with a staff member from the RitaBot team.
Upcoming Changes to RITA and what we have been doing.
PLEASE NOTE: This Update was accurate at the time of sharing. Please refer to our Support documentation to ensure accurate and up-to-date information is known, If you have any questions or concerns please join our Discord Server and someone will assist.
That's it for now, but we will have some more info for you when we can. and if you want to check out all the changes made, dive into our change logs over in Version History
From all the Development Team at RITA, See you soon.
Upcoming Changes to RITA and what we have been doing.
PLEASE NOTE: This Update was accurate at the time of sharing. Please refer to our Support documentation to ensure accurate and up-to-date information is known, If you have any questions or concerns please join our Discord Server and someone will assist.
Once a user hit these limits, no suspension activity took place however we would enquire about the usage to ensure validity, Once we knew it was all hunky dory we would not inquire again.
Ex. You are a "Casual" Plan user, Your server has used 300k characters since the start of the month.
You use 3 languages on your server, English, German and Russian.
You translate to en -> ru and en -> de. German [de] will use Google whilst Russian [ru] will use ML. This is because German is not Optimised and would provide a poor-quality of translation.
Please see #optimised-langaugesfor a list of Support Languages.
If we have used the wrong flag we apologise, Were only matching language codes from Dicords Supported Emoji list. Please let us know and we will update it.
Assamese
as
:flag_as:
Aymara
ay
Bambara
bm
:flag_bm:
Dhivehi
dv
Ewe
ee
:flag_ee:
Guarani
gn
:flag_gn:
Javanese
jv or jw
Kinyarwanda
rw
:flag_rw:
Lingala
ln
Oriya
or
Oromo
om
:flag_om:
Quechua
qu
Sanskrit
sa
Tatar
tt
:flag_tt:
Tigrinya
ti
Tsonga
ts
Turkmen
tk
:flag_tk:
Twi (Akan)
ak
Uyghur
ug
RITA - BLUE
RITA - YELLOW
BITA - RED
RITA - PURPLE
You can invite RITA Blue by clicking Here or clicking on RITA’s Icon & click “Add to server”
These Policies take effect as of May 01, 2023, Until then the preceding version are still in effect.
Thats it for now, but we will have some more info for you when we can. and if you want to check out all the changes made, dive into our change logs over in Version History
From all the Development Team at RITA, See you soon.
In Effect Fom: May 01, 2023 / Last updated: April 05, 2023
Privacy Policy - Document Version 3 (In Effect May 01, 2023 > Current)
This Privacy Policy describes Our policies and procedures on the collection, use and disclosure of Your information when You use the Service and tells You about Your privacy rights and how the law protects You.
We use Your Personal data to provide and improve the Service. By using the Service, You agree to the collection and use of information in accordance with this Privacy Policy.
We do not Sell or Provide any Personal Data collected, as defined below, to any 3rd Party Company.
The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located Here.
While using Our Service, We may ask You to provide Us with certain personally identifiable information that can be used to identify You and provide your access to the Service. Personally identifiable information may include, but is not limited to: Discord Account ID's, Channel ID's, Server ID's and more.
While using Our Service, We may collect anonymized translation data. This is used to help train our in-house Machine Learning translation model. The data collected is comprised of the following values;
Source Language
Destination Language
Content of Message sent
Content of Message received after translation
This data cannot be linked to the source server. All identifiable values such as Guild ID, User ID, Username, Channel ID and other identifiable data found within the Discord API is not collected. This data is stored for a period of 60 days, or when the collection files (All possible Language Pairs) reach 200GB, which ever is sooner. Data is automatically overridden and non-recoverable.
As this data is anonymized it is not possible to request this data as part of a Subject Access request, more commonly known as "Request My Data". If you desire not to be part of this data collection you may open a ticket in order for us to find a solution for you.
Usage Data is collected automatically when using the Service.
Usage Data in relation to our Website may include information such as Your Device's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that You visit, the time and date of Your visit, the time spent on those pages, unique device identifiers and other diagnostic data.
When You access the Service on Discord, We may collect certain information automatically, including, but not limited to, original message language, target language, character count, and other diagnostic data.
We may also collect information that Your browser sends whenever You visit our Website.
We use Cookies and similar tracking technologies to track the activity on Our Service and store certain information. Tracking technologies used are beacons, tags, and scripts to collect and track information and to improve and analyze Our Service. The technologies We use may include:
Cookies or Browser Cookies. A cookie is a small file placed on Your Device. You can instruct Your browser to refuse all Cookies or to indicate when a Cookie is being sent. However, if You do not accept Cookies, You may not be able to use some parts of our Service. Unless you have adjusted Your browser setting so that it will refuse Cookies, our Service may use Cookies.
Flash Cookies. Certain features of our Service may use local stored objects (or Flash Cookies) to collect and store information about Your preferences or Your activity on our Service. Flash Cookies are not managed by the same browser settings as those used for Browser Cookies. For more information on how You can delete Flash Cookies, please read "Where can I change the settings for disabling, or deleting local shared objects?" available at https://helpx.adobe.com/flash-player/kb/disable-local-shared-objects-flash.html#main_Where_can_I_change_the_settings_for_disabling__or_deleting_local_shared_objects_
Web Beacons. Certain sections of our Service and our emails may contain small electronic files known as web beacons (also referred to as clear gifs, pixel tags, and single-pixel gifs) that permit the Company, for example, to count users who have visited those pages or opened an email and for other related website statistics (for example, recording the popularity of a certain section and verifying system and server integrity).
Cookies can be "Persistent" or "Session" Cookies. Persistent Cookies remain on Your personal computer or mobile device when You go offline, while Session Cookies are deleted as soon as You close Your web browser. You can learn more about cookies here: Cookies by TermsFeed Generator.
We use both Session and Persistent Cookies for the purposes set out below:
Necessary / Essential Cookies
Type: Session Cookies
Administered by: Us
Purpose: These Cookies are essential to provide You with services available through the Website and to enable You to use some of its features. They help to authenticate users and prevent fraudulent use of user accounts. Without these Cookies, the services that You have asked for cannot be provided, and We only use these Cookies to provide You with those services.
Cookies Policy / Notice Acceptance Cookies
Type: Persistent Cookies
Administered by: Us
Purpose: These Cookies identify if users have accepted the use of cookies on the Website.
Functionality Cookies
Type: Persistent Cookies
Administered by: Us
Purpose: These Cookies allow us to remember choices You make when You use the Website, such as remembering your login details or language preference. The purpose of these Cookies is to provide You with a more personal experience and to avoid You having to re-enter your preferences every time You use the Website.
For more information about the cookies we use and your choices regarding cookies, please visit our Cookies Policy or the Cookies section of our Privacy Policy.
The Company may use Personal Data for the following purposes:
To provide and maintain our Service, including to monitor the usage of our Service.
To manage Your Account: to manage Your registration as a user of the Service. The Personal Data You provide can give You access to different functionalities of the Service that are available to You as a registered user.
For the performance of a contract: the development, compliance and undertaking of the purchase contract for the products, items or services You have purchased or of any other contract with Us through the Service.
To contact You: To contact You by email, telephone calls, SMS, or other equivalent forms of electronic communication, such as a mobile application's push notifications regarding updates or informative communications related to the functionalities, products or contracted services, including the security updates, when necessary or reasonable for their implementation.
To provide You with news, special offers and general information about other goods, services and events which we offer that are similar to those that you have already purchased or enquired about unless You have opted not to receive such information.
To manage Your requests: To attend and manage Your requests to Us.
For business transfers: We may use Your information to evaluate or conduct a merger, divestiture, restructuring, reorganization, dissolution, or other sale or transfer of some or all of Our assets, whether as a going concern or as part of bankruptcy, liquidation, or similar proceeding, in which Personal Data held by Us about our Service users is among the assets transferred.
For other purposes: We may use Your information for other purposes, such as data analysis, identifying usage trends, determining the effectiveness of our promotional campaigns and to evaluate and improve our Service, products, services, marketing and your experience.
We may share Your personal information in the following situations:
With Service Providers: We may share Your personal information with Service Providers to monitor and analyze the use of our Service, to contact You.
For business transfers: We may share or transfer Your personal information in connection with, or during negotiations of, any merger, sale of Company assets, financing, or acquisition of all or a portion of Our business to another company.
With Affiliates: We may share Your information with Our affiliates, in which case we will require those affiliates to honor this Privacy Policy. Affiliates include Our parent company and any other subsidiaries, joint venture partners or other companies that We control or that are under common control with Us.
With business partners: We may share Your information with Our business partners to offer You certain products, services or promotions.
With other users: when You share personal information or otherwise interact in the public areas with other users, such information may be viewed by all users and may be publicly distributed outside.
With Your consent: We may disclose Your personal information for any other purpose with Your consent.
The Company will retain Your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use Your Personal Data to the extent necessary to comply with our legal obligations (for example, if we are required to retain your data to comply with applicable laws), resolve disputes, and enforce our legal agreements and policies.
The Company will also retain Usage Data for internal analysis purposes. Usage Data is generally retained for a shorter period of time, except when this data is used to strengthen the security or to improve the functionality of Our Service, or We are legally obligated to retain this data for longer time periods.
Your information, including Personal Data, is processed at the Company's operating offices and in any other places where the parties involved in the processing are located. It means that this information may be transferred to — and maintained on — computers located outside of Your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from Your jurisdiction.
Your consent to this Privacy Policy followed by Your submission of such information represents Your agreement to that transfer.
The Company will take all steps reasonably necessary to ensure that Your data is treated securely and in accordance with this Privacy Policy and no transfer of Your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of Your data and other personal information.
If the Company is involved in a merger, acquisition or asset sale, Your Personal Data may be transferred. We will provide notice before Your Personal Data is transferred and becomes subject to a different Privacy Policy.
Under certain circumstances, the Company may be required to disclose Your Personal Data if required to do so by law or in response to valid requests by public authorities (e.g. a court or a government agency).
The Company may disclose Your Personal Data in the good faith belief that such action is necessary to:
Comply with a legal obligation
Protect and defend the rights or property of the Company
Prevent or investigate possible wrongdoing in connection with the Service
Protect the personal safety of Users of the Service or the public
Protect against legal liability
The security of Your Personal Data is important to Us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While We strive to use commercially acceptable means to protect Your Personal Data, We cannot guarantee its absolute security.
Our Service does not address anyone under the age of 13. We do not knowingly collect personally identifiable information from anyone under the age of 13. If You are a parent or guardian and You are aware that Your child has provided Us with Personal Data, please contact Us. If We become aware that We have collected Personal Data from anyone under the age of 13 without verification of parental consent, We take steps to remove that information from Our servers.
If We need to rely on consent as a legal basis for processing Your information and Your country requires consent from a parent, We may require Your parent's consent before We collect and use that information.
Our Service may contain links to other websites that are not operated by Us. If You click on a third party link, You will be directed to that third party's site. We strongly advise You to review the Privacy Policy of every site You visit.
We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.
We may update Our Privacy Policy from time to time. We will notify You of any changes by posting the new Privacy Policy on this page.
We will let You know via a prominent notice on Our Service or Discord Announcement, prior to the change becoming effective and update the "Last updated" date at the top of this Privacy Policy.
You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page or the date provided on the notice.
All changes to this policy can be found below
If you have any questions about this Privacy Policy, You can contact us:
By email: dev@ritabot.gg
By visiting this page on our website: https://discord.gg/invite/7yYUWruQp6