Clistr Studio

Privacy Policy

This policy explains what Clistr Studio collects, why it is used, how connected social-platform data is handled, and the choices available to creators.

Last updated: 27 September 2026

1. Information we process

Clistr Studio may process account and profile information, creator preferences, projects, prompts, uploaded media, generated content, publishing settings, usage records and technical/security information needed to operate the service.

Authentication is separate from social-platform connections. You may sign in using a supported identity provider or a registered passkey. Clistr Studio minimises authentication data and does not retain provider profile photos for account authentication. A passkey stores a public credential and related security metadata; the private key remains with your device or passkey provider.

When you connect a supported social platform, we process only the data and permissions you authorise. Depending on the platform and permissions granted, this may include account identifiers, profile information, posts or videos, captions, publishing status, performance metrics, audience or engagement insights, and access tokens required to maintain the connection.

2. How we use information

We use information to provide and secure Clistr Studio; analyse the performance of your content; develop Clistr Studio signals from eligible non-YouTube sources; identify content opportunities and market patterns; recommend topics, formats, hooks and experiments; create and edit content; publish or schedule content when you instruct us to do so; and improve product reliability.

Clistr Studio may combine eligible non-YouTube authorised performance data with permitted public or market-level signals to recommend what you could create next. YouTube API data is kept separate from those Clistr Studio personalisation calculations and cross-platform recommendation signals. We do not claim ownership of your connected social accounts or content.

3. YouTube API Services

Clistr Studio uses YouTube API Services. When you connect YouTube, the information Clistr Studio may access and store depends on the permissions you grant and can include your YouTube channel identifier and profile information, upload/video metadata, titles and descriptions, thumbnails, privacy status, video performance and YouTube Analytics data, publishing status, and OAuth access or refresh tokens needed to maintain the authorised connection.

We use authorised YouTube data to show the connected channel, provide user-facing YouTube reporting, display authorised channel/video performance, attribute YouTube performance to the creator's own published content for reporting, and upload or schedule videos only when the creator expressly instructs Clistr Studio to do so. Clistr Studio does not use YouTube API data to train Clistr Studio, calculate personalisation scores, rank Clistr Studio topics or hooks, generate opportunity/trend scores, or merge YouTube API data into cross-platform derived metrics.

Your use of YouTube through Clistr Studio is also subject to the YouTube Terms of Service. Google's handling of information is described in the Google Privacy Policy.

You can revoke Clistr Studio's Google/YouTube access from Clistr Studio's Connections area, through your Google Account permissions, or through Google's third-party access security settings. Disconnecting YouTube in Clistr Studio attempts to revoke the Google OAuth token and deletes the connected YouTube account record, imported YouTube videos and analytics, and other locally stored authorised YouTube data associated with that connection.

If Google/YouTube authorization is revoked or becomes definitively invalid outside Clistr Studio, authenticated collection stops and Clistr Studio deletes the locally stored authorised YouTube data associated with that connection when the revocation is detected, as soon as practicable and no later than seven calendar days after revocation.

Clistr Studio checks connected YouTube authorisation and refreshes current YouTube channel, video metadata and authorised analytics automatically in the background, normally every six hours. Stored non-statistical YouTube API metadata is refreshed or deleted before it reaches 30 days old. If authorisation is revoked or becomes invalid, authenticated collection stops and the associated locally stored authorised YouTube data is deleted as described above.

For questions about Clistr Studio's use of YouTube API Services, YouTube data, privacy, revocation or deletion, contact creatorsdna.support@gmail.com.

4. Other social-platform connections

Connections to services such as Instagram, Facebook and TikTok are governed by the permissions you approve and by those platforms' own terms and privacy policies. You can disconnect a supported social account from Clistr Studio. Disconnecting stops future authenticated access and removes the active connection.

Instagram performance history is not used for Clistr Studio personalisation merely because an Instagram account is connected. The creator must explicitly enable the personalisation control for that Instagram account. When enabled, authorised Instagram history is used only to personalise that creator's own Clistr Studio recommendations and is not pooled with another creator's Instagram history to train a shared creator profile or improve another creator's recommendations.

The creator may turn Instagram personalisation off at any time. Turning it off removes Instagram-derived signals from the active personalised learning profile while leaving the authorised Instagram connection available for account-level viewing and syncing. Disconnecting Instagram removes the connection and its imported account data, and Clistr Studio is rebuilt without that Instagram account's signals.

Access tokens are stored server-side and protected using encryption. We do not expose platform secrets or creator access tokens in the browser where they are not required.

5. Sharing and service providers

We may use infrastructure, storage, database, AI, media-processing, analytics, payment and delivery providers to operate Clistr Studio. They receive information only as needed to perform services for us. We do not sell creator account data to advertisers.

6. Retention

We retain information for as long as reasonably needed to provide the service, maintain security, meet legal or accounting obligations, resolve disputes, or preserve non-platform operational records. Connected-platform data is also subject to the retention and deletion requirements imposed by the relevant platform, including the YouTube requirements described above.

7. Your choices and rights

You can disconnect supported social accounts, remove registered passkeys, remove content where product controls allow, and request deletion of Clistr Studio account data. Depending on where you live, you may also have rights to access, correct, restrict, object to, port or erase personal information.

See the Data Deletion Instructions for the available deletion process.

8. Security

We use technical and organisational safeguards designed to protect data, including encrypted secret storage, authenticated access controls, passkey public-key authentication and separation of creator accounts. Passkey private keys are not stored by Clistr Studio. No internet service can guarantee absolute security.

9. International processing

Clistr Studio and its service providers may process information in countries other than the country where you live. Where required, appropriate safeguards are used for international transfers.

10. Children

Clistr Studio is not intended for children who do not meet the minimum age required by applicable law and the connected social platforms. YouTube publishing includes an audience control so creators can identify whether an uploaded video is made for kids.

11. Changes and contact

We may update this policy as the product, connected platforms or legal requirements change. The current version will be published at this URL.

Privacy questions, data requests and YouTube API data enquiries can be sent to creatorsdna.support@gmail.com.