This page documents, publicly and in one place, every way a member can come to receive text messages from an organization using SynaiConnect, and what each of those ways looks like. It is written to be verifiable: section 2 reproduces the actual consent control rather than describing it.
1.Who sends the messages
SynaiConnect is a platform used by churches and community organizations. The organization is the sender — each one registers its own messaging campaign, uses its own phone number, and messages only its own members. We provide the software; we do not send messages of our own to an organization’s members, and organizations never message each other’s members.
Nothing on this platform sends marketing or promotional text messages. The traffic is informational: service times and changes, event announcements, prayer requests, and volunteer coordination.
2.How a member opts in
Members are invited by their organization and receive an email link to create their password. That screen is where consent is given. The messaging consent control is separate from accepting the Terms and Privacy Policy, is unchecked by default, and is never required — the account is created whether or not the member ticks it, and it is only shown to members who have a phone number on file.
As it appears to the member
“Grace Community Church” and the number above are placeholders. In the real screen both are the member’s own organization and their own number, and the box is empty until the member ticks it.
Ticking it records the consent against that member with the method member_form and the moment it was given. Leaving it unticked records nothing at all.
3.Opting in by text
A member who knows their organization’s number can text START to it. Our messaging provider resumes delivery at the network level, and we record the opt-in against that member with the method keyword_start and the moment it arrived. The same applies to a member who had previously replied STOP — texting START opts them back in.
Because the text is sent to one organization’s own number, it only ever affects that member’s relationship with that organization. It cannot opt them in to, or out of, any other organization on the platform.
4.Consent an organization collected itself
Many organizations already hold written or verbal consent gathered outside this platform — a membership form, a sign-up sheet, a conversation, or their own website — for members they then add here by hand or import from a file. Those members never saw the control in section 2.
For those people the organization must confirm, at the moment it adds them, that it already obtained their consent. That confirmation is an explicit, unticked checkbox on both the add-a-person form and the file import, it is only offered where a phone number is present, and it is recorded per member with the method org_attested. Our Terms and Conditions make obtaining that consent, and honouring opt-outs, the organization’s responsibility as the sender.
An organization re-importing its directory cannot use this to overwrite a member’s own consent, and cannot use it to re-add consent for someone who has opted out.
5.Opting out, and getting help
Reply STOP to any message to stop receiving them. Opt-outs are processed by our messaging provider at the network level, so they take effect immediately for that number and do not depend on anyone at the organization acting on them. We also record the opt-out against the member, so the organization’s own directory shows it and our sending stops selecting them — the carrier’s decision and ours cannot drift apart. Reply HELP to any message for help information.
A member can also ask their organization to remove their number, or write to us at office@synaiconnect.com. Opting out of text messages does not close the member’s account or stop email and in-app notifications, which are separate.
6.What we do with the number
Mobile phone numbers and SMS consent data are not shared, sold, rented or otherwise provided to third parties or affiliates for marketing or promotional purposes. The only third parties that receive a number are the ones required to deliver a message the member asked for: our messaging provider and the member’s own mobile carrier. Section 10 of our Privacy Policy sets this out in full, along with everything else we hold about text messaging.