Suffle Online

Operated by Naucera Travel Private Limited

1. Purpose and Scope

This Connected Apps & Accounts Policy explains how Suffle Online handles connections between a customer's Suffle account and external apps, websites, accounts, email services, booking services, shopping services, travel services, transport services, bill/recharge services and other supported third-party services.

The policy applies when a customer voluntarily connects, imports from, or authorises access to an external service through Suffle.

This policy supplements the Suffle Online Privacy Policy, Data Security & Protection Policy, Terms & Conditions, Gmail/Email Data Policy and Suffle AI Terms.

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 a Connected Account Means

A connected account is an external account or service that the customer has intentionally authorised Suffle to access or use for a specific feature.

Connection does not mean that Suffle owns, controls or operates the external service. The external provider remains responsible for its own platform, policies, security and service availability.

A connection may provide read access, limited action capability, import capability, notification capability or another permission explicitly supported by the integration.

4. Legitimate Connection Methods

Suffle may support legitimate connection methods including OAuth, provider-supported authorisation, mobile-number and OTP authentication, email and OTP authentication, authorised sessions, provider login mechanisms where appropriate, booking import, email/PDF/screenshot upload and manual entry.

Suffle will use the method appropriate to the supported provider and feature.

Suffle will not intentionally bypass CAPTCHA, MFA, OTP, provider security controls, access restrictions or technical safeguards.

5. OAuth and Authorisation

Where OAuth or another provider-supported authorisation mechanism is available, Suffle should prefer that mechanism rather than requesting the customer's external-account password.

The permissions requested should be limited to those reasonably required for the enabled feature.

Customers should review the permissions shown by the external provider before authorising a connection.

6. Passwords, OTPs and Authentication Secrets

Suffle does not require customers to provide passwords, OTPs or security secrets merely to use the Suffle platform when an authorised alternative is available.

Customers must never provide Suffle AI with an external banking password, UPI PIN, ATM PIN, payment PIN, CVV or similar payment authentication secret.

OTP values are authentication secrets and should not be stored as ordinary customer data or exposed to AI, sellers or unauthorised personnel.

Where a provider requires interactive authentication, the authentication should occur through the legitimate provider-controlled flow.

7. Connection Status

Suffle must not display an account as connected merely because a connection attempt, login page or frontend flow was opened.

Where technically applicable, connection status should reflect a verifiable backend/provider state.

Supported states may include: Connected, Syncing, Re-login Required, Disconnected, Connection Error, Service Unavailable and Not Connected.

Actions that depend on an active connection must not be represented as completed unless the backend/provider confirms the relevant result.

8. Permissions and Scope

Each connection should have a defined permission scope. Suffle should request only the minimum access necessary for the selected feature.

Where a provider permits separate permissions, customers may be able to grant or deny individual permissions.

Additional permissions should require appropriate user awareness and, where necessary, renewed authorisation.

9. What Suffle May Access

Depending on the service and permissions granted, Suffle may access information such as account/profile details, bookings, orders, invoices, delivery information, subscriptions, bills, travel records, documents, communications or other records required for the enabled feature.

The exact information available depends on the provider's API, authorisation scope, account settings and technical capabilities.

Suffle does not claim access to information that the provider does not make available through the authorised connection.

10. What Suffle Does Not Assume

Suffle does not assume that connecting one service gives it access to every account or service owned by the customer.

Access is not automatically extended from one provider to another.

A connected email account does not automatically authorise Suffle to access unrelated external accounts unless a separate supported connection or lawful import mechanism exists.

11. Data Synchronisation and Imports

Connected information may be synchronised into Suffle to provide the enabled feature, such as organising bookings, orders, reminders, documents or tracking information.

Imported information should be associated with the correct customer account and relevant central Suffle record.

Suffle should merge information into existing records where appropriate rather than creating duplicate bookings, orders, documents or reminders.

12. Universal Search

Information from connected services may become searchable through Suffle's customer-scoped Universal Search when the relevant feature is enabled.

Universal Search is not a global search facility. A customer may search only information that the customer is authorised to access.

If no verified information is available, Suffle should clearly state that no verified information was found in the customer's connected services and Suffle records rather than inventing a result.

13. AI Access to Connected Data

Suffle uses one central Super AI / Universal AI system for applicable AI-assisted features. Connected data may be made available to AI only when necessary for an enabled feature and permitted by the applicable authorisation and access controls.

AI access must remain subject to backend authorisation and customer/account boundaries.

AI must not expose connected-account data to another customer, seller or unauthorised administrator.

14. AI Accuracy and No Fabrication

AI may summarise, organise or reason over verified connected information, but it must not fabricate bookings, prices, balances, availability, refunds, payment success, tracking events, provider status or other factual account states.

If connected information is missing, stale, unavailable or ambiguous, Suffle should communicate that limitation rather than presenting an unverified assumption as fact.

15. Actions Through Connected Accounts

Where a connected service supports actions, Suffle may provide an action interface only where the integration legitimately supports that action and the customer has the required permission.

Opening a provider website, creating a draft, sending a request or submitting an action is not the same as successful completion.

Completion should be reported only after a verifiable response from the provider or Suffle backend confirms the action.

16. Provider Availability and Changes

Third-party providers may change APIs, authentication requirements, permissions, terms, security controls, interfaces or availability.

A connection may therefore stop working, require re-authorisation or become unavailable without Suffle being able to prevent the provider-side change.

Suffle may disable or modify an integration where required for security, legal, operational or provider-policy reasons.

17. Re-Authentication

A connected account may require re-login or renewed authorisation because a session expires, permissions change, a password changes, the provider revokes access or a security event occurs.

Suffle should provide a clear re-authentication path where supported.

Until the connection is restored, Suffle should not imply that new provider data is being successfully synchronised.

18. Disconnecting an Account

Customers may disconnect supported accounts through the available Suffle connection controls, subject to technical and legal requirements.

After disconnection, Suffle should stop using the connection for new synchronisation or actions, except where limited retention or processing is required for security, legal, accounting, dispute-resolution or other lawful purposes.

Disconnecting a provider does not necessarily delete information already lawfully stored in Suffle. Deletion is governed by the Privacy Policy and Account Deletion & Data Retention Policy.

19. Revocation at the Provider

Customers may also revoke Suffle's authorisation directly through the external provider where the provider offers such controls.

Provider-side revocation may cause Suffle to show Re-login Required, Disconnected or another appropriate status.

Customers should use provider-side security controls if they suspect unauthorised access.

20. Third-Party Terms and Responsibility

External providers may have their own terms, privacy policies, security practices and service limitations.

Customers remain responsible for complying with the terms applicable to accounts they connect.

Suffle is not responsible for an external provider's independent security failure, outage, inaccurate data, policy change or discontinuation, although Suffle will take reasonable measures within its control.

21. Security Controls

Connected-account information and credentials must be protected using the security controls described in Suffle's Data Security & Protection Policy.

Tokens and secrets should be stored securely, access should follow least privilege, and security-relevant actions should be auditable.

Raw passwords and sensitive authentication secrets should not be exposed to AI systems, sellers or unauthorised personnel.

22. Customer Responsibilities

Customers must connect only accounts they own or are authorised to control.

Customers must not use Suffle to access another person's account without lawful authorisation.

Customers should keep devices, passwords and authentication methods secure and promptly disconnect compromised accounts.

Customers should review connected-account permissions periodically and revoke access they no longer need.

23. Prohibited Connection Activities

Customers must not use Suffle to bypass provider security controls, CAPTCHA, MFA, OTP verification, rate limits, access restrictions or other safeguards.

Customers must not use connections to scrape, harvest, copy, redistribute or misuse information in violation of law or provider terms.

Suffle may restrict, suspend or terminate connection functionality where misuse or security risk is detected.

24. Connected Data and Sellers

Connected customer-account information is private customer information. Sellers do not receive access merely because a customer purchases from or communicates with the seller.

Seller access is limited to order, fulfilment, support and other information legitimately required for the seller's authorised operation.

Connected-account credentials, private email data and unrelated customer records must not be disclosed to sellers.

25. Connected Data and Administrators

Super Admin and internal administrative access should be role-based and limited to legitimate operational, security, compliance or support needs.

Administrative access must not be treated as unrestricted access to every connected account.

Sensitive connected data should be logged and audited where appropriate, and access should be reviewable.

26. Email, Gmail and Other Communications

Where email or Gmail is connected, the Gmail/Email Data Policy applies in addition to this Policy.

Suffle may use authorised email information to identify relevant bookings, orders, invoices, deliveries, returns, refunds, bills, subscriptions, documents and similar records where the feature is enabled.

Email connection does not authorise Suffle to send messages or take actions beyond the permissions and features actually granted.

27. Documents and Screenshots as Alternatives

If a provider does not support a direct connection, Suffle may support customer-authorised imports such as PDFs, screenshots, emails or manual entry for supported workflows.

Imported information is treated as customer-provided information and should be protected accordingly.

AI may assist with extraction, but extracted information should not be treated as verified provider data unless it can be appropriately validated or confirmed.

28. Data Retention and Deletion

Connected-account data should be retained only as required for the relevant feature, lawful purpose, security, accounting, dispute handling or other applicable requirement.

Customers may request deletion or exercise applicable data rights as described in the Privacy Policy.

Deleting a connection, deleting an individual record and deleting the Suffle account are different operations and may have different effects.

29. Security Incidents

If Suffle detects a suspected compromise of a connected integration, it may revoke sessions or tokens, disable the integration, require re-authorisation, investigate the event and take other protective measures.

Where applicable, personal-data breach handling and regulatory notifications will follow the Data Security & Protection Policy and applicable law.

30. No Guarantee of Continuous Integration

Suffle does not guarantee that every external service will always be connectable or continuously synchronised.

Provider outages, API changes, authentication failures, account restrictions, network failures and other third-party conditions may interrupt functionality.

Suffle will not represent unavailable or unverified provider data as current or live.

31. Changes to this Policy

Suffle may update this Policy when integrations, security practices, services, technology or legal requirements change.

The current effective version should be maintained through Suffle's central legal/policy management system.

32. Legal and Implementation Note

This Policy describes the intended governance and security framework for connected accounts. Individual integrations may have additional provider-specific restrictions and technical requirements.

Only integrations that are legitimately supported and technically implemented should be represented to customers as available.

This Policy should be reviewed by qualified Indian legal counsel and, where appropriate, an information-security professional before publication and before enabling material new third-party integrations.

Critical Rules

·       Do not bypass CAPTCHA, MFA, OTP, provider security controls or access restrictions.

·       Do not expose raw passwords, OTPs, UPI PINs, ATM PINs, CVV, payment PINs or banking passwords to Suffle AI or unauthorised personnel.

·       Do not claim a connection or provider action is successful without verifiable confirmation.

·       Connected customer data is customer-scoped and must not be disclosed to sellers or other customers.

·       Disconnecting an account stops future connection use but does not automatically mean all previously stored records are deleted.

Related Suffle Policies

·       Privacy Policy

·       Data Security & Protection Policy

·       Gmail/Email Data Policy

·       Suffle AI Terms

·       AI Tracking / Automated Processing Notice

·       Document Policy

·       Account Deletion & Data Retention Policy

·       Terms & Conditions

Regulatory / Drafting Reference

This policy is designed to operate alongside the Digital Personal Data Protection Act, 2023 and applicable rules, information-technology and cybersecurity requirements, while recognising that each external provider may impose additional contractual and technical requirements.