Privacy Policy
- Runs locally. Nothing leaves your browser unless you send it.
- Your tasks, the pages you automate and their content stay on your device. They are never sent to the developer or anyone else.
- The only data ever sent is an optional "Pro" interest message, and only when you click its button. It contains an anonymous random ID and, only if you type it in, your email address.
- No analytics, no tracking, no ads, no accounts, no remote code, and no selling of data.
Permissions and when they are used
activeTab: temporary access to the tab you are on, granted by Chrome only when you click the toolbar icon, choose a ClickRow item in the right-click menu, or press a ClickRow keyboard shortcut.scripting: to run ClickRow's own scripts (included in the extension package) on that tab.contextMenus: to add the "Quick fill with ClickRow" item to the right-click menu.storage: to keep your tasks and settings in your browser (section 2).- Optional website access (
http://*/*,https://*/*are only the upper limit Chrome lets the extension ask for): nothing is granted at install. ClickRow asks only when you turn on "Run automatically" for a task, and only for the websites in that task's address rules. It never asks for all websites.
When you install ClickRow, it opens its own welcome and practice page once (a page inside the extension, not a website).
1. What the extension does on your device
ClickRow repeats clicks, typing, selections and key presses that you set up or record on a web page. It works on the tab where you start it, after you click its toolbar icon, choose its item in the right-click menu (contextMenus permission) or press one of its keyboard shortcuts. Chrome then gives it temporary access to that one tab (the activeTab permission). The only exception is "Run automatically" (below), which works only on the websites you allowed for it. ClickRow has no access to your other tabs or to any other website.
Quick fill. When you choose "Quick fill with ClickRow" (This field / This form / Whole page) in the right-click menu, or press its keyboard shortcut, ClickRow scans the form fields on that tab the same way as "Scan this page's form" and types random test data into them right away. Password, card-number and one-time-code / verification-code fields are not filled. A small box in the corner shows how many fields were filled and lets you fill again, undo, or save the fields as a task. Nothing is saved unless you click "Save as task" (then the task is saved like any other task, with random-test-data placeholders such as {{fake:email}}, not the generated values). The values ClickRow writes and the field values it remembers for "Undo" stay in that tab's memory and are gone when the page is closed or reloaded.
Run automatically (optional, off by default). In a task's settings you can turn on "Run automatically when a matching page opens". Only then does ClickRow ask Chrome for access to the websites in that task's web address rules (for example https://shop.example.com/*); Chrome shows you the request and you can decline. The extension asks for no website access when it is installed, and it never asks for access to all websites. With that access, when a tab finishes loading a page whose address matches the task, ClickRow runs the task on it once and shows a box in the corner with "Undo this fill" and "Stop auto-running". It does not run again on the same tab and address within 30 seconds, never runs tasks that click delete-type buttons or that ask you for a value while running ({{ask}}), and by default leaves fields that already have a value as they are. To be able to undo, it remembers the values the fields had before, only in that tab's memory. When you turn the option off, ClickRow gives back the website access that no other auto-run task still needs; you can also remove it at any time in Chrome's extension settings. The addresses of the pages it runs on are checked in your browser and never sent anywhere; the last one per tab is kept for 30 seconds only (cr_autorun_seen below).
On that tab ClickRow runs scripts that are part of the extension package (scripting permission) to find the elements in your task, perform the steps, show a small control bar, let you pick an element, or record your own clicks and typing. While doing this it reads only what it needs from the page — for example an element's position, label, visibility and the value of a field after it was filled — to run the step and explain a failure. This happens in your browser. Page content, the text you type into tasks, and the addresses of the pages you automate are not sent anywhere.
"Scan this page's form". ClickRow reads the contents of the form on the tab only when you click "Scan form" / "Scan this page's form". It then reads the visible form fields' labels, types and options (and the page title, used as the default name of a new task), and shows them in the popup for you to review. You choose how values are filled in:
- Current page values: the values currently in the fields are copied into the rows you add, and saved with your task on your device (in plain text, like any text you type into a task). Password, card-number and one-time-code / verification-code fields (including every box of a code split into separate boxes) are not read; those rows get the placeholder
{{ask}}and ClickRow asks you for the value each time the task runs. - Random test data (the default): text fields get placeholders such as
{{fake:email}}that create new test data on every run, so the text currently in the page's fields is not saved. Only whether checkboxes and switches are ticked is kept (you can change that to random), and a week field, which has no random format, keeps its current value.
Scan results stay in the popup's memory until you add them, and anything you don't add is discarded. Scanning never sends anything outside your browser.
"This page has a form" suggestion. When you open ClickRow's popup on a tab (which gives it access to that tab), it counts how many fillable form fields are visible there, so it can suggest scanning the form. This count only checks which fields exist and whether they are visible and enabled: it does not read what is typed or selected in them, does not read their labels, and does not save or send anything. Only the number reaches the popup, and the suggestion appears only when there are at least three fields. Choose "Don't suggest here" to stop the suggestion on that website.
Help and feedback links. "Help", the "What is this?" links next to error codes, and "Send feedback" are ordinary links that open only when you click them. Help opens the help pages at newbieroutine.github.io/clickrow-privacy/help/ in a new tab, like any website you visit (GitHub, which hosts them, can see your IP address as for any page). "Send feedback" opens your own email app with a draft to the developer that contains the extension version, your browser name and version, and the interface language; nothing is sent unless you send that email yourself. ClickRow itself makes no request in either case.
Language. The interface is shown in English unless you choose another language with the language button; the language files are part of the extension package and are not downloaded.
2. Data stored on your device
ClickRow keeps the following items in your browser. They are never uploaded by ClickRow. Removing the extension deletes all of them (see section 2a). They live in two different places:
- Extension storage (
chrome.storage.localandchrome.storage.session): Chrome's storage area for this extension.localstays until you delete it or remove the extension;sessionis kept in memory and cleared when the browser closes. ClickRow does not usechrome.storage.sync, so nothing is synced to your Google account by ClickRow. - Extension page web storage (
localStorageof ClickRow's own popup page, originchrome-extension://<extension id>): a separate store used only for the two Pro-message items at the end of the table. Web pages you visit cannot read it.
Text you type into tasks (for example the text of a "Type" row) is stored as you entered it, in plain text. When ClickRow records you typing into a password, card-number or one-time-code / verification-code field, it saves the placeholder {{ask}} instead of the value and asks you for it each time the task runs; that value is never saved.
Answers to {{ask}}. Before a task with {{ask}} rows runs, ClickRow shows one small form for all of them. Answers for password, card-number and one-time-code / verification-code fields are never saved. Other answers are saved on your device as the pre-filled default for the next run of the same task (cr_ask_last below, up to 2,000 characters per answer), so you can just confirm them; you can change or clear them in the form each time. While a run continues on the next page of the same site, ClickRow keeps your answers only in the extension's memory (its background service worker), so it doesn't ask again on every page. This in-memory copy is never written to storage or to disk, and it is cleared when the run finishes, fails or is stopped, or when you close the tab. If Chrome unloads the extension's background in the meantime, it is gone and ClickRow simply asks again.
| Stored item | Where | Purpose |
|---|---|---|
cr_schema | chrome.storage.local | Version number of the saved data format |
cr_tasks | chrome.storage.local | Your tasks: names, the web address patterns you entered, loop settings, whether the task runs automatically and whether it overwrites fields that already have a value, and rows (element selectors and labels, text to type, options to choose, what change to expect after a click). Text to type is stored in plain text. |
cr_draft_<task> | chrome.storage.local | Steps you picked or recorded but have not saved yet |
cr_pending_pick | chrome.storage.local | The element you just picked on the page, until the editor takes it |
cr_pick_expect | chrome.storage.local | That the element you are picking is the one a click row should make appear (task and row only), until the editor takes it |
cr_trash | chrome.storage.local | Up to 20 recently deleted tasks, so you can undo a delete |
cr_backup_v<N> | chrome.storage.local | A copy of your tasks made before the data format is upgraded |
cr_last_result | chrome.storage.local | The result of the last run, including why a step failed |
cr_runlog_<task> | chrome.storage.local | Run history of a task: for each of its latest 20 runs, when it started and ended, how many rounds ran, whether it finished (and whether it ended because there was nothing more to process, or was started by "Run automatically"), failed or was stopped, the row number and step ID where it failed with the failure reason code (such as NOT_FOUND), and how long each row took on average. It never contains text you typed, answers to {{ask}}, web addresses or page content. Deleted when you clear the history, and (Chrome 130 or later) automatically once the task is permanently deleted. |
cr_last_task | chrome.storage.local | For each website (its origin, such as https://example.com) where you ran a task, which task ran last, so the keyboard shortcut can run it again |
cr_hotkey_confirmed_<task> | chrome.storage.local | That you confirmed running this task with the keyboard shortcut |
cr_danger_ok_<task> | chrome.storage.local | That you confirmed running this task even though it deletes or removes things (asked once per task, before its first run) |
cr_lu_guide | chrome.storage.local | For a task made from the "Delete list rows" template: which of its rows still need you to pick the delete or confirm button (row IDs only). Deleted when you finish picking. |
cr_st_defaults | chrome.storage.local | For a task made from the "Repeat a click" template that has no rows yet: the row defaults to use for its first rows (click rows don't wait after clicking). Deleted once the task has rows. |
cr_scan_value_mode | chrome.storage.local | Which value mode ("Random test data" or "Current page values") you last chose when scanning a form |
cr_scan_hint_off | chrome.storage.local | The websites (their origin, such as https://example.com; at most 200) where you chose "Don't suggest here" for the "This page has a form" suggestion |
cr_ask_last | chrome.storage.local | For each task that has {{ask}} rows: your last answers (except password, card-number and one-time-code / verification-code answers, which are never saved), whether you chose to be asked every round, and when, used to pre-fill the form next time. Each answer is cut to 2,000 characters. Kept until you remove the extension. |
cr_ui_lang | chrome.storage.local | The interface language you chose with the language button or in Settings ("Follow browser" or one of the 10 languages). Not set until you choose; English is used by default. |
cr_backup_hint_dismissed | chrome.storage.local | That you closed the "Export a backup" reminder |
cr_run | chrome.storage.session (cleared when the browser closes) | The position of a running task (tab, task, a random ID for that run, website origin, round and row, and the address of the page it was on just before moving to another page), so it can continue after the page moves to another page of the same site, and so a failure on the new page can offer “go back to the previous page” as a fix |
cr_runlog_cur | chrome.storage.session (cleared when the browser closes) | While a task is running: the same kind of timing data as the run history above (task, start time, round, row, row durations), so the record survives if Chrome unloads the extension's background. Removed when the run ends. |
cr_rec | chrome.storage.session (cleared when the browser closes) | While you are recording: which tab and task, the website origin, and how many unsaved rows there were before, so recording can continue after the page moves to another page of the same site. Deleted when recording stops. |
cr_autorun_seen | chrome.storage.session (cleared when the browser closes) | For "Run automatically": for each tab where a task ran automatically in the last 30 seconds, the page address (without the part after #) and the time, so the task does not run again when the same page reloads. Entries older than 30 seconds are dropped. |
cr_open_editor | chrome.storage.session (cleared when the browser closes) | When you click "Open editor" on the page's ClickRow bar: which task and tab to open and that page's address. The popup deletes it as soon as it reads it, and ignores it after 30 seconds. |
cr_anon_id | localStorage of ClickRow's popup page (not chrome.storage) | The random ID described in section 3, created only when you first click a Pro button |
cr_wl_sent_pro_want, cr_wl_sent_pro_waitlist | localStorage of ClickRow's popup page (not chrome.storage) | The time each Pro message was delivered, so it is not sent twice |
Exported files. You can export your tasks to a JSON file. The file is saved where you choose and ClickRow does not send it anywhere. It contains your tasks exactly as stored, including any text you typed into rows, in plain text (not encrypted); anyone who gets the file can read it. If a task fills a card, code or password field with a value you typed, ClickRow warns you before exporting. Keep exported files private, or replace such values with {{ask}} before exporting.
2a. Keeping and deleting your data
- Everything in section 2 stays in your browser until you delete it or remove the extension. Removing ClickRow from Chrome deletes all of it, including the popup page's
localStorage. - Items in
chrome.storage.sessionare cleared when the browser closes; several are removed earlier, as described in the table. - Deleting a task moves it to the trash (the 20 most recent deleted tasks are kept so you can undo). Its run history can be cleared at any time in the task's history; it is also removed after the task leaves the trash (Chrome 130 or later). Saved
{{ask}}defaults (cr_ask_last) are not removed when a task is deleted; they are removed with the extension. - ClickRow keeps no copy of your data anywhere else, so there is nothing for the developer to delete except a Pro message you chose to send (section 3).
3. Optional "Pro" interest message
The extension shows a "Batch from CSV" page for a Pro feature that is not available yet. Nothing is sent unless you click one of its buttons. When you do, the extension sends a single message to the form service Web3Forms (api.web3forms.com), which forwards it to the developer's email inbox:
| When | Fields sent |
|---|---|
| You click "I want this" | event name (pro_want), feature name (csv_batch), extension version, your browser language (for example en-US), and a random ID generated on your device. If you typed an email address before clicking, it is included too. |
| You type your email and click "Notify me" | event name (pro_waitlist), feature name, extension version, browser language, the same random ID, and the email address you entered |
Each message also carries the form's public access key, a fixed subject line ("ClickRow - Pro interest" or "ClickRow - Pro waitlist") and the sender name "ClickRow". The random ID is not linked to your Google account, your browsing or your tasks. No task, page address, page content or browsing information is included.
Each type of message is sent at most once per installation: after it has been delivered, the extension remembers that and does not send it again. If delivery fails, it may be tried again the next time you click.
Your email is used only to tell you when the Pro feature launches. As with any web request, Web3Forms can see your IP address; the extension does not add it to the message. Web3Forms is an independent service: it may keep submitted messages and request logs under its own privacy policy (web3forms.com/privacy), which ClickRow does not control. To have your email deleted from the developer's inbox, contact the developer (see Contact below); you can also contact Web3Forms about the copy it keeps.
4. What we do not do
- No analytics, telemetry, tracking pixels, crash reporting or advertising.
- No user accounts or sign-in.
- We do not collect your browsing history, the websites you automate, page content, or what you type into tasks.
- We do not sell, rent or share data with third parties, and we do not use it for any purpose unrelated to the extension's single purpose. Web3Forms only delivers the optional message in section 3 to the developer (and may keep it under its own policy, as described there).
- No remote code: all of the extension's code is included in the package published on the Chrome Web Store. Tasks are plain data that you create or import yourself; the extension does not download tasks or code from the internet.
The use of information by ClickRow adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
5. Children's privacy
The extension is not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has sent us an email address through the Pro form, please contact us and we will delete it.
6. Changes to this policy
If the extension's data practices change, this page will be updated and its effective date changed before the new version is published.
7. Contact
Questions, or requests to delete your email: 603356553@qq.com (the same address used by "Send feedback" in the extension).