S.A.L.T.S Policy

In Effect From: August 20, 2023 / Last updated: August 15, 2023

S.A.L.T.S Policy - Document Version 4 (In Effect August 20, 2023 > Current)

S.A.L.T.S Stands for Subscription, Activation, Limitations, Termination and Suspension Policy. This describes Our policies and procedures on how each of the aforementioned processes are handled.

By using the Service, You agree to the following processes and be subject to enforcement of them.

Interpretation and Definitions

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

Subscription

A User subscription follows the below flows. These are different for each subscription platform.

Activation Process

Refer to activation steps below in Activation Section.

Payment & Renewal Dates

Subscriptions are renewed on different days depending on the platform.

  1. Patreon

    1. Renews monthly on the 1st of each month regardless of subscription date. E.g., subscription is purchased and payment is taken on the 09th of May. On the 1st of June payment is taken, then again on the 1st July. This continues monthly until cancelation.

ACTIVE - Subscription Tier's and Cost

These plans are the base subscription plans on offer. Costs are fixed and can not be changed. Once a user has subscribed to the plan they will remain on the plan until the subscription is cancelled. See Tier Cost Changes & Availability for More information.

TRIAL USER - The TRIAL will allow a user to try RITA for a period of one (1) month, or until limits have been reached, whichever comes first. Servers are limited to 1 TRIAL Per Server - Per Users.

PROMOTIONAL- Subscription Tier's and Cost

These plans are subject to availability and are time-limited. Costs are fixed and can not be changed. Once a user has subscribed to the plan they will remain on the plan until the subscription is cancelled. Once an offer window has passed there is not guarantee it will be available again. See Tier Cost Changes & Availability for More information.

RETIRED - Subscription Tier's and Cost

These plans are retired and no longer available. Costs are fixed and can not be changed. Once a user has subscribed to the plan they will remain on the plan until the subscription is cancelled. Once an is retired it will be available again. See Tier Cost Changes & Availability for More information.

Tier Cost Changes & Availability

  • Once a User has purchased a subscription, the cost they pay will not change, unless they cancel the subscription and then re-subscribe.

    • Cancellation due to failed payment resulting in the cancellation of an archived or expired plan cannot be re-activated, regardless of the reason.

  • No notice will be given on archiving or retiring a plan or removing availability; however, We believe in an open dialect with our customers. That said, business reason depends, We will provide information in the form of an announcement when possible.

Other Limitation(s)

All Plans/Tiers are subject to other limitations, detailed below.

Subscription Activation

  1. User Invites RITA to server >

  2. User Joins RMS Server >

  3. User selects relevant plan provided by Patreon >

  4. User completes payment via platform

    1. Patreon > Payment is handled by Patreon

  5. Upon Confirmation of payment User activates Discord integration through account linking.

    1. Guide for Patreon

  6. Integration uses the Patreon Bot to apply relevant roles to User, a Role from Payment, Tier, and the Subscription section below are needed for RITA to work.

  7. RITA detects role additions and adds relevant and required data to our Subscription Database

  8. Once User has all identifying Roles they are able to see the channel #activate-rita-here.

    1. If role addition fails or is incomplete, then it is investigated by the ADMIN team. The ADMIN team will manually validate payment completion and then apply correct roles, if necessary.

  9. User types `!tr sub` in the above noted channel or in their own server. If they own more than one server or are admin in more than one server, then they are prompted to select the server they want to use RITA in.

    1. RITA must be in the server before the command is run, else an error will be provided.

  10. RITA is activated and the subscription process is completed.

TRIAL Activation

  1. User Invites RITA to server >

  2. User types `!tr trial` in their own server.

  3. RITA is activated and the TRIAL Activation process is completed.

Limitations

Each plan has the following limitation applied.

Due to the rising cost of our Hosting, Charges to Google and Payment Processing Services, we have made changes to the character limitations applied to each plan, this will take effect on the 1st of May 2023

TRIAL USER - The TRIAL will allow a user to try RITA for a period of one (1) month, or until limits have been reached, whichever comes first. Servers are limited to 1 TRIAL Per Server - Per Users. Once Limit has been reached RITA will stop functioning for translations. Users do not need to be a Member of the RMS (RITA Management Server) to use the TRIAL.

Hard Cap = not enforced to the digit but close. This is calculated by

  • Example from English to French: Hello -> Bonjour

    • (5 Characters * 1 language translation) + 5 original chars = 10 Total Chars

Exceeding Character Limit will result in bot ceasing to respond to translation requests.

Soft Cap = not enforced to the digit but close. This is calculated by

(Number of Characters in message * Number of languages translated to) + Original Char Count = Total Char Count.

  • Example from English to French: Hello -> Bonjour

    • (5 Characters * 1 language translation) + 5 original chars = 10 Total Chars

  1. Exceeding Character Limit. Either of the following Scenarios are taken, via automation by RITA or manual intervention by a member of RMS Staff

    • A server exceeds the soft caps assigned to their plan

    • Translation Services are swapped from Implicit Google API Translation to Implicit Machine Learning API Translation for Languages we have trained and that are optimized to a high standard. See Machine Learning API for more information.

    • At the start of the next calendar month Implicit Google API Translation is reactivated until breach of soft cap

Machine Learning API

ML API currently has an upper bound limit of 10 million characters translated per month. This upper bond if not hard coded in to RITA, however it is checked periodically throughout the month. If a User exceeds this a custom tier cost or solution may be required, however no suspension will happen as a result of this limit.

Optimised Languages

Termination

The Termination Process is used in conjunction with the Suspension Process and follows a pre-defined path.

AT NO POINT IN THIS PROCESS IS THE END USER ELIGIBLE FOR A REFUND. THIS PROCESS IS ONLY EXECUTED IN THE MOST SERIOUS OF CIRCUMSTANCES.

The Termination flow can only executed/started by the following RMS staff levels and is governed by a strict time frame.

  • Owners

  • Admins

  • Developers

Step 1: Contact with User is attempted by RMS staff.

Attempted contact must be made for process to start. Time line starts once receipt of contact is confirmed. Contact can be via Direct Message from RITA, Tagged/Pinged in RMS, DM from a member of staff or notice provided on the User’s server by RITA or Member of staff.

If User has not made contact within 24 hours move on to Step 2.

Step 2: Service is Suspended.

RITA Translation and Command service is PAUSED, as defined in Suspension Process.

A Further Notice/Contact Attempt is sent to User. This can be via a Direct Message from RITA, Tagged/Pinged in RMS, DM from a member of staff or notice provided on the User’s server by RITA or Member of staff.

User has not made contact within 48 hours move on to Step 3.

Step 3: RITA is Ejected

As a security measure RITA is able to Self-Eject from a server at any time. This function is executed. This results in no loss of data on the server.

A Further Notice/Contact Attempt is sent to The User via a Direct Message from RITA, Tagged/Pinged in RMS, DM from a member of staff or notice provided on the User’s server by RITA or Member of staff.

User has not made contact within 72 hours move on to Step 4.

Step 4: Server is Blacklisted

The Server ID is Blacklisted. If the User attempts to add RITA back to a server that is blacklisted, RITA will kick herself from the server.

NO Further Notice/Contact Attempt to The User is made at this point

User has not made contact within 24 hours move on to Step 5.

Step 5: NO FURTHER CONTACT

No further contact to User will be attempted or made. The matter is classified as closed and no further support will be provided

Suspension

  1. A Suspension of Service can be implemented for a varying number of reasons. This is referred to as Pausing.

  2. Pausing and resuming of service can only be conducted by the following RMS staff levels

    1. RITA

    2. Owners

    3. Admins

    4. Developers

    5. Senior Staff

  3. Service can be Paused under the following conditions

    1. Detection of suspicious activity.

      1. We cannot share what this look like to prevent anti-detection methods

    2. Exceeding Character Limits of Tier (*When Implemented)

      1. This could be Google API Limits or ML Limits

  4. Suspicion that RITA is being used for SPAM or JUNK flooding

  5. Request to Terminate by third party agencies or companies in line with our Privacy Policy and ToS.

  6. Identification that RITA is being used for Commercial use exceeding fair and reasonable use. This is not defined and will be reviewed on a case by case basis. This does not exclude the use of RITA from commercial use.

If Service is Paused, We are not able to offer pro rata refunds for the time the service is paused, inactive or non-operational. This is in line with our Refund Policy.

Last updated

Copyright © 2019 - 2023 RitaBotProject. All rights reserved.