PrintQLock Privacy Policy

About This Policy

This policy explains how PrintQLock handles information when you use the PrintQLock Chrome extension and its connection to a PrintQLock server. PrintQLock is developed by FikesMedia. This policy is separate from the privacy policy for the FikesMedia website.

PrintQLock is designed for organization-hosted printing. Your organization selects and operates its PrintQLock server, or appoints a service provider to operate it. Its privacy notices and agreements govern how it manages accounts, print documents, records and access to that server.

Information the Extension Handles

Print documents and settings: when you deliberately print to the PrintQLock destination, the extension receives the PDF, document title and selected print options. It sends them to your configured PrintQLock server. Documents may contain personal, confidential or sensitive information that you choose to print.

Account and printing information: the extension retrieves your account name, username, printing permissions, held-job count and remaining printing allowance. A username may be an email address. This information identifies the sender, applies printing restrictions and displays your print workspace.

Connection and authentication information: the extension uses your configured server address, an optional organization Access Key, and scoped authorization tokens. Sign-in takes place on your organization’s PrintQLock portal. The extension’s scripts do not read the password entered on that portal or access biometric information used by a passkey.

Operational information: pending submissions include an account identifier, submission reference and timestamp. Local notifications contain print confirmations or error messages, timestamps and read status. Requests to the server include the extension identifier.

How Information Is Used

The extension uses this information to authenticate your connection, obtain your permitted print options, submit documents, display queue information, retry interrupted submissions, report errors and disconnect your browser. Portal shortcuts open your organization’s PrintQLock client application to review jobs, view access information and release prints.

The extension does not read your browsing history, scan unrelated pages, or access your Gmail or Google Drive account. It receives the content you choose to send through the print workflow. It contains no advertising or analytics SDKs and does not transmit extension data for advertising, sale, creditworthiness or lending purposes.

Server Access and Permissions

At installation, the extension does not request access to every HTTPS website. When you click Sign In, it requests optional access to the hostname of your configured PrintQLock server. Browser permission may cover multiple paths or ports on that hostname; the extension separately restricts API requests to the exact configured HTTPS origin and port.

You can decline or revoke server access through Chrome. Without the required access, sign-in and print API requests cannot proceed. The extension does not request host access silently during background printing. Organization-managed browsers may impose additional permission policies.

The extension uses browser storage for configuration, tokens, notifications and pending uploads; the identity API for the portal sign-in flow; and the printer-provider API to register the print destination and receive documents you send to it. Managed deployments can supply the server address and Access Key.

Where Information Goes

Print submissions and account requests go to your configured organization server over HTTPS. A shared FikesMedia print cloud is not required. Installing the extension does not automatically send your documents to FikesMedia.

Your organization’s authorized administrators and service providers may have access to documents, identities and print records according to its server settings and policies. The server, reverse proxy and network infrastructure may record connection information such as IP addresses and request times.

If FikesMedia operates your organization’s server or receives information through a support request, the applicable hosting or support arrangements also govern that handling. Choosing to contact support may disclose information you include in your message.

Local Storage and Retention

The extension stores connection settings, authorization tokens and notification history in your browser profile. Pending PDF documents and related submission information are stored locally to allow retry after an interruption. This is local browser storage; it is not a guarantee that the stored files are encrypted at rest.

After a successful submission is acknowledged, the pending local document is removed. If an upload fails or its outcome is uncertain, the local copy can remain until a successful retry, manual discard, successful disconnect or extension reset. Clearing Notifications removes the local notification history.

PrintQLock server retention is separate. Your organization determines how long it keeps documents, print history, reports, logs and backups. Deleting a pending browser copy or resetting the extension does not delete documents or records already received by the server.

Your Choices and Access

Use Notifications to retry or discard pending local documents and clear notification history. Use Settings to disconnect or reset the extension. A successful disconnect clears the local authorization and pending submissions. Reset clears local extension data and attempts to revoke the server connection; if the server cannot be reached, server-side revocation may need to be completed later.

Changing server hosts or resetting the extension attempts to remove previous optional host grants, subject to browser policy. Organization-managed configuration may remain or be reapplied after reset.

You can revoke connected-browser access through your PrintQLock account where available, or ask your administrator to revoke it. Contact your organization about access, correction, deletion or retention of accounts, documents and records on its server. FikesMedia cannot automatically access or delete data on independently operated servers.

School and Organization Use

PrintQLock may be deployed by schools and other organizations. The organization is responsible for deciding who may use its deployment, configuring access, providing applicable notices and arranging any required permissions or consents. For a student’s account or print records, contact the school administrator. If you believe information about a child has been sent directly to FikesMedia inappropriately, contact us using the address below.

Security

The extension requires HTTPS for its server connection and uses scoped authorization tokens. Its scripts do not bypass certificate validation. Protect your browser profile, account and device because local pending documents and credentials can be sensitive. No method of transmission or storage can guarantee absolute security.

Changes and Contact

FikesMedia may update this policy as PrintQLock changes. The updated version will show a revised date on this page.

For questions about this policy or information received directly by FikesMedia, contact support@fikesmedia.com. For documents and records held by your organization’s PrintQLock server, contact its administrator first. Do not include passwords, Access Keys, authorization tokens or confidential documents in an initial support request.