Cookie Policy & Cookie Usage | Privacy & Data | Ample Wings | Best eCommerce Agency in Delhi NRC and India Australia USA Canada Germany

Last Updated: 1 August 2026
Effective Date: 1 August 2026

This Cookie Policy explains how Ample Wings Overseas (“Ample Wings,” “we,” “us,” or “our”) uses cookies and similar technologies on the AW Co-Pilot AI website, web application and related online services (collectively, the “Service”).

AW Co-Pilot is an AI-powered marketplace management platform that helps businesses manage products, listings, pricing, inventory, orders, reports and connected sales channels.

This Cookie Policy should be read together with our:

  • Privacy Policy
  • Data Deletion Policy
  • Security Policy
  • Acceptable Use Policy
  • Terms & Conditions

1. What Are Cookies?

Cookies are small text files placed on your device when you visit a website or use a web application.

They allow websites to:

  • Remember your login session.
  • Maintain security.
  • Remember preferences.
  • Understand how the Service is used.
  • Improve performance.
  • Measure website traffic.
  • Provide relevant functionality.

We may also use technologies similar to cookies, including:

  • Local storage
  • Session storage
  • Pixels
  • Web beacons
  • Device identifiers
  • Authentication tokens
  • Similar technologies

For simplicity, this Policy refers to these technologies collectively as “Cookies.”

2. Why AW Co-Pilot Uses Cookies

We use Cookies for legitimate operational and business purposes, including:

🔐 Security

To help:

  • Authenticate users.
  • Maintain secure sessions.
  • Detect suspicious activity.
  • Protect accounts.
  • Prevent unauthorized access.

⚙️ Functionality

To:

  • Remember preferences.
  • Maintain application settings.
  • Keep users signed in where appropriate.
  • Maintain shopping or product-management workflows.
  • Remember interface preferences.

📊 Analytics

Where enabled, analytics technologies help us understand:

  • Number of visitors.
  • Pages viewed.
  • Features used.
  • Application performance.
  • Traffic sources.
  • Errors and technical issues.

📈 Service Improvement

Usage information may help us improve:

  • AW Co-Pilot functionality.
  • User interface.
  • Performance.
  • Navigation.
  • Reliability.

3. Types of Cookies We May Use

We classify Cookies into the following categories.

Cookie Type Purpose Usually Required?
Strictly Necessary Login, security and core functionality ✅ Yes
Functional Preferences and application settings 🟢 Usually optional
Analytics Usage and performance measurement 🟡 Optional
Performance Monitoring application performance 🟡 Optional
Marketing Advertising and campaign measurement 🟡 Optional
Third-Party Services provided by external providers Depends on purpose

4. Strictly Necessary Cookies

These Cookies are required for the Service to operate correctly.

They may be used for:

  • User authentication.
  • Login sessions.
  • Session management.
  • Security.
  • Fraud prevention.
  • CSRF protection.
  • Load balancing.
  • Application functionality.
  • Account access.

Without these Cookies, certain AW Co-Pilot functions may not work correctly.

Because these Cookies are necessary for providing the Service, they generally cannot be disabled through an optional cookie-preference mechanism while continuing to use the affected functionality.

5. Authentication Cookies

When you sign in to AW Co-Pilot, we may use Cookies or similar technologies to maintain your authenticated session.

These technologies help us determine that:

“This authenticated request belongs to this authorized user.”

Authentication information should be stored and transmitted using appropriate security controls.

We do not intentionally store marketplace passwords such as Amazon Seller Central passwords in browser Cookies.

6. Security Cookies

Security-related Cookies may help us:

  • Detect suspicious activity.
  • Prevent session hijacking.
  • Prevent unauthorized requests.
  • Protect against automated abuse.
  • Maintain application security.
  • Identify unusual authentication activity.

Security Cookies may remain active for the duration necessary to provide the relevant security function.

7. Functional Cookies

Functional Cookies may remember user preferences such as:

  • Language.
  • Dashboard configuration.
  • Display preferences.
  • Recently selected settings.
  • Application preferences.

These Cookies improve the user experience but may not be necessary for the core operation of every feature.

8. Analytics Cookies

If analytics services are enabled, we may use Cookies to understand how visitors interact with our website and application.

Analytics information may include:

  • Pages visited.
  • Features accessed.
  • Session duration.
  • Browser type.
  • Device type.
  • Approximate geographic information.
  • Referral source.
  • Application errors.

Analytics data is used primarily for:

  • Measuring performance.
  • Identifying usability problems.
  • Improving features.
  • Understanding general usage patterns.

9. Performance Monitoring

We may use performance-monitoring technologies to identify technical issues.

For example, we may measure:

  • Page-load performance.
  • API response times.
  • Application errors.
  • Failed requests.
  • Browser compatibility.
  • Service availability.

These technologies help our technical team diagnose and resolve problems.

10. Marketing Cookies

If we use marketing or advertising technologies, these may be used to:

  • Measure advertising campaigns.
  • Understand advertising performance.
  • Attribute conversions.
  • Build advertising audiences where permitted.
  • Display relevant advertisements.

Marketing Cookies will be used only where permitted by applicable law and according to the applicable consent requirements.

If we do not use marketing Cookies on a particular version of the Service, this category will not be active.

11. Third-Party Cookies

Some Cookies may be placed by third-party providers whose services we use.

These providers may include providers of:

  • Analytics.
  • Cloud infrastructure.
  • Authentication.
  • Customer support.
  • Payments.
  • Security.
  • Performance monitoring.
  • Marketing.

Third-party providers may process information according to their own privacy policies and contractual arrangements.

We recommend reviewing the privacy policies of any third-party services presented through the Service.

12. Marketplace Connections

AW Co-Pilot may connect with marketplaces such as Amazon and other supported sales channels.

Marketplace API authorization is generally handled through the marketplace's authorized authentication mechanism rather than ordinary browser Cookies.

Cookies used by AW Co-Pilot do not give us access to your marketplace password.

Marketplace information accessed through APIs is governed separately by:

  • The applicable marketplace's terms.
  • API policies.
  • Our Privacy Policy.
  • Our Security Policy.
  • Our Data Deletion Policy.

13. Local Storage and Similar Technologies

AW Co-Pilot may use browser technologies such as:

  • Local Storage.
  • Session Storage.
  • IndexedDB.
  • Similar browser storage mechanisms.

These technologies may be used for:

  • Application preferences.
  • Temporary application state.
  • Interface configuration.
  • Performance improvements.
  • Authentication-related functionality where appropriate.

They are subject to the same security and privacy principles described in this Cookie Policy.

14. Session Cookies

Session Cookies generally remain on your device while your browser session is active.

They may be deleted when:

  • You log out.
  • Your session expires.
  • Your browser is closed, depending on the implementation.

Session Cookies may be required for secure operation of AW Co-Pilot.

15. Persistent Cookies

Persistent Cookies remain on your device for a defined period.

They may be used to:

  • Remember preferences.
  • Maintain certain settings.
  • Measure recurring usage.
  • Support authentication features where appropriate.

Persistent Cookies should have an appropriate expiration period based on their purpose.

16. Cookie Duration

Cookies may generally fall into two categories:

Session Cookies

Deleted when the session ends or according to the browser/application behavior.

Persistent Cookies

Remain for a defined period and expire automatically.

The actual duration depends on the specific Cookie and its purpose.

We aim not to retain Cookies longer than reasonably necessary for their intended purpose.

17. Cookie Consent

Where applicable law requires consent for non-essential Cookies, we may provide a Cookie preference mechanism allowing users to:

  • Accept optional Cookies.
  • Reject optional Cookies.
  • Manage Cookie preferences.
  • Change their preferences later.

Strictly necessary Cookies may continue to operate because they are required to provide the requested Service.

18. Changing Cookie Preferences

If our website provides a Cookie Preference Center, you can change your preferences through that interface.

You may also control Cookies through your browser settings.

However, disabling certain Cookies may cause some features to:

  • Stop working.
  • Work incorrectly.
  • Require repeated login.
  • Lose saved preferences.
  • Provide a reduced experience.

19. Browser Controls

Most modern browsers allow users to:

  • View Cookies.
  • Delete Cookies.
  • Block Cookies.
  • Block third-party Cookies.
  • Allow Cookies from specific websites.
  • Delete Cookies when closing the browser.

Browser controls vary between:

  • Chrome
  • Microsoft Edge
  • Firefox
  • Safari
  • Other browsers

Please refer to your browser's own documentation for instructions.

20. Cookies and Personal Information

Some Cookies may contain or be associated with information that can identify a user or device.

Examples may include:

  • Session identifiers.
  • Account identifiers.
  • Authentication-related identifiers.
  • Preference identifiers.

We treat information associated with identifiable users according to our Privacy Policy and applicable data-protection requirements.

We do not intentionally use Cookies to collect unnecessary sensitive personal information.

21. Cookies and Security

Cookies can be security-sensitive.

Where appropriate, AW Co-Pilot may use security attributes such as:

  • Secure
  • HttpOnly
  • SameSite

These controls help reduce risks such as:

  • Session theft.
  • Cross-site request attacks.
  • Unauthorized access.

The exact controls depend on the technology and functionality involved.

22. Protection of Authentication Information

Authentication/session Cookies should not expose:

  • Marketplace passwords.
  • API secret keys.
  • OAuth client secrets.
  • Encryption keys.
  • Database credentials.

Sensitive credentials should be maintained server-side using appropriate secure-storage mechanisms.

23. Cookies Used by the AW Co-Pilot Application

Depending on the implementation, AW Co-Pilot may use Cookies for:

Category Example Purpose
Authentication Maintain signed-in session
Security Prevent unauthorized requests
Preferences Remember user settings
Application State Maintain selected workspace/settings
Performance Diagnose technical issues
Analytics Understand feature usage
Consent Remember Cookie choices
Support Maintain customer-support session

The exact Cookie inventory may change as the application develops.

24. Cookie Inventory

As AW Co-Pilot moves into production, Ample Wings may maintain an internal Cookie inventory containing:

Cookie Provider Purpose Type Duration
Authentication Cookie AW Co-Pilot User authentication Necessary Session / configured period
Security Cookie AW Co-Pilot Security protection Necessary Configured period
Preference Cookie AW Co-Pilot User preferences Functional Configured period
Consent Cookie AW Co-Pilot Cookie preferences Necessary/Functional Configured period
Analytics Cookie Analytics Provider Usage analytics Optional Provider-defined
Performance Cookie Monitoring Provider Performance monitoring Optional Provider-defined

Note: The final production Cookie inventory should be updated to contain the actual Cookie names, providers, purposes and expiration periods used by AW Co-Pilot.

25. Cookies Used on Ample Wings Websites

Ample Wings operates websites and online services relating to:

  • Marketplace management.
  • Marketplace onboarding.
  • Digital marketing.
  • Web design and development.
  • Ecommerce services.
  • AW Co-Pilot AI.
  • Other technology and professional services.

Cookies may differ between individual websites and services.

This Cookie Policy applies to Cookies used on the relevant AW Co-Pilot and Ample Wings online services where this Policy is published.

26. Third-Party Website Links

AW Co-Pilot may contain links to third-party websites.

Examples may include:

  • Marketplaces.
  • Payment providers.
  • Social media.
  • Documentation.
  • Support services.

When you leave our website, the third party's own Cookie Policy and privacy practices apply.

We do not control third-party Cookies.

27. Social Media Technologies

Our websites may contain links or integrations with social-media platforms such as:

  • Instagram
  • Facebook
  • LinkedIn

If social-media technologies are embedded on a page, those providers may collect information according to their own policies.

We recommend reviewing their respective privacy and Cookie policies.

28. Payment Services

Where payments are processed through third-party payment providers, the provider may use Cookies or similar technologies.

Payment providers may use these technologies for:

  • Security.
  • Fraud prevention.
  • Payment processing.
  • Authentication.

AW Co-Pilot does not intentionally store complete payment-card information or CVV/security codes.

29. Cookie Data Sharing

We may allow service providers to process Cookie-related information where necessary to provide:

  • Hosting.
  • Security.
  • Analytics.
  • Monitoring.
  • Customer support.
  • Payment services.
  • Marketing.
  • Other legitimate business functions.

We do not intentionally sell users' Cookie information as a standalone data product.

30. Data Retention

Cookie-related information is retained according to its purpose.

For example:

  • Session identifiers may expire when the session ends.
  • Preference Cookies may remain until their configured expiration.
  • Analytics records may be retained according to our analytics configuration.
  • Security logs may be retained according to our Security Policy and applicable requirements.

Information that is no longer necessary should be deleted or anonymized where appropriate.

31. Children's Privacy

AW Co-Pilot is intended for businesses and professional users.

The Service is not intentionally directed toward children.

We do not knowingly use Cookies to collect personal information from children in violation of applicable law.

If you believe a child has provided personal information through our Service, contact:

support@amplewings.com

32. International Users

AW Co-Pilot may be accessed by customers in different countries.

Cookie processing may therefore be subject to different legal requirements depending on the user's jurisdiction.

Where required, we will implement appropriate Cookie-consent and preference mechanisms.

33. Legal Basis for Cookies

Depending on the jurisdiction and purpose, Cookies may be processed based on:

  • Necessity to provide the requested Service.
  • User consent.
  • Legitimate interests.
  • Compliance with legal obligations.

Where consent is legally required, optional Cookies will not be activated before the appropriate consent is obtained.

34. Withdrawal of Consent

Where Cookie processing is based on consent, you may withdraw your consent through the available Cookie Preference Center or other applicable mechanism.

Withdrawal of consent does not affect processing that occurred before withdrawal.

Some strictly necessary Cookies may continue to operate because they are necessary to provide the Service.

35. Do Not Track Signals

Some browsers provide “Do Not Track” or similar privacy signals.

Because browser implementations vary, AW Co-Pilot may not respond to every such signal unless required by applicable law.

Where legally required, we will implement applicable privacy-signal requirements.

36. Security Incidents Involving Cookies

If we identify a security incident involving Cookies or authentication tokens, we may take actions including:

  • Invalidating sessions.
  • Revoking authentication tokens.
  • Requiring users to log in again.
  • Rotating credentials.
  • Investigating affected systems.
  • Notifying affected users where required.
  • Notifying authorities or third parties where legally required.

37. Your Responsibilities

You should:

  • Keep your browser updated.
  • Use a secure device.
  • Protect your AW Co-Pilot credentials.
  • Avoid sharing your login session.
  • Log out from shared devices.
  • Report suspicious activity.

38. Changes to This Cookie Policy

We may update this Cookie Policy when:

  • New application features are introduced.
  • New analytics tools are implemented.
  • New third-party services are added.
  • Cookie technology changes.
  • Legal requirements change.
  • Our website architecture changes.

The Last Updated date will be revised when material changes are made.

39. Contact Us

For questions about Cookies, privacy or data processing:

Ample Wings Overseas

Address:
4/284, Subhash Nagar
New Delhi, West Delhi
Delhi – 110027
India

Privacy / Cookie Questions:
support@amplewings.com

Sales:
sales@amplewings.com

Phone / WhatsApp:
+91 9318305286