Privacy and data management

This is a development version. The operator must provide its legal identity, contact details and retention policy before opening the service to clients.

Data used by the platform

Account and workspace details, advertising performance and thumbnails, and won Odoo opportunities when connected. Facebook passwords are not required; authorization happens directly on Meta.

Separate client workspaces

The server checks workspace ownership for every request. Connection tokens and Odoo keys are encrypted on the server and are not returned to the browser.

Disconnecting and deleting data

Disconnect in Settings to remove the stored connection token. Revoke the app in Meta settings to withdraw Meta authorization. Full account deletion requires the operator in this version; self-service deletion is not yet implemented.

Support requests

Support requests are stored with your reply email. Attaching connection provider names and timestamps is optional. Credentials are never attached automatically. Email drafts open in your own email application. Scheduled daily reports use the server-side email provider configured by the operator.

Current limitations

WordPress, AI provider, and report schedule connections are stored per workspace. The operator must configure retention, deletion, email delivery, and provider requirements before client launch.