Privacy Policy

Last updated: June 19, 2026

This policy applies to SAFE918's website, in-person enrollment, volunteer onboarding, and all SMS messaging programs operated under the SAFE918 brand registered under A2P 10DLC.

Who we are

SAFE918 is a 501(c)(3) nonprofit harm reduction program serving Washington County, Oklahoma and the surrounding region. We are a state-registered harm reduction site under Oklahoma SB 511 and operate in coordination with the Oklahoma State Department of Health (OSDH). When we say “we,” “us,” or “SAFE918,” we mean SAFE918 and its volunteers acting on its behalf.

For privacy reasons, some of our mailings and emails go out under the name 918 Resources — including packages addressed from 918 Resources, emails from @918resources.org, and the tracking page at track.918resources.org. 918 Resources is operated by SAFE918; this policy applies equally to anything you receive under either name.

Information we collect, use, and share

Information we collect

We try to collect as little as possible. Depending on which part of our program you use, we may collect:

  • Order information for SAFEKits: a name or alias of your choice, mobile phone number, and a pickup location or mailing address.
  • Volunteer information: name, contact info, role interest, and any background or scheduling information you choose to share.
  • Online donation information: online donations are not currently processed through this application. If online donations return, this policy should be updated before that flow goes live.
  • Conversation data from SAFEBot: the answers you submit during a chat flow, stored alongside the order or volunteer record they belong to.
  • SMS request/contact data: phone numbers and request context submitted in order, volunteer, or callback flows. The current application stores this in the related order, volunteer, request, or bot conversation record; it does not maintain a separate SMS-consent evidence table with IP address, user-agent, campaign identifier, and verbatim consent text fields.
  • Usage analytics: anonymized event data (page views, button clicks, bot-step completion) via PostHog, used to understand which flows work and which break. Not linked to identifying program data.

What we do not collect

We do not require government ID, immigration status, insurance information, or proof of address. We do not collect Social Security numbers. We do not record drug use history except where you voluntarily share it as part of a kit request.

How we use information

  • To fulfill SAFEKit orders and send pickup or shipping updates.
  • To coordinate volunteer scheduling, training, and shift logistics.
  • To prepare aggregate, de-identified program reports required by OSDH under SB 511. These reports do not include individual participant identifiers.
  • To improve the site and bot, using anonymized analytics.

How we share information

We never sell your information. We share it only with:

  • Service providers who help us run the program, strictly to the extent needed to provide their service: Twilio (SMS delivery), our hosting and email providers, and PostHog (anonymized analytics).
  • Government reporting required by SB 511 and related Oklahoma law, in aggregate de-identified form.
  • Legal process, if compelled by a valid subpoena or court order. We will resist over-broad requests where we reasonably can.

SMS messages

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All categories of personal information will be subject to the SAFE918 Privacy Policy. Information sharing to subcontractors in support of services provided by SAFE918 (e.g., SMS delivery via Twilio) is permitted strictly to provide the requested service. None of this information will be shared with any third parties for their own marketing or promotional purposes.

We use SMS only for program-related communications that are wired in this application: order confirmations, order-ready and order-shipped notices, HELP replies, and volunteer/internal coordination alerts where configured. We do not use the program SMS number for marketing, fundraising solicitations, third-party content, or affiliate offers.

Who we message and why

SAFE918 SMS is sent to two recipient groups in the current code:

  1. Program participants — people who provide a phone number in an order or callback flow. Messages cover order confirmation, pickup-ready, order-shipped, callback, and HELP responses.
  2. Internal staff/volunteer recipients — the configured Pamala/internal number receives operational alerts where the relevant environment variable is configured.

The database does not currently store separate SMS campaign consent records or campaign-scoped opt-out records.

How we obtain consent

The online flows show SMS disclosure language before a user submits a phone number for a callback, kit order, or volunteer request. In the current codebase, that consent context is stored with the related request/order/volunteer/bot records rather than in a dedicated consent-audit table. Paper forms or documented phone-call consent, if used operationally, are outside this application.

“By providing your phone number, you consent to receive a transactional SMS from SAFE918 about this request. Message and data rates may apply. Reply STOP to opt out, HELP for help.”

Frequency, cost, and opt-out

Frequency. Message frequency varies based on your interaction with the program. The wired customer-facing templates are transactional order/callback messages; volunteer coordination messages are sent only where configured.

Cost. Message and data rates may apply. SAFE918 does not charge for messages, but your mobile carrier may.

Opting out. Reply STOP, UNSUBSCRIBE, CANCEL, END, or QUIT to any SAFE918 message to be removed from program SMS where the Twilio/carrier opt-out controls are active. Reply HELP for help and program contact information. Carriers are not liable for delayed or undelivered messages.

US carrier registration (A2P 10DLC)

The codebase sends SMS through Twilio from the configured SAFE918 phone number. Carrier/TCR campaign registration and provider-side suppression lists live outside this repository. We do not share opt-in data or phone numbers with any third party for marketing or affiliate purposes. Sharing is restricted to what is required to deliver requested messages.

Opt-in evidence we retain

Current code-backed records may include the following, depending on the flow used:

  • Phone number submitted in an order, volunteer, or request flow
  • Order legal acknowledgement and timestamp where collected
  • Bot conversation messages and timestamps while the conversation record exists
  • Request status and internal notes added by administrators

The current schema does not include a standalone SMS-consent record with IP address, browser identifier, campaign identifier, and verbatim consent text.

Embedded links and phone numbers

The wired SMS templates currently include plain text order confirmations, pickup-ready notices, shipped notices, and HELP replies. They do not include URL shorteners in this codebase.

Retention

Order, volunteer, request, and inventory records remain in the database until an administrator or future retention workflow changes them. Bot conversations have an expiration timestamp; the repository includes a cleanup helper for expired bot conversations, but no scheduled cleanup job is configured in this codebase. Online donations are not currently processed by this application. You can request deletion at any time; see “Your rights” below.

Your rights

You can ask us at any time what we have on file about you, correct it, or ask us to delete it. We honor deletion requests except where retention is required by law or needed for program operations. Email [email protected] or call our program line.

Security

We use industry-standard encryption in transit (HTTPS) and at rest, restrict access to program data to a small number of authorized volunteers and staff, and conduct regular review of our privacy and security procedures consistent with CTIA Messaging Principles & Best Practices §§5.2.2 and 5.2.3. No system is perfectly secure; if we become aware of a breach affecting your information, we will notify you as required by law.

Children

This site is not directed at children under 13, and we do not knowingly collect information from them. Harm reduction services may be provided to minors where lawful and clinically appropriate; consent and data handling for minors follow Oklahoma law and OSDH guidance.

Changes

We will post any changes here and update the “Last updated” date. Material changes affecting SMS consent or data sharing will be communicated to active program participants and volunteers directly.

Contact

Privacy questions, legal inquiries, or rights requests: [email protected]. SMS program help: reply HELP to any SAFE918 message, or call our program line listed in the site footer.