Privacy follows the customer-controlled architecture.

Effective date: This version takes effect when it is published to production at ccos.axiward.com.

1. Scope and responsible party

This policy applies to the C.C.O.S. product website, product support, and standalone C.C.O.S. software. C.C.O.S. is a product of Axiward Technologies, which is the public business and privacy-controller identity for these services.

Privacy and deletion requests may be sent to privacy@axiward.com.

2. Eligibility

C.C.O.S. is intended only for people who are at least 18 years old and legally capable of entering a binding agreement.

3. Information involved

Customers may provide objectives, brand and audience configuration, generated content, model-provider settings, platform connection settings, account or channel identifiers, and support messages. The local runtime may create workflow state, artifacts, package manifests, logs, and diagnostics. OAuth connections may involve authorization codes, access and refresh tokens, granted scopes, expiry data, and the authorized platform account identifier.

4. Where data is processed

C.C.O.S. is designed to run in the customer's environment. Runtime state and encrypted workspace connection records are stored locally under customer-controlled private directories. Model requests and authorized platform operations send the information required for that operation to the provider configured by the customer. The public pages are static and contain no customer account system, analytics, or advertising tracker. A dedicated server-side TikTok OAuth Worker at the /oauth/ boundary validates authorization state, exchanges authorization codes, and stores encrypted TikTok connection records needed for the customer-initiated connection handoff. Its hosting and storage providers may process ordinary request metadata and the minimum encrypted OAuth records needed to serve and secure that flow.

5. How information is used

Information is used to operate requested C.C.O.S. features, generate and validate deliverables, maintain recovery state, connect an authorized account, verify scopes and account identity, execute an explicitly approved platform operation, investigate support requests, and protect the product and its users.

6. Google API data and Limited Use

The qualified YouTube integration requests permission to view the authenticated YouTube account and manage video uploads. It uses Google user data to identify and bind the authorized YouTube channel, maintain workspace-scoped OAuth credentials, refresh access when authorized, construct the publishing client, and perform a customer-approved YouTube operation. Google credentials are stored in the encrypted local workspace connection vault. The qualified implementation does not use Google user data for advertising, sell it, or use it to train a generalized AI or machine-learning model. Use and transfer of information received from Google APIs is limited to providing or improving user-facing C.C.O.S. features and will comply with the Google API Services User Data Policy, including the Limited Use requirements.

7. Meta and other connected-platform data

The qualified connection boundary uses provider data only for authorization, granted-scope checks, token lifecycle, account identity binding, publishing-client construction where supported, and an operation the customer separately approves. For Instagram, the runtime exchanges and refreshes long-lived credentials and requests provider-side permission removal during disconnect; it removes the local record only after the provider confirms revocation. Connected platforms receive the data required for requests made to their APIs and process it under their own terms and privacy policies. Connection support does not imply provider endorsement or production approval.

8. Credentials and security

Workspace connection records are encrypted at rest with a customer-held key and restrictive filesystem permissions. OAuth state, callback, workspace, session, scope, and account-identity checks are enforced where applicable. Browser responses and customer-facing status data omit credentials. Customers remain responsible for securing their environment, encryption keys, provider client files, credentials, devices, and backups. Security reports may be sent to security@axiward.com. No system can be guaranteed completely secure.

9. Support and disclosure

Information voluntarily sent to support@axiward.com, privacy@axiward.com, security@axiward.com, or legal@axiward.com is used to respond to the request and protect legitimate legal and security interests. Customers should not send passwords, OAuth tokens, client secrets, private callback URLs, or unnecessary customer content by email.

10. Retention and customer control

Customer-local data remains under the customer's control until the customer deletes it, subject to backups and third-party provider practices. Disconnecting a provider removes local credentials according to the implemented lifecycle and attempts remote revocation where supported. Axiward Technologies retains support, privacy, security, and legal correspondence only as long as reasonably necessary for the purpose collected, security, dispute resolution, legal obligations, and recordkeeping. Verified deletion requests are handled within the time required by applicable law.

11. Additional rights and changes

Additional privacy rights may apply based on a person's jurisdiction and will be honored where legally required. Material changes will be published on this page and take effect on the stated publication date.