Crux Publisher
Crux Publisher: Privacy.
Crux Publisher uploads Crux gameplay videos to the Crux YouTube channel. It works only with that channel, for its owner, and keeps its records on Pizzart's own computer.
1. The short version
Crux Publisher is the tool Pizzart uses to publish Crux gameplay videos to the Crux YouTube channel. It has one user: the owner of that channel. It works only with that channel, keeps its records on Pizzart's own computer, and shares them with nobody.
2. Who we are
Crux Publisher is run by Pizzart Pte. Ltd., Singapore, the maker of the Crux app and crux.quest. For any question or complaint about privacy, write to support@crux.quest.
3. YouTube API Services
Crux Publisher uses YouTube API Services to work with the Crux YouTube channel. By using Crux Publisher, its user agrees to be bound by the YouTube Terms of Service.
Google handles the information on its side under the Google Privacy Policy.
4. What the tool accesses
When the channel owner connects the channel, Google shows a consent screen and the owner approves it. After that, Crux Publisher accesses the owner's own channel only:
- The channel. Its name, picture and ID, so the tool can show which channel is connected.
- The channel's videos. The tool uploads Crux gameplay videos and sets or edits their titles, descriptions, tags, thumbnails and visibility. It reads the list of the channel's own videos, their status and the comments on them.
- The channel's analytics. Views, watch time, likes, comments and subscriber counts for the channel and its videos, through the YouTube Analytics API.
Every request is about the Crux channel and is made for its owner. Other YouTube users and other channels are outside the tool's scope.
5. How the information is used
- To publish Crux's videos to the Crux channel at the time the owner chooses.
- To keep their titles, descriptions and thumbnails correct.
- To show the owner how the channel's videos are performing.
The information is used for these purposes only. It is processed on Pizzart's own computer and sent only to YouTube.
6. What is stored, and where
- The sign-in token. The OAuth token Google issues when the owner connects the channel. It is kept for as long as the channel stays connected, so that scheduled uploads work.
- Post records. For each post: the video file, its title, description and thumbnail, when it was scheduled and published, and the YouTube video ID and link that came back.
- Channel details and figures. The channel name, picture and ID, and the analytics figures the tool has read. Details read from YouTube are refreshed from YouTube or removed within 30 days.
All of this is stored on a computer that Pizzart owns and controls. It is protected by a password and reached over an encrypted connection.
8. Cookies and devices
Crux Publisher keeps one sign-in session in its user's browser, so the owner stays signed in. It places no advertising or tracking cookies, and it collects nothing from anyone else's device.
9. Revoking access
The channel owner can remove Crux Publisher's access at any time on the Google security settings page, at myaccount.google.com/permissions (also reachable at security.google.com/settings/security/permissions). Choose Crux Publisher and remove its access. The owner can also disconnect the channel inside the tool.
After access is removed, the stored token and the information read from YouTube are deleted, within 7 days of a disconnect in the tool and within 30 days of a removal on the Google page.
10. Asking for deletion
To have the stored information deleted, write to support@crux.quest. We delete it within 7 days and confirm by email. This removes the copies held by Crux Publisher. Videos and data held by YouTube are managed in YouTube itself.
11. Changes
If this policy changes, the new version is published on this page and the effective date above changes with it.