Last updated: September 22, 2026. This operational policy requires final owner/legal approval before broad commercial launch.
Information processed
We process account identifiers, workspace content, contact enquiries and connection metadata needed to provide the service. OAuth credentials and tokens are handled server-side.
How information is used
Information is used to authenticate users, operate workspaces, manage requested social connections, schedule content and respond to enquiries.
Service providers
The current application uses Vercel for hosting and Firebase for authentication and database services. Social providers process data when a user explicitly connects an account.
Retention and deletion
Retention periods and formal deletion-request procedures must be approved by the product owner before commercial launch. Contact the product team through the contact page for current requests.
Security
Secrets are kept server-side, provider tokens are encrypted at rest by the application, and database rules deny unspecified client access.
Changes
Material updates will be reflected on this page with a revised date.