Team Payments Privacy Supplement
This Team Payments Privacy Supplement describes the additional information involved when an
organization uses Universal Scheduling to collect registration and entry-fee payments from its teams
through Stripe Connect. It forms part of our
Privacy Policy and adds to it; everything in
the main policy continues to apply. It is relevant only to organizations that turn team payments on, and
to the people who pay them — if you have never seen a payment page on this site, nothing here
applies to you.
Effective date
August 8, 2026.
Who does what
Payments are processed by Stripe. The organization running the event is the merchant of record and the seller of the registration; Universal Scheduling provides the software and facilitates the payment. Stripe is a payment processor for us, and is also an independent controller of the identity information it collects to meet its own legal obligations (know-your-customer, anti-money-laundering, and sanctions screening). Stripe's handling of that information is governed by Stripe's privacy policy.
Information about the organization and its owners
Information about people who pay
Records we keep of administrative actions
Because these actions move money, we keep an audit record when a member of an organization accepts the onboarding agreement or issues a refund. That record includes the signed-in user's email address, their IP address, the browser's user-agent string, and the time. It exists for accountability and dispute resolution, and is not used for anything else.
Who we share it with
We share the information described above with Stripe, to process payments and to meet Stripe's own regulatory obligations, and with the organization whose event the payment is for — the organization can see who paid, for which team, how much, and the payment's status. We do not sell this information, do not use it for advertising, and do not add payer addresses to any marketing list. The commitment in the main policy about email addresses given to us for an event applies here too.
Retention
Payment records, refund audit records, and agreement-acceptance records are financial and compliance records. We keep them for as long as needed for accounting, tax, dispute, and audit purposes, which is generally longer than ordinary event data and may extend past the end of the event or the closure of an account. Stripe keeps its own records under its own retention rules.
Your choices
Paying through this site is optional; an organization may offer other ways to pay. To ask about information we hold, or to request deletion of information that we are not required to retain as a financial record, contact us at the address below. Requests about identity information held by Stripe should go to Stripe, since we do not hold it.
Changes
If we make material changes to this supplement we will update this page and change the effective date above.
Contact
Questions or requests: [email protected].
Effective date
August 8, 2026.
Who does what
Payments are processed by Stripe. The organization running the event is the merchant of record and the seller of the registration; Universal Scheduling provides the software and facilitates the payment. Stripe is a payment processor for us, and is also an independent controller of the identity information it collects to meet its own legal obligations (know-your-customer, anti-money-laundering, and sanctions screening). Stripe's handling of that information is governed by Stripe's privacy policy.
Information about the organization and its owners
- Collected by Stripe, not by us. To open a payment account, Stripe verifies the business and the people behind it. Through Stripe's onboarding screens — which appear inside our admin console but are operated by Stripe — Stripe collects business details (legal name, address, tax identification number), information about beneficial owners and the account representative (name, date of birth, home address, government identification number, and where Stripe requires it, a copy of an identity document), and the bank account that will receive payouts.
- We do not receive or store that identity information. Those details go from the person entering them to Stripe. We never see identity documents, dates of birth, government identification numbers, or bank account numbers, and none of them are stored on our servers.
- What we send Stripe. When creating the account we send only the organization's country and its contact email address.
- What we get back. Stripe returns the account's status — whether it can accept payments and receive payouts, and the categories of information still outstanding (for example "identity document required"). We store that status so the admin console can show the organization what to do next. The outstanding-items list names what is missing, not its contents.
Information about people who pay
- Email address. Paying begins by entering an email address and clicking a link we send to it. We store that address with the payment record, and we pass it to Stripe with the payment so Stripe can issue receipts and match the payment to the payer.
- Payment record. We store which event, team, and division the payment was for, the amounts, the method used (card or bank payment), the payment's status, and any refund amount.
- Card and bank details never touch our servers. They are entered directly into Stripe's payment form and go to Stripe. We receive only a payment identifier and status.
Records we keep of administrative actions
Because these actions move money, we keep an audit record when a member of an organization accepts the onboarding agreement or issues a refund. That record includes the signed-in user's email address, their IP address, the browser's user-agent string, and the time. It exists for accountability and dispute resolution, and is not used for anything else.
Who we share it with
We share the information described above with Stripe, to process payments and to meet Stripe's own regulatory obligations, and with the organization whose event the payment is for — the organization can see who paid, for which team, how much, and the payment's status. We do not sell this information, do not use it for advertising, and do not add payer addresses to any marketing list. The commitment in the main policy about email addresses given to us for an event applies here too.
Retention
Payment records, refund audit records, and agreement-acceptance records are financial and compliance records. We keep them for as long as needed for accounting, tax, dispute, and audit purposes, which is generally longer than ordinary event data and may extend past the end of the event or the closure of an account. Stripe keeps its own records under its own retention rules.
Your choices
Paying through this site is optional; an organization may offer other ways to pay. To ask about information we hold, or to request deletion of information that we are not required to retain as a financial record, contact us at the address below. Requests about identity information held by Stripe should go to Stripe, since we do not hold it.
Changes
If we make material changes to this supplement we will update this page and change the effective date above.
Contact
Questions or requests: [email protected].