Chrome Extension Privacy Policy
Effective October 29, 2026. Version 2026-10-29.
- Nothing passes through us. The extension does not send data to its publisher and has no analytics, telemetry or third-party SDKs.
- Only to your Ordo. Everything you capture goes only to the Ordo server whose address you yourself provided.
- Only when you ask. The current page is read only when you click the icon, use the menu or a shortcut.
- No Google account. The extension does not request access to your Google account and does not use Google APIs.
1. The extension
The Ordo — tarefas e projetos extension (the “extension”) is published by Banvya Consultoria em BaaS Ltda. (CNPJ 29.341.943/0001-60), which operates Ordo. It has a single purpose: creating and tracking tasks in Ordo from the browser — capturing the page or selected text as a task, reporting issues with a screenshot, seeing what is due today and receiving reminders.
To work, the extension requires an account on a Ordo server (the cloud service at app.ordopath.com or your company's own installation) and a personal API token that you create on that server. It works in Chrome and in Chromium-based browsers, such as Edge, Brave, Arc, Opera and Vivaldi.
2. Data the extension processes
| Data | When | Purpose | Where it is kept |
|---|---|---|---|
| Server address and API token | When you configure the extension | Authenticating calls to your Ordo | Only in this browser (chrome.storage.local); not synced with your Google account |
| Your name, email address and list of workspaces | When testing the connection and when opening the popup | Showing which account you are connected with and allowing you to switch workspaces | Only in this browser |
| Address, title and icon of the current tab and the selected text | Only when you trigger the extension: always via the right-click menu or the capture shortcut; via the popup, if “Attach this page” is checked | Composing the task and the link to the source page | Sent to your Ordo server |
| Screenshot of the visible tab and your annotations | Only in “Report on this page”, after you click Send | Attaching it to the issue report or suggestion | Sent to your Ordo server |
| Technical report data: page address and title, referring page, browser, language, time zone and screen size | Only in “Report on this page” | Helping the team reproduce the issue | Sent to your Ordo server |
| Diagnostics collected by the website's widget — only if the website visited has the Ordo feedback widget installed, as configured by the website's administrator: console errors, recent requests (address, method and status), URL parameters, names of the fields of the last form submitted (without the values), cookies (names only, or names and values, never those that appear to be secrets), recent clicks and the user identification provided by the website | Only in “Report on this page” | Helping the team reproduce the issue | Sent to your Ordo server |
| Tasks due today, overdue tasks and upcoming tasks with a set time (temporary copy: title, key, project, link and due date) | At each periodic check (default: 5 minutes) | Showing the counter on the icon and due-date reminders | Only in this browser |
| Offline queue | When the server is unreachable while creating a task | Resending the task when the connection is restored, without duplicates | Only in this browser, until sent or until you discard it |
On its own, the extension does not read your browsing history, does not run in the background on the pages you visit, does not read forms or passwords and does not access any page other than the tab that is active at the moment you trigger it.
Before a report is sent, password fields and areas the website has marked as sensitive are masked in the screenshot, and you can blur any other area. Technical text (console, requests) undergoes automatic redaction of tokens, email addresses, CPF and CNPJ numbers (Brazilian individual and corporate taxpayer IDs) and card numbers.
3. Where the data goes
Data leaves the browser only to the Ordo server whose address you provided in the extension settings, over HTTPS (or HTTP, if you configure an internal network address). The extension requests browser access only to that server's origin and revokes it if you switch servers.
The extension's publisher does not operate intermediary servers and does not receive a copy of anything. The processing of data within the server is governed by the privacy policy of whoever operates it: for the cloud service, the Ordo Privacy Policy; for a self-hosted installation, your company's policy.
4. Google account and Gmail
The extension does not request access to your Google account, does not use the chrome.identity API and does not call Google APIs. The “Sign in with Google” feature exists only in the web application and is described in the Privacy Policy.
“Smart capture” recognizes GitLab, GitHub and Gmail pages solely to give the task a clean title and store the page link. In Gmail, it uses only the address and title of the tab open at the moment you trigger the extension — it does not read your inbox, the body of emails or your contacts.
5. What we never do
- Sell, rent or transfer data to third parties.
- Use or transfer data for advertising, user profiling or any purpose unrelated to the extension's single purpose.
- Use or transfer data to determine creditworthiness or for lending purposes.
- Allow humans to read the data, except with your consent, for security purposes, to comply with the law, or when the data is aggregated and anonymized.
- Load or execute remote code: all of the extension's code is contained in the published package.
The extension's use of data complies with the Limited Use policy and the Chrome Web Store User Data Policy.
6. Permissions and why they are requested
| Permission | Use |
|---|---|
storage | Storing the settings, the token, the offline queue and the temporary copy of tasks due today, overdue tasks and upcoming tasks with a set time. |
alarms | Periodic check (icon counter and resending of the offline queue) and one alarm per task with a set time, 15 minutes before the due time. |
notifications | Confirming captures and alerting you to upcoming due dates, with Complete and Snooze buttons. |
contextMenus | “Create task…” and “Report issue…” items in the right-click menu. |
activeTab | Reading the tab's address and title and capturing the visible screen only when you trigger the extension. |
scripting | Reading the selected text and opening the annotation editor in the active tab, together with activeTab; nothing remains permanently injected. |
| Site access (optional) | Requested at runtime only for the address of your Ordo server, so that the extension can call its API. |
7. Legal bases and roles
The extension is a tool that runs in your browser under your control. The data it sends to the Ordo server becomes Customer Data, processed by the Provider as operator (processor) (LGPD) or processor (GDPR) on behalf of the company that owns the workspace, on the basis of the performance of the contract and that company's legitimate interests in organizing work (LGPD, art. 7, V and IX; GDPR, art. 6(1)(b) and (f)). Browser notifications depend on your authorization. Your rights are described in Section 13 of the Privacy Policy.
8. Retention and how to delete
- Removing the extension deletes from the browser everything it stored (settings, token, queue and temporary copies).
- You may revoke the token at any time in Ordo, under Settings → API tokens; the extension loses access immediately.
- Tasks, reports and attachments already sent remain on the Ordo server and can be deleted there. For other requests concerning this data (access, rectification, deletion — LGPD, GDPR, CCPA), contact your workspace administrator or the Data Protection Officer of the server's operator.
9. Security
The token is kept only in the extension's local storage and is sent only to your server, in the authorization header. Calls do not carry the browser's cookies. The extension's pages follow a content security policy that prohibits external scripts and dynamic code.
10. Changes to this policy
If this policy changes, the date at the top of this page will be updated. Material changes in how data is processed will be accompanied by a new version of the extension and, where required, a new request for consent.
11. Contact
Questions or requests about this policy: Artur da Silva Júnior, Data Protection Officer (DPO / encarregado), [email protected]. Extension support: [email protected].
This document is also available in Portuguese, English and Spanish. If the versions differ, the Portuguese version prevails.