Privacy policy — DLOG Video Factory

1. Operator and scope

Dlog PME Inc. operates DLOG Video Factory for video production and monitoring its YouTube channels. This policy covers this internal, limited-access application and data obtained through its Google integrations. Questions, complaints, and requests: bonjour@dlogpme.com.

2. Google data accessed and purposes

The application uses the YouTube Data API and YouTube Analytics API with these permissions:

• https://www.googleapis.com/auth/youtube.readonly: authorized channel identity, video list, identifiers, titles, available dates, cumulative counters, and publication statuses accessible to the authorized account.
• https://www.googleapis.com/auth/yt-analytics.readonly: reports for videos linked to productions, including views, minutes watched, average view duration, average percentage viewed, and subscribers gained for the selected period.

This data verifies the connected channel, links its videos to productions, and displays their performance. Impressions and click-through rates may be imported manually from a CSV file. Production costs come from internal records; these permissions do not grant access to YouTube revenue reports.

The current permissions do not authorize uploading, publishing, modifying, or deleting data on YouTube. The application receives OAuth tokens for authorized reads; it does not request the Google password.

3. Consent and revocation

An authorized user initiates the connection. Google displays the permissions in the system browser, where users may accept or decline them. The flow checks request state and uses PKCE. Google statistics cannot be synchronized without authorization.

You can remove access through your Google account security settings. Revocation prevents future authorized reads; it does not by itself erase stored data. To request deletion, email bonjour@dlogpme.com identifying the channel concerned, without sending a token or password.

4. Storage, caches, and logs

Active databases, the multichannel registry, and Google data are stored in the Windows account’s local application directory under LOCALAPPDATA, outside the Git repository and OneDrive folders. Access and refresh tokens are encrypted using Windows DPAPI for that account, without a plain-text fallback. The OAuth configuration file is kept in this private storage but is not encrypted using DPAPI like the tokens.

Statistics, CSV imports, video associations, channel information, and synchronization states are stored in local SQLite databases separated by channel. The central registry also holds production and statistics indexes. The application does not encrypt the databases; Windows directory permissions are limited to the current account, SYSTEM, and administrators.

Cached data may be retained after network, quota, or configuration errors. A Google authorization confirmed to be invalid instead triggers the purge procedure. Local server request logs are disabled; diagnostics use predefined codes. Deletion records contain a timestamp, operation identifier, counts, and technical states, without names, YouTube identifiers, tokens, secrets, or user paths.

The application creates no new backups of tokens or personal YouTube data. Existing backups, reports, and old browser profiles were identified and moved into local quarantine outside OneDrive. This move does not establish their deletion or that of any cloud copies or versions. Windows backups and third-party tools outside the application still require inventory.

5. Third-party services and AI processing

Authorization and read requests are sent to Google over HTTPS. Production also uses Google Gemini for editorial processing and narration, and Pixabay for media searches. The generation paths reviewed use briefs, text, and editorial sources; no transfer of OAuth tokens or YouTube statistics into these paths was identified.

No use of Google data obtained through OAuth to train AI models was identified in the reviewed code. This observation is not a guarantee about all providers’ practices. The complete inventory of recipients, data flows, processing locations, and provider terms remains to be verified; this policy does not claim an exhaustive inventory.

These pages load fonts from Google Fonts, as does the existing DLOG website; the browser contacts that service. Public website hosting logs and their retention remain to be documented. See also the Google Privacy Policy.

6. Retention, disconnection, and deletion

Disconnection or a deletion request handled by DLOG initiates channel deletion through the private dashboard or its operator command. The application first blocks synchronization and invalidates earlier pending consent flows. It attempts to revoke authorization with Google, then removes the channel’s tokens, statistics, imports, associations, and Google information from active databases and managed cache, export, and report folders. Other channels and original DLOG video/audio files are preserved. No videos hosted on YouTube are deleted.

If revocation fails because of the network or an unconfirmed response, active local copies are still deleted and the application indicates that access must also be removed through Google security settings. Revocation is not reported as successful without confirmation. Google may withdraw other authorizations associated with the same account and project.

An invalid_grant response or a second HTTP 401 after token refresh triggers local deletion. Maintenance runs at server startup and hourly thereafter; it rechecks authorization at least daily while the server is running. After seven days without successful verification, it purges active copies. An interrupted deletion remains blocked and is retried by maintenance.

The operating target is deletion as soon as possible and within seven calendar days. Maintenance cannot run while the application or computer is off: checks resume at the next execution. DLOG must handle requests received at bonjour@dlogpme.com and run the operator procedure.

Local backups with an identified channel owner and identified Analytics reports are handled by the purge. Composite reports, historical browser profiles, and OneDrive copies, recycle bins, and versions still require separate review and handling. They are not represented as deleted. Deleting copies held by DLOG does not delete data on YouTube.

7. Observed security measures

Implemented and tested measures include read-only permissions, DPAPI token encryption, Windows permissions on private storage, Google requests over HTTPS, OAuth state validation and PKCE, expected-channel verification, and multichannel isolation. The workspace is served locally. Deletion requires an explicit channel; modification requests check origin and CSRF protection.

Google operations for a channel are serialized to prevent an in-flight synchronization from recreating its data after deletion. Consent flows preceding deletion are invalidated. Sensitive files are not served by the dashboard’s media routes.

These measures do not guarantee encryption of the disk, every database, or any system backups. No deletion of historical cloud copies or irreversible physical erasure of storage media is asserted.

8. Google and YouTube policies

Use of Google data is subject to the Google API Services User Data Policy, including its Limited Use requirements where applicable, the YouTube Developer Policies, and the YouTube Terms of Service.

Verification of actual compliance, particularly retention, revocation, and deletion mechanisms, remains open. Publication of this policy does not constitute approval or compliance certification by Google.

9. Historical copies and updates

• Review and handle composite reports and old browser profiles retained in quarantine.
• Verify actual OneDrive state, recycle bins, versions, and remote copies, as well as any Windows or third-party backups.
• Confirm procedures and timelines for those historical copies, and operational execution of maintenance and emailed deletion requests.

The new functions were tested using synthetic data; no real data was deleted during tests. Active data and identified local copies were subsequently moved outside OneDrive in a separate migration. These checks do not establish deletion of historical copies.

Last updated on October 22, 2026. Material changes in use must be explained before data is used for a new purpose, with renewed consent where required.