1. Who operates this service
First Class Ventures, LLC, doing business as OdooClass.com, operates Factory Line at factoryline.odooclass.com. Factory Line provides a creative production workspace and Channel Studio for authorized YouTube channel work. Its Google-connected Channel Studio is currently used by the owner and expressly authorized assistance; it is not open for public registration or third-party channel onboarding.
This policy covers Factory Line. The separate OdooClass training website and its Google sign-in are governed by that website’s policies. A Factory Line channel connection does not change an OdooClass login.
2. Information we access, collect and store
- Channel and video information: the authorized channel’s identifier and name, its uploads playlist, video identifiers, titles, descriptions, publication dates, links, visibility, duration, caption and custom-thumbnail availability, and available view, like and comment counts. Authorized reads can include metadata for non-public videos.
- Optional analytics: when selected and approved, channel and video performance measurements such as views, watch time, average viewing duration and percentage, likes, comment counts, shares and subscriber changes. These reports do not identify individual viewers or provide their private messages.
- Connection information: Google OAuth access and refresh tokens, granted permissions, expiry information, channel-to-project associations and connection or synchronization status. Google handles Google passwords; Factory Line does not receive them.
- Publishing information: owner-selected source media, title, description, audience declaration and requested visibility; the file’s size and integrity hash; transfer progress and a temporary resumable-upload reference; and YouTube’s resulting video identifier, visibility and processing status.
- Workspace information you provide: projects, instructions, uploaded media, generated files, review rules, description links, disclosures and other saved work. This information is separate from the imported channel library.
- Operational information: account and access records, request times, IP addresses, requested paths, response status and error information needed to operate and secure the service. Application access credentials and connection tokens are not included in public reports or published video metadata.
The channel connection does not request Gmail messages, Google Drive files, Contacts or Calendar access. The Google consent screen identifies the permissions requested. Analytics and video uploads are optional choices requiring the corresponding grant.
3. How we use this information
We use channel data to confirm access to the selected channel, maintain its connection, display and search video information, show requested performance reports, export reports at the owner’s request and identify videos matching owner-authored review rules. Refresh tokens maintain an approved connection without repeated sign-in for every request.
For a requested publication, we send the selected video and its approved metadata to YouTube, record transfer progress so interruptions can be reconciled, and check the resulting video’s status. Connecting a channel does not itself upload anything. Changes to existing videos require a separate owner instruction and a supported operation with suitable Google permission.
Workspace instructions and media are used to perform the work the owner requests. Separate creative features may send selected inputs to the provider chosen for that task. Connecting YouTube does not automatically make channel data available to those creative workflows.
4. Google data, sharing and AI
Factory Line uses YouTube API Services. We handle Google API data according to the Google API Services User Data Policy, including its Limited Use requirements, and the applicable YouTube developer policies.
We do not sell Google user data, give it to data brokers, use it for advertising targeting or credit decisions, or use it to train generalized AI or machine-learning models. Channel Studio’s library, analytics and rule-based review operations do not automatically send imported Google data to generative AI providers.
Data is processed by Google/YouTube and by infrastructure providers required to host, deliver, secure and back up the application. The owner may authorize an operator or assistant to access specific information needed to carry out a requested task. Such access is limited to that purpose. Other human access is limited to consented support, necessary security investigation or legal obligations, as permitted by applicable Google policies.
We do not make private channel reports available to other customers. A video is sent to YouTube only for an authorized upload, and an exported report is under the owner’s control after download. Any transfer connected with a business sale must respect applicable Google consent requirements.
5. Storage and security
Connection credentials and channel records are stored in the application’s server database. Source media and generated artifacts are stored in the workspace’s file storage. Access is restricted by account and project, with additional controls for infrastructure administration. Google API requests and public application access use HTTPS. Restricted database backups contain sensitive information and are accessible only to authorized administration.
Do not put passwords, access tokens or client secrets in video titles, descriptions or support messages. If you suspect unauthorized access, contact us promptly using the contact link below.
6. Retention
Imported video-library and analytics cache entries expire after no more than 30 days. Expired entries are excluded from application reads and removed by maintenance. A requested refresh retrieves current information from YouTube.
OAuth credentials are retained while the connection is active and are removed locally when disconnected, replaced or permanently rejected by Google. A resumable-upload reference is retained while needed to reconcile a transfer, and is erased after a completed transfer or when the connection is disconnected.
Owner-authored project work, source media, links, rules and publication history remain until removed through their relevant controls or a deletion request. Publication history includes the receipt needed to identify an upload and avoid accidental duplicate publication. Deleting a channel’s local data removes its publication records; it does not remove the original workspace job or media.
Routine database backups rotate after a newly verified backup and normally retain approximately seven days of archives. Backup failures can delay rotation. Separate restricted recovery copies are handled through the deletion and recovery process. Revoked credentials or deleted Google data must not be restored into active service from a backup.
7. Disconnecting, revoking access and deleting data
- Clear imported data: open the channel’s Video library, expand Stored data controls, and choose Clear imported data. This removes imported library and analytics records while keeping the connection and authored records.
- Disconnect: use Disconnect on the channel to erase local credentials and clear imported library and analytics data. This does not revoke Google’s entire application grant or remove other projects’ connections.
- Delete local data: use this control on the channel to remove its local connection, permissions, imported records, publication history and saved links or review rules.
- Revoke at Google: remove the application at Google Account connections or Google’s permissions page. Use Delete local data as well, or contact us, to request removal of local records. Google revocation and local deletion are separate actions.
- Request help: use OdooClass Contact Us and identify Factory Line, the relevant project and channel. You may request access, correction, export or deletion. Requests to delete stored Google/YouTube data are handled within 30 days, subject to identity verification and applicable legal requirements.
Local deletion does not delete videos already hosted on YouTube. Manage those videos through YouTube Studio. To delete source files or other workspace records as well, include them in your request. Copies you exported to your own devices are outside the application’s deletion controls.
8. Browser storage and third parties
The workspace uses essential cookies and browser storage for access, selected projects and the temporary OAuth handoff. These public policy pages do not require sign-in. Google authorization pages, YouTube and any embedded YouTube player may use their own cookies and collect device or playback information according to their policies. A connected channel is not permission to use its data for advertising.
See the Google Privacy Policy and YouTube Terms of Service.
9. Changes and contact
Before introducing new uses of Google data or opening Channel Studio to additional users, we will update the disclosures and obtain any required consent. The effective date above identifies this version.
First Class Ventures, LLC DBA OdooClass.com
3000 S Jefferson, St Louis, MO 63118, United States
Contact the operator about privacy, support or deletion