Privacy

One user-chosen value, for one active transfer

Fill from Phone handles only the destination context and value needed to move text into the field the user explicitly selects.

Effective 2026-10-06 · Protocol version 5

Single purpose

Move one value from the user's phone to one selected Chrome field

The extension does not provide advertising, analytics, identity, credential storage, browsing-history collection, or background page inspection. Its transfer receiver activates only after the user invokes Fill from Phone on an editable field. A separate no-data presence marker runs only on the product's extension test page.

Data handled

What the product processes

User-selected value: The phone temporarily processes the text the user chooses to send. That value may contain personal information, authentication information, or other website content. It is encrypted on the phone before upload and decrypted only by the extension for insertion into the selected field.
Destination context: The extension temporarily uses the active page origin and whether the chosen target is a password, single-line text, or multi-line text field. The destination context is authenticated end-to-end and shown to the phone, but is excluded from the relay reservation schema.
Installation test marker: Only on /test, the extension sets the literal value installed so the page can display whether it is ready to test. The marker sends no extension ID, version, account, browsing history, selected-field data, or security authority and creates no separate request.
Transfer metadata: Short-lived random route, expiry, capability hashes, presented bearer capabilities, cryptographic public material at the endpoints, and an opaque encrypted envelope are processed to operate the transfer. No account or persistent user identifier is created.
Connection metadata: Hosting and network providers necessarily process routine connection information such as IP address, timing, and HTTP delivery metadata to deliver the website and service. Fill from Phone disables application and origin access logging for transfer requests and does not use connection metadata for advertising or profiling.

Use, sharing, and retention

No sale, advertising, or unrelated reuse

Data is used only to provide, secure, and troubleshoot the user-requested transfer.
Hosting and network providers process encrypted traffic and routine connection metadata only as necessary to operate the service. Fill from Phone does not sell transferred data or share it with advertisers, data brokers, or unrelated third parties.
The active relay state is held in memory, works once, and expires within two minutes. The service creates no recoverable transfer history and intentionally persists no transferred plaintext.
Humans are not given access to transferred values. Support and vulnerability reports must use synthetic examples and must not include passwords, private keys, capability tokens, or other sensitive content.

Chrome Web Store Limited Use

Use is limited to the disclosed transfer

Fill from Phone's use of information received through Chrome extension APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Information is used only to provide or improve the single user-facing transfer purpose, is not used for personalized advertising or credit decisions, and is not sold.

User control

Start, cancel, or let it expire

A transfer begins only after the user selects an editable field and invokes Fill from Phone. The desktop can cancel while the QR is visible. The phone clears its visible control when Send is pressed, the relay removes the envelope after delivery or expiry, and the extension never submits the destination form.

For privacy or technical questions, email contact@asanowharton.com or use the support page. For suspected vulnerabilities, follow the security reporting guidance. This policy will be updated before any material change to data handling is released.