GramG Ninja — Privacy Policy
Effective date: 11 November 2026 · Applies to the GramG Ninja browser extension for Chrome and Edge, version 7.0.0 and later. Usage statistics (§5) start with version 10.0.0; the optional Supervisor App connection (§5A) with version 11.0.0, and its account details with version 12.0.0. The block confirmation, settings from our server and voluntary support (§5B) start with version 13.0.0. The optional AI helpers (§5C) are in the GramG Ninja Android app only. Your Team — the GP and its block office (§5D) — starts with version 15.0.0. · ← Back to GramG Ninja · Website privacy policy
1. Who we are
GramG Ninja is a free productivity extension published by Vision Technologies and Robotics.
It helps authorized users of the Government of India / State Government VB-G RAM G (Viksit
Bharat – Rozgar & Aajeevika Mission, Gramin / MGNREGA) portal (*.dord.gov.in) complete
routine data-entry and reporting tasks faster. It is an independent tool and is not affiliated with, or
endorsed by, any government body.
2. What the extension stores — and where
All storage is local to your browser/device: either the extension's own storage
(chrome.storage) or the browser storage of the portal page you are using
(localStorage). The extension has no account system. The only things it sends to our servers are
the usage statistics and live counters, and — only if you choose to — “Register your GP”, the block confirmation,
the uninstall survey (§5) and the Supervisor App connection (§5A). From version 13 it also downloads a small
settings file from us (§5B).
| Data | Why | Where it is kept |
|---|---|---|
| Your signing details (name, designation, department, mobile, email) | To fill the Work Entry certificate blocks for you | chrome.storage (see §3 on Chrome sync) |
| Settings and saved join recipes (which report pages to combine) | To remember your preferences and offer one-click re-runs | chrome.storage.local |
| Autofill defaults: for each field you choose, the page, the field and the value you saved. A value can be anything you type into that field, including a password if you choose to save one for a password field. | To fill the field for you the next time the page loads | chrome.storage.local, also copied to chrome.storage.sync (see §3) |
| Caste register cache (Job Card number → caste), taken from the Registration Application Register — when you open it, or (version 13+) when GramG Ninja reads it for you during a Sync or a Caste breakup | To show the caste-wise wage-list breakup without re-opening the register each time | chrome.storage.local (on your device only) |
| Registration register names (job card number, name, gender, age, and whether the register marks the person deleted), read from the GP's public Registration Application Register when you click Sync | So the List Builder, the eKYC / ABPS data and the worker list leave out people deleted from a job card and include new applicants | chrome.storage.local (on your device only) |
| eKYC / ABPS status data (registration numbers, applicant names, eKYC and ABPS status), taken from the portal's Aadhaar / ABPS Status Report when you click Sync | To skip workers who are not eKYC-done / ABPS-enabled in Work Demand and Work Allocation, to build the 4A list in the List Builder, and to show eKYC/ABPS status on the Wage List | chrome.storage.local (on your device only) |
| Account status data: from the portal's Add/Edit Commercial/RRB Bank, Branch, Ac No. details list, read when you click Sync (step 3) on the Sync page — for each person on it, the job card number, name, whether an account number is entered (not frozen) or missing, and the last 4 digits of that account number (never the whole number); anyone else on the register counts as frozen | To show A/C ✓ / A/C not frozen / No A/C in the List Builder and Bank Account Entry, and (only the word) to the Supervisor App when connected (§5A) | chrome.storage.local (on your device only); a reading cut short by the portal is kept for a day so the next Sync can finish it |
| List Builder draft (the households and people you ticked) | To keep your list if the page reloads before you load or download it | chrome.storage.local |
| ABPS enable (NPCI) run log: for each worker processed, the village, job card number, registration number, name, the name as printed on the Aadhaar record, and the result and reason the portal gave | To resume a long run after an interruption, to give you the downloadable log, and to show the NPCI reason beside each worker on the Wage List | The portal page's localStorage while a run is active; a copy of the last run's results in chrome.storage.local |
| Muster Roll run log: work code, work name, muster roll number, number of workers, persondays, amount, and the result | To resume a long run and give you the log | The portal page's localStorage while a run is active; a copy of the last run's results in chrome.storage.local |
| FTO verification memory: for each State Sanction No., the people already accepted (job card number + job seeker name) | So "Accept unique & Submit" can stop at someone already accepted for that sanction in an earlier submit | The portal page's localStorage; forgotten automatically after 180 days |
| Bank Account Entry list (version 12+): for each worker you add, the job card number, applicant number, name, IFSC, account number, the name in the bank, what the portal already had, and the portal's answer after Update | To enter each worker's account on the portal one by one, keep the list if the page reloads, and show the results | The portal page's localStorage, in your browser, until you press Clear list. Passbook photos from the Supervisor App are shown, not saved. |
| Work Demand / Work Allocation run progress (registration numbers, applicant names, dates, status) while a bulk autofill is in progress | To let you resume a long sheet after an interruption | The portal page's localStorage, in your browser |
| GramG Tracker connection key and your GP's name, only if you approve a connection on the Tracker's connect page. In version 7 nothing uses it, because sending is switched off (§4). | For sending works to your GP's Tracker sheet, if a later version switches sending on | chrome.storage.local; removed when you disconnect or remove the extension |
| Usage statistics (version 10+): a random install id made at install, per-day counts per module (for example “Work Demand: opened 3, submitted 41”), and the codes and names of the Panchayats you worked on | Kept until they are sent once a day (§5); counts older than 14 days are dropped | chrome.storage.local; removed when you remove the extension |
| Supervisor App connection (optional): the connection key, your operator name, when each GP's worker list was last shared, and the latest counts of people waiting per village (with the supervisors' names), and the queue of Work Demand results not yet sent back | To load supervisors' lists, send results back and show the counter on the toolbar icon | chrome.storage.local; the results queue in the portal page's localStorage |
| Register your GP (optional, versions 10 to 14.5): the name, designation, mobile, email and note you typed | So the form shows what you sent | chrome.storage.local; the version after 14.5 no longer has the form and deletes these details from your browser |
| Block confirmation (version 13+, block / PO login): that you confirmed your block, and when | So you are not asked again | chrome.storage.local |
| Settings from our server (version 13+): the support and notice texts (§5B), when a reminder or the support card was last shown, which notices you have seen, and the date you pressed I've supported | To show reminders at most as often as described, and not at all for 3 months after you supported | chrome.storage.local |
| Report tables and PDFs you choose to process | To export CSV/JSON, build summaries, split an 8-page PDF into the 8 certificates, or compress oversized scans | Held in memory during the action; not persisted or transmitted |
Aadhaar numbers are never read or stored. When the ABPS enable feature presses the portal's Show Aadhaar button so that the portal can check with NPCI, the number the portal reveals is not read, copied or saved by the extension. The Wage List status feature never reads the Aadhaar column.
3. Chrome account sync
Your signing details and your autofill defaults may be saved with chrome.storage.sync so they
survive a reinstall and follow you to the same Chrome profile on another computer. If you are signed in to
Chrome with sync on, Google carries this data through your own Google account; that transfer is handled by
Google under Google's Privacy Policy, not by us, and we never receive it. If you are not signed in to Chrome,
the data stays only on your device. If you would rather a value did not travel with your Chrome account,
such as a password, do not save it as an autofill default.
4. GramG Tracker connection (switched off in version 7.0.0)
GramG Tracker is a free web app from Vision Technologies and Robotics where a GP's staff keep one shared works sheet. The extension contains a connection to it, but in version 7.0.0 Send to Tracker is switched off and has no button, so nothing is sent. The Tracker's own connect page can still hand the extension a connection key, which is stored but not used. If a later version switches sending on, it will work only as described below, and this policy will be updated first.
- Off by default: used only if you click Connect to GramG Tracker, sign in to your Tracker account and approve the connection.
- What would be sent: when you click Send to Tracker on a portal report and confirm,
the work-level columns of that report: work code, work name, financial year, category, sansad, persondays,
and labour and material costs, to
gramgninja.subho.net, into your own GP's sheet. - What would never be sent: worker or applicant names, job card numbers, Aadhaar, eKYC/ABPS data, bank details, caste data, or your signing details.
- When: only when you click Send. Nothing in the background.
- Stopping it: Disconnect in the extension, or remove the connection in GramG Tracker → Settings.
- Data in GramG Tracker is covered by the GramG Tracker privacy page.
5. Usage statistics, “Register your GP” and the uninstall survey (version 10 and later)
Usage statistics — always on (from version 13). So that we know which modules
people use and where things go wrong, the extension sends a short report to our server
(deowb-cms.subho.net, run by Vision Technologies and Robotics) about once a day:
- a random install id made by the extension (not linked to your name, email or Google account);
- the extension version, browser (Chrome or Edge) and browser language;
- per day and per module, counts only: how often a module’s panel was opened, how many runs were started and finished, and the totals of a run — for example “Work Demand: 41 submitted, 3 rejected” or “Re-Print: 36 muster rolls saved” — and which modules you switched off in Settings;
- the Panchayats you worked on: the public LGD-style codes and names of the State, District, Block and Gram Panchayat, as shown on the portal.
Live counters (from version 10.0.1). Our Freeze DPR, IAY Activity and Generate & Print Muster Roll pages show how many DPRs, activity lines and muster rolls GramG Ninja has done for all users. For that, each time one of those three tools freezes a DPR, saves an activity line or generates a muster roll, it sends one short message straight away with the 10-digit Gram Panchayat code, the work (scheme) code, a random id for that run and the tool's version — plus the activity code you chose (for example ACT888) for IAY Activity, and the muster roll number the portal gave for Generate & Print Muster Roll. These codes are public on the portal; no name, job card, install id or anything else is in it.
It never sends worker or applicant names, job card or registration numbers, Aadhaar, eKYC / ABPS details, bank details, caste data, your signing details, your autofill values, or anything you type. Work codes and muster roll numbers are sent only by the live counters below. Because the Panchayat is included, these statistics show which Gram Panchayats use GramG Ninja; they are not anonymous. Our server stores the counts with the time they arrived; it does not keep your IP address with them.
No switch from version 13. The statistics are part of how GramG Ninja is kept free and improved, so version 13 and later always send them; they stop when you remove the extension. (Versions 10 to 12 had a Share usage statistics switch; a copy updated to version 13 sends them whatever it was set to.) Copies of the extension loaded for testing never send them.
In the GramG Ninja Android app. The app sends the same statistics and block confirmation, recorded as coming from the Android app. Our server takes them only together with the app's licence: a note signed by the Supervisor App server when you connect the app to your Supervisor App operator account (§5A), renewed every day. It holds an account number the Supervisor App made for you (an internal id, not your name, email or phone number), the codes of your Gram Panchayats in the Supervisor App, your plan (free) and its expiry, so these statistics are linked to that Supervisor App account. If the app is not connected to the Supervisor App, it has no licence and our server does not keep its statistics.
Register your GP (optional, versions 10 to 14.5). In Settings → Register your GP you could send us your name, designation, mobile number and/or email, a note, and the Panchayat the extension last worked on, so we can tell you about updates and help you. It was sent only when you pressed Send. The version after 14.5 no longer offers it (your Supervisor App account and the portal login already tell us who and which Panchayat). What was sent stays with us, used only for that, until you ask us to delete it (§10).
Confirm your block (version 13+, optional). On the block (Programme Officer) login, a box asks once a day, until you confirm, whether the State, District and Block GramG Ninja read from the portal are right, and for your email. Only when you press Confirm it sends us your email, the State, District and Block names, the 7-digit block code shown on the portal, the extension version and the install id. We use it only to tell block users about GramG Ninja updates and to help them; it is kept until you ask us to delete it. Later sends nothing.
Uninstall survey (optional). When the extension is removed, your browser opens a page on
deowb.subho.net asking why. Answering is optional; it sends the boxes you tick, what you write,
the extension version and — only if usage statistics were on — the install id.
How long we keep it, and who sees it: usage statistics and survey answers for up to 24 months; a registration until you ask us to delete it. Only Vision Technologies and Robotics staff can see them, in a private admin page. We use them only to improve GramG Ninja and to contact registered users about it; we never sell or share them. To have your registration or statistics deleted, email [email protected] with your name or Panchayat.
5A. Supervisor App connection (optional, version 11.0.0 and later)
GramG Ninja – Supervisor App (demand.sebagram.in), also run by Vision Technologies and Robotics, lets your GP's supervisors (mates) prepare work-demand lists on their phones. Nothing is sent to it until you connect GramG Ninja with your operator account there (popup → Data tools → Supervisor App). Once connected:
- Sharing the worker list — when you press Share, and (from version 13) automatically after each Sync while you are connected: the GP's code and the names of the State, District, Block and GP, the village names, and for each worker the job card number, applicant number, name, village, and eKYC yes/no and ABPS yes/no; and, once GramG Ninja has read the portal's Add/Edit Bank list (Sync step 3 on the Sync page), the account status word: frozen, not frozen, or no account — with the date that list was read. Never Aadhaar, account numbers (not even the last 4 digits) or other bank details, caste, signing details or anything you type.
- Lists from supervisors — when you press 📥 From supervisors on the Work Demand page, the extension downloads the people supervisors sent for your GP (job card, name, Work From date, days) and the app marks them as taken by the operator.
- Results — after a Work Demand run, for each of those people: entered or needs a check, with the message the portal gave, so the supervisor can see it.
- Asking for account details (version 12+) — when you press 📨 Ask supervisors for account details on Generate Wagelist: for each worker you ticked, the job card number, applicant number and name, so your GP's supervisors can collect the passbook.
- Account details from supervisors (version 12+) — when you press 📥 From supervisors in Bank Account Entry, the extension downloads the account details you verified in the app: job card, applicant number, name, account number, IFSC and account holder's name, and the supervisor's name. The passbook photo is fetched only when you open it, to check against, and is not saved. The app marks them as taken by the operator.
- Account results (version 12+) — after each Update in Bank Account Entry, for each of those workers: updated or refused, the portal's message, and the account number, IFSC and holder's name that were entered, so the request is closed or comes back to the operator.
- Works you create — when you save a work on the portal's Work Entry pages (or press 📥 Send this work to the Supervisor App on a work's edit page): the work code, work name and the details shown on those pages, so supervisors can pick the work in their demand lists.
- The counter — every 10 minutes, and when you open the popup, the extension asks how many people are waiting per village (counts and the supervisors' names), how many verified account details are waiting, and (version 13+) how many supervisors wait for your approval, for the GPs you work for.
- Start the Supervisor App guide (version 13+) — the guide asks the app for your GP's join link and how many supervisors are waiting / approved, to show the link, its QR code and a ready WhatsApp message. Sending that message is up to you.
The shared data goes only to your own GP in the Supervisor App, where your GP's operators and approved supervisors use it. What the Supervisor App keeps, for how long, and who can see it is in its own privacy policy; to have data deleted there, see data deletion. To stop: Disconnect in Data tools (and remove the connected browser on the site).
5D. Your Team: the GP and its block office (optional, version 15.0.0 and later)
With the Supervisor App connected (§5A), a GP and the block office above it (the Programme Officer's office, as on the portal) can work together through it. A GP belongs to exactly one block office. Nothing here happens unless you are connected, and the portal work itself is still done by you, on the portal.
- Which office you are in — on a page of your portal login, the extension sends the Supervisor App what that page shows about your office: on a block (PO) login the State, District and Block names, the block code and the block's Panchayats as its list shows them (codes and names); on a GP login the GP's code and name. The Supervisor App uses it to put you in that block office, or to check an invite is used on the right office's login. It is read from the page; nothing is typed or sent to the portal.
- One-time invites — when you make one in Your Team, the app keeps which office it is for, who made it and when, and who used it; the code itself is shown to you once and kept only as a one-way hash. An invite link you open in this browser hands its code to the extension (the externally connectable page, §8), which keeps it until you open a page of that office's login.
- Accounts to freeze — when Bank Account Entry puts an account on the portal, and when you press 🧊 Ask your block to freeze on Generate Wagelist: each worker's job card number, name and the last 4 digits of the account (never the whole number) go to your GP's block office there. At the block, the extension downloads them when a member presses 📥 From GPs in Freeze Worker Accounts, and after the run sends each one's result (Frozen, Not found, Name differs… and the portal's message).
- Allocation and muster rolls — the people Work Demand entered from the supervisors' lists wait in Work Allocation (📥 To allocate: job card, name, dates and work, as already held for your GP); after a run, each one's result goes back with the dates allocated. The block office then sees, per GP, the work, the allocated dates and the number of workers (no names) for the muster rolls to generate; after its run, the muster roll numbers go back, to the GP's Re-Print (📥 New muster rolls).
- Who sees what — the members of a block office see the GPs of their block on GramG Ninja (name, code, how many operators) and what those GPs sent them; a GP's operators see their block office's name and members (names and roles, never contact details) and what it did with their requests; supervisors see the allocation and muster roll of the people they sent, and the freezing of the accounts they sent, and get a notification when a muster roll is made (only the GP's name and a count).
All of this is kept in the Supervisor App under its own privacy policy. To stop it, disconnect GramG Ninja (§5A) or ask the office's owner to remove you.
5B. Settings from our server and voluntary support (version 13 and later)
Settings. About once a day the extension downloads a small settings file from
deowb-cms.subho.net: the texts and UPI details of the support request, how often it may be shown,
and an occasional notice about GramG Ninja. Nothing about you or your work is sent with that request.
Support (voluntary). GramG Ninja is free. After a run has finished, a small card inside the portal page may ask for support — at most once a week, never as a system notification, and not for 3 months after you press I've supported. The support page shows our UPI ID and a UPI QR code (Vision Technologies and Robotics); you pay, if you choose to, with your own UPI app, and the payment is handled by your UPI app and bank. GramG Ninja does not see or store your bank or payment details, and paying or not changes nothing in the extension. The usage statistics (§5) count only that the card or page was shown or clicked.
5C. AI helpers in the GramG Ninja Android app (optional)
The GramG Ninja Android app can use your own Google Gemini API key for AI helpers. The browser extension for Chrome and Edge has no AI helpers.
- Your key is added by you in the app's Settings → AI helpers. It is kept only on that phone, encrypted with the Android Keystore, and is never sent to Vision Technologies and Robotics. You can test it or forget it there at any time. Its use and any cost are between you and Google.
- Nothing is sent unless you tap an AI action. Today the only one is Read with AI on a passbook photo in the Supervisor App's Accounts screen, opened in the app.
- What is sent then: that one passbook photo, which shows a worker's name and bank details, goes from your phone straight to Google using your key. It never passes through our servers.
- What comes back: the account number, IFSC and account holder's name that could be read. They are only filled into the boxes for you to check against the passbook. Nothing is saved or submitted for you; you still press Verified yourself.
- Free and paid keys: with a free Gemini key, Google may use what is sent to improve its products; with a billing-enabled key it does not (see Google's Gemini API terms). The app asks for your agreement before the first photo is sent, and you can withdraw it in Settings → AI helpers.
- The app's usage records keep only whether a read worked and how long it took, never the photo or the values.
6. What the extension does NOT do
- It does not send the portal data it works with to Vision Technologies and Robotics or to any third-party
server. Apart from the usage statistics, live counters and the optional registration and survey in §5, and
the Supervisor App connection if you connect it (§5A), the only network
requests it makes are to the portal itself, on your own logged-in session — for example, reading every
village of the ABPS report when you click Sync, or every wage list of the GP for the payment-readiness
report — and to the portal's public reports site (
vbgramgrep.dord.gov.in) for your GP's Registration Application Register during a Sync or Caste breakup. From version 13 it also fetches the settings file and sends the block confirmation described in §5 and §5B. - It never reads or stores Aadhaar numbers.
- It contains no third-party analytics, tracking pixels or advertising; its only telemetry is the usage statistics in §5 (always on from version 13).
- It does not sell, rent, or share your data with anyone.
- It works on websites other than the portal only if you switch that on yourself (Settings → Other websites), and even then only fills, pastes or reveals what you ask it to on the page you are using (see §8). Usage statistics never include other websites.
- It does not run remote or hosted code — all libraries (pdf.js, jsPDF, SheetJS) are bundled and run offline.
7. Sensitive / third-party data
Several features handle data about workers that you, as an authorized officer, already see on the portal: caste values from the Registration Application Register (for the caste-wise wage breakup), eKYC / ABPS status, names as printed on Aadhaar records (in the NPCI run log), and names and job card numbers (in the FTO memory). GramG Ninja keeps this only on your device to do the job you asked for; it is never uploaded anywhere. You can clear each item at any time (see §10). Please use these features only for legitimate, authorized administrative work, and keep the computer you use them on secure.
8. Permissions and why they are needed
| Permission | Why |
|---|---|
storage, unlimitedStorage | Save your signing details, settings, saved recipes, autofill defaults, the caste cache and the eKYC/ABPS data locally. Unlimited storage lets the caches grow across many Gram Panchayats without hitting the small default quota. |
activeTab, scripting | When you click the toolbar or a button, run the fill/extract logic on the page you are viewing. |
tabs | List your open report tabs so you can pick which ones to consolidate, and show the toolbar re-run badge when a saved recipe's pages are open. Only tab URLs/titles are read, on your device. |
Host access to *.dord.gov.in | The extension's features run on the VB-G RAM G portal pages. |
Optional broad host access (*://*/*) | Optional and requested only at runtime, with your explicit approval. It is used for two things you switch on yourself: the “Extract this page” data tool, which reads tables from a report page whose address it cannot know in advance; and Settings → Other websites, which lets autofill, copy & paste and the show-password button work on sites other than the portal. It is not requested at install and is never used silently. |
alarms | When the Supervisor App is connected: check every 10 minutes how many people supervisors sent are waiting, for the counter on the toolbar icon (§5A). From version 13 also: fetch the settings file about once a day (§5B). |
externally_connectable (demand.sebagram.in) | Lets only the Supervisor App's connect page hand the extension its connection key after you approve there (§5A), and (version 15+) its invite page hand over a one-time invite code you opened (§5D). No other website can talk to the extension this way. |
Optional host access to gramgninja.subho.net and externally_connectable (gramgninja.subho.net) | For the GramG Tracker connection, which is switched off in version 7.0.0 (§4). The host access would be requested only when you click Connect to GramG Tracker; externally_connectable would let only the Tracker's connect page hand the extension its connection key after you approve. No other website can talk to the extension. |
The usage statistics (§5) need no extra permission: they are sent as a plain request that our server accepts only from the extension.
9. Data retention
Data stays on your device until you remove it, with two exceptions: the FTO verification memory forgets each
sanction's accepted people automatically after 180 days, and usage-statistics counts are dropped from your
device 14 days after they were counted. What reaches our server is kept as described in §5. Uninstalling the extension removes its
chrome.storage data, and clearing the portal's site data removes what is kept in the portal page's
localStorage. Synced data is also removed from your Google account when Chrome next syncs after
uninstall.
10. How to delete your data
- Signing details, settings, caste cache: open the extension's options and clear the
fields, or remove the extension from
chrome://extensions. - Autofill defaults: in the extension's saved autofill defaults, press 🗑 Delete this default beside each one.
- eKYC / ABPS data: 🗑 Clear ABPS data.
- List Builder draft: 🗑 Clear list in the List Builder.
- ABPS enable (NPCI) and Muster Roll logs: ↺ New run (clear) in the panel clears the run kept in the portal page. The copy of the last run's results in the extension's storage stays until the next run replaces it or you remove the extension.
- FTO verification memory: Forget in the FTO panel, for the sanction you are viewing; otherwise it is forgotten after 180 days.
- Work Demand / Work Allocation progress: use Start over in the panel, or clear site data for the portal.
- Everything kept in the portal page: clear the site data for the portal in your browser's settings.
- Supervisor App: Disconnect in Data tools removes the connection key and the counts from your browser. For the data already shared with the Supervisor App, see its data deletion page.
- Usage statistics: from version 13 they stop only when you remove the extension (the counts on your device go with it). For what already reached our server, and for a registration, email us (§13).
11. Children
GramG Ninja is a workplace tool for government administrative staff and is not directed to children.
12. Changes to this policy
If this policy changes, we will update this page and its effective date. Material changes will also be noted in the extension's What's new page. The 18 October 2026 update added the usage statistics, registration and uninstall survey of version 10 (§5). The 20 October 2026 update added the live counters of version 10.0.1 (§5). The 21 October 2026 update added the optional Supervisor App connection of version 11.0.0 (§5A). The 25 October 2026 update added the bank account details exchanged with the Supervisor App in version 12.0.0 (§5A) and the Bank Account Entry list kept in your browser (§2). The 30 October 2026 update covers version 13.0.0: usage statistics always on (§5), the block confirmation with email (§5), settings from our server and voluntary UPI support (§5B), sharing the worker list after each Sync, works and the join link with the Supervisor App (§5A), and the Registration Application Register read during a Sync (§2, §6). The 3 November 2026 update added the optional AI helpers of the GramG Ninja Android app, with your own Gemini key (§5C). The 6 November 2026 update added the Android app's licence, sent with its usage statistics and block confirmation (§5).
13. Contact
Questions or requests: [email protected] — Vision Technologies and Robotics.
© 2026 Vision Technologies and Robotics · GramG Ninja · Project page · Work Demand (4A) guide