Privacy Policy
Last updated: September 2026
This Privacy Policy explains how Klyfton collects, uses, shares, retains and protects your personal data when you use our website or platform, including when you connect Google and YouTube.
1. Who we are
Klyfton OS Ltd ("Klyfton", "we", "us") operates this website and the Klyfton platform. We are the data controller responsible for your personal data.
If you have any questions about this policy, you can contact us at privacy@klyfton.io.
2. Information we collect
When you join our waitlist or request access to the demo, we collect the email address you provide.
When you use our website, we may automatically collect limited technical data such as device type, browser and anonymised usage analytics to help us improve the product.
If you choose to connect Google and YouTube, we receive encrypted OAuth credentials; basic AdSense account identifiers; monthly AdSense estimated earnings, currency and reporting periods; and YouTube Analytics metrics including daily views, watch time, average view duration, and subscribers gained or lost. We do not request permission to edit your channel or publish content.
3. How we use your information
We use your email to manage the waitlist, send you product updates about early access, and contact you about the beta.
We use aggregated, anonymised analytics to understand how the site is used and to improve it. We do not sell your personal data.
We use Google and YouTube data only to provide the creator who connected the account with private revenue history, channel-performance analytics, synchronization, support and security. We do not sell this data or use it for advertising.
4. Google API Services
Klyfton's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Klyfton requests only read-only AdSense and YouTube Analytics permissions. OAuth credentials are encrypted in storage and access is limited to systems and personnel that need it to operate and secure the service.
You can revoke Klyfton's access at any time by disconnecting YouTube in Klyfton or through Google's connected-app permissions page at https://security.google.com/settings/security/permissions.
5. Sharing and service providers
We do not sell Google or YouTube user data. We disclose personal data only to service providers acting on our instructions where needed to host, secure, support or operate Klyfton; when you direct us to do so; or where disclosure is required by law. Providers are subject to appropriate confidentiality and data-protection obligations.
6. Email and marketing
We use a third-party email platform (Mailchimp) to manage waitlist and demo communications. You can unsubscribe at any time using the link in any email we send.
7. Data retention and deletion
We keep your waitlist information until you ask us to remove it or until it is no longer needed for the purpose it was collected.
When you disconnect YouTube, Klyfton revokes the Google authorization, destroys the stored OAuth credentials, and deletes the YouTube Analytics metrics associated with that connection. Klyfton applies the same credential and analytics cleanup when Google rejects or withdraws the authorization.
AdSense estimated-earnings records form part of the financial history you asked Klyfton to maintain. We retain those records under our financial-data retention policy after a disconnect. You may request deletion by contacting privacy@klyfton.io; we will delete or de-identify them unless a legal or regulatory obligation requires limited retention.
8. Your choices and rights
Depending on your location, you may have the right to access, correct, delete or restrict the processing of your personal data. To exercise any of these rights, contact privacy@klyfton.io.
Connecting Google and YouTube is optional. You can review or withdraw that permission at any time without affecting unrelated Klyfton features.
9. Changes to this policy
We may update this policy from time to time. Material changes will be reflected by updating the date at the top of this page.