Privacy Policy

Who is responsible for your data

labi.mov is the controller of the personal data described here. Privacy questions and requests can be sent to privacy@labi.mov.

What labi.mov collects

Account and security data

This includes your display name, handle, email address, password hash, exact date of birth, email-verification state, account and channel creation times, roles, preferences, referral code, the code used to join, scheduled deletion state, and any account ban, its reason, end time, and staff initiator. If you enable multi-factor authentication, the service stores passkey public-key data or an authenticator secret and recovery codes. It does not store a passkey's private key.

Sign-in records include session identifiers, expiry times, IP addresses and browser information. Attempted sign-ins record whether the email belongs to an account and the country reported by Cloudflare. Security emails may include the IP address, country, browser, operating system and time of the attempt.

Content and activity

This includes uploaded videos, thumbnails, captions, channel images, titles, descriptions, schedules, comments, replies, comment edit history, reactions, saves, follows and unfollows, blocks, reports, video appeals and their reasons, support conversations, notification state, search activity, custom channel HTML and CSS, and moderation records. Moderation records include private staff notes, review flags, warnings and their reasons, a copy of the warned video's title or comment text, withdrawals, and bans. Warnings remain on record after the related video or comment is deleted. Referral records identify who created and redeemed a code.

We keep edit history for changes to content, account preferences and moderation settings, whether made by users or staff. Only staff can review this history. Each entry records the previous and current values, time, and account that made the change. This history does not include passwords, authentication secrets or payment credentials.

Viewing and analytics data

When you watch while signed in, labi.mov records which thumbnails you see, which videos you open, counted views, watch time, playback position, pauses, skips and completed videos. It also records how you found a video, its position on the page, the website you came from, device type, operating system, browser and whether you followed the channel. Viewing records can link a video to the previous video you watched.

Cloudflare supplies country, region and continent information. Your date of birth provides an age range for audience statistics. Creators can see grouped statistics for new and returning viewers, follows, other creators their audience watches, and which videos viewers watch next. They do not receive the identities or individual histories behind these reports.

labi.mov keeps the date of your first counted view of each channel and a daily record of the channels and videos you watch. Watch time linked to your account, each video and your billing period is also used to calculate creator earnings. Signed-out viewing does not contribute to these records.

For signed-in playback, delivery records identify the video segments sent to your account and when they were delivered. These records check playback reports and provide a rough watch-time estimate when reports are missing or invalid.

When you are signed out

Watching while signed out does not create labi.mov impression, view, watch-time, playback, retention or visitor-ID records. This policy still applies to the request data needed to deliver and protect the site. Cloudflare and labi.mov may process your IP address, browser information, requested page or file, time, country, region and security signals.

Payments and payouts

Membership records include the chosen amount, status, billing period, and Stripe customer, subscription, invoice, charge, dispute, and refund identifiers. Stripe collects payment details and billing addresses directly. labi.mov does not store full card numbers. Creator payout records include the chosen payout provider, destination email or account identifier, amount, status, and provider transaction identifiers.

Data received automatically

Cloudflare may process and log request data such as IP address, request time, requested URL, browser information, network information, country, region, and security signals. Application monitoring also records request IDs, routes, response status, timing, and server errors. Publicly embedded players receive the embedding site's referrer when the browser sends it.

Why labi.mov uses this data

Provide the service

Create accounts and channels, authenticate users, host and play videos, remember settings and watch progress, send notifications, process memberships and payouts, and answer support requests. The legal basis is performance of the contract you request.

Keep the service safe

Prevent abuse, rate-limit requests, secure accounts, investigate reports, review uploads, detect technical failures, and enforce the Terms. The legal basis is legitimate interests in security, integrity, and operating a lawful service.

Recommend and improve content

Rank videos, measure impressions and viewing, calculate retention, improve playback, and provide grouped creator analytics. The intended legal basis is legitimate interests, subject to a documented balancing assessment.

Meet legal duties

Keep records or disclose information when required by tax, accounting, consumer, court, or law-enforcement rules. The legal basis is compliance with a legal obligation.

The site does not store a separate analytics visitor identifier in your browser. Sign-in, the one-time referral prompt and dismissed featured items use browser storage. The preference for hiding a dismissed featured item expires after one year. The proposed legal basis for account-linked analytics still requires legal review.

What is public

Public channel names, handles, profile images, biographies, follower counts, public videos, thumbnails, descriptions, view and reaction counts, and public comments can be seen by anyone. Unlisted videos can be viewed by people who have the link. Private and unlisted videos can be accessed by authorized labi.mov moderators and administrators for review, support, safety, and legal work.

Service providers

labi.mov does not sell your data. It sends limited data to these providers when their service is needed:

• Cloudflare: site hosting, video storage and delivery, security, monitoring and automatic captions. Video audio is sent to Cloudflare when captions are generated.
• Railway: original videos, custom thumbnails and technical file information to prepare uploads for playback and check content credentials and watermarks. Temporary working copies are deleted after processing.
• Bunny.net: original videos and technical file information for some older uploads. Copies are scheduled for deletion two hours after the processed video has been transferred to labi.mov.
• Resend: email address, subject, message content, and delivery metadata for account, security, billing, moderation, and support email.
• Stripe: account identifier, email address, billing address, membership amount, payment and subscription data, refunds, disputes, and connected-account information.
• PayPal: payout destination, amount and transaction status when a creator chooses PayPal payouts. PayPal payouts currently use its test environment.

Providers may process data outside the European Economic Area. This draft does not yet specify the transfer safeguards for each provider.

How long data is kept

• Unverified account registrations are deleted after 24 hours.
• Email-change requests store the current and requested email addresses, a link-token hash and the confirming session. Links expire after one hour. Completed requests are removed immediately; expired requests are removed during daily cleanup.
• Edit history is kept for one year, including after individual content is deleted. Account deletion removes the account's content and preference history. Separate moderation and legal records follow their own retention rules.
• Playback delivery records and processed server estimates are kept for two days. Counted watch time follows the viewing and billing retention periods below.
• Incomplete upload sessions expire after 24 hours.
• Original source videos are scheduled for deletion 120 minutes after transcoding finishes. Encoded video, thumbnails, and captions remain while the video is active.
• Detailed thumbnail-impression and playback records are deleted after 90 days. Temporary data used to build retention charts is deleted after 2 days. Counted-view records and account-linked daily viewing records are deleted after five years.
• Viewing sessions, including the positions reached in each video, are kept for five years. The date of your first counted view of a channel remains while both your account and that channel exist. Saved watch progress remains until the account or video is deleted. Account deletion removes your identity from viewing sessions before their five-year expiry. Grouped creator statistics remain while the video exists.
• Development-only email outbox entries expire after 1 hour.
• Pending delivery messages are encrypted. Account-action messages expire after 1 hour; other messages expire after at most 23 hours. Their stored contents are removed after sending or a terminal delivery failure. Delivery metadata, including recipient, provider ID, status, attempt count, and timestamps, is removed after 30 days. Bounced or suppressed addresses remain on a suppression list until removed so the service does not repeatedly send undeliverable email.
• Account and channel deletion normally has a 30-day recovery period. A successful sign-in cancels account deletion. A legal hold can pause deletion.
• Billing, payout, moderation, security, audit, and support records are kept while needed for the service, disputes, fraud prevention, or a legal duty. Final production retention periods still need to be set for these records.

Deletion from active systems does not necessarily remove data immediately from provider backups. Provider backup schedules must be confirmed before production.

Recommendations and automated checks

Recommendations use viewing, reactions, follows, saves, comments, category, freshness, popularity, and explicit feedback such as “Not interested.” The system also limits repeated channels and excludes blocked or hidden content. Creators receive grouped results, not a list of individual viewers.

Uploads can be checked for Content Credentials and invisible watermark signals. A signal can place content in the moderation queue, but it does not automatically decide that the content is prohibited. A moderator can review the content and override a false positive. These systems do not make decisions with legal or similarly significant effects without human review.

Your choices and rights

You can change profile details, notification and playback preferences, reactions, follows, saves, comments, and channel content from the service. You can schedule account deletion from Settings.

You may ask for access, correction, deletion, restriction, portability, or an objection to processing. Where processing depends on consent, you may withdraw it without affecting earlier lawful processing. Send a request to privacy@labi.mov. Identity may need to be verified before a request is completed.

You may also complain to the data-protection authority where you live or work, or where you believe a data-protection violation occurred.

Children

You must be at least 16 years old to create an account. The date of birth is used to enforce that rule and to produce grouped age-range analytics. Exact dates of birth are not shown to creators.

Security

labi.mov uses hashed passwords, email verification, optional passkeys or authenticator codes, session controls, rate limits, restricted staff actions, request validation, and audit records. No system can guarantee absolute security. Report a suspected account or data breach to privacy@labi.mov.

Changes

Material changes will be explained before they take effect when required. The date at the top will change whenever this policy changes.

See also the Terms of Service.