Burbly Extension Privacy Policy

Last updated: 2026-03-30

The Burbly browser extension helps users create and review flashcards.

Data We Process

• Account identity from Firebase Authentication (Google sign-in): user id, email, display name, photo URL.
• Flashcard data created by the user: question/answer, deck and pack organization, review scheduling metadata.
• Optional source metadata when user creates cards from a page/video: page URL/title, YouTube timestamps, optional tags.
• Optional highlighted text only when user explicitly triggers related capture/generation actions.

How Data Is Used

• To create, organize, and review flashcards.
• To schedule next reviews based on user study ratings.
• To show study stats and calendar views.
• To generate flashcard suggestions via the configured AI proxy endpoint.

Where Data Is Stored

• Primary storage: Firebase Firestore under the authenticated user account.
• Local extension storage: temporary UI/session state and cached draft/context data.

Data Sharing

• Firebase services (Auth + Firestore) for account and data sync.
• AI proxy endpoint only for AI-generation requests initiated by the user.
• We do not sell user data.

Permissions Rationale

• storage: local extension state.
• activeTab: user-initiated actions on the current tab.
• tabs: identify active tab context (e.g., YouTube watch tab).
• scripting: inject capture helpers when user initiates specific actions.
• identity: Google OAuth sign-in flow.
• Host permissions are limited to Firebase/Google auth APIs, configured proxy API, and YouTube for side panel features.

User Controls

• Users can sign out at any time.
• Users can delete extension data by clearing browser extension storage and deleting data from their Burbly account backend.

Contact

For privacy questions, contact the Burbly team through the official support channel.