Pubzo · development service
Privacy policy
This notice explains how The Help handles information for the Pubzo development website and publishing workspace.
Last updated: 26 October 2026.
Information processed
The publishing workspace processes information you provide or authorise through a connected platform:
- Account or channel identifiers, usernames and profile details needed to identify the connected account.
- Access and refresh credentials issued by a platform after you authorise access.
- Videos you select, file metadata, titles, captions, audience and visibility choices, and publication or scheduling details.
- Local workspace membership, essential session information, timestamps and operational records used to check publishing outcomes.
If you email support, we receive the message, your email address and any information you choose to include. Do not send passwords, access tokens or other secrets by email.
How information is used and shared
We use this information to connect the account you choose, prepare and carry out reviewed actions, display their status, resolve interrupted operations and provide development support.
When you authorise a connection or confirm a platform action, the relevant information is exchanged with the selected provider, such as Google/YouTube, Meta/Instagram or TikTok. Provider terms and privacy policies also apply to their processing. A connection alone does not authorise a new post.
During local testing, a configured HTTPS tunnel may carry authorisation returns or an expiring link for a video explicitly prepared for a provider. Its operator can process the network requests passing through that service. A tunnel does not make the whole publishing workspace public.
The public information site is prepared for hosting on Cloudflare Pages. Hosting and email providers may process network, delivery and security information needed to operate their services. Our page code does not set cookies, use advertising trackers or load analytics. The separate local workspace uses an essential session cookie.
Storage, protection and retention
Development workspace data is currently stored in the operator's local development database and video storage. Provider credentials are encrypted on the server with a server-held key. They are not included in this public website.
We have not set a single automatic retention period for all prototype records. Drafts, media and operational records can remain until they are removed or the development environment is reset. Local disconnection disables the connection; encrypted records from interrupted authorisation or cleanup may remain while those operations are resolved. Contact us to request deletion of development data.
Removing local records or disconnecting an account does not delete content already sent to a platform. Those posts remain subject to that platform's controls.
Your choices and contact
You can stop testing, disconnect a local account and remove Pubzo's permissions in the connected platform's app-permission settings. Contact us to ask about your development data, request correction or deletion, or raise a privacy concern. We will use an appropriate way to check that the request relates to your account.
We will update this notice when the development service or its data handling changes. The date above identifies this version.