Privacy Policy
Service operator: RL Global. Effective: 25 September 2026 · Product policy for the current Vidora service. Review with qualified counsel before relying on it as jurisdiction-specific legal advice.
1. Scope & service operator
Vidora is a service operated by RL Global. This policy covers data processed through Vidora accounts, Google/Facebook/Instagram/Threads/X/TikTok/Pinterest/LinkedIn social sign-in, Social Publishing for Facebook/Instagram/Threads/TikTok/X/Google Business Profile/Pinterest/LinkedIn/YouTube, workspace sites, Lead/Payment forms, Gatekeeper access gate, commerce, Leads, Orders, Unified Inbox, first-party analytics, third-party tracking/pixels, WhatsApp Business API, Media Library, invoice/AWB functions, domains, support and ChatGPT/MCP connections. Workspaces may need their own end-customer privacy and consent notices.
2. Account, workspace & media data
Vidora may process name, email, password hash, workspace details, plan, site content/configuration, domains, revisions, support tickets, tenant media and audio-license metadata such as creator/rights owner, license name, source URL and uploaded or linked license evidence submitted for rights review.
2A. Social sign-in & account linking
If you use Google, Facebook, Instagram, Threads, X, TikTok, Pinterest or LinkedIn to sign in or link an account, Vidora may receive the provider user ID, display name, username, email when supplied by the provider, email-verification status and avatar/profile URL, together with temporary authorization data needed to complete OAuth. Vidora stores the linked provider identity so you can sign in later; Vidora does not receive your provider password. Where a provider supplies a verified email, Vidora may use it to match an existing Vidora account. You can unlink a provider in Account & Security; if it is your last sign-in method, Vidora may require a Vidora password first. Social sign-in availability is subject to provider app status, permissions, review, policies and service availability.
2B. Social Publishing & platform connections
Social Publishing is separate from social sign-in. When a workspace connects Facebook, Instagram, Threads, TikTok, X, Google Business Profile, Pinterest, LinkedIn or YouTube for publishing, Vidora may store connection data such as provider account/channel/page/board/location IDs, display names, connection metadata, required access or refresh tokens, connection status and timestamps. Platform app credentials may be configured to reuse the same App ID/Secret as Sign-in, while user publishing tokens and connections remain separate from login identities.
2C. Social Publishing drafts, schedules & media
When Social Publishing is used, Vidora may store the main caption, platform-specific caption overrides, titles, destination URLs, selected platforms, Draft/Scheduled/Published/Failed status, scheduled time, uploaded image/video files and related technical metadata. Fields are used only for selected platforms that support that content type. Provider-side posts already published may remain on the provider after a Vidora connection is disconnected.
3. Visitor & lead data
Workspace forms may collect name, email, phone and message. Payment/shipping forms may also collect address and order details. Workspaces determine the business purpose for end-customer data collected on their sites.
4. Orders & payments
Vidora may store order number, items, totals, payment status/provider/reference and review/refund status. Merchant credentials are encrypted. Vidora should not be used to store full card numbers or CVV. Payment providers process data under their own policies.
5. Shipping
Shipping may process recipient name, phone, address, postcode/state, provider, AWB/tracking and delivery status. EasyParcel/couriers may receive required data when live integrations are used.
6. Domains & technical data
Vidora processes domains, DNS verification tokens, SSL state, IP/visitor hashes, user-agent/log data, rate-limit metadata and diagnostics needed for security and operations.
7. Analytics & attribution
First-party analytics may record pageviews, sessions, timestamps, hashed visitor identifiers, paths, referrers/referral domains, source/medium, UTM campaign/term/content, device type, browser, operating system, language, country code when available, events, conversions and order value for operational reporting and attribution. Vidora does not sell this data to advertisers.
8. Third-party pixels, tags & analytics
If a workspace enables GA4, Google Tag Manager, Google Ads, Meta Pixel, TikTok Pixel, LinkedIn Insight Tag, Microsoft UET, Pinterest Tag, Snap Pixel or Microsoft Clarity, the visitor browser may communicate directly with those providers. Workspaces are responsible for required cookie/consent notices, configuration and lawful processing.
9. WhatsApp Business API
When a workspace connects WABA, Vidora may process WABA and Business Manager IDs, WhatsApp phone numbers, template/message metadata, encrypted credentials, inbound/outbound messages, delivery status, contact name/phone and lead/order data needed for automation. Meta webhooks may deliver events to Vidora. If AI chatbot replies are enabled, required message content may be sent to the AI provider configured by the workspace.
10. ChatGPT / MCP / OAuth
Vidora processes authorization records, scopes and token/hash data required for workspace connections. Third-party AI services have their own policies.
11. Processing purposes
To provide accounts, sites, leads/orders, domains, notifications, analytics, support, security, abuse prevention, operational recovery and legal compliance.
12. Third parties
Data may be sent to or received from user/workspace-selected providers including Google/YouTube/Google Business Profile, Meta services (Facebook, Instagram and Threads), TikTok, X, Pinterest and LinkedIn, as well as payment, shipping, infrastructure and AI/MCP providers, only as required for the relevant function. Each provider has its own terms, privacy policy, permissions and review processes.
13. Security
Controls include password hashing, encryption for selected secrets, CSRF protection, rate limits, workspace scoping, HTTPS and security logs. No system is risk-free.
14. Retention & deletion
Data is retained as needed for service, security, disputes, backups/operations and applicable law. A social sign-in identity can be unlinked in Account & Security without deleting the workspace. Social Publishing connections can be disconnected separately; drafts, scheduled posts, captions and publishing media still stored in Vidora remain workspace data until deleted or the full workspace deletion process is completed. Full account/workspace deletion can be requested through Account deletion or Support; public instructions are available on the Data Deletion page. Some records may be retained where needed for security, fraud prevention, backups, disputes or legal obligations.
15. Workspace responsibilities
Workspaces must have a lawful basis for end-customer data, provide required notices/consents and avoid unnecessary sensitive data.
16. Children & sensitive data
Vidora is not designed for unnecessary collection of children’s or sensitive-category data.
17. Plans, entitlements & billing
Vidora may process plan details, free/paid website status, subscription state, billing periods, subscription-payment records and feature entitlements such as custom domains, WhatsApp Business API, Gatekeeper, team limits, storage and traffic limits. Platform-authorized showcase/unlimited workspaces may receive special entitlements without a standard subscription; the entitlement shown by the service controls actual access at that time.
18. Unified Inbox, lead/order matching & internal notes
Unified Inbox may match WhatsApp phone numbers with leads or orders in the workspace and store conversation-to-lead/order links, lead type, unread/open/pending/closed state and related attribution. Internal lead/order notes may store the note text, timestamp and the staff/admin name or role that added it for audit and team collaboration.
19. Gatekeeper, anti-bot & Traffic Guard
Gatekeeper and security controls may process request metadata, timestamps, IP or technical identifiers, rate-limit signals, request patterns, anti-bot/anti-scalper outcomes and suspension state. Vidora may use this information to prevent abuse, protect availability and investigate incidents.
20. Media, compression & quotas
Uploaded media may be processed for validation, compression/optimization, technical metadata, storage accounting and security. Workspaces are subject to the file types, size limits and quotas displayed by their plan. Compression is intended to reduce file size, but final rendering may vary slightly by format, browser or processing pipeline.
21. Analytics date filtering
Choosing 7/30/90 days, this month, last month or a custom date range only changes the reporting window being displayed. Changing a report filter does not by itself delete source data or alter the retention period described in this policy.
22. Changes
This policy may change as services or law evolve.
23. Contact
Use Support for privacy/access/correction/deletion requests and never include secrets. Public data-deletion instructions are available at https://vidora.online/?route=data-deletion.