Privacy Policy

Collectivision is a live video platform for artists, musicians, performers, venues, and the people who love what they make. We're based in Oregon, in the United States, and our infrastructure is primarily in the United States. In this policy, "we" and "us" mean Collectivision, and "you" means you.

This covers collectivision.net, Collectivision Studio, hosted spaces and galleries (including ones served on creators' own custom domains), share-code and file pages, live chat, and our apps.

One thing worth understanding up front: when you watch a creator's video or post in their chat, both we and that creator handle some information about it. We're responsible for the platform. The creator is responsible for what they do with what they can see — their chat, their audience, their donation links. If you have a question about a particular creator's practices, ask them directly.

Questions about anything on this page go to privacy@collectivision.net, and a human reads them. If you need a postal address for a formal request, ask and we'll provide one.

If you're just watching

You can watch a shared video without an account, and we keep this as thin as we can make it.

We set no advertising cookies, and there are no third-party analytics or tracking scripts anywhere on the site.

If you post in chat

Chat is public to everyone who can see that page, and messages stay there until you or the space owner removes them. Please don't put anything private in it.

If you comment

Comments are public to everyone who can see the page they're on. The space's owner and the moderators they appoint can see the name you posted under and whether you have an account — not your email address or IP. They can hide, delete or ban; see the community guidelines.

If you make a free viewer account

• Your email address and a password — hashed by our authentication provider. We never see or store the plaintext.
• An optional display name, so you're not just an email address in chat and comments. If you don't pick one, we derive a starting point from your email and you can change it any time.
• An optional profile photo, shown beside your comments, and how you framed it. It's stored at a public address like other images on the site. Replacing or removing it deletes the old file. An offensive photo is removed if enough people in a space report it or a space's moderators take it down (community guidelines).
• Whether you want emails about replies to your comments (on unless you turn it off), and a token for its one-click unsubscribe.
• The videos you've favorited and the spaces you follow, so we can show you your own list.
• Your email notification preferences and an unsubscribe token, so "new video from someone you follow" emails work and so a single click can stop them.

Every notification email has a working one-click unsubscribe. We don't send marketing email to viewer accounts.

If you join the waitlist

Your email address and which page you signed up from, so we can send you an invite code when a spot opens. That's the whole record.

If you have a Studio account

Everything above, plus what's needed to run a publishing account:

• The invite code you redeemed and when — to keep track of invites and to stop code guessing.
• Your spaces, projects, videos and files, including titles, descriptions, tags, filenames and file sizes.
• The video and file content itself.
• Access credentials you set on gated content — usernames as you entered them, passwords hashed.
• Custom domains you've connected, plus their DNS and certificate status.
• Donation links you configure, so they can be shown on your pages. The money itself never passes through us.
• People you've added to a space and their roles.
• Storage and bandwidth usage for your spaces, so you can see where you stand and so our costs don't surprise either of us.

If you pay for something

Payments are handled by Stripe. You enter your card on Stripe's checkout, and we never see or store card or bank details. Alongside Stripe's reference numbers for each payment, what we keep depends on what you're paying for:

If you accept payments as a creator, we keep your Stripe account ID, whether it's able to take payments and payouts, its country, currency, and business name. Stripe runs the identity and bank checks itself; we don't see those documents.

If your ticket came from Ticket Tailor

Some spaces sell tickets through their own Ticket Tailor box office and connect it to Collectivision, so a livestream ticket bought there gets you into the stream here. For each ticket to a show linked this way, we copy from Ticket Tailor the order email, the ticket holder's name, the ticket's price, barcode, type, and status, and Ticket Tailor's order and ticket numbers. That's what lets you in when you enter your email or barcode, or sign in with the email you ordered with — and it's why a ticket voided over there stops working here.

The space connects with a read-only Ticket Tailor key, which we store encrypted, along with who connected it. We only read tickets for shows the space has linked, and we never change anything on Ticket Tailor. Everything you gave Ticket Tailor when you bought is covered by Ticket Tailor's own privacy policy.

If you connect an Instagram account

Studio can publish a finished vertical video straight to an Instagram professional account. Nothing happens until someone in a space connects an account through Instagram's own login screen, where Instagram shows what Collectivision is asking for. After that, we post only when a person in the space presses Publish.

What goes to Instagram: the caption and a link to the video file, which Instagram fetches from our video host. If Instagram refuses a post, we ask it whether the account has used up its daily posting limit, so we can tell you why. We don't store the answer.

What we don't do with it: we ask Instagram for two things only — basic account details, and permission to publish. We don't read the account's followers, messages, comments, insights, or other posts. Nothing we get from Instagram is used for advertising, analytics, or profiling, and none of it is sold or passed to anyone else.

When something breaks

We record technical error reports: an error fingerprint, the message and stack trace, which route and method it happened on, the status code, and which release was running. This is how we find and fix bugs, and it's the only thing we use it for. An error report can incidentally include personal data if it happened to be in the request that failed — we try to keep that out, and we don't go looking through these for anything but the bug.

• We don't collect your precise location.
• We don't fingerprint your device or browser.
• We don't buy data about you from anyone.
• We don't scan the contents of your videos for advertising or profiling.
• We don't use your content, your chat, or your metadata to train AI models, and we don't grant our providers the right to.
• We never see or store card or bank details. Payments go through Stripe's checkout and Stripe holds them; what we do keep is set out in section 2, under paying for something.
• We don't send SMS. There's an unused phone-number field left over from planned text notifications; nothing writes to it and nothing sends to it. It goes away or gets used properly with explicit consent — not quietly in between.

If you're in the UK, EU, or somewhere with similar law, these are our lawful bases for processing:

• Performing our contract with you — running your account, hosting your content, and delivering it to the people you've chosen.
• Legitimate interests — keeping the service secure, preventing abuse and fraud, counting views so creators know how they're doing, and understanding errors so we can fix them. We've weighed these against your interests, and the design reflects it: hashed identifiers instead of IP addresses, per-video scoping instead of cross-site tracking.
• Consent — optional things like following a space for email updates. You can withdraw it at any time, and the unsubscribe link in every email is the fastest way.
• Legal obligation — tax and accounting records, responding to valid legal process, and mandatory reporting of child sexual abuse material.

We're a small team standing on other people's infrastructure, and you should know whose. These are our processors — companies that handle data on our behalf, under contracts requiring them to protect it and barring them from using it for their own purposes. Processing is primarily in the United States, with CDN delivery from edge locations worldwide.

We keep this table current. If we add a provider that materially changes how your data is handled, we'll update it and note it in the changelog at the bottom of this page.

Beyond that, we share personal data only when:

• You ask us to — for example, connecting an integration.
• The law requires it — a valid subpoena, warrant, or court order. We check that legal demands are actually valid, we push back on overbroad ones, and where we're legally allowed to tell you about a demand for your data, we will.
• Safety requires it — to prevent imminent serious harm, or as legally mandated for child safety reporting.
• The business changes hands — in a merger or acquisition, with notice to you, and the acquirer bound by this same policy until it gives you notice and a chance to leave.

Instagram

Meta, which runs Instagram, isn't one of our processors — it's a destination you choose. When someone in your space publishes, we send Instagram the caption and a link to the video, and from then on the post lives on Instagram under Instagram's own terms and privacy policy. Deleting a video in Collectivision doesn't take down a post that's already on Instagram; delete it there too.

We have never sold personal data, and we never will. We also don't "share" it for cross-context behavioral advertising, as California law defines that term.

Every cookie we set is functional — there are no advertising or analytics cookies here, which is why you won't find a consent banner.

They're set httpOnly, sameSite=lax, and secure in production — which means scripts running on the page can't read them. Blocking them mostly still works: you can watch, but you'll re-enter passwords and won't stay signed in.

Where we've said "until you delete it," that's the literal truth rather than a euphemism — we don't currently run automatic expiry on chat, views, or error reports. As we add scheduled deletion, we'll put the actual periods in this table rather than leaving it vague.

When you close your account, we keep your content available for 30 days in case you change your mind or forgot to export something, then delete it. If you'd rather it went immediately, say so and we'll do that. We may hold a minimal record that an account existed and when it closed, plus anything a legal hold or tax law requires.

Wherever you live, you can ask us to:

• Show you what we hold about you.
• Send you a copy in a portable format.
• Fix something that's wrong.
• Delete your data and your account.
• Stop a particular use, or withdraw consent you'd given.
• Object to processing we've based on legitimate interests.

How: email privacy@collectivision.net from your account address and tell us what you want. We'll acknowledge within 5 business days and complete it within 30 days, or tell you why we need longer — we won't take longer than the law allows. It's free, unless a request is genuinely excessive or repetitive.

Right now these requests are handled by a person rather than a button in your settings. We'd rather tell you that plainly than imply an automated flow that doesn't exist yet; self-serve export and deletion are on the way.

We won't treat you worse for exercising any of these rights — no degraded service, no different pricing, no friction designed to make you give up.

A note on deletion: some things can't be pulled back. If your chat message was quoted by someone else, or a viewer downloaded a video you'd allowed downloads on, deleting on our side doesn't reach those copies. CDN edge caches and encrypted backups also take a little while to roll off — we won't serve or restore that content in the meantime.

If you connected an Instagram account

These take effect immediately, without emailing us:

• Disconnect it in Studio, on the Connections page. We delete the access token, and nobody in the space can publish as that account until it's connected again.
• Remove Collectivision in Instagram's settings, under apps and websites. Instagram tells us, and we delete the token the same way.
• Ask Instagram to have your data deleted. Instagram passes the request to us, and we delete the connection outright — account ID, username, and token — and remove Instagram's ID and link from past posts. You'll get a confirmation code and a page on collectivision.net showing the status of the request.

That covers what we hold about the Instagram account. The videos, captions, and publishing history belong to the Collectivision space, so they stay with it; to delete those, use the rights above.

If you're in the EU, UK, or Switzerland

You have the rights above under the GDPR and its equivalents, plus the right to complain to your local supervisory authority. We'd appreciate the chance to put something right first, but you're not required to come to us before going to them. Your data is processed in the United States; where a transfer needs a legal mechanism, we rely on the European Commission's Standard Contractual Clauses with our processors.

If you're in California

Under the CCPA and CPRA you have rights to know, delete, correct, and opt out of the sale or sharing of personal information. We don't sell or share personal information as those terms are defined, so there's nothing to opt out of — but the email above works for everything else. You can use an authorized agent; we'll just ask for proof they're authorized.

If you're elsewhere in the US

Colorado, Connecticut, Virginia, Utah, Texas, Oregon and other states give similar rights. Same email, same process — we apply the same handling to everyone rather than running different tiers by geography.

We use current, reasonable measures: TLS everywhere, passwords hashed by our authentication provider, row-level security on every database table with no direct public access, signed and httpOnly cookies, hashed rather than raw IP addresses, Instagram access tokens and Ticket Tailor keys encrypted before they're stored, scoped credentials for infrastructure, and production data access limited to people who need it.

No system is perfectly secure, and we won't pretend otherwise. If there's a breach affecting your personal data, we'll notify you and the relevant regulators as the law requires, and we'll tell you what we actually know as soon as we reliably know it — not weeks later once the messaging is polished.

Security researchers: we want your reports and we won't punish you for them. Send findings to security@collectivision.net. If you act in good faith — staying in your own accounts, not accessing or taking anyone else's data, not degrading the service, and giving us reasonable time to fix things before publishing — we won't pursue legal action against you, and we'll credit you if you'd like.

Collectivision isn't for children under 13, and we don't knowingly collect their personal data. Studio accounts require you to be 18, or the age of majority where you live.

If you believe a child under 13 has given us personal data, email privacy@collectivision.net and we'll delete it.

Creators: if your own audience includes children, that brings obligations on your side too — COPPA in the US, the Age Appropriate Design Code in the UK, and similar rules elsewhere. Worth looking into before you build for a young audience.

This is a young platform and this page will change as it grows. Material changes — anything that meaningfully affects what we collect, why, or who sees it — get at least 30 days' notice by email to your account address and a notice on the site before they take effect. Clarifications and corrections take effect when posted.

Either way, the changelog at the bottom of this page records what changed and when, so you can see the history without diffing two walls of text. We won't apply a change retroactively to data we've already collected in a way that would surprise you.

A human reads all of these. If you need a postal address for a formal request, ask and we'll provide one.