Permissions & Data Use

Why the extension asks for these permissions

This page is designed to help both users and Chrome Web Store reviewers understand the extension's permissions, host access, and data flow.

Single purpose

The single purpose of Supabase to Google Sheets Export is to let users export data from a Supabase project into Google Sheets, including optional scheduled syncs for Pro users.

Extension permissions

storage

Used to save local connection settings, Google auth state, schedules, and license metadata in the extension so the product keeps working between sessions.

alarms

Used only for recurring scheduled syncs in the Pro workflow. Without it, the extension could not run hourly, daily, or weekly exports on schedule.

identity

Used for Chrome's Google OAuth flow so the extension can write to Google Sheets and read spreadsheet metadata with the user's permission.

sidePanel

Used to present the extension's main interface in Chrome's side panel so users can manage connections, exports, and licensing without leaving the page context.

Host permissions

https://*.supabase.co/*

Required to read schema and row data from the user's chosen Supabase project.

https://sheets.googleapis.com/* and https://www.googleapis.com/*

Required to create spreadsheets, update sheets, and read limited file metadata used by the export workflow.

Remote services used by the product

  • Supabase for the source data selected by the user.
  • Google for spreadsheet creation and updates.
  • Stripe for checkout and payment processing.
  • Netlify Functions and Neon for license validation, payment record storage, and usage metrics.

What is not done

  • No broad browsing history access.
  • No injection on arbitrary websites.
  • No sale of user data.
  • No remote code execution from the licensing backend.