Privacy Policy

Glaxosoft LLC operates BrowserChef, including the browser extension, browserchef.com, and the backend services used for accounts, workflow sync, AI features, and billing. This policy explains how those services handle your information.

What BrowserChef does locally

Workflow steps run in your browser. Depending on the actions you configure, they can read page content, interact with forms, access website cookies, copy text, download files, send HTTP requests, and display results. BrowserChef does not collect your general browsing history for advertising or resale.

Execution history, step results, and cached workflows are stored in your browser. Workflow actions can send data to the websites or endpoints you configure. Review a workflow before enabling it, especially one imported from another person.

Accounts and workflow sync

We use Google Firebase Authentication for accounts, including an anonymous identifier when you start without registering. If you register, Firebase processes your email address, display name, and authentication information.

Firebase Authentication and our Firebase backend also process IP addresses and technical request information, such as user-agent strings, to provide the service and prevent abuse. See Firebase's data processing information for provider details.

Saved workflow definitions, names, descriptions, triggers, action inputs, folders, and user-variable names and values are stored in Cloud Firestore and cached locally. Variable values are stored separately from shared workflow definitions and are restricted to the workflow owner. They are not an end-to-end encrypted password vault.

Workflows marked public can be viewed on the website. Link-shared workflows can be accessed by people with the link. Private variable values are excluded from workflow sharing and exports, but anything typed directly into a workflow action remains part of its definition. Keep credentials out of shared action inputs.

AI features and OpenAI

AI features send requests through our Firebase backend to OpenAI only when you use an AI feature or run a workflow containing an AI action.

• AI Action: sends your instruction, page title, page URL, and a limited description of visible interactive controls, including labels, names, available options, and relevant link or form destinations. URL query strings and fragments are removed. Current input values and the full page DOM are not automatically sent.
• Use AI: sends your prompt after workflow variables have been substituted. This includes any page content, prior-step output, or private variable values you explicitly include in that prompt.
• Workflow AI helper: sends your request and the current workflow configuration to create or edit a workflow. Private user-variable values are excluded; values written directly into action inputs are included.

OpenAI also receives a hashed account identifier for abuse prevention. We set API response storage to false. OpenAI may retain request data under its API data policies, including for abuse monitoring. See OpenAI's Privacy Policy. Do not include sensitive information that you are not authorized to send to OpenAI.

Payments and AI credits

Stripe processes subscription and credit-pack payments. Payment details are entered on Stripe's checkout pages; BrowserChef does not receive your full card number or security code. We store customer and transaction identifiers, subscription status, credit balances, usage counts, and refund or dispute records in Firebase to provide paid access and reconcile payments.

Information we may collect on this website

• Basic contact information you choose to send us by email.
• Anonymous or pseudonymous website usage data, such as page views and CTA clicks, to understand how people use the site.
• Technical information your browser sends when visiting the site, such as IP address, browser type, approximate device information, and referral data.

How we use information

• To authenticate accounts, save and sync workflows, and provide the actions you configure.
• To answer AI requests, maintain credit balances, and process billing.
• To respond to support requests and understand website usage.
• To prevent abuse, diagnose failures, maintain reliability, and meet legal obligations.

Analytics

We may use Firebase Analytics or similar privacy-conscious analytics tooling on the website to measure page usage and important website events such as install, pricing, and workflow interactions. This helps us improve the site and understand demand.

These analytics are for the website experience. They are not used to inspect the contents of the workflows you run locally in the extension.

Cookies and local storage

The site may use cookies or similar browser storage for analytics, essential site behavior, and performance. See our Cookies Policy for more detail.

Third-party services

Google Firebase and Google Cloud provide authentication, database storage, hosting, analytics, and backend infrastructure. OpenAI processes AI requests. Stripe processes payments. These services receive the information needed for those functions and may process it in other countries, including the United States. Support messages are handled by our email provider.

We do not sell personal information or use workflow content or browsing activity for advertising. We share information only to provide the features described here, at your direction, or when reasonably necessary to comply with law or protect the service. Our use of data obtained through Chrome APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Data retention

Saved workflows and private variables remain until you delete them or your account. Account deletion starts removal of associated workflows, variables, and AI-credit records. Billing, support, security logs, and provider backups may remain as needed for accounting, fraud prevention, legal obligations, or the provider's retention schedule. AI-credit reservations are short-lived; completed AI responses may remain in your local execution history.

Deleting cloud data does not erase exported files, copies installed by other users, or data already sent to third-party websites by your workflows. You can clear local execution history in the extension or remove extension storage through your browser.

Security and your choices

We use HTTPS for backend connections and access controls to separate users' private records. No service can guarantee absolute security. You can edit or delete workflows and variables, change sharing visibility, avoid AI features, delete your account in Settings, or uninstall the extension.

Your rights

Depending on your location, you may have rights to access, correct, delete, or object to certain processing of your personal data. To make a request, contact us at usama@browserchef.com.

Contact us

If you have questions about this Privacy Policy, contact us at usama@browserchef.com.