Omadata is built around provider-specific, read-only data access.
This page is for integration reviewers, platform partners, and internal product teams. The direction is provider-by-provider access with explicit consent, auditable syncs, and no general-purpose write surface for user accounts or external providers.
Provider-scoped, not open write access
Omadata is shaping its external access around provider connectors, scoped tokens, and reviewable sync paths. Public write APIs are not the default model.
Read-only by default
User consent gates access. The platform is intended to read and organize approved data, not move money or control provider activity.
Clear public contact paths
Reviewer questions, access issues, and integration feedback can be handled through the public support layer and legal documents linked below.
Procountor and related business reporting workflows.
Bank, card, and portfolio surfaces with consent-led access.
Sport, health, email, and parcel-related signal ingestion later on.