Complex day at Faire

Decide how closed-account data is deleted without breaking operations

Published Oct 22, 2026

You’re the legal / compliance lead. Your team is in the room.

The setting

connects independent retailers with small brands and suppliers. Its lets brands list and sell products, and lets retailers find, order and pay for them.

The regulator needs one account of deletion while the underlying records tell several.

A fast, durable response protects regulatory credibility, while a broad commitment could disrupt records needed for marketplace operations.

Who you’d be doing this for

“I closed the shop months ago, so I didn’t expect my old order details to still show up.”

Nicolas Lopez · Retail Store Owner · a character in this brief

A retailer who closed a storefront and expects the marketplace to honor the deletion request for their business account data.

What is at stake

A regulator found a closed retailer account in an operational record after a deletion request. You must weigh a firm deletion commitment against the records marketplace operations still rely on.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • deletion commitments vs operational recordkeeping
  • regulator speed vs verified evidence
  • retailer expectations vs investigation readiness
  • cross-border consistency vs local workflow realities

Why Faire

Retailer and brand data moves through discovery, ordering, and operational workflows that support a global wholesale marketplace.

Written with these in mind

privacy product counseldata governance leadermarketplace regulatory counsel

Not your kind of problem? 59 more at Faire, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Faire. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

  • Senior Counsel, Regulatory & Product (opens in a new tab)
    • Translate emerging legal and regulatory obligations into practical product and operational requirements
    • Reporting to the Deputy General Counsel, you'll partner closely with our product and engineering teams, helping them craft practical solutions to navigate legal complexity.
  • Senior Counsel, Privacy & Product · no longer posted
    • Act as a senior legal advisor to the business on data governance issues, including privacy, data use, information security, retention and deletion, and cross-border data flows
  • Compliance Specialist · no longer posted
    • Coordinate timely and accurate responses to auditors and regulators on compliance matters
    • We are using technology and data to level the playing field: We are leveraging the power of product innovation and machine learning to connect brands and boutiques from all over the world, building a growing community of more than 350,000 small business owners.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these is about an irreversible change forced by a fixed date.

The same setting, from another role

Each is set around Faire’s Wholesale discovery marketplace, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to make strict, complex requirements operational so people doing careful work can move quickly and safely.