Your data, clearly explained.

VidiRow is operated by SÆTHER TRADING, organization number 831 726 202, Bakåsveien 6, 3265 Larvik, Norway. We are the controller for personal data handled to operate VidiRow. For privacy questions or requests, email support@vidirow.com.

• Website access permission. The extension requests access to all websites (<all_urls>) and runs content scripts on matching pages, which is how it can be ready to work wherever you are. That broad technical permission exists independently of your actions: capture only happens when you start it and select the content to process. VidiRow does not need your browsing history to perform a capture.
• Webpage content you capture. When you start a capture, the extension processes the page area or screenshot you select, which may contain personal or sensitive information.
• Your Google account and Sheets. Google sign-in provides your account identity, including your email address. The extension currently requests the Google Sheets spreadsheets OAuth scope, which technically permits access to all spreadsheets in the connected Google account; this is not a file-limited permission. In normal use it works with the spreadsheet destination you choose: it reads sheet structure and relevant existing cells, can add headings, writes the data you approve, and can perform limited undo. VidiRow does not request Gmail access.
• Images you upload or paste. Images you upload or paste into the extension can be sent through VidiRow's Cloudflare backend to the OpenAI API for image analysis, including when you create a Playbook.
• Playbooks and settings. We process the fields you choose in a Playbook, your selected destination, Smart Capture settings, and actions needed to provide the service.
• Support messages. If you email us, we receive what you choose to send and use it to respond.

VidiRow uses selected webpage content to extract structured details. The active Playbook defines the fields; Smart Capture can help choose a Playbook if you enable it. The extension shows results for review and then uses the Google Sheets API to write the rows you approve. We use account and usage metadata to authenticate users, operate the service, prevent abuse, and understand whether a requested action succeeded.

We do not sell personal data, and we do not use or transfer captured content or Google data for advertising of any kind. We do not use Google user data to train generalized AI models.

In plain English, there are four places data can be: in the extension — your settings, Sheet destinations, Playbooks and recent activity stay on your own computer in Chrome; in the VidiRow backend — Cloudflare Workers and a Cloudflare database, which handle sign-in, access status, your custom Playbooks and capture status; at the OpenAI API — the selected content that has to be read to extract fields; and in your Google Sheet — the rows you approve.

What may be sent to OpenAI, through our backend: the screenshot or text you selected, images you upload or paste, the fields defined by your Playbook, and your spreadsheet column headings, which may be sent so columns can be mapped automatically. Existing row values in your spreadsheet are used inside the extension for the operations that need them and are not sent to OpenAI for that mapping.

Our API requests set response storage to off, but that is not the same as Zero Data Retention and is not a promise of zero retention by OpenAI; OpenAI may retain API content in abuse-monitoring logs under its published data controls: https://platform.openai.com/docs/guides/your-data

Approved rows are sent to Google Sheets. We use these providers to deliver the features you request, not to sell your information. Provider processing may occur outside Norway or the European Economic Area, subject to their applicable safeguards.

Our backend stores account identifiers including a hashed sign-in email, session-token hashes, access and entitlement status, your custom Playbooks, capture-status records, and AI action and usage metadata. It is not designed to keep your captured screenshots or extracted row content as permanent VidiRow records.

The extension stores settings, connected Sheet destinations, Playbooks, and up to 20 recent activity entries locally in Chrome. Recent activity can include spreadsheet identifiers, row locations, and written or previous values used for review and undo. Data written to a Google Sheet remains in that Sheet under your Google account until you change or delete it there.

The cleanup that exists today is limited and specific: sessions expire after 30 days, and expired session records are removed during later sign-ins; in-progress capture records older than 10 minutes are removed during later capture operations. That is not a comprehensive scheduled purge of account data, completed-capture metadata, or custom Playbooks, and we do not publish a retention period for those categories.

You choose when to capture, which Playbook to use, whether Smart Capture is on, what to save, and which Sheet receives it. You can revoke VidiRow's Google access in your Google Account: https://myaccount.google.com/connections

Revoking access stops future API access, but does not erase rows already saved in your Sheet or all data stored by VidiRow.

You can ask us to access, correct, or delete your VidiRow account data by emailing support@vidirow.com. We may need to verify your identity and retain limited information where law or security requires it. Requests are handled manually; we assess, act on, and answer every request without undue delay and normally within one month, subject to applicable legal exceptions and permitted extensions. The data deletion page explains the steps. If you are in Norway or the EEA, you may also have the right to complain to your data protection authority.

This website is separate from the extension. The demo on the home page uses fictional sample data, does not connect to a Google account, and does not save anything to Google Sheets.

The website and its hosting providers may process ordinary technical information needed to deliver and secure the site, such as IP address, request time, requested page, and browser or device information. The website also loads Google Fonts, which may cause your browser to make requests to Google.

VidiRow's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: https://developers.google.com/terms/api-services-user-data-policy

VidiRow's use of data received through Google APIs also adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.

Data obtained through Chrome extension permissions is used to provide or improve VidiRow's user-facing capture features, and transferred only when needed to deliver those features or for security or legal reasons. We do not sell this data, and we do not use or transfer it for advertising of any kind. We do not allow people to read captured user content except with the user's specific consent for support, or when necessary for security or legal compliance. Nothing here means Google has reviewed or approved VidiRow.

We will update this policy when VidiRow's data-handling practices materially change. Material changes will be disclosed before they take effect and, where required, presented for renewed consent.