Privacy
Last updated 13 October 2026
Draft — not yet reviewed by a lawyer. This privacy notice describes what the platform actually does today, written from the database schema and the code rather than from a template. It has not been reviewed by counsel and should be before anyone relies on it. If something here does not match how the product behaves, the product is right and this page is wrong — tell us at mail@reallyfeproductions.com.
Reallyfe Street Starz — the community, the website and the iPhone app — is run by Reallyfe Productions, LLC, 1801 N Pearl Street #513, Dallas, TX 75201. This page says what we hold about you, why, where it is kept, who else gets it, how long we keep it, and what you can do about it.
Where your data lives
- Servers we rent from Hetzner in Hillsboro, Oregon, USA (shared with the company’s other projects). The database, the photos, audio and video you upload, the live audio and video server (LiveKit, which we run ourselves) and our visit counter (Umami, also ours) all run there. Your account data is not kept by a third-party app platform.
- Backups. The database is backed up every night on the server, and encrypted copies go to Backblaze B2 in the US, where daily copies are kept for a week and weekly copies for about four weeks. The copies on the server itself have no fixed deletion schedule yet.
What we collect
| Data | Why we hold it | When |
|---|---|---|
| Email address and password | To identify your account and sign you in. The password is stored only as a salted hash by our sign-in service — we never store or log it in readable form. | You create an account |
| Apple or Google sign-in | Your name and email from Apple or Google. The name becomes your handle and display name; we don’t use their photo. | You choose “Continue with Apple / Google” |
| Two-step verification | The authenticator-app link, held by our sign-in service. | You turn it on in Settings |
| Handle, display name, bio, photo, cover, interests | Your identity in the community; interests shape what you see first. | You sign up, finish setup or edit your profile |
| Your birthday | Asked once, to set your account up for your age. Under 18, you have a teen account: only people you follow can message you, nothing can be bought, 18+ rooms and videos are hidden, going live, giveaways and tournaments are off, ads are limited and your profile isn’t suggested to adults. It switches off by itself on your 18th birthday. Your birthday is never shown on your profile or to other members; only our team can see it, to correct it when you or a parent ask (it can’t be changed in the app). An under-13 answer is never kept, and no account is made. | You join, or answer the one-time birthday question |
| Posts, replies, reactions, episode comments, photos, audio and video you upload | They are the community; other members see them. | You post |
| Direct messages and group chats | Delivered to the people in the conversation. A message someone reports is seen by our moderators. | You send a message |
| Room chat, live audio and video | Audio and video are carried live to the people in the room and aren’t kept unless the room is recorded (a recording shows a notice to everyone in it). Room chat is saved with the room. A Super Chat shows your name, message and amount to the room. | You chat, speak or go on camera in a live |
| Points, XP, badges, missions | Your balance, your level and the Wall. Points and XP are kept as append-only ledgers. | You take part |
| What you watch and how you use the feed | Which posts you see, open, react to, skip or hide; what you play and how long you watch; which lives you were in and how you got there; where you followed someone. Used to recommend posts, episodes and people to you (the feed also weighs who you message and who replies to you), and to give creators counts, never names. Watch time on a video post and “when your followers are online” only show once at least 3 people are counted; other counts can be as small as one. | You use the feed, Watch and lives |
| Where you came from | Before you have an account, a cookie notes the campaign tags in the link you followed, the website that sent you (its address, not the page), the page you landed on and whether it was an invite. It is saved once with your new account (and is in your data download) so we can see which posts bring people in; the reports our team reads never name anyone. | Your first visit, saved when you sign up |
| Invites | The invite code you followed, who invited you, and a scrambled (hashed) form of your IP address so invites can’t be farmed. Your inviter sees your handle, name and whether the invite counted. | You join from an invite |
| Sign-up and sign-in protection | Hashed forms of your IP address and email at sign-up, and a count of wrong passwords, to stop abuse. Our sign-in service also keeps its own record of sign-ins and sessions, which normally includes the IP address and browser; an hourly check reads it, may email you a fresh sign-in link, and tells our team about an account that looks under attack. | You sign up or sign in |
| Days active and kind of device | One word per active day (iPhone app, iPhone web, Android or computer) and when you were last active. It shows as “Active now” only to people you message with, if you allow it, and it also decides “we miss you” emails, whether an invite counts, and a creator’s “when your followers are online”. | You use the site |
| Push notification details | For web push: your browser’s push address and its identifying string (browser, version, operating system). In the iPhone app: Apple’s push token, the app’s install ID and version, and lock-screen live tokens. | You turn notifications on |
| Membership, purchases and Stripe / Shopify IDs | Your tier, what you bought (memberships, gifts, tips, room tickets, Vault unlocks, bookings, sponsorships) and the IDs that connect you to Stripe and Shopify. No card numbers; we keep your card’s brand, last four digits and expiry date to remind you before it expires. | You subscribe or pay for something |
| Ads you see | Each ad shown to you, whether it was on screen, how much of a video ad played, clicks, and after a click whether you added to the bag or checked out (with the bag’s value), under a scrambled ID made from your account (or, signed out, from rf_vid). Used to cap how often you see an ad and for sponsors’ counts. Spotlight link clicks are counted the same way. | You see or click an ad |
| Payout account (creators) | If you receive tips or sell room tickets, Stripe collects your identity and bank details for payouts; we keep only the Stripe account ID and its status. | You set up payouts |
| Giveaway entries | Name, email, postal address, optional phone and your 18+ confirmation, from every entrant, because an entry is only valid if the prize can be delivered. Used to run the giveaway and send the prize. | You enter a giveaway |
| Tournament prize claims | The winner’s legal name as on their ID, a US address or where to send a cash prize (a PayPal email, $Cashtag or Zelle), and their 18+ and US confirmations. A tax form (W-9) is handled by email; the site keeps only whether one is on file — never a Social Security number. | You win a prize tournament and claim it |
| 18+ confirmation | Signed in, the date of birth you give is your birthday (above), asked once. Signed out, it’s checked and thrown away, and this browser keeps only that you confirmed. | You open something marked 18+ |
| Emails and newsletter clicks | The email address you give in the 15%-off sign-up box, and which links you click in our emails. | You sign up for the offer, or click a link in an email |
| Contact and booking forms | What you send us (name, email, phone, message), so we can answer. | You write to us or request a booking |
| Reports, blocks, mutes and moderation records | To keep the community safe and to handle appeals. | You use the safety tools, or a moderator acts |
Cookies and similar technologies
We set only our own cookies, each for one job. There are no advertising networks, social-media pixels or cross-site trackers.
| Cookie | What it does | How long |
|---|---|---|
| sb-…-auth-token | Keeps you signed in (it can come in numbered parts). While you sign in, confirm your email or reset a password, the same library sets “code-verifier” cookies, which stay until that sign-in finishes or you sign out. | 400 days, renewed while you use the site; removed when you sign out |
| rlss_src | Where you came from (see above), before you have an account. | 30 days, or until you sign up |
| rlss_ref | The invite code you followed. | 30 days, or until you sign up |
| rlss_seat | You arrived from Facebook, Instagram or our store and were shown the welcome page once, so Home isn’t swapped for it again. Holds nothing but “1”. | 30 days |
| rlss_oauth_next | Where to bring you back after Apple or Google sign-in. | 10 minutes |
| rlss_entry | How you got into a live (from an alert, Home, a share…), counted for the creator. | 6 hours |
| rlss_18 | You confirmed you’re 18 or older while signed out. | 1 year |
| rlss_u18 | An under-18 answer, so the age check isn’t asked again straight away. | 1 day |
| rlss_u13 | An under-13 answer when joining (or to the birthday question), so it isn’t asked again straight away. No account is made and nothing about the date is kept. | 1 day |
| rlss_dob | Joining with Apple or Google: the birthday you just gave, so it can be saved on your new account when you come back. Sent only to the sign-in return address. | 10 minutes |
| rlss_bbn | You hid the payment-problem notice for today. | 1 day |
| rf_vid | A random visitor ID for people who aren’t signed in, to cap how often an ad is shown and to count views. We store it only in scrambled form. | 1 year |
| rf_ad_attr | The last ad you clicked, so a merch order can be credited to that ad. | 7 days |
| rf_free_preview | Staff only: previewing the site as a free member. | 12 hours |
| rf_app_device, rf_app_sf | iPhone app only: the app’s install ID (so signing out removes that phone’s notifications) and your App Store country (which decides whether purchase buttons show in the app). | 1 year |
The page’s own scripts can read the sign-in cookies, rf_ad_attr, rlss_bbn, rf_app_device and rf_app_sf; the others are only readable by our server.
The site also keeps a few things in your browser’s own storage that never leave your device unless a feature needs them: your shopping bag, unsent message drafts, your last searches, your camera and microphone choice, sound settings, voices you muted at a table, and when you dismissed a pop-up or prompt. Pages we send you to — Stripe’s and Shopify’s checkouts, Cloudflare’s human check, and YouTube’s player once you press play — may set their own cookies on their own sites.
Analytics
We count visits with Umami, which runs on our own server. It sets no cookies and doesn’t build a profile of you: it records the address of each page viewed without anything after the “?” (so search words and signed links are not recorded), the website that sent you, your browser, operating system, kind of device, screen size and language, and an approximate location worked out from your IP address (the address itself isn’t kept), grouping a visit under a scrambled ID that changes over time. Like any website, our web server also logs requests, including IP addresses, to keep the site running and secure; we haven’t set a fixed deletion schedule for those logs yet.
The iPhone app
The app shows the same community as the website, with a native tab bar, notifications, lock-screen lives and a voice bar. On top of what the website collects, it holds an install ID and Apple’s push and lock-screen tokens (see above), and it remembers on the phone which version of the Terms you agreed to, and when you last chose “Not now” for alerts and “Remind me later” for the birthday question. It asks for your camera when you go on camera or take a photo to post; your microphone when you go live, talk in a room or the Lounge, or record a voice note or voice post; your photo library when you pick a photo or video to post, send or use on your profile; and permission to add a photo to your library when you save one. It never asks for your location. The app contains no third-party analytics or advertising code; the website pages it shows use our own visit counter and ad measurement, as they do in a browser.
Screening with AI
We use Anthropic’s Claude to screen for threats, hate, harassment and other breaches of the community rules. Content the screen judges clearly over the line is hidden automatically (a photo is refused before it is stored); a moderator reviews it and you can appeal. Some things — event listings, pinned notes, Spotlight items, ads and tip messages — wait or are refused when the screen can’t answer. Only the content is sent — never your name or account ID. What is sent:
- Text of posts, replies, episode comments, group-chat messages, chat-room names and descriptions, threads and replies, debate questions, comments on phone lives, tip messages, pinned notes and room rules, event listings, creator page and Spotlight text, sponsor text and paid ad campaigns.
- Photos posted in the feed, in group chats and in direct messages, Spotlight photos, and live covers, flyers and sponsor logos.
- A direct message’s text only when it comes from someone the recipient doesn’t follow and has never replied to.
Not sent: profile photos, live-room chat, voice notes and other direct-message text. If you ask the events helper to read a flyer or write a description, that flyer and the event details are sent to Claude to do it. Under Anthropic’s commercial terms, content sent through its service isn’t used to train its models.
Who else gets it
Only the services needed to run the platform, and only what each one needs. We don’t sell personal information, and we don’t share it for advertising.
- Hetzner (our servers, Hillsboro, Oregon) and Backblaze (encrypted backups, US).
- Stripe runs every payment and membership on its own checkout pages — your card goes to Stripe, never to us — and holds your email, handle and account ID. Payments are taken on the Stripe account of 20/20 Vision Productions, which other businesses also use. Creators’ payout accounts are Stripe Connect accounts.
- Shopify runs the merch store and its checkout. We use your account email to find you there and mark your membership discount, and a shopping bag carries which campaign or ad it came from and whether you’re a member. A giveaway winner’s name, address, phone and handle go to Shopify when the prize ships from our store.
- Resend sends our email: account emails (confirming your address, resetting a password), notifications, newsletters, and the contact and booking forms you send us (to our inbox) and our answers.
- Microsoft 365 hosts our mailbox, mail@reallyfeproductions.com: what you email us — forms, privacy requests, prize and tax-form correspondence — is kept there.
- Cloudflare checks that you are human on sign-in, sign-up and password reset (Turnstile receives your IP address and browser signals). If a host broadcasts from streaming software, that video goes through Cloudflare Stream, which records it, and viewers load it from Cloudflare, which sees their IP addresses.
- Knock, only if we switch it on, would deliver “your prize has shipped” alerts: the winner’s account ID, the prize and its tracking number.
- Google’s speech service hears a speaker’s audio when a host turns on live captions and that speaker uses Chrome (each speaker’s own browser makes their captions).
- Anthropic screens content, as described above.
- Apple signs you in if you choose Sign in with Apple, delivers notifications to the iPhone app (an alert’s title and text; a direct-message alert says only “New direct message”) and tells the app your App Store country. Google signs you in if you choose Continue with Google.
- Browser push services (Google, Mozilla, Apple, Microsoft) carry web notifications to your browser.
- YouTube plays the episodes through youtube-nocookie.com, and episode thumbnails load from YouTube’s image servers, which see your IP address. Once you press play, YouTube’s own privacy policy applies.
- Music and social link cards (Spotify, Apple Music, SoundCloud, TikTok, Instagram, X) show a thumbnail from that service; their player loads only when you tap it.
- Google Fonts and Fontshare serve typefaces. Requesting a font shows them your IP address.
In a live room, the people with you see your name, handle and photo, and hear or see you when you’re on stage. Our live server is our own, not a third party’s.
What other members can see
The community’s pages need an account, but much of what’s posted there isn’t technically locked to members: posts, replies, reactions, photos and voice posts, your public profile details, chat in free rooms and the Wall can be read through the site’s public connection without signing in, and our public Community page shows the week’s top contributors and their points. Treat anything you post as public. Anyone can also see the comments you leave on an episode’s page, with your name, handle and photo.
Members can see your handle, display name, bio, photo and cover, membership tier, badges and level, follower count (and your follower and following lists unless you hide them), linked music, your posts, replies and reactions, what you say in rooms, a Super Chat’s name, message and amount, your points total on the Wall, your seat, chips and results at After Hours tables and in tournament replays, where you’re playing (shown to mutual follows unless you turn it off), and — if you win — your handle when a giveaway says up front that it names its winner, or your display name as a tournament’s winner. When such a giveaway is drawn on the Live Draw stage, entrants’ handles roll across the screen.
Not visible to other members: your email, password, phone, card and payout details, shipping details, your full points ledger, what you watch, and your private messages (only the people in the conversation see those).
How long we keep it
| Data | How long |
|---|---|
| Your account, profile, posts, messages, points and XP | While your account exists. Deleting your account removes them, except what’s listed below. |
| Feed activity (what you see and do in the feed) | 120 days |
| Watch activity (plays, watch time, finishes, shares) | 180 days after your last activity on that item |
| Resume points (“Continue watching”) | Until you clear your history or delete your account |
| Other viewing records (episode views, rooms joined, who was in a live and how they got there, where follows were made, watch time on video posts) and days active | While your account exists — no shorter limit is set yet |
| Wrong-password counts | 30 days |
| The sign-in help log (fresh sign-in links we sent, and why) and the sign-in alert log (accounts our team was told about) | 90 days |
| Push notification details | Until you turn notifications off, sign out of the app, the token stops working, or you delete your account. Lock-screen live tokens: 12 hours at most. |
| Recordings | Phone-live replays: 7 days after the live (at once if the host turns saving off). Other room recordings are kept until our team deletes them; replays published to the Vault stay there. |
| Where you came from | The cookie: 30 days. The saved record: while your account exists. |
| Giveaway entries and tournament prize claims | Kept as the record of that giveaway or tournament, including names and addresses, also after you delete your account. A fixed limit is being set with our lawyer and accountant. |
| Payment records (tips and Super Chats, room tickets, gift purchases, Vault unlocks, bookings, sponsorships, paid promotions) | Kept as financial records after you delete your account, with the link to your account removed. Your membership record is deleted with your account; Stripe keeps its own invoices and customer record. |
| Ad records | No fixed limit yet; they use a scrambled ID, so they aren’t removed with your account. |
| Hashed sign-up records | No fixed limit yet; not tied to your account, so not removed with it. The sign-in service’s own sign-in and session records have no deletion schedule of ours yet. |
| Group-chat messages | After you delete your account, the messages stay in the group with your name removed. |
| Reports and moderation records, invite records, newsletter clicks | Kept, with the link to your account removed when you delete it (a report about you keeps your former account ID, and we keep a note that your account was deleted and when). |
| The 15%-off sign-up email | Until you ask us to remove it |
| Backups | Off-site copies about four weeks; copies on the server itself have no fixed schedule yet |
Your choices
- See or correct your data — most of it is editable in your profile and Settings.
- Download your data — Settings → Account gives you a copy of your profile, posts, replies, comments, direct messages, points and XP, follows, watch history, notifications, tips, rewards and bookings, giveaway entries, the lives you were in, where you came from and your birthday. It doesn’t include everything yet — for example the photo, voice and video files themselves, your reactions, group chats, room chat, feed activity, episode views and rooms joined, days active, invites, blocks, reports, tickets and other purchases, events, game records, push details, memberships and gifts, and prize claims. Email us for any of those.
- Delete your account — Settings → Account, by typing your handle. If you have All-Access, cancel it first. Deletion is immediate: your profile, posts, direct messages, points and the rest go at once, with the files in your folders for photos, audio, message attachments, covers and clips. What we keep is listed above. Some files can stay reachable at their address — event flyers, Spotlight and guest-shop photos — and rooms you hosted stay with the host left blank; email us and we will remove the files. Stripe and Shopify keep their own customer records.
- Notifications — choose email and push per kind in Settings → Notifications. Every marketing email has a one-click unsubscribe.
- Privacy settings — Settings → Privacy, including whether people you message see when you’re active.
- Cookies — you can clear or block them in your browser; signing out removes the sign-in cookie.
Depending on where you live (for example California, other US states, the UK or the EU) you may have rights to access, correct, delete or move your data, or to object to how it’s used. Exercise any of them by emailing mail@reallyfeproductions.com.
Children and teen accounts
You must be 13 or older to have an account (see the Terms), and purchases, tips, giveaways, tournaments, After Hours and going live are for adults 18 and older. Joining asks your birthday before anything else is sent: an under-13 answer makes no account and keeps nothing. We don’t knowingly collect data from children under 13; if a member tells us they’re under 13, the account is restricted and closed. If you believe a child under 13 has an account, tell us and we will delete it.
Members aged 13 to 17 have a teen account, set by their birthday: only people they follow can message them or add them to a group chat; spending is off; After Hours, 18+ rooms and mature videos are hidden; going live, giveaways and tournaments are off; no ad is ever chosen for them by who they are, and nothing adult-themed is shown; and they aren’t suggested to adults (their exact handle still finds them). Reporting, blocking and muting work for everyone. A parent or guardian can ask us to review or close a teen’s account at mail@reallyfeproductions.com. A member who joined before birthdays were asked is asked once; until they answer (after a week of “Remind me later”), their account has the same teen settings.
Security, honestly stated
Passwords are hashed, traffic is encrypted in transit, database access is restricted row by row, private columns are unreadable even by other signed-in members, two-step verification is available, and card details never touch our servers. No system is perfect; if we ever discover a breach affecting your data we will tell you what happened and what we did.
Contact
mail@reallyfeproductions.com — Reallyfe Productions, LLC, 1801 N Pearl Street #513, Dallas, TX 75201.
Privacy · Terms · Refunds · Copyright · Accessibility