Louisiana and Oklahoma privacy laws start January 1. Check if either reaches your store, then fix the request inbox
Louisiana's law can reach a company on revenue alone, with barely any Louisiana customers. Oklahoma's looks at how many people's data you handle. Three made-up businesses show how different the answers can be, and what the covered ones have to be ready to answer.

Louisiana's Data Privacy Act and Oklahoma's Consumer Data Privacy Act both take effect January 1, 2027. Louisiana applies if you do business there and have over $25 million in revenue, handle data on 75,000 or more consumers, households or devices, or earn half your revenue from selling data. Oklahoma looks at 100,000 consumers, or 25,000 plus half of revenue from data sales. If either applies, you need a privacy notice, a working request process and vendor contracts. Check exemptions with counsel.
Two new laws, two different questions
On January 1, 2027, two more states' comprehensive privacy laws start applying: the Louisiana Data Privacy Act and the Oklahoma Consumer Data Privacy Act. A law firm's year-end alert notes more are coming, with Alabama on May 1, 2027 and Vermont on January 1, 2028. Not legal advice here, just a way to find out whether you should be asking a lawyer.
The two laws ask different questions about you. Oklahoma asks how many Oklahomans' data you handle. Louisiana asks that too, but it also asks how much money you make, and the money question can be enough by itself.
Three made-up businesses
These are composites, built to show how the thresholds work.
A candle shop. Two people, a Shopify store, about $200,000 a year, customers all over the country. Louisiana's revenue test isn't close. The data-volume test counts "consumers, households or devices" handled in a year, a wording that can include devices, so the number to look up isn't only the customer list. If the shop is far below 75,000, Louisiana probably doesn't reach it. Oklahoma wants 100,000 Oklahoma consumers; a small shop won't have them.
An apparel brand. A $40 million company shipping to every state with only a small share in Louisiana. The revenue test alone puts it in Louisiana's scope, even if it handles little data from that state. Oklahoma probably doesn't apply unless its Oklahoma customer data is large. This is the case that surprises people, since most state privacy laws look at data volume and not revenue.
A regional nonprofit clinic. Both laws list exemptions. Louisiana's include nonprofits, HIPAA covered entities and their business associates, state agencies and local governments, and financial institutions covered by federal rules. A nonprofit clinic has a good chance of being outside Louisiana's law, though it may have obligations under other rules.
Exemptions can apply to the organization or only to certain data, and a law firm's alert stresses reading them carefully before concluding a law applies or doesn't. Coverage may also depend on where your customers live, not where you're based.
To run the numbers for your own business, you need three figures, and you can get rough versions in an afternoon. Annual gross revenue comes from your accountant. Louisiana and Oklahoma customer counts come from your order export, filtered by shipping or billing state. The harder one is Louisiana's "consumers, households or devices": your analytics and ad tools may count visitors and devices from Louisiana that never bought anything. Write the three figures down with the date and where each came from, and take them to whoever advises you on privacy. A rough number with a source is far more useful to a lawyer than a guess.
Decision guide
How each law decides whether it applies
| Consideration | Louisiana (any one is enough) | Oklahoma |
|---|---|---|
| Revenue | More than $25 million a year, even with little Louisiana data | Revenue alone doesn't trigger it |
| Data volume | 75,000 or more consumers, households or devices a year | 100,000 or more Oklahoma consumers a year |
| Data sales | 50% or more of revenue from selling personal data | 25,000 consumers plus more than 50% of revenue from data sales |
| Fix period | 30-day cure period until July 31, 2027, then it ends | 30-day cure period stays in the law |
Louisiana gives you forty-five days. The work is making sure the request reaches someone on day one.
If you're covered, what's expected
For a covered business, both laws require a privacy notice, written contracts with vendors that process data for you, consent before processing sensitive data, and documented assessments for higher-risk processing such as targeted advertising, selling data and handling sensitive data. In Louisiana those assessments apply to processing as of January 1, 2027 and aren't retroactive. Louisiana's notice has to be reasonably accessible and clear, and cover six things: the categories of data you process, why, how people exercise their rights and appeal, what you sell, who buys it, and how to submit a request.
Enforcement belongs to each state's Attorney General, and neither law gives people a private right to sue. Louisiana gives a cure period: from January 1 to July 31, 2027 the Attorney General must give 30 days' written notice before investigating, and can't proceed if you fix the problem. After July 31 that ends. Oklahoma keeps its 30-day cure period permanently and sets penalties of up to $7,500 per violation.
The request inbox
Most of the policy work is a one-time job. The part that keeps going is the inbox: people can ask you to confirm what you hold, correct it or delete it. Under Louisiana's act, per the OpenAgreements guide, you respond within 45 days (once extendable by 45 more with notice), you explain any refusal with instructions for appeal, and an appeal gets a written answer within 60 days. Louisiana gives you forty-five days. The work is making sure the request reaches someone on day one.
Where does a request actually land today? Often in a general support inbox, mixed in with order questions, or on a form nobody checks. A usable process has five parts. A single place requests go, with a form that asks for what you need. A way to confirm the person is who they say, without asking for more data than you already hold. A search across every system that holds personal data: the store, the email tool, the helpdesk, ad audiences and the spreadsheets people made for a campaign. An answer inside the deadline. And a log of what was asked, found and done.
The search step is where it falls apart. Personal data lives in more places than anyone remembers, and nobody has a list. Drawing that list is useful even if neither law applies to you.
A practical way to start is to take one real customer, ideally a colleague who has bought from you, and look for them everywhere. Their order history is in the store. Their address may be in the shipping tool. Their emails are in the helpdesk and the marketing list. Their name may sit in a returns spreadsheet, an ad platform's uploaded audience, or a review app. Each place you find them goes on the list, with who can search it and who can delete from it. Places where nobody knows how to delete a person are the gaps to fix first, because those are the ones that will blow a 45-day deadline.
Where we help
A policy page isn't the project. The project is the process behind it: a request form that goes somewhere, identity checks, a way to find and remove a person across your tools, and a log. That's the connecting and tracking work our business automation practice does. A lawyer should decide what applies to you; if it does, talk to us about building the process.
Related work: Sutton|Place
How the work moves
A request, from arrival to answer
- Arrives
A form, an email or a support ticket. It must reach one place on day one.
- Verified
Confirm the person is who they say before releasing or deleting anything.
- Searched
Check the store, email tool, helpdesk, ad audiences and spreadsheets.
- Answered
Respond within 45 days, or explain a refusal and how to appeal.
- Logged
Keep what was asked, found, done and when.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.