How do you classify the service functionality?
A user-to-user classification turns on functionality, not branding. Ask whether content generated, uploaded, or shared by one user may be encountered by another. Public or group posts, user profiles, uploaded media, marketplace listings, in-game chat, collaborative spaces, and messaging can meet the test. The amount of user-generated content does not matter, and a Schedule 1 exemption must be tested separately.
For search, ask whether a person can search more than one website or database. General search and vertical search for products, jobs, travel, academic material, or another topic can qualify. A tool restricted to one website or one database does not meet the section 229 search-engine definition merely because it uses filters, recommendations, or sophisticated ranking.
If one product has both functions, apply the section 3 tie-breaker. Unless its only user-generated content falls within the specified exempt types, it is treated as user-to-user. If the same provider also operates a public search engine, it is a and the search duties apply to that engine.
- Inventory every function through which a user creates, uploads, shares, searches, comments on, or encounters content.
- Record whether communications are public, group, one-to-one, live, aural, asynchronous, internal, or attached to provider content.
- For each search function, record the websites and databases searched and the entity that controls indexing, ranking, requests, and results.
- Classify distinct functions and service parts before deciding whether an exemption covers the whole product or only a defined part.
Binding definitions and tie-breaker for services that include both user-generated content and a search engine.
Binding search-engine definition, including the exclusion for a search limited to one website or database.
Official examples and explanation of user-to-user, search, vertical-search, and combined-service classification.