Privacy Policy
Last updated: 17 November 2026
DriveCast Studio (“DriveCast”, “we”) is a content publishing service built and operated by Naimat Majeed. It publishes a creator's own videos and photos to the creator's own YouTube channel, Facebook Page and Instagram account, on the creator's instruction. This policy explains what we access, why, and how you can remove it.
1. Who uses DriveCast
DriveCast is operated for creators and businesses (“clients”) who ask us to manage the publishing of their own content. Each client connects their accounts themselves, through Google's or Meta's own consent screen.
2. Information we access
- Google (YouTube and Google Drive): the basic profile of the YouTube channel (name, picture, channel ID, public statistics), the permission to upload videos to that channel, and access to the Google Drive folders used to store the client's content.
- Meta (Facebook and Instagram): the list of Facebook Pages the client manages, a Page access token to publish posts and read basic post statistics, and, where connected, the client's Instagram Professional account ID, username and permission to publish content.
- Content: the videos, photos and captions that the client provides or asks us to collect from the client's own public profiles.
- Technical data: logs needed to run the service, such as upload results and error messages.
3. How we use it
Only to publish the client's content to the client's own accounts, to schedule those posts, to show the client how the posts perform, and to keep the service secure. We do not use this information for advertising, we do not sell it, and we do not share it with anyone except Google and Meta as needed to publish.
4. Google API Services
DriveCast's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. YouTube features are subject to the YouTube Terms of Service and the Google Privacy Policy.
5. Storage and security
Access tokens and passwords are stored encrypted on the server that runs DriveCast. Files are cleaned of hidden metadata before publishing, and local copies are deleted a few hours after they are published. Backups are encrypted with a password chosen by the operator.
6. Keeping and deleting data
We keep connection tokens only while a client uses the service. A client can end access at any time:
- Google: myaccount.google.com/connections
- Facebook and Instagram: Facebook Settings › Business Integrations, or Instagram Settings › Apps and websites
- or by writing to [email protected] — we delete the client's tokens and records within 30 days. Content already published stays on the platforms, where the client controls it.
7. Children
DriveCast is not intended for anyone under 18.
8. Changes
If this policy changes, the new version is posted on this page with a new date.