RitaBot Discord Translator

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

Things you can do with Rita

• 🗣️ Speak with others across multiple channels using the /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

How much does it cost?

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 the Dashboard or by reading Avalaible Plans

How to intall ?

To install, you can follow the guide Quick setup steps

The Owners

Development & Core Staff

Bot & Community Helpers

Major Changes

Dev only Command handler has been added in to enable fast changes to command restrictions.

Bug Fixes

• Lots of little things, nothing of consequence.

Command Changes

• !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.

Database Changes

• A new column has been added to manage blacklisting and Warning, backwards compatible to all previous versions.

Misc. Changes

• 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.

Change Log

• 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.

Prefix and Commands

The bot’s default prefix is !tr, or !translate - All commands must start with this prefix for the bot to process them.

You can also use discord slash commands to interact with the bot.

Command structure

[prefix] + [main command] + [parameters]

For Example:

!translate help modules

!tr help modules

!tr help

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.

Command

!tr this: [msg] - Translates to default server language

!tr this to [lang]: [msg] - detects language and translates to your to langugae

Parameters

• to [lang] - Defaults to server default language

• to [lang, lang, ...] - Translates to multiple languages

• from [lang] - Defaults to automatic detection

Examples

!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?

Translates last message chain(s) in channel. A chain is a collection of messages by the same author, to keep things simple.

Commands

!tr last

!tr last [n] to [lang] from [lang]

Parameters

• 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

Examples

!tr last 2

!tr last to english

!tr last to english, german, french

!tr last -6 to english from german

!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.

What is RITA and who are we?

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 .

Why did you make Rita?

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.

The history of Rita?

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.

Why RITA and what does it stand for?

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.

For support, please visit us at our If you wish to email us about payments, please use

Inital Release

V-1

V-2

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.

Help

!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.

Links

!tr invite - Creates an invite link for the bot so other can use it, i would not recommend using this command.

Supported Languages

!tr list - Lists all supported languages the bot can use.

Version

!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.

Parameters

** [version]** - Version number.

Tasks

!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.

Donate

!tr donate oc - Donation link for open Collective.

!tr donate github - Donation link for GitHub.

Prefix

!tr prefix [prefix] - Sets custom bot prefix

parameters

** [prefix] - custom prefix**

ID Info

!tr id - Shows various ID info

Inital Release

### 1.3.12-0
Date: 30/10/22
User: Qjuh
> ----------
>>> auto.js, send.js
* Added support for stickers being sent as attachments for cross-channel translation tasks
* Added the error log for empty message again, as it should be fixed now

>>> translate.js
* Fixed translation throwing empty message errors in blockChain mode

>>> events.js
* Fixed joining of Threads to only try threads we didn't join yet

Inital Release

### 1.3.21-0
Date: 8/12/22
User: Zycore
> ----------
>>> db.js
* Created case 
    db.updateTable (action, id, columnName, value, _cb)
        action = (server, stats, reset)
    db.increaseCount (action, column, id)
        action = (server, stats)
    db.sumCharUsed (action, _cb)
        action = (google, ml)

>>> Core Code Files
* Changed db.updateServerTable > db.updateTable
* Changed db.updateStatsTable > db.updateTable
* Changed db.increaseServerCount > db.increaseCount
* Changed db.increaseStatsCount > db.increaseCount

V-1

### 1.3.21-1
Date: 9/12/22
User: Zycore
> ----------
>>> choose_server.js
* Removed mention of Ko-Fi from prompt.

Inital Release

### 1.3.11-0
Date: 30/10/22
User: Qjuh
> ----------
>>> check.js (both /commands and /slashcommands)
* Added whitelist status and applications.commands scope to bot/server check
* Implemented `/check channel` and `!tr check channel` command

>>> pause.js
* Fixed display of paused servers

>>> auto.js
* Fixed ForumChannels translating although env var is not set

>>> db.js
* Fixed paused status getting set to false although subscription has a value of true

>>> interaction.reply.js
* Fixed usage of editReply if reply was deferred before

>>> send.js
* Commented logging of empty message errors because they're annoying atm and we know the reason

>>> slashcommands/settings.js
* Fixed usage of servers table from server_obj in `/settings show` command

Inital Release

### 1.3.17-0
Date: 21/11/22
User: Qjuh
> ----------
>>> commands.js
* New file for checking command permissions, sub-only commands, tier-restricted commands and potentially more
* Moved list of commands from args.js to commands.js

>>> args.js
* Calls commands.js to determine what function to call

>>> permissions.js, auth.js
* Added auth.helperID and use it to populate the BitField with BotHelper value
* Fixed GuildAdmin using BitField value of GlobalChanManager by accident

Inital Release

### 1.3.10.0
Date: 27/10/22
User: Zycore
> ----------
>>> permission.js
* new file, playing around with BitField

>>> events.js
* saved supportguild to client, but im not sure if this will run every action and thus leak or if it will only store once.

>>> message.js
* if a command is run, then the BitField value is added ot data.BitField

>>> misc.js, args.js
* Test command

Inital Release

### 1.3.15-0
Date: 13/11/22
User: Qjuh
> ----------
>>> db.js
* added subscriptions to server_obj
* refactored building of server_obj to do three seperate loops for servers, stats and subscriptions instead of nested loops
* removed global property from server_obj as it's not used anymore
* removed .paused from `server_obj[].servers` as its now accessible from subscriptions directly
* changed `updatePaused()` to only update subscriptions and not servers anymore (see above)

>>> translate.react.js, translate.js, message.js
* Removed mentions of `server_obj.global`

>>> translate.react.js, pause.js, message.js, slashcommand.js
* Moved .paused check from `server_obj[].servers` to `server_obj[].subscriptions`

>>> send.js
* Refined check for empty message error to not apply for stickers/attachments sent in same channel translations

Major Changes

• 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.

Bug Fixes

• 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

Command Changes

• !tr stats global / !tr stats server now show message based stats, take a look.

Database Changes

• It working so were not going to touch it. (Well Zycore wont)

Misc Changes

• 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.

Inital Release

### 1.3.7-0
Date: 19/10/22
User: Qjuh
> ----------
>>> message.js, misc.js, settings.js, mod.js, sql_execute.js, stats.js, bot2bot.js, announce.js, debug.js, embed.js, prefix.js, purge.js, react.js, sub.js, translate.auto.js, translate.group_auto.js, translate.stop.js, translate.tasks.js, check.js, create.channel.js, help.js, invite.js, pause.js, command.send.js, dev.send.js, send.js
* Attached `isAdmin`, `isChanManager`, `isGlobalChanManager`, `isDev`, `isGuildOwner` and `isBotOwner` to `data` instead of the cached `data.message`
* Removed `data.message.sourceID` as it was only ever used as fallback in cases when `data.message.guild.id` would be defined anyway
* Removed `data.message.roleColor` as it wasn't used anywhere

>>> db.js, dbInit.js, dbModels,js, dbServersModel.js, dbStatsModel.js, dbSubscriptionsModel.js, dbTasksModel.js
* Split Sequelize Models for all tables into seperate files, as well as initialization

>>> db.js
* Fixed a few undefined variables

>>> args.js, translate.last.js, translate.react.js, translate.this.js, auto.js, translate.js
* Added some more `async/await` for even more helpful stacktraces

>> Error's
List error found in console, if any.

V-1

### 1.3.7-1
Date: 19/10/22
User: Qjuh
> ----------
>>> translate.js
* Fixed `catch` statement in `sendData` function

Inital Release

### 1.3.26-0
Date: 12/02/23
User: Qjuh 
> ----------
>>> eject.js
* Remove abus reference from eject and warn

V-1

### 1.3.26-1
Date: 14/02/23
User: Qjuh 
> ----------
>>> send.js
* Fixed embed sending with only translated fields

V-2

### 1.3.26-2
Date: 21/02/23
User: Qjuh 
> ----------
>>> translate.stop.js, db.js, send.js
* Refactoring of various variables

V-3

### 1.3.26-3
Date: 21/02/23
User: Qjuh 
> ----------
>>> group.js
* Fixed `/group link` subcommand missing reply column

V-4

### 1.3.26-4
Date: 24/02/23
User: Qjuh 
> ----------
>>> choose_server.js, helpers.js, events.js
* Added automatic tasklimit increase on role change

>>> events.js
* Bug fixed to `removeTask` 

Inital Release

### 1.3.18-0
Date: 24/11/22
User: Qjuh
> ----------
>>> shard.js, commands.js
* New command `!tr shard restart {shardId}` to restart a specific shard

>>> misc.js
* Fixed `!tr shards` to list shard ids starting from 1 instead of 0 to be in line with `!tr check` and `!tr proc`

V-1

### 1.3.18-1
Date: 3/12/22
User: Qjuh
> ----------
>>> commands.js
* Revamped permission checks to allow for multiple needed permissions as well as seperate alternatives, like being BotHelper or being Admin with Casual Tier subscription

>>> permissions.js
* BotHelper permission is assigned by checking for BotHelper role on support server now
* Export RITAPermissions Flags array to be used in other files

>>> auth.js
* Read BotHelper role ID from .env with hardcoded fallback

Inital Release

### 1.3.28-0
Date: 09/03/23
User: Artanis, Qjuh
> ----------
>>> Core Code Files
* Refactoring of variables for `getInfo`
* Edit translation incorporated using ML
* Fixed a embed off bug

V-1

### 1.3.28-1
Date: 10/03/23
User: Artanis
> ----------
>>> Core BOT code
* Prettified some methods, moved translation split to after translation to maintain a coherent translation

>>> events.js
* Fixed a bug with message deletion

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.

Copyright (c) 2019 RITA

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.

Copyright (c) 2017 Aziz

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.

Please review our S.A.L.T.S Policy for more information on Availability, Limitations and Restrictions.

Groups channels using Automatic Channel Translation in a simple, easy-to-manage manner.

Command

You can use slash commands like /group create in order to create groups or use the commands listed bellow.

Video with slash command

Legacy commands

• !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

Parameters

• [GROUPNAME] refers to the group name you give to the group (can check groups with !tr group list)

Examples

Group Creation

Group List

Group Link

Group Unlink

Group Delete

Notes

• 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

Major Changes

• 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.

Bug Fixes

• !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.

Command Changes

• !tr react on/off now turns on and off flag reactions.

Database Changes

• 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

Misc. Changes

• Sooooooo Many spelling mistakes corrected that it would be too many to list here.

• Help Menu updated with new commands.

Major Changes

• 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.

Bug Fixes

• Color now working in Embed on and takes user role color.

• Stop command for @user has now been fixed

Command Changes

• 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.

Database Changes

• Validation Checks added at startup to avoid Blacklist and Stats SQL Errors

Misc. Changes

• 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

Inital Release

V-1

Inital Release

V-1

V-2

Inital Release

V-1

V-2

V-3

BETA TESTERS WANTED

How many do we need?

Are there any restrictions?

What do I need to do?

What next?

Will I need to set everything up again?

What do I have to do as a BETA Tester?

Are there any downsides?

What's in it for me?

But.......

Inital Release

V-1

V-2

A Year in Review - RITA 2022

RITA Message Statistics for 2022:

RITA Artificial Intelligence Machine Learning (ML) Work In Progress

RITA Team and Server Updates for 2022

Change Log

• 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-watchhave 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.

Interpretation and Definitions

The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located .

Disclaimer

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

Proprietary Rights

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.

Availability

• 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.

Server / Guild Data

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 . This information is only used for analytics and can not be tracked back to You.

S.A.L.T.S

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 for more information.

Wait, what, I've missed something?

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 .

How do I Subscribe?

You can do this in a few ways. You can purchase from or . For info and step by step guide check out.

I've Subscribed, Now what?

Head to and type `!tr sub` to get started... What are you waiting for?.

Something has gone wrong, it didn't work!

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.

Inital Release

V-1

V-2

Inital Release

No Public Change Log

V-1

### 1.3.19-1
Date: 3/12/22
User: Qjuh
> ----------
>>> commands.js
* Added some perms in that were missing.

>>> misc.js, stats.js
* Fixed object when no active sub
* now shows bot value

>>> choose_server.js, sub.js
* now saves bot value

>>> check.js
* Fixed error with object missing table

>>> db.js
* Bot value is save in DB with sub

>>> events.js
* client.user.id now stored in config

V-2

### 1.3.19-2
Date: 8/12/22
User: Qjuh
> ----------
>>> translate.tasks.js, slashcommands/.../tasks.js
* Added `/tasks [channelId]` as global command needing ManageChannels permission per default
* Added `/tasks {server|channnel|me} [id]` as support guild only dev-commands needing Administrator permission per default (can be changed in server setttings->integration though)
* Added page number in footer of paginated embeds

>>> db.js
* Simplified getTasks() function used by `!tr tasks` and `/tasks` a bit

>>> slashcommands/.../translate.js, slashcommands/.../group.js, slashcommands/.../check.js
* Minor cleanup

>>> commands.js, permissions.js
* Added a dev-only command to list all commands and their needed permissions
* Added a `plaintext()` function in permissions.js to turn BitField into their readable names again

Inital Release

### 1.3.5-0
Date: 17/10/22
User: Zycore
> ----------
>>> .env File
* Defined `DISCORD_BOT_DEV_ID` in env file

>>> message.js
* Changed variable `message.isOwner` to `message.isGuildOwner`

>>> events.js
* Added in `process.env.DISCORD_BOT_DEV_ID = process.env.DISCORD_BOT_DEV_ID || "0";` to load variables on boot.

>>> translate.js
* Updated with arts new code

>>> auth.js
* Removed `exports.donation` as it was not used
* Removed `exports.changelog` as it was not used
* Removed `devID` and set variable in `.env` file
* Set fallback for if `DISCORD_BOT_DEV_ID` is missing and will use `DISCORD_BOT_OWNER_ID`

>>> settings.js
* Removed `listservers` command from settings.js
* Removed `listusers` command from settings.js

>>> misc.js
* Removed `costcalc` commands and variables
* Removed Mentions of ko-fi from responces

>>> join.js, invalid.js, choose_server
* Removed Mentions of ko-fi from responces

V-1

### 1.3.5-1
Date: 17/10/22
User: Zycore
> ----------
>>> translate.js
* New `translate.js` code

>> Error's
TypeError: Cannot read properties of null (reading 'user_id')
    at Object.checkSubActive (c:..\GitHub\RitaBotBuild\src\core\helpers.js:79:24)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.subExpired (c:..\GitHub\RitaBotBuild\src\core\helpers.js:39:7)
    at async run (c:..\GitHub\RitaBotBuild\src\message.js:265:8)

V-2

### 1.3.5-2
Date: 18/10/22
User: Qjuh
> ----------
>>> message.js
* Removed `message.server` and `message.stats` being attached to cached messages

>>> profanity.js, send.js, translate.js, translate.last.js
* Changed to use `db.server_obj` instead of the now removed `data.message.server`

>>> helpers.js
* added check `if(!sub)` to account for non-subbed servers and fix the error in console `Cannot read properties of null (reading 'user_id')`

Steps to follow in order to install RITA

1. Check that your discord account is the owner of the server or an admin of the server you want RITA Bot in

2. Invite RITA in your discord server : https://ritabot.gg/invite

3. Subscribe to a RITA plan through dashboard : https://dashboard.ritabot.gg/

4. On dashboard, select the server you want to link to the subscription you've just took

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 groupor /group createand following the instructions displayed

Quick setup steps FAQ

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.

Current-server-settings

This command will display a printout of your current server settings.

!tr settings or /settings

Set custom Bot Prefix

This command will allow you to set a custom prefix for RITA in your server.

!tr prefix [prefix]

!translate prefix [prefix]

Developer Announcement Messages

This command will turn off messages from the Development team.

!tr announce [on/off]

Embedded Message Style

This command will allow you to use either embed or webhook translation Styles.

• !tr embed [on/off]

• /settings embed

Language Detection

This command will add a source Language marker to the translated text.

• !tr settings langdetect [on/off]

• /settings langdetect

Bot to Bot Translation Status

This command will allow RITA to translate messages from most bots

!tr bot2bot [on/off]

!tr help bot2bot

Tags(everyone, here and user)

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]

Parameters

none - RITA won't ignore any mentions

everyone - RITA will ignore everyone and here tags

all - RITA will ignore all mentions

Reaction Translations

This command will turn off the ability to translate a message with Country flags.

!tr react [on/off]

Auto Deletion Commands

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]

Webhook Debug Active State

This command will allow you to turn on debugging for RITA related errors in your server.

!tr debug [on/off]

!tr help debug

Reset All Settings

This command will reset all Settings to their default setting.

!tr settings reset

Inital Release

V-1

V-2

Inital Release

V-1

V-2

V-3

V-4

V-5

V-6

Inital Release

V-1

V-2

V-3

Inital Release

V-1

V-2

V-3

V-4

05/06/25 Refund, Privacy & S.A.L.T.S Policy Update

• The change to our and Policy does not constitute a Right-to-Exit unless stated, however, we will review all cases and claims on a case-by-case basis if raised.

• The change to our Policy may constitute a Right-to-Exit under the following conditions:

  • Where the request does not fall within the terms and authorisation of the updated Policy, users may request termination and refund of the subscription service equal to 1 month at the cost of the active subscription.

  • Any changes to a subscription plan, cost, payment method or billing platform constitutes acceptance of this policy change and will make any request null and void unless they fall within the terms and authorisation of the updated Policy.

  • Right-to-exit requests are limited to the scope of 3 months from the dated change of the Policy and;

    • acceptance of a right-to-exit request will result in the termination of any active subscription.

    • user subscriptions must be active at the time of this change.

• The notice must be provided to exercise a Right-to-Exit BEFORE self-cancellation of an active subscription. Cancellation of subscription prior to notice to exercise a Right-to-Exit will result in the denial of the claim.

  • Notice can be provided via our in a support ticket or by sending an email to

• Further clarification of changes can be provided upon request.

15/08/23 S.A.L.T.S Policy Update

• The change to our Policy does not constitute a Right-to-Exit.

• Further clarification of changes can be provided upon request.

01/05/23 Privacy & S.A.L.T.S Policy Update

• The change to our , and Policy's do not constitute a Right-to-Exit unless stated, however we will review all cases and claims on a case-by-case basis if raised.

• Change to soft Limits defined in 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 [email protected] 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

• 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

• The change to our and Policy does not constitute a Right-to-Exit, however we will review all cases and claims on a case by case basis if raised.

• Please email [email protected] 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

• Further clarification of changes can be provided upon request.

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.

Interpretation and Definitions

The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located .

Subscription Refunds - Exclusion Timeframe

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

Patreon Payments

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.

Other Possible Reasons

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.

Non-Acceptable Inquires

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.

Usage Exception

Donation Refunds

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.

Chargebacks

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.

Important Notes

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.

Contact Us

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

• 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.

Major Changes

• Rita now uses Discord.js V12.

Bug Fixes

• 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.

Command Changes

• 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.

Database Changes

• 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)

Misc Changes

• 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

Inital Release

### 1.3.23-0
Date: 10/12/22
User: Zycore
> ----------
>>> Env Files
* Update backup env files
* Update dependancies
    > body-parser               ^1.19.0  →  ^1.20.1
    > canvas                     ^2.9.1  →  ^2.10.2
    > common-tags                ^1.8.0  →   ^1.8.2
    > discord.js                ^14.6.0  →  ^14.7.1
    > ejs                        ^3.1.6  →   ^3.1.8
    > express                   ^4.17.1  →  ^4.18.2
    > express-session           ^1.17.2  →  ^1.17.3
    > iso-639-1                 ^2.1.13  →  ^2.1.15
    > memorystore                ^1.6.6  →   ^1.6.7
    > pg                         ^8.7.3  →   ^8.8.0
    > sqlite3                    ^5.0.2  →   ^5.1.2
    > @babel/core              ^7.17.10  →  ^7.20.5
    > @babel/eslint-parser      ^7.17.0  →  ^7.19.1
    > eslint                    ^8.15.0  →  ^8.29.0
    > nodemon                   ^2.0.12  →  ^2.0.20

V-1

### 1.3.23-1
Date: 10/12/22
User: Zycore
> ----------
>>> commands.js
* Change Last command pointer from .old to .run
    the code in .old cause all data to be deleted from the object, Major bug. 

>>> translate.last.js
* Commented out the .old method so it can be called by accident.

V-2

### 1.3.23-2
Date: 13/12/22
User: Qjuh
> ----------
>>> deploy-interactions.js, events.js
* added possibility for slashcommand files to have only dev-commands

>>> slashcommands/../announce.js
* Added `/announce [role:]` to send an announcement message to all servers, optionally only those whose subscription owners have the mentioned role in RMS

>>> slashcommands/../translate.js, core/translate.js
* Fixed import/export of discordPatch and translateFix methods used for `/translate {text} [from] [to]`

V-3

### 1.3.23-3
Date: 14/12/22
User:  Zycore
> ----------
>>> bot.js
* Added auto deploy code of slash commands on each boot.

V-4

### 1.3.23-4
Date: 27/12/22
User: Qjuh, Zycore
> ----------
>>> translate.react.js
* Added exclusion/catch for await statment of emojio remove

>>> db.js
* Fixed task count for removal of tasks
* Values for chars_used and ml_chars_used are now set to 0 not 1.

>>> send.js
* Corrected a error catch to not log to console
* Added printout for 40005 error to source channel

>>> bot.js
* Removed auto deploy code of slash commands on each boot

>>> misc.js
* fix a object error with selection of counters.

V-5

### 1.3.23-5
Date: 10/01/23
User: Qjuh 
> ----------
>>> translate.js
* Fix bug timestamps and slash commands
* eslint corrections
* regex Fix for code block detection

Inital Release

### 1.4.0-0
Date: 17/03/23
User: Qjuh
> ----------
>>> Bug Fixes
* args.js
	> Removal of Default Server Language output (Unused)
* command.js
	> Fixed URL Parsing
* translate.react.js
	> Fixed variable on error for `Raction Failed`
* auth.js
	> Type correction for botOwner constant
* db.js
	> Refactoring of return statments
* message.js, events.js
	> Fix for thread support
* slashcommands.js
	> subCommand correction
* All files
	> Corerction of `msg:` to `description:` for logger messages
	> Removal of all `function error (err)` calls to logger.js
* eslint Corrections

V-1

### 1.4.0-1
Date: 19/03/23
User: Qjuh
> ----------
>>> choose_server.js
* Fixed taskcount being "0" instead of 0, logger fix

>>> join.js, settings.js
* Removal of all `function error (err)` calls to logger.js

V-2

### 1.4.0-2
Date: 30/03/23
User: Qjuh
> ----------
>>> translate.auto.js
* Fixed Auto task count bug

V-3

### 1.4.0-3
Date: 31/03/23
User: Qjuh
> ----------
>>> send.js
* Improve DM error logs

V-4

### 1.4.0-4
Date: 04/04/23
User: Qjuh
> ----------
>>> send.js
* Fixed sendembeds in embedOn mode

V-5

### 1.4.0-5
Date: 05/04/23
User: Zycore
> ----------
>>> settings.js
* Removing Protected Code

>>> helpers.js, events.js
* Added varaibles for `REDCATED` plan and `REDCATED` plan to `getMaxChars`

>>> lang.check.js
* New languages added 
    > LANGUAGE              CODE
    > Assamese              as
    > Aymara                ay
    > Bambara               bm
    > Dhivehi               dv
    > Ewe                   ee
    > Guarani               gn
    > Javanese              jv
    > Kinyarwanda           rw
    > Lingala               ln
    > Oriya                 or
    > Oromo                 om
    > Quechua               qu
    > Sanskrit              sa
    > Tatar                 tt
    > Tigrinya              ti
    > Tsonga                ts
    > Turkmen               tk
    > Twi (Akan)            ak
    > Uyghur                ug

Goodbye Patreon, Hello Stripe

Over the last year, we have been hard at work integrating Stripe subscription and payment process, With a dedicated DASHBOARD to allow you to manage your subscription,

• Manage every aspect of your RITA subscription past, present, and future,

• We now offer Bi-monthly subscriptions, allowing you to pay for 2 months in advance,

• Role-based subscriptions are so RITA 1.0.

  • Thanks to our dashboard integration we know who you are and which discord account to link with at the point of sale. Click, Pay, Go,

• Modify server settings such as embed style, reaction translation etc.,

• Select the translation engine you want

  • 100% Machine Learning

  • Optimized

  • Normal

• Built with Stripe in mind. (More about Stripe below),

• Contact Support directly from the Dashboard,

• These are just some of the current features. Expect increased functionality in the Dashboard as we continue development!,

• Just login and get started! Current subscriptions with Patreon will appear, but you can buy new Dashboard subscriptions

Dashboard features (Current)

We will be expanding the features available to users in the dashboard as we continue development, For now, the core functions and most important ones are available to use.

• You can choose to pay on the 1st of each month like we currently offer, or the same day you subscribe, free to choose.

• You will be able to see all your subscriptions in one place.

• You can modify server settings such as embed style, reaction translation etc.

A Few Dashboard Q&A's

• What is a Dashboard?

  • The RITA Dashboard is a website in which you login with your Discord account and can oversee all your RITA servers, access the billing portal, and buy new plans,

• Will 'I' need to do anything to keep using my current paid version of RITA?:

  • No, we do suggest converting any current Patreon subscriptions to Stripe via the Dashboard when it makes sense for you.,

  • Cancelling your Patreon subscriptions gives you access until the first day of the next month, so you should cancel and resubscribe via the Dashboard on that renewal date.,

• Will 'I' need to pay more for the Dashboard?:

  • Nope! If anything, you’ll pay less with an assortment of promotion codes we will be handing out to encourage people to move over.,

• Is it free to upgrade/switch to RITA v2?

  • Of course, RITA updates will always benefit all subscribers and not paywall optimizations

Slash Command News

• Great news for any RITA users who speaks Spanish, Italian, Portuguese, Russian, Simplified Chinese, or Turkish

  • Once you've set the server's language to one of the above,

  • Or after checking that your Discord client's location is set to one of those above locals,

• RITA's slash commands will now be in those languages,

• More language support in the Slash Commands to follow!

Bots Changes

• Reply function: These are now translated across channels just like the original message.

• Style: you can now prefix the message with the source language Emoji

• Slash commands: Most of the core function commands are now available as slash commands.

Technical and Misc Improvements

• Our Dedicated ML server got some upgrades, increasing performance and resulting in reduced downtime (if you ever felt it),

• Improved redundancy and fall over protection for RITA.

• Database Changes, are not important for you, but important for us.

  • We made several changes to the way we store and manage data.

  • Improve efficiency in our Database code allowing for more agile adding in new functionality.

  • Improved testing to development behavior before pushing changes to our production environment, making sure every change made in our code won't lead to downtime.

  • Code refactoring: to answer your queries quicker.

• As a result of our downtime in April, we have new private servers.

• Our new private server also hosts our backend code, dashboard code and ML Engine,

• Over 300 commits to our code base

Final Remarks

• A HUGE Thank you to the entire RITA Team. Without each of you RITA wouldn't be what it is today!

• Thanks to you all the RITA users! It's our pleasure to keep making RITA better and better. I can't wait to see what RITA 3.0 will look like!

• As always we are available to answer any questions you have or assist with troubleshooting any issues.

What's next ?

^{CHECK BACK LATER FOR MORE INFO.}

The following Interpretations and Definitions apply to the following Policies

• Terms of Service (TOS)

• S.A.L.T.S Policy

• Privacy Policy

• Refund Policy

Interpretation

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.

Definitions

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.

Inital Release

### 1.3.9-0
Date: 23/10/22
User: Qjuh
> ----------
>>> various files
* Removed unneccessary eslint disables
* Moved some disables to next-line disables to not affect the whole file

>>> args.js
* Changed for..in to for..of and removed the eslint-disable

>>> join.js, event.js
* Removed the unused config parameter for guild join

>>> purge.js
* Commented unused `target` variable, made the function synchronous

>>> sub.js
* Backported the changes to addsub->subadd and removesub from development branch for manual dev-override subscriptions

>>> helpers.js
* Added `awaitMessage` function, was in translate.group_auto.js before, now used by that and sub.js

>>> translate.group_auto.js
* Removed unused `groupName` parameter from `listGroups` function

>> send.js
* Merged redundant webhook.send calls into one call (yes, I touched it again)

>>> translate.js
* Removed unused `guild` parameter from `bufferChains` function
* Changed `bufferChains` to use `translationHandler` too, instead of using Google Translate always

>>> deploy-interactions.js, slashcommand.js, slashcommands/../settings.js, slashcommands/../group.js, slashcommands/../translate.js, slashcommands/../check.js
* Added handler for slashcommands
* Changed deploy script to dynamically deploy commands that exist in slashcommands folder
* Added `/settings`, equivalent to `!tr settings` and its subcommands `reactpersist`, `menupersist`, `flagpersist` and `reset`, as well as `prefix` (ironic, I know), `bot2bot`, `embed`, `react`. Also has `/settings devreset` which accepts a serverId as option, but won`t be deployed globally, only to support server with needing Administrator permission per default to even appear and safeguarded as isDev internally.
* Added `/group`, equivalent to `!tr group` and all its subcommands
* Added `/check`, equivalent to `!tr check` and its subcommands, including a support-server only `/check server` command accepting a serverId as option, needing Administrator permission per default to even appear and safeguarded as isDev internally.
* Added `/translate` command, equivalent to `!tr this`
* These won't show unless deploy-interaction.js is run (which we shouldn't until we want to release them)

>>> message.js
* Fixed small bug not showing serverId of blacklisted server in redundancy check

V-1

### 1.3.9-1
Date: 24/10/22
User: Qjuh
> ----------
>>> misc.js
* Added response for `!tr taskfix` command

>>> eject.js, command.send.js, send.js, db.js
* Moved increment of server_obj values to `increaseServersCount()` function

>>> country.langs.js
* Removed `rm` from `ch` flag

>>> db.js
* Switched order of some db calls to make sure the values we use still exist when we use them
* Moved another server_obj update to a `updateServerObj()` call

>>> helpers.js
* Fixed `subExpired()` and `checkSubActive()` functions according tp dev branch

>>> send.js
* Merged embed send if/else into one, according to dev branch

>>> args.js
* Fixed usage of `subadd` instead of `addsub`

V-2

### 1.3.9-2
Date: 25/10/22
User: Qjuh
> ----------
>>> send.js
* use attachments collection directly instead of converting to array
* added some ?. for safety
* simplified servertags check

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.

Interpretation and Definitions

The words of which the initial letter is capitalized have meanings defined under Interpretations and Definitions, they are located Here.

Subscription Refunds - Exclusion Timeframe

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

Patreon Payments

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.

KOFI Payments (DISCONTINUED)

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.

Other Possible Reasons

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.

Non-Acceptable Inquires

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.

Usage Exception

Donation Refunds

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.

Chargebacks

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.

Important Notes

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.

Contact Us

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 [email protected]

• 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.

What is Patreon

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.

How to Subscribe

• Navigate to Patreon

• 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.

Linking/Creating an Account - Before & After

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