# Right To Exit 18**/05/26 Refund, Privacy & S.A.L.T.S Policy Update** * The change to our [Privacy](/ritabot-docs/policys/privacy-policy.md), [S.A.L.T.S](/ritabot-docs/policys/s.a.l.t.s-policy.md) and [Refund](/ritabot-docs/policys/refund-policy.md) Policy's 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. * Change to soft Limits defined in [S.A.L.T.S Policy #DeepL API Usage Updated Limits](/ritabot-docs/policys/s.a.l.t.s-policy.md#deepl-api-usage-updated-limits) may constitute a Right-to-Exit. All such cases and claims shall be reviewed on a case-by-case basis if raised. Any accepted claim must be submitted within thirty (30) days of the dated policy change, after which no further claim shall constitute a Right-to-Exit and all such claims shall be denied. * A Right-to-Exit in respect of such changes shall only apply where the reduced usage limits can be reasonably proven to have a material adverse effect on the functionality or reliability of the Service, and where supported machine learning trained languages are not provided to a substantially equivalent standard, or where a fault in such trained models is identified. * Any changes to a subscription plan, cost, payment method, or billing platform constitute acceptance of this policy change and shall render any such request null and void unless it falls within the terms and authorisation of the updated [Refund](/ritabot-docs/policys/refund-policy.md) Policy. * Acceptance of a Right-to-Exit request shall result in the termination of any active subscription. User subscriptions must be active at the time of the relevant policy change. * 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 [**Discord Server**](https://discord.gg/mgNR64R) in a support ticket or by sending an email to [**stripe@ritabot.gg**](mailto:stripe@ritabot.gg) * Further clarification of changes can be provided upon request. *** **05/06/25 Refund, Privacy & S.A.L.T.S Policy Update** * The change to our [S.A.L.T.S](/ritabot-docs/policys/s.a.l.t.s-policy.md) and [Refund](/ritabot-docs/policys/refund-policy.md) 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 [Privacy](/ritabot-docs/policys/privacy-policy.md) 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 [Refund](/ritabot-docs/policys/refund-policy.md) 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 [Refund](/ritabot-docs/policys/refund-policy.md) Policy. * Right-to-exit requests are limited to the scope of 3 months from the dated change of the [Privacy](/ritabot-docs/policys/privacy-policy.md) 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 [**Discord Server**](https://discord.gg/mgNR64R) in a support ticket or by sending an email to [**stripe@ritabot.gg**](mailto:stripe@ritabot.gg) * Further clarification of changes can be provided upon request. *** **15/08/23 S.A.L.T.S Policy Update** * The change to our [S.A.L.T.S](/ritabot-docs/policys/s.a.l.t.s-policy.md) 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 [Privacy](/ritabot-docs/policys/privacy-policy.md), [S.A.L.T.S](/ritabot-docs/policys/s.a.l.t.s-policy.md) and [Refund](/ritabot-docs/policys/refund-policy.md) Policy's 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. * Change to soft Limits defined in [S.A.L.T.S Policy #Limitations](/ritabot-docs/policys/s.a.l.t.s-policy.md#limitations) may constitute a Right-to-Exit, all cases and claims will be reviewed on case-by-case basis if raised. Accepted claims must be raised within 30 days from the dated change of policy, after which, further claims will not constitute a Right-to-Exit and claims will be denied. * Please email with details of your case/claim and we will review. * Please allow 48 hours for a response * Requesting a chargeback or refund from your payment provider will be managed under our [Refund Policy](/ritabot-docs/policys/refund-policy.md) * 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 [Privacy](/ritabot-docs/policys/privacy-policy.md) and [S.A.L.T.S](/ritabot-docs/policys/s.a.l.t.s-policy.md) 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 with details of your case/claim and we will review. * Please allow 48 hours for a response * Requesting a chargeback or refund from your payment provider will be managed under our [Refund Policy](/ritabot-docs/policys/refund-policy.md) * Further clarification of changes can be provided upon request. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ritabot.gg/ritabot-docs/policys/right-to-exit.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.