Procedure
Unverified entries. Entries marked Unverified are recorded from the help pages listed with each entry and have not been examined by personnel. Help pages lag behind the services they describe. The Shipped column describes possible starting settings, not confirmed current defaults. Menus differ by account type, region and app version. Check your own account before changing anything.
Choose a service. The chooser groups services by category, and each name in the list of entries on file opens that entry. Read both columns and the reason given for each suggestion. The suggestions are options, not instructions. Tick a setting once you have changed it yourself. The tick is a record only. This page cannot change any service settings.
Entries on file: listed in the register file. The register is held as services.json and can be read without JavaScript. Links to services open only when followed. No account details are sent.
Retrieving the register. If nothing appears, JavaScript may be unavailable. The register file linked above can still be read.
Settings under examination
No settings on file for this service match that pattern. Choose another pattern, or All patterns.
Sources consulted
Help pages read when the entry was recorded. Most are published by the service. Some are press reports or guides by others, used where the service's own pages said nothing. Reading them is not the same as an examination by personnel.
No sources recorded for this entry.
Records held on this device
Ticks are held in this browser under pf:defaults. A tick does not verify an entry. Export downloads the Factory Settings ticks as one JSON file. Expunge removes Factory Settings ticks only. Neither changes any service account.
Filing a new entry
Personnel may file further entries by merge request. Accepted entries are added to the register. Filing confers no priority.
Edit site/factory-settings/data/services.json in the repository and add one object to its array, in the shape below. Record three to six settings. Service ids are unique, lower case and hyphenated. Setting ids are unique within their service. Do not change an id once filed. Saved ticks depend on it.
{
"id": "service-name",
"name": "Service name",
"category": "Video and music",
"checked": null,
"sources": ["https://help.example.com/autoplay"],
"settings": [
{
"id": "autoplay",
"label": "Autoplay",
"pattern": "algorithmic-substitution",
"shipped": "The next item may start without being chosen.",
"suggested": "Turn autoplay off.",
"why": "Another item starts only when the subject chooses one.",
"path": ["Settings", "Playback", "Autoplay"],
"link": null
}
]
}Use a category already in the register where one fits. The service chooser groups entries by category, in the order they first appear in the file. List in sources each help page used, as a full HTTPS URL. Prefer the service's own help pages. New entries must give at least one source.
Use a pattern id from the canonical pattern list. Enter null where no direct settings link exists, or give a full HTTP(S) URL. A path lists each menu step in order. A single vague hint is not accepted. Do not include personal account links or details.
Leave checked as null until the entry has been examined. An examined entry carries a real date, such as 2026-10-01. In the merge request, state the region, account type and app version examined, and give evidence for each default and path. Record any uncertainty. Write the copy yourself, short and plain.
Run node --test and node scripts/check-site.js site from the repository root. Then open a merge request in the repository for inspection. Corrections to existing entries are filed the same way.