Connectors Hub vs Personal Data Sovereignty Hub

Connectors Hub and Personal Data Sovereignty Hub are related but separate.

Connectors Hub

Connectors Hub answers:

• Which external tools can Prox OS connect?
• Which objects can each provider expose?
• Which scopes are needed?
• Which fields can be mapped?
• Which sync jobs are healthy?
• Which dashboard-ready views can be created?
• Which write-back operations are risky?

Connectors Hub focuses on integration, schema, sync, and dashboard preparation.

Personal Data Sovereignty Hub

Personal Data Sovereignty Hub answers:

• Who owns the data?
• How can the user export it?
• How can the user delete, back up, migrate, or archive it?
• Which permissions were granted?
• Which apps and AI contexts can read it?
• Which lifecycle and privacy rules apply?
• Which audit trail proves what happened?

Personal Data Sovereignty Hub focuses on ownership, privacy, portability, lifecycle, consent, backups, audit, and governance.

Product Rule

Connectors Hub must not swallow Personal Data Sovereignty Hub. A connector can show source state, sync state, scopes, schema drift, and dashboard readiness. Long-term ownership, export, retention, privacy, and legal governance belong to Personal Data Sovereignty Hub and related permission surfaces.