Loading the page
2.1Admarket uses cookies for three things: keeping you signed in and acting as the right workspace, remembering the choices you make about how the marketplace is shown to you, and letting our payment partner detect fraud at checkout.
2.2That is the whole list. Nothing on Admarket follows you around the wider web, builds an advertising profile of you, or is shared with an advertising network.
The irony is not lost on us — We sell advertising space for a living and we set no advertising cookies. Tracking you across the internet is a different business from selling a billboard, and we are not in it.
3.1These make the platform work. Without them you cannot sign in, stay signed in, act as the right workspace, or complete a booking. They are set because you asked for a service that needs them, they require no consent, and they cannot be switched off from within the platform.
| Cookie | What it holds | Lifetime |
|---|---|---|
| admarket.session_token | Your signed-in session. Set by the Admarket API, HTTP-only and — in production — secure, so no script on the page can read it. | 30 days, refreshed each day you use the platform |
| admarket.session_data | A short-lived cached copy of your session so every page load does not have to reach the database. Signed, HTTP-only. | 5 minutes |
| am_ws | Which of your workspaces you are currently acting as. Needed before the first byte of the dashboard is rendered, because the navigation itself depends on it. The value is always checked against the workspaces you actually belong to — a hand-edited cookie gets you nothing. | 1 year, or until you switch workspace |
3.2Sign-in uses an email address and password, so there are no third-party sign-in cookies. Our sessions are protected by origin checking rather than a separate anti-forgery cookie.
4.1These remember the choices you make in the preferences panel at the bottom of every page: the country you are browsing, the currency prices are shown in, whether measurements are metric or imperial, the language, and light or dark theme.
4.2They are set only when you actually choose something. While a cookie is absent the value follows your country, which is how picking a country changes the default currency without ever overwriting a choice you made yourself.
| Cookie | What it holds | Lifetime |
|---|---|---|
| am_country | The country you are browsing, as an ISO 3166-1 code — DE, GB, TR. It decides which inventory the page is built from, so the server has to know it before rendering. | 1 year |
| am_currency | The currency prices are converted into for display, as an ISO 4217 code. Charges are always taken in the listing's own currency, whatever this says. | 1 year |
| am_measure | metric or imperial — whether a billboard is shown in metres or feet. | 1 year |
| am_locale | The language you last chose, so a request that arrives without a language in the address goes to your language rather than to English. | 1 year |
| am_theme | light, dark, or absent. Absent means follow your operating system, which is the default until you choose. | 1 year |
4.3None of these are HTTP-only, because none of them is a credential. None contains your name, your email address or anything that identifies you personally.
4.4Language is also carried in the address itself — every Admarket URL begins with it. The cookie only decides where you land when the address does not say.
5.1One cookie exists only inside the admin panel and is never set for a marketplace visitor.
| Cookie | What it holds | Lifetime |
|---|---|---|
| am_staff | Which Admarket staff identity the admin panel is being viewed as, so the panel can be seen through each role's permissions rather than only a superuser's. Set only for our own team, on our own tools. | 1 year |
6.1One provider sets cookies in the course of doing its job for the platform: Stripe, our payment partner. Its scripts load on the pages where you pay, and they set cookies used to detect and prevent payment fraud.
| Cookie | What it holds | Lifetime |
|---|---|---|
| __stripe_mid | A Stripe device identifier used for fraud prevention. Set by Stripe, not by Admarket. | 1 year |
| __stripe_sid | A Stripe session identifier used for fraud prevention during a single checkout. | 30 minutes |
6.2These are strictly necessary to take a payment safely, and blocking them will stop checkout from working. Stripe's own privacy and cookie policies govern what it does with them.
6.3There are no advertising-network cookies on Admarket, no social media pixels, no third-party tag managers and no data brokers. We do not embed anything that watches you on our behalf.
7.1Admarket currently sets no analytics cookies. Nothing on the platform measures your behaviour across pages by storing an identifier in your browser today.
7.2If we introduce analytics, we will do it on these conditions, and we are writing them down now so we are held to them: the tables above are updated before the cookie ships; the measurement is anonymised or aggregated; where the law requires consent, the cookie is set only after you give it and never before; and it will never be used for advertising.
7.3Our servers keep ordinary technical logs — the requests they answer, with IP addresses and timestamps — for security and debugging. That is not a cookie, you cannot turn it off, and it is described in the privacy policy.
8.1Preference cookies you manage in the platform: open the preferences panel from the bottom of any page and change country, language, currency, units or theme. Setting a preference back to “follow the country” clears the cookie rather than pinning a value.
8.2Everything else you manage in your browser. Every major browser lets you see the cookies a site has set, delete them, block third-party cookies, or block all cookies for a site. The controls are usually under Settings, then Privacy.
8.3What breaks if you block them:
8.4Signing out ends your session and clears the session cookies. Closing your account removes the rest on your next visit; you can also clear them yourself at any time from your browser.
8.5Your browser's “do not track” or global privacy signal is respected in the sense that there is nothing to stop — we run no tracking to turn off.
9.1The tables in this policy are part of the platform, not a document that drifts away from it. When a cookie is added, removed or has its purpose or lifetime changed, this page is updated in the same change.
9.2Material changes — a new category of cookie, or anything that would require your consent — are notified before they take effect, and consent is asked for rather than assumed.
10.1Questions about cookies, and requests about the data behind them, reach the team through the support system on the platform. If you do not have an account, use the public contact page.
See also the terms of service and the privacy policy. Questions? Message the team.