MotoPin
SMS Messaging Consent & Opt-In Policy
How we collect verifiable consent before sending any text message
MotoPin
SMS Messaging Consent & Opt-In Policy
How we collect verifiable consent before sending any text messageThis page documents how MotoPin collects opt-in consent from every person before sending them a single SMS message, the types of messages we send, and how anyone can opt out at any time. It exists so our messaging program is fully transparent to our users and to our messaging providers and carriers.
MotoPin uses SMS double opt-in. When a rider adds an emergency
contact, that contact receives one opt-in request explicitly asking them to agree to receive text
messages, and nothing else is ever sent unless they reply YES.
Our backend hard-blocks every outbound alert to any number whose consent status is not
confirmed, and logs an immutable audit record for every opt-in, confirmation,
and opt-out. This program sends transactional safety alerts only — never marketing.
Program name: MotoPin Safety Alerts
Operated by: Oxigenic Inc. (MotoPin)
What MotoPin is: a motorcycle ride-safety app. A rider starts a ride in the app and the people they choose — their emergency contacts — are notified if the ride ends safely, if the rider triggers an SOS, or if a possible crash is detected and the rider is unresponsive.
Message types (transactional safety alerts): ride-status and crash/SOS alerts, plus a one-time confirmation message when someone is added as an emergency contact. We do not send marketing or promotional texts through this program.
Message frequency: recurring, event-based — messages are sent only when a ride event occurs, so volume varies by how often the rider rides.
The people who receive text messages from this program are the rider's emergency contacts. Consent is collected directly from each message recipient, over SMS, before any alert is ever sent — a rider cannot consent on a contact's behalf.
When a rider adds an emergency contact, MotoPin sends that contact one opt-in request that explicitly asks them to agree to receive text messages. We deliver safety alerts only to contacts who reply YES. Until they do, their status stays pending and our system blocks every message. Anyone can reply STOP at any time to opt out immediately and receive no further messages.
The one and only message sent before consent is confirmed.
Only after the recipient replies YES does their status become confirmed and alerts are enabled.
When a rider on a plan that includes SMS alerts adds a new emergency contact by phone number, they must actively check an unchecked acknowledgment box in the app. The box is never pre-checked, and checking it is not a condition of using unrelated parts of the app. This acknowledgment informs the rider about the texts their contacts will receive — it does not substitute for the contact's own consent, which is always collected directly from the contact by SMS as shown above. On plans without SMS alerts no text messages are sent at all — neither alerts nor the opt-in request — and the opt-in request is only sent if the rider later moves to a plan that includes SMS alerts. Whether or not a particular in-app path shows this acknowledgment, the contact-side flow never changes: every number that will receive alerts first receives the same opt-in request and is texted safety alerts only after replying YES.
Once — and only once — a contact has replied YES, they may receive event-based safety alerts like these during a ride:
Sample alert messages. Every one carries the MotoPin identity; recipients can reply STOP at any time.
Recipients can opt out at any time by replying STOP to any message; we will send no further texts to that number. Reply START to opt back in. Reply HELP for help, or contact us at support@oxigenic.com. Opt-out requests are honored immediately and recorded in our consent audit log.
No mobile information is shared with third parties or affiliates for marketing or promotional purposes. Phone numbers collected for this messaging program are used solely to deliver the safety alerts described above and are not sold or shared, except with the service providers (such as our SMS carrier) that are strictly necessary to deliver these messages.
For full details, see our Privacy Policy and Terms of Service.