Privacy Policy

Data PulseFrame processes

PulseFrame processes account information, uploaded media, generated edits, publishing metadata, and data from services you explicitly connect. We use this information only to provide the editing, analytics, account, and publishing features you request.

Google and YouTube data

PulseFrame uses YouTube API Services and Google OAuth 2.0. When you connect Google / YouTube, PulseFrame may access your Google account identity (such as name, email, and profile image), YouTube channel identity, channel statistics, recent video metadata and statistics, and the authorization needed to upload videos that you explicitly choose to publish.

PulseFrame does not request or store your Google or YouTube password. OAuth access and refresh tokens are kept server-side and encrypted at rest.

How Google user data is used

Google user data is used to show the connected account and channel, display channel and recent-video statistics, refresh authorization, and perform YouTube uploads that you explicitly initiate. PulseFrame does not use Google user data for advertising and does not sell Google user data.

Sharing and service providers

PulseFrame does not disclose authorized Google or YouTube data to unrelated third parties. Data may be processed by infrastructure providers strictly as needed to operate PulseFrame, secure accounts, store private application data, or perform actions requested by you.

Retention, deletion, and revoking access

You can disconnect Google / YouTube from your PulseFrame profile. PulseFrame removes the stored YouTube connection and OAuth tokens when you disconnect. You can also revoke PulseFrame access at any time from Google security settings.

Uploaded and generated media may remain while your account needs it or until it is deleted through available product controls or an account-support request. Where law requires longer retention, only the necessary information is retained.

Google API Services User Data Policy

PulseFrame's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Google privacy information

Google's handling of personal information is described in the Google Privacy Policy.

Security

PulseFrame uses encrypted transport for production traffic, keeps OAuth secrets server-side, encrypts stored OAuth tokens, and separates application data by authenticated account. No internet service can guarantee absolute security.

Payments and billing

When a paid plan is purchased, the selected payment provider may process transaction data required to complete the payment, prevent fraud, and meet legal obligations. PulseFrame does not store full bank-card credentials.

Contact and support

For privacy, deletion, payment, or account questions, use the PulseFrame support ticket system, email pulseframenew@gmail.com, or Telegram @pulseframenew.