Integrations & Connected Accounts

Effective date: 22 June 2026

This notice explains what happens when you connect an account you own — a mailbox, a spreadsheet, a messaging workspace, a CRM — to RAiN AI Studio, so that an agent can work in it on your behalf. It forms part of our Terms of Service and should be read with our Privacy Policy.

You are asked to accept it at the moment you connect an account, because that is the moment it matters.

1. What connecting does

Connecting sends you to the service's own sign-in and consent screen. You choose whether to grant access, and to what. If you agree, that service issues an authorisation — not your password — which allows the actions you approved.

An agent you configure can then use that authorisation to act: reading a message, writing a row, sending a reply. It may do so automatically, on a schedule, and while nobody is watching. That is the purpose of the product, and it is worth being deliberate about which accounts you connect and what you allow.

2. Who holds the authorisation

RAiN uses a third-party integration provider to create and store these authorisations on our instructions. We do not receive or store your password for a connected service, and we do not hold the authorisation ourselves.

This means a token permitting access to your account is held by a provider outside Rivium Analytics, under their security practices and their terms, and may be processed outside Nigeria. We choose providers we consider reputable, and we require that they process this data only on our instructions.

We may change provider. If we do, or if we move this function in-house, the existing authorisations cannot be transferred — you would be asked to connect your accounts again. We will tell you before that happens.

3. What an agent may do

An agent can only perform the actions RAiN exposes for that integration, using the permissions you approved. We deliberately expose a limited set of actions rather than everything a service allows.

You remain responsible for what you instruct an agent to do, and for the consequences of it — including messages it sends, records it changes, and decisions taken from its output. Review an agent's behaviour before connecting it to anything that matters, and use the send limits and approval steps the Studio provides.

4. Where an expert connects a business's account

Where an expert connects an account belonging to a business they are working for, the business remains responsible for that account. The expert acts on that business's instruction. Both should be satisfied that the access granted is no wider than the work requires.

5. Content that passes through

To perform a task, an agent may read content from a connected account and send it to the AI model provider selected for that project. Content is processed to produce the result you asked for. Traces of a run — the steps taken and the outputs produced — are stored so that you can inspect what happened.

6. Revoking

You can disconnect an account in RAiN at any time. You can also revoke access from the service's own security settings, which works even if you no longer use RAiN. Revoking stops future runs from acting on that account; it does not undo actions already taken.

7. Availability

Third-party services change, restrict, or withdraw their interfaces without notice to us. An integration may stop working, change behaviour, or be removed. We do not control those services and cannot guarantee their availability, and their own terms govern your use of them.

8. Contact

Questions about this notice: support@rain.com.ng.