Privacy policy

Last updated 15 November 2026.

Session Central is the creator community for Scrybe, run by Scrybe Streaming. This page says what we collect when you use it, why, who else sees it, and how long we keep it. It sits beside our terms and the community guidelines.

What we collect

Your account. Your email, display name, handle, the roles you do and your city, your time zone, and when you confirmed you're 18 or older and agreed to the terms. Your password is stored only as a one-way hash, and a Sign in with Scrybe account may have none. If you add a passkey or two-factor authentication, we keep what they need to work.

What you put on your profile. Your bio, photo, banner, intro, portfolio, genres, links and anything else you add. You choose who sees your profile in Settings → Privacy.

Your MyScrybe link. When you connect MyScrybe or sign in with Scrybe, Scrybe tells us your Scrybe account's id and email, and, for an artist, your stage name, photo, bio, genres, city, whether you're verified, and your released music. We copy your photo into our own storage. If your Scrybe account runs a label, Scrybe also tells us the label's name, bio and logo, and the artists on its roster. A label's page here can show a roster artist's name and picture from Scrybe when Scrybe has verified them, whether or not they've joined Session Central. We never receive or keep your Scrybe password or a Scrybe sign-in token.

Subscriptions for Scrybe Exchange. You can support an Exchange campaign by subscribing on Scrybe, or by redeeming a subscription you already have. When you do, we ask Scrybe whether you hold a subscription covering that artist, album or track. Scrybe tells us which subscription it is, when it started, and whether a supporter's link led to it. Scrybe tells us nothing else about it, never the price or how you paid. We keep the answer with your support, along with a scrambled form of it so one subscription can't earn twice.

Proof of support on Scrybe Exchange. When you support a campaign, you send proof: a link to your post, your handle there, a note or a screenshot. You see it, the campaign's owner sees it to review it, and Session Central's staff see it only while it waits past its review deadline or is under appeal. We keep a scrambled form of the link or screenshot so one post can't earn twice.

Supporters' links. A supporter's link to Scrybe counts a click once per visitor a day. For that we keep a scrambled form of who clicked (your account if you're signed in, otherwise your network address) that changes every day, and whether you were signed in. It never says who you are.

Bookings and payments. Service listings, quotes and bookings are a test preview, open only to the Scrybe team and run in Stripe's test mode, so no real money moves yet. This is what we handle when you use them.

  • What Stripe receives. When you pay for a booking, you type your card details into Stripe's own form on our page. They go straight to Stripe and never reach Session Central. We tell Stripe the amount, the currency and which booking the payment is for. When you set up payouts as a provider, you give Stripe what it needs to check who you are and to pay you, such as identity and bank details, on Stripe's own pages. We never receive those either. Stripe handles what it gets under the Stripe privacy policy.
  • What we keep. The ids Stripe gives us for your payout account and for each payment, refund and transfer; the amounts, the fee and the currency; where each payment and payout stands and when it changed; and whether your payout account is ready. Never a card number, a bank account number or an identity document.
  • The booking itself. The brief, the quote, the files you both send, deliveries, and the booking's timeline.
  • Disputes. The reason, what each of you writes, the files you add as evidence, and what staff decide. If a buyer disputes a charge with their bank, Stripe tells us, and we keep that dispute's id and how it ended.
  • Receipts. We email the buyer a receipt when a payment is held and when it's refunded, and the provider a statement when they're paid. These are always sent. They carry the amounts and the booking's title, never the brief or files.

Paid verification. If you verify your identity for Session Central's check (a test preview, open only to the Scrybe team and run in Stripe's test mode), this is what happens with it:

  • What Stripe receives. You pay on Stripe's own page, and your card details go to Stripe, never to Session Central. You show your photo ID and take a selfie on Stripe's own page too. Stripe checks that the ID is real and that the selfie matches its photo, under Stripe's privacy policy. Stripe asks for your consent there first, since matching a face is biometric information.
  • What we keep. The ids Stripe gives us for your subscription, its payments and any refund, the price, when each month is paid through, whether your identity check is waiting, passed or failed, how many tries failed, and Stripe's reason code for the last one.
  • What we never keep. Your ID, its number, your name or date of birth as they appear on it, or your selfie. Stripe doesn't send them to us, and we never ask.

What you post and send. Posts, comments, photos, videos, votes, saves, follows, subsessions you make and join, opportunities and responses, events you host or answer, listening rooms you host or join and what you say in their chat, and messages. Photos lose their location and other hidden details when they're processed.

Reports and moderation. Reports you file or that are filed about you, what moderators decide, and appeals. A report of a message keeps a copy of it and the 20 messages before it.

How Session Central is used. We count things like sign-ups, which links to MyScrybe, Scrybe and the magazine are clicked and where they sat on the page, posts made and messages sent: never what anyone wrote. We note which days you did something here (posted, commented, messaged, followed, voted or saved) and your Verified status that day, to know how many people are active each week. If you sign up on MyScrybe from a link here, MyScrybe tells us a sign-up came from Session Central and which link it was.

Feedback you send. What you write in Send feedback, and the page you sent it from (without anything after a ? in its address), for the Session Central team to read.

Sessions and security. The IP address, browser and device each of your sign-ins is from, so you can see and end them in Settings → Security, and a record of changes to your account, for your safety and ours.

Cookies. A session cookie that keeps you signed in, one that protects forms from forgery, and your theme. On Scrybe Exchange's pages, a random id for your browser, so accounts used on one browser can't support each other's campaigns: we keep only a scrambled form of it, with your account, for 90 days after you last use Exchange there. There are no advertising cookies and no third-party trackers.

Push notifications. If you turn on push in a browser, we keep the address its push service gave it and the keys that encrypt what we send, with your account and that browser's sign-in. A push says what the notification says in the app, and nothing more: never a photo, a message's words or a link elsewhere.

How we use it

To run Session Central: show your profile and posts to the people your settings allow, deliver messages and notifications, and email you as you choose in Settings → Notifications. To keep it safe: handle reports, stop spam and impersonation, and enforce the guidelines. And to learn: during the pilot we measure how many people are active, what they do, and how many MyScrybe sign-ups come from here, to decide what to build next.

We don't sell your information, and we don't show ads.

Who else sees it

Other members and visitors see what you post where you post it, and your profile as your privacy settings allow. Posts in public subsessions can be read by anyone, signed in or not.

Scrybe. When you connect MyScrybe, we tell Scrybe what's needed to keep the link working, and MyScrybe can show your unread Session Central counts on your dashboard.

The services we run on, each only for what it does for us: Laravel Cloud (hosting and the database), Amazon Web Services (storing and delivering photos and videos, checking uploads for malware, and converting video), Resend (email), Sentry (error reports) and Stripe (payments for bookings, providers' payouts, and paid verification's subscription and identity check). They're in the United States. A push you turned on goes through your browser's own push service (Google for Chrome, Microsoft for Edge, Mozilla for Firefox, Apple for Safari), encrypted so that only your browser can read it.

The other person in a booking sees what you send them there: the brief, the quote, deliveries and files, and the amount. A provider never sees the buyer's card, and a buyer never sees the provider's bank or identity details.

Dispute evidence. Everything either person adds to a dispute is seen by both of them and by the Session Central staff deciding it. Staff also see the booking's summary, timeline, deliveries and files. They don't see your conversation about the booking, unless a message in it is reported.

Our analytics export. Each day's usage counts are saved in our own private storage with your account replaced by a code that can't be traced back without our key.

The law. We share information when the law requires it, or to protect someone from serious harm.

How long we keep it

  • Your account and profile: while your account is open, and 30 days after you deactivate it. Then it's deleted, and your posts and comments show as "Deleted member".
  • Messages: while either of you keeps the conversation.
  • A listening room's chat: 90 days after the room ends or is cancelled. A report keeps its own copy.
  • Exchange proof: 12 months after the campaign completes, or after the proof was decided if it never does. Then the link, handle, note and screenshot are removed. The decision and the scrambled form stay.
  • Photos and videos: removed within 60 days of nothing showing them any more.
  • Reports, moderation records and the account change record: 7 years.
  • Payment records (payments, holds, fees, refunds, transfers and dispute decisions, and paid verification's subscription, payments, refund and whether your identity check passed): 7 years, including after you delete your account.
  • Work files in a booking, dispute evidence included: 12 months after the booking ends or the quote request closes. A disputed booking's files stay until the dispute is decided, then 12 months. They stay for the other person in the booking even if you delete your account.
  • Usage counts, and which days you were active: 13 months, then only daily totals that name nobody.
  • Feedback: kept so we can act on it. After you delete your account it no longer shows your name.
  • Sessions: until you sign out or end them; a session left unused expires.
  • Notifications: 90 days after you read them, and a year at most.
  • Push in a browser: until you turn it off, sign out of that browser, or the browser goes 60 days without a visit.

Your choices

You can edit or delete what you post, change who can see your profile and message you, choose your notifications and turn push on or off, disconnect MyScrybe, deactivate your account or delete it, all from Settings. To ask for a copy of what we hold about you, or to correct or delete it, use Send feedback under the nav, or write to us at the address below if you can't sign in.

Contact

Session Central is run by Scrybe Streaming. Write to us about your information at privacy@sessioncentral.com.

Age

Session Central is for people 18 or older. If we learn that an account belongs to someone younger, we close it.

Changes

We'll say on this page when this policy changes. If a change matters for how your information is used, we'll tell you in the app before it applies.