Privacy notice
How Devlog handles your account, private workspace and connected services.
Why we process personal information
Craig Bryant, trading as Devlog Studio in the United Kingdom, is responsible for Devlog’s account and service personal information. We process account identity, workspace information and requested integrations to provide and administer the service under our contract with you. We rely on legitimate interests for proportionate security, fraud prevention, service reliability and support, and legal obligations for records we must retain. Optional connection permissions, reports and public publishing are controlled by you. We do not treat accepting the terms or reading this notice as consent to marketing. Customer-supplied outreach contacts are used to provide the customer’s requested tools; customers remain responsible for the lawful use of their contact lists and email content. Devlog does not make automated decisions with legal or similarly significant effects about you.
Your privacy rights and complaints
Depending on the law that applies, you may request access to your personal information, correction, deletion, restriction of processing or a portable copy. You may object to processing based on legitimate interests and withdraw consent for optional processing without affecting earlier lawful processing. Some rights have exceptions, including records needed for legal obligations or disputes. Email hello@devlog.studio. We may verify your identity using information proportionate to the request. We normally respond to UK GDPR requests within one month; permitted extensions and their reasons will be explained. You can also complain to the UK Information Commissioner’s Office or your local data protection authority.
Third-party media and browser storage
Devlog uses secure session cookies for sign-in and browser storage to remember interface preferences. We do not use advertising cookies or email open tracking. Press-kit trailers use YouTube’s privacy-enhanced embedded player. Loading the player connects to YouTube, which receives your IP address and browser information and may use its own storage under its policies. Public press-kit visits and download or store-link actions can be recorded as aggregate activity; the press-kit privacy section explains this separately.
Where your data is stored
Devlog is hosted by Cloudflare. Account details, game workspaces, imported Steam reports, timeline cards, assistant conversations, feedback, encrypted connection credentials, email drafts and sending records are stored in Cloudflare D1. Uploaded images and videos are stored in Cloudflare R2. At the time of this policy update, the primary production database and uploaded-media storage are located in Cloudflare’s Western Europe region. These storage resources are not configured with a UK-only or EU-only residency restriction. Cloudflare runs the application on its global network, so requests may be processed outside the storage region.
Encrypted database exports are also held on devices controlled by the site operator for recovery. Your browser stores interface preferences and some temporary cached information on your own device.
Connected services, including OpenAI, Google, Microsoft, Zoho and Stripe, process the information needed for their features on their own infrastructure, which may be outside the UK or European Economic Area. The sections below explain what information is shared with these services.
Sign-in and account identity
Devlog supports Google sign-in, Steam sign-in and email codes. Google sign-in requests OpenID, email and basic profile permission to verify your identity and provide your initial display name. We store the provider account identifier, verified email address and display name. Google sign-in does not request Gmail, Drive or YouTube account access. Connecting Gmail is a separate action that requests permission to send emails and identify the chosen sender account; it does not permit Devlog to read your inbox. Sessions use secure HTTP-only cookies; only session token hashes are stored.
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.
Optional Indie Metrics contributions
Connecting Steamworks or importing reports does not grant contribution consent. You can separately enable ongoing contribution for a specific game’s full available imported performance history, including existing history and later imports. Permission does not extend to other games accessible through the same financial key. We use private daily reports and confirmed dates internally to calculate supported milestones, conversions and aligned performance trends. We retain a private game and account link for updates and withdrawal, and derived figures, aligned series, coverage information and broad cohort context in the active pool. Public responses contain rounded medians, quartile ranges and sample sizes with at least ten qualifying games from ten distinct developer accounts per metric, trend point or cohort. API keys, game names, account details, exact dates, daily records and individual results are not published. Fictional samples are separate and never count towards real benchmarks.
Disabling contribution removes that game’s derived figures, aligned series, coverage and consent record from the active community pool. Future imports no longer contribute that game. Its private Devlog history is preserved. Deleting a game or account also removes its contributions. Previously viewed or copied aggregates cannot be recalled. Existing backup retention and security protections described below apply to contribution records.
Steamworks financial reporting keys and data
Connecting financial reporting is optional and separate from signing in with Steam. You supply a Steamworks financial API key so Devlog can retrieve wishlist and sales reports from Valve, including country-level reporting. Devlog uses this connection for manual report syncs and enabled automatic reporting checks. It does not use the financial reporting connection to change your Steam store, initiate payments or alter payouts. A financial API key can have access to reporting across your Steamworks partner account, so it should be treated as a sensitive credential.
Your key is sent to Devlog over HTTPS and encrypted with AES-GCM before storage in Cloudflare D1. The encryption secret is held separately in the server’s runtime secrets. The key is decrypted on the server only when needed to authenticate reporting requests to Valve over HTTPS. Stored keys are not returned to the browser, included in workspace exports or public press kits, or sent to the assistant, OpenAI, email recipients or Stripe. Private reporting requests check your signed-in account and ownership of the game. Hosting, database and recovery-backup administration are restricted to authorised operators.
Imported wishlist and sales reports are saved in your private workspace on Cloudflare. When you use the assistant, relevant saved reporting figures may be sent to OpenAI to answer your questions. If you enable progress report emails, reporting summaries are sent to Zoho for delivery to your selected recipient address. The financial API key itself is not included in either process. Financial reports are not automatically published in your press kit or shared with other Devlog users.
Disconnecting Steam reporting deletes the saved encrypted key for that game from the active database and stops future use of that connection. It does not revoke the key at Valve or delete reports already imported. Requests already in progress may finish. If you connected the same key to other games, disconnect those connections separately. Permanently removing a game deletes its saved reporting connection and imported reporting data from the active database. Contact hello@devlog.studio to request account deletion. Encrypted recovery backups may retain earlier copies after active records are deleted; those copies are not used for normal app access. To invalidate a key at its source, revoke it through Steamworks.
Public press kits
Press kits start as private drafts. Publishing makes the text, contact email and selected images you approve publicly accessible on Devlog, including to search engines. We do not publish your account email, sales, wishlists, conversations or private notes as part of a press kit. Images are stored on Cloudflare R2 and count toward your account storage. YouTube trailers use an embedded player, which sends requests to YouTube when it loads and during playback. External trailer-download links take visitors to the developer’s chosen provider. Unpublishing stops Devlog serving the page and its public asset links, but cannot remove copies that visitors have already downloaded or search engines have cached. Deleting the game also removes its press kit and queues its uploaded files for deletion.
Published press kits record daily totals for visits, asset download clicks and clicks to Steam, the linked website and trailer downloads. These totals are visible only to the workspace owner. Engagement records do not include visitor identities, email addresses, IP addresses or browsing histories. Engagement tracking does not set cookies or use browser storage. Hashed IP-based request limits help prevent abuse and are separate from engagement totals. Aggregate engagement is stored with the game workspace and deleted when the game is permanently removed.
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 records public Steam online-player counts when you open a game and during enabled background monitoring, including linked demos. These are observations of simultaneous players, not records of individual players or unique people who played.
Creator outreach
Creator shortlists, saved contact emails, outreach stages, private notes and follow-up dates are stored with your game. They are included in account exports and removed when the game is deleted. Removing a creator from a shortlist archives the outreach record so it can be restored. Notes are not sent to creators or used to generate messages.
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. Public social counts may be refreshed during enabled background checks. Devlog does not reconstruct counts from before tracking began.
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.
Information we access and collect
Devlog uses YouTube API Services for game coverage discovery and public channel tracking. We access and store public video and channel IDs, names, handles, URLs, video titles and descriptions, publication dates, thumbnail URLs, and available subscriber, video, view, like and comment counts. This can include public information about creators whose channels you do not own. We store the time information was checked and dated observations for the tracking history. We do not access private channel analytics, viewer demographics, watch history, comment text or private videos. YouTube tracking does not request permission to access your YouTube account.
We associate saved YouTube results with your private Devlog account and selected game. This includes your account identifier, game name and Steam app ID, search requests and filters, channel handles or URLs you enter, video assignments, ignored items, timeline notes, and monitoring and notification preferences. Your sign-in name and email, where provided, are handled as described in the account sections of this policy. Adding a public channel does not verify that you own it.
How we use YouTube information
We use game names and search requests to find relevant public videos, check their relevance, avoid duplicate coverage, and display source-linked coverage in your workspace and timeline. Channel and video totals support the statistics, changes between saved observations and history charts displayed in Social media. Your preferences control scheduled checks, updates, and coverage information included in your enabled notifications and reports. Channel-to-game matching uses rules; AI-assisted coverage research can also assess relevant public metadata. Devlog does not upload videos, post comments or change channels through these features.
Who receives YouTube information
Google and YouTube receive API requests containing the search terms, video IDs or channel references needed for the requested feature, together with Devlog’s server connection information and project API credential. Viewing remotely hosted thumbnails or loading embedded YouTube videos connects your browser to Google or YouTube, which can receive your IP address, browser information and information about the requested content under their own policies.
Cloudflare processes and stores the YouTube information associated with your workspace as our hosting and database provider. Encrypted recovery copies are handled under the storage and backup arrangements described above. When AI-assisted research or an assistant conversation uses YouTube information, we send relevant search requests, public video or channel metadata and relevant saved card contents or notes to OpenAI to produce or verify the response. A standard public-channel tracking refresh uses YouTube API requests and matching rules rather than sending its library to OpenAI.
Your saved results, assignments and notes are visible to you in your signed-in workspace. The Devlog operator may access relevant records when necessary for support, maintenance, security or legal obligations; service providers process information to operate these features. Coverage information is included in emails only according to the notification and report settings you choose. We do not sell YouTube information, share it with advertisers or publish your private coverage library as a public creator directory.
Your choices and removal
You can stop scheduled checks in Monitoring, change notification preferences, ignore or remove coverage entries, and remove tracked channels in Social media. The 29-day tracking retention described below applies to the tracking cache and statistical observations. Separately saved coverage entries, user notes and assistant conversations follow the workspace retention arrangements in this policy. Contact hello@devlog.studio to request deletion of your account or associated YouTube information.
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 public YouTube data to provide your private workspace and does not sell it or use it for advertising. Assigning tracked channel videos to games uses matching rules rather than AI. Assistant research and conversations can send relevant public video information and saved card contents to the OpenAI API, as described 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, saved card context and candidate coverage details may be sent to the OpenAI API. This can include public YouTube video titles, descriptions, channel information and statistics used to assess whether coverage matches your game. Research may access public websites. Steam requests retrieve public store information or private reporting where connected; YouTube requests use Devlog’s server-side API key to retrieve public coverage and channel data. Your connection credentials 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 accounts with active Pro or Portfolio access and 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 coverage alerts and daily or weekly progress reports 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 and extend complimentary account access, suspend accounts and revoke sessions; these changes and expiry dates are recorded. Access start, extension, upcoming expiry and end notices use your verified email independently of optional coverage reports.
Email delivery
Sign-in codes, enabled coverage alerts and progress reports are delivered through Zoho CPaaS. Your recipient address and email content are sent to Zoho for delivery. Email open and link-click tracking are disabled. You can unsubscribe from optional discovery emails without disabling sign-in codes. Delivery and request records help prevent duplicate messages and investigate failures. Administrators can connect a Zoho Mail mailbox to compose personal branded messages. The sender and recipient addresses and message content are sent to Zoho Mail; drafts and sending history are saved privately in Devlog. Connection tokens are encrypted.
Connected mailboxes and outreach emails
You can connect several Gmail, Google Workspace, Outlook or Zoho Mail mailboxes to send emails you review and approve. Devlog requests sending permission and basic account identity, not inbox-reading permission. Connection tokens are encrypted. Drafts and sending records are saved privately with your account. Sending shares the sender, recipient and email content with your selected email provider for delivery. Assistant drafting sends your writing instructions, current draft, game description and selected creator name and profile to OpenAI; it does not read your mailbox. Replies stay in your normal inbox. Remove a mailbox in Devlog to delete its stored connection, or revoke permission in your provider account. Saved drafts and sending history remain until their associated game is removed. No email open or click tracking is added.
Devlog’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google API Services User Data Policy
How Google data is shared
Devlog uses Google account identity to sign you in and identify mailboxes you choose to connect. Google receives authentication requests and, when you approve sending, the sender address, recipient address, subject and message content needed to deliver your email. Intended recipients receive the email you send. Cloudflare provides Devlog’s hosting and database infrastructure and processes stored account identity, encrypted mailbox connection credentials, drafts and sending records on our behalf. When you ask the assistant to draft an email, OpenAI receives your instructions, current subject and message body, your Devlog display name, and relevant game and selected creator details. This can include a display name originally supplied by Google. Google credentials are never sent to OpenAI, Zoho, Stripe or email recipients. Devlog does not sell Google user data, share it with advertisers or data brokers, or use it for targeted advertising. Disclosures to authorities occur only where required by law; limited access may be necessary to investigate security incidents. Human access to Google user data is limited to your explicit consent, necessary security investigation or legal obligations.
How Google data is protected
Connections to Google and Devlog use HTTPS to protect data in transit. Gmail refresh tokens are encrypted with AES-GCM before database storage, using a server-side encryption secret. Access tokens are used on the server for an authorised request and are not stored with your drafts or exposed to the assistant. Private workspace requests check the signed-in account and ownership of the requested records. Sign-in sessions use secure HTTP-only cookies and stored token hashes; Google connections use state, nonce and PKCE checks to protect the consent flow. Hosting and database administration are restricted to authorised operators. These controls also protect the Google account identifiers and email addresses associated with your workspace.
Google data retention and deletion
Google sign-in identifiers, verified email addresses and saved profile details are retained while your Devlog account exists. Sign-in does not retain a Google access token or refresh token. Connected Gmail mailbox identifiers, sender addresses and encrypted refresh tokens are retained until you remove that mailbox from Email. Removing a mailbox deletes its saved credentials and pending connection flows immediately, but leaves your saved drafts and sending history available. You can also revoke Devlog’s permission in your Google Account; revocation stops Google API access but does not itself delete saved workspace records. Drafts and sending records, including their sender and recipient addresses, subjects and message bodies, are retained until their associated game is permanently removed. Archived drafts remain stored until that removal. To request deletion of your entire account and its Google-related data, email hello@devlog.studio. Account deletion is handled by the site operator, not a self-service button. Email already delivered to Google or a recipient remains subject to their own retention controls. Public YouTube data follows the separate 29-day retention rules described above.
Connections and API keys
Your Steamworks reporting key and Bluesky credentials are encrypted before database storage. Disconnecting a connection removes its saved credentials; it does not erase reports already saved in your workspace. YouTube tracking and discovery use Devlog’s server-side API key. Users do not need to provide their own YouTube API key or grant access to their YouTube account.
Subscription payments
When you start a subscription, Devlog sends your account display name and verified contact email, if available, to Stripe to identify your billing account. Devlog stores payment-provider customer and subscription identifiers, plan, billing status and access dates. Card details and payment transactions are handled by Stripe and Link, rather than stored in Devlog. Stripe’s privacy policy explains how payment information is processed.
Feedback you send
Feedback is stored privately on Cloudflare with your account identifier, the selected game and the app section you were using. If you ask for a reply, we also store the email address you provide. The site operator uses this information to investigate problems and improve Devlog. Passwords, API keys, email drafts and financial reports are not collected automatically. Feedback is retained until you request its deletion or your account is deleted. To request deletion, contact hello@devlog.studio.
Saved history and controls
Saved workspace records remain until removed, except for service-specific expiry rules such as the YouTube retention policy above. 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 export your workspace, remove tracked channels, disconnect integrations and disable optional monitoring. Contact hello@devlog.studio to request account deletion or ask about saved data; full account deletion is not currently self-service.
Contact and updates
Devlog is operated by Craig Bryant. Contact hello@devlog.studio for privacy questions, access or deletion requests. This notice is updated when our features or data handling change. Last updated: 21 October 2026.