Topaz decides what information is reasonably necessary to collect
What Personal Information Topaz collects varies with the Services used and its interactions with people. The text says the company reserves the right to decide what information is reasonably necessary for the operation, security and improvement of the Services, subject to applicable law.
Supporting quotations
Paz reserves the right to determine what information is reasonably necessary for the operation, security, and improvement of the Services, subject to applicable law
Qualifications & exceptions
"subject to applicable law".
Not stated here
The name "Paz" appears here where the policy otherwise says "Topaz"; the text does not say whether it means Topaz.
Data Access & Collection · Company practice
Topaz may collect the listed categories, subject to legal requirements
Section 2.1 introduces a list of categories of Personal Information Topaz may collect. The list is framed as what Topaz "may" collect and the collected information "may differ depending on the circumstances", subject to applicable legal requirements and restrictions.
Supporting quotations
we may collect the following categories of Personal Information (subject to applicable legal requirements and restrictions)
Qualifications & exceptions
"may" collect, depending on circumstances; "subject to applicable legal requirements and restrictions".
Data Access & Collection · Company practice
Name, email, account and licensing details are collected
The listed categories include identifiers such as name and email address, and account and profile data such as license tier, subscription plan, seat assignments and other account settings.
Supporting quotations
identifiers such as name and email address
information such as your license tier, subscription plan, seat assignments, and other account settings
Data Access & Collection · Company practice
Device information such as IP address, browser, operating system and device identifiers is collected
The listed categories include device information: IP address, web browser type, operating system version, phone carrier and manufacturer, application installations and device identifiers.
Supporting quotations
Internet protocol (IP) address, web browser type, operating system version, phone carrier and manufacturer, application installations, device identifiers
The listed categories include communications, described only as "direct communications".
Supporting quotations
Communications: direct communications
Not stated here
The policy gives no further detail on which communications are meant beyond the phrase "direct communications".
Data Access & Collection · Company practice
Usage, billing and licensing data, including images processed and API calls, is collected
The listed categories include internet or other electronic network activity information, including how you interact with the Services: number of images or frames processed, API calls made, timestamps, license keys, subscription status and other metrics needed to calculate fees and validate licenses. The words "including but not limited to" show the list is not complete.
Supporting quotations
including, but not limited to, information regarding a consumer’s interaction with the Services, such as the number of images or frames processed, API calls made, timestamps, license keys, subscription status, and other metrics required to calculate fees and validate licenses
General location information, such as a region inferred from your IP address, is collected
The listed categories include general location information; the policy's example is that your IP address may indicate your more general geographic region.
Supporting quotations
general location information (for example, your IP address may indicate your more general geographic region)
Qualifications & exceptions
Described as "general" location, with an IP-address example.
Audio, video and other electronic data and media are collected
The listed categories include audio, electronic, visual or similar information and media. This block does not say which uses or retention apply to it; other sections cover media content storage and AI training.
Supporting quotations
audio, electronic, visual, or similar information and media
Not stated here
This category does not say whether it means the content you submit to the Services or something else.
Data Access & Collection · Company practice
Information comes directly from you and automatically from your use of the Services
Topaz says it may collect Personal Information directly from you, such as when you make a purchase or contact support, and from your use of the Services, including information collected automatically from the Software, Web Applications, APIs or On-Premise Deployments. That second source also includes information Topaz derives about your preferences or interests from the information it collects and its interactions with you.
Supporting quotations
Directly from you: such as when you make a purchase or contact us for support purposes
including information we collect automatically when you use our Software, Web Applications, APIs, or On-Premise Deployments
information we derive about you and your preferences or interests
Qualifications & exceptions
"may" collect; the examples for direct collection are purchases and support contacts.
Data Access & Collection · Company practice
Topaz keeps a record of your emails and support contacts and may not respond if they lack identifying information
When you email or otherwise contact Topaz, it collects and maintains a record of your contact details, your communications and its responses. Topaz may decline to respond to inquiries or support requests that lack enough identifying or contextual information, and you acknowledge that information you voluntarily provide in those communications may be used consistent with the policy.
Supporting quotations
we collect and maintain a record of your contact details, communications, and our responses
Topaz may decline to respond to inquiries or support requests that do not contain sufficient identifying or contextual information
any information voluntarily provided in such communications may be used consistent with this Policy
Qualifications & exceptions
Topaz "may decline to respond" where an inquiry lacks "sufficient identifying or contextual information".
Not stated here
The policy does not say how long communication records are kept.
Data Access & Collection · Company practice
Locally run On-Premise Deployments and the CLI may be required to send usage, billing and licensing data to Topaz
Services that run on your own hardware, such as On-Premise Deployments and the Command Line Interface (CLI), may be required to transmit Usage, Billing and Licensing Data to Topaz over the internet from time to time. Topaz says this is necessary, "without limitation", to provide the Services, ensure billing accuracy, validate licenses and verify compliance with the EULA. By using them you expressly consent to the transmissions, and you agree that not permitting them may lead to suspension, throttling or termination of the Services.
Supporting quotations
certain Services which run on your local hardware, such as On-Premise Deployments and the Command Line Interface (CLI), may be required to periodically transmit Usage, Billing, and Licensing Data to Topaz over the internet
to provide the Services, ensure billing accuracy, validate licenses, and verify compliance with the End User License Agreement (EULA)
you expressly consent to such transmissions, and you agree that failure to permit such transmissions may result in suspension, throttling, or termination of the Services
Qualifications & exceptions
Stated for Services that run on local hardware, with On-Premise Deployments and the CLI as examples.
Transmission is "periodic"; the reasons are introduced with "without limitation".
Not stated here
The policy does not say how often the data is sent or which data fields beyond "Usage, Billing, and Licensing Data" are included.
Topaz and its service providers may use cookies, pixels, SDKs and similar tracking technologies
Topaz and its service providers may use cookies, log files, pixels, SDKs and similar tracking technologies to operate, analyze, secure and improve the Services, and for fraud prevention and compliance. You may disable cookies through your browser or device settings, but some features may then not work properly.
Supporting quotations
Topaz and its service providers may use cookies, log files, pixels, SDKs, and similar tracking technologies to operate, analyze, secure, and improve the Services, as well as for fraud prevention and compliance
You may disable cookies through your browser or device settings; however, certain features of the Services may not function properly if cookies are disabled
Qualifications & exceptions
The choice described is disabling cookies; the text offers no choice for other tracking technologies such as pixels or SDKs.
Not stated here
The policy does not name the cookies or tracking tools used.
Data Access & Collection · Company commitment
No facial recognition or biometric processing unless you explicitly opt in to improve AI models
Topaz says it does not collect, store, retain, transmit or otherwise process facial recognition data or biometric identifiers unless a user explicitly opts in to provide images for the purpose of improving its AI models. The opt-in must be through a clear, affirmative mechanism within the Services.
Supporting quotations
Topaz Labs does not collect, store, retain, transmit, or otherwise process facial recognition data or biometric identifiers unless a user explicitly opts in to provide images for the purpose of improving our AI models
Such opt-in must occur through a clear, affirmative mechanism within the Services
Qualifications & exceptions
Exception: an explicit opt-in to provide images for improving AI models.
The opt-in must be a "clear, affirmative mechanism within the Services".
Not stated here
The policy does not describe the opt-in mechanism or where in the Services it appears.
Cross-references
contrast (model-proposed): No AI training on your media without prior consent, but derived de-identified, aggregated or synthetic data may be used — The facial-information section describes an explicit, affirmative opt-in for improving AI models, while the AI model training section describes prior consent "which shall not be unreasonably withheld" and a separate allowance for derived data. The wording of the two consent standards differs and the policy does not reconcile them.
contrast (model-proposed): California: a table summarises handling by category; Topaz says it does not collect Sensitive Personal Information — The California section says Topaz does not collect Sensitive Personal Information, while the facial-information section describes biometric identifiers and facial recognition data that Topaz may process if a user opts in. The policy does not define Sensitive Personal Information, so it does not say whether the two overlap.
Services are not for children under 13; Topaz deletes information it learns it holds about them, as the law requires
The Services do not address anyone under 13, and Topaz says it does not knowingly collect or maintain Personal Information from children it actually knows are under 13 at collection. If it discovers it has collected such information online, it will promptly delete it to the extent required by applicable law. You can contact Topaz with concerns about children's information.
Supporting quotations
we do not knowingly collect or maintain Personal Information from children we actually know at the time of collection are under the age of 13
we will promptly delete that Personal Information to the extent required by applicable law
Qualifications & exceptions
Applies to children Topaz "actually know[s]" are under 13.
Deletion is "to the extent required by applicable law".
California table: for each category, sources, purposes, and the recipients to which Topaz provides the information
The California table has four columns: the category of Personal Information, the categories of sources from which it was collected, the business or commercial purpose for collecting and providing it, and the categories of third parties and other entities to which Topaz provides it. The table is a summary and the rows below should be read with the collection, use and disclosure sections. The table has seven category rows, and has no separate row for account and profile data or for billing and licensing data, which section 2.1 lists; the policy does not explain why.
Supporting quotations
PERSONAL
INFORMATION WAS COLLECTED
CATEGORY OF PERSONAL INFORMATION
PERSONAL INFORMATION
Qualifications & exceptions
The table is described as a summary of general practices, not a complete statement.
Not stated here
The policy does not say why the table has no row for account and profile data, or for billing and licensing data, which the collection section lists.
Data Access & Collection · Company practice
California table: identifiers and device information come from you and from third-party suppliers and partners
For the name, contact information and other identifiers row, and the device information row, the table lists the sources as directly from the user and from third-party data suppliers and business partners. The purposes listed are to provide and improve the Software, communicate with the user, analyze and improve the business, secure and protect the business, defend the company's legal rights, auditing, reporting, corporate governance and internal operations, comply with legal obligations, and legitimate business interests. These are the only two rows that list third-party sources.
Supporting quotations
Name, Contact Information, and other Identifiers
From third-party data suppliers and business partners
To defend the company’s legal rights
For legitimate business interests
Device Information
From third-party data suppliers and business partners
governance and internal operations
To comply with legal obligations
For legitimate business interests
phone carrier and manufacturer
Qualifications & exceptions
Only these two rows name third-party data suppliers and business partners as a source.
Not stated here
The table does not name the third-party suppliers or business partners.
California table: communications, usage and geolocation data are listed as coming directly from the user
For the communications, usage data and geolocation data rows, the table lists the source as directly from the user, with the same list of purposes as the other rows. The usage data row is described as interaction with the Software and time spent, rather than the images processed, API calls, license keys and fees described in the collection section. The geolocation row repeats that location may be indicated by your IP address.
Supporting quotations
Communications: direct communications
Directly from the user
Usage data
the time spent on the Software and other statistics
For legitimate business interests
Geolocation Data
Directly from the user
license keys, subscription status, and other metrics required to calculate fees and validate licenses
general location information
Qualifications & exceptions
The table says "Directly from the user" for these rows, while the collection section says some usage information is collected automatically.
Not stated here
The table's usage row does not mention billing or licensing data, which the collection section lists with usage data.
California table: audio, video and other electronic data, including photographs and recordings, is from the user
For the audio, video and other electronic data row, the table gives photographs and audiovisual recordings as examples, lists the source as directly from the user, and gives the same purposes and recipients as the other rows.
Supporting quotations
Audio, Video, and other Electronic Data
photographs and audiovisual recordings
Directly from the user
Data Access & Collection · Company commitment
California: a table summarises handling by category; Topaz says it does not collect Sensitive Personal Information
The policy says the CCPA requires specific disclosures for each category of Personal Information collected and that the table below summarises Topaz's general data handling practices, which are more fully described in Sections 2, 3 and 4 of the policy. Topaz also states that it does not collect Sensitive Personal Information. The policy does not define that term, and the table header names four columns: category, sources, purposes for collecting and providing the category, and categories of third parties and other entities to which Personal Information is provided.
Supporting quotations
The table below summarizes our general data handling practices which are more fully described in Sections 2, 3, and 4 of this Policy
We do not collect Sensitive Personal Information
The CCPA requires specific disclosures for each category of Personal Information that we collect
CATEGORIES OF SOURCES FROM
Qualifications & exceptions
The table is described as a summary of "general data handling practices".
The statement on Sensitive Personal Information appears in the California section.
Not stated here
The policy does not define "Sensitive Personal Information", so it does not say whether face images, which the facial-information section addresses, count.
The section headings in this text carry no visible numbers, so "Sections 2, 3, and 4" is read from the numbered sub-items 2.1, 3A and 4A and the order of the headings (collection, use, disclosure); the policy does not state the mapping.
Cross-references
contrast (model-proposed): No facial recognition or biometric processing unless you explicitly opt in to improve AI models — The California section says Topaz does not collect Sensitive Personal Information, while the facial-information section describes biometric identifiers and facial recognition data that Topaz may process if a user opts in. The policy does not define Sensitive Personal Information, so it does not say whether the two overlap.