This policy covers the website at cardanorecord.com and
the private publishing automation ("the Application") used to upload videos to the YouTube
channel @CardanoRecord.
Summary. The Application is a single-user tool. It signs in only as its own operator, in order to upload videos to a channel that operator owns. It does not collect, request, store or process personal data belonging to anyone else, and it shares no data with third parties.
The Application and channel are operated by one independent individual. There is no company, no team and no third-party processor. It is not affiliated with the Cardano Foundation, Input Output, Intersect, Indigo Protocol, Google or YouTube.
The Application uses the YouTube Data API v3 and requests these OAuth scopes, for the operator's own Google Account only:
youtube.upload — to upload video files to the operator's channel.youtube — to read the channel's own identity, and to set video metadata
such as title, description, tags and thumbnail.youtube.force-ssl — to attach caption tracks to the operator's own videos.No other Google API, product or scope is used. The Application never requests authorisation from any other person, and no other person can sign in to it.
Solely to publish the operator's own video content to the operator's own channel. The Application reads the channel's name, ID and public statistics to confirm it is uploading to the correct destination, and writes videos, thumbnails, captions and metadata. It performs no other action on the account.
The OAuth refresh token issued by Google is stored in a single file on the operator's own
computer, readable only by the operating-system account that runs the Application
(permissions 0600). It is not transmitted anywhere except to Google's own
authentication endpoints, is not stored in any cloud service, database or version-control
repository, and is not backed up off the machine.
No Google user data is retained beyond that credential and the operator's own published video files.
No Google user data is sold, rented, shared, transferred or disclosed to any third party. It is not used for advertising, profiling, or to train machine-learning or AI models, and it is not transferred to any other application or service.
The credential is retained only while the channel is active. The operator can revoke the Application's access at any time at myaccount.google.com/permissions, which immediately and permanently invalidates it; the local file is then deleted. Since no data belonging to any other person is collected, there is nothing further to delete on anyone else's behalf.
The site is static and hosted on GitHub Pages. It sets no cookies, has no login and no comment system. GitHub may log ordinary web-server request data (such as IP address) as part of serving the page; see GitHub's Privacy Statement. The operator receives no such data.
Visit counts. Pages load GoatCounter, a privacy-friendly analytics service, to count page views. It sets no cookies and collects no personal data: the operator sees aggregate counts (pages, referring sites, country, browser and screen size), never individual visitors. See GoatCounter's privacy policy.
Waitlist and contact form. The "Join the waitlist" and "Get in touch" links open a Google Form. Anything you choose to submit there (such as your name, email and interests) is stored in the operator's Google account and used only to reply to you about the data services; it is never sold or shared. Google processes form submissions under Google's Privacy Policy. To have a submission deleted, email the address in section 11.
Watching videos on YouTube is governed by Google's Privacy Policy and the YouTube Terms of Service, not by this policy. The operator can see only the aggregate, anonymised statistics YouTube provides to any channel owner, and does not attempt to identify individual viewers.
Each episode's prediction is posted as a comment, and viewers may reply YES or NO. To count those votes the Application reads the public replies to that one comment. It keeps only the totals (number of YES and number of NO per prediction). Replier names, channel IDs and reply text are used only in memory while counting (to allow one vote per account) and are not stored.
The same short videos may be published to the channel's own TikTok account through TikTok's Content Posting API. The Application signs in only as that account, requests only basic account information and permission to upload videos, and stores the resulting access token locally on the operator's machine. It does not read, collect or store data about other TikTok users. Watching on TikTok is governed by TikTok's Privacy Policy. Access can be revoked at any time from TikTok's app settings.
The channel is not directed to children, and its videos are not designated as made-for-kids.
Material changes to this policy will be published on this page with an updated date above.
Questions about this policy: amarrer1+cardanorecord@gmail.com