Privacy Policy

Awelora analyses supported listing information on supported Vinted websites to provide BUY, OFFER, REVIEW and SKIP decisions, estimated resale information and opportunity tracking. This processing supports the extension's single purpose of helping users make better-informed resale decisions.

Awelora analyses information from pages the user chooses to browse. The extension does not independently crawl Vinted, automatically revisit listings in the background, or buy, offer, message or otherwise transact on the user's behalf.

The extension may process the following information from supported Vinted pages:

• listing titles, prices, URLs and image URLs;
• condition, size, category, product model and other visible listing details;
• the supported Vinted pages and listings with which the user interacts.

The extension may also store information supplied or created by the user:

• buying rules, risk preferences and extension settings;
• saved opportunities and status information;
• purchase prices, sale prices, selling costs and recorded outcomes;
• feedback about models, estimates, conditions or decisions;
• local market-memory data and deduplication records;
• the user's market-contribution consent choice.

If the user affirmatively enables market contribution, Awelora sends a limited, structured market observation to Awelora's HTTPS service after a supported listing is analysed. These observations are used only to provide and improve Awelora's core resale intelligence, including region-specific market evidence and estimates.

A collective market observation can include:

• marketplace and region;
• brand, product model, category, size and condition;
• asking price and Awelora's estimated resale values;
• the BUY, OFFER, REVIEW or SKIP result, score and confidence;
• comparable-sample counts and market-quality signals.

The collective observation does not include the listing URL or image URL, seller identity, seller messages, contact details, or the user's name or email address. Before transmission, the Awelora account identifier is converted into a one-way pseudonymous hash so market observations are not stored under the user's direct account identifier.

Listing URLs may be processed locally to create a one-way deduplication key so the same listing is not repeatedly contributed after a refresh. The raw listing URL is not sent in the collective market-observation request.

Market contribution is off unless the user accepts the in-extension disclosure. A user who does not enable it can continue using Awelora's normal resale-analysis features.

Buying settings, saved opportunities, recorded outcomes, feedback, local market memory, deduplication information and other extension state are stored locally in Chrome extension storage unless this policy expressly describes a server-side use.

When a user connects the extension to an Awelora account, limited account and installation metadata is transmitted to Awelora so the service can authenticate the installation and enforce account/device limits. This can include a randomly generated installation identifier, a user-facing device name, pairing status and timestamps, and the Clerk account identifier of the user who authorises that installation.

A device credential is generated for the installation. Awelora stores only a cryptographic hash of that device credential and of temporary pairing tokens in its server-side database; the plaintext device credential remains with the extension.

Awelora does not sell extension data, use it for personalised advertising, use it for credit or lending decisions, or permit routine human access to raw extension data. The extension does not load or execute remotely hosted code.

The storage permission is used to save settings, market memory, opportunities, feedback, outcomes, account-pairing state, consent choices and local deduplication data between browser sessions.

Access to supported Vinted websites is used only to read supported listing information and display Awelora's user-facing analysis on those pages. The extension is not permitted to read general browsing activity on unrelated websites.

The extension communicates with Awelora's own HTTPS service for authentication, pairing, entitlement, device authorisation and, where the user has opted in, structured collective market observations.

Users may choose to export, copy or import extension backups. Files or clipboard data created through those user-requested actions are controlled by the user.

Users can remove locally stored extension information by clearing the extension's data in Chrome or uninstalling Awelora. Uninstalling removes Chrome extension storage from that browser profile. Server-side account/device authorisation records and collective market observations may remain while reasonably needed to operate, secure and improve Awelora, subject to applicable deletion rights.

Users may request deletion of server-side information associated with their Awelora account by contacting Awelora at the address below.

Awelora uses Clerk to provide website account authentication. Clerk processes the account information needed to create and operate a login, such as an email address, authentication credentials and session information, according to its role as Awelora's authentication service provider.

Awelora uses Cloudflare infrastructure, including D1 databases, to operate account, device and collective market-memory services. Payment and subscription information may also be processed by the payment providers used by Awelora. Service-provider data is not sold or used by Awelora for personalised advertising.

Information may be disclosed only to service providers needed to operate the service, where required by law, for security purposes, or as part of a lawful business transfer.

Awelora uses reasonable technical and organisational safeguards appropriate to the information handled. Information sent between the extension, website and Awelora's services is transmitted over HTTPS. Sensitive pairing credentials and temporary pairing tokens are stored server-side only as cryptographic hashes.

Local extension data is retained until the user clears it or uninstalls the extension. Temporary pairing requests expire after a short period. Device-authorisation records are retained while reasonably needed to provide account access, enforce device limits, investigate abuse and support account security. Collective market observations are retained while reasonably needed to provide and improve Awelora's regional market intelligence, unless deletion is required sooner.

Awelora's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only to provide or improve Awelora's disclosed resale-analysis, market-intelligence, tracking, authentication and account-security features. It is not used for personalised advertising or sold to third parties.

This policy may be updated when Awelora's features or data practices change. Material changes will be reflected on this page with a revised date and, where required, will be disclosed within the extension before the changed collection begins.

Questions or deletion requests can be sent to aweloraresale@gmail.com.