Quidio Cookie Policy
Last updated: 13 July 2026
This Cookie Policy explains how Quidio Ltd, a company registered in England and Wales with company number 17082575, operating the Quidio service under the Quidio brand ("Quidio", "we", "us", or "our"), uses cookies, browser storage, mobile application storage, software development kits (SDKs), device identifiers and similar technologies when you use our websites, mobile applications, seller tools, hosted storefronts and related services, including https://quidio.ai and https://quidio.shop (together, the Services).
This Cookie Policy should be read together with our Privacy Policy and Terms of Use.
1. Cookies and similar technologies
Cookies are small text files stored on your device when you visit a website. Similar technologies include browser local storage, session storage, mobile application storage, SDKs, device or installation identifiers, pixels, tags and other technologies that store information on, or access information from, your device.
In this policy, references to cookies include these similar technologies unless stated otherwise.
2. How Quidio uses these technologies
Quidio uses cookies and similar technologies to:
-
operate, secure and maintain the Services;
-
authenticate users and maintain account sessions;
-
remember user choices and settings;
-
support seller onboarding, product-listing and order-management workflows;
-
support buyer checkout and payment-related functions;
-
prevent fraud, abuse and unauthorised access;
-
deliver service communications and mobile push notifications;
-
monitor performance, diagnose errors and improve reliability; and
-
understand how users interact with the Services so that we can improve them.
Quidio does not currently use cookies or SDKs for third-party behavioural advertising, retargeting, cross-site or cross-app tracking, advertising attribution, or sharing data with data brokers.
3. Categories of cookies and similar technologies
3.1 Strictly necessary technologies
These technologies are required for the Services to operate securely or to provide functionality requested by the user. They may include:
-
authentication and login technologies;
-
session-management technologies;
-
security, fraud-prevention and abuse-prevention technologies;
-
load-balancing and infrastructure technologies;
-
cookie-preference storage;
-
checkout and payment-support technologies; and
-
rate-limiting and service-protection technologies.
Where these technologies are strictly necessary to provide a service requested by the user, consent is not required under applicable UK and EU cookie rules. Blocking them may prevent parts of the Services from working correctly.
3.2 Analytics technologies
Quidio uses Firebase Analytics to understand how users interact with the mobile application and related Services. Depending on the event being measured, analytics information may include:
-
app launches and sessions;
-
screens or features used;
-
taps, clicks and other product-interaction events;
-
general device, operating-system and app-version information;
-
installation or app-instance identifiers;
-
referral or acquisition information, where available; and
-
general geographic information derived from technical data such as an IP address.
On websites, non-essential analytics technologies will only be used where required consent has been obtained. In mobile applications, analytics collection is managed through the app, device and platform controls available to the user and in accordance with applicable law.
3.3 Diagnostics and performance technologies
Quidio uses Firebase Crashlytics and related technical logging and monitoring to identify crashes, errors, performance problems and reliability issues.
Diagnostics information may include:
-
crash reports and error traces;
-
app version, device model and operating-system version;
-
technical session or installation identifiers;
-
performance and reliability events; and
-
technical logs associated with a fault or failed request.
Some diagnostics are necessary to maintain the security and reliability of the Services. Where a diagnostic technology is not strictly necessary and consent is required, it will only be used after the required consent has been obtained.
3.4 Authentication and account technologies
Quidio uses Amazon Cognito to support account registration, authentication, login, session management and account security. Cognito and related AWS infrastructure may use tokens, browser storage, device information or similar technologies to maintain secure sessions and protect accounts.
3.5 Payment, onboarding and fraud-prevention technologies
Quidio uses Stripe for payment processing, seller onboarding, payouts, identity verification and fraud or risk checks.
Stripe may place or access cookies and similar technologies when a user interacts with Stripe-hosted or Stripe-supported functionality. These technologies may be used for:
-
checkout and payment processing;
-
seller onboarding and account verification;
-
security authentication;
-
fraud detection and prevention;
-
risk assessment;
-
dispute, refund and chargeback handling; and
-
compliance with Stripe's legal and regulatory obligations.
Stripe controls the technologies used on its own hosted pages and services. Users should review Stripe's privacy and cookie information for further details.
3.6 Push-notification technologies
Quidio uses Firebase Cloud Messaging and platform notification services to deliver operational notifications, such as account, listing, order or service-related updates. These services may use app-instance tokens, device identifiers and device settings needed to route notifications.
Users can manage mobile notification permissions through their device settings.
4. Third-party providers
The third-party providers that may use cookies or similar technologies in connection with the current Services include:
| Provider | Purpose |
|---|---|
| Amazon Web Services, including Amazon Cognito | Hosting, infrastructure, account authentication, session management and security |
| Google Firebase Analytics | App usage and product-interaction analytics |
| Google Firebase Crashlytics | Crash reporting, diagnostics and performance monitoring |
| Google Firebase Cloud Messaging | Mobile push notifications |
| Stripe | Checkout, payments, seller onboarding, identity verification, payouts, fraud prevention and risk checks |
These providers process information in accordance with their own privacy notices and their agreements with Quidio.
Quidio may change or add service providers as the Services develop. We will update this policy where a change materially affects how cookies or similar technologies are used.
5. Browser storage, SDKs and mobile application storage
Quidio may use local storage, session storage, mobile application storage, authentication tokens, SDKs and device or installation identifiers to:
-
maintain secure sessions;
-
remember preferences;
-
support core app and website functions;
-
enable analytics, crash reporting and notifications;
-
support security and fraud prevention; and
-
improve performance and reliability.
Clearing browser or app storage, removing the app, signing out, or resetting a device identifier may remove some locally stored information. Some account information and server-side records will remain as described in our Privacy Policy.
6. Consent and managing your preferences
Where required by law, Quidio will not place or access non-essential website cookies until the user has made a choice. The cookie controls provided will allow users to accept or reject non-essential categories without affecting strictly necessary technologies.
You can also manage cookies and similar technologies by:
-
using the cookie settings made available on the relevant Quidio website;
-
blocking or deleting cookies through your browser settings;
-
clearing browser local storage or app data;
-
managing analytics, privacy and advertising settings provided by your device or operating system;
-
disabling mobile notifications through device settings; or
-
uninstalling the mobile application.
Your browser or device may provide additional privacy controls. Blocking strictly necessary technologies may prevent login, checkout, security or other requested functions from working correctly.
Quidio does not currently use advertising identifiers for targeted advertising or cross-service tracking.
7. Information collected through these technologies
Depending on the technology and the way the Services are used, information collected may include:
-
account, session or authentication identifiers;
-
app-instance, installation or device identifiers;
-
IP address and general location derived from it;
-
browser, device, operating-system and app-version information;
-
pages, screens, features and interactions;
-
crash reports, errors, diagnostic data and performance events;
-
cookie and privacy preferences;
-
checkout, onboarding, payment or fraud-prevention events; and
-
push-notification tokens and delivery information.
Further information about how Quidio uses, shares, retains and protects personal information is provided in our Privacy Policy.
8. Changes to this policy
We may update this Cookie Policy to reflect changes in the Services, technologies, service providers, legal requirements or business practices.
Where required, we will provide additional notice or request renewed consent. The current version will be published on the Quidio website with its last-updated date.
9. Contact us
Questions about this Cookie Policy or Quidio's use of cookies and similar technologies can be sent to: