Suffle Online

Operated by Naucera Travel Private Limited

1. Purpose and Scope

This Subscription Policy governs paid subscription plans offered by Suffle Online for Suffle software features, including WhatsApp/Business Messaging functionality where included in a selected plan.

Subscription plans are separate from marketplace product purchases. Buying a product from the Suffle marketplace does not purchase a software/WhatsApp subscription, and purchasing a subscription does not purchase marketplace products.

This Policy supplements the Terms & Conditions, Payment Information Policy, Privacy Policy, Data Security & Protection Policy and WhatsApp / Business Messaging Policy.

2. Company and Contact

Suffle Online is operated by Naucera Travel Private Limited.

Website: www.suffleonline.com

General Support / Grievance Email: info@flyshoppy.com

Grievance Officer: Mr. Roopal Jain, Managing Director

Grievance Officer Mobile: 9707669981

Grievance Officer Email: info@flyshoppy.com

Address: 707, N. T. Road, Nalbari-781435 (Assam), India.

3. What the Subscription Covers

A Suffle subscription provides access only to the features, limits and entitlements assigned to the selected plan.

Where a plan includes WhatsApp/Business Messaging functionality, the subscription may govern access to messaging software features such as Business messaging, bulk marketing, campaigns, scheduling, templates, segmentation, AI-assisted messaging, reporting or other configured features.

Actual availability of a feature is subject to the plan configuration, Suffle system availability and applicable third-party/provider requirements.

4. Subscription Plans and Configuration

Subscription plans, features, usage limits, campaign limits and other entitlements are controlled through Suffle's central subscription system.

Super Admin may create, edit, activate, deactivate and configure plans and their rules.

Plan configuration may include subscription duration, enabled features, messaging limits, campaign limits, recipient limits, batch size, pause interval, hourly/daily limits, retry limits and safety controls where applicable.

Public-facing areas should not display subscription plan prices unless the user is appropriately logged in or otherwise authorised to view them. Subscription pricing and payment details are intended to be available within the authenticated subscription/purchase flow.

5. Subscription Eligibility

A user may purchase or activate a plan only where the account and requested feature are eligible under the configured subscription rules.

Suffle may require a valid Suffle account and, for WhatsApp features, a legitimately connected WhatsApp Business account/number as required by the applicable feature.

Subscription eligibility does not override WhatsApp, Meta, payment-provider or other applicable platform requirements.

6. Subscription Purchase

Subscription purchases are made through the Suffle subscription checkout using the configured payment flow.

Razorpay is used for Suffle subscription payment processing as configured by Suffle.

The subscription entitlement is not activated merely because a checkout page was opened, payment was attempted or a frontend success message was displayed.

7. Payment Verification and Activation

A subscription becomes active only after Suffle's backend verifies the applicable payment successfully.

Payment verification should use the configured server-side gateway verification and webhook/signature mechanisms.

Idempotency and duplicate-event protection should prevent duplicate subscription activations caused by repeated or duplicated payment events.

Where payment is failed, cancelled, expired or unverified, the subscription must not be represented as successfully activated.

8. Subscription Start Date

The subscription start date is the date/time determined by Suffle's subscription system after successful payment verification and entitlement activation, unless a separately configured activation rule applies.

Frontend checkout time, payment-link creation time or manual order creation time does not by itself establish the subscription start date.

9. Subscription Duration and Expiry

Each plan has a defined subscription duration according to its configuration, such as a specified number of days, months or one year where offered.

Once the configured subscription period expires, the associated paid entitlement must automatically become inactive unless the user has purchased/received a new valid entitlement or an authorised Super Admin has extended/activated it.

The system should calculate expiry from the authoritative subscription record rather than from frontend state.

10. No Automatic Assumption of Renewal

A subscription should not be treated as renewed unless a valid renewal/extension transaction or authorised manual activation has been recorded.

If automatic renewal is ever introduced, it must be separately disclosed and implemented with appropriate user consent and payment-provider support.

11. Subscription Statuses

Depending on the platform implementation, subscription statuses may include Draft, Pending Payment, Active, Scheduled, Expired, Cancelled, Suspended, Payment Failed, Refunded, Manually Activated and other operational states.

Only an appropriate Active status should grant the paid entitlement.

12. Manual Super Admin Activation

Super Admin may manually activate or extend a subscription for an eligible user without requiring a customer payment where the administrative system permits such action.

Manual activation must be authorised, recorded and auditable, including the administrator, date/time, plan, duration, reason and resulting entitlement.

Manual activation must not be presented as a customer-paid transaction when no payment occurred.

13. Subscription Changes and Upgrades

Where supported, a user may change plans through the available subscription management flow.

Plan changes must update the central entitlement record and should not create overlapping or duplicate active subscriptions unless the configured business rules expressly allow them.

Any credit, proration, extension or refund associated with a plan change must be calculated and recorded by the central subscription/payment system.

14. WhatsApp Connection Requirement

Where a plan includes WhatsApp Business functionality, the user must connect the WhatsApp account/number through the supported legitimate connection mechanism.

One active WhatsApp Business connection is permitted per Suffle account unless the platform configuration is expressly changed in the future.

Changing the connected number requires the existing connection to be disconnected and invalidated before a new number is connected.

15. WhatsApp Provider Compliance

Subscription access does not provide permission to bypass WhatsApp or Meta rules.

Users must comply with applicable opt-in/consent, opt-out, messaging-template, content, profile, anti-spam and other provider requirements.

Suffle may restrict messaging features where required by provider policy, legal requirements, safety controls or detected misuse.

16. Messaging Limits and Safety Controls

Where applicable, the subscription system may enforce monthly limits, campaign limits, recipient limits, batch size, pause intervals, hourly/daily limits, retry limits and safety-pause rules.

Actual sending is also subject to provider-side limits and restrictions. A Suffle plan does not guarantee a particular delivery rate or provider acceptance.

Usage counters and reports should reflect actual system events rather than estimates.

17. Campaign and Messaging States

Where campaign functionality is included, campaign states may include Draft, Scheduled, Queued, Sending, Paused, Completed, Partially Completed, Failed and Cancelled.

Message-level status should reflect actual available delivery information, such as Pending, Sent, Delivered, Read or Failed, where the provider supplies such information.

18. Subscription and Marketplace Separation

Marketplace customer purchases use the central marketplace order/payment system and are not subscription transactions.

Marketplace commissions, seller settlements, product refunds and customer order payments must remain separate from subscription revenue, refunds and entitlements.

Subscription payment history must not be used as proof that a marketplace product order was paid.

19. Subscription Refunds

Refund eligibility for a subscription is governed by the applicable subscription terms and refund rules presented to the customer.

Where a refund is approved, the refund should be processed through the applicable payment system and must not be represented as completed until the relevant refund state is verified.

A subscription refund may affect or terminate the associated entitlement according to the applicable refund rule.

20. Payment Failure and Expiry

If a subscription payment fails or is not verified, no paid entitlement should be activated for that payment.

An expired subscription automatically loses paid-plan access unless a valid new entitlement is activated.

Payment retries, if offered, must not create duplicate active subscriptions.

21. Suspension and Termination

Suffle may suspend or terminate a subscription where required for security, fraud prevention, misuse, provider-policy compliance, legal compliance, payment issues or material breach of applicable terms.

Where reasonably appropriate, Suffle may notify the user and provide information about the reason and available remedy.

Suspension of a WhatsApp connection or messaging feature does not necessarily mean that the user's entire Suffle account is deleted.

22. Misuse and Prohibited Activities

Users must not use subscription features for spam, deceptive messaging, unlawful content, fraudulent activity, unauthorised access, purchased/scraped recipient lists, security bypasses or other prohibited activity.

Suffle may enforce safety limits, pause campaigns, restrict accounts or terminate subscription access where misuse is detected.

23. AI Features Included in a Plan

Where AI-assisted messaging or other AI features are included, the Suffle AI Terms also apply.

AI does not guarantee factual accuracy, delivery, provider approval or campaign performance.

AI must not invent customer consent, message delivery status, payment status, provider approval, product facts or other system states.

24. Subscription Usage Records

Suffle may maintain records of subscription activation, expiry, plan, usage, payment, refunds, feature access, campaign activity and administrative changes.

Usage and financial records should be protected and auditable under the Data Security & Protection Policy.

25. Account and Subscription Relationship

The subscription is associated with the relevant Suffle account and may not be transferable unless Suffle expressly permits transfer.

If an account is deleted, suspended or otherwise restricted, subscription access may be affected.

Deletion of an account does not necessarily erase payment or financial records that Suffle is required to retain.

26. Third-Party Services and Availability

WhatsApp/Meta and other third-party services may change APIs, policies, limits, authentication requirements or availability.

Suffle does not guarantee continuous availability of third-party messaging or connected-service functionality.

Third-party restrictions may affect a subscribed feature even while the subscription itself remains within its configured validity period.

27. No Guaranteed Messaging Outcome

A paid subscription provides access to configured software functionality; it does not guarantee that a particular message will be delivered, read, replied to or accepted by a recipient or third-party provider.

Delivery depends on valid recipient information, consent, provider policies, connectivity, account status and other technical conditions.

28. Security and Credentials

Subscription users must protect their Suffle account and connected-service authentication methods.

Passwords, OTPs, UPI PINs, CVV, banking passwords, payment PINs and other sensitive authentication secrets must not be provided to Suffle AI, sellers or unauthorised personnel.

Payment-provider credentials, webhook secrets and integration tokens are subject to the Data Security & Protection Policy.

29. Taxes and Charges

Applicable taxes, payment-provider charges or other transaction charges, if any, will be handled according to the checkout information and applicable law.

Users should rely on the authoritative Suffle payment/invoice records for financial information.

30. Disputes and Grievances

Subscription-related complaints may be raised through Suffle support or grievance channels.

Grievances will be handled under the Grievance Redressal Policy and applicable law.

Payment disputes may also involve the relevant payment provider or financial institution.

31. Policy Changes

Suffle may modify subscription plans, features, limits, pricing visibility rules, supported providers and subscription functionality as the service evolves.

Changes to an active subscription should be handled according to the applicable contractual terms and disclosed where required.

This Policy may also be updated when legal, payment-provider or messaging-provider requirements change.

32. Relationship with Other Policies

This Policy should be read with the Terms & Conditions, Privacy Policy, Data Security & Protection Policy, Payment Information Policy, WhatsApp / Business Messaging Policy, Suffle AI Terms, Refund & Cancellation Policy and other applicable policies.

Where a specialised policy provides more specific rules for a feature, that policy applies in addition to this Policy.

33. Legal and Implementation Note

This Policy describes the intended subscription architecture and must be aligned with the actual plan, payment and entitlement configuration deployed by Suffle.

Before launch or material changes, Suffle should verify payment verification, webhook handling, entitlement activation/expiry, refund handling, manual-admin controls, usage limits and provider-specific WhatsApp requirements.

This Policy should be reviewed by qualified Indian legal counsel and appropriate payment/compliance professionals before publication.

Critical Subscription Rules

·       Subscription plans are separate from marketplace product purchases.

·       A subscription becomes active only after successful server-side payment verification, unless an authorised Super Admin manually activates it.

·       Subscription expiry must automatically deactivate the paid entitlement when the configured period ends.

·       One active WhatsApp Business connection is permitted per Suffle account unless future platform configuration expressly changes this rule.

·       Changing the connected WhatsApp number requires disconnecting and invalidating the old connection before connecting the new one.

·       A subscription does not guarantee WhatsApp message delivery, provider acceptance or campaign performance.

·       Public areas must not expose subscription plan prices unless the user is appropriately authenticated/authorised.

Related Suffle Policies

·       Terms & Conditions

·       Privacy Policy

·       Data Security & Protection Policy

·       Payment Information Policy

·       WhatsApp / Business Messaging Policy

·       Suffle AI Terms

·       Refund & Cancellation Policy

·       Grievance Redressal Policy

Regulatory / Drafting Reference

This Policy is intended to operate alongside applicable Indian consumer-protection, data-protection, payment, tax, information-technology and electronic-commerce requirements, as well as applicable third-party messaging-provider terms and payment-provider requirements.