PUBRAIL
Privacy Policy
Last updated: 15 August 2026
Controller and scope
This policy explains how PubRail, a trading brand of Zeplin Software Ltd (company number 12257869), handles information when you use the PubRail dashboard and its connected publishing integrations. Zeplin Software Ltd is the controller for its own service operations and may act as a processor where an organisation uses the service to manage its content.
Information we process
We process account and authentication details, workspace stories and prompts, generated or uploaded media, voice and caption artifacts, production and cost records, usage and diagnostic data, and the identifiers needed to publish to a destination you authorize. We do not need the password for a connected social account.
Why we process it
We use this information to provide the service you request, maintain workspace security, operate and troubleshoot production and publishing, measure usage and provider costs, prevent abuse, and meet legal obligations. Connecting a social account is optional and is based on your authorization.
Connected platforms and subprocessors
Depending on the features you use, data may be processed by AWS, Stripe, OpenAI, fal.ai, ElevenLabs, Amazon Polly, Remotion, Amazon SES, PostHog and Google Analytics. PostHog and Google Analytics are used only when enabled with the applicable analytics and consent controls. A current provider and transfer register is maintained in the product documentation and updated when providers change. YouTube/Google, Instagram/Meta, Facebook/Meta, Threads, TikTok and X are separate controllers for data processed by their own services when you authorize a connection. Processing may occur outside your country under applicable contractual and technical safeguards and each provider's own terms.
OAuth data and connected accounts
When you connect a social account, PubRail receives only the identity, destination metadata and permissions needed for the selected feature. OAuth credentials are encrypted and are not placed in browser responses, workflow payloads or logs. Platform-specific access-token expiry, renewable credentials, refresh-token rotation and retention rules apply. Disconnecting or revoking a connection stops new publication, invalidates its destinations and starts credential cleanup; provider-side revocation may have its own confirmation timing.
Storage, retention and security
Private report history and related run records are retained according to the approved private-report policy while your account or lifetime plan remains active. An account with no active subscription or lifetime plan that remains inactive for more than three months may be marked inactive and, after reasonable notice and an export or reactivation period, its content may be deleted. Operational logs have a default retention target of at least 12 months and may be retained longer where troubleshooting, security, incident response, fraud, dispute, legal, regulatory or approved operational-retention requirements make that necessary. Security and audit logs have a default retention target of 24 months and may be retained longer for an active incident, investigation, legal claim, regulatory requirement or legal hold. Billing and tax records may be retained for up to 10 years after the relevant financial year, and longer only where an active dispute, fraud investigation, legal claim, regulatory investigation or legal hold requires it. Backups follow their own expiry schedule. We use access controls, encryption and other reasonable technical and organisational safeguards, but no internet service can guarantee absolute security.
AI-assisted output
AI-generated research, scripts, images, audio and metadata can be incomplete or inaccurate. You are responsible for reviewing facts, rights, safety and destination rules before publishing.
Your choices and rights
You may disconnect a provider, stop using the service, and contact us to request access, correction, export, objection or deletion where applicable law provides that right. These requests are commonly called data-subject access requests (DSARs). Contact privacy@pubrail.com; we may ask for information needed to verify the request and aim to respond within one month where applicable. Some records may need to be retained for security, billing, audit, fraud, tax or legal obligations. You may also exercise applicable rights directly with a connected social platform, which acts as a separate controller for its own processing.
Age, markets and security contact
The service is intended for people aged 18 or over and is offered internationally where payment services, provider access, applicable law and account eligibility permit. Report security vulnerabilities or incidents to security@pubrail.com. We do not publish a physical business address on this page.
Contact
For privacy, deletion, export or correction requests, contact privacy@pubrail.com. For general questions, contact hello@pubrail.com.