1 of 87

RitaBot Docs

Introduction

The official documentation of RitaBot. Breaking the language barrier for thousands of people.

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

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

How to intall ?

Meet the Team

Get to know us, we dont Bite.

The Owners

Artanis - CDO

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.

Jupiter - CCO

He looks sometimes like if he was not born in earth, but he's nice too

JShep89 - CHRO

Always thinking about improvement of bot from user-ends, he will always listen to your feedbacks (even if he hates writing)

Zycore - CFO

The one who doesn't want to fill this section
He's shy but not that much.

Development & Core Staff

Z3US - Core Developer

My skills centre in IT and Telephony.

I have a focus on newer style technologies such as VoIP and Cloud Distributed SIP environments, however I also have a strong grounding in older Siemens Telephony systems (HighPath 3k, Realities).

My hobby happens to be coding, I focus on Powershell and NodeJS. Hence my possition here at RITABot. While I am still a beginner, I never stop learning new things.

I am proficient in Windows, MacOS and Linux, and have started learning Unix in the form of BSD. The main focus behind this is so that any task I take on, I am not limited by my knowledge of the Operating system involved.

I never shy away from a challenge and always find a way to improve.

Qjuh - Developer

I‘m Qjuh, I’m a teacher for maths and computer science and in my free time I’m a hobby programmer and mobile gamer What lead me to become a RITA user at first (for our multilingual mobile gaming discord) and then gradually getting more and more involved in its development. Well, here I am now and trying not to break too much while adding stuff here and there…

Brozer - Database Developer

At work, i'm a DBA on the development side who help dev teams (over 600 people) to modelize their data into RDBMS like PostgreSQL and Oracle. I also help them to build secured databases, evolutive with perf guarantees. As a support member, I also give them lessons on fundamentals like how to code properly in SQL ANSI, how to choose a database to fit their needs (relational Vs NoSQL) and how to improve their physical model in adequation with the datas they want to store in, even for huge storage / huge sollicitations.

My hobbies are mainly development, that's why i joined RITA Team for learning and helping on Node.js and Sequelize with my "DB skills" first. I also code for my home automation (bash, Lua, JSON, XML, SQLite, ...)

Trainer Paul - Senior Helper(Retired)

I have a long history of Dos, Windows, Database building, and Server building experience, but nothing compared to the combined knowledge of the Rita team. Why Trainer? I used to actually train employees, and a Electrical instructor of years past. I support the Rita team, users, and helping is one of my qualities. Thanks Rita team for closing the gap on communication for all members on Discord.

Support Staff

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!

Community Helpers

Quick setup steps

How to make RITA running in your Discord Server

Steps to follow in order to install RITA

Check that your discord account is the owner of the server or an admin of the server you want RITA Bot in
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.

Quick setup steps FAQ

Do I need to purchase a subscription to get RITA work ?

Yes

I had an issue with my payments in Patreon, got over it, but !tr sub is still not working

This occurs due to some issues with Patreon

Check that your payment has been successful in Patreon
Try to unlink/relink your discord account and then run !tr sub again in your server
If none of this works - please open a support ticket in our discord server

I'm the owner of the server where RITA is, and i installed it / purchased the subscription. I don't want to configure it, can one of my server admin do it ?

Yes of course !

How to change the server where RITA is translating ?

To move your subscription from one server to another you only need to invite RITA and run the command !tr sub in the server you wish it to be in.

Usage, Commands & Settings

Basic Usage Information.

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.

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

Command structure

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

For Example:

!translate help modules

!tr help modules

!tr help

Translation Commands

Information on Transaltion Commands.

Group Translations

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

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

Channel Translation

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

Legacy commands

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

Parameters

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.

Examples

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

Server Admins/Mods

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

Stopping Translations

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]

Parameters

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

Admins/Mods

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

Notes

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

Custom Message

Important Note

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?

Last Message

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.

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

Important Note

Users who wish to receive automatic translations in private must enable DMs via server privacy settings.

Statistics

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

Settings

Important Note

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

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]

!tr help embed

This is embed style: This is webhook style:

Language Detection

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

!tr settings langdetect [on/off]

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

Important Note

Users who wish to receive automatic translations in private must enable DMs via server privacy settings.

Misc. Commands

Important Note

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

Premium/Paid Features

Overview

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.

About Subscribing

Maintenance and Uptime

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.

Servers

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.

How to Activate?

Soft Limit

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.

Quality

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

Limits

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.

What do I get with each plan?

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.

Function / Command

Casual

Tinkerer

Pro

Task Limit

100

200

350

Soft Limit (characters)

~200k Google

~450k Google

~700k Google

Character Limit (backed by ML)

Unlimited

What is a task?

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

How to Subscribe

All the information you need to know about subscriptions.

Available Plans

All Plans, Prices, Limitations and Restrictions are correct at time of publication.

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

Patreon

This is a Guide on how to subscribe on Patreon

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.

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

Cancelling a Subscription

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.

Payment FAQ

Why have been charged too much?

This may only happen with Patreon. Patreon rounds up to the nearest .5 increment of your currency. This is not something we are able to overcome, this is how Patreon works.

Can I use <insert service here> to pay for RITA?

No, we only use Patreon to facilitate our payments and automation. If the payment methods supported by Patreon do not include your desired payment service then we can't assist you regarding this.

Contact Us

Misc

It’s All About Rita

All development and support of the self-hosted version has now been discontinued

What is RITA and who are we?

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.

MIT License

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

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

FAQ

Here are some of the common questions that have been asked about the process.

Why is RITA no longer free?

We used an old version of the Google Translate Website API that was intended to be decommissioned prior to 2010. Google has now shut this down, as such, we are now required to use the Google Cloud Translate API which comes with costs.

Can I continue to use Self-Hosting?

Due to the impending shutdown of all V11 and V12 API, the self-hosting option has reached end-of-life. Once the support goes down, the self-hosting bots will immediately cease to function and there will be nothing we can do.

Why is self hosting support ending?

There are a few reason why self hosting support is ending.

Currently the self hosting version operates an older version of the RITA Code, as such it constantly needs to be managed, updated and maintained.

This means we need to update the code and ensure it works. This takes time. At the moment we want to dedicate this time to ensuring the paid version is working and online. When we split our attention it has an impact on our ability to help everyone.

This does not mean a member of the community, if they want to, cant offer support to another member of the community. There won't be official Dev/Admin/helper support for self hosting issues.

In the future this may change, but at the moment we can not dedicate our time to supporting self hosting users.

Can I use a personal API Key using Self-Hosting instead?

At this time, we cannot offer that option as the self-hosting option will require a full rewrite to be V13 compatible. As such, ALL self-hosting will be unavailable and unsupported. This may change in the future but not till 2023 at the earliest.

Can I purchase a lifetime subscription?

No Lifetime subscriptions are not offered as the API that we have to pay for requires monthly payments. The likelihood of running into financial instability if everyone had a lifetime sub would be very high. Continuing with a monthly plan has the greatest chance for operational longevity.

Is payment per server or per user?

The subscription will be a mix of per-user/per-server. Each server you wish to have RITA active in will require you to be the owner of the server (Yes owner not admin) to purchase the subscription. This owner could theoretically use this single license in any server they are the owner of, however, it will only work on 1 server at a time.

Is there a limit to how many servers we can purchase for?

Currently, users are limited to 1 server at this time. More servers will be allowed in the future. Criteria: User must be the SERVER_OWNER, User must pay for the subscription themselves as the sub is mapped to their USER ID.

What are our future plans?

RITA as it stands is using the Google Cloud API, and is charged, as such we are charged for usage, thus the need for a subscription fee. However, there are other APIs available for use.

The long term goal is to have a paid-for, all features version. All our changes, new features and work will continue on this version.

Like a lot of other discord bots, we want to try and introduce a free limited version, and we are looking at how this can be done, with some of the other APIs that are free, with limited languages and support, reduced accuracy and higher delaying in responses. This is not saying we will reduce the accuracy or reliablilty of these API, its just the nature of API data we will have access too.

We are looking at ways we can implement these into a free version. It will be limited and would have limits such as 10 tasks, flags only, etc etc.

This means we can continue to draw in users, while offering all our support and time to paid users, ensuring that we continue development and can keep RITA running for years to come.

What support can I expect?

The level of support you get at the moment will inevitably change, And we will not turn into a “you don’t pay so you don't matter” support server. All our users are important. Without all of you, we would not be where we are today.

There will be things however that will be managed by a single or maybe two members of staff, such as payment-related issues. This will not be able to be managed by general support staff and will require an Admin. This means there may be an SLA of 24 hours to allow for time zones and real life. More details will be provided on responsibilities and roles close to launch.

How will payments be made?

Currently we offer subscriptions though Patreon. Patreon utilizes PayPal and card payments.

What Subscription levels will be offered?

Currently, we are offering 3 levels.

Reaction = 0 Tasks - Translation by Reaction only Casual = 100 Tasks Tinkerer = 200 Tasks Pro= 350 Tasks Ultima = 550 Tasks All levels come with Discord access and roles, with bot support for the lifetime of your subscription. To hold your subscription you must be in our support server.

Why is there a Task limit?

Again this is simple, if every server had 1000 task limit, and we have 10k servers, that's 10,000,000 (Million) Tasks. Not only is this too many for us to think about but, it would also have a massive impact on reliability and speed.

100 is a fair starting limit, and since 98% of our current user base has less than 100 it is easy to launch with most of the work done.

We recognise that some server may need more tasks, thats why we have other plans to pick from.

Do i need to set RITA up again in my server?

If you had RITA in your server before, any configuration you had previously will continue to operate without additional setup. Please note, however, that if your task count exceeds 250, then the basic plan will not be enough for you, and RITA may not start translating immediately until upgraded.

Version History

V1.2.?

Version History for 1.2.?

V1.2.0

Information about the 1.2.0 Update.

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.

V1.2.1

Information about the 1.2.2 Update.

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

V1.2.2

Information about the 1.2.2 Update.

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

V1.2.3

Information about the 1.2.3 Update.

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.

V1.2.4

Information about the 1.2.4 Update.

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.

V1.2.5

Information about the 1.2.5 Update.

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

V1.2.6

Information about the 1.2.6 Update.

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.

V1.3.0

Version History for 1.3.?

Updates

Policys

Reaction Translation

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.

Translates a message in the server when you react to it with a flag emoji.

The full Supported list can be found below

Code

Flag

Country

Translates Tonga

Lang Code

:flag_af:

Afghanistan

Pashto

:flag_ax:

Aland Islands

Swedish

:flag_al:

Albania

Albanian

:flag_dz:

Algeria

Arabic, French

ar, fr

:flag_as:

American Samoa

English, Samoan

en, sm

:flag_ad:

Andorra

Valencian

:flag_ao:

Angola

Portuguese

:flag_ai:

Anguilla

English

:flag_aq:

Antarctica

null

:flag_ag:

Antigua And Barbuda

English

:flag_ar:

Argentina

Spanish

:flag_am:

Armenia

Armenian

:flag_aw:

Aruba

Dutch

:flag_au:

Australia

English

:flag_at:

Austria

German

:flag_az:

Azerbaijan

Azerbaijani

:flag_bs:

Bahamas

English

:flag_bh:

Bahrain

Arabic

:flag_bd:

Bangladesh

Bengali

:flag_bb:

Barbados

English

: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

:fag_bm:

Bermuda

English

:flag_bt:

Bhutan

Dzongkha

:flag_bo:

Bolivia

Spanish

:flag_ba:

Bosnia And Herzegovina

Bosnian, Croatian, Serbian

bs, hr, sr

:flag_bw:

Botswana

English

:flag_bv:

Bouvet Island

Norwegian

:flag_br:

Brazil

Portuguese

:flag_io:

British Indian Ocean Territory

English

:flag_bn:

Brunei Darussalam

Malay, English

ms, en

:flag_bg:

Bulgaria

Bulgarian

:flag_bf:

Burkina Faso

French

:flag_bi:

Burundi

French, Rundi

fr, rn

:flag_kh:

Cambodia

Central Khmer

:flag_cm:

Cameroon

French, English

fr, en

:flag_ca:

Canada

English, French

en, fr

:flag_cv:

Cape Verde

Portuguese

:flag_ky:

Cayman Islands

English

:flag_cf:

Central African Republic

French, Sango

fr, sg

:flag_td:

Chad

Arabic, French

ar, fr

:flag_cl:

Chile

Spanish

: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

: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

:flag_cr:

Costa Rica

Spanish

:flag_ci:

Cote D’Ivoire

French

:flag_hr:

Croatia

Croatian

:flag_cu:

Cuba

Spanish

:flag_cy:

Cyprus

Greek, Turkish

el, tr

:flag_cz:

Czech Republic

Czech

:flag_dk:

Denmark

Danish

:flag_dj:

Djibouti

Arabic, French

ar, fr

:flag_dm:

Dominica

English

:flag_do:

Dominican Republic

Spanish

:flag_ec:

Ecuador

Spanish

:flag_eg:

Egypt

Arabic

:flag_sv:

El Salvador

Spanish

:flag_gq;

Equatorial Guinea

Spanish, French, Portuguese

es, fr, pt

:flag_er:

Eritrea

Arabic, English, Tigrinya

ar, en, ti

:flag_ee:

Estonia

Estonian

:flag_et:

Ethiopia

Oriya, Amharic, Somali, Tigrinya

or, am, so, ti

:flag_fk:

Falkland Islands (Malvinas)

English

: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

:flag_gf:

French Guiana

French

:flag_pf:

French Polynesia

French

:flag_tf:

French Southern Territories

French

:flag_ga:

Gabon

French

:flag_gm:

Gambia

English

:flag_ge:

Georgia

Georgian

:flag_de:

Germany

German

:flag_gh:

Ghana

English

:flag_gi:

Gibraltar

English, Spanish

en, es

:flag_gr:

Greece

Greek

:flag_gl:

Greenland

Kalaallisut, Danish

kl, da

:flag_gd:

Grenada

English

:flag_gp:

Guadeloupe

French

:flag_gu:

Guam

English, Chamorro

en, ch

:flag_gt:

Guatemala

Spanish

:flag_gg:

Guernsey

English

:flag_gn:

Guinea

French

:flag_gw:

Guinea-Bissau

Portuguese

:flag_gy:

Guyana

English

:flag_ht:

Haiti

French

:flag_hm:

Heard Island & Mcdonald Islands

null

:flag_va:

Holy See (Vatican City State)

Latin, Italian

la, it

:flag_hn:

Honduras

Spanish

:flag_hk:

Hong Kong

Chinese, English

zh-tw, en

:flag_hu:

Hungary

Hungarian

:flag_is:

Iceland

Icelandic

:flag_in:

India

Hindi

:flag_id:

Indonesia

Indonesian

:flag_ir:

Iran

Persian

: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

:flag_jm:

Jamaica

English

:flag_jp:

Japan

Japanese

:flag_je:

Jersey

English

:flag_jo:

Jordan

Arabic

:flag_kz:

Kazakhstan

Kazakh, Russian

kk, ru

:flag_ke:

Kenya

English, Swahili

en, sw

:flag_ki:

Kiribati

English

:flag_kr:

South Korea

Korean

:flag_kw:

Kuwait

Arabic

:flag_kg:

Kyrgyzstan

Kirghiz, Russian

ky, ru

:flag_la:

Lao People’s Democratic Republic

Lao

:flag_lv:

Latvia

Latvian

:flag_lb:

Lebanon

Arabic

:flag_ls:

Lesotho

Southern Sotho, English

st, en

:flag_lr:

Liberia

English

:flag_ly:

Libya

Arabic

:flag_li:

Liechtenstein

German

:flag_lt:

Lithuania

Lithuanian

:flag_lu:

Luxembourg

Letzeburgesch, French, German

lb, fr, de

:flag_mo:

Macao

Chinese, Portuguese

zh-tw, pt

:flag_mk:

Macedonia

Macedonian

:flag_mg:

Madagascar

Malagasy, French

mg, fr

:flag_mw:

Malawi

English

:flag_my:

Malaysia

Malay

:flag_mv:

Maldives

Maldivian

:flag_ml:

Mali

French

:flag_mt:

Malta

Maltese

:flag_mh:

Marshall Islands

Marshallese, English

mh, en

:flag_mq:

Martinique

French

:flag_mr:

Mauritania

Arabic

:flag_mu:

Mauritius

English, French

en, fr

:flag_yt:

Mayotte

French

:flag_mx:

Mexico

Spanish

:flag_fm:

Micronesia

English

:flag_md:

Moldova

Romanian

:flag_mc:

Monaco

French

:flag_mn:

Mongolia

Mongolian

:flag_me:

Montenegro

Montenegrin

cnr

:flag_ms:

Montserrat

English

:flag_ma:

Morocco

Arabic

:flag_mz:

Mozambique

Portuguese

:flag_mm:

Myanmar

Burmese

:flag_na:

Namibia

English

:flag_nr:

Nauru

:flag_np:

Nepal

Nepali

:flag_nl:

Netherlands

Dutch

:flag_bq:

Netherlands Antilles

Dutch

:flag_nc:

New Caledonia

French

:flag_nz:

New Zealand

English

:flag_ni:

Nicaragua

Spanish

:flag_ne:

Niger

French

:flag_ng:

Nigeria

English

:flag_nu:

Niue

English, Niuean

en, niu

:flag_nf:

Norfolk Island

English

:flag_mp:

Northern Mariana Islands

English, Chamorro, Carolinian

en, ch, cal

:flag_no:

Norway

Norwegian

:flag_om:

Oman

Arabic

:flag_pk:

Pakistan

Urdu

:flag_pw:

Palau

English, Palauan

en, pau

:flag_ps:

Palestinian Territory

Arabic

:flag_pa:

Panama

Spanish

: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

:flag_ph:

Philippines

Tagalog

:flag_pn:

Pitcairn

English

:flag_pl:

Poland

Polish

:flag_pt:

Portugal

Portuguese

:flag_pr:

Puerto Rico

Spanish

:flag_qa:

Qatar

Arabic

:flag_re:

Reunion

French

:flag_ro:

Romania

Romanian

:flag_ru:

Russian Federation

Russian

:flag_rw:

Rwanda

Kinyarwanda, English, French, Swahili

rw, en, fr, sw

:flag_bl:

Saint Barthelemy

French

:flag_sh:

Saint Helena

English

:flag_kn:

Saint Kitts And Nevis

English

:flag_lc:

Saint Lucia

English

:flag_sx:

Saint Martin

Dutch, French, German

nl, fr

:flag_pm:

Saint Pierre And Miquelon

French

:flag_vc:

Saint Vincent And Grenadines

English

:flag_ws:

Samoa

Samoan, English

sm, en

:flag_sm:

San Marino

Italian

:flag_st:

Sao Tome and Principe

Portuguese

:flag_sa:

Saudi Arabia

Arabic

:flag_sn:

Senegal

French

:flag_rs:

Serbia

Serbian

:flag_sc:

Seychelles

English, French

en, fr

:flag_sl:

Sierra Leone

English

:flag_sg:

Singapore

English, Tamil, Chinese, Malay

en, ta, zh-tw, ms

:flag_sk:

Slovakia

Slovak

:flag_si:

Slovenia

Slovenian

:flag_sb:

Solomon Islands

English

: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

:flag_es:

Spain

Spanish

:flag_lk:

Sri Lanka

Sinhalese, Tamil

si, ta

:flag_sd:

Sudan

Arabic

:flag_sr:

Suriname

Dutch

:flag_sj:

Svalbard And Jan Mayen

Norwegian

:flag_sz:

Swaziland

Swati, English

ss, en

:flag_se:

Sweden

Swedish

:flag_ch:

Switzerland

German, French, Italian

de, fr, it

:flag_sy:

Syrian Arab Republic

Arabic

:flag_tw:

Taiwan

Chinese

zh-tw

:flag_tj:

Tajikistan

Tajik

:flag_tz:

Tanzania

Swahili

:flag_th:

Thailand

Thai

:flag_tl:

Timor-Leste

Tetum, Portuguese

tet, pt

:flag_tg:

Togo

French

:flag_tk:

Tokelau

Tokelau, English

tkl, en

:flag_to:

Tonga

Tonga, English

to, en

:flag_tt:

Trinidad and Tobago

English

:flag_tn:

Tunisia

Arabic

:flag_tr:

Turkey

Turkish

:flag_tm:

Turkmenistan

Turkmen

:flag_tc:

Turks and Caicos Islands

English

:flag_tv:

Tuvalu

Tuvalu, English

tvl, en

:flag_ug:

Uganda

English, Swahili

en, sw

:flag_ua:

Ukraine

Ukrainian

:flag_ae:

United Arab Emirates

Arabic

:flag_gb:

United Kingdom

English

:flag_us:

United States

English

:flag_um:

United States Outlying Islands

English

:flag_uy:

Uruguay

Spanish, Portuguese

es, pt

:flag_uz:

Uzbekistan

Uzbek

:flag_vu:

Vanuatu

Bislama, English, French

bi, en, fr

:flag_ve:

Venezuela

Spanish

:flag_vn:

Vietnam

Vietnamese

:flag_vg:

British Virgin Islands

English

:flag_vi:

Us Virgin Islands

English

:flag_wf:

Wallis and Futuna

French

:flag_eh:

Western Sahara

Arabic

:flag_ye:

Yemen

Arabic

:flag_zm:

Zambia

English

:flag_zw:

Zimbabwe

Chichewa, English, Xhosa, Southern Sotho, Shona

ny, en, xh, st, sn

Important Note

Users who wish to receive automatic translations in private must enable DMs via server privacy settings.

Privacy Policy

In Effect Fom: May 01, 2023 / Last updated: April 05, 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.

Interpretation and Definitions

Collecting and Using Your Personal Data

Types of Data Collected

Personal Data

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.

Anonymized Translation Data Collection

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

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.

Tracking Technologies and Cookies

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

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.

Use of Your Personal Data

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.

Retention of Your Personal Data

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.

Transfer of Your Personal Data

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.

Disclosure of Your Personal Data

Business Transactions

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.

Law enforcement

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

Other legal requirements

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

Security of Your Personal Data

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.

Children's Privacy

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.

Links to Other Websites

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.

Changes to this Privacy Policy

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.