Privacy by design

A privacy setting can only govern choices the system has already made possible. Earlier decisions determine which information exists, whether it is centralised, how it moves and which suppliers can touch it.

Portal Page intends to make privacy questions part of product discovery and technical design. Each information type should have a stated purpose, an accountable owner, an audience and a lifecycle. Where a less identifying approach meets the purpose, it should be preferred.

This is a direction that must be carried into engineering practice, customer configuration and contracts. A public principle is useful because it creates a standard; evidence comes from the implemented system.

Data minimisation is not a demand for a featureless product. It is a demand for relevance. A portal may need identity, membership and activity information to operate a private community, but each field should earn its place.

Purpose limitation prevents a reasonable collection from becoming a blank cheque for unrelated use. Information supplied to join a community should not quietly become advertising material. Content contributed to a private group should not automatically become artificial intelligence training data.

Retention closes the loop. Portal Page and its customers should distinguish operational history, required records, dormant information and material that no longer serves the community purpose.

• Ask only for necessary profile information
• Use role-based access rather than broad administrator visibility
• Set retention according to purpose and obligation
• Challenge new integrations and secondary uses

People cannot exercise meaningful choice when language is vague, options are hidden or declining causes unexplained disadvantage. Privacy controls, profile visibility, notifications and community departure should use direct language.

Administrators also make privacy decisions. Configuration should show the practical effect of audience, role and integration changes. Good defaults reduce risk, but important choices still need context and review.

Accessibility matters here: a privacy control that cannot be used with a keyboard, assistive technology or plain language is not a meaningful control for everyone.

Communities change. New groups form, integrations are proposed and old purposes fade. Privacy review should accompany material change rather than rely forever on the launch assessment.

Organisations should provide routes for questions and complaints, record consequential decisions and test assumptions with the people affected. Portal Page should communicate material service changes clearly and maintain accurate information about processors and data practices.

Read the full Portal Page principles, data ownership approach and draft privacy notice for the surrounding framework. Professional privacy and legal review is required before production launch.