Account profile fields
What the person typed when signing up: name, email, phone, address, birthday and more.
In one line
Can keep the details you typed when signing up, such as name, email and address
What the person typed when signing up: name, email, phone, address, birthday and more.
Once signed in, every action ties to a stored identity. The site holds the typed fields plus order, device and login history. Email and phone are the keys ad platforms and data brokers use to match the person across services.
What it can and can't do
What the user does: You fill in a sign up or checkout form and tap Create account.
It can
- Keep the name, email, phone, address or birthday you typed
- Show them back to you and use them for mail, shipping or billing
- Combine them with what you do on the site
It cannot
- See details you did not enter
- Check that what you typed is true, unless it verifies it
- See your browser's saved addresses and cards until you choose to autofill
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | :Form fields work everywhere |
| Edge | Supported | 1 | Not listed | :Form fields work everywhere |
| Firefox | Supported | 1 | 2004-11-09 | :Form fields work everywhere |
| Safari | Supported | 1 | 2003-06-23 | :Form fields work everywhere |
| Safari on iPhone | Supported | 1 | 2007-06-29 | :Form fields work everywhere |
| Chrome on Android | Supported | 1 | Not listed | :Form fields work everywhere |
| Samsung Internet | Supported | 1 | 2013-04-27 | :Form fields work everywhere |
How a site asks for it
| API | HTML forms with autocomplete tokens; server database |
| How access is granted | gesture |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Kept for the life of the account and usually for months after deletion for legal reasons |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Typical flow
- Person fills sign-up form or picks autofill
- Server stores fields
- Later logins attach activity to that record
Data you get
What comes back: Name, email, phone, address, birthday
Shape: object
How often: at sign-up and edits
No individual data fields. The signal is the access itself.
Technical limits
- Only what the person enters or autofills
- Browser autofill fills fields only after the person picks an entry
- Laws such as GDPR and CCPA add access and delete rights
The story
What it is
What you typed when you signed up: name, email, phone, address, birthday and more.
For you
You see forms asking for your name, email and more, often with an autofill suggestion. The more you share, the more the site can tailor and remember.
For makers
Profile fields are the basis for personal service, marketing and fraud checks. Makers want accurate data, but each extra field lowers sign ups. Many also buy or match this data for ads.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | A store uses your name, address and birthday to prefill checkout and send a birthday offer. | Amazon |
| social | A social site uses your birthday and city to suggest friends and show age limited content. | |
| dating | A dating app uses your age, gender and city to match you. | None named |
| games | A browser game uses your username and birth year to set chat and spending limits. | None named |
| banking | A bank checks your name, address and birth date during sign up to confirm identity. | None named |
| ads | An advertiser matches a hashed email to build an ad audience of your type. | Meta, Google Ads |
| kids | A kids site asks a parent for an email to give consent, based on the age given. | None named |
Risks
- Data sold or matched
- Identity theft if leaked
What the platform says
- MDN: autocomplete attribute. Documents how browsers fill account and address fields so people type less.
- web.dev: Sign in form best practices. Google teaches sites to make sign up and sign in simple, using autofill and clear fields.
Good uses and abuse
Legitimate uses
- Accounts, delivery, support
Known abuse
- Resale or ad matching using email and phone
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 5 of 5 | How useful it is to honest apps |
| Friction | 1 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2018-05, all: GDPR in force: access, deletion and portability rights
- 2020-01, all: CCPA in force in California
Related capabilities
Related
- Hashed email as identity. Can recognize you across sites by a scrambled version of your email
- Cross device identity linking. Can recognize you as one person across your phone, laptop and tablet when you sign in
Sources
How well checked: Based on official documentation.