Effective date: November 12, 2026
Operator: Avant Payments Inc. (Chrome Web Store publisher name: Avant Payments)
Privacy and support contact: contact@avantpayments.com
Website: https://avantpayments.com/
This policy describes Avant Print version 0.2.1, Chrome extension apioddgapongcglooghplepdnoonolio, and its on-demand Windows USB receipt-printing helper. Avant Print is a companion to Avant POS; it is not a standalone printing application.
The authorized Avant POS website supplies the receipt text to be printed, a store/order-based receipt identifier, a random request identifier, an automatic-print or reprint mode, and printer-setup requests.
Receipts can include business names and addresses; cashier and customer names or a customer phone number; products, quantities, dates, order and register references, and notes; transaction amounts, discounts, tax, tender, change, payment method, and displayed payment references or masked identifiers. Supported order notes may contain allergy information or other information entered by the merchant. The printer bridge checks text structure and length; it does not remove sensitive subjects from receipt text. Merchants should not enter passwords, authentication tokens, or unnecessary sensitive information into fields that may print on receipts.
The extension receives the sending page's URL and origin to verify that a printing request comes from the authorized Avant POS website. It forwards the origin, not the complete page URL, to the local helper. It does not query Chrome's browsing-history database or monitor unrelated browsing. As of version 0.2.1, the Chrome Web Store package accepts requests only from https://cookie-pos-staging.vercel.app; production merchant use requires a separately approved release.
The helper reads local Windows printer queue names, drivers, USB ports, data type and status, and USB device-interface identifiers to select and verify a printer. A hash of the selected USB device identifier is saved. Setup and status responses may return the selected printer name and status; print responses may return a Windows print-job number.
The helper does not request browser cookies, passwords, account credentials, microphone, camera, or GPS access. Receipt text comes from Avant POS, not from email, messaging, or medical services. The bridge does not classify the subject matter of merchant-entered notes.
Information is used only for requested receipt printing, printer setup and readiness, and prevention of duplicate print submissions. The local printing path is: authorized Avant POS website → Chrome extension → on-demand Windows native helper → Windows printing system → selected USB receipt printer.
Receipt contents are processed in memory by the extension and helper. They are not deliberately saved as receipt documents or diagnostic logs by those components. Windows and the printer may separately retain job contents or job and account metadata according to their own settings. Printed paper necessarily contains the submitted receipt information. Retention by Windows and the printer has not been independently verified.
The extension, runtime helper, and installer do not contain an analytics, advertising, cloud-printing, email, or developer-upload client. They do not send merchant receipt contents to an external server. Browser and Windows distribution, security, updates, and downloads, and the separate Avant POS application's own data and network activity, are subject to their respective systems and policies. Publisher-side installer signing and timestamping are build activities, not transmissions of merchant receipt data.
The Avant POS website stores an automatic-print claim in browser local storage using a store/order-based key and an attempted-print value. The helper stores files under %LOCALAPPDATA%\AvantPOS\Print, including:
printer.json — selected printer details and a hashed device identifier;
attempts\<hash>.attempt — a hash derived from the origin, receipt identifier, and automatic-print or reprint request context, plus an attempted marker; and
installation and native-host metadata.
File metadata can reveal when an attempt occurred. Hashes are not a guarantee of anonymity. These records support printer setup and protection against repeated automatic submissions. Attempt files do not contain receipt text or transaction amounts. Printer-selection and attempt records are ordinary local files, not separately application-encrypted archives.
There is no scheduled expiration or automatic purge for these records. Removing the Chrome extension does not remove the website's browser local storage or the helper's retained files. Uninstalling the helper removes its executables and native-host registration and its owned Windows Apps registration, but intentionally retains printer selection, duplicate-prevention history, and an installation ownership marker to support safe reinstallation. Uninstallation does not erase Avant POS financial records or data held by Windows or the printer.
Merchants may disable automatic printing in Avant POS Hardware Settings, use the existing browser-printing option, change the selected printer, remove the Chrome extension, and uninstall the Windows helper separately.
There is currently no built-in erase-history control. For questions about retained local records or to arrange reviewed removal when records are no longer required, contact Avant Payments Inc. at contact@avantpayments.com. Deleting browser print claims or helper attempt records can remove duplicate-print protection, so merchants should not clear them to retry an uncertain print job. Avant Print cannot remotely remove records from a merchant's computer.
Do not provide receipt contents, passwords, credentials, or diagnostic logs to support unless they are specifically needed and knowingly authorized.
Avant Print's handling of user information complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Information is used and transferred only as necessary for the disclosed local printing, setup, and duplicate-prevention purposes. Avant Print does not sell user data, transfer it for unrelated purposes, use it for advertising, or use it to determine creditworthiness or for lending.
The reviewed implementation has no facility for developer access to receipt contents. Any separately arranged support access must be specifically authorized by the user and comply with applicable Limited Use requirements.