mirror of
https://github.com/zitadel/zitadel.git
synced 2026-08-19 01:14:48 -05:00
59f1105b04
# Which Problems Are Solved For username/email + password, "login data" seems like uncommon and confusing terminology to me. I also think "loginname" is that, maybe it should be written like "login name" or "username", but I'm having oversight with that now because it seems to be the way Zitadel calls it. Here's what Gemini has to say: > Login Credentials: This is the most widely accepted and formal term in the tech and security industry. A "credential" is an item of information that confirms an identity. The pair (username/email and password) is the set of identifiers used to authenticate the user and grant access (i.e., log in). > > Login Details: This is also very common in general use and often used interchangeably with "login credentials," especially in user-facing contexts (e.g., "Please enter your login details"). It is slightly less formal than "credentials." > > Login Data: While technically correct (as the information is data), this term is less specific and is more commonly used when referring to a larger collection of information, like a file containing many users' credentials, or the data transmitted during the login process. # How the Problems Are Solved Renames all occurrences of login data or login credentials to login details. # Additional Changes None. # Additional Context I believe this is an improvement but feel free to object. Co-authored-by: Max Peintner <max@caos.ch> Co-authored-by: Ramon <mail@conblem.me>
115 lines
2.7 KiB
React
115 lines
2.7 KiB
React
import React from "react";
|
|
|
|
export function PiiTable() {
|
|
|
|
const pii = [
|
|
{
|
|
type: "Basic data",
|
|
examples: [
|
|
'Names',
|
|
'Email addresses',
|
|
'User names'
|
|
],
|
|
subjects: "All users as uploaded by Customer."
|
|
},
|
|
{
|
|
type: "Login details",
|
|
examples: [
|
|
'Randomly generated ID',
|
|
'Passwords',
|
|
'Public keys / certificates ("FIDO2", "U2F", "x509", ...)',
|
|
'User names or identifiers of external login providers',
|
|
'Phone numbers',
|
|
],
|
|
subjects: "All users as uploaded and feature use by Customer."
|
|
},
|
|
{
|
|
type: "Profile data",
|
|
examples: [
|
|
'Profile pictures',
|
|
'Gender',
|
|
'Languages',
|
|
'Nicknames or Display names',
|
|
'Phone numbers',
|
|
'Metadata'
|
|
],
|
|
subjects: "All users as uploaded by Customer"
|
|
},
|
|
{
|
|
type: "Communication data",
|
|
examples: [
|
|
'Emails',
|
|
'Chats',
|
|
'Call metadata',
|
|
'Call recording and transcripts',
|
|
'Form submissions',
|
|
],
|
|
subjects: "Customers and users who communicate with us directly (e.g. support, chat)."
|
|
},
|
|
{
|
|
type: "Payment data",
|
|
examples: [
|
|
'Billing address',
|
|
'Payment information',
|
|
'Customer number',
|
|
'Support Customer history',
|
|
'Credit rating information',
|
|
],
|
|
subjects: "Customers who use services that require payment. Credit rating information: Only customers who pay by invoice."
|
|
},
|
|
{
|
|
type: "Analytics data",
|
|
examples: [
|
|
'Usage metrics',
|
|
'User behavior',
|
|
'User journeys (eg, Milestones)',
|
|
'Telemetry data',
|
|
'Client-side anonymized session replay',
|
|
],
|
|
subjects: "Customers who use our services."
|
|
},
|
|
{
|
|
type: "Usage metadata",
|
|
examples: [
|
|
'User agent',
|
|
'IP addresses',
|
|
'Operating system',
|
|
'Time and date',
|
|
'URL',
|
|
'Referrer URL',
|
|
'Accepted Language',
|
|
],
|
|
subjects: "All users"
|
|
},
|
|
]
|
|
|
|
return (
|
|
<table className="text-xs">
|
|
<thead>
|
|
<tr>
|
|
<th>Type of personal data</th>
|
|
<th>Examples</th>
|
|
<th>Affected data subjects</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
{
|
|
pii.map((row) => (
|
|
<tr key={row.type}>
|
|
<td>{row.type}</td>
|
|
<td>
|
|
<ul>
|
|
{row.examples.map((example) => (
|
|
<li key={example}>{example}</li>
|
|
))}
|
|
</ul>
|
|
</td>
|
|
<td>{row.subjects}</td>
|
|
</tr>
|
|
))
|
|
}
|
|
</tbody>
|
|
</table>
|
|
);
|
|
}
|