1. About this policy
Voycerizer is a software service designed to connect conversational assistants with scheduling and social-media publishing capabilities. This draft covers the Voycerizer website and connected publishing service. It should be replaced by a finalized, dated policy before launch.
2. Information the service may process
To provide requested capabilities, Voycerizer may process:
- Account information, such as email address, account identifier and sign-in metadata.
- Connected-platform identifiers and the permissions granted through OAuth.
- Publishing instructions, captions, media files, destination choices, schedules, and publication receipts.
- Operational records necessary to troubleshoot, prevent abuse, secure sessions, and support requests.
- Billing records when paid publishing is enabled; payment-processing details may be managed by a payment provider.
3. How information is used
Information is intended to be used to authenticate users, connect approved accounts, validate and execute instructions, schedule and reconcile publishing activity, provide support, and protect the reliability of the service. Voycerizer should not publish without the authorization required for that action.
4. Social accounts and third parties
Connecting a social platform redirects you to that platform's own authorization flow. Voycerizer's design does not require users to provide their social-media passwords to the chat interface. Authorized API calls are made subject to the platform's permissions and policies. If you connect through an LLM host, information you provide to that host is also subject to that host's privacy practices.
5. Storage and security
The production design calls for provider credentials and refresh tokens to remain in access-restricted server-side storage rather than in public webpages or model-visible responses. Media, schedules, and receipts may be held in service storage to deliver requested functionality. Specific storage vendors, retention periods, access controls, backups, and cross-border transfer details must be verified and disclosed before this draft becomes effective.
6. Your choices
Users should be able to disconnect linked accounts and revoke access at the social platform. A privacy request process for accessing, correcting, or deleting eligible data will be established before public onboarding. Disconnecting an integration may not remove already-published content from the destination platform.
7. Retention
Retention will depend on the data category and technical, contractual, and legal requirements. No fixed retention duration is claimed in this draft; the final policy must provide accurate periods or criteria.
8. Children
Voycerizer is not designed as a service directed to children. Minimum-age requirements will follow applicable law and connected platforms' rules.
9. Changes and contact
The effective date, operating legal entity, monitored privacy contact, and available regional rights will be inserted after the deployment and legal review. See the contact page for the required launch preparation items.