Legal
Common Plays LLC, operator of RarePause.
To run the platform we use a small number of outside companies. Each one processes information only to provide its service to us, under contract, and none is permitted to use it for its own purposes.
This page lists them. We update it before a new provider begins handling your information.
Hosting and content delivery. Every request to RarePause passes through Cloudflare, so it handles your IP address and the ordinary technical details of a web request. It also runs the background jobs that send reminders.
Our main database, sign-in, and the live updates you see during a session. This holds your account, your registrations, your schedule, and anything you post during an event. Session recordings are not stored here.
Two separate things, both in the US East (Ohio) region.
Free-text answers on a registration form, and any answer a community marked sensitive, are held in a database kept apart from the main one, encrypted at rest with a managed key. Partly-completed registration forms are held the same way until you finish or abandon them.
Separately, when an account is deleted we write a record of what was erased to storage that we can add to but not read back, so there is an auditable trail that deletion happened.
We hold an executed business associate addendum with AWS covering these services. We are not a HIPAA covered entity or business associate, and that addendum is a precaution rather than an admission that HIPAA applies to us.
Payments. Stripe handles card details directly and we never receive them. In the ordinary registration flow we send Stripe identifiers rather than your name or email address, so what Stripe holds about a payment comes mostly from you entering it at their checkout, not from us passing it on. Communities that collect money through RarePause have their own Stripe accounts, and Stripe is the payment processor for those too.
Transactional email: registration confirmations, appointment reminders, the link that cancels an account deletion, and similar. Resend receives your email address and the contents of the message we send you. We do not use it for marketing.
Session video. Recordings and live streams are hosted on YouTube and played inside RarePause using YouTube's no-cookie player, which does not set advertising cookies. Google still receives your IP address, your browser details, and the fact that the video was played from RarePause. If a community removes a recording from RarePause that controls whether it appears here; the file itself is on YouTube and only the community can remove it there.
If you turn on notifications, your browser, not us, decides which company delivers them. Chrome uses a Google service, Firefox uses one run by Mozilla, Safari uses Apple, and Edge uses Microsoft. We cannot choose on your behalf and we do not have a contract with whichever one your browser picks.
What we send it is the address your browser gave us plus an encrypted message. The delivery service can see that a notification is on its way to your device and can see the address, but the contents are encrypted for your browser and it cannot read them.
Turning notifications off in your account stops this. Your browser also has its own control for it.
We do not use advertising networks, analytics products that track you across other websites, or data brokers.
We update this page before a new provider begins handling your information, and we tell organizations about material additions. If you want to know more about any company listed here, write to help@rarepause.com.