RAINCLOUD asks for more access than most vendors: your CRM, and authority over sending domains. This page sets out what is asked for, why, where the work runs and who can touch it. It is a plain statement from a one-operator firm, not a certification.
All four are due within ten business days of signature. Nothing beyond them is required to run the program.
RAINCLOUD builds on your CRM, your domains, your mailboxes and your website. Your pipeline is not moved into a platform RAINCLOUD owns. The domains are registered in your company’s name, the content publishes on your domain, and the records stay in your CRM.
Access covers what the program needs and no more. RAINCLOUD writes only the fields it needs and does not administer your CRM beyond them. Where your CRM supports it, the simplest setup is a dedicated user with only the permissions the work needs, which you can review or revoke at any time.
Before anything goes out, it is checked against the live CRM. Suppressed: current customers, open opportunities, accounts a rep touched in the last 30 days, opt-outs and negative replies (for good), competitors, partners, investors and the board, current and former employees, and anyone another lane touched in the last 90 days.
LinkedIn is draft-and-approve only. RAINCLOUD writes the message. Your rep reviews it and presses send.
The engagement is run by Colin Dowling, with the systems he builds and runs for it. There is no pooled delivery team. That is part of why RAINCLOUD takes four clients at a time.
RAINCLOUD does not publish a SOC 2 report, an ISO 27001 certificate or any other third-party security attestation. If your security review uses a questionnaire, send it before signature and it will be answered in writing.
If you believe something RAINCLOUD runs has exposed data, or you have found a vulnerability, email [email protected] with “Security” in the subject line.
Last updated November 14, 2026.