Lafrancian Enterprises

Consent documentation

Consent is explicit and phone-specific.

This page is a public, non-interactive representation of the authenticated Crewenda SMS consent workflow. It does not collect information or enroll website visitors.

Effective September 21, 2026

1. Non-interactive representation

Inside Crewenda, an authorized organization administrator enters or verifies the mobile number of an authenticated user. SMS remains off until the mobile-number owner separately agrees to the disclosure and the administrator records the evidence source.

Crewenda · People administration Public example only

This disabled example cannot submit data or record consent.

2. The authenticated consent flow

  1. An organization invites a person to an authenticated Crewenda account. Account creation and application access do not require SMS.
  2. An authorized organization administrator enters or verifies the user’s current mobile number in the People administration workflow.
  3. Crewenda shows a separate SMS preference and consent attestation. They begin unchecked and are separate from acceptance of the Terms of Service.
  4. The mobile-number owner is shown the operational message categories and the recurring-messages, variable-frequency, message-and-data-rates, STOP, HELP, and optional-consent disclosures.
  5. Only after the mobile-number owner explicitly agrees does the administrator select the evidence source and affirm the separate consent control. Server-side validation rejects SMS enablement without both.

3. What Crewenda records

Crewenda stores an append-only consent event that identifies the organization, user, normalized mobile number, event type, timestamp, evidence source, disclosure version, actor, and operation identifier. The record connects the current permission to the specific mobile number and disclosure presented.

Changing the mobile number invalidates the earlier permission for sending to the new number. Fresh consent is required.

4. Checks before each message

Before attempting delivery, Crewenda checks that messaging is enabled, the current mobile number matches the consent record, the latest effective consent permits sending, and the recipient’s preference remains enabled. The application record remains authoritative if delivery is delayed or fails.

Crewenda sends only bounded operational templates. Participating organizations may supply tenant-scoped context such as company, project, date, or start time; they cannot author free-form broadcasts through this program.

5. Withdrawal and re-enrollment

Reply STOP to opt out. Crewenda disables the SMS preference when provider suppression is reported or when a manual opt-out is recorded.

START or UNSTOP may remove provider-level suppression where supported, but does not silently re-enable Crewenda. The mobile-number owner must explicitly request re-enrollment, and Crewenda must record a fresh opt-in event for the current number before messages resume.

For help, reply HELP, visit lafrancian.com/contact, or email kajlafrancian@gmail.com.