DriveStream Pro Privacy Policy

1. Who we are and what this policy covers

This policy covers DriveStream Pro at drivestream.pro, our Studio and Admin applications, and the services that import, prepare, store and broadcast videos you own or are licensed to use. Our support and privacy contact is drivestreampro@gmail.com. It explains the data we access, why we use it, where we store it, and when we share or delete it.

2. Information we collect and access

• Account information: your Firebase account identifier, email address, display name, sign-in provider, email verification status, application role and account preferences. Firebase Authentication handles sign-in credentials; Google passwords are not requested or stored by DriveStream Pro.
• Media and import records: the video files you upload or select for import; filenames, source links or file identifiers, sizes, duration and technical media properties; prepared copies; playlist order; import status; and your confirmation that you have rights to use the content.
• Connected accounts: the connected account email or provider identifiers, permissions granted, connection times, encrypted OAuth access and refresh tokens, and live destination URLs and encrypted stream keys you provide.
• Billing information: the plan and resource allowances you select, billing period, payment-provider customer and subscription identifiers, purchase references, payment status and cancellation status. If eligible card checkout is offered, the billing address you enter is sent to PayPal for that payment and is not saved in your DriveStream account. Stripe, Razorpay, or PayPal, when configured, handles payment details. We do not store full card numbers or card security codes.
• Operation and security information: stream schedules, start and stop events, destination-hours, measured or estimated transfer usage, storage reservations and completed media size, preparation usage, technical errors, and request or security logs that can contain an IP address, browser information and timestamps.
• Support and preferences: messages you send to us, marketing consent and unsubscribe preferences, language settings, and browser data needed for sign-in or resumable uploads.

3. Google Drive and YouTube connections

Google Drive data and permissions

Connecting Google Drive is optional. We request https://www.googleapis.com/auth/drive.readonly so our file browser can list accessible video files and folders and download the videos you explicitly select. We also request https://www.googleapis.com/auth/userinfo.email to identify the Google account connected to your workspace.

Read-only Drive permission can cover all files accessible to that Google account. Our integration uses it to obtain file and folder names and identifiers, parent-folder information, file type, size and other available file metadata needed for browsing and import. We download a video's contents only when you select it for an import. We store the imported copy and necessary source and consent records in your private workspace; connecting Drive alone does not copy your entire Drive.

OAuth access and refresh tokens let the service perform authorized requests and maintain the connection when an access token expires. These tokens are encrypted in persistent storage. We do not change, delete or share your original Google Drive files, change their permissions, or bypass Google's file restrictions or download quotas. Workspace and plan limits still apply.

You can use device uploads without connecting Drive. You can disconnect Drive in Studio → Account or revoke access through your Google Account's third-party connection settings. Disconnecting removes our saved Drive connection credentials and attempts to revoke the authorization with Google. Imported copies already in your media library remain until you delete them or your workspace is cleaned up.

YouTube API Services

Connecting YouTube in Studio → Channels is optional and separate from connecting Google Drive. This feature uses YouTube API Services and requests https://www.googleapis.com/auth/youtube.force-ssl when you connect your channel. We use this permission to identify the channel you authorize, list its live events, create and link the live broadcast and streaming destination you request, read the selected event's receiving and live status, and publish the title, description, tags, privacy setting and thumbnail you choose for an event owned by that channel. Read-only permission cannot perform these requested changes. Google's description of this scope is broader than these features; the active integration does not provide video deletion, comment management or caption management.

We store encrypted YouTube access and refresh tokens, the connected channel's identifier, display name and thumbnail URL, and the event identifiers, streaming-destination bindings, publication records and health observations needed for your selected broadcasts. Your video and audio are sent to the destination you choose when you start or schedule a stream. We do not make changes to an unrelated channel or use your YouTube connection to access another customer's account.

Stop streams using a channel before disconnecting it in Studio → Channels. A successful disconnect removes that channel's saved connection credentials and channel metadata, active event bindings, resolved event references in drafts, and channel-specific health snapshots. Your uploaded media, written titles, descriptions, tags, privacy choices and uploaded thumbnails remain. Unfinished event-creation records can remain for reconciliation so an uncertain API response does not cause a duplicate broadcast; other operational records can also remain as described under retention below. Disconnecting does not delete videos or broadcasts from YouTube.

Disconnecting one channel in Studio does not automatically revoke the app's Google authorization. You can revoke that authorization through Google Account permissions. Revoking access there can also affect other channels or Google features authorized through the same app. Google revocation does not itself erase the copies of records already stored by DriveStream Pro. To request deletion of remaining YouTube-derived records, email drivestreampro@gmail.com.

Your use of YouTube features is also subject to the YouTube Terms of Service. Google's handling of information is explained in the Google Privacy Policy.

4. How we use information

We use account data to authenticate you and keep each user's workspace separate. We use selected media, file metadata and source information to import files, check streaming compatibility, prepare videos when permitted, build playlists, and run the broadcasts and schedules you configure. We use resource measurements and billing records to apply your plan, show usage, process purchases and protect shared infrastructure from abuse.

We use technical logs to detect failures, secure the service and investigate abuse. We use support messages to respond to your request. When email delivery is enabled, we may send essential account, payment, cancellation or usage notices. Product updates and promotional email require a separate opt-in; you can withdraw that opt-in in Account or using the email's unsubscribe link.

When you submit a contact message or request a custom plan, we store your name, email address, message, the requirements you choose to share and your permission to receive a reply. Authorized staff use these records to respond and prepare a proposal. Replies and their approval and delivery records are kept with your request. We use limited security records to prevent spam. Submitting a request does not subscribe you to promotional email, purchase a plan or authorize a charge. You can contact us to request deletion of your inquiry records.

5. Google API data: Limited Use and human access

Our use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements. Google Drive and YouTube data are used to provide or improve the user-facing import, media preparation, channel connection, live-event management, broadcasting and health-status features described here.

We do not sell Google API data, use it for advertising or advertising targeting, or use it to train general-purpose artificial intelligence or machine-learning models. We do not use Google Drive content to create unrelated personal profiles.

Authorized personnel may access account, billing and usage records as necessary for operations and support. Human access to Google API-derived content is limited to your affirmative permission for specific content or a support task, necessary security or abuse investigations, compliance with applicable law, or internal operations using aggregated and de-identified information. Connected Google tokens and file content are not made publicly available through the admin directory.

6. Sharing, transfers and service providers

We share information only for the functions described in this policy, your explicit instructions, or required legal and security purposes. We do not give an advertising business access to your Drive connection.

• Google Firebase Authentication: sign-in credentials, account identifiers, verification status and authentication roles. Application, plan, usage and workspace records are stored in our PostgreSQL database; a private Hasura service supplies authorized realtime updates. Saved Drive tokens and live connection secrets are encrypted before being stored in workspace records.
• Hosting and compute providers: the selected media and technical records needed to store, download, prepare and stream files on our VPS or assigned workers. Prepared copies and temporary working files may be created during conversion. Providers process this information to run the requested service.
• Stripe, Razorpay, or PayPal: account email, selected purchase and necessary payment or subscription information when that provider is enabled. These providers do not receive your Drive refresh token or media library from us for payment processing.
• Mailjet: email address, any display name used in a message, and the content of account notices or opted-in promotional messages when email delivery is enabled. Drive file contents and Drive refresh tokens are not used to target promotional messages.
• Your streaming destinations: selected video and audio, and any live-event details you choose to send, when you start or schedule a broadcast. These can be YouTube, Facebook, Instagram, X or another RTMP service. A public destination can expose that broadcast to its audience under its own settings and privacy rules. Your Drive token and unrelated Drive files are not sent as part of the broadcast.

We may disclose necessary records when legally required, to investigate fraud or security incidents, or to protect users and the service. Google API data remains subject to the Limited Use commitments above. Contact us for information about the infrastructure providers or processing regions used for your workspace.

7. Storage, security and international processing

Firebase Authentication handles sign-in records. Account and application metadata is stored in PostgreSQL on our hosting infrastructure, with a private Hasura service for authorized realtime updates. Uploaded or imported media, prepared videos and temporary working files are stored in a user-specific location on our VPS or streaming and preparation infrastructure. Data may be processed outside your country depending on the providers and regions used.

We use HTTPS for service and provider requests, signed authentication tokens, checks that restrict access to the requesting user, role-based administrator access and plan enforcement. Persistent Drive tokens and RTMP secrets are encrypted with authenticated encryption. OAuth uses an expiring authorization session, PKCE and a private browser-bound callback cookie. Infrastructure access is restricted to authorized operators. These safeguards reduce risk; no internet service can guarantee absolute security.

8. Retention and deletion

• Media you delete: you can delete retained workspace media through the library, subject to stopping any broadcast using it. This does not delete the original in Google Drive or another source service.
• Paid access ending: streaming and media access stop. Your workspace is retained for seven days to allow renewal. After seven days, videos, playlists, saved streams and schedules are automatically deleted once ended access is verified. Cleanup can be delayed while a payment or storage operation needs reconciliation. Your login and payment history remain available, and you can buy a new plan to start with an empty workspace. Deleted workspace data cannot be recovered.
• Incomplete uploads and preparation: partial upload bytes and recovery information can remain while an upload is resumable. They are removed when you cancel or the upload session expires. Preparation may create temporary files and completed copies subject to storage limits and cleanup.
• Drive credentials: retained to operate your connection until you disconnect, revoke access, or applicable workspace/account cleanup removes the saved connection. Drive originals remain under your Google account's control.
• YouTube connection records: saved credentials and resolved event references are removed on successful Studio disconnect as described above. Unfinished creation checkpoints and operational records may remain for reconciliation, security or support. Revoking the app in Google Account permissions prevents further authorized Google access but does not by itself remove these locally stored records. Contact us to request their deletion; your user-authored drafts and media are separate from the YouTube connection.
• Account, billing and operation records: login details, necessary billing records, support records and aggregate usage counters may remain after media cleanup while needed for your account, security, accounting or applicable legal obligations. We remove or de-identify records when they are no longer needed, subject to those obligations.

Renewing before cleanup restores access to retained files. Paying after completed cleanup creates an empty media workspace. You may email drivestreampro@gmail.com to request earlier deletion, account deletion or information about retained records. We may ask you to confirm control of the account and will explain any records that must be retained. Do not send passwords, stream keys or Google tokens by email.

9. Browser storage and cookies

We use essential browser storage and cookies for authentication, language preferences, OAuth security, upload progress and resumption. If you choose file recovery, the browser may retain permission-controlled information about the original file. Browser settings can clear this data, but clearing it may sign you out or prevent automatic upload recovery. Third-party sign-in and payment services may use their own cookies under their policies.

Optional website analytics

With your permission, the public website uses Google Analytics 4 to understand page visits and engagement. The Analytics tag is not loaded before you accept analytics. Choosing “Reject” leaves analytics off. You can change your choice using the “Change analytics preferences” button on this Privacy page; withdrawing consent removes our Analytics cookies and reloads the page to stop the tag.

Google processes analytics cookie identifiers, page names, visit times, browser and device information and approximate location derived from network information. We strip URL query strings and fragments and send only the referring website origin. We do not send account emails, user IDs, Drive files, upload details, OAuth tokens or stream keys to Analytics. This integration does not run in Studio or Admin. Google Signals and advertising personalization are disabled in our tag configuration.

Analytics information is used to improve the website. Google processes it under its Privacy Policy and may process it outside your country. Your browser remembers your analytics choice locally. Google Analytics cookies can persist across visits; clearing cookies or rejecting analytics removes the cookies set by this website. Individual event data is retained according to our Analytics property retention setting.

We use your IP address locally to suggest India (INR) or international (USD) pricing. This country-level suggestion does not require GPS access or change an existing subscription. You can change it before checkout. The lookup does not send your IP to the database provider. This product includes GeoLite2 data created by MaxMind.

10. Your choices and privacy requests

You can change account preferences, decline promotional email, disconnect providers, revoke Google access, delete workspace media and manage your subscription. Depending on your location, you may also have rights to request access, a copy, correction or deletion of your personal information, or to object to or restrict certain processing. Contact DriveStream Pro Support at drivestreampro@gmail.com for support and privacy requests.

Upload or import personal information about other people only when you have the necessary rights and permissions. If you believe a child's personal information or other content has been provided improperly, contact us so we can investigate and take appropriate action.

11. Changes to this policy

We publish changes here with an updated effective date. We will notify users through the service or their account email when the use of Google user data changes materially. If a new feature needs broader Google permissions, it requires a new consent flow; this policy alone does not authorize that access.