본문으로 건너뛰기
Pellio

Privacy policy

What we collect, why, who processes it for us, how long we keep it, and what you can ask of us. The terms of service, the affiliate terms and the copyright notice page cover their own subjects.

Last updated 25 October 2026.

1. Who we are

  • Pellio is run by ScaleMath Ltd, 128 City Road, London EC1V 2NX, United Kingdom (company registered in England and Wales; VAT number GB417393977). Write to support@pellio.io about anything in this policy.
  • This policy covers pellio.io, the Pellio app (pellio.io/app), the API (api.pellio.io), the player (play.pellio.io and the embed script customers put on their sites), the WordPress plugin, and our emails.

2. Two roles

  • For visitors to pellio.io, people with a Pellio account, people who write to us and affiliates, we are the controller: we decide what we collect and why, and this policy applies in full.
  • For people who watch videos our customers host with Pellio ("viewers"), the customer is the controller and we are their processor. What a customer collects about you through their videos (whether you are identified by name or email, whether a lead form is shown) is their decision, under their own privacy policy. We process viewer data only on their instructions and as described in section 5.

3. What we collect from visitors and customers

  • Account: your name, email address, password (stored as a hash) or Google sign-in, two-factor settings, profile picture, and the workspaces you belong to.
  • Content: the videos, captions, transcripts, thumbnails, titles, descriptions and settings you upload or create, and the share links, embeds and playlists you make. Videos and Pellio Drive files are stored with our storage provider, and a copy of each original video with a second provider (section 7).
  • Billing: the name, billing address and VAT number you give us, the plan you choose, invoices and receipts. Card details go to Stripe and never reach our servers; we keep the card brand, the last four digits and the expiry date to show you which card is on file.
  • Usage and security: sign-ins (time, address, browser), API keys and their use, connected apps, the audit log of changes in your workspace, storage and bandwidth use, and server logs kept for security and troubleshooting.
  • Support and forms: what you send through "Help & support" in the app, the contact form, the beta access request, the report-a-video form, DMCA notices and counter-notices, and our replies. Support requests are handled in Missive (section 7).
  • Affiliates: your application, your affiliate code, clicks on your link (as counts per day; a visitor’s address is kept only as a hash, for that day), the workspaces linked to you, commissions, and the bank details, address and VAT number you give us to be paid.
  • Emails: whether an email we sent bounced or was marked as spam, so we stop sending to addresses that can’t receive mail.
  • Marketing attribution: how you found Pellio. When you arrive on pellio.io from an ad, a tagged link (UTM parameters), an affiliate’s link or another website, we record that visit: the ad platform’s click id, the campaign tags, the referring site (without its query string), the page you landed on, your language and approximate country. When you ask for access or create an account, those visits are linked to your request or workspace, together with the ad platforms’ own browser identifiers (section 6), so we can see which campaigns bring customers and what they go on to buy.

4. Why, and on what basis

  • To provide the service you signed up for: hosting, playing and protecting your videos, analytics, billing, support (performance of a contract).
  • To keep Pellio safe and running: sign-in security, fraud prevention, abuse and copyright handling, backups, monitoring (our legitimate interests, and legal obligations such as copyright law).
  • To run the affiliate program and pay affiliates, and to keep the financial records the law requires (contract and legal obligation).
  • To send you emails about your account, your videos, your billing and your requests. Reports and marketing emails are opt-in and every one has a way to stop them. We don’t sell personal data and we don’t show advertising.
  • To measure and improve our own marketing: which ads, campaigns and websites bring visitors who sign up and pay, and to tell the ad platforms we use when someone they showed an ad to signs up or pays, so they show our ads to people likely to find Pellio useful (our legitimate interests).

5. Viewers: what the player records

  • When a video plays, the player sends us: which video, how much of it was watched and when, playback quality (start time, stalls, errors, resolution), the browser and device type, the page the video is on, and the viewer’s IP address, from which we derive an approximate country and then discard the address from analytics. This lets customers see how their videos perform.
  • If the customer’s site or learning platform identifies you to the player (a name, an email, a learner ID), or you fill in a form in the video, the customer sees who watched. Pellio shows that only to the customer’s workspace and to integrations the customer connects (their CRM, their LMS, Zapier).
  • For compliance features (watch-to-complete lessons, attestations, learner logs, SCORM and cmi5 packages), the player records the seconds actually watched so the customer can prove completion.
  • A viewer can report a video from the player ("Report this video"); the report goes to our trust and safety team.
  • To exercise your rights over viewer data, contact the customer whose video you watched; we help them answer. Write to us if you can’t reach them.

6. Cookies and local storage

  • Signing in sets a session cookie on pellio.io so you stay signed in; a second cookie protects against cross-site request forgery. They are first-party and deleted when you sign out or the session expires.
  • Preferences such as your theme, the workspace you were last in, and unsent drafts are kept in your browser’s local storage, never sent anywhere.
  • If you arrive through an affiliate’s link (a pellio.io address with ?ref=), we set a first-party cookie named pellio_ref holding the affiliate’s code for 60 days, so they are credited if you create a workspace. It contains nothing about you and is not used for anything else. Delete it in your browser settings if you’d rather we didn’t keep it.
  • The player sets no cookies to track you across sites. When a customer runs an A/B test on a video, a small partitioned cookie on play.pellio.io remembers which version you saw so it doesn’t change between visits; it cannot be read by other sites.
  • Every visit to pellio.io gets a first-party cookie named pellio_vid: a random identifier, kept for 400 days, that links the visits we record for attribution (section 3) to a later access request or account. A second cookie, pellio_lt, remembers the last such visit for 30 minutes so a reload isn’t counted twice, and pellio_evt holds a random event id for ten minutes while you create an account.
  • On pellio.io’s public pages and the sign-up page (never inside the app), we use Google Analytics and Google Ads, the Meta Pixel, the LinkedIn Insight Tag, the X Pixel and the TikTok Pixel. They set their own cookies (such as _ga, _gcl_aw, _fbp, _fbc, li_fat_id, _twclid and _ttp) to measure visits and to tell each platform when someone it showed an ad to asks for access or signs up. Your browser’s settings or a content blocker can stop them.
  • We honor Global Privacy Control. If your browser sends the GPC signal, pellio.io sets no pellio_vid or pellio_ref cookie, records none of your visits for attribution and loads none of the analytics and advertising tags listed above. Our /.well-known/gpc.json file declares this.

7. Who else processes data for us

  • Amazon Web Services (hosting of our servers, database and cache, in London, United Kingdom), Cloudflare (network security and delivery for pellio.io, api.pellio.io and play.pellio.io, and storage of uploaded videos and Pellio Drive files in Cloudflare R2, primarily in Western Europe), Backblaze (a copy of every original video, for safety), Stripe (payments and invoices), Postmark (sending our emails), Missive (our support inbox), Google (sign-in with Google, if you use it), ElevenLabs (AI dubbing, only for a video whose owner orders a dub, and transcription, only for a Pellio Review file a team member asks to transcribe), Z.ai (drafts of titles, descriptions, chapters, tags and posts in Pellio Review, only when a team member asks; it receives the file’s transcript and the workspace’s style guide), Revolut (paying affiliates), Better Stack (error reports from our servers: what failed and where in our code, the page or address without its query string and your browser type; never cookies, emails or what you typed), and MaxMind’s GeoIP database (run on our own servers to turn an IP address into a country; nothing is sent to MaxMind).
  • Advertising and analytics platforms: Google (Google Analytics and Google Ads), Meta (Facebook and Instagram ads), LinkedIn, X and TikTok. Besides their tags on our public pages (section 6), our servers tell them about sign-ups, trials and payments that came from their ads: the event, its value, the ad platform’s click id and browser identifiers, the IP address and browser of your latest sign-in, and your email address as a one-way hash (SHA-256), never in readable form. Each uses it under its own terms to measure our ads and, in some cases, its own services. If your browser sends the Global Privacy Control signal when you ask for access, create an account or use the app, our servers send none of this to any of them, then or later (trials, payments and plan changes included); we keep the record for our own reporting only.
  • Our help center, blog and changelog are published from a WordPress site we run; reading them involves no account.
  • YouTube: if you connect a YouTube channel, Pellio uses YouTube API Services (Google) to upload the videos you choose with their title, description, tags, thumbnail, captions, playlist and schedule, and to read their YouTube statistics to show them in Pellio. We store a token for each connected channel (encrypted) and the YouTube ids and statistics of videos uploaded through Pellio; we don’t access other videos or data in your Google account. Google’s Privacy Policy (policies.google.com/privacy) applies to what Google does. Disconnect a channel in Pellio to delete its token, or remove Pellio’s access at myaccount.google.com/permissions. Pellio’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
  • Integrations you connect yourself (HubSpot, Mailchimp, Customer.io, ActiveCampaign, Klaviyo, MailerLite, Marketo, Segment or RudderStack, Zapier, an LMS, an AI assistant through MCP) receive the data you choose to send them, under their own terms.
  • Some of these providers are in the United States. Transfers from the UK rely on the UK-US data bridge where the provider is certified, and otherwise on the International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses.

8. How long we keep things

  • Your account and content: while your account exists. A video you delete stays in the Trash for 30 days, restorable, then it and its files are removed; the safety copy of the original is removed within a further 30 days. When you delete your account, the same applies to everything in it.
  • Viewer analytics: as long as the customer’s workspace exists, so their statistics stay complete.
  • Invoices, receipts, affiliate payouts and other financial records: six years after the year they relate to, as UK tax law requires.
  • Support conversations, reports and copyright notices: kept after the account is closed, so we can show what was said if a dispute arises. Evidence kept for a trust and safety decision is retained for one year.
  • Server and security logs: a short period, measured in weeks.
  • Marketing attribution: visits linked to an access request or a workspace are kept as long as the workspace exists (or the request, if no account follows), so we can tell where customers came from years later; visits never linked to either are deleted after 13 months. What the ad platforms keep is set by their own policies.

9. Your rights

  • You can see, correct, download or delete the personal data we hold about you, object to or restrict some processing, and withdraw consent where we rely on it. Most of this you can do yourself in Settings; for the rest, write to support@pellio.io and we answer within a month.
  • You can complain to the Information Commissioner’s Office (ico.org.uk) or, if you are in the EU, to your national data protection authority. We would rather hear from you first.
  • Pellio is for businesses and adults; we don’t knowingly collect data from children under 16, and we delete it if we learn we have.

10. Changes

  • We update this policy when the service changes. The date below says when; a material change is announced by email to account holders before it takes effect.