1. Overview

RevenueFlow Assistant is a Chrome extension provided by Netbase JSC. It helps users locate payment-related messages in Gmail, review extracted payment records, detect possible duplicates, and write user-approved records to Google Sheets.

This Privacy Policy explains what Google user data and extension data RevenueFlow Assistant accesses, how that data is used, and what choices users have.

2. Google user data we access

RevenueFlow Assistant may access the following data only after the user grants permission through Google OAuth:

• Gmail account information: Gmail account address and mailbox profile information, used to show which Gmail account is connected.
• Payment-related Gmail messages: email metadata and message content needed to identify and parse payment notifications, such as PayPal, Stripe, or other configured payment sources.
• Payment record details: customer name, customer email, payment amount, payment provider, order/reference number, transaction ID, profile/subscription ID, and related payment fields extracted from payment emails.
• Google Sheets data: spreadsheet identifiers, tab names, cell ranges, and row values required to create, test, and write reviewed payment records to a Google Sheet selected or created by the user.

3. How we use Google user data

Google user data is used only to provide the extension’s payment reconciliation workflow:

• Find payment-related messages in the authorized Gmail mailbox.
• Extract payment fields for user review.
• Detect possible duplicate transactions.
• Show payment records inside the extension for user confirmation.
• Create, test, or write approved rows to a Google Sheet controlled by the user.

RevenueFlow Assistant does not use Google user data for advertising, analytics profiling, creditworthiness decisions, lending purposes, or unrelated product features.

4. Gmail permissions and limitations

RevenueFlow Assistant uses Gmail read-only access. The extension cannot send, delete, move, label, or mark Gmail messages as read through the Gmail API.

The extension does not request or store Gmail passwords. Google authentication and authorization are handled by Chrome and Google OAuth.

5. Google Sheets access

Google Sheets access is used to support the spreadsheet workflow selected by the user. This may include creating a private RevenueFlow spreadsheet in the connected Google account, checking spreadsheet access, confirming a tab/range, and writing user-approved payment rows.

RevenueFlow Assistant writes to Google Sheets only after a user action or a user-enabled workflow setting. The user remains responsible for reviewing payment records before saving them.

6. Storage and retention

• Email message content is processed in the extension to extract payment fields and is not stored as a complete email archive.
• Extension settings, connected Gmail display information, product rules, and up to 50 recent parsed payment-history records may be stored in chrome.storage.local in the user’s Chrome profile.
• Google OAuth access tokens are handled by Chrome Identity and are not written to RevenueFlow Assistant’s local storage.
• Local extension history remains until the user clears it, removes the extension, or clears Chrome profile extension data.
• Rows already written to Google Sheets remain in the user’s Google account and can be edited or deleted by the user in Google Sheets.

7. Sharing and transfer

RevenueFlow Assistant does not sell Google user data, payment records, Gmail content, or customer data.

RevenueFlow Assistant does not use Google user data for advertising and does not transfer Google user data to data brokers.

In this release, Gmail message content and parsed payment records are processed locally in the Chrome extension and are not transmitted to Netbase JSC servers. If cloud sync or server-side processing is introduced in the future, this policy will be updated and users will be asked to re-consent where required.

8. Security

• Gmail access uses a read-only OAuth scope.
• Google API traffic uses HTTPS.
• Remote executable code is not used; extension scripts are packaged with the extension.
• Sheet writes may be blocked when required fields are missing or an unreviewed possible duplicate is detected.
• Users can revoke Google access at any time from their Google Account security settings.

9. Limited Use statement

RevenueFlow Assistant’s use and transfer of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. RevenueFlow Assistant’s use and transfer of information received from Google APIs will also adhere to the Google API Services User Data Policy, including the Limited Use requirements.

10. Your choices and deletion

• Disconnect Gmail from RevenueFlow Assistant.
• Revoke RevenueFlow Assistant’s access in Google Account security settings.
• Clear local payment history inside the extension where available.
• Uninstall the extension to remove extension-local data from that Chrome profile.
• Edit or delete any rows already written to Google Sheets directly in Google Sheets.

11. Children

RevenueFlow Assistant is a business productivity tool and is not directed to children.

12. Changes to this policy

Material changes to data access, data use, cloud processing, or third-party sharing will be reflected in this policy. When required, users will be asked to provide renewed consent.

13. Contact

Privacy questions, support requests, and deletion requests can be sent to:

Netbase JSC
Email: [email protected]
Website: https://netbasejsc.com/