Most data companies can tell you what is in a dataset. Fewer can tell you where it came from. They cannot explain it in a way that would satisfy a real compliance check, not just a marketing claim. That gap is common across the data industry, and most companies never close it unless something forces them to.
The Industry Standard Most Companies Default To
A common practice is to buy bulk data from middlemen. These middlemen often do not know much about how the original data was collected. They vouch for the data. Sometimes they vouch for its legality in a general way. But the buyer still does not get a clear answer to a basic question: who agreed to have their information collected, and for what reason.
That gap can turn into a real problem later. Data collected without clear consent can carry legal risk. That risk passes on to whoever uses the data next, no matter what it cost or how exclusive it seemed at the time. The risk is not just about reputation, though a damaged reputation is often what finally makes a company look closely at its own sourcing.
Where Atlantic Tech Draws a Different Line
Atlantic Tech is a data intelligence company based in Cheyenne, Wyoming. Its approach to ethical data acquisition starts with a stricter idea of consent than most of the industry uses. If data was gathered without a clear, traceable basis for collection, it does not enter the pipeline. That is true no matter how useful the data might be. The rule applies the same way across the logistics and commodity trading clients the company mainly serves.
The company treats this as a filter that comes first, not last. A source that fails the provenance test does not proceed to a quality review, even if the dataset appears complete and well-organized. Founder and CEO Peter Kazan has said that checking usefulness before checking where data came from is exactly how weaker sourcing habits creep into a pipeline. Nobody decides to lower the bar. It just happens gradually, one shortcut at a time.
What Counts as Consent in a Data Pipeline
Kazan has described the internal rule in simple terms. Before any data source gets approved, the company has to answer one clear question: can we explain exactly how this information came to exist, and who agreed to let it be used? If a source cannot pass that test, it does not make it into the system. That is true no matter how complete or valuable the dataset looks on its own.
That bar is higher than what most data buyers ask for. A vague question, like whether a source seems generally trustworthy, is much easier for a middleman to answer than a specific one about where one particular dataset came from. The company treats that extra difficulty as the whole point, not as a hassle to work around.
Insight Collection Without Overreach
The same rule shapes how the company handles insight collection, the process of turning intent signals into information that can be used for targeting. There is a clear line here too. On one side is collecting signals that a person or company has effectively made available for that purpose. On the other side is the practice of collecting information by exploiting gaps in disclosure or consent. The company has said it will not cross that line, even in cases where doing so would be technically easy and hard to catch.
That line matters more in insight collection than in most other parts of a data pipeline. Intent signals are closer to a person’s real, active behavior than a static dataset usually is. The same signals that make insight collection useful for targeting are also the signals most likely to raise consent questions, if the company is not careful about where it draws its own boundaries.
Why Ethics and Precision Are Not in Tension
The company treats ethical sourcing and data precision as partners, not competitors. A smaller, more accountable set of sources tends to produce cleaner signal than a large, loosely sourced one. Sources with clear origins are also easier to check and easier to fix when something changes.
That claim challenges a common assumption: that stricter sourcing rules always lead to a smaller, less useful dataset. The company disagrees with that tradeoff as usually described. A large pile of data nobody can verify is worth less in practice than a smaller pile the company can actually stand behind when a client asks where a specific data point came from.
How Clients in Logistics and Commodity Trading See the Difference
For clients in regulated or reputation-sensitive industries, the source of data is not a minor detail. A commodity trading firm that relies on improperly acquired data can face real exposure, well beyond the original business deal. That risk has pushed sourcing questions higher up the checklist that clients use when evaluating a data vendor.
Clients in these industries have started asking data vendors directly about sourcing practices. Part of that shift comes from a string of publicized data scandals in other industries. Being able to answer that question with specifics, rather than a general assurance, has become part of how the company stands out in client conversations that now often start with sourcing rather than end with it.
What the Company Will Not Do
The list of excluded practices is specific. The company will not scrape data in violation of a platform’s terms. It will not buy data through middlemen who refuse to disclose how the data was originally collected. And it will not acquire information from sources with no way to verify consent. Each of these disqualifies a source, no matter the price or how exclusive the deal looks.
That lack of exceptions is itself part of the standard. A rule that bends for a good enough deal is not really a rule. The company has pointed to specific cases where it walked away from data it could have legally acquired, simply because the consent trail did not meet its own bar, not because a regulator forced its hand.
Setting a Standard the Rest of the Industry Has Not
It remains an open question whether this standard will spread across the wider data intelligence industry. For now, the company treats its acquisition rule as a strength rather than a limitation. Clients, it argues, increasingly want to know not just what a data provider can deliver, but how that data was obtained in the first place.
The company expects this standard to become common eventually, as regulators pay closer attention to data sourcing across every industry. Until that happens, the gap between its own practice and the industry norm is treated as a real advantage worth keeping, not a cost worth cutting.
