Privacy notice

Prepared 9 September 2026 for the private pilot. This draft must be reviewed before public launch.

Information used

With account-owner authorization, AiAutoSM requests permitted social profile information, account identifiers, public video or post metadata, and available performance metrics. It stores authorization tokens to access connected services. The current local implementation encrypts social authorization tokens; developer credentials are stored in local server configuration.

Purpose

Data is used to display connected accounts, synchronize owned content, analyze engagement, and inform content strategy and draft generation. Connected-account access does not itself authorize publishing or advertising expenditure.

AI processing

When an AI planning workflow runs, selected content summaries and performance evidence may be sent to the AI provider configured for that workflow. Provider selection and production data-handling arrangements must be finalized before onboarding external customers.

Storage and retention

The current pilot stores data on the operator's local computer. No automatic retention or deletion schedule is implemented yet. Before public release, the operator must define a retention schedule and test deletion of tokens, imported posts, derived memories and backups.

Access and deletion requests

You may revoke AiAutoSM access in the relevant social platform's settings. Revocation prevents future authorized access but does not automatically erase previously imported information. Contact gerakanputra@gmail.com to request access, correction or deletion. Requests during the private pilot require manual handling.

Before publication

The responsible operator's legal identity, applicable contact details, hosting location, retention periods and customer-facing rights process remain to be confirmed.