Can't Access CSV File Stored in Cloud Storage by Looker Studio - 403 Forbidden

I uploaded a CSV file directly to Looker Studio and it’s working fine in my report. However, I cannot download or access the original file that Looker Studio automatically stored in Google Cloud Storage. I’m getting 403 errors on everything.

Setup

  • Data source: CSV uploaded directly to Looker Studio (47.2 MB file)

  • Report access: I have full edit access to the report

  • GCP account: (PII Removed by Staff) with 3 active projects

The Problem

Looker Studio created this bucket automatically:

gs://looker-studio-data-import-e028e878-3dc1-4908-9bc1-4908-9bc1-38df0a596b05

When I check the bucket details with gsutil ls -L -b, I see:

  • ACL: [] (empty!)

  • Default ACL: [] (empty!)

This means the bucket was created without any permissions for anyone, including me.

What I’ve Tried

:cross_mark: Download from Cloud Storage console → 403 Forbidden
:cross_mark: gsutil cp command → 403: storage.objects.get denied
:cross_mark: gsutil iam ch to add permissions → 403: storage.buckets.getIamPolicy denied
:cross_mark: Export CSV option in Looker Studio → doesn’t exist for uploaded CSVs

Questions

  1. Is this a known bug? Why would Looker Studio create a bucket with empty ACLs?

  2. How can I access my own data? The file is mine, but I’m completely locked out

  3. Is there a workaround to export the complete dataset from Looker Studio?

  4. Who actually owns this bucket? It doesn’t appear in any of my GCP projects

Workarounds I Found

The only way I can get data out is by manually exporting each visualization/chart as CSV, but this is impractical for large datasets and doesn’t give me the raw data.

Related Info

  • Report ID: 37f4fa68-6096-430e-8f8e-2e7500fa555f

  • Bucket created: January 3, 2026

  • Location: US (multi-region)

  • File name visible: CARUARU_FINAL_COM_ANO

Has anyone else experienced this? Any suggestions would be greatly appreciated!


Update: Still unresolved. Looking for any workarounds or official Google response on this issue.