1. Summary
Your workbook is read locally by the extension and uploaded directly to Google when you request conversion. The converted Sheet is made viewable to anyone who has its link, including people without a Google account. We do not operate an intermediary workbook-upload server or maintain a user account database.
2. Information the extension accesses
When you select a workbook, the extension may access:
- the selected file name, file type, size, sheet names, cell values, formulas, formatting, dimensions, and workbook structure;
- the Google Sheet created from that workbook, including its identifier, link, sheet properties, values, and formulas;
- the Google authorization token supplied and managed by Chrome for the permissions described below; and
- a temporary browser-window identifier used to focus the existing extension window.
The extension does not request access to passwords, payment information, contacts, email, browsing history, or unrelated files on your device.
3. Google user data and API permissions
The extension uses Google OAuth through Chrome Identity. Google displays the requested permissions before access is granted.
After a successful conversion, the extension creates an anyone / reader permission with discovery disabled. Anyone who obtains the result link can view the converted Sheet without signing in, but the extension does not request that Google list it in public search.
Google access is used only to provide the user-requested workbook conversion, validation, repair, and link-sharing features. We do not use Google user data for advertising, credit decisions, surveillance, or training general-purpose AI models.
Use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
4. Optional DeepSeek formula fallback
If the installed build has the DeepSeek repair fallback enabled, it is used only after Google import produces a formula error that cannot be handled by a deterministic rule.
For such a formula, the extension may send directly to DeepSeek: the target sheet and cell, the original formula, the imported formula, the calculated error, and the workbook's sheet names. It does not send the entire workbook as part of this fallback request.
This processing is subject to DeepSeek's Privacy Policy. Do not process a workbook containing confidential data if you do not accept this limited transfer. A build without a DeepSeek API key does not make DeepSeek requests.
5. Extension usage analytics
If analytics is enabled in the installed build, the extension sends product-usage and reliability events directly to Google Analytics 4. These events may include a randomly generated extension client identifier, a temporary session identifier, event time, extension version, file type, a coarse file-size range, conversion stage and outcome, duration, and aggregate counts such as sheets, formulas, and repairs.
Analytics events do not include workbook or sheet names, cell contents, formulas, Google Sheet identifiers or links, Google authorization tokens, or raw error messages. Events are marked for non-personalized advertising and are used to understand the conversion funnel and improve reliability. Google processes these events under its own privacy terms.
6. Storage and retention
- Developer servers: we do not receive or retain your workbook or Google access token on a developer-operated backend.
- Your browser: workbook data is held in memory while conversion is running and is released when the page or extension process ends. Chrome storage retains a random analytics client identifier, and session storage temporarily retains analytics session state and the extension window ID.
- Google Drive: the converted Google Sheet remains in your Google Drive until you delete it. It has view-only access for anyone with the link unless you change or remove that permission. Google controls its storage and retention.
- Google Analytics: usage events are retained according to the configured GA4 property settings and Google's retention practices.
- DeepSeek: any limited formula fallback data is handled under DeepSeek's own retention practices.
8. Security
The extension uses encrypted HTTPS connections to Google, Google Analytics, and DeepSeek. Google OAuth tokens are requested through Chrome Identity and are not written into the extension configuration. Link access is not equivalent to private access: anyone who obtains a result link can view that Sheet. The website uses no sign-in system and does not accept workbook uploads.
No method of electronic processing can guarantee absolute security. Keep your browser current, review the permissions shown by Google, and do not share extension builds that contain private third-party API keys.
9. Your choices and controls
- You can decline Google authorization and avoid using conversion features.
- You can remove the extension at any time through your browser's extension settings.
- You can revoke Google access from your Google Account's third-party connections page.
- You can open the converted Sheet's sharing settings and change General access from “Anyone with the link” to “Restricted.”
- You can delete converted files from Google Drive.
- You may use a build without the optional DeepSeek fallback.
10. This website
This static website provides product, privacy, and support information. It does not accept workbook uploads, run advertising scripts, set analytics cookies, or create user accounts. Standard technical request information, such as IP address and user agent, may be processed by Cloudflare to deliver and secure the site under Cloudflare's policies.
11. Changes and contact
We may update this policy when the extension's data practices or legal requirements change. The effective date at the top identifies the current version.
Questions, privacy requests, and deletion questions can be submitted through @extensions_support on Telegram or by using the instructions on the Support page.