We use essential cookies to keep you signed in and to secure checkout, and optional cookies for personalization. See our Privacy Policy and Cookie Policy.

AI Tracking / Automated Processing Notice

Version 2.1 · Effective 2026-09-09

Suffle Online

Operated by Naucera Travel Private Limited

1. Purpose and Scope

This Notice explains how Suffle Online may use automated processing, AI-assisted processing and its central AI Tracking Engine to identify, organise, update, monitor and surface information connected with a user's authorised Suffle records and services.

It applies to tracking of orders, shipments, bookings, trips, documents, subscriptions, bills/recharges, reminders and other supported records, including information imported from authorised email or connected services.

It should be read with the Privacy Policy, Suffle AI Terms, Connected Apps & Accounts Policy, Gmail / Email Data Policy, Data Security & Protection Policy and Reminder Engine rules.

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. Central AI Tracking Engine

Suffle uses one central AI Tracking Engine rather than separate tracking systems for each feature.

The engine may receive authorised information from orders, bookings, connected apps, email/imports, documents, provider websites, manual entries and customer-confirmed information.

Different Suffle modules may display tracking information, but the underlying tracking record should remain part of the central tracking architecture.

4. What Automated Processing Means

Automated processing means software rules, algorithms or AI systems may analyse information and perform defined processing without a person manually reviewing every individual event.

Examples include identifying an order-status update, matching an email to an existing order, detecting a shipment number, recognising a document type, identifying a likely reminder date or detecting that a record may require attention.

5. AI-Assisted Processing

AI may assist with extraction, classification, matching, summarisation, prioritisation, anomaly detection and natural-language explanations.

AI output is treated as an interpretation or assistance layer unless the underlying source and applicable system rules verify the event.

AI does not have authority to invent or confirm facts that are not supported by actual records.

6. Sources of Tracking Information

Tracking information may come from Direct Integration, Authorized Email, Imported Email, PDF, Screenshot, Uploaded Document, Provider Website, Manual Entry, AI Detected information or Customer Confirmed information.

The source should be retained as part of the tracking record where technically appropriate so that users and administrators can distinguish verified information from manually supplied or AI-detected information.

7. Tracking Statuses

The central Tracking Engine may use statuses such as Tracking, Checking, Attention Required, Tracking Error, Unavailable and Paused.

These statuses describe Suffle's processing state and must not be represented as a provider's live status unless the provider has actually supplied that status.

8. No Fabricated Live Tracking

Suffle must not display a shipment, booking, order or other item as LIVE unless the underlying source genuinely provides current/live information.

If current verification is unavailable, Suffle should clearly communicate that the information is unavailable, last known, imported, manually entered or otherwise qualified.

9. Order and Shipment Tracking

For marketplace orders, Suffle may track seller-provided courier name, AWB/tracking ID and shipping status through available legitimate sources.

Sellers are responsible for shipping and for entering accurate courier/tracking information where the Suffle workflow requires it.

Suffle does not guarantee third-party courier availability or accuracy.

10. Bookings and Trips

Automated processing may identify or update flights, hotels, trains, buses, cabs, activities and other supported travel records from authorised sources.

Imported or AI-detected information should be merged with existing records rather than creating duplicates.

Where important information is uncertain, Suffle may request user confirmation.

11. Email and Gmail Processing

Where the user voluntarily connects an email service through an authorised method, Suffle may process relevant messages and attachments for supported tracking and organisation purposes.

High-confidence information may update an existing record automatically; medium-confidence information may require confirmation; low-confidence information should not automatically create or change important records.

Email processing is governed in detail by the Gmail / Email Data Policy.

12. Documents, PDFs and Screenshots

Users may provide PDFs, screenshots or other documents for tracking or record creation where supported.

AI may extract dates, reference numbers, names, amounts, status information or other relevant fields from the submitted material.

Extraction can contain errors. Users should review important information before relying on it.

13. Manual and Customer-Confirmed Information

Users may manually enter or confirm tracking information where a provider integration or authorised import is unavailable.

Customer-confirmed information may be stored as part of the relevant record with an appropriate source indicator.

Manual entry does not become provider-verified merely because it is stored in Suffle.

14. Confidence-Based Processing

Suffle may use confidence levels to determine whether information can be automatically applied.

High-confidence information may be used to update or create a record where permitted. Medium-confidence information may require confirmation. Low-confidence information should not automatically create or materially alter important records.

Confidence is an internal processing signal and is not a guarantee that the extracted information is correct.

15. Record Matching and Deduplication

The Tracking Engine may compare identifiers, dates, provider information, order numbers, booking references, email metadata and other permitted fields to determine whether new information belongs to an existing record.

Matching is intended to prevent duplicate orders, bookings, trips, reminders or tracking records.

Where a match is uncertain, Suffle should avoid silently merging unrelated records.

16. Automated Updates

Automated processing may update a record when the source and system rules support the change.

Material actions or changes that could create financial, legal or other significant consequences should require appropriate verification or user confirmation where necessary.

An automated update is not proof that a third-party provider has accepted or completed an action.

17. Reminders and Notifications

Automated tracking may identify events that could require a reminder, such as delivery updates, booking dates, document expiry, subscription renewal or another configured event.

The central Reminder Engine should be used rather than creating separate reminder systems for individual features.

Notifications should be based on actual stored or verified information and should not imply certainty where the underlying information is uncertain.

18. AI-Generated Summaries and Explanations

Suffle AI may summarise tracking information or explain what a status means.

Summaries are generated from available records and may omit context or contain interpretation errors.

For important decisions, users should rely on the underlying provider record or source rather than an AI summary alone.

19. Automated Processing and Payments

Automated processing may associate payment records with an order or subscription when backend payment records support the association.

A browser event, frontend success message, cookie or AI inference is not sufficient to confirm payment.

Marketplace order confirmation requires server-side verified payment. Subscription entitlement likewise requires verified payment according to the Subscription Policy.

20. Automated Processing and Marketplace Discovery

Automated systems may support search, recommendation, personalisation and product discovery using eligible marketplace data.

Such processing does not override seller approval, product approval, inventory or serviceability requirements.

Ranking and discovery are governed by the Ranking & Discovery Transparency Policy.

21. Automated Processing and Seller Data

Seller product data may be processed for completeness checks, attribute suggestions, image enhancement, moderation and tracking of fulfilment records.

Seller-provided information remains subject to the Seller Terms and marketplace verification process.

AI may assist with compliance or content checks but does not replace final Super Admin verification where human approval is required.

22. Human Review

Suffle may use human review where automated processing identifies uncertainty, risk, complaints, suspected fraud, compliance issues, intellectual-property concerns or other matters requiring judgement.

Super Admin retains final authority for platform verification decisions that are designated as administrative decisions.

23. No Sole Reliance for High-Impact Decisions

Suffle should not rely solely on an unverified AI inference to make a decision that could materially affect a user's legal rights, account access, financial entitlement or other significant interest where applicable safeguards require human involvement.

Where a decision is based on automated processing and applicable law provides rights concerning such processing, Suffle will provide the applicable mechanism described in its privacy and grievance framework.

24. User Review and Correction

Users should be able to review relevant records and report incorrect tracking information through available Suffle interfaces.

Where a source can be corrected or re-imported, Suffle may update the record based on the corrected information.

Users should not intentionally provide false information to cause automated tracking systems to produce an incorrect result.

25. Connected Services and Provider Limitations

Automated tracking may depend on a provider's website, email, integration, authentication or availability.

Suffle cannot guarantee that every provider will expose tracking information or continue to support a particular method.

Suffle must not bypass CAPTCHA, MFA, OTP, provider security controls or terms of service to obtain tracking information.

26. Privacy and Data Minimisation

Automated tracking may involve personal data, transaction information, documents, communication content or identifiers.

Suffle should process only information reasonably necessary for the stated purpose and should apply the controls described in the Privacy Policy and Data Security & Protection Policy.

Private customer data must not be exposed to another customer, seller or unauthorised administrator.

27. AI Access Controls

AI access to tracking data must be controlled by account permissions, feature permissions and the actual scope of connected services.

A user's ability to ask Suffle AI a question does not automatically authorise access to unrelated accounts or another person's information.

AI must follow the same data-isolation and authorisation rules as the underlying application.

28. Security of Tracking Data

Tracking records and source data should be protected through appropriate authentication, authorisation, encryption, logging, access controls and other safeguards.

Security incidents involving tracking or automated-processing data should be handled under Suffle's Data Security & Protection Policy and incident-response procedures.

29. Retention and Deletion

Tracking records may be retained for the purposes described in the Privacy Policy, including providing services, maintaining order/booking history, customer support, dispute resolution, security and legal obligations.

Deletion or account-closure requests are handled according to the Account Deletion & Data Retention framework and applicable law.

Disconnecting a source does not necessarily delete historical records already lawfully created from that source.

30. Automated Processing Errors

Automated extraction, classification, matching and prediction can be wrong.

Suffle should provide appropriate source/status information and correction mechanisms for important records.

Users should verify critical dates, amounts, booking references, delivery information and other material facts against the original source when necessary.

31. Fraud, Abuse and Manipulation

Suffle may use automated systems to detect suspicious activity, duplicate records, manipulated tracking information, fraudulent orders or other abuse.

Automated flags are risk signals and may require human investigation before adverse action where appropriate.

Users and sellers must not manipulate tracking IDs, documents, screenshots, emails or other information to deceive the system.

32. Third-Party AI or Technology Providers

Suffle may use third-party technology providers to support AI, OCR, analytics, security or other processing where appropriately configured.

Any such provider should be subject to appropriate contractual, privacy and security controls.

Suffle should not represent a third-party provider's output as independently verified information when it is not.

33. No Guarantee of Availability or Accuracy

Automated tracking depends on source quality, provider availability, connectivity, document quality and other technical factors.

Suffle does not guarantee uninterrupted tracking or that every status will be detected immediately.

Where tracking is unavailable, the interface should state the applicable limitation rather than fabricate an update.

34. Relationship with Suffle AI Terms

The Suffle AI Terms govern general AI functionality, limitations, generated content, AI actions and AI security.

This Notice provides additional transparency specifically for automated tracking and automated processing.

Where the two documents overlap, both apply and the more specific tracking rule applies to the tracking feature.

35. Relationship with Other Policies

This Notice should be read with the Privacy Policy, Data Security & Protection Policy, Connected Apps & Accounts Policy, Gmail / Email Data Policy, Suffle AI Terms, Ranking & Discovery Transparency Policy, Reminder Engine rules, Refund & Cancellation Policy and Account Deletion & Data Retention Policy.

36. Changes to Automated Processing

Suffle may change its automated processing methods, models, rules, data sources and tracking features as the platform evolves.

Material changes should be reflected in applicable notices, settings or user communications where required.

37. Legal and Implementation Note

This Notice describes Suffle's intended automated-processing architecture and governance. Actual implementation should match the live systems, data sources, models, permissions, retention periods and user controls.

Where applicable, automated processing should be implemented consistently with the Digital Personal Data Protection Act, 2023, applicable rules and other Indian laws in force at the relevant time.

This Notice should be reviewed by qualified Indian privacy, technology and e-commerce counsel before publication and periodically thereafter.

38. Notice Updates

Suffle may update this Notice to reflect changes in AI capabilities, tracking sources, automated processing, legal requirements or platform architecture.

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

Critical Automated Processing Rules

·       One central AI Tracking Engine should be used across supported tracking features; do not create duplicate tracking engines.

·       AI or automation must not fabricate orders, bookings, shipment status, payment status, balances, refunds or other facts.

·       Tracking sources and statuses should distinguish verified, imported, manual and AI-detected information.

·       High-confidence information may be automated where appropriate; uncertain information should require confirmation or remain uncommitted.

·       Payment and order confirmation must rely on verified backend/payment records, not AI inference or browser events.

·       AI does not gain authority to access private connected services merely because a user asks a question.

·       Human review should remain available for significant, uncertain, disputed or high-risk decisions where appropriate.

Related Suffle Policies

·       Privacy Policy

·       Data Security & Protection Policy

·       Connected Apps & Accounts Policy

·       Gmail / Email Data Policy

·       Suffle AI Terms

·       Ranking & Discovery Transparency Policy

·       Refund & Cancellation Policy

·       Account Deletion & Data Retention

·       Reminder Engine Rules

Implementation Requirement

The production system should maintain auditable source metadata, processing status, confidence where used, timestamps, correction history and access controls for automated tracking records. Important automated changes should be traceable to the source event or user confirmation that caused the change.