Let customers choose how you reach them

Your marketing platform stores preferences. Fyno enforces them. When a customer opts out of SMS in your marketing tool, the opt-out is recorded in a database. But if another system, a different LoB, or a triggered workflow sends a message through a different path, that preference may not be checked. Fyno enforces preferences at the routing layer, meaning every message, from every source, is validated against the customer's current preferences before dispatch. The enforcement is not optional and cannot be bypassed by upstream systems.

Both. Fyno supports two tiers of consent. At the channel level, customers can opt in or out of SMS, WhatsApp, email, push, and in-app independently. At the topic level, customers can subscribe or unsubscribe from specific communication categories: marketing updates, product announcements, account alerts, regulatory notices. Topics are classified as soft (customer can unsubscribe) or hard (mandatory, such as regulatory notices). A customer might receive transaction alerts on all channels but marketing updates only via email.

Fyno provides native SDKs for iOS, Android, and web. The preference centre runs inside your app with your branding. No Fyno branding is visible to end users. Once a customer's distinct ID is registered, the SDK captures preferences directly and syncs them with Fyno's routing engine. Your backend does not need to pass channel-specific details with every API call. Fyno retrieves the latest preferences automatically at send time.

The preference change takes effect immediately at the routing layer. Even if a campaign segment was built an hour ago and the send is in progress, Fyno validates each individual message against the customer's current preference state before dispatch. If the customer opted out of SMS between segment build and send, the SMS is suppressed for that customer. This real-time enforcement is what distinguishes Fyno from systems that check consent only at segmentation time.

DPDP requires that consent be tied to a specific communication purpose, not a blanket opt-in. Fyno tracks consent per purpose: marketing, transactional, service, regulatory. Each message is tagged with its purpose at the template level. Before sending, Fyno validates that the customer has active consent for that specific purpose on that specific channel. The audit trail links every send to the consent record that authorised it, providing evidence for any Data Protection Board inquiry.

Yes. Fyno supports configurable frequency caps per customer, such as a maximum of four to eight notifications per ten-day window. Do-Not-Disturb windows prevent marketing messages from being sent after defined hours, typically 8 PM. DLT categorisation is enforced during template creation, and the routing engine applies different consent rules based on whether a message is classified as Service Explicit, Service Implicit, or Transactional. This prevents marketing messages from being accidentally sent as transactional to bypass DND restrictions.

Retention is configurable. The default is 7 days of real-time logs plus 6 months of archival logs. For RBI compliance, retention can be extended to 7+ years. Every preference change is logged with a full audit trail showing who changed what, when, and through which interface. Maker-checker approval workflows apply to consent policy changes, ensuring that modifications to default channel configurations go through governance before taking effect.