YARRAPOST · UPDATED 10 SEPTEMBER 2026

Privacy policy

Who operates this service

YarraPost is operated by Yarra Systems. Contact support@yarrapost.com for privacy questions, access, correction or deletion requests.

Information we handle

We store workspace and identity details, sign-in identifiers and email addresses, connected channel identifiers and labels, encrypted provider credentials, uploaded media, draft and approved post content, schedules, delivery results and publication links. We also retain activity records, API idempotency records, invitation and sign-in records, webhook configuration and delivery records, and deletion requests.

Why we use it

We use this information to authenticate people and agents, enforce workspace permissions, connect channels with your consent, validate media, obtain approval, publish or schedule the approved content, recover interrupted deliveries and show the outcome. Sign-in challenges and request limits help protect access. Operational diagnostics help investigate failures.

Google and YouTube data

Google sign-in identifies your YarraPost account. Connecting YouTube is a separate authorization: YarraPost accesses channel information to identify your destination, uploads your selected videos, and reads video status to confirm processing and publication. YarraPost uses YouTube API Services. See the Google Privacy Policy. You can revoke access through your Google account permissions and request deletion of stored data as described below.

Sharing and service providers

Content and media are sent to the social networks you select for publishing. Cloudflare provides hosting, database, object storage and email infrastructure. Workspace administrators control access for other people and agents. If an administrator configures a webhook, workspace event data is sent to that endpoint. Published content is subject to the selected network’s visibility settings and policies.

YarraPost does not provide AI content assistance. Agents you authorize may access workspace data through the API or MCP according to their permissions; review the practices of any agent service you connect.

Cookies and credentials

We use essential session and sign-in flow cookies. If you use a workspace bearer credential in the browser, it is held in session storage. Provider credentials are encrypted before storage. Keep account and agent credentials private.

Retention and deletion

Workspace content and publishing records remain stored until removed through a verified deletion process. Disconnecting a channel removes its stored connection credentials but does not erase posts, media or all delivery records. A deletion request is reviewed before erasure, including any active publishing operation. Backup and operational-log retention must be confirmed as part of the deletion response; we do not describe those copies as immediately erased.

See data deletion instructions. Deleting YarraPost data does not remove content already published on a social network. Manage that content on the network itself.

Changes and questions

This policy will be updated when the service’s data handling changes. Contact the operator above if you need information about your data or believe it has been handled incorrectly.