Privacy notice

Sign-in and account identity

Devlog supports Google sign-in, Steam sign-in and email codes. We store provider identifiers, basic profile details and verified contact emails where available. Sessions use secure HTTP-only cookies; only session token hashes are stored. Google credentials are used to verify identity, not to access Gmail or Drive.

What is saved

Devlog stores your games, cards, sources, assistant conversations, tasks, notes, change history, imported or fetched reporting, community and player snapshots, and operation usage records. Device-local preferences remember your selected game and chart settings.

Studio tasks, notes and player observations

Tasks and notes are stored privately per game and included in your account export. Archived items remain available to restore until the game is removed. Devlog stores public Steam online-player samples when you open a game; it does not track individual players or run continuous monitoring.

Bluesky connection

Connecting Bluesky stores encrypted OAuth credentials, your public profile, follower observations, recent public posts, drafts and publication records for the selected game. Uploaded images and videos are stored privately with your draft and media library. Publishing sends the approved text and media to Bluesky publicly and saves a timeline card. Removing a game deletes its saved media. Disconnect revokes app access; saved history remains until the game is deleted. Devlog does not reconstruct earlier follower counts or monitor accounts while the site is closed.

YouTube tracking and Google data

Devlog uses YouTube API Services. YouTube tracking uses a channel handle or URL and public data; it does not request YouTube account permissions or store OAuth tokens. Tracking uses public channel and video data: channel identity, public uploads, titles, descriptions, publication dates, thumbnails, subscriber counts, views, likes and comment counts. Private and unlisted videos are excluded. We do not read comment text, upload videos or change your channel. You choose which games each video belongs to; your assignment decisions and timeline notes are stored in your private workspace.

Public tracking statistics are kept for a rolling 29 days. Cached video details are refreshed or cleared within 29 days. Removing a tracked channel clears its tracking library, subscriber history and imported YouTube details from timeline cards and their undo history, while preserving your own notes. Assignment decisions are retained during tracking and removed when you remove the channel. Remove the channel inside Devlog to stop public tracking. If you authorised the previous account connection feature, you can also revoke that older permission through your Google Account; Devlog no longer uses it. You can contact hello@devlog.studio to request deletion or ask questions about your data.

Google and YouTube process API requests under their own policies. Devlog stores tracking data to provide your private workspace and does not sell Google or YouTube data or use it for advertising. YouTube tracking data is not sent to AI services for automatic video assignment. If you ask the assistant about a timeline card, its saved contents can be included in that request as described in the assistant section below.

YouTube Terms of Service · Google Privacy Policy · Revoke Devlog’s Google access

Assistant and external services

When you use the assistant or research tools, relevant game information, messages and card context are sent to the OpenAI API. Research may access public websites. Steam and optional YouTube requests retrieve store, reporting or coverage data. Financial API keys are used for reporting requests and are not included in assistant context.

Background monitoring and notifications

Monitoring stores per-game preferences, check times, discovered sources, API request counts and error codes. Only enabled beta accounts with monitoring selected are checked. Checks use the site’s YouTube key, public Steam information and, for monitored games with a connection, your encrypted Steamworks reporting key. Optional discovery emails use your verified contact address through Zoho. Email content and submission status are retained to avoid duplicate sends and investigate failures. Open and click tracking are disabled. Unsubscribe links turn off discovery emails without affecting sign-in codes. Administrators can grant monitoring access, suspend accounts and revoke sessions; these changes are logged.

Email delivery

When you request an email from Devlog, your recipient address and message content are sent to Zoho CPaaS for delivery. Devlog disables email open and link-click tracking. Delivery-test request times count toward a limited sending allowance.

Connections and API keys

Steam financial and optional YouTube keys are encrypted before database storage. Disconnecting a connection removes its saved key. It does not erase reports already imported into your workspace.

Saved history and controls

Saved workspace records currently have no automatic expiry. Individual card deletion can be reversed through change history. You can permanently remove a game and its saved workspace data and Steam reporting connection from Account; game removal cannot be undone. You can also export your workspace, disconnect API connections in the workspace, and sign out. Self-service erasure of the entire account is not available in this prototype.

Before a public launch

This notice describes the current prototype. Operator contact details, formal retention and erasure procedures, and the final service-provider information must be completed before public registration opens.