Google data in plain language: Connecting Google is optional. With your permission, PodRise reads only the Search Console, Google Analytics, and YouTube information needed for your chosen features. A separate permission lets you explicitly upload videos to your selected YouTube channel as Private. You can disconnect Google at any time.
PodRise (“PodRise,” “we,” “our,” or “us”) is a podcast production and growth software service developed by Podcast HQ. This Privacy Policy explains what information PodRise processes when you use mypodrise.com, its application, and connected services. It also explains your options to access, correct, disconnect, or request deletion of information.
1. Information we collect
Depending on the features you use, this may include:
- Account details: information needed to register, authenticate, support, and administer your account, such as account identifiers, name, and email address.
- Podcast and workspace content: shows, episode metadata, guest or production details you provide, transcripts, generated drafts, keywords, notes, publishing plans, uploaded or linked audio/video files, and associated metadata.
- Usage and technical information: feature activity, requested actions, authentication and operational events, error and security logs, and device or browser information made available by the hosting platform. Privacy-permitted website analytics may also be collected where configured.
- Connected third-party information: only the account or property information and authorized metrics you choose to connect, as described below.
- Communications: information you send when contacting us for support, account management, privacy requests, or feedback.
2. Google API data: what PodRise accesses
Google connections are optional and subject to the permissions shown on Google's OAuth consent screen. PodRise currently requests some or all of the following scopes based on the feature you choose:
webmasters.readonlyDiscover website properties you can access and retrieve authorized search-performance information for the property you select.
analytics.readonlyDiscover accessible GA4 properties and read relevant traffic, engagement, and conversion reporting for your selected property.
youtube.readonlyyt-analytics.readonlyIdentify an authorized YouTube channel, inspect relevant channel or video metadata, and read available channel-performance reporting.
youtube.uploadOnly after you separately authorize this permission and initiate a transfer, upload a video file that you select to your authorized channel. The current workflow sets the uploaded video to Private by default; PodRise does not make it public automatically.
We use the resulting information to display your connected properties, populate authorized performance snapshots and episode reports, help organize content and growth decisions, or carry out a specific upload you approve. We do not need access to Gmail messages, Google Drive documents, your contacts, or your Google password for these integrations.
3. How we use and limit Google user data
We use Google API information only to provide or improve the user-facing connected features you request, keep authorized connections working, troubleshoot them, and protect the service. We do not sell Google user data, use it to target third-party advertising, or make connected Google user data available to data brokers. We do not use data obtained through Google APIs to train generalized AI models.
Human access is limited to circumstances necessary for security, troubleshooting, compliance with law, or a request for support, and is subject to appropriate safeguards. If PodRise adds a new use of Google information, we will update this policy and request additional consent when required before the new use begins.
PodRise's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
4. How Google data is stored and secured
Google OAuth access and refresh credentials are stored on the server in encrypted form. Credentials are not intended to be exposed to client-side application code. PodRise stores the connected property or channel identifiers you select and may store limited, dated performance snapshots and authorization metadata to power the workspace.
We use access controls, encryption of stored OAuth credentials, HTTPS connections, and operational safeguards to help protect information. No internet service can guarantee absolute security. Your original audio/video assets may be processed or stored by separate infrastructure as configured and authorized within the product.
5. When information may be shared
Information is processed by services used to provide PodRise, such as application hosting, database, file storage, authentication, processing, and authorized external integrations. These service providers act in connection with providing our service, subject to their applicable terms and safeguards. We may disclose information where legally required, to investigate abuse, or in a business transfer subject to applicable obligations.
When you select a video and authorize its upload, the video and accompanying title or description are transmitted to YouTube under your Google authorization. When you choose to publish through another provider's external interface, that provider's own privacy policy applies. Public podcast directory information is distinct from your private connected-account data.
6. AI-assisted features and podcast materials
Some PodRise features use AI-enabled processing to help prepare transcripts, show notes, content drafts, and recommendations. Materials you submit to those features may be processed by the providers that power them, according to the feature's configuration and applicable provider agreements. Review generated content for accuracy before publishing. Do not upload information you lack permission to process or share.
Connecting a Google account does not itself authorize PodRise to use all your Google account information for AI prompts. Google data use remains limited to the connected features and purposes described in this policy.
7. Retention, disconnection, and deletion
We retain account and workspace information as needed to provide the service, comply with applicable requirements, address security or disputes, and maintain operational records. Retention varies by data type and provider; we do not promise that every backup is erased instantly.
To disconnect Google, open your show's Analytics workspace and choose Disconnect for the Google connection. This deletes the saved Google connection record and associated stored authorization credentials in PodRise. It does not automatically delete previously imported performance snapshots or content you created in the workspace, nor does it revoke consent in Google's systems.
To separately revoke Google's authorization, visit Google Account → Third-party connections and remove PodRise's access. To request deletion of remaining Google-derived snapshots, account information, or workspace materials, email team@podcast-hq.com with the subject “PodRise Data Deletion Request.” We may need to verify account ownership. We will process verified requests in accordance with applicable law and legitimate retention obligations.
8. Cookies and authentication
PodRise and its hosting or authentication services may use necessary cookies, session credentials, or local browser storage to keep you signed in, maintain security, and remember application preferences. Where optional website analytics or other measurement tools are enabled, those technologies may collect information subject to applicable privacy requirements and user choices.
9. Your choices and privacy rights
You can choose whether to connect Google, select or change authorized properties, disconnect a connection, request correction or deletion of personal information, and avoid submitting optional information. Depending on where you live, additional rights may include access, portability, objection, restriction, and appeal. Contact team@podcast-hq.com to submit a request; we may need to confirm ownership and applicable exceptions.
10. Children
PodRise is designed for professional and adult podcast creators, not directed to children under 13. We do not knowingly solicit personal information directly from children under 13. Contact us if you believe a child has provided information so we can review the concern.
11. Changes to this policy
We may update this policy as the beta and integrations evolve. We will update the effective date and provide additional notice or request consent where law or Google's policies require it, particularly before using connected Google data for materially different purposes.
12. Contact and developer identity
PodRise is developed by Podcast HQ in South Florida, United States. For privacy, Google API data, access, or deletion requests, contact team@podcast-hq.com. You can also learn more about the developer at podcast-hq.com.
Questions or privacy requests?
Contact PodRise through its developer, Podcast HQ, at team@podcast-hq.com. Include “PodRise Privacy Request” or “PodRise Terms” in the subject, and do not include passwords or access tokens.
