GridBee is a Google Sheets productivity platform operated as a sole proprietorship. We offer a Chrome extension and a suite of digital products — including templates, cheatsheets, and automated Google Apps Script systems — targeted at individuals and teams who use Google Workspace.

This Privacy Policy applies to all products and services offered under the GridBee brand, including our website, Chrome extension, and any downloadable digital products sold through our platform.

GridBee is operated by Briltek Cloud. You can reach us at gridbee@briltek.cloud.

We collect only information necessary to provide and improve our services. This includes:

• Account & contact information: Your name and email address when you register or contact us.

• Purchase information: When you buy a product, your transaction is processed. GridBee receives a purchase confirmation but does not store your full payment details.

• Usage data: Per-module usage counters (number of operations performed today and in total) stored alongside your account in Firestore so we can show your progress in the side panel. Website page-view analytics are anonymous and not linked to your account.

• Device & browser information (website only): When you visit gridbee.app, our website host (Wix) automatically collects browser type, operating system, IP address, and referring URL. The GridBee Chrome extension does not collect or transmit any of this information.

• Support communications: Any information you provide when contacting our support team.

• Google Sheets data : The GridBee Chrome extension may access spreadsheet data solely to perform the features you activate (e.g. remote data entry, sheet styling). This data is never stored on GridBee servers or transmitted externally.

• What we never store on our servers: GridBee does not store the
  contents of your spreadsheets, documents, presentations, calendar
  events, Apps Script source code, or any other Google Workspace
  content on its servers. All such content is read directly from
  Google's APIs into your browser, processed locally to perform the
  feature you activated, and discarded when the operation completes.
  The only information stored in our Firestore database is your
  account identity (name, email, profile photo, Firebase UID),
  subscription state, per-module usage counters, and feedback you
  choose to submit.
   

We use your information to:

• Deliver, operate, and improve GridBee products and services

• Process and fulfill your purchases 

• Send transactional communications (receipts, license keys, product updates)

• Respond to support requests and enquiries

• Detect and prevent fraud, abuse, or security incidents

• Comply with applicable legal and regulatory obligations

• Send occasional marketing emails about GridBee products (you may opt out at any time)
  
  We do not sell your personal data. Your information is never sold, rented, or shared with third parties for their independent marketing purposes.

The GridBee Chrome extension is designed with privacy by default:

• The extension activates only on the Google Workspace pages where you've explicitly opened the GridBee side panel — currently Google Sheets (docs.google.com/spreadsheets) and Google Apps Script (script.google.com).

• Spreadsheet data accessed by the extension is processed locally in your browser and is not transmitted to GridBee servers.

• We store minimal state data (e.g. active tab ID, extension preferences) in chrome.storage.local, which remains on your device.

• The extension does not track your browsing activity outside of Google Sheets.

• No personal data is collected from spreadsheets you open.

Our Chrome extension complies with the Chrome Web Store Developer Program Policies, including the principle of minimal and necessary data use.

When you complete a GridBee Mastery assessment, you can download a badge HTML file that includes a verification URL (gridbee.app/mastery/verify?id=…). To make this verification work, we publish a small record to a public Firestore collection containing only the data shown on the badge itself: your display name, profile photo (the same one you use across Google services), badge level, score, number of questions, and the timestamp of completion.

Each badge gets a unique, unguessable ID. The badge data is publicly readable by anyone who knows the verification URL — this is what makes the badge verifiable to third parties (e.g., employers checking a candidate's claim). No other fields from your account are exposed.

If you do not want your badge to be publicly verifiable, do not download or share the badge file — no public record is created until you complete an assessment.

GridBee requests the following OAuth scopes from your Google account.
We use each only for the user-facing feature it powers, and never for
any other purpose.

• openid
  Required to sign you into GridBee via Firebase Authentication.

• https://www.googleapis.com/auth/userinfo.profile
  Reads your display name and profile photo to show them in the side
  panel header.

• https://www.googleapis.com/auth/userinfo.email
  Reads your email address to identify your GridBee account and pre-fill
  it at checkout.

• https://www.googleapis.com/auth/spreadsheets
  Reads and writes the spreadsheets you have open. Used by Stylist
  (cell formatting), Health (formula diagnostics), and Automation
  (writing generated rows back to source sheets). Cell values and
  formulas are processed in your browser and never stored by GridBee.

• https://www.googleapis.com/auth/documents
  Creates and writes Google Docs from the rows in your spreadsheet,
  using a Doc template you select. Used by the Docs Generator
  automation. Document text is never stored by GridBee.

• https://www.googleapis.com/auth/presentations
  Creates and writes Google Slides from the rows in your spreadsheet,
  using a Slides template you select. Used by the Slides Generator
  automation. Slide content is never stored by GridBee.

• https://www.googleapis.com/auth/calendar.events
  Creates calendar events from the rows in your spreadsheet. Used by
  the Calendar Events automation. We only create events GridBee itself
  owns — we never read other events from your calendar. Event details
  are never stored by GridBee.

• https://www.googleapis.com/auth/drive.file
  Per-file access to the specific files you select via Google's Drive
  Picker. Used by Automation to write generated Docs/Slides into the
  folder you choose. GridBee never has access to any other files in
  your Drive.

• https://www.googleapis.com/auth/script.projects.readonly
  Read-only access to a single Apps Script project — the one you're
  currently viewing when you open Vaps. Used solely to export the
  project's source for the user to download. Source code is never
  stored by GridBee.

You can review and revoke any of these grants at any time at
myaccount.google.com/permissions.
 

All purchases made through GridBee are processed by Lemon Squeezy, our Merchant of Record. When you complete a purchase:

• You are redirected to a checkout page hosted by Lemon Squeezy (lemonsqueezy.com / store.gridbee.app).

• Lemon Squeezy collects and stores your payment details (card number, billing address, tax identifiers where applicable) directly. GridBee never sees or stores your card information.

• Lemon Squeezy handles tax calculation, VAT/GST compliance, fraud prevention, chargebacks, and payouts.

• When a payment succeeds, Lemon Squeezy sends GridBee a webhook with your customer email, subscription ID, and renewal date so we can grant Pro access on your account.

We do not sell your data. We may share your information only in limited circumstances:​

• Service providers: Third-party tools we use to operate our business (e.g. email delivery, analytics), who are contractually bound to protect your data.

• Legal compliance: When required by law, court order, or governmental authority.

• Business transfers: In the event of a merger, acquisition, or sale of assets, your data may be transferred as part of that transaction.

GridBee's use and transfer to any other app of information received
from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In particular:

• We use Google user data only to provide and improve user-facing features that are prominent in the GridBee user interface.

• We do not transfer Google user data to third parties except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets — and only with appropriate notice.

• We do not use Google user data for serving advertisements.

• We do not allow humans to read Google user data unless we have your explicit consent, it is necessary for security purposes (for example, to investigate abuse), it is required to comply with law, or the data has been aggregated and anonymized so it is no longer identifiable.

GridBee relies on the following processors to operate. Each is subject to its own privacy policy. 
 

Google
We use Google Identity for sign-in and Google Workspace APIs (Sheets, Docs, Slides, Drive, Calendar, Apps Script) to perform the actions you request. See Google's Privacy Policy.
 

Firebase

We use Firebase Authentication and Cloud Firestore (operated by Google LLC) to store your GridBee account record, subscription state, settings, and the per-module counters described above. See Firebase Privacy and Security Information.

Lemon Squeezy
Lemon Squeezy is our Merchant of Record and processes all GridBee subscription payments. When you upgrade, you are redirected to a checkout page hosted by Lemon Squeezy. Lemon Squeezy collects your name, email, and payment-method information directly — GridBee never sees your card details. When a payment succeeds or your subscription renews, Lemon Squeezy sends GridBee a webhook event with your customer email, subscription ID, status, and renewal date so we can grant Pro access on your account. See Lemon Squeezy's Privacy Policy.

Google Cloud Run
Our payment webhook handler runs on Google Cloud Run. The service receives subscription event payloads from Lemon Squeezy, verifies their authenticity via an HMAC-SHA256 signature, and updates your subscription record in Firestore.

Firebase Hosting
We host a small Google Drive Picker integration page at gridbee-picker.web.app through Firebase Hosting. When you use the Automation module's file picker, this page is opened briefly in a popup window so you can select files from your Drive. The page is then closed.

Your account data is stored in Google Cloud regions managed by Firebase. Access to your users/{your-id} document is restricted by Firestore Security Rules so that only requests authenticated as you can read or modify it. Sensitive fields such as your subscription state and account creation date are write-protected against client modification and can only be changed by our server-side webhook handler.

Your local data — including your cached account record and any in-progress preferences  is stored in your browser through chrome.storage.local. This data is sandboxed to the GridBee extension; other extensions and websites cannot read it.

All communication between GridBee, our backend, and Google's APIs uses HTTPS.

GridBee itself does not set cookies. The extension uses chrome.storage.local to cache your account data so the side panel renders quickly. When you sign out, this cache is cleared.
 

Our website uses cookies to enhance your experience. These include:

• Essential cookies: Required for core site functionality (e.g. session management).

• Analytics cookies: Anonymous usage data to help us understand how visitors use the site.

• Preference cookies: Store your settings and preferences.

The Drive Picker page at gridbee-picker.web.app runs as a Google-hosted application and may use cookies as required by Google's Picker API. We do not place additional tracking cookies on that page.

We retain your account record for as long as you maintain an active GridBee account.

When you sign out of GridBee, your local cached data is removed from your browser, but your Firestore account record persists so that your subscription state and settings can be restored if you sign back in.

To permanently delete your data — including your Firestore account record, feedback you have submitted, and any associated webhook audit entries — email us at gridbee@briltek.cloud from the email address on your GridBee account. We will process your request within 30 days.

Webhook event records used for payment auditing are retained for the period legally required for tax and accounting purposes (typically seven years).

Depending on where you live, you may have the following rights regarding your personal information:

• Access — request a copy of the personal information we hold about you

• Correction — request that we correct inaccurate information

• Deletion — request that we delete your account and associated data

• Portability — request a machine-readable export of your information

• Objection — object to certain uses of your information

• Withdrawal of consent — revoke the Google OAuth grant at any time

To exercise any of these rights, email gridbee@briltek.cloud from the address on your GridBee account. We respond within 30 days.

You can revoke GridBee's access to your Google account at any time by visiting myaccount.google.com/permissions. Revoking access signs you out of GridBee and prevents any further exchange of Google data.

GridBee is operated from Nigeria. The cloud services we depend on (Firebase, Google Cloud Run, Lemon Squeezy) operate from multiple regions around the world, including the United States and the European Union.

If you are located in the European Economic Area, the United Kingdom, or another region with cross-border data transfer rules, your information may be transferred to and processed in countries with different data protection standards than your own. Where required, we rely on the Standard Contractual Clauses or equivalent safeguards provided by our processors.

GridBee is intended for users aged 16 and over. We do not knowingly collect personal information from children under 16. If you believe a child has provided us with their information, contact us at gridbee@briltek.cloud and we will delete it.

We may update this Privacy Policy from time to time. When we make material changes, we will notify you by updating the "Last updated" date at the top of this page and, where appropriate, by sending a notice through the extension or by email to the address on your account.

Your continued use of GridBee after a change takes effect means you accept the updated policy.

Questions about this Privacy Policy or how your data is handled?

• Email: gridbee@briltek.cloud

• Operator: Briltek Cloud

Product home: gridbee.app