Consent and opt-in

ComplianceDraft — not publishedUpdated 2026-07-26

Consent in Arino One is stored per contact, per channel and per purpose, with the source, timestamp and the wording shown at capture. It is enforced at send time, not at segment-build time.

What is recorded

  • Channel (WhatsApp, SMS, email, RCS) and purpose (transactional, marketing).
  • Capture source — QR opt-in, web form, imported record, inbound keyword.
  • Timestamp and the exact consent text displayed.

Withdrawal

Inbound STOP-style keywords and unsubscribe clicks write an opt-out immediately, and the contact drops out of marketing sends on that channel from that moment.

Imported contacts

An import must carry its own consent evidence. Importing a list with no source and no timestamp gives you a contact you cannot lawfully market to.

Next step

Bring this to your enterprise stack

See how a dedicated Arino One instance — deployed in your region (EU, NA or APAC) — would sit inside your operation. Architecture, DPA, and rollout plan walked through live.