Privacy Policy

Awelora analyses supported listing information on the Vinted UK website to provide BUY, OFFER, REVIEW and SKIP decisions, estimated resale information and opportunity tracking. This processing is necessary for the extension's single purpose.

Awelora analyses information from pages the user chooses to browse. The current 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 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;
• market-memory data used to support local estimates;
• a local record that the user accepted Awelora's first-run data-use disclosure.

Listing information, browsing activity on supported Vinted pages, saved opportunities, buying settings, recorded outcomes and market-memory information are stored locally in Chrome extension storage. Awelora does not currently transmit those categories to its servers as part of account pairing.

When a user chooses to connect 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 advertising, use it for credit or lending decisions, or allow people to read it. The extension does not load or execute remotely hosted code.

Before Awelora begins analysing Vinted pages, the extension presents a first-run disclosure explaining the website content it processes, why it is needed and where the resulting information is stored. Analysis begins only after the user accepts that disclosure.

The storage permission is used to save settings, market memory, opportunities, feedback, outcomes, account-pairing state and the first-run disclosure choice locally so they remain available between browser sessions.

Access to https://www.vinted.co.uk/* is used only to read supported listing information and display Awelora's user-facing analysis on Vinted UK pages. The extension is not permitted to read general browsing activity on unrelated websites.

When account pairing is enabled, the extension may also communicate with Awelora's own HTTPS service only for authentication, pairing, entitlement and device-authorisation purposes.

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 may remain until they are revoked or no longer reasonably needed for account security and abuse prevention.

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.

When a person submits an Awelora early-access form, the website may collect their first name, email address, Vinted experience, resale interests, usage frequency, optional message and acceptance of the early-access disclaimer. This information is used only to manage early access, contact applicants and improve the product.

Early-access submissions are stored using Supabase. Account/device pairing records are stored using Cloudflare D1. They are not sold or used 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. Website and pairing information 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. Early-access data is retained only for as long as reasonably needed to manage access and communications.

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, tracking, authentication and account-security features.

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.

Questions or deletion requests relating to Awelora account, device or early-access information can be sent to hello@awelora.com.