SMS Opt-in Policy

1. Program details

Sender: Jorik, operated by Eesha Solutions LLC, North Carolina, United States.

Short-code scope: this is a recurring US short-code program proposed for supported US carrier networks. The short code is pending assignment and approval; no number is invented or implied to be live. Eesha Solutions LLC controls message content, approved templates, and sending rules. Jorik users cannot compose arbitrary SMS or use this program to send unconsented invitations.

Recipients: designated emergency contacts who personally and affirmatively agree to Jorik SMS. A Jorik account holder cannot consent on behalf of another contact simply by entering their phone number.

Content and frequency: service-only contact confirmations, missed-check-in notifications, last authorized location, and related service updates. Frequency varies with enrollment and the app user’s check-in activity. Message and data rates may apply. Messages may be sent using automated technology.

Safety limits: a missed check-in does not prove an emergency. Location may be old or inaccurate, and delivery or response cannot be guaranteed. Jorik does not replace emergency services or dispatch emergency responders. Call 911 or the appropriate local emergency number when necessary.

2. Required opt-in flow in Jorik

1. Designation is pending. A user identifies a proposed emergency contact in Jorik. Entering that number does not enable SMS or count as consent.
2. The recipient receives a consent link without an unsolicited SMS. The user can share the link through their own communication channel. Jorik must not text an invitation or designation notice to an unconsented recipient. Any SMS-based invitation requires the recipient’s prior consent for that message.
3. The recipient reviews the program. The Jorik consent screen identifies the app user, Jorik and Eesha Solutions LLC, the message types, frequency, rates, STOP/HELP instructions, optional nature of consent, and links to these Terms & Conditions and Privacy Policy.
4. The recipient actively agrees. The recipient provides or confirms their own number, selects a separate, initially unchecked SMS checkbox, and submits the consent action. The app must verify that the consenting recipient is authorized to use the number. Any verification text itself requires appropriate prior consent.
5. Consent is recorded and enrollment confirmed. The app stores the consent evidence, completes required number verification, and sends one enrollment-confirmation SMS before any recurring program alerts. The confirmation must identify Jorik Emergency Contact Alerts and include frequency, rates, HELP, and STOP information. The confirmation is required for this recurring program, not an optional extra.
6. Permission remains revocable. STOP and other valid revocations must disable further program texts, apart from a permitted single opt-out confirmation. New messages require a new valid opt-in. Other apps and email notifications must not inherit SMS consent automatically.

No passive opt-in. Silence, a preselected checkbox, acceptance of general terms, an app user’s nomination, or failure to opt out does not establish a contact’s SMS consent. There must be a clear way to decline.

Number verification (recommended design). After the contact personally requests verification and agrees to receive that verification text, send a one-time code for entry in the enrollment screen. Do not enable recurring alerts until verification and the separate program opt-in are complete. Double opt-in is not universally mandatory under CTIA guidelines, but recipient-controlled number verification is an appropriate safeguard for this contact-designation flow and is subject to provider review.

3. Proposed consent wording

The following is proposed wording for the Jorik consent screen, not a working signup control:

The screen must identify the relevant Jorik user before submission and include info@eeshasolutions.com for support. Do not bundle this checkbox with unrelated permissions, preselect it, or treat agreement to these documents as the checkbox’s affirmative selection.

View the proposed visual consent screen → The mockup includes the separate unchecked checkbox, support contact, disclosure text, policy links, and disabled demonstration controls. It neither enrolls recipients nor proves anyone’s consent.

4. What constitutes opt-in evidence

Current evidence status: no implemented Jorik opt-in screen or screenshots have been supplied. This policy is a description of the planned flow, not proof that a particular contact has enrolled.

Before sending program texts, retain recipient-specific evidence showing:

• The recipient’s authorized phone number and the specific program and app user association.
• The date and time, method of consent, and exact disclosure text or version presented.
• The recipient’s affirmative action, such as selecting the unchecked SMS checkbox and submitting it.
• Number authorization or verification evidence where applicable.
• Any later consent changes, revocations, suppression status, and valid renewed consent.

For short-code application review, supply the clearly labeled proposed visual mockup or an authentic screenshot of the implemented screen showing the unchecked checkbox, disclosure text, policy links, and submit action. Twilio accepts application mockups of planned screens, but a written description alone is insufficient. Do not portray a proposed screen as deployed or fabricate recipient consent. Actual recipient-specific records must be kept securely, not published on this page.

Evidence must be retained for applicable legal and provider requirements, including while relied upon for messaging. Minimal suppression records may remain after opt-out to prevent further unwanted texts. This website does not currently collect or store these records for Jorik.

5. Illustrative messages after valid consent

These are examples, not messages that have already been sent. Actual messages must identify Jorik and reflect the recipient’s authorized program.

In a real alert, include the authorized user identifier and actual last-location details or a secure location link, with the location timestamp when available. If location is unavailable, say so; never invent coordinates or imply that old data is a live location.

Square brackets mark real event data to substitute in approved templates; they are not invented events or consent. Submit representative test-rendered examples to Twilio if requested. If verification messages share the short code, disclose and obtain approval for that message type too.

6. Opt-out, help, and delivery

You can cancel at any time by texting STOP to the Jorik short code that sent the message. The service will send one unsubscribe confirmation and no further program texts unless you complete a new valid opt-in. Rejoin by completing the recipient enrollment process again.

Recognize STOP, END, CANCEL, UNSUBSCRIBE, and QUIT, as well as other standard keywords and reasonable revocations. You may email info@eeshasolutions.com with “SMS opt-out” and the relevant number.

Help: reply HELP to an active program message, or email info@eeshasolutions.com. STOP/HELP replies become available only when the SMS program is active; this policy page itself does not receive text replies.

Short-code handling requirement: HELP and STOP responses must work for subscribed and unsubscribed senders. A requested HELP or STOP reply is not new consent. Twilio does not manage short-code keywords or opt-out blocking by default. Before launch, implement application handlers and a program-wide suppression list, or configure and verify Twilio Messaging Services Advanced Opt-Out with compliant responses. Do not assume the short code already has this protection.

The implemented program must check suppression before every send, including queued alerts, and block messages across all contacts and app users associated with the same recipient in this program. Apart from requested compliance replies, no further texts may be sent after opt-out without a new valid opt-in. Opting out stops Jorik SMS, including missed-check-in alerts, but does not itself close an account. Notify the app user through an appropriate available channel so they can make other safety arrangements; never send another alert to the opted-out contact for that purpose.

Tell us if you change or give up an enrolled number. Reassigned and deactivated numbers must be addressed before further sends. Delivery depends on devices, networks, and carriers. Carriers are not liable for delayed or undelivered messages, subject to applicable law. Message and data rates may apply to incoming and outgoing messages; consult your wireless provider about your plan.

7. Privacy, eligibility, and contact

Mobile numbers, SMS opt-in information, and consent records are not sold, rented, or shared with third parties or affiliates for marketing or promotional purposes. Restricted messaging and support providers may process information only as needed for service delivery, lawful consent or suppression records, and legal obligations. See the Privacy Policy.

No blanket numerical age minimum is imposed here. Participation requires legally valid consent, any required parent or guardian involvement, children’s privacy safeguards, and compliance with applicable messaging-provider rules. These requirements must be satisfied before enrollment.

Eesha Solutions LLC
Charlotte, North Carolina, United States
Email: info@eeshasolutions.com