Carpe Diem Publisher privacy policy
This policy covers the private Carpe Diem Publisher application and its account connections. Carpe Diem News operates the application for its channel owner.
Information we access and store
For a YouTube connection, the application receives the channel ID and name, the Google OAuth client ID and secret supplied by the owner, and access and refresh tokens granted through Google authorization. It records when the connection was verified. Temporary authorization records contain a one-time state identifier, an encrypted authorization verifier and client configuration, the expected channel name, and an expiration time.
For Bluesky, it stores the account handle, stable account identifier, dedicated app password and session credentials, plus connection and publication metadata. Content and media supplied for a publishing request are sent to the selected platform.
For Pinterest, Facebook, Instagram, Threads and X connections, the application stores the app/client ID and secret, expected account name or ID, any supplied login configuration ID, granted access and refresh tokens where available, token expiration details, the authorized account ID and display name, and the last verification time. Temporary connection attempts contain encrypted app configuration and a one-time authorization verifier. The signed-in operator identifier and brand associate records with their owner.
Publication records may contain a request identifier, content fingerprint, status, timestamps and resulting post URL to prevent duplicate posts and check delivery. Hosting and sign-in services may also process technical request information needed to operate and secure the service.
How information is used
Account information is used to verify the intended channel or profile, maintain authorization, and perform owner-authorized account and publishing operations. YouTube read access is currently used to check channel identity. Upload access is requested for authorized video publishing; public API uploads are not enabled while the YouTube API audit is pending.
An AI assistant may receive connection status, channel names and identifiers, and results of authorized operations. Stored passwords, client secrets and access or refresh tokens are not returned in publisher tool responses. Google user data is not used to train generalized AI or machine-learning models, target advertisements, or build unrelated profiles.
Pinterest and other social connections
The Pinterest connection requests user_accounts:read, boards:read, pins:read and pins:write. These permissions support identifying our authorized account, selecting its boards, reading its Pins and creating owner-approved Pins as publishing features are enabled. This is a private tool for our own account, not a service for accessing other people's private boards or Pins. Connection verification currently reads account identity; authorization does not itself publish content or establish production approval.
Meta and X connections similarly use account information and granted permissions to identify the intended Page or profile, maintain authorization, and support owner-authorized publishing as available. Availability depends on the platform's approvals and the application's enabled features.
We do not sell connected-platform data, use it to build advertising profiles, or use it to train machine-learning models.
Storage and service providers
Credentials are encrypted before being stored, and connection records are restricted to the signed-in owner. The application is hosted through OpenAI Sites and uses Cloudflare hosting and database infrastructure. These providers process application data as needed to host and operate the service. Google, Bluesky, Pinterest, Meta and X receive requests and content needed for their respective connected-account operations. Content published to a public profile or board can be seen and shared by others under that platform's settings. When the owner invokes the application through ChatGPT or another authorized AI client, that service processes the supplied task inputs and tool results under its own policies. Secrets are handled on the Publisher server and are not included in normal tool results. Account names, identifiers, verification times and publication metadata are stored separately from encrypted credentials. No online service can guarantee absolute security.
We do not sell Google user data or disclose it to advertisers. Disclosure is limited to operation of the requested service, the owner's authorization, security needs, or applicable legal requirements. Carpe Diem Publisher's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Retention, revocation and deletion
Saved connection records are retained until removed or deletion is requested. A temporary YouTube or other social-platform authorization attempt expires after 15 minutes and cannot then be completed; expired records are cleaned up when the owner starts another authorization attempt. A consumed authorization attempt is deleted.
To revoke Google access, remove the application's connection through Google Account connections. To revoke Bluesky access, delete its dedicated app password in Bluesky settings. Revocation stops further authorized access but does not itself delete the application's saved records or content already posted to a platform.
For Pinterest, Meta or X, revoke the Publisher's access through the platform's connected-app or account settings. Revoking access does not automatically remove saved Publisher records. Publication records are retained as needed to prevent duplicate delivery and troubleshoot results.
To request access, correction or deletion of saved setup credentials, tokens, connection data or publication records, email carpediemnewsdesk@gmail.com. Include the platform and account name. We verify the requester's account ownership before responding or removing applicable records, subject to any necessary legal or security retention. Never include passwords, tokens or client secrets in the request. Existing posts must be managed separately on their platform.
Changes and contact
This page will be updated when the application's data practices change. For privacy questions, contact carpediemnewsdesk@gmail.com.
Carpe Diem News
PO Box 145
Pollock Pines, CA 95726
Email subscriptions are covered separately by our newsletter privacy policy.