Closed Beta
Privacy Policy
This privacy notice applies to the MarketingOS AI Closed Beta and describes the principal categories of information handled by the service.
1. Service identity
MarketingOS AI is the service name used for this Closed Beta.
This notice describes how the service handles information during the Closed Beta. It does not invent or assert a legal entity name, postal address, or other operator information that has not yet been formally published.
2. Information we collect
We may process account and authentication information, workspace and brand information, content and prompts you submit, generated content, usage records, publication records, connected social-account information, audit records, and technical information required to operate and secure the service.
We may also process identifiers and authorization information provided through integrations that you choose to connect.
3. Why we process information
We use information to authenticate users, provide workspace features, generate and manage content, operate publication workflows, measure usage, enforce plan or credit limits, secure the service, investigate failures, and improve reliability.
4. AI and service providers
Content-generation requests may be processed by configured third-party AI or infrastructure providers where required to provide the requested feature.
We limit the information sent to a provider to information required for the relevant service function and our configured integration.
5. Meta and Facebook integrations
If you choose to connect a Meta or Facebook account or Page, the service may process identifiers, permissions, authorization information, Page information, publication state, and related records required to provide the integration.
Connecting a social account is optional. Publication operations remain subject to the service's authorization and safety controls.
6. Cookies and session data
The service uses session and authentication mechanisms needed to keep users signed in and to protect authenticated requests.
Security-related cookie and session settings are used as part of the application's authentication boundary.
7. Usage, credit, and billing-related data
The service may record feature usage, AI usage, token or processing usage, credit consumption, and related operational records required to display usage and enforce service limits.
8. Data retention
Information is retained only for as long as reasonably necessary for the service purpose, security, audit, dispute handling, or applicable legal obligations.
A fixed retention duration is not stated in this Closed Beta notice because no repository-supported fixed duration has been established for all data categories.
9. Security
We use application and operational safeguards designed to protect authentication, workspace isolation, credentials, publication workflows, and service data.
No online service can guarantee absolute security. Closed Beta participants should not submit information that is unnecessary for testing the service.
10. Your choices and rights
You may choose whether to connect optional third-party integrations and may stop using the service at any time.
Requests concerning access, correction, deletion, or other applicable data rights can be raised through the support channel provided with the service or Closed Beta invitation.
11. Account and data deletion
Where an account-deletion or data-deletion flow is available, you may use that flow. You may also request deletion through the support channel provided with your account or Closed Beta invitation.
Deletion requests may be subject to information that must be retained temporarily for security, audit, dispute handling, or applicable legal obligations.
12. Third-party services
Optional integrations and infrastructure providers may process information under their own terms and privacy practices.
You should review the privacy information of any third-party service you choose to connect.
13. Changes to this notice
This notice may be updated as the Closed Beta evolves, new integrations are introduced, or the service prepares for broader public availability.
Material changes should be reflected on this page before they take effect for broader public use.
14. Contact
Closed Beta participants should use the support or contact channel provided with their account, service interface, or Beta invitation.
Additional formally published operator and contact information will be added before broader public release where required.