Frequently asked questions

1. Right-click the destination field and choose Remote Fill.
2. Scan the one-time QR with your phone.
3. Enter or paste one value, send it, and review the filled field.

No account or phone app is required. The extension never submits the destination form.

You can transfer one short-text, long-text, or password value to common editable fields. Without the extension, use Web transfer. It decrypts locally, then lets you copy the value into the destination yourself.

The web option uses the clipboard; the extension does not. If you only need to create a new value, the password generator runs locally without creating a transfer.

Yes. Web transfer shows a short-lived Share with me link beside the QR. The link's eight-character code is grouped as XXXX-XXXX for readability. Send that link only to the intended person and keep the receiving page open. Opening it starts the encrypted handoff directly; someone entering its code manually selects Continue. The shared link and QR represent the same one-time invitation, so the first successful claim wins and both disappear together.

Remote Fill cannot identify the recipient or control how they use, copy, store, or share a value after delivery. The sender must know and trust the recipient; a sent value cannot be recalled. A share code is easier to communicate but has less guessing resistance than the full QR invitation; its two-minute lifetime, strict request limits, and encrypted browser-to-browser exchange reduce that exposure.

• Use Chrome 120 or newer and confirm detection on the test page.
• Start again if the QR is over two minutes old or has already been scanned.
• Keep the original page and selected field open until delivery finishes.
• Chrome internal pages and fields replaced by the site cannot be filled.

Password managers usually bind credentials to a website. The transfer page and destination have different addresses, so the destination credential may not appear. Open your password manager and copy the one value manually.

The extension creates a one-time route and ephemeral P-256 ECDH key. Your phone derives a key with HKDF-SHA-256 and encrypts the value with AES-256-GCM before upload. The relay carries the opaque envelope but has no decryption key; the extension authenticates the route, destination, field type, and expiry before inserting the value.

For a remote share, the open receiving browser separately encrypts that same one-time invitation to an ephemeral key created by the sender's browser. The relay sees the short code and opaque wrapping envelope, but not the invitation or its write capability.

This is relay opacity, not a formal zero-knowledge proof. Formal zero-knowledge cryptography does not inherently require accounts or storage. However, the “zero-knowledge vault” model commonly described by password managers assumes a service that manages an account and persistently stores encrypted user data while lacking its decryption key. Remote Fill intentionally provides neither account management nor persistent credential storage, so relay opacity is the narrower and more accurate claim: the relay briefly coordinates delivery of ciphertext but cannot decrypt the value.

Release tests cover tampering, replay, concurrent claims, single consumption, and cryptographic known-answer cases. These tests do not claim FIPS validation, FedRAMP authorization, an ATO, penetration testing, or an independent audit.

No. The first valid phone or shared-code sender claims the route, each envelope can be delivered once, and all active state expires within two minutes. Remote Fill creates no account or recoverable transfer history.

Someone who captures the QR or share link could race the intended sender for the first claim, so treat either invitation as a short-lived secret.

It cannot protect plaintext from a compromised phone, extension, browser, operating system, keylogger, screen capture, password manager, or destination page after insertion. The phone and extension are endpoints and necessarily handle the plaintext.

See the Privacy page for the complete data-handling record.

Remote Fill application code, protocol implementation, documentation, visual assets, and trademarks remain proprietary. Commercial evaluation, integration, and licensing are available only by written agreement. The licenses below apply only to the named third-party materials.