1. Introduction
This Privacy Policy explains how Quaker Window Products Co., doing business as Quaker Windows & Doors ("Quaker," "we," "us," or "our") collects, uses, discloses, and protects personal information when you use the Quaker Partner Hub website and the Quaker Partner Hub mobile application for iOS and Android (together, the "Services").
The Quaker Partner Hub is a business-to-business platform. It gives dealers and partner personnel, architects and design professionals, course instructors, and Quaker personnel access to product information, technical resources, document libraries, continuing-education courses and certificates, and related services.
By using the Services, you acknowledge that you have read and understood this Privacy Policy. Your use of the Services is also governed by our Terms of Service. If you do not agree with this Privacy Policy, please do not use the Services.
Quaker is a Missouri corporation with headquarters at 504 Highway 63 South, Freeburg, Missouri 65035, United States. The Services are intended for users in the United States and Canada.
2. Scope and audience
The Services are intended for business users who are at least 18 years old and are acting in a professional or commercial capacity. The Services are not directed to children and are not intended for personal, family, or household use.
This Privacy Policy applies to personal information we process about:
registered users of the Services, including dealers and partner personnel, architects and design professionals, course instructors, and Quaker personnel;
people who ask for access to the Services, such as architects who request course access, with or without a presentation event code;
people who contact us through the Services; and
visitors to the public areas of the Services, including the public certificate-verification pages and the public account-deletion page.
This Privacy Policy does not apply to:
Quaker's other websites (quakerwindows.com, quakerresidentialwindows.com, quakercommercialwindows.com, quartzluxurywindows.com, and workatquaker.com), which are covered by Quaker's separate privacy policies and terms of use for those websites. The Hub sign-in widget on the first four of those sites is part of the Services and is covered as described in Section 3.4;
information collected by third-party websites, products, or services that we do not control, including external job-application sites and other pages you open through the Services; or
information you give Quaker outside the Services (for example, through sales, warranty, or manufacturing channels), which separate notices may govern.
3. Information we collect
3.1 Information you provide to us
When you register for and use the Services, you may provide:
Identity and contact information: first and last name, email address, telephone number, username, and mailing address (street, city, state or province, and ZIP or postal code).
Professional and business information: company or organization name, division, and role or job title. Architects who ask for course access also give their firm name, firm role, the presentation or event code they attended, and any note they add to the request.
Membership information: whether you are a member of the American Institute of Architects (AIA), your AIA member number if you choose to give it, or your statement that you are not an AIA member. We use this to issue continuing-education certificates and to report learning units as described in Section 9.
Instructor information (course instructors only): a professional biography, credentials, a photograph, and a signature image that appears on certificates.
Account and authentication information: your password (stored only as a one-way hash), email-verification and registration tokens, and one-time sign-in codes that we email to Quaker personnel. If your account was migrated from Quaker's earlier WordPress systems, we also hold the legacy password hash until you first sign in, when it is replaced with a current hash.
Content and communications: course notes, saved links and bookmarks, course evaluations and comments, test answers, comments on news posts where comments are enabled, support requests, feedback, and anything else you choose to submit.
Account requests: if you delete your account and later ask us to restore it, the reason you give, the date, the IP address you sent it from, and whether you sent it from the website or the app.
Legal acceptances: which version of the Terms of Service and this Privacy Policy you accepted, when, and the IP address and browser or device you accepted from.
3.2 Information we collect automatically
When you use the Services, we and our service providers automatically collect:
Device and connection data: IP address, browser type and user-agent string, and operating system and version. In the mobile app we also collect a random device identifier that the app creates, the device name your operating system reports (which often includes your own name, as in "Ana's iPhone"), the platform, the app version, and the IP address each registered device used most recently.
Usage and operational logs: the files, documents, and videos you view, download, or stream; timestamps; download sizes and durations; pages and screens viewed; searches; features used; and, in the mobile app, performance measurements such as load times and cache hits. We keep these logs in our own systems to deliver, support, troubleshoot, and secure the Services and to meet continuing-education recordkeeping requirements. They are not shared with Google, and the analytics settings in Section 4 do not turn them off.
Course engagement and attendance-verification data: for continuing-education courses, your enrollment and progress, which video segments you watch and for how long, pause and seek counts, playback speed, whether the course tab or app stayed in focus, counts of mouse and keyboard activity while a video plays, your answers to periodic attendance checks, and your test attempts, answers, and scores. AIA requires providers to verify attendance, and this data is how we do it (see Section 9).
Security and authentication events: sign-ins, sign-outs, failed sign-in attempts (including the email address that was tried), password resets and changes, one-time-code requests, rate-limiting and abuse-prevention events, device registrations and revocations, and account deletions, with the related IP address, user-agent, device, session, and platform.
Push-notification identifiers: the push token Apple or Google issues for your device, and your notification preferences.
Error and crash reports: when the website or app hits an error, a report with the error, a stack trace, the device and app version, and related technical context goes to our error-monitoring provider, Sentry. These reports are configured to leave out your name, email address, IP address, and the contents of forms you submit, and we do not attach your account to them.
Cookies and analytics data: as described in Section 4. Google may derive an approximate location (city or region) from your IP address as part of its analytics processing.
3.3 Information we receive from third parties
Quaker's other websites. When you use the Hub sign-in widget on one of Quaker's websites, we receive the information described in Section 3.4.
Learning-management integration. If Quaker turns on the BlueVolt learning platform for your account, we share your first name, last name, email address, and an opaque account identifier with BlueVolt so you can be signed in there, and we may receive BlueVolt's list of enrolled users to match accounts between the two systems. This integration is not active on the effective date of this Policy. We will update this Policy before it is.
Service providers that help us operate, secure, and analyze the Services (see Section 7).
We do not buy personal information from data brokers. We do not receive personal information about you from AIA; reporting runs one way, from us to AIA (see Section 9).
3.4 The Hub sign-in widget on Quaker's websites
Quaker's websites at quakerwindows.com, quakerresidentialwindows.com, quakercommercialwindows.com, and quartzluxurywindows.com carry a Quaker Partner Hub sign-in widget. The widget is part of the Services, and this Policy covers what you enter in it and what it shows you. Everything else on those websites, including their own analytics, forms, and cookies, is covered by those websites' own privacy notices.
Signing in. When you sign in through the widget, the email address, password, and any one-time code you enter pass through that website's server to the Hub over an encrypted connection. The website does not store your password or code. The Hub then gives the website your name, email address, account number, account status, and a sign-in token that expires after 8 hours. The website keeps the token encrypted in a cookie in your browser.
Signing in across sites. Signing in on one Quaker website can also sign you in to the Hub and to the other Quaker websites that carry the widget. Signing out ends all of those sign-ins, and so does deleting your account or a change that means your account is no longer approved, such as a suspension.
What the widget shows. The widget displays your Hub notifications from the past two weeks and your saved links, and lets you save the page you are on. A saved link records the page's title, its address (without the query string unless you choose to include it), and the website it came from. Saved links are shared across the Hub and every website with the widget. The website's server may keep a copy of this information for up to 60 seconds so the widget loads quickly, and deletes it when you sign out. In your browser, the widget keeps only your display name and unread-notification count, in session storage that is cleared when you sign out or close the browser.
Returning visitors. If you have signed in through the widget on a website before, that website may briefly send your browser to the Hub to check whether you are still signed in, no more than about once every 30 minutes. For that check, the Hub receives your IP address, your browser type, the website, and the address of the page you are on, without its query string or fragment. Visitors who have never signed in through the widget are not sent to the Hub, and the check runs only after you have accepted at least one optional cookie category in that website's cookie banner.
Records. The Hub records widget sign-ins and failed sign-in attempts with your IP address, browser, the time, and the website you signed in from, as part of the security records described in Section 3.2.
Cookies. The widget sets its cookies on the Quaker website you are visiting, not on the Hub. They are an encrypted sign-in token and a companion marker (8 hours), a sign-in check marker (2 minutes), a returning-visitor marker (1 year, removed when you sign out), and a check-frequency marker (30 minutes). They are necessary for the sign-in you ask for, and each website's cookie notice lists them.
Updated terms. The widget links to our Terms of Service and this Policy. When we update either one, you will be asked to accept the new version on the Hub before you can keep using the widget.
4. Cookies, analytics, and similar technologies
4.1 What we use on the website
Cookies are small text files a website stores on your device. Similar technologies include local storage, tags, and scripts loaded from other domains. We use them to run the Services, keep you signed in, remember your choices, protect the Services, and understand how they are used.
Category | Purpose | Cookies and technologies (how long they last) |
|---|---|---|
Necessary | Required for the Services to work. These cannot be switched off. | Session cookie partner_hub_session (24 hours after your last activity); cross-site request forgery token XSRF-TOKEN (up to 1 day); "remember me" sign-in cookie remember_web_* (up to 400 days, or until you sign out); Cookiebot consent cookie CookieConsent, which stores your choice (12 months); a Pusher local-storage entry used for real-time notifications; and local-storage entries that remember settings you choose: your caption setting on the course video player (whether captions are on, and in which language) and, in the administration panel used by Quaker personnel, the light or dark display theme and whether the sidebar and its menu groups are open or collapsed. These stay on your device and are not sent to us or to anyone else. |
Preferences | Remember choices you make. | None. The settings the Services remember for you are listed under Necessary above. Settings you save to your account, such as notification preferences, are kept with your account (Section 3.2). |
Statistics | Help us understand how the Services are used so we can improve them. Off until you accept. | Google Analytics 4 cookies _ga and _ga_* (up to 2 years), set through Google Tag Manager only after you accept Statistics. For signed-in users, a pseudonymous account identifier is also sent to Google Analytics while Statistics is accepted (see Section 4.5). |
Marketing | Deliver or measure advertising. | None. We do not use marketing, advertising, or social-media cookies or tracking pixels, and advertising features are turned off in our Google Analytics property. |
Some pages load fonts, scripts, and stylesheets from third-party content delivery networks, including Adobe Fonts, Bunny Fonts, the jQuery and DataTables CDNs, jsDelivr, and, on news pages, Google Fonts. When your browser fetches those files, it sends your IP address and user-agent to the network that serves them. We do not send those providers your account information.
The current list of every cookie on the website, including who sets each one and how long it lasts, is in the "Details" tab of the consent banner. Our consent-management platform keeps that list up to date by scanning the website regularly.
4.2 Consent management on the website
We use the Cookiebot consent-management platform (a Usercentrics service) with Google Consent Mode v2.
Before you make a choice, the Google tag loads in a consent-denied state. In that state it sets no analytics cookies, stores no analytics identifier on your device, and sends at most cookieless pings that do not identify you. The advertising consent signals are always set to "denied."
Statistics cookies and analytics identifiers are set only after you accept the Statistics category in the consent banner. Cookiebot holds back other non-essential scripts until you accept the category they belong to.
Cookiebot keeps a record of your choice (with a truncated or hashed IP address, the date and time, and the categories you chose) so that we can show consent was given and so the website remembers your choice on later visits.
You can change or withdraw your choice at any time with the round Cookiebot button in the lower-left corner of every page, which reopens your cookie settings and the cookie list. If you withdraw consent to Statistics, analytics collection stops and the analytics cookies are removed from your browser.
4.3 Browser controls and opt-out preference signals
You can block or delete cookies in your browser settings. Blocking necessary cookies will stop you from signing in.
We do not sell or share personal information for cross-context behavioral advertising, and we do not use the Services for targeted advertising. An opt-out preference signal such as Global Privacy Control therefore does not change how we process your information, because there is no sale, sharing, or targeted advertising for it to switch off. On the website, the consent banner controls analytics cookies. In the mobile app, the setting described in Section 4.4 controls analytics.
4.4 The mobile app
The mobile app does not use website cookies. It uses:
Google Analytics for Firebase to measure how the app is used, such as screens viewed, features used, and course activity. Measurement is on by default. You can turn it off at any time in Settings › Privacy › "Share usage data with Google Analytics." Turning it off stops the app from sending usage data to Google. It does not affect the Hub's own activity, security, and performance logs described in Section 3.2, which we need to keep the app working, support continuing-education audits, and protect accounts.
A pseudonymous account identifier. This is a keyed hash derived from your account. It contains no name or email address, and it lets us measure activity across the website and the app. The app sends it to Google only while analytics is on, and clears it when you turn analytics off or sign out.
Push notifications through Apple Push Notification service or Firebase Cloud Messaging, if you allow notifications.
Crash and error reporting through Sentry, described in Section 3.2. This is separate from the analytics setting and stays on so we can keep the app working.
Device permissions you grant through your operating system: Face ID, Touch ID, or fingerprint for biometric sign-in (your device performs the check, and biometric data never leaves it); local-network access to find Chromecast or AirPlay devices for casting; and notifications.
On-device storage for content you download for offline use (course videos, documents, and notes), cached files, your preferences, and encrypted sign-in tokens. Downloaded content stays on your device until you remove it in Settings › Storage › Downloads, your access to the related course is revoked, or you uninstall the app. Signing out does not delete it.
The app does not use the advertising identifier (IDFA or Android Advertising ID) and contains no advertising software. It does not show Apple's App Tracking Transparency prompt because it does not track you across other companies' apps or websites.
When you open an external link in the app's built-in viewer, the site you open may store its own cookies in the app's browser storage. That site's privacy notice applies.
4.5 What Google receives
We limit what our analytics send to Google as follows.
Never sent to Google: your name, email address, phone number, company, AIA member number, raw account number, the full address of signed download or video links, password-reset, verification, and other links that carry a token, or free-text content. Search terms are the one exception: they are sent after we clean them, and dropped if they look like an email address or an identification number.
Sent to Google: the pseudonymous account identifier, your user type (such as partner personnel, architect, or Quaker personnel), whether you are an AIA member (yes or no only), page or screen type, course and resource identifiers, test outcomes and scores, search terms, and the domain (not the full address) of external links you open.
Server-side events: our servers also send Google Analytics a small set of account events (account approval and suspension, architect access decisions, course enrollment and completion, test results, and certificate issuance) with the same pseudonymous identifier. We check consent when each event is sent and send it only if your browser or app has given consent.
Retention: Google Analytics keeps event data for 14 months. We export raw analytics events to Google BigQuery in the United States and keep them there for 26 months. The export contains no names, email addresses, or other direct identifiers.
Advertising features: Google Signals, advertising personalization, Google Ads links, advertising identifiers, and remarketing are turned off for our analytics property. Every server-side event is marked non-personalized.
Google processes analytics data as our service provider under Google's terms. When you delete your account, or ask us to delete your personal information, we ask Google Analytics to delete the data linked to your pseudonymous identifier and delete matching rows from our BigQuery export (see Section 13.2).
5. How we use personal information
We use personal information to:
Provide and operate the Services: create, approve, and manage accounts; authenticate you; deliver product information, technical resources, document libraries, notes, saved links, and notifications; sign you in across Quaker's websites; and make the Services available on the web and in the app.
Run continuing education and certification: administer courses, verify attendance, grade tests, calculate and track learning units, verify membership status, issue certificates, publish certificate-verification pages, and report completions to AIA (see Section 9).
Communicate with you: answer inquiries and support requests; send service and administrative messages, including registration, verification, one-time-code, password-reset, legal-update, account-deletion, and certificate emails; and, where you have turned them on, send push notifications and email reminders.
Secure the Services: detect and prevent fraud, abuse, account sharing, and unauthorized access; limit request rates; enforce our Terms of Service; investigate security events; and keep the Services available and intact.
Improve the Services: understand usage, diagnose errors and performance problems, and develop features and content, including through the analytics in Section 4.
Meet legal and industry requirements: meet legal, regulatory, tax, accounting, and recordkeeping obligations, including AIA Continuing Education System provider requirements; respond to audits; and establish, exercise, or defend legal claims.
Where applicable law requires consent for certain processing, such as statistics cookies on the website, we ask for it first. You can withdraw consent at any time as described in this Policy.
6. How we disclose personal information
We disclose personal information:
To service providers that work for us under contract and on our instructions, including for cloud hosting and storage, content delivery, video streaming, real-time messaging, push notifications, email delivery, analytics, error monitoring, and consent management (see Section 7).
Within Quaker, among Quaker's business functions, divisions, and affiliates as needed to run and support the Services, approve accounts, and serve your organization. Quaker personnel with administrative roles can see account, enrollment, engagement, and certificate records so they can administer the Services, and they are notified when an account is deleted or a restoration is requested.
To Quaker's websites that carry the Hub sign-in widget, the information described in Section 3.4, when you sign in or use the widget there.
To your organization. Where your account is associated with a company or division, authorized Quaker personnel may share account status and training completion with that organization.
For continuing-education reporting. When you complete an AIA-registered course and have given us an AIA member number, we report your member number, the course number, the session code, and the completion date to AIA (see Section 9).
On public certificate-verification pages. Anyone who scans or enters a certificate's verification link can see the holder's name, course title, completion date, certificate number, revision, and credits earned, and whether the certificate is valid, superseded, or revoked.
About instructors. If you are a course instructor, your name, credentials, biography, photograph, and signature appear on course pages and certificates.
For legal and safety reasons, to comply with law, regulation, legal process, or a government request; to enforce our agreements; and to protect the rights, property, or safety of Quaker, our users, or others.
In a business transfer, such as a merger, acquisition, financing, reorganization, or sale of assets, subject to this Policy or a successor policy.
We do not disclose personal information to third parties for their own marketing.
7. Service providers
The providers below process personal information on our behalf under contractual confidentiality and security obligations. Providers marked "when enabled" are integrated but not active unless Quaker turns them on.
Provider | What it does for us | Data involved |
|---|---|---|
Amazon Web Services (S3, CloudFront; MediaConvert when Bunny Stream is not in use) | Cloud storage, private document storage, content delivery, database backups, video transcoding | Uploaded and served content, certificates, backups, and access logs with IP address and user-agent |
Bunny.net (Bunny Stream) | Course-video hosting and streaming through time-limited signed playback links | IP address, user-agent, and the video requested; no account information |
Bunny.net (Bunny Fonts) and Adobe Fonts | Web fonts | IP address and user-agent of the browser |
jQuery CDN, DataTables CDN, jsDelivr, Google Fonts | Scripts, stylesheets, and fonts | IP address and user-agent of the browser |
Pusher | Real-time in-app notifications over WebSockets | Account channel identifier and connection metadata |
Google Firebase Cloud Messaging and Apple Push Notification service | Push-notification delivery | Device push tokens and notification content |
Resend or Mailgun | Transactional email delivery (our administrators choose which) | Email address and message content |
Google Tag Manager, Google Analytics 4, Google Analytics for Firebase, Google BigQuery | Website and app analytics (consent-based on the web, opt-out in the app) and raw-event export | Usage data, device and connection data, analytics cookies and app-instance identifiers, pseudonymous account identifier |
Cookiebot (Usercentrics) | Website consent management and consent records | Consent choices, truncated or hashed IP address, timestamp |
Sentry | Error and crash monitoring for the website and app | Error details and stack traces, device and app version; personal identifiers excluded |
JotForm (when embedded) | Forms our editors embed in individual news posts | Whatever you enter in the form, under JotForm's terms |
Apple App Store and Google Play | Distribution of the mobile app | Governed by Apple's and Google's own notices |
BlueVolt (when enabled) | Learning-platform single sign-on and account matching | First name, last name, email address, opaque account identifier |
Our database, cache, job queue, and internal performance dashboards run on infrastructure we control; the companies that supply that infrastructure do not receive your data as separate recipients. We will update this list when our providers change materially.
8. We do not sell or share your personal information
We do not sell your personal information, and we do not share it for cross-context behavioral advertising, as "sell" and "share" are defined in the California Consumer Privacy Act, as amended by the California Privacy Rights Act (the "CCPA"), and in similar U.S. state laws. We have not sold or shared personal information in the past 12 months.
We use Google Analytics and Google Analytics for Firebase for measurement only, with advertising features turned off, and not to deliver targeted advertising.
We do not use or disclose sensitive personal information for any purpose that would require us to offer a "right to limit" under applicable law. We use sensitive personal information, such as account credentials, only as reasonably necessary to provide and secure the Services.
We do not knowingly sell or share the personal information of anyone under 16. We are not a data broker and do not make personal information available to data brokers.
9. Continuing-education records and AIA reporting
Quaker is a registered provider in the AIA Continuing Education System ("AIA CES"). If you take continuing-education courses through the Services, the following applies.
Attendance verification. AIA requires providers to verify that learners attended and took part in a course. We do this with the engagement data described in Section 3.2 (watch time, periodic attendance checks, and focus and activity signals) and with tests. Whether a course counts as complete, and whether you receive a certificate, depends on meeting the course's attendance and passing thresholds.
What we report to AIA. For AIA-registered courses completed by learners who have given an AIA member number, a Quaker administrator exports a report containing your AIA member number, the course number, the session code, and the date completed, and uploads it to AIA's CES provider portal. We do not send AIA your name, email address, or engagement data. AIA records the learning units against your AIA account under its own privacy practices. If you have stated that you are not an AIA member, we report nothing to AIA and issue a certificate for your own records.
Certificates and verification pages. Each certificate has a certificate number and a verification link or QR code. The public verification page shows the holder's name, course title, completion date, certificate number, revision, and credits, and says whether the certificate is valid, superseded, or revoked. We may re-issue or supersede a certificate to correct an error; we keep the original record for audit.
Record retention. AIA CES requires providers to keep attendance and completion records for audit. We keep continuing-education records (enrollments, attendance-verification data, test results, evaluations, certificates, reports sent to AIA, and the related audit trail) for at least six years from completion, which is longer than AIA's minimum. We keep issued certificates and their verification records indefinitely so that a certificate can always be verified. We keep these records even if you delete your account (see Sections 10 and 13.2).
Learning-unit expiry. Your credit history marks learning units as expired six years after you earned them, in line with AIA's reporting window. Expired credits stay in your history for reference.
State licensing boards. State and provincial boards set their own continuing-education requirements. Anything we say about board acceptance is general guidance only. You are responsible for confirming your own board's requirements and for submitting certificates to your board where required.
Removing your AIA member number. You can ask us, through your profile, to remove your AIA member number from your account. We cannot withdraw completions already reported to AIA.
10. Data retention
We keep personal information for as long as we need it to provide the Services and maintain your account, to meet legal, regulatory, and industry obligations (including AIA CES provider requirements), to resolve disputes, to enforce our agreements, and for legitimate business purposes such as security and recordkeeping. Typical retention periods:
Data | How long we keep it |
|---|---|
Account and profile information, saved links, notes, notification preferences | For the life of your account. After you delete your account, 30 days (the restoration window in Section 13.2), then deleted or de-identified. |
Continuing-education records: enrollments, attendance-verification and engagement data, test attempts, evaluations, AIA export reports | At least 6 years from completion (AIA CES audit requirement). AIA reporting audit trail up to 10 years. |
Certificates, learning-unit history, certificate-verification records | Indefinitely, including after account deletion, so certificates stay verifiable and reportable. |
Architect access requests (firm name, role, note, member-number snapshot) | Personal details are de-identified 24 months after a request is denied, withdrawn, or left undecided. The decision record is kept without personal details. |
Account-restoration requests (reason, date, IP address) | Deleted with the account data at the end of the 30-day restoration window, or 12 months after the request if the account is restored. |
Legal acceptance records (versions accepted, timestamp, IP address, user-agent) | For the life of your account and any longer period needed to show consent. |
Security and authentication event records, file-access logs | For the life of your account and two years after it is deleted, for security investigation and continuing-education audit. |
Server log files | Security logs 90 days, general application logs 14 days, mobile API logs 30 days. |
General activity records (other than security events and the AIA reporting audit trail) | 365 days. |
App performance measurements (load times, cache hits, device and app version) | 90 days. |
One-time sign-in codes and password-reset tokens | Deleted once they expire (15 and 60 minutes). |
Registered mobile devices (device name, platform, app version, last IP address) and push tokens | Active until you sign out of the device (unless biometric sign-in is on), remove it from your device list, or delete your account. Push tokens are removed when a device is deactivated, and deactivated device records are deleted after 90 days. |
Error and crash reports (Sentry) | 90 days. |
Analytics | Google Analytics event data 14 months; BigQuery export and our analytics identity table 26 months; Cookiebot consent records 12 months. |
Data exports generated in the admin panel | 30 days. |
Database backups | 30 days, and never more than the ten most recent full backups, on private encrypted storage. |
Sessions, tokens, and links | Website session: 24 hours of inactivity. "Remember me" cookie: up to 400 days, or until you sign out. Mobile access token: 2 hours. Sign-in token for the widget on Quaker's websites: 8 hours. Mobile refresh token: 30 days. One-time sign-in code: 15 minutes. Password-reset link: 60 minutes. Registration verification link: 48 hours. Offline-course download authorization: 7 days, renewed while you have access. |
BlueVolt integration records (when enabled) | Sync attempts 90 days; audit events and resolved cases 365 days; imported rosters 7 days. |
When we no longer need personal information, we delete it, de-identify it, or archive it securely. If we must keep a record for AIA audit or legal reasons after you ask us to delete your personal information, we remove or de-identify the personal details that record does not need.
11. How we protect personal information
We maintain administrative, technical, and physical safeguards designed to protect personal information against unauthorized access, use, alteration, and destruction. They include:
encryption in transit (HTTPS with HTTP Strict Transport Security) and encryption at rest for cloud storage and backups;
password hashing with bcrypt, so passwords are never stored in readable form, and upgrading of legacy password hashes from earlier systems at first sign-in;
email one-time codes as a second step for Quaker personnel sign-in, plus rate limits and temporary lockouts after repeated failed sign-ins, by account and by IP address;
account approval and email-domain rules before anyone can see non-public content;
role-based access controls that limit what each user type and each Quaker administrator can see and do, with role and permission changes recorded in an audit log;
private storage and time-limited signed links for restricted documents, certificates, and course videos (typically one to four hours; a link to download a course video for offline use lasts up to 24 hours, while the offline authorization itself is renewed every 7 days as described in Section 10), so links cannot be passed around indefinitely;
security headers, a content security policy, secure HTTP-only cookies, and cross-site request forgery protection on the website;
in the mobile app, sign-in tokens held in the device's secure keychain or keystore, short-lived access tokens with rotating refresh tokens, biometric checks performed on the device, a list of registered devices you can revoke, and an option to sign out of all devices;
logging and monitoring of security events, with suspicious activity flagged for review; and
exclusion of passwords, tokens, and AIA member numbers from activity logs and error reports.
No method of transmission or storage is completely secure, and we cannot guarantee absolute security. If you believe your account has been compromised, contact us right away at the address in Section 19.
If a security breach affects your personal information, we will notify you, and any regulators the law requires, under the applicable breach-notification laws, including Missouri's (Mo. Rev. Stat. § 407.1500) and those of the state or province where you live. Section 13.5 describes our additional obligations in Canada.
12. International data transfers
We store and process personal information in the United States, including in our cloud storage, databases, backups, and email delivery, and in the Google Analytics and BigQuery data described in Section 4. Some providers run global networks: video and font delivery networks serve files from the location nearest to you, and our consent-management provider, Cookiebot (Usercentrics), may store consent records in the European Union.
If you use the Services from Canada or elsewhere, your personal information will be transferred to, stored in, and processed in the United States and the other locations described above, where data-protection laws may differ from those where you live. Where applicable law requires it, including Quebec's Law 25, we assess the protection your information will receive before transferring it outside your province or country and put contractual or other safeguards in place.
13. Your privacy rights and choices
Your rights depend on where you live and which laws apply. We do not discriminate or retaliate against anyone for exercising them.
13.1 Controls in the Services
Profile. You can view and update your name, contact details, and company in your profile on the website or in the app's account settings, and your mailing address on the website.
AIA member number. You can ask for your AIA member number to be removed from your profile.
Analytics. On the website, use the consent banner or the round Cookiebot button in the lower-left corner of each page. In the app, use Settings › Privacy › "Share usage data with Google Analytics."
Notifications. Manage email and push preferences in your notification settings, or turn off push notifications in your device settings.
Devices. In the app, view and revoke the devices signed in to your account, or sign out of all devices.
Downloaded content. In the app, remove offline content in Settings › Storage › Downloads.
This Policy and the Terms. Both are linked from the website footer and from Settings in the app.
13.2 Deleting your account
Dealer and partner personnel accounts and architect accounts can be deleted by the account holder:
on the website, from the "Delete my account" section at the bottom of your profile page; or
in the app, by opening Settings, tapping your name, and choosing "Delete my account."
You will be asked for your password. Instructions are also on our public Delete Your Account page. Quaker personnel, anyone with an administrator or editor role, and anyone currently assigned as a course instructor cannot delete their account this way; they can ask us through the contacts in Section 19.
When you delete your account, we immediately:
sign you out on every device, and on the Quaker websites where you signed in through the widget, and invalidate your sign-in tokens;
deactivate your registered devices and remove their push tokens;
close the account so it can no longer be used;
ask Google Analytics to delete the data linked to your pseudonymous identifier and delete matching rows from our BigQuery export (see Section 4.5); and
notify Quaker administrators.
For 30 days after you delete it, we can restore the account if you change your mind. To ask, sign in with your email address and password and send the short request form, or contact support. During those 30 days you cannot register a new account with the same email address.
After 30 days we permanently delete or de-identify your profile, contact details, notes, saved links, preferences, devices, and the rest of your account data. We keep only the certificates and continuing-education records described in Section 9, stripped of any personal details those records do not need, and the security, file-access, and legal-acceptance records we keep for the periods in Section 10. Once that happens the account cannot be restored, and you can register again with the same email address.
If you want your personal information erased sooner, or you hold an account you cannot delete yourself, email privacy@quakerwindows.com.
13.3 United States: state privacy rights
If you live in a U.S. state with a comprehensive consumer privacy law in effect, you may have the following rights, subject to the conditions and exceptions in that law:
to know and access the categories and specific pieces of personal information we hold about you, its sources, the purposes we use it for, and the categories of third parties we disclose it to;
to correct inaccurate personal information;
to delete personal information we collected from you;
to receive a copy of your personal information in a portable format;
to opt out of the sale or sharing of personal information and of targeted advertising (we do none of these);
to opt out of profiling that produces legal or similarly significant effects;
to limit the use of sensitive personal information; and
to appeal a denial of your request, where your state provides that right.
On the effective date of this Policy, comprehensive state privacy laws are in effect in California, Virginia, Colorado, Connecticut, Utah, Iowa, Texas, Oregon, Montana, Florida, Delaware, New Hampshire, New Jersey, Minnesota, Maryland, Tennessee, Nebraska, Indiana, Kentucky, and Rhode Island, and more take effect over time. We extend the rights above to residents of any state whose law grants them. Missouri, where we are headquartered, has not enacted a comprehensive consumer privacy law; we still offer the controls in Sections 13.1 and 13.2 to all users.
Because the Services are a business-to-business platform, some state laws treat personal information handled in a purely commercial or employment context differently, and some rights may be limited in those states. California does not make that exception (see Section 13.4). We honor verifiable requests as applicable law requires.
How to make a request. Email privacy@quakerwindows.com or write to the address in Section 19. We will verify your request using information linked to your account, and may ask you to confirm it from the email address on the account, before we respond within the time the law requires. You may use an authorized agent; we may ask for proof of the agent's authority and verify your identity.
13.4 California residents
These additional disclosures apply to California residents.
Business and employment context. California's privacy law has no general business-to-business or employee exemption. If you are a California resident, the rights in this Section apply to your personal information even when you use the Services in a professional capacity.
Categories collected. In the past 12 months we have collected these CCPA categories: identifiers (name, email address, telephone number, username, IP address, device identifiers, push tokens, pseudonymous analytics identifier); customer-records information (mailing address, company, telephone number); internet or other electronic network activity (usage, engagement, file-access, and interaction data); geolocation data (approximate only, derived by Google Analytics from IP address); professional or employment-related information (company, division, role, firm, AIA membership); education information (course enrollments, attendance verification, test results, certificates, learning units); audio or visual information (instructor photographs and signature images only); and inferences limited to engagement and attendance status for continuing-education purposes. Account credentials may be sensitive personal information.
Sources, purposes, and recipients. We collect this information from the sources in Section 3, use it for the purposes in Sections 5 and 9, and disclose it for the business purposes and to the categories of recipients in Sections 6, 7, and 9.
No sale or sharing. We do not sell or share personal information for cross-context behavioral advertising, including that of consumers under 16 (see Section 8).
Sensitive personal information. We do not use or disclose it for purposes that require a right to limit.
Retention. See Section 10.
Non-discrimination and appeal. You have the right not to be treated differently for exercising your rights, and to appeal a denial by replying to our decision or emailing privacy@quakerwindows.com.
"Shine the Light." California Civil Code § 1798.83 lets California residents ask about disclosures of personal information to third parties for their direct marketing. We make no such disclosures.
Financial incentives. We offer no financial incentive in exchange for collecting, selling, or keeping personal information.
13.5 Canada: PIPEDA and Quebec Law 25
If you are in Canada, the Personal Information Protection and Electronic Documents Act (PIPEDA) and, for Quebec residents, Law 25 (An Act to modernize legislative provisions as regards the protection of personal information) give you rights over your personal information, including the right to:
access the personal information we hold about you and learn how it is used and disclosed;
correct inaccurate, incomplete, or ambiguous personal information;
withdraw consent to its collection, use, or disclosure, subject to legal or contractual limits;
receive computerized personal information you gave us in a structured, commonly used technological format, where Law 25 provides for it;
ask us to stop disseminating it or to de-index it in the circumstances Law 25 provides; and
be informed about decisions based exclusively on automated processing (see Section 15).
We obtain consent where PIPEDA and Law 25 require it and apply confidentiality by default on the website: statistics cookies stay off until you accept them, and advertising features are always off. Usage measurement in the mobile app is on by default and can be turned off in Settings › Privacy.
If a security or confidentiality incident occurs, we will give the notices the law requires. Under PIPEDA we report breaches of security safeguards that create a real risk of significant harm to the Office of the Privacy Commissioner of Canada and to affected individuals, and we keep records of all breaches. Under Law 25 we notify the Commission d'accès à l'information du Québec and affected individuals of any confidentiality incident that presents a risk of serious injury.
Quebec residents may contact our Privacy Officer (Section 19). You may also complain to the Office of the Privacy Commissioner of Canada or the Commission d'accès à l'information du Québec.
14. Children's privacy
The Services are for business users 18 or older and are not directed to children. We do not knowingly collect personal information from children under 13, or under the minimum age that applies where you live. If we learn that we have collected a child's personal information in violation of applicable law, we will delete it. If you believe a child has given us personal information, contact privacy@quakerwindows.com.
15. Automated decision-making
We do not make decisions that produce legal or similarly significant effects on you based solely on automated processing. Some features do use automated rules:
Attendance verification and testing. Whether a course is marked complete and a certificate is issued depends on automated checks of your watch time, attendance-check answers, and test score against the course's thresholds. These rules apply the AIA CES attendance standard. If you think a result is wrong, contact us and a Quaker administrator will review the underlying record.
Security and abuse prevention. Rate limits, sign-in lockouts, and suspicious-activity flags are automated. They support human oversight rather than replace it.
Account and course-access approval. Architect accounts are activated automatically once the email address is verified. Other accounts, and all architect requests for course access, are approved by Quaker personnel. A presentation event code links a request to the event you attended; it does not grant access by itself.
As rules on automated decision-making technology take effect, including under California's privacy regulations and Quebec's Law 25, we will give any additional notice, access, and opt-out rights those laws require.
16. Third-party links and services
The Services may link to, or open inside the app, websites, products, and services that we do not operate or control, including embedded forms, external product pages, and the external sites that job listings link to for applications. This Privacy Policy does not apply to them. Please read a third party's privacy notice before giving it personal information.
17. Changes to this Privacy Policy
We may update this Privacy Policy from time to time. When we do, we will change the "Last updated" date above and publish the new version in the Services. We keep every published version, along with a record of which version each user accepted. If a change is material, we will give any additional notice the law requires, which may include a notice in the Services and a prompt to review and accept the updated Policy the next time you sign in on the website or open the app. If you keep using the Services after an update takes effect, you accept the updated Policy, except where the law requires additional consent.
18. Accessibility
If you need this Policy in another format, contact privacy@quakerwindows.com.
19. Contact us
For questions about this Privacy Policy or our privacy practices, or to exercise your rights, contact:
Quaker Window Products Co. (Quaker Windows & Doors), Privacy Officer
504 Highway 63 South
Freeburg, MO 65035
United States
Email: privacy@quakerwindows.com
Support: support@quakerwindows.com
For Canadian residents, the Privacy Officer named above is responsible for our compliance with PIPEDA and Quebec Law 25, including access requests and complaints.
Last updated: October 20, 2026
