Anti-Spam Policy

Last updated: November 2022

This anti-spam policy (“Anti-Spam Policy”) sets out the obligations of the Client using the Service provided by otp.dev and the rights of the recipient of the message that is sent by the Client using the Service (“Message Recipient”). All and every term, unless specifically defined herein, is being used in the meaning of the Terms of Service available here.

otp.dev does not tolerate spam messages. Any message that does not contain relevant information that the Message Recipient subscribed for, is sent without the Message Recipient’s consent if the applicable legislation requires it, is unprompted, and/or is sent by unauthorized users of otp.dev's system will be considered spam (e.g. unsolicited and unauthorized advertising, promotion, junk mail, chain letters, pyramid, and other similar schemes). The prohibited content described in this Anti-Spam Policy is not exhaustive. Depending on where the Service is used, additional local legislation concerning spam may apply. It is the Client’s responsibility to comply with the applicable legislation.

Depending on where the Service is used, additional local legislation concerning spam may apply. It is the Client’s responsibility to comply with the applicable legislation.

The Client’s obligations

The Client, once it has accepted the Terms of Service, is obliged by the Terms of Service not to abuse otp.dev's system for spamming purposes. Violation of the Terms of Service (including the terms of this Anti-Spam Policy) can result in the termination of the provision of the Service or the Client’s Account.

Among other things, the aforementioned also includes the following prohibitions. Client shall not:

Use harvested phone numbers/contact lists;
Use third-party, purchased, or rented phone number/contact lists, unless the Client is able to provide proof that all of the individuals on the list have affirmatively opted in to receiving messages of the type the Client will be sending to them;
Collect phone numbers/contacts from the web by scanning or other similar means

According to the Terms of Service, otp.dev has the right to screen text messages sent using the Service for purposes of preventing prohibited behavior (including spamming) and reserves the right to intervene if deemed necessary. Text messages that are unsolicited, irrelevant, or otherwise fall under otp.dev's definition of spam, will not be delivered to the Message Recipient. otp.dev can give the Client an opportunity to revise the original message so that it would be compliant with the Terms of Service, and it could be delivered to the Message Recipient.

The Client agrees to fulfill requirements set out in applicable legislation, including incorporating an opt-out and/or opt-in mechanism when required. The request to opt out should be dealt with by the Client within 10 calendar days from the date of such request by the Message Recipient.

The Message Recipient’s Rights

Opt-Out/Unsubscribe

It is in otp.dev's best interests to keep the Message Recipient happy and content with the messages sent using the Service. The Message Recipient can opt out/unsubscribe from the messages sent by the Client at any time.

Report Spam/Abuse

If the Message Recipient believes any text message sent to its phone number to be spam or something it did not sign up for (i.e., unrelated content) or from a number the Message Recipient does not recall subscribing to (i.e., unsolicited content), they should not hesitate to contact otp.dev immediately by e-mail info@otp.dev.com. These notifications should include details such as the Sender ID (sender’s phone number if available), the Message Recipient’s mobile phone number, the content of the message, and the date and time of the received text message.

Once otp.dev receives the complaint, it will conduct an investigation of the case and the reported Client to determine the legitimacy of the complaint and what course of action to take. Regardless of the outcome, the Message Recipient’s phone number will be removed from the potentially abusing Client’s list to avoid future inconveniences (i.e., no messages from the potentially abusing Client will be delivered to the reporting Message Recipient). The whole process will remain confidential to avoid revealing any identifying information about both the Message Recipient and the reported Client.