Messaging Terms

Last updated: August 1, 2026

These terms explain the messages involved in NomVote Route 1: a phone verification code that you request, push notifications that you separately enable, and invitation or result links a host chooses to share. Voting through an invitation link does not require verification, installation, or notification permission.

1. Phone Verification Messages

If you explicitly ask to verify a phone number, Google Firebase Authentication may send a one-time verification code. A retry can send another code, subject to provider and NomVote abuse limits. Message and data rates may apply. Requesting or entering a verification code proves control of that number; it does not consent to invitation, decision, marketing, or recurring text messages.

2. Invitations and Results

NomVote does not currently send automated Route 1 invitation or final-decision SMS messages. A host can copy a link or open an operating-system share or messaging screen and choose recipients. NomVote prepares the link; it does not know whether the host completed the send or whether a carrier delivered it.

If a host selects a group conversation or sends one message to multiple recipients, their messaging app may expose the recipients' phone numbers to one another. Hosts should use individual messages when that privacy tradeoff matters.

      Selected, prepared, provider accepted, delivered, opened, joined, and voted are
      different states. Opening a share screen is not proof that a message was sent.
    

3. Push Notifications

After verifying an installed app or PWA, you may separately enable push notifications. Push permission is optional and can be turned off in NomVote or browser/Android settings. NomVote first tries native push for a registered app, then Web Push for a verified installed PWA only after native endpoints are definitively unavailable, and otherwise leaves an explicit manual-share recovery. An accepted or unknown provider result does not silently fall through to another automated channel. There is no SMS fallback.

4. Providers and Privacy

Google Firebase processes phone verification and native push. Browser or operating-system push services process Web Push subscriptions. Your selected messaging app and carrier process a host-shared message. Twilio is not used for Route 1 verification, invitations, decisions, or fallback. See the NomVote Privacy Policy for stored data, retention, deletion, and provider details.

5. Unwanted Invitations, Opt-out, and Support

If a person shares an invitation you did not expect, you can ignore the link; opening or ignoring it creates no recurring SMS enrollment. Because Route 1 has no automated invitation-text program, STOP/START keyword claims do not apply to it. Use notification settings to disable push, or ask the sender not to contact you. For help or an unwanted-invitation report, email privacy@nomvote.com.

6. Changes

We may update these terms as the implemented message channels change. Any future automated SMS program would require a separate consent flow, suppression behavior, provider/compliance approval, and updated terms before activation. The date above identifies the current published version.