The Formula.Firewall error, or the "information is required about data privacy" dialog, appears when one query combines data from two sources and Power Query is not sure they may be mixed. It is a safety check, not corruption. The safe fix is to set a privacy level for each source, and, if the error persists, to restructure the queries so one step does not read a source and another query at once.
What is Power Query actually worried about?
Privacy levels exist so that private data is not accidentally sent to a place that should not see it. When a query reads a source and also reads another query, Power Query may need to pass values from one to the other. If one source is private and the other is public, that could leak. Power Query cannot tell what your sources are, so it asks you to label them. The message looks like: "Query 'X' references other queries or steps, so it may not directly access a data source. Please rebuild this data combination."
What are the three levels?
| Level | Meaning | Typical example |
|---|---|---|
| Private | Sensitive; never share with other sources | Your statements folder, your budget workbook |
| Organizational | Can be shared within a company, not outside | A shared company file |
| Public | Anyone may see it | A public web page |
Two sources set to Private can still be combined in the same workbook; Power Query just makes sure data is not sent out through a query to another source. For personal statements and a local budget table, Private for both is the natural choice.
How do I set the levels?
- When the dialog appears, choose the level for each source it lists, then Save. Excel remembers it for that source.
- To check or change later, go to Data, Get Data, Data Source Settings.
- Pick the source, choose Edit Permissions, and set the Privacy Level.
- Refresh the query again.
Do this for both sides of the merge. If one is unset, the error can come back. Settings made for a path apply to that path only, so a moved folder asks again.
What if the error stays after setting the levels?
The usual reason is a single query that both reads a source and refers to another query in the same step. Fix it by splitting:
- Make one query only for the statement folder and name it Statements, doing nothing but reading and cleaning.
- Make another only for your local table, named Rules.
- Merge them in a third query that references the two, so no step is reading raw data and another query together.
- Set the staging queries to connection only, and load just the final result.
What does ignoring privacy levels change?
Under File, Options, Query Options, Privacy, you can choose to ignore privacy levels for the current workbook. The error stops, and queries may run faster, because Power Query no longer isolates sources from each other. The cost is that nothing then stops values from one source being sent into a query on another. With two local files on your own computer, that matters little. If one source is a web page, a database or a cloud service, think twice, and prefer setting levels. It is your call, so choose it knowingly.
What else triggers the message?
- A merge between a local source and a web source, which is where the rules matter most.
- A parameter or lookup that feeds a value from one query into another source's query.
- A workbook sent to someone else: their Excel has no saved permissions and asks again.
The workbook route is flexible but brings these prompts and permissions with it. If you would rather keep statements in one private place, SpendixAI keeps your records in your own workspace with role-based access, and its security page describes how it handles your data.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


