# Use Cases - Octet

Source: https://octetproof.com/use-cases/

> Location as a factor in sign-ins and approvals, compliance with sanctions and state licenses, and a strong, provable location signal for risk decisions.

For the whole site in one file, read https://octetproof.com/llms.txt

# Use cases

- Prove each action comes from a real phone in a location your rules allow
- Run a model in permitted regions only, or attach location evidence to software commits
- Apply Utah's adult content rule only in Utah
- Approve an agent's action or a consequential production change from your office
- Draw your own policy
- Proof that a real device, held by a human, is in a place; the software that acts on that proof makes the physical world programmable.

1

Cybersecurity

## Location as a factor.

A password, a one-time code and a session token work the same wherever they are used, so whoever holds them can use them from anywhere. Octet adds where the phone is as a factor in sign-ins, approvals and other actions that matter, with no extra step for the user. Octet returns a signed answer, and your system decides what to allow.

``

1.1

### Location as a sign-in factor

Octet runs on the customer's enrolled phone alongside your existing login. When the phone is at the login, your app skips the push, the SMS code and the "was this you?" prompt. When stolen credentials are used from another country, the phone is still with its owner, the proof fails, and the real customer never sees a challenge.

Predicate isWithin(login_region)
The problem Step-up checks at sign-in punish real users with prompts and false declines.

1.2

### Payment approvals

A large wire moves on a few sign-offs, and a sign-off is often an email. Octet binds each approval to a signed proof that it came from an enrolled device of an authorized signer, standing in one of your offices.

Predicate device ∈ finance_signers - contains(office_site, 100 m)
The problem An approval sent from a stolen email account looks the same as a real one.

1.3

### Agent actions approved by a human, in an authorized place

Agents now act on real systems with real keys. In June 2026 an OpenAI agent running an internal evaluation [got around the access blocks](https://www.abc.net.au/news/2026-09-24/ai-agent-accessed-australian-government-site-pm-says/107189078) on an old Services Australia website and reached non-public Medicare statistics. OpenAI said its models took actions it did not intend.

Octet puts a person at the point of decision. Before an agent deletes, pays, deploys or opens something sensitive, it asks for approval, and the approval counts only with a signed proof from a real phone, held by a human, inside an authorized place. A token copied by an agent cannot produce that proof.

Predicate device ∈ approvers - contains(authorized_site, 100 m)
The problem Agents act with keys and tokens, and a token says nothing about whether a person approved the action or where they were.

1.4

### The remote engineer who isn't where they claim

You hire a remote engineer. They pass the interviews, say they're in Austin, and you grant repository and wallet access. From that moment on, "Austin" is a claim nobody ever checks again.

Octet makes it a measurement: taken on the device, signed in hardware the user can't reach, at onboarding and on every sensitive action. An engineer who is actually in Moscow, Tehran or Pyongyang cannot produce one.

A determined adversary can still ship a laptop to a US address and pay someone to host it. That is the part the FBI prosecutes, and it is a considerably harder business than a VPN subscription.

Predicate isOutside([KP, IR, RU, BY, CU, SY])
The problem Hire one operative posing as a remote dev and a sanctioned actor holds your code and keys, and every paycheck is a strict-liability OFAC violation.

1.5

### Data that opens only in one place

Some data should only be read from one place: model weights, evaluation sets, health records, export-controlled files. The rule is usually enforced with credentials and an office IP range, and both work from anywhere once they are stolen.

The US [Data Security Program](https://www.justice.gov/nsd/data-security) restricts *access* to bulk sensitive data from countries of concern, not only transfers.

With Octet, the data store releases a key only with a fresh signed proof that the requesting device is inside the approved site. Credentials used from a server somewhere else cannot produce one.

Predicate contains(secure_site, 100 m)
The problem Data rules are written about where data is read, and enforced with credentials that work from anywhere.

1.6

### Capabilities that unlock only at a secure facility

Labs already ship models that do more for the right people in the right setting. Anthropic's [Claude Gov](https://www.anthropic.com/news/claude-gov-models-for-u-s-national-security-customers) models refuse less when handling classified material, and access is limited to people who work in classified environments. OpenAI's reasoning models run on Los Alamos' [Venado supercomputer](https://www.energy.gov/node/4852451) on a classified network. In April 2026 OpenAI released [GPT-5.4-Cyber](https://openai.com/index/scaling-trusted-access-for-cyber-defense/), which lowers the refusal boundary for verified defenders.

Today the gate is the account, or the network the model runs on. With Octet, a model unlocks a capability, such as binary reverse engineering or work on controlled defense material, only with a signed proof that the device belongs to cleared staff and is inside an accredited facility. Anywhere else, it behaves like the public model.

Predicate device ∈ cleared_staff - contains(accredited_facility, 100 m)
The problem A capability gated by account goes wherever the account goes, so a stolen login carries the most dangerous version of the model out of the building.

2

Compliance

## Location is law.

[Major IP geolocation databases](https://ip.octetproof.com/) disagree on the same address by an average of 620 kilometers. The largest sanctions fine in banking history was $8.9 billion (BNP Paribas, 2014). A recent one was $4.3 billion (Binance, 2023), and the CEO did prison time. Octet replaces the IP lookup with a yes or no about the device's location, signed in its hardware, even when the VPN is on.

``

2.1

### Sanctioned jurisdiction blocking

[71M](https://ip.octetproof.com/) people in sanctioned jurisdictions live within 100 km of a non-sanctioned border, and IP lookups miss by several times that distance. Instead of looking the location up, the phone builds it up from its own sensors, checks it against the sanctioned regions in your policy, and signs the answer in its hardware.

Predicate isOutside(sanctions_set)
The problem Strict liability: intent is no defense, and firms have lost their license to operate.

2.2

### National exclusion: blocking the United States

SEC Regulation S requires a **reasonable belief** that the buyer is outside the US. IP geolocation does not meet that standard. Self-attestation does not either. KYC proves identity at signup, at real conversion cost, never that the buyer was outside the US at the moment of the trade.

Octet issues a hardware-signed proof before the session opens, covering Puerto Rico, Guam, American Samoa, the US Virgin Islands, and the Northern Mariana Islands.

Predicate isOutside(united_states)
The problem A single non-compliant US sale is an unregistered securities sale on its own: strict liability, rescission, SEC exposure.

2.3

### State-by-state activation

A single platform can serve only the jurisdictions where it holds authorization, or where federal preemption has been judicially confirmed. The geofence updates without a client release as state injunctions issue or lift. The same primitive supports county-level and municipal carve-outs, and tribal land where gaming compacts apply.

Predicate isWithin(licensed_states)
The problem Run in a state that hasn't licensed you and it reads as unlicensed gambling: cease-and-desist orders, fines, removal from the state.

2.4

### Tribal lands and gaming compacts

Gaming on Native American land runs under tribal compacts, and those compacts end at the reservation boundary. A wager placed on tribal land falls under the compact. One placed a mile outside falls under the state, which may not allow it at all. IP geolocation cannot tell the two apart.

Octet supports polygons at any scale, from a single casino floor to a reservation's full boundary, with the same cryptographic guarantee as a national geofence. Each wager carries a signed answer for which side of the line the phone was on.

Predicate isWithin(tribal_land)
The problem A wager on the wrong side of a reservation line breaks either the compact or the state's gaming law, and the operator carries the liability.

2.5

### Frontier model access by country

Labs decide where their models can be used. Anthropic does not serve China, and since [September 2025](https://www.anthropic.com/news/updating-restrictions-of-sales-to-unsupported-regions) it also refuses companies controlled from there, wherever they operate. The check is still mostly an IP address.

In February 2026 Anthropic [reported](https://www.anthropic.com/news/detecting-and-preventing-distillation-attacks) that DeepSeek, Moonshot and MiniMax ran more than 16 million exchanges with Claude through about 24,000 fraudulent accounts, reaching it from China through commercial proxy services.

Octet ties each account, and each API key it issues, to a signed proof from a real device outside the restricted regions, at sign-up and again at intervals. A proxy changes the IP address but not where the phone is.

Predicate isOutside([CN, RU, IR, KP])
The problem Region rules are enforced on the IP address, so a proxy network turns one refused customer into thousands of new accounts.

3

Fraud and risk

## A signed location for fraud and risk decisions.

Fraud and risk systems already weigh location, mostly from an IP address that a VPN or a proxy changes in seconds. Octet gives them a signed answer about where the phone is. Your rules decide what a NO means: a review, a step-up check or a hold on the payment.

``

3.1

### Card payments at checkout

A card issued in France is used for an online purchase. The IP address says the Netherlands, because the buyer runs a VPN. Your risk engine has to tell a real customer from a stolen card.

Octet adds a signed answer about whether the buyer's phone is in France. Your rules decide what follows: a YES can let the payment through without a challenge, and a NO can send it to review.

Predicate isWithin(card_country)
The problem False declines cost about nine times as much as the fraud itself, and a VPN makes a real customer look like a stolen card.

3.2

### New accounts where the applicant says they live

An application says the applicant lives in Germany. The documents pass, and the IP address says Germany as well, through a proxy.

Octet adds a signed answer about whether the applicant's phone is in Germany when the account opens, and again at the first withdrawal.

Predicate isWithin(declared_country)
The problem An identity check confirms the document and leaves the applicant's location to an IP lookup.

3.3

### Device farms and multi-accounting

Sign-up bonuses, referral rewards and airdrops are paid per account, so one operator runs hundreds of accounts from racks of phones in one room. Each phone is a real device and passes a device check.

With Octet, your rules can check whether a new account's phone is inside a small area where other accounts were opened, and send the third, the tenth or the hundredth to review. Real users see no CAPTCHA.

Predicate not_colocated_with(existing_accounts)
The problem Every phone in a farm is a real device, so each account passes the checks built to stop bots.

3.4

### Invoice fraud

Invoices that carry a signed proof the sender's device is at the supplier's registered address get fast-tracked. An attacker in Vietnam compromises your supplier's email and sends a fake invoice. Their device cannot produce a proof for the supplier's address. Flagged before payment.

Predicate contains(supplier_address, 5 km)
The problem A fake invoice from a compromised supplier account looks the same as a real one.

4

Localization

## Localization from a signed location.

Products change by place: the catalog, the price, the payment methods at checkout, a feature that opens only at one venue. Most of these choices run on an IP lookup, which puts a user on a VPN in the wrong country. Octet gives the product a signed answer about where the phone is, and the user can keep the VPN on.

``

4.1

### Regional catalogs and prices

Streaming catalogs, app prices and subscription tiers are set country by country. A VPN moves a user into another country's catalog or a cheaper price, and an IP lookup can move a traveller into the wrong one.

Octet gives the app a signed answer about the country the phone is in, so the catalog and the price follow the phone.

Predicate isWithin(country)
The problem Prices and catalogs set per country reach anyone who changes their IP address.

4.2

### The right payment methods at checkout

Buyers in Brazil pay with Pix, in India with UPI and in the Netherlands with iDEAL. The checkout chooses which methods to show from the buyer's country, usually from the IP address, so a buyer on a VPN or a corporate network sees another country's options.

With Octet, the checkout shows the payment methods for the country the phone is in.

Predicate isWithin(BR)
The problem A buyer who doesn't see the method they use can't pay with it.

4.3

### Features that open only at a venue

A ticketed event unlocks content only for people inside the stadium. A reward applies only in one store. An IP address resolves to a city at best, and anyone can claim to be at the venue.

Octet gives the app a signed answer that the phone is inside the venue or the store when the feature is used.

Predicate isWithin(venue)
The problem A check-in or a QR code works from anywhere once it has been shared.

If you have a use case you don't see here, tell us where location determines an action in your product. We'll tell you if Octet can be valuable.

[Contact us ->](mailto:hello@octetproof.com?subject=A%20use%20case%20for%20Octet) hello@octetproof.com