Acceptable use

This applies to everyone using Ringfully through your account, and to everything sent or received with it. It forms part of the terms of service, and your organization is responsible for the conduct of everyone it gives an account to.

Do not use Ringfully to:

1. harass, threaten, defraud or impersonate anyone;
2. record a call without the consent the law where each party is located requires — see the recording page, which is more specific than most people expect;
3. send commercial messages without consent, or ignore a request to stop;
4. disguise where a call or message came from, including presenting a number you have no right to present; or
5. break sanctions, export controls, or telecommunications law anywhere involved.

Carriers police traffic in aggregate, so what one customer sends can get a route blocked for every customer on it. This is the clause we enforce fastest.

Do not:

1. place bulk automated or pre-recorded calls, or run a dialler through the service;
2. send bulk unsolicited messaging, or send at a volume or pattern that reads as a campaign rather than a conversation;
3. rotate numbers to evade filtering, or spread traffic across numbers for the same purpose; or
4. send content in categories carriers block outright — in North America that generally covers high-interest lending, cannabis, firearms and gambling, whatever the law where you are says.

We may suspend messaging or calling immediately, without notice, under this clause. Not because your traffic is necessarily wrong, but because the alternative is every other customer losing their phone service while it is investigated.

Do not dial 9-1-1 to test anything, ever. A test call occupies a dispatcher and a line someone else may need at that moment, and it is an offence in most places.

9-3-3 is the emergency-services test number and the only one that may be used to check this path. It is off by default on every account. The emergency calling page sets out what does and does not work.

Do not attempt to reach another organization’s data, probe or scan the service beyond your own account, decompile or reverse-engineer it, get round rate limits or the spend ceiling, or resell it.

Genuine security research is welcome and is covered by the vulnerability disclosure policy, which says what is in scope and offers safe harbour for staying inside it. Note that there is no public API to test — the only interfaces are the ones the softphone and console use.

Do not use Ringfully for protected health information, or for anything requiring HIPAA or PCI-certified handling. We hold no certification for either, and would not be able to sign an agreement saying we do.

Do not make it anyone’s only means of reaching emergency services. That is a requirement, not advice.

Usually we will tell you and ask you to fix it. Where continuing would break the law, put other customers’ service at risk, or where a carrier requires it, we may suspend part or all of the account first and discuss it afterwards. Repeated or deliberate breach ends the agreement.

To report misuse of Ringfully by someone else, write to [TBD] with the number and the time, and we will look into it.