diff --git a/docs/security/database-permission/export.mdx b/docs/security/database-permission/export.mdx
index 84971e83..f0305ad8 100644
--- a/docs/security/database-permission/export.mdx
+++ b/docs/security/database-permission/export.mdx
@@ -9,7 +9,7 @@ There are two ways to export data:
 
 ## Export directly from SQL Editor
 
-As **SQL Editor User**, after you run a query, you can export the result by clicking **Export** button. The exported data still respects the masking policy to mask exported columns.
+As **SQL Editor User**, after you run a query, you can export the result by clicking the **Export** button. See [Export data](/sql-editor/run-queries#export-data) for how Export behaves.
 
 ![sql-editor](/content/docs/security/database-permission/export/sql-editor.webp)
 
diff --git a/docs/sql-editor/run-queries.mdx b/docs/sql-editor/run-queries.mdx
index c9740218..ad1cc028 100644
--- a/docs/sql-editor/run-queries.mdx
+++ b/docs/sql-editor/run-queries.mdx
@@ -58,7 +58,9 @@ The default query result size is **100 MB**. You can change it under the Workspa
 
 <Info>
 
-The exported data still respects the [masking policy](/sql-editor/mask-data/) to mask exported columns if enforced.
+**Export re-runs your SQL statement against the database** — it does not download the result set currently displayed in the tab. If the underlying data changed between the time you ran the query and the time you clicked **Export**, the exported rows will reflect the later state. To capture a specific point-in-time result set, copy the rows from the result panel or re-run the query immediately before exporting.
+
+The re-execution goes through the same row limit, data-source selection, and [masking policy](/sql-editor/mask-data) as the original query, so exported columns are masked if the policy is enforced.
 
 </Info>