Nyanza.ai - Nyanza Autofill browser extension

Privacy Policy

Last updated: November 12, 2026

Nyanza Autofill helps you fill out job applications using the profile you built at nyanza.ai. The extension keeps a local autofill copy, while your synced source profile and kits live in your Nyanza account. The extension fills supported fields and you review and submit the application. It never clicks a page-owned Next, Continue, or final Submit control.

The short version: we don't sell your data, run advertising analytics, or load remote code. The extension exchanges data with your nyanza.ai account. When you ask Nyanza to generate a kit or answer, relevant job and career content may be processed by Nyanza's server and its managed AI provider or the provider you configured. Values placed into an employer-controlled page may be processed by that page before you submit. An optional, default-off vault can securely store and fill a host-bound employer-site login on narrowly reviewed account steps.

What the extension does

Its single purpose is to help you apply to jobs with your own Nyanza materials. It can read and save a posting you choose, show fit and sponsorship history, request a prepared kit or draft, fill matching application fields, attach your tailored resume, and record the outcome. You review everything and submit directly on the application page.

After you start a fill, the extension keeps filling new steps of the same application on that page as you advance them yourself, and shows a small note on the page with a Stop button. It stops when you press Stop, move to a different application, or submit. Each new step uses a fresh read from your Nyanza account; when a later step asks for your resume, the extension fetches the same resume again for that step instead of keeping a copy.

If you separately enable the login vault, the extension can generate or retrieve an employer-site credential, store it encrypted in your Nyanza account, and fill it only on a reviewed account-creation or sign-in surface for the same host. Account consent, verification challenges, and the Create Account or Sign In action remain yours.

For Save + build kit, the extension reads only this browser's Local/Cloud engine choice from nyanza.ai. In known Local mode it saves the posting but does not request cloud kit generation. If it cannot verify the choice, it explains that the build uses Nyanza's server and an AI provider and requires a second confirmation before starting it. The relayed preference contains no API key, model name, prompt, resume, or profile content.

Sponsorship history on job pages (opt-in, off by default)

Whether or not you are signed in to Nyanza, you can choose Show it on job pages in the extension or its options. Chrome then asks you to allow access to LinkedIn, Indeed, Greenhouse, Lever, Ashby, and Workday job pages. On a single job posting there, the extension reads the employer's name and the posting's own wording about visa sponsorship on your device. It sends only the employer's name to Nyanza's public sponsorship lookup, without your Nyanza cookie, the page address, the job text, or any identifier, and shows that employer's past H-1B and green-card (PERM) filings from public USCIS and Department of Labor records, with a link to its public sponsorship page. Past filings are history, not a promise, and "no filings found" means unknown, not a no. Nyanza's server does not save these lookups; like any web request, they pass through our hosting provider, whose short-lived request logs record the address a request came from. Answers may come from a shared cache, and recent answers stay in the extension's session storage for up to six hours. The badge never fills, clicks, or submits anything.

When you are signed in, the popup's job card and the fit check show the same sponsorship wording, using the same public lookup that sends only the employer's name, with no cookie; the posting's own wording is read on your device.

The badge works the same way signed in and signed out. Its last line differs: signed in, it links to the full fit check for that posting in Nyanza, and the posting's address goes to Nyanza only if you open that link; signed out, it links to the waitlist and to sign-in. To choose that line, the extension keeps one yes-or-no value: whether the nyanza.ai page shows someone signed in, never who. Turn the badge off in the extension's options or by removing the site access in Chrome.

In-page fit check (opt-in, off by default)

If you grant the optional access to every HTTPS site, the extension can recognize a page that looks like a job posting on your device and offer a Check fit prompt. Recognizing the page and showing the prompt send nothing. Only when you click Check fit does the extension send that posting's page address and the job details it detected on the page (title, company, location, and up to about 20,000 characters of description text) to your signed-in Nyanza account. Nyanza's server may fetch the public posting itself, compares the role with your Career Persona, and shows the result on the page. Choosing Not now sends nothing. The check never fills, clicks, or submits anything, and you can remove the access in Chrome at any time. With the same access, the extension can also recognize an application form and offer to autofill it; that fill starts only when you click Autofill on its prompt.

DS-160 visa form fill (preview, switched off)

The extension contains a fill with review for the U.S. visa application (Form DS-160) on ceac.state.gov. It is switched off for everyone while Nyanza reviews that site's terms, and nothing in this section happens unless it is turned on.

When it is on, you first pick whose DS-160 this is (you or a family member you added in Nyanza), and the panel names that person the whole time. Only after you press Fill this page on a DS-160 page does the extension ask Chrome for access to that one site, load that person's DS-160 answer sheet from your Nyanza account, and reads the fields on the page on your device. It writes each answer that has one empty field on that page, including the choices that make the site reload the page to open more questions, outlines every field it wrote, and lists what it filled and where each value comes from. You review after the fill: a value you change in the list is changed on the page, and Undo this fill puts the page back. A field that already holds something else is left alone unless you ask. It never presses Next, Save, or Sign, never answers the security question, a CAPTCHA, or a declaration. Verify everything before submitting. This is not legal advice.

Your application history. After a fill, the extension saves to the Immigration profile in your Nyanza account: the Application ID the page shows, the form's OMB control number, form number and printed expiration date, the visa type you chose, and which page was filled with how many fields. It is kept so you can find the application again, and you can remove an entry on your Immigration Profile page. No value from a field on the visa page is sent, and Nyanza never stores your security question or its answer.

Passport and ID numbers. Passport, national ID, Social Security, taxpayer, visa, driver's license, SEVIS, and petition numbers come from two places. Numbers you confirmed for a person in Nyanza are stored there encrypted and tied to that person, and arrive in that person's answer sheet only. Numbers you type into the extension are kept in its storage on your computer, separately for each person, are used instead of the ones in Nyanza, and are never sent to Nyanza. For a national ID, Social Security, taxpayer or passport book number you can instead mark that it does not apply; the extension then ticks the form's own "Does Not Apply" box for that field. A number goes only to a field of its own page, and never into the sign page's passport box. Remove these numbers in the panel, Clear local Persona cache in the extension's options, or removing the extension deletes the typed ones; the ones in Nyanza are removed on the Immigration profile page.

One person per application. The extension refuses to fill an application whose Application ID is already in another family member's history, before writing anything.

The job-application autofill, its in-page prompt, and the fit check do not run on ceac.state.gov.

Information the extension handles

The extension does not use Chrome's History API or build or store a browsing history. Guided autofill handles the current page URL and content only when you invoke it. If you grant optional site access, the extension can inspect the pages that access covers to detect an application form or a job posting (see the in-page fit check above for what a check sends).

How your information is used

Your information is used only for these purposes. It is never used for advertising, creditworthiness, or lending.

Where your information is stored and sent

Nyanza does not send extension data to advertising analytics or use it for unrelated purposes. The AI-provider and employer/ATS disclosures above are the feature-related destinations.

Autofill compatibility reports

The extension's Autofill history remains available after the original application tab closes. It explains field and page failures and shows whether an eligible report is not shared, queued, uploaded, waiting to retry, or revoked. You can share one event, retry or cancel a queued report, revoke an uploaded report, delete a local receipt, or clear device history. These controls do not edit or delete your private Saved Answers.

Local field receipts, page receipts, queued report payloads, and payload-free delivery records are physically deleted after at most 90 days. The local ledgers are also size capped, and surviving rows are rebuilt through allowlist schemas on worker startup.

Shared report content is retained by Nyanza for at most 90 days and is capped per account. Revoking deletes the structural content; Nyanza may keep only the random event ID and revocation time for up to 180 days so a delayed offline retry cannot restore it. Deleting the Nyanza account removes its dedicated structural-report store. Clearing device history by itself does not delete reports already sent to Nyanza, and the extension warns you when remote reports remain.

Nyanza clusters only closed structural fields such as ATS family, page type, adapter version, normalized field intent, widget type, failure code, pseudonymous fingerprint, and verified resolution outcome. Extension version is retained as an aggregate breakdown rather than used to split the same component pattern into separate clusters. A cluster is shown as candidate evidence only after at least 3 distinct users across 2 distinct sites. Aggregates contain counts, not user identities or site hashes. A single correction never creates a global rule. Learned recipes are not distributed to or executed by the extension.

Disabled future "Report this form" diagnostic

This richer diagnostic is a design only and is not enabled. The extension does not currently capture or upload form HTML, labels, option text, or screenshots for self-healing. Any future version would require a separate preview and consent flow, clone only the relevant form area, and aggressively remove values, checked/selected states, filenames, hidden inputs, tokens, scripts, styles, unrelated content, and sensitive/legal/ self-identification fields. It would also require short encrypted retention, restricted operator access, and deletion controls. Whether labels, options, reduced markup, or screenshots should ever be allowed; how redaction is verified; retention and operator access; third-party content; and backup/derived-data deletion remain open privacy decisions. The feature will stay disabled until those decisions and safety thresholds are resolved.

What the extension does not do

Permissions and why they're needed

Your choices

You can view and edit the extension's local autofill copy from its "Edit details" screen. You can turn aggregate reliability sharing on or off at any time in Fill settings; it is off by default. Autofill history lets you revoke shared reports and delete individual local receipts; you can also clear device history or remove the extension. Clearing local storage does not revoke a report already received by Nyanza, so use Revoke first when you also want the server content deleted. Individual receipts and reports are bounded by the caps and retention periods above. Private Saved Answers remain separate and are not changed by these controls. Vault logins can be deleted from the extension, and revealed or copied in your Nyanza Profile, when the vault is available. Your synced source profile, kits, and activity remain in your Nyanza account until you edit or delete them there. To stop the extension from accessing the account, sign out of nyanza.ai; to remove optional site access, revoke it in Chrome's extension settings.

Changes to this policy

If this policy changes, we'll update the date at the top of this page.

Contact

Questions about this policy or your data? Email privacy@nyanza.ai.