AssetView Sidecar Privacy Notice

Last updated: October 4, 2026

This notice describes how the AssetView Sidecar browser extension treats your information. It adds to the AssetView Products and Services Privacy Policy, which continues to apply to your Account and to the Services. Terms that begin with a capital letter have the meaning that policy gives them.

What the Sidecar is

AssetView Sidecar ("Sidecar") is an optional browser extension that AssetView publishes for the Chrome browser. It does one thing. When you ask the Services for more information about a transaction that is already recorded in your Account, the Sidecar finds the matching purchase or payment on a source you have turned on, in your own browser, and returns its details to your Account for you to review. The sources today are Amazon.com (United States) and Venmo (personal accounts). The Sidecar works only after you install it, sign in to it with your AssetView Account, and approve its pairing with your Account, and only while its panel is open in your browser.

Your details stay in your portfolio

What the Sidecar finds goes to your own portfolio in your Account and nowhere else. AssetView does not use it and does not keep a copy it can read: it is encrypted in your browser, before it is sent, to a key that belongs to your Account, and the means to open it exist only inside the Services' application when you have unlocked it. AssetView's servers store and deliver it in encrypted form only.

What the Sidecar reads, and when

The Sidecar reads a source only after all of the following:

• you have turned that source on in the Sidecar, and granted the extension access to that source's one website in your browser's own permission prompt (www.amazon.com for Amazon, account.venmo.com for Venmo). The Services ask the Sidecar about a source's transactions only after you turn that source on; and
• you have approved the request in the Sidecar, or you have turned on the Sidecar's "Always" setting for that source. With "Always" on, the Sidecar starts that source's searches for new requests without asking again, while its panel is open and the access to the website is still granted, until you turn the setting off.

The Sidecar reads in your browser, in the session you are already signed in to at the source.

Amazon. The Sidecar reads two kinds of page on www.amazon.com: Your Payments (Transactions), and the order details page of a charge that matches a purchase you asked about. On Your Payments it reads, for each charge listed: the date, the amount, whether it is a charge or a refund, the payment method label as Amazon displays it (for example a card type and its last four digits), the order number and the merchant line. On an order details page it reads the order number and the items (name, quantity and price). To reach older charges the Sidecar may press Amazon's "Next Page" control on Your Payments, up to twelve pages back. While it pages through Your Payments, a notice in that tab says so.

Venmo. The Sidecar opens your personal account's statement page on account.venmo.com and requests, for each month it needs to cover the payments you asked about, the same statement that the page's own Download button provides. It does not press that button, and it types nothing. The statement contains, for each entry, an identifier, a date, a type, a status, a note, the names of both parties, amounts and a funding source, together with balance, fee and other sections. From it the Sidecar keeps only completed payments that you sent, and of those only the payment's identifier, date, amount, the recipient's name, the payment's note and the name of the funding source. The rest of the statement is discarded in your browser and is not kept or sent. The request uses your browser's signed-in session; the Sidecar does not read your Venmo credentials or cookies.

The Sidecar also reads, from the Services, the requests addressed to it. A request identifies each transaction you asked about by a reference, its date, its amount and the payee as your bank shows it.

How the Sidecar knows where to read

For each source, AssetView publishes a signed description: the website, the addresses of the pages the Sidecar may open, and where on a page or in a statement each detail is found. The Sidecar receives these descriptions from the Services, verifies AssetView's signature with a key built into the extension, and uses only those that verify. A description is data, not a program. It says which pages to open, how to tell that a page is ready or wants you to sign in, where each detail is, and how close a date must be to count as a match. It cannot give the Sidecar a new control to press or anything to type, and it cannot reach a website you have not turned on; the one control the Sidecar can press, "Next Page" on Amazon's Your Payments, is built into the extension. AssetView can follow a change in a source's pages by publishing a new description. A source on a website the extension does not already list needs a new version of the extension, because the extension lists the only source websites your browser can grant it (today www.amazon.com and account.venmo.com). A source still does nothing until you turn it on and grant its website in your browser's prompt.

What the Sidecar keeps in your browser, and for how long

• Your sign-in. An access token, a refresh token and the identifier of the signed-in user, so that you stay signed in. Kept until you sign out of the Sidecar, the sign-in ends, or you remove the extension.
• Your pairing. Identifiers of your user and of the pairing, the date of the pairing, and an encrypted record that holds the key the Sidecar signs its requests with and the public key it encrypts its answers to. Kept until you unpair, pair again, or remove the extension. The key that opens that record is kept for the browser session only, and is erased when you sign out of the Sidecar. After you restart your browser, the Services' web application, open and unlocked in the same browser, can give that key back to the Sidecar.
• Encrypted working records, kept with the pairing. The signed source descriptions the Sidecar accepted; the requests it is working on; fingerprints of the requested transactions it has already answered (their reference, date, amount and currency) and of the source records it used, so that it does not answer twice; and answers that are already encrypted and are waiting to be delivered. An answer is removed when the Services confirm that they received it or refuse it. These records are removed with the pairing's record when you unpair and the Services confirm it. If the pairing is ended from the Services instead, they stay in the browser, encrypted and unreadable, until you pair again or remove the extension.
• Your choices. Which sources you turned on, your "Always" setting for a source, and a snooze you set. A source stays on until you turn it off. "Always" belongs to the pairing that chose it and ends with that pairing; turning a source off does not clear it.
• The session's working state. A log of the last hundred steps the Sidecar took (counts, months and dates; no amounts, names or order numbers), whether its panel is open, and, while an unpair waits for the Services to confirm it, the keys that sign it. Kept for the browser session only.

After an update, the Sidecar reads and removes records that an older version of it left in the browser.

Details read from a source are held in the extension's working memory while its panel is open. They are not written to the browser's storage in readable form.

What the Sidecar sends, and to whom

The Sidecar sends information to AssetView only. To read a source, its tabs load that source's own pages and request its statement from the source itself, as your browser does when you use the site, with your signed-in session; those requests carry an order number or a month's dates to the site that already holds them. Otherwise it connects to:

1. AssetView's sign-in service (clerk.assetview.com), to sign you in, to keep you signed in, and to end the sign-in when you sign out. It sends the sign-in tokens described above.
2. The Services' programming interface (client.assetview.com/api). With each request it sends its access token and, once it is paired, a signature made with the pairing's key. When you pair it, it sends a label for the browser: the name "Sidecar", the browser's name, the operating system, and a number derived from the browser's user agent string, its language, and the screen's size and color depth, so that you can recognize this browser in your list of companions. While it is paired and open, it sends a regular notice that it is available and which sources it can answer for; that notice is encrypted to your Account's key. And it sends its answers.
3. A notification connection, at a hosted messaging service whose address and access token the Services provide, over which the Sidecar is told that there is new work. The Sidecar sends no messages over this connection.

An answer is sent only for a purchase or payment that matched a transaction you asked about. For an Amazon purchase it contains: whether it is a charge or a refund, its date, amount and payment method label, the order number and the address of the order page when the charge names an order, and the items (name, quantity and amount) when the order page could be read. For a Venmo payment it contains: its date and amount, the payment's identifier, the recipient's name, the payment's note and the name of the funding source. The recipient's name and the words of the note become part of your own records. Each answer also names the source, the revision of the source description that was used, the time the answer was made, which request and transactions it answers, the dates it covers and, when something could not be read, a short reason. Around the encrypted answer the Sidecar sends the identifiers, digests and signature that deliver it. Before an answer leaves your browser, the Sidecar encrypts it to a key associated with your Account, which it received when you approved the pairing, and signs it. Charges and payments that match none of your requests are not sent.

If a source's page changes and the Sidecar cannot read it, you may choose "Report a problem". The report tells AssetView the name and revision of the source description, which kind of page it was, which named parts could not be read, and the Sidecar's version. It contains nothing from the page.

As with any connection from your browser, the services above receive your IP address and standard connection information.

What the Sidecar does not read or send

• It does not read or store a password. You enter your AssetView credentials on AssetView's own sign-in page, not in the Sidecar. It does not read your credentials for any source, and it does not read cookies.
• It does not read any website other than those of the sources you turned on, and on those only what is described above. It does not ask for access to a source's separate sign-in website. It does not read your browsing history, your other tabs or your location.
• It does not read your name or your delivery address from Amazon. It reads a payment method only by the label the source displays.
• It does not place orders, send money or change anything in your account at a source. The only control it operates on any website is "Next Page" on Amazon's Your Payments.
• It does not create or change transactions or other records in your Account. Its answers are for you to review in the Services.
• It contacts no advertising or analytics service, and it runs no code from outside the extension.

How you remove the Sidecar's access

• Turn a source off, in the Sidecar's Work menu. The Sidecar gives that website's access back to your browser and the Services stop asking it about that source. An answer that was already waiting is still delivered. If you turn the source on again, your browser may restore the access without asking a second time.
• Unpair, in the Sidecar's Account menu. The Services stop sharing with that Sidecar, and once they confirm, the Sidecar forgets the pairing and what it kept with it.
• Remove it in the Services, under Vault, then Companions. This ends the pairing at once, also when you no longer have the browser the Sidecar was in.
• Sign out, in the Sidecar's Account menu. The Sidecar asks the sign-in service to revoke its sign-in and erases its tokens. Signing out does not end the pairing.
• Withdraw a site permission. In your browser's extension settings, remove the Sidecar's access to a source's website. It can then read no page there until you grant the access again.
• Turn off "Always", in the Sidecar's Work menu.
• Remove the extension. Your browser deletes what the Sidecar kept. Removing the extension does not by itself end the pairing or revoke the sign-in: unpair and sign out first, or remove the Sidecar under Vault, then Companions.

How AssetView uses this information

AssetView uses the information the Sidecar reads and sends only to provide the feature described in this notice. AssetView does not sell it. AssetView does not transfer it to third parties, except to service providers as needed to provide the feature, to comply with applicable law, or to protect against fraud and abuse. AssetView does not use or transfer it to determine creditworthiness or for lending purposes. AssetView's use of information handled by the Sidecar adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.

Contact us

Questions about this notice: assetview.com/support, or the contact details in the AssetView Products and Services Privacy Policy.