Aisle Privacy Policy

Last updated 2026-10-28 · Aisle

The short version

1. What this covers

This policy covers the Aisle browser extension and the Aisle service it talks to. It is written and maintained by Aisle, who is the data controller for the information described below. If you have a question about anything here, write to [email protected].

It does not cover the websites you use Aisle on. Those sites have their own policies and their own practices, and Aisle's presence on a page does not change them.

2. What we collect, and why

WhatWhenWhy
The address (URL) and title of the tab you are viewing Whenever the side panel is open Aisle's rooms are anchored to URLs. This is how we know which room to show you, and how the room stays the same room for everyone looking at the same page. Addresses are normalized — tracking parameters and session identifiers are stripped before a room key is formed.
Your display name and, if you sign in, your Google account identifier, email address, name, and profile picture URL On sign-in To keep your identity, reputation, and history attached to you across devices, and to let moderators act on an account rather than a session. Signing in is optional.
Messages you post, votes you cast, and reports you file When you post, vote, or report They are the service. See section 4 — messages are public.
Questions you ask the AI concierge, and the answers it gives When you ask To answer the question, to keep the thread of a conversation within a room, and to cache answers so the same question is not billed twice.
Content from a web page — its product data, specification table, published reviews, and main body text Only on sites you have explicitly granted, and only at the moment you ask the concierge a question So the answer can set what the page claims against what people in the room found. See section 3.
The price a page publishes about itself, and whether it says the item is in stock Only on sites you have explicitly granted, when the panel opens on one of their pages So a page can tell you whether its price has moved since people were last looking at it. It is kept against the page, not against you — nothing records who was looking. See section 3.
Coarse usage signals: the panel being opened, a sign-in succeeding or failing, a websocket connecting or dropping, and client-side errors During normal use To know whether the service is working. This is a fixed, short list of event names — there is no click, scroll, keystroke, or mouse tracking of any kind.
Your IP address On each request, as with any web service Used to rate-limit abuse (for example, to stop one machine creating twenty identities an hour). It is used at request time and is not stored against your account or your messages.

We do not collect health information, financial or payment information, your precise location, your passwords, or the contents of pages you have not granted us.

3. Reading web pages: how the permission works

This is the part of Aisle most worth understanding, so it is stated plainly.

4. What is public

Aisle is a public conversation. Messages you post, the display name you post them under, your reputation score, and your votes' effect on a message's score are visible to everyone who opens the same room. Treat a message the way you would treat a public comment: do not put anything in one you would not want a stranger, an employer, or the site's owner to read.

Your email address is never shown to other users. Questions you ask the concierge, and the answers you get, are private to you: nobody else can read your conversation, and you can delete it at any time. The one exception is an answer you choose to share into the room: after you confirm, your question, that answer and any note you add are posted under your name, marked as shared from the concierge, like any other message you post — and deleting your conversation does not remove them from the room.

5. The AI concierge

When you ask the concierge a question, we send the following to a third-party AI provider in order to generate an answer: your question, recent messages from that room, and — if you have granted the site — the page content described in section 3.

The provider is a commercial AI service engaged as our processor under contract: it processes the request in order to return an answer, and is not permitted to use it to train its models. We do not send it your email address, your account identifier, or your IP address. If you want to know which provider is in use, ask us at [email protected] — we will tell you.

A second, smaller model is also used for moderation — it classifies messages that the fast automated checks flag as borderline. That means a message you post may be sent to an AI provider for classification before it goes live, on the same terms.

Answers are generated by a language model and can be wrong. They are not advice, and you should check anything that matters against the seller.

The room FAQ

A room can show a short list of common questions with answers written by Aisle, so newcomers can read them without asking. Entries get there in two ways:

Entries are never shown with anyone's name, are checked by the moderation model before they appear, and can be hidden by the room's moderators. Moderators can also correct an entry; a corrected entry is labelled as edited by a moderator, and its new wording is theirs, not Aisle's or any asker's. Deleting your concierge conversation deletes your questions. The counts behind the list stay: they hold no question text, only the fingerprint and a keyed hash that is used to count people and is never shown or used to look anyone up.

6. Moderation

Every message passes through automated checks before it is stored, and may be classified by the AI moderation model described above. Messages that are flagged enter a review queue that human moderators can read, along with the reports other users have filed against them. Moderators can delete messages, mute accounts, and — for repeated abuse — ban them. This is the one route by which a person other than you routinely reads a message that is not already public.

7. Who we share with

We do not sell personal information, and we do not share it with data brokers, advertisers, or ad networks. We disclose it only to:

If the service is ever acquired or merged, information may transfer to the acquirer, who would remain bound by this policy until you are told otherwise.

8. How long we keep things

WhatKept for
Messages, votes, and rooms Until you delete your account or a moderator removes the message. Rooms are a public archive by design.
Guest accounts that never posted anything Deleted automatically after 7 days of disuse. A guest account with messages is kept, because its identity is attached to visible content.
Sign-in tokens 30 days, extended by activity. Signing out revokes the token immediately.
Concierge conversations The most recent turns per room; older turns are dropped as new ones arrive, and everything goes when the account does.
Cached page content and cached answers Minutes to hours. These are caches, not records — they expire on their own.
Operational telemetry and error logs A rolling window for service monitoring, then discarded.

9. Your choices and your rights

Depending on where you live — including in the EEA, the UK, and California — you may also have the right to access a copy of your data, correct it, object to or restrict how it is used, ask for it in a portable form, and complain to your data protection authority. Write to [email protected] and we will answer within 30 days. We will not treat you differently for exercising any of these rights.

Where the law requires a legal basis, ours are: performing the contract you entered by using the service (showing rooms, delivering messages, answering questions); your consent (signing in with Google, granting a site's page access — each withdrawable as above); and our legitimate interest in keeping the service working and free of abuse (rate limiting, moderation, error monitoring).

10. Children

Aisle is not intended for children. Do not use it if you are under 13, or under 16 in the EEA and the UK. We do not knowingly collect information from anyone in that group; if we learn that we have, we delete the account. If you believe a child has an account, tell us at [email protected].

11. Security and transfers

Traffic between the extension and our servers is encrypted in transit. Access to production data is limited to the people who operate the service. No system is perfectly secure, and we do not claim otherwise — which is the practical reason messages are public by design and payment details are never collected at all.

Our infrastructure and our providers may be located outside your country, including in the United States. Where such a transfer is regulated, it is made under the safeguards the law requires, such as the European Commission's standard contractual clauses.

12. Changes to this policy

If we change this policy, the date at the top changes with it. A change that materially widens what we collect or who we send it to will be announced in the extension before it takes effect — not published here and left to be discovered.

13. Contact

Questions, requests, and complaints: [email protected].