Privacy

Who runs this site

This site and its Chrome extension are made by Aleh Vasilyeu, who decides what happens to the data this site collects.

Write to contact@almost.trade about anything on this page.

What the site collects

Visit counts

We use GoatCounter to learn how many people come, which pages they open and what share of them go on to search. Each time you open a page, it records:

• the page you open, without the part of its address that holds the item, so the item you search is never counted;
• the site you came from;
• your country, worked out from your IP address, and for a few countries the region too; the IP address itself is never written down;
• your browser, your operating system and the size of your screen.

It also counts six moments on the way to a search, each as a fixed label such as “search started”, never with the page’s address: the welcome page opening on a phone; the welcome page opening on a computer; sending yourself the welcome page’s link from a phone; pressing the welcome page’s button that opens the extension in the Chrome Web Store; opening the extension’s code on GitHub from the welcome page; and a search starting in the item finder.

GoatCounter sets no cookies and does not follow you to other sites. To tell a new visit from a reload, it holds your IP address and your browser’s details in memory for up to eight hours, never on disk. It deletes the counts after two years.

The counts tell us whether the site is useful and what to fix. This is our legitimate interest (GDPR Art. 6(1)(f)).

Problem reports

When you send a problem report from the item finder or the build page, our server emails it to us. It carries your text, your email or Discord name if you give one, the parts of the page you marked, the page’s address, your browser and system, its window size, the site’s version and when you sent it. Our server also reads how long the panel was open, to catch bots, and keeps nothing of it.

With the box ticked, it also carries the trade site’s answers for the search on screen, without sellers’ account and character names. From the build page, it carries the Path of Building code you pasted instead.

To stop spam, our server keeps a scrambled form of your IP address for an hour after you send, or for as long as we ban it. That form goes into the email too, and the email is the only copy of your report; we delete it once the problem is solved.

We use a report to fix what went wrong, and the scrambled IP address to stop spam. This is our legitimate interest (GDPR Art. 6(1)(f)).

Error reports

The site also sends our server an error report on its own when a page breaks or does not start, a search fails, the game’s data does not load, the currency exchange cannot be read, a pasted link or build code is refused, or a problem report cannot be sent. Each report carries the error’s name, the first 200 characters of its message, where in the site’s own code it happened, which part of the site it was on — the item finder, the build page or another — and, once the site has started, its version. We never add the address you are on, the item you search or the build you pasted, and any web address inside the message is cut down to the site’s name. Each page you open sends at most 20 reports, and the welcome page sends one only when it does not start.

The extension sends the same kind of report on its own when its code breaks. It carries the error’s name, the first 200 characters of its message, where in the extension’s code it happened, whether that was on a guide page or in the part of the extension that talks to the trade site, and the extension’s version.

On a mobalytics guide page it also reports a trade link it cannot read or cannot place a badge beside, and a guide you leave on which it found no trade link at all. Such a report holds a fixed label for what it could not do instead of an error’s name and message. The extension never adds the guide’s address, the item or your pathofexile.com login, and any web address inside a message is cut down to the site’s name. Each mobalytics page you load sends at most 20 reports, and the part that talks to the trade site at most 20 per run, which Chrome ends after about thirty seconds with nothing to do.

Our server writes each report to Cloudflare’s logs, which are emptied after three days. The reports of a page that broke or did not start, and of the extension’s code breaking, also go into a list of errors Cloudflare holds for us, and beside each one it stores your country, worked out from your IP address, and the browser and system your browser names. The IP address itself is dropped, and Cloudflare does not say how long the list lasts.

The reports show us that something broke before anyone has to write in. This is our legitimate interest (GDPR Art. 6(1)(f)).

Serving the pages

Cloudflare, which hosts this site, receives your IP address, the page you open and your browser’s details with each request, and the time it came. The page’s address carries the item you search, so Cloudflare sees which item that is. Neither we nor Cloudflare, for us, keep a record of these requests. Only what Problem reports and Error reports above set out is kept.

Cloudflare needs this to run the site and protect it from abuse. This is our legitimate interest (GDPR Art. 6(1)(f)). What Cloudflare itself does with it is set out in its own privacy policy.

What stays in your browser

This site sets no cookies.

While you search, the site keeps the trade site’s answers in your tab’s session storage, so a reload, or opening the same link again in that tab, does not run the searches again. A Path of Building code you paste is kept there too, with the item set you chose, so a reload does not lose your build. Your browser deletes both when you close the tab, and they are never sent anywhere unless you attach them to a problem report.

The trade site lets each player search only so often. So that all your Almost tabs share that limit, your browser’s local storage keeps the time your next request to the trade site may go out. Beside that time it keeps whether the trade site’s last answer found you logged in, so the next item you open from a guide goes straight to the screen for that login. Both stay until you clear this site’s data and never leave your browser.

The extension

The Almost extension for Chrome runs the trade searches for you.

• It sends requests to www.pathofexile.com, of four kinds: run a search, fetch the items for sale it found, read the trade site’s own reference lists, and — only when you press Travel to Hideout — ask the trade site to send your character to the seller’s hideout, as its own button does.
• Your browser adds your pathofexile.com login cookie to those requests, as it does when you search on the trade site yourself. The extension never reads that cookie, and this site never sees it.
• Before a search it reads from web.poecdn.com what each currency traded for on the game’s currency exchange in the last few hours, so prices in different currencies can be compared. That request carries no login.
• It also runs on mobalytics.gg/poe-2 guide pages. There it reads the page to find trade links and adds the Almost badge to each item that has one, except uniques. It sends mobalytics nothing.
• When its code breaks, or when a guide has a trade link it cannot badge, or none at all, it sends our server a short error report, as Error reports above sets out.
• Chrome lists every site the extension runs on when you add it.
• The answers go only to the Almost page open in your own browser. The answers never reach us, unless you attach them to a problem report.
• It stores nothing and has no analytics. Chrome gives it no access to your cookies, tabs or storage.
• You can check what the extension sends, and where, in its code on GitHub. Each version in the Chrome Web Store is built there, from that code.

The extension’s use of data follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Other services

Grinding Gear Games’ picture and data server, web.poecdn.com

Item pictures and currency icons load from it, as on pathofexile.com, whenever this site cannot show a copy of its own; so do the icons of the skills an item grants. The extension reads the game’s currency exchange there too. Your browser asks that server directly, which shows it your IP address.

pathofexile.com

The extension’s searches go there, and so does Travel to Hideout when you press it. Grinding Gear Games’ terms of use and privacy policy apply there.

Cloudflare

Hosts this site and keeps the error reports, the extension’s included; both are set out under What the site collects.

GoatCounter

Counts visits, as listed under Visit counts.

mobalytics.gg

Where the Almost badge appears on guides. The extension sends nothing to mobalytics; your visit there falls under mobalytics’ own privacy policy.

This site serves its fonts itself and loads no script from another company.

Cloudflare may handle your request outside the EU. For that it relies on the EU–U.S. Data Privacy Framework and, where that does not apply, the EU’s Standard Contractual Clauses. GoatCounter keeps the visit counts in the EU, in Finland and Germany.

What we never do

• Ask you to sign up or log in here. The only login a search uses is your own, on pathofexile.com.
• Sell your data or share it for advertising.
• Show ads.
• Track you across other sites.

Your rights

You have the right to:

• see the data we hold about you;
• have it corrected or deleted;
• limit or object to how we use it;
• receive it in a portable form;
• complain to the data-protection authority in your country.

To use them, write to contact@almost.trade. We answer within one month. There are no accounts, and the visit counts hold no IP address; the list of errors keeps only a country, a browser and a system beside each entry. So unless you sent us a problem report, we usually hold nothing that points to you. Tell us what you would like us to look for.

Children

This site is made for Path of Exile 2 players and is not aimed at children. It needs no personal details from anyone; the email or Discord name on a problem report is optional.

Changes to this page

When we edit this page, we update the date at the top.