iQOLI · PRIVACY & YOUR DATA
Privacy Policy
Last updated: 3 November 2026
This policy covers the iQOLI website, early-access and contact forms, member profiles, saved collections, business listing submissions, uploaded listing images, private enquiries and owner administration. The mobile apps and transactional marketplace services remain in development. Checkout, payments, livestream broadcasting and real transactional auctions are not available on this release. A virtual-credit practice-auction feature is provided as a clearly labelled demonstration. This notice must be reviewed against the actual mobile apps before their launch.
1. Who is responsible and how to contact us
iQOLI is the service and brand responsible for the purposes described in this notice. You can contact the iQOLI team using the dedicated privacy form below, without creating an account or logging in. Choose your request type and use an email address at which we can respond.
The registered legal operator, its business address and any applicable representative details have not yet been supplied for this pre-launch website. These details remain to be confirmed and published. This notice does not assert that iQOLI is incorporated in any particular country.
2. Information we collect
| Category | Information | Source |
|---|---|---|
| Early-access and business enquiries | Name, email address, country or region, buyer/business/brand/partner role, chosen page language, optional company name and optional message. General contact forms also collect your subject and message. | Information you submit in our form. |
| Consent and registration record | Submission date and time and the version of the consent notice and a separate optional marketing-consent choice. Records from the earlier notice retain their original consent record; a new marketing opt-in is not inferred. | Created when the form is submitted. |
| Privacy and deletion requests | Email address, optional name, request type, affected data, optional explanation, reference number, request status and submission time. Verification and response correspondence may also be needed. | Your request and its handling. |
| Member profiles and saved items | A stable site-specific user identifier, email and optional name from ChatGPT sign-in; the profile name, role, company, country and biography you supply; saved item identifiers; registration time and accepted terms version. | Your sign-in provider and your actions on the site. |
| Business listings and images | Listing title, description, category, image or image URL, price, currency, condition, location, owner identifier, review status and creation date. Uploaded listing images are stored as files and may be publicly accessible through their direct URL even before a listing is published. | The business member submitting a listing or upload. |
| Private enquiries | Sender and recipient identifiers, listing identifier, enquiry type, message, optional proposed offer and appointment time, business reply, status and date. | You and the business responding to you. |
| Practice auction sessions | Your site-specific user identifier, demonstration lot identifier, session identifier, opening and current virtual-credit amounts, bid increments, expiry, bid amounts and timestamps. These are private practice records, not sales or payment records. | Your use of the practice-bidding feature. |
| Technical connection information | Hosting infrastructure necessarily receives connection information such as IP address, requested URL, browser information and request times to deliver and protect the service. The form database does not add these fields to your enquiry. | Your browser and the hosting service. |
We do not ask for precise location, contacts, access to your photo library, microphone or camera, health information, identity documents or payment-card details on this website. Do not include sensitive information in free-text fields. An optional message is not required to register interest. Business members may voluntarily select and upload a listing image; no device-library access permission is requested.
3. Why we use information
- Handle enquiries: to understand and respond to your interest in buying, selling, brand participation or partnerships. Where applicable, this is to take steps you request before entering a contract, or our legitimate interest in responding to correspondence.
- Send requested launch news: based on the consent you provide. You may withdraw it at any time using the privacy form. Submission does not create a marketplace account or a purchase obligation.
- Provide requested account features: to save your member profile and collection, manage listing drafts and review submissions, and route private enquiries and business responses. We process these records to provide the website service you request and maintain its integrity.
- Manage privacy rights: to verify and fulfil access, correction, objection, withdrawal and deletion requests and meet applicable legal obligations.
- Operate and protect the site: our legitimate interest in reliable delivery, preventing abuse and preserving a minimal audit trail, subject to your rights.
We do not sell your personal information, use it for targeted advertising or make decisions with legal or similarly significant effects solely by automated processing. We do not enrich your registration with purchased personal profiles.
5. How information is protected
The deployed website uses HTTPS. Form submissions are validated on the server, requests from a different browser origin are rejected, and database writes use parameterised queries. There is no public endpoint that lists registrations or privacy requests. Account records are scoped to the authenticated member; seller replies are restricted to the recipient; listing moderation and private administration are restricted server-side to the configured owner identity. Listing images are public assets and must not contain confidential data. Provider-managed access controls protect the database; administrative access should be restricted to authorised personnel.
No internet service can guarantee absolute security. Do not send passwords, bank details, identity-document copies or other sensitive material through these forms. Any verification request should be proportionate to the information being handled.
6. How long information is retained
Early-access registrations are kept while needed to manage the enquiry and send the launch updates requested, unless you withdraw consent or ask for deletion. The pre-launch service has no confirmed fixed launch date or automatic expiry for these registrations. Records should be reviewed and removed when they are no longer needed; you can request removal now.
Member profiles, saved items, listing records, uploads, practice-auction sessions and bids, and conversation records are kept while needed to provide your account and requested business services, unless you request removal or the purpose ends. There is not yet an automatic expiry schedule for these records. Deletion requests must cover associated records and files as appropriate, rather than only disabling sign-in.
Privacy-request records and verification correspondence may be retained to demonstrate the request was handled and to meet a specific legal obligation or resolve a dispute. There is no published fixed retention period for those records yet. If an exception prevents deletion, we will explain the data concerned, the reason and the applicable period or criteria in our response. This website has no sales, payment or tax records from marketplace transactions.
Deleted information may remain temporarily in provider-controlled backups or security logs until their applicable retention cycle ends. A fixed backup or infrastructure-log expiry has not been verified. Such residual copies should not be used for marketing or returned to active use without reapplying the deletion. You may request the applicable details.
7. Cookies, analytics and external content
This website does not intentionally set advertising cookies, use tracking pixels or include an advertising analytics SDK. Editorial images and fonts are served with the website. A business may provide an externally hosted image URL; loading that image may send connection information to its host. Uploaded listing images are served through the website. ChatGPT sign-in has its own provider session and privacy terms. Language selection uses a URL rather than a profiling cookie. Hosting infrastructure may use essential operational or security mechanisms. Links to third-party websites, including privacy regulators, are governed by their own notices when you follow them.
8. Your choices and rights
Depending on the law that applies, you may request access or a copy of your information, correction, erasure, restriction of processing, portability, objection to processing based on legitimate interests, and withdrawal of consent. Withdrawal does not affect processing lawfully carried out before withdrawal. Rights can have legal limits.
Use the form below for any privacy request or visit Account Deletion to request deletion. No sign-in, purchase or app installation is required. We may need proportionate verification so that another person cannot obtain or delete your information.
For requests covered by the UK or EU GDPR, we will respond without undue delay and normally within one calendar month, subject to applicable identity-verification rules. Where permitted for complexity or multiple requests, this may be extended by up to two further months; we will notify you of the reason within the initial period. We do not normally charge for rights requests.
You can complain to the data-protection authority relevant to you. In the UK, contact the Information Commissioner’s Office. In the EEA, contact your local supervisory authority. You do not have to complain to us first.
9. Children
This early-access service is intended for adults aged 18 or over. We do not intentionally solicit children’s registrations. If you believe a child has submitted information, use the privacy form so we can review and remove it as appropriate.
10. Changes and future app services
The date above identifies this version. Material changes to collection or use will be described here and, where required, brought to affected users’ attention. New app permissions, SDKs, transaction records, payment providers, additional merchant sharing, app-store disclosures and any new retention rules must be assessed and disclosed before those features are enabled. This website notice must not be treated as a verified description of an uninspected app build.