Privacy policy

The short version

• Three cookies, all first-party: a login session, an anonymous view key, and your light/dark preference.
• No analytics service, no ad-network pixel, no social buttons, no fingerprinting — none of that exists in the codebase.
• Adverts are files we host ourselves and serve from our own media path, so displaying one tells nobody else you were here.
• View counts are counted against a random cookie value, never against a name, an email, or an IP address.
• Deleting your account deletes your comments, messages, saves and playlists with it.

Browsing without an account

The first time a video registers a view we set a cookie called tube_anon:

• its value is 16 random bytes, generated on our server, tied to nothing else about you;
• it is httpOnly and sameSite=lax, so scripts on the page cannot read it and it is not sent to other sites;
• it lives for one year, or until you clear your cookies.

That key is written into exactly three kinds of row:

• Views — video id, the random key, and a timestamp. One row per video per key, so replays do not inflate the count.
• Heartbeats — video id, the random key, and a “last seen” time, which is what the “being watched now” numbers are built from. A background job deletes every heartbeat older than five minutes, so this data disappears minutes after you stop watching.
• Reactions — if you like or dislike a video without signing in, the like is stored against the same key so the button remembers its state.

We do not store your IP address alongside those rows, and we do not attempt to identify you from them. Whatever web server or CDN sits in front of the application may keep its own short-lived access logs, which is standard for any site on the internet.

The theme cookie

Switching between light and dark (the rope in the header) writes tube_theme=light or tube_theme=dark, valid for a year. The server reads it so the first paint is already in the right theme. It contains nothing but that one word.

If you create an account

We store:

• Email address — used to sign in, to reset a password, and to reach you about your account. It is never shown to other members.
• Username — public. It appears on your comments and on any playlist you make public.
• Password — only as a salted scrypt hash. The original is never written to disk, never logged, and cannot be recovered by us or by anyone who steals the database table.
• Optional profile — display name, short bio, and an avatar image, which is re-encoded on upload so nothing hidden in the original file survives.
• Two-factor secret — only if you switch two-factor authentication on.
• Sign-up date, and a ban timestamp if an account is suspended.

Signing in creates a session row and sets the tube_session cookie: a random token,httpOnly, valid for 30 days. Logging out deletes the row, and expired rows are cleaned up automatically. The cookie carries no personal data — it is only a lookup key.

What you create while signed in

• Comments — public, shown with your username and the time you posted. Comments containing links are rejected on submission and are never stored.
• Favourites, watch later, and model follows — private to you.
• Playlists — private unless you mark one public, in which case its name and contents can be seen by anyone with the link.
• Private messages — stored as plain text in our database so they can be delivered and shown to you. They are not end-to-end encrypted, and staff can read them when investigating an abuse report.
• Reports — the reason you picked, anything you typed, and the email address you gave if you were not signed in.

Staff actions in the admin panel are written to an internal audit log with the staff username and the IP address they acted from. That log is about our own people, not about visitors.

What we do not do

There is no Google Analytics, no Meta pixel, no TikTok pixel, no ad-network tag, no heatmap recorder, no session replay, and no social share widget anywhere in this codebase. Advertising creatives are uploaded by us and served from our own media path, so no third party learns which page you were on. Web fonts are downloaded at build time and served from this domain, so viewing a page makes no request to a font provider. We do not sell, rent, or trade personal data, and we run no cross-site profiling.

The one thing we cannot control is where an advert or a friends-bar link takes you after you click it. From that moment on, the destination site’s own privacy policy applies.

Who else can see the data

Data stays on infrastructure we control: the application database, and the storage servers holding the encoded video files. The people with access are the site operators and the hosting provider that runs those machines. We disclose data outside that circle only when a valid legal order requires it, or where it is necessary to investigate abuse or protect someone from harm.

How long we keep things

• Heartbeats — deleted about five minutes after you stop watching.
• Sessions — 30 days, or immediately when you log out.
• Anonymous view rows — kept while the video exists, because they are the view count; they are removed with the video.
• Account, comments, messages, saves, playlists — kept until you ask us to delete the account.
• Reports and the staff audit log — kept as a compliance record after the case is closed.

Your choices

• Deleting your account. Email privacy@familystrokeshd.com from the address on the account. Deletion cascades: comments, private messages, favourites, watch later, playlists, and model follows go with it. Anonymous view rows survive because they are not linked to you.
• Getting a copy of your data. Ask at the same address. There is no self-service export button, so we assemble it by hand and send it to the account address.
• Correcting something. Profile details you can edit yourself are changed from your account area; anything else, including your email address, is corrected on request.
• Browsing without any of it. Clearing site cookies removes all three at once. A private window keeps them for that window only.

If you live somewhere that grants statutory rights over your data — access, correction, erasure, objection, or portability — the way to exercise them is that same email address. We handle those requests manually, and we aim to answer within 30 days. Nothing here is automated, and this policy does not claim a formal compliance programme the software does not implement. If your jurisdiction requires a named controller or a representative, that identity to be completed before launch.

Security

Passwords use scrypt with per-user salts. Media files are never public: every image and video URL is signed and expires, so a copied link stops working. The admin panel lives on a separate, configurable path and is excluded from search engines along with /api/, /media/ and /me/. No system is perfectly secure — if you find a weakness, tell us at privacy@familystrokeshd.com rather than publishing it.

Children

This is an 18+ service. We do not knowingly hold data about anyone under 18, and any account we believe belongs to a minor is deleted rather than suspended.

Changes and contact

Material changes are announced on this page. Questions, requests, and complaints: privacy@familystrokeshd.com. Copyright and content takedowns have their own route on the DMCA page.