Portability Provenance and Partner Communication Research Note

Portability Provenance and Partner Communication Research Note

Portability and provenance

Portability asks whether a person can obtain and reuse data across services. Attribution asks whether the source travels with that data and how it is displayed. Ownership, access, processing permission, contractual use, privacy rights, provenance, and endorsement are separate questions.

The ICO's portability guidance is jurisdiction-specific and applies under defined conditions. It does not make every field portable everywhere. W3C PROV provides a technical vocabulary for derivation and attribution without deciding legal ownership or contract terms.

Garmin's 2025 policy demonstrates that a provider can require source attribution across screens, exports, APIs, and derived uses. Strava's current API agreement and brand guidelines show that Strava also imposes downstream conditions. A product can support user access while preserving source metadata, subject to applicable law and agreements.

Partner communication

The PRSA Code emphasizes accuracy, truth, independent counsel, fairness, disclosure, and prompt correction. In a live dispute, the company should separate confirmed operations, its own position, the other party's attributed position, allegations in public filings, and unresolved matters.

The shared customer needs continuity, required action, known impact, alternatives, support, and the next update point before a moral argument about the partner.

Audience memory matters. A statement should be checked against the company's current policies, recent enforcement, brand requirements, and prior claims. A contradiction may be explainable, but ignoring it invites the audience to supply the explanation.

Publication rule

The portability page is educational and must retain jurisdiction and contract boundaries. The communication page cannot advise disclosure of privileged or confidential material and should require counsel review for live disputes.