How the platform works

Brands

Every brand is the anchor for everything else: keywords, watch profiles, alerts, cases and reports all hang off a brand. It is also the main filter on your dashboard.

What to provide

The commercial name, the registered titles attached to it — filing number, office, Nice classes, jurisdictions — and the official assets that must never be reported.

Keywords

Each keyword carries a type that determines its role in the search.

Statuses

An inactive keyword stays visible but is no longer scanned.

Actions

Watch profiles

A profile ties a brand to a selection of keywords, a set of channels and a frequency. It is what triggers the automated scans.

Channels

Marketplace, social network, search, advertising, app store, domain names. The domain names channel runs through a separate pipeline (monitoring of new registrations) and feeds domain alerts; every other channel feeds ordinary alerts.

Geographic and language scope

The anchor markets decide which country the search is issued from and which marketplace domain is queried (amazon.fr, ebay.fr…). Every market you add multiplies the external calls. The languages covered, on the other hand, are combined into a single query: adding more costs nothing.

Frequency and statuses

Hourly, daily, weekly or monthly.

Actions

Exclusions

An exclusion applies upstream of triage: matching future alerts are set aside automatically, and alerts already present are re-evaluated the moment the rule is activated.

Two possible effects

• Ignore files the alert silently — it disappears from your triage screens.
• Reject marks it as dismissed, keeping a record of the reason.

Scope

A rule can be limited to one or several brands, or apply to the whole organization. You create it from this module or straight from an alert, which pre-fills the value.

Official assets

Declare them in their own module so they are never reported. The Verify ownership action checks a DNS TXT record on the domain before adding it to the allow list — that is what stops a third party from passing their site off as yours.

Alerts

An alert is a page: a marketplace listing, a search result, a post, an advert. It carries the URL, the title, the seller, the price, the country, the detection date and the watch profile that produced it.

Reading the list

Each card carries two colours, and they answer two different questions. The left edge is the status — where the alert sits in the workflow. The strip across the thumbnail is the risk band — how much it matters. An alert can be escalated and low risk, or never reviewed and critical, so neither colour can stand in for the other.

Why this score

Every alert sheet carries a Why this score block: the score, its band, and the signals present on that alert — where the brand name was found, the name similarity measured at collection, the watch term that found it, what kind of site it sits on, whether goods are priced. A minus sign marks what is missing, including the one that explains most surprises: the page has never been opened.

Narrowing the list

Six filters, and each option says how many alerts it would leave you. The counts are computed against the filters you have already set, so an option is never offered that leads to an empty list — and choosing an organisation reduces the brand list to that organisation’s brands.

Enrichment

A raw alert only contains what the search engine returned. Enrichment actually opens the page to extract the product, the seller and their contact details. The state shows on every row:

Actions

The Workflow menu on an alert opens with Promote to case highlighted and first. It is the step the rest of the alert exists for; everything else on the menu is a way of not doing it.

Domain alerts

These alerts do not come from a page but from monitoring of the registries. Each row is a brand × domain pair, with the registration date and a typosquatting score.

Reading the score

The registry action column states the event observed: added (a fresh registration, the most sensitive case), updated or dropped.

Statuses

Actions

Cases

A case brings together one or more alerts covering the same infringement. It carries a reference, a brand, a priority, an owner, a risk score and a summary written during analysis and then reviewed.

The priority (low, medium, high, critical) is proposed automatically and stays editable. The risk score (0–100) is computed from the attached alerts.

Taking cases out of the portal

The Export button offers four documents, and every one of them is built from what the filters have left on screen — the filters themselves are printed on the document, because a list of forty cases out of three hundred with nothing saying which forty will be misread the week after it is sent.

The case record

Every case opens on a summary view gathering the screenshot, the identified product, the operator, the legal grounds, the actions taken and the exchanges. The analysis buttons are directly available there. After each action the record shows the state of the last run: in progress while the analysis is running, then done or error with the message returned. An action in progress is not blocking — you can carry on working.

Actions

Products

When the same counterfeit is sold across twelve listings, the platform gathers them into a single product record: name, reference, description, image, price range, number of sellers, first and last sighting.

What to look at

Brand use confirmed means the brand does appear in at least one listing — that is the signal separating an infringement from a mere resemblance. The counterfeit indicators list the signals picked up (price, wording, origin). The estimated Nice class is compared with the classes of your registered titles.

Statuses

Product sellers

Every one of them is on the Product sellers page. An observed seller only becomes one we act against once its listings infringe your rights. The status carries that nuance: Active for a confirmed infringement, Monitoring while doubt remains, Allowed for a legitimate reseller, Excluded for a definitive false positive.

The record

Entity type (individual, company, network), country, risk level, structured postal details, emails, contact form, own website, selling countries, observed identifiers (VAT numbers, registrations, accounts). The linked products, domains, cases and actions are listed there.

What we still have to find

A letter needs four things: a contact, an email, a postal address and a country. Each card carries four dots saying which of them we hold, the Ready to write tile counts the sellers that have all four, and the Data found buttons narrow the list to the ones that carry the facts you need — press two and you get the sellers reachable both ways.

Correcting a seller

This page is editable. Open a seller and use Edit this sheet: the form offers exactly the fields your role may change, so what you see there is what you may write. New seller records one by hand — a name is enough to start, and the rest is filled on the sheet that opens.

The marketplace is not the seller

A listing on a marketplace involves two companies, and they are not interchangeable. The venue is the site the listing sits on; the seller is the trader who put it there. A sheet can carry both, and the one you are acting against decides where the letter goes: a cease and desist meant for the trader, addressed to the marketplace’s legal department, reaches a company that did not make the goods and cannot stop making them.

The platform works it out from the listing itself — the storefront, the site it is on, and the marketplace reference list — and shows you what it concluded. Where it is wrong, say so on the sheet: a correction made by a person is recorded as one, and it is not overwritten the next time the site is scanned.

Actions

Taking the list with you

Export offers four: seller sheets as a PDF (the twenty most recent of whatever the filters left, one block each), the whole filtered list as an Excel workbook or as CSV, and the table printed as it is. Every one of them names the filters that produced it on the document itself.

Domains

A domain appears here once, whichever brand is concerned, with its registration data, its host and its country. Domain alerts point to it; this is where the history consolidates.

Actions

Preparing a demand, step by step

A cease and desist is not a form. It is a chain of findings — what you own, who they are, whether the two collide — and each link has to hold before the next one is worth making. The request page walks that chain: ten steps, each one a single question, each settled by a person and stamped with their name and the date.

Nothing advances on its own. A step becomes settled when you say it is, and the green button at the foot of the panel then carries you to the next question. You can go back to any step and change your answer; the trail keeps both, because a decision that changed is more informative than a decision that appears never to have been made.

The ten steps

Steps 2 and 4: the two halves of one question

Our rights is where you tick the registrations the letter will quote. Ticked titles are the ones that appear in it — which is what replaces a template guessing at which marks are being invoked. The filters propose the marks matching the brand, the territory and the Nice classes of the listing, because those three are what makes a registration relevant to this case rather than merely yours.

Their rights searches the registers for a mark held by the other side that would defeat yours. This step deliberately cannot conclude. It produces a dated search and a statement signed by whoever ran it — not a verdict — because “we found nothing” and “there is nothing” are different sentences and only the first one is true.

Step 5: the judgement, and what it is careful not to say

Steps 2 and 4 each answer half a question, and the Assessment puts the two halves side by side: the marks you hold against the marks they hold, the goods against the goods, the territory against the territory. What overlaps is drawn; what does not is drawn too, because the gaps are the argument the other side will make.

Beside it sit four axes you set yourself — how confident you are, how serious it is, how urgent, and how solid the evidence — and a recommended action that follows from them. An AI analysis button fills the four in as a proposal; a proposal is marked as one until a person confirms it, and the name recorded against the assessment is always the person’s, never the model’s.

Steps 6 and 7: an address is not a recipient

Contacts lists every address known for the operator, each one carrying where it came from — a public register, a legal notice page, a marketplace profile, a reply you received. Provenance matters more here than quantity: one address off the company register is worth five scraped from a storefront.

Recipient is the choice of who the letter is addressed to, and it is bounded by a rule that does not bend: only a verified contact — one a human has confirmed — can be named in a formal notice. Naming the wrong individual in a cease and desist is a defamation risk, so the step will show you an unverified address and refuse to put a person’s name on it.

Step 8: one choice decides the letter

The action you are taking decides the template, and the template decides the wording. That choice is carried over from your assessment at step 5 — changing it here is allowed, and when you do, the panel says plainly which action step 5 had recommended, so an override is a decision rather than a slip.

The panel also states, before anything is generated, who the letter comes from and on what basis: the marks being claimed, the recipient it is addressed to, and the signature. That last one is not a preference. A firm writes on behalf of its client because that is what a firm is; a rights holder writes in its own name because the right is its own. The platform derives it from your organisation’s profile, and an explicit setting on the organisation record overrides the derivation — a choice somebody recorded always beats one the software worked out.

How the letter travels — email, registered post, the marketplace’s own complaint form — and the language it is written in are chosen here too. The shape of the letter follows the channel: an email does not open on a postal address.

Steps 9 and 10: leaving, and coming back

Approval is given on the message exactly as it will leave — recipient, channel, sender and date included — and not on a draft that still might change. Send then shows the departure and everything that follows it: delivery, the reply if one comes, the reminder at day fifteen, and the outcome.

The trail, and the time it took

Every settled step is written down as it happens: who settled what, on which day. That list is the case’s own account of how it was built, and it is the reason a file assembled over three weeks can be explained to somebody who was not there.

It is also what the time sheets are built from. Settling a step is work — somebody read a register, compared two names, decided — and each one logs an entry at the usual duration for that kind of step. Those entries are marked automatic: they are estimates of a step’s ordinary shape, not measurements of you, and our team corrects them where the real work was longer or shorter. Re-settling a step never logs it twice.

Actions

Available types

Statuses and outcome

The outcome describes what actually happened, independently of the status: content removed, account suspended, domain suspended, no response, escalated. That is the field feeding the success rate on your dashboard.

The due date is computed at creation from the average response time observed on the platform being addressed.

Actions

Actions & requests

An action and its letters are one thing read apart: the action is what is being asked for, the letter is how it was put. The Actions & requests page puts them back together — one card per demand, with its letters underneath — so the question “what is outstanding on the whole account, and who is it waiting on” has a page instead of a tour through every case.

The three stages

The stage is not the status column. A status is one of fourteen values spread over two collections; the stage answers who is holding the request, which is the only question a list of them is read with. A date always beats a status where the two disagree: an action carrying a submission date has been submitted, whatever its status was last set to by hand.

Three ways of reading the same list

The same requests, laid out for three different mornings. Cards answer “what is this demand” — the whole story of one, letters included. Kanban answers “where is the work”, one column per stage, and an empty column is a fact worth the space it takes. Table answers “which one of these three hundred”. The choice is remembered in your browser. Nothing on the board can be dragged: moving a card between those columns would mean claiming a letter went out, and there is exactly one place in this portal where a step like that is taken — the record itself, behind the confirmation its workflow declares.

One demand, several cases

A seller with forty listings is forty cases, and it is not forty demands. An action can cover several cases at once: one of them is the lead case — the one the letter is addressed about, and the one the credits are charged to — and the others are listed beside it on the card, each one a link. All of them are searchable from this page, so a grouped demand is findable from any of the cases it covers, and each of those cases shows the action on its own sheet rather than looking as though nothing had been done about it.

Running the next step from here

Each card carries a Workflow button, and so does each letter under it: the steps of a demand (generate a letter, close it) are not the steps of the letter (approve, produce the PDF, send, post). Choosing one opens the record it belongs to with that step ready to confirm — the wording, the form and the permission check are the record’s own, because there is exactly one place in the portal where anything is actually sent.

A letter whose action you cannot see is still listed, on a card of its own, marked as such. A letter nobody can account for is precisely the one worth seeing.

Seller contacts

An action needs a recipient. The Seller contacts page is every address and every name we have found behind the operators you are acting against — collected from public registers, legal notice pages, contact pages and marketplace profiles, and from the replies you receive.

What we look for, and what we found

Four things make a recipient usable: a name, an email, a postal address and a phone. The Data found filter narrows the list to the contacts that carry the ones you need — press two of them and you get the contacts reachable both ways, which is the list a registered letter with an email copy is built from.

A contact with no name is not a mistake. A functional address (legal@, abuse@) never had one, and a row collected from a legal notice page often carries only a number. Those are marked Further research is required: the address works, the person behind it is still unknown.

Verification is a human act

A contact stays To be verified until a person — not an algorithm — has confirmed it, and only a verified contact can be used in a formal letter. That rule is not administrative caution: a name attributed to the wrong individual in a cease and desist is a defamation risk, which is why the decision never happens through a form on your side.

Personal data, and how long we keep it

These records are personal data. The legal basis is legitimate interest — the defence of intellectual property rights — and the purpose is exactly one: identifying the recipient of a notice. Harvesting personal social media is not done at all.

Each contact carries a retention date, by default twenty-four months after it was last useful. When it passes, the contact is marked Purge proposed and enters a review queue; nothing is deleted automatically, because an erasure nobody looked at is as much of a mistake as one nobody made.

From a contact you can open the operator it belongs to, and View all operator contacts puts every address recorded at that company side by side — which is how you decide who a letter should go to when there are three.

The preferred contact

Once that decision is made it is recorded: a contact sheet carries a Preferred contact switch, and the one marked leads the list wherever the platform offers a recipient. There is one per operator — marking a second releases the first, because the question has one answer.

It says which address the next letter goes to, and nothing else. In particular it does not make a contact usable: an unverified contact stays unusable in a letter whether or not it is preferred.

Letters

Choices at generation

Choosing the recipient

A letter sheet lists the contacts recorded at the operator behind the case, under Send this letter to, with the preferred one first. Choosing one writes the name, the email and the organization onto the letter; the postal address is taken from the operator only where the letter still has none, so an address corrected by hand is never overwritten.

Two rules show themselves there rather than being enforced silently: a contact that has not been verified cannot be chosen at all, and once the letter is approved the list is there to be read and nothing more.

The approval circuit

Actions

Letter templates

Every letter is produced from a template. The Letter templates page lists the ones available on your account: read the exact wording before it is ever used, filter by letter type, language, sender or tone, and generate a letter from any of them against an open enforcement action.

The parts written in braces are the merge fields. They are filled in from the case when the letter is produced — the mark, the operator, the case reference, the deadline — which is why a template reads as a form rather than as a finished letter.

Writing your own

You are not limited to our library. Use New template to write your own wording: a name, a letter type, a language, a tone, the signatory, a subject and the body. It is shared with every member of your organization and with nobody else, and from that point it sits alongside ours in the list, with the same generation button.

• Your own templates go through the same approval circuit, the same PDF and the same delivery methods as ours. Writing one changes the wording, not the safeguards.
• Editing a template affects letters generated from then on. Letters already produced keep the wording they were written with.
• Archiving takes a template out of the list and out of the generator without touching a single letter already sent.

Generating from a template

The generation window asks for one thing the platform cannot guess: the enforcement action the letter belongs to. Search it by case reference, case title, brand or action type — the list narrows as you type, and the case its operator, contacts and evidence come from is the one you pick. Everything else (letter type, language, signatory, delivery) is proposed from the template and stays editable.

Exchanges

Every dispatch attempt creates an outbound row, every reply an inbound row attached to the original message. The thread reassembles itself even if the recipient replies from another address.

Delivery statuses

Actions

Evidence

Screenshots, page archives, WHOIS records, test purchases, product photos, invoices, emails, letters, reports. Every item carries its capture date, its source and a digital fingerprint attesting that it has not been modified since.

Statuses

Page monitoring

A monitor sits on the URL of an open case and re-checks it every week or every month. It answers a single question: has the content been removed?

Result of each check

A removal is only confirmed after two consistent checks, or on the first one if the server explicitly answers that the page no longer exists. That caution avoids closing a case on a temporary outage.

Monitor statuses

Test purchases

The module tracks the order, the delivery, the assessment and the verdict, with the associated items: photos, invoice, report. It is the strongest evidence against an operator who disputes the claim, and often the decisive item in proceedings.

The price of the product is advanced and re-invoiced separately.

Registered trademarks

Your portfolio as the platform holds it: denomination, jurisdiction, registration and application numbers, filing, registration and expiry dates, Nice classes, the owner name on the register and the image for a figurative mark.

Whose mark is it

A title is filed under your organization when its owner name matches one of the names declared on your organization record. Anything the register has not been reconciled with yet stays Not yet classified rather than being quietly counted as somebody else’s — if a mark of yours is sitting there, the fix is to add the owner name to your organization, not to edit the title.

Search the registers

The Search trademarks page answers one question: does anyone hold a right on this name here? The left-hand column is your own portfolio filtered by what you typed; the right-hand column is what the official registers answer for the same name, which our rows cannot speak for.

Pick a jurisdiction and the page tells you which office keeps the register there and links straight into it. Arriving from a jurisdiction sheet, that country is already selected.

Why this comes before a letter

Two facts decide whether a case is worth opening: that you hold a right covering these goods, and that the other side does not. A mark registered by the operator in the country it sells from turns a takedown into a dispute — and that is a thing to know before writing, not after.

Jurisdictions

A reference sheet per country and per regional body: official name, codes, region, languages, currencies, whether UDRP applies, the trademark office that keeps the register, the regional office where there is one, and the text of the local trademark law with a link to its official source.

Three views of the same 255 rows — cards for one place at a time, a table to compare and sort, and a map, which is the one that answers “where are we actually working”. Every figure drawn on it is yours: your cases, your marks, your operators, your domains.

What a jurisdiction sheet holds

• Six counters across the top: cases, operators based here, operators selling into here, trademarks, domains, and whether UDRP applies.
• Four buttons on the office block: Search the register and Regional register go to the offices, Local legislation to the official text of the law, and Search known trademarks comes back into the platform with this country already chosen.
• The ten most recent trademarks registered here, the operators, and the domains — each with a way to see the rest.

Dashboard

Four counters aligned on the journey: alerts detected, cases opened, actions taken, letters produced. Between each counter, the conversion rate — that is where the friction points show.

Each section breaks down the split by status, a second axis (channel, priority, action type, delivery method) and the monthly trend. Clicking a bar, a pie slice or a counter opens the matching list.

Filters available: period, brand owner, brand, and a free keyword on titles, URLs, sellers and subjects.

Reports

You define a schedule (frequency, brands covered, recipients) and the platform produces and archives the document. Past editions stay available, which lets you compare one period with another.

Support

Categories: question, ask an IP attorney, bug, feature request, billing, account, other. Priorities: low, medium, high, urgent.

Statuses

Every ticket is a thread you can reply to. Give the address of the page concerned — it speeds up diagnosis considerably. The Related page URL field on the form is there for exactly that.

Asking an IP attorney

One category is not support and is not free. Ask an IP attorney puts a question to a qualified industrial-property attorney rather than to our team: is this case strong enough to push, is the wording of this letter safe to send, does the answer that just came back mean what it appears to mean. It is opened like any other ticket, and the fastest way in is from the record it is about — every case, letter and exchange carries the entry in its Actions menu, which brings the permalink and a subject with it.

Credits and the ledger

Billable acts are paid in credits. Your plan grants a monthly allowance; anything beyond it is drawn from top-ups. The Credit ledger is the record of every movement: date, action, quantity, unit cost, the case or record it belongs to, and the resulting balance.

Watching costs nothing. Scans, domain watches and the automatic searches that enrich what they find are covered by your monitoring subscription, not by your credits — a month in which you decide nothing costs you nothing. Credits pay for what you choose to do about a finding: investigating it by hand, gathering evidence, writing and sending demands, escalating.

The ledger is append-only. An entry is never edited and never deleted — a correction is a new entry that reverses the first one. That is the whole reason it can be audited, and the reason a charge you dispute stays visible next to its reversal.

Reading a charge

What actions cost

The What actions cost page is the price list in full: every billable act, what it does, and what it costs in credits — automatically and when an analyst carries it out. Some entries are free, some are included in a parent act and are never billed twice, and a few are quoted rather than priced.

Read it the other way round when you are planning: it is also the clearest list of what the platform can actually do for you.

Time sheets

The ledger says what was billed. The Time sheets page says what was done: a reply to one of your tickets, a register searched, a contact hunted down, a letter written and posted — with the duration of each, grouped by the day it happened on and totalled per day.

Where the entries come from

• Logged automatically as the work happens. A reply to one of your tickets is logged at ten minutes, an outbound letter at the standard time for its channel, and a manual act at the duration the catalogue gives it.
• Logged from the steps of a demand. Settling a step on the request page — searching the registers, identifying the operator, recording an assessment — writes an entry at the usual duration for that kind of step. Going back and re-settling one never logs it a second time.
• Corrected by our team afterwards. A default is a starting point, not a claim: a search that took an hour is put right by the analyst who ran it.
• Marked To be confirmed when nobody has yet said the work was theirs. Those lines are visible on purpose — you can see what has been checked and what has not.

A cancelled entry is struck through rather than removed: it is part of the record of what happened, including the part that was corrected. An entry marked not charged is work done and not billed — onboarding, rework, goodwill.

Not every hour is the same hour

Most of what you will see here is an IP Defender analyst, and those lines carry no badge because that is the ordinary case. A line marked External IP attorney is not us: it is a qualified industrial-property attorney reading your case, which is a different piece of work at a different price — see asking an IP attorney. The badge is there so that counsel’s half-hour can be told apart from an analyst’s: counsel’s time is invoiced to you by the firm and never reaches your credit ledger, while ours does.

Notifications

Two channels for the same events: in the portal, in the Notifications inbox, and by email. The inbox always receives everything your role can see; email is opt-in, category by category.

Each notification carries a link straight to the record it is about — the case, the letter, the ticket — so it opens where the decision is taken rather than on a list you then have to search.

Choosing what reaches your inbox

The categories are set on My account: new cases, new letters, letters awaiting your approval, replies received, comments on your records, tickets in your organization, and the daily and monthly digests. Turning a category off silences the email, never the in-portal entry.

My account

Your name, your email, the interface language (English or French, switchable at any moment from the flag in the header) and your notification categories. The theme — light or dark — follows your system and can be pinned either way.

The password and the sign-in method are handled by the platform’s own account screens, not from this page.

My organization

The My organization page holds what everything else hangs off: the legal entity, the client reference, the active subscription and its plan, the monthly credit allowance, the brands under watch, and the owner names your registered trademarks are reconciled against.

It also lists the members: who has access, with what role, and whether an invitation is still pending. Everything any of them sees is scoped to this organization — there is no view in the platform that crosses from one client’s data to another’s.

Comments and team notes

Every record in the platform — a case, an alert, a letter, a domain, a jurisdiction — carries a comment thread at the bottom of its sheet. It is the place for the sentence that explains a decision, and it stays with the record instead of in somebody’s mailbox.

• Replying quotes the message you are answering, so a thread read six months later still says what it was about.
• Mentioning a colleague notifies that person and nobody else. Without a mention, a comment notifies the whole organization — which is right for a decision and heavy for a note to one person.

The Team comments page gathers every thread in one place, newest first, so a week’s discussion can be caught up on without opening twenty records.

AI assistant

The AI assistant reads what you can read and nothing else — your cases, your alerts, your marks, your jurisdictions — and answers questions about them in ordinary language: what is open, what is overdue, what an action would cost, what the options are in a given country.

Most record sheets offer it four ready-made questions about that record, plus a free one. A conversation is personal: it belongs to you, not to your organization, and colleagues cannot read it.

Exchanges are billable at one credit each — the same entry as any other act, visible in the ledger.

A counterfeit spotted on a marketplace

A suspect domain has just been registered

The recipient replies