Data stored
Sonar may store account information, authentication state, subscription references, settings, contact records, campaign data, campaign leads, notes, reply status, send history, and mailbox connection settings.
A production-ready structure placeholder that should be reviewed before launch.
Sonar may store account information, authentication state, subscription references, settings, contact records, campaign data, campaign leads, notes, reply status, send history, and mailbox connection settings.
Uploaded contacts belong to the user account that imported them. Campaign activity should not overwrite the master contact database.
Mailbox credentials should be used only for mailbox testing, campaign sending, and reply fetching.
Plan status and provider references may be stored locally while payment processing is handled by the payment provider.
Retention and deletion rules should be finalized before production launch.