Loading the page
1.1The Admarket platform is operated by Admarket, Inc., a corporation incorporated in the State of Delaware, United States (“Admarket”, “we”, “us”). This policy explains what personal data we handle, why, on what legal basis, who we share it with and what you can do about it.
1.2It covers everything reached through the platform: the public marketplace, the seller store pages, search and landing pages, the dashboards, the admin tools, messaging, the support system, the Job Network and the sponsorship board.
1.3It applies to buyers, sellers, workspace members, AdBrokers, job posters and applicants, sponsorship posters and their guardians, support requesters without an account, and visitors who are only browsing.
1.4It sits alongside the terms of service and the cookie policy. Words defined in the terms of service have the same meaning here.
2.1Admarket is the controller of the personal data it holds to run the platform: accounts, listings, orders, held payments, proof, messages, tickets and the records behind them.
2.2The other side of a transaction is a separate, independent controller of the data it receives through the platform. When a seller receives a buyer's booking details, or a job poster receives an applicant's CV, or a sponsor receives a guardian's message, that party decides for itself what it does with that data — and is responsible for it under the law that applies to it.
2.3We require every user to use another user's data only for the transaction it was shared for. We do not, and cannot, supervise what each party does with it after that. If you have a concern about how another user handled your data, tell us and tell them; we will act on it under the terms of service, but the responsibility for their handling is theirs.
In short — We are responsible for the platform. The person on the other side of your order is responsible for what they do with what the order shows them.
3.1Data you give us:
3.2Data the platform creates:
3.3Data collected automatically:
3.4We do not ask for special category data — health, beliefs, political opinions, biometrics — and you should not put it into listings, messages, CVs or tickets. If it arrives anyway, we handle it only to run the process it arrived in, and delete it where we can.
3.5We do not collect or store bank account numbers or full card numbers. Those go to our payment partner directly.
4.1We use personal data for the purposes below. Where the UK GDPR, the EU GDPR or an equivalent law applies, the legal basis for each purpose is given with it.
4.2Where we rely on legitimate interests, we have weighed them against your rights and concluded they do not override them. You can ask us for that assessment, and you can object — see section 16.
5.1All conversations on the platform are monitored. Automated systems scan every message; a person reviews what is flagged. We do this to detect fraud, protect users from harm, enforce the terms of service, and preserve evidence for claims.
5.2Sharing off-platform contact details is flagged automatically, and a moderation note is posted into the thread where both parties can see it. Monitoring is not conducted secretly and enforcement is not conducted behind your back.
5.3Deleting a message hides it from a view; it does not remove it from our records. “Delete for everyone” leaves a visible marker in the thread and the original is retained for moderation and claim review.
5.4If you invite colleagues into a workspace, tell them their messages on the platform are monitored. You are responsible for informing your own team, and where you are their employer, for doing so in the way your local employment and privacy law requires.
5.5Do not use platform messaging for anything you would not want reviewed: no passwords, no card numbers, no confidential material unrelated to the transaction.
6.1Content submitted to the platform is screened automatically before it goes live: listings, job posts, sponsorship posts, reviews, store text, case studies, creative and message attachments. The screening returns a pass, a warning or a failure with reasons.
6.2Part of that screening uses a third-party artificial intelligence service, Google Cloud's Vertex AI. Where it applies, the text of the listing being screened — its title, description, format, dimensions, location, price, audience figures and categories — is sent to Google, which processes it on our instructions under contract terms that do not permit it to be used to train Google's models. The rest of the screening runs on our own systems against fixed rules.
6.3Your private messages are not sent to that service. Neither are CVs, job applications, support tickets, proof media or payment data. What is sent is content you are publishing to a public marketplace.
6.4Content that passes is published without a person seeing it. Content that fails or cannot be cleared goes to a human review queue and waits for a decision by a member of our team.
6.5You always have the right to a human decision. If automated screening blocks something you published, it is already routed to a person; if you believe an automated outcome is wrong, open a support ticket and a person will review it, hear your point of view and decide.
6.6Automated screening is a filter, not a verification. It does not check whether your claims are true, and passing it does not mean we have approved, endorsed or verified anything — see section 7 of the terms of service.
6.7We also use automated checks to screen payments and accounts for fraud and sanctions exposure, which can result in a payment being blocked or an account restricted. A person reviews any restriction you challenge.
7.1Listings and other user-generated content are translated automatically into the platform's languages, so the marketplace can be read worldwide. The service we use for this is Google Cloud's Vertex AI, the same provider as the automated screening in section 6, on the same terms: it processes the text on our instructions and may not use it to train Google's models.
7.2What is sent for translation is content you publish: listing copy; the copy of advertising assets, bundles, sponsorship posts and services; reviews you write about a seller; and a seller's public profile description. The service is also asked to identify the language a piece of that content is written in.
7.3Content you publish is sent to that service for translation. Do not put personal data into a listing that you would not want translated and published — a listing is public by design. A review you write carries your workspace's name when it is published, and the text of it is translated the same way.
7.4Interface text is translated by people, not machines. Private messages are not machine-translated for publication, and are not sent to the translation service at all.
8.1Proof photographs and video document advertising in public places. People walking past, vehicles and shopfronts can appear in them incidentally, and photographs carry the date and the coordinates where they were taken.
8.2We use that media for one purpose: evidencing delivery on the order it belongs to. It is shown to the two parties to the order, used in a claim if one is opened, and produced to a court, regulator or payment partner if we are required to produce it.
8.3Where a seller enables it, proof photography of their own space may also appear in that seller's listing gallery as recent evidence of live campaigns. Sellers must not upload proof showing identifiable individuals as the subject of the photograph.
8.4Sellers are responsible for taking proof lawfully in the place they take it, including any local rule about photography, and for the people who appear in it. If you appear in proof media and want it addressed, contact us — see section 22.
9.1Payments and payouts are handled by Stripe. Card details, bank account details, identity documents and tax forms go to Stripe directly and are held by Stripe as a controller in its own right, under Stripe's privacy policy.
9.2Admarket does not hold card numbers or bank account numbers. What we see and store is the transaction record: amounts, currency, status, holds, releases, refunds, payout status, commission and a masked summary of the destination account.
9.3Sellers and AdBrokers complete identity and business verification through Stripe. We receive the outcome — verified, pending, documents outstanding — and act on it. Where Stripe cannot decide, a member of our team reviews the case.
9.4We screen accounts, payments and payouts against sanctions and fraud signals, and keep the records that anti-money-laundering and tax rules require us to keep.
10.1When you apply for a job posted on the platform, your application — your message, your CV, your portfolio and your account profile — goes to the employer who posted it. From that moment the employer is an independent controller of it and decides what happens to it.
10.2Admarket does not screen, rank, score or assess applicants, does not verify anything in a CV, and takes no part in the hiring decision. We are not an employment agency and we hold no candidate database for sale or search.
10.3Employers must use applications only to consider the person for the role advertised, keep them no longer than their own law allows, and comply with their own obligations as a controller — including telling applicants how long they keep them.
10.4Do not include in an application anything an employer must not ask for in your country. A CV attached to a message can be seen by whoever the employer has given access to their workspace.
11.1Sponsorship posts are public. Everything in a post — the exposure inventory, the audience figures, the story, the photographs and the name of the party seeking sponsorship — is visible to anyone browsing.
11.2Where the person being sponsored is under 18, the post must name an adult guardian, and that guardian must be the person submitting it: they confirm as much when they submit, and their identity is verified by government-ID check before the post publishes. The guardian's own workspace is the only route in — every message goes there, and there is no way to contact a minor directly through Admarket. That routing cannot be switched off.
11.3The guardian is responsible for what is published about the minor and for consenting to it on the minor's behalf. Publish the minimum: a first name and a discipline is usually enough, and a home address, a school name, a training schedule or a direct contact never belongs in a post.
11.4We review sponsorship posts before they go live and will not publish one about a minor without a named, verified adult. Review is a filter, not supervision of the arrangement that follows.
11.5A guardian may ask us to remove a post and the data in it at any time, and we will act on it promptly.
12.1A marketplace works by showing things. When you publish, the following is public and is indexed by search engines: your listings, your seller store page, your business name, business type, location, coverage, founding year, team and ownership details, accreditations, case studies, ratings, reviews and response times, and the name and role of the contact person you nominate.
12.2Reviews you write are published with your workspace's name attached. Sponsorship posts are public. Job posts are visible to members only. Private listings are shown only to the workspace they are addressed to, and are excluded from search, maps and indexing.
12.3The dashboard and the admin panel are closed to search engines entirely.
12.4Anything you make public can be copied by others once it is out there. Publish the business, not the person: use a role inbox rather than a personal one where you can.
14.1Admarket is a global marketplace operated from the United States, and its providers operate internationally. Your data will be transferred to and processed in countries other than your own, including the United States.
14.2Where data is transferred out of the United Kingdom or the European Economic Area, we rely on an adequacy decision where one covers the transfer, and otherwise on the Standard Contractual Clauses (with the UK Addendum where relevant), together with the additional technical and organisational measures the transfer requires.
14.3The automated screening and the automatic translation described in sections 6 and 7 are not pinned to a region. Content sent to that provider may be processed in any country in which it operates, and we do not choose or control which. That transfer relies on the Standard Contractual Clauses described above, and on the provider's own contractual commitments about how it handles what we send.
What this means in practice — The listing text you publish, and the reviews and profile copy that are translated with it, may be processed outside the UK and the EEA. Your messages, applications, tickets and payment data are not sent to that provider at all.
14.4You can ask us for details of the safeguards applied to a particular transfer — see section 22.
15.1Closing your account does not delete records we are required to keep, and does not delete the record of an order, a claim or a moderation decision. Where we must keep something, we keep the minimum and stop using it for anything else.
16.1Depending on where you are, you have some or all of the following rights over your personal data:
16.2Much of this you can do yourself: edit your profile and workspace details, manage notification preferences, review and end open sessions, and close your account from the account page.
16.3For anything else, open a support ticket and we will answer within one month, extending only where the request is complex and telling you if we do. We may need to verify who you are before we act.
16.4Rights are not absolute. We may refuse or narrow a request where we must keep a record — an order, an invoice, proof, a claim, a moderation decision — and we will tell you which exemption applies.
16.5If you are unhappy with how we handled a request, you can complain to your data protection authority: in the UK, the Information Commissioner's Office; in the EU, the authority in your country of residence or workplace.
17.1If you live in a US state with a comprehensive privacy law — California, Colorado, Connecticut, Virginia and others — you have rights to know, access, correct, delete and, in some states, appeal a decision, and you may use an authorised agent.
17.2We do not sell personal information and do not share it for cross-context behavioural advertising, as those terms are defined in California law. We do not use or disclose sensitive personal information beyond the purposes permitted without a right to limit.
17.3We will not discriminate against you for exercising a right. Requests go through the same route as section 16.
19.1The platform is a business marketplace. Accounts are for adults: you must be 18 or over to register, and we do not knowingly collect personal data from children through an account.
19.2The single exception is a sponsorship post about a person under 18, which exists only through a named, verified adult guardian and is governed by section 11.
19.3If you believe a child has registered an account, tell us and we will close it and delete the data.
20.1We protect the platform with encryption in transit, hashed passwords, optional two-factor authentication, per-role access controls enforced on the server as well as in the interface, session management you can see and revoke, audit logging of administrative actions, and separation of the payment and identity data we deliberately do not hold.
20.2No system is perfectly secure. If a breach affects your personal data and is likely to result in a risk to you, we will notify you and the relevant authority within the time the law requires.
20.3Your part matters: use a strong, unique password, turn on two-factor authentication, review your open sessions, and remove members who have left your organisation.
21.1We update this policy as the platform changes. The current version is always published here with its date.
21.2Material changes are notified before they take effect, by email or in the platform. Where a change requires your consent, we will ask for it rather than assume it.
22.1Privacy questions, rights requests and complaints reach us through the support system on the platform, which attaches them to your account and routes them to the team that covers your market.
22.2If you do not have an account, use the public contact page; a ticket opened that way is answered by the email address you give.
22.3We will always answer you first. You are entitled to go to your data protection authority at any time, whether or not you come to us first.
See also the regulamin and the polityka plików cookie. Questions? Napisz do zespołu.