Privacy Policy

1. Who this covers

This Privacy Policy explains how Reunionsoft [LLC] ("Reunionsoft," "we," "us"), Tampa, Florida, handles personal information across reunionsoft.com, reunion pages on custom domains we host, and the emails we send.

It applies to three groups:

• Organizers: you created an account to run a reunion.
• Attendees: you RSVP'd or bought a ticket on a reunion page.
• Classmates: an organizer added your name to a class list. You may never have visited this site. Section 4 is written for you.

If you are a classmate and just want to know how to get off a list, skip to Section 9.

2. Information we collect from organizers

Account: your email address and the name you give us. We sign you in with a one-time code emailed to you, so we do not store a password.

Reunion details: school, graduation year, event name, date, venue, description, ticket price, capacity, and an optional cover image.

Class list: everything you enter or import about classmates; see Section 4.

Planning data: budget line items and vendors, tasks and the names of volunteers you assign them to, and check-in records.

Payments: when you buy search credits or a custom domain, Stripe collects your card details directly. We receive a record of the purchase, not your card number. When you connect a bank account for ticket payouts, Stripe collects the identity and banking details it needs and shares with us only the status of your account and the payouts made to it.

Credits: a ledger of credits granted, purchased, and spent, including which classmate record each search was for.

Technical: session cookies, IP address, browser type, and the times you sign in.

3. Information we collect from attendees

When you RSVP we collect your name, email address, and the number of tickets or guests. If you buy a ticket, Stripe collects your card details; we receive the amount, a payment reference, and whether it succeeded. We send you a confirmation and, for paid tickets, a receipt.

If your email matches a record on the organizer's class list, we link your RSVP to that record so the organizer sees you as attending. On the night, the organizer may mark you as checked in.

We do not require an account to RSVP and we do not create one for you.

4. Information about classmates, including people who never used the site

This is the part that makes Reunionsoft different from most websites: much of the personal information we hold is about people who did not give it to us. An organizer building a reunion may add your name from a yearbook or alumni list, and may then use a search credit to look up your current contact details.

A classmate record can include: full name, maiden name, current city, email address, phone number, links to Facebook, Instagram, or LinkedIn profiles, a short bio, notes the organizer writes, whether and when you were invited, your RSVP status, and where the record came from.

Where it comes from:

• The organizer: typed in or imported from a spreadsheet.
• You: if you joined the class yourself through the site.
• People Data Labs: a licensed people-data provider. When an organizer spends a credit, we send your name, the school, the graduation year, and (if known) your last city and ask for a single best match above a high confidence threshold. If there is one, we save the email, phone, city, and profile links it returns. A lookup never overwrites something a person typed in themselves.

Our lawful basis for holding this information is the legitimate interest of a class in reaching its own graduates for a reunion, balanced against your privacy, which is why we cap what we store, use it only for reunion outreach, and honor removal requests promptly.

5. How we use information

• To run the Service: build class lists, send invitations, publish reunion pages, take RSVPs and payments, pay organizers, and check guests in.
• To send transactional email: sign-in codes, invitations from an organizer, RSVP confirmations, and payment receipts. We do not send marketing email to classmates or attendees.
• To bill: charge for credits, tickets, and domains, and to detect and respond to fraud, refunds, and chargebacks.
• To improve the Service: aggregate usage of our marketing site through cookieless analytics, and error logs from the app.
• To comply with law and protect rights: respond to lawful requests, enforce our Terms, and defend claims.

We do not sell personal information, and we do not share class lists with advertisers, data brokers, or any other organizer. We do not use classmate data to train models or to build profiles for any purpose other than the reunion it was added for.

6. Who can see what

• The organizer of a reunion sees the full class list for that class, all RSVPs, and all payments for that reunion.
• Attendees see the public reunion page: event name, date, venue, description, ticket price, and the school and year. The guest list is not public.
• Classmates who join a class through the site can see and edit their own record. Class lists are not visible to the public or to search engines.
• Public reunion pages are indexed by search engines and listed in our sitemap; they show event details, not people.

7. Service providers

We share information with companies that help us run the Service, under contracts that limit what they can do with it:

• Stripe: payments, payouts, and organizer identity verification (Stripe Connect). Stripe is an independent controller for the card and bank details it collects; see Stripe's privacy policy.
• Resend: delivers our email. Receives recipient addresses and message content.
• People Data Labs: classmate lookups. Receives the name, school, year, and city we search for.
• Neon: hosts our database. Vercel: hosts the site, serves it, and registers custom domains on our behalf; Vercel Web Analytics on the marketing page collects aggregate, cookieless page-view data.
• Clarky: powers the support-chat widget on our marketing site. If you use it, your messages and any contact details you type are shared with that service.

We may also disclose information when the law requires it, to protect the rights or safety of any person, or as part of a merger, acquisition, or sale of assets (in which case this policy continues to apply to the transferred data).

8. Cookies and similar technologies

We use a small number of cookies and browser storage:

• A session cookie that keeps you signed in. It is strictly necessary and expires when your session does.
• A browser-storage preference for light or dark mode.
• Vercel Web Analytics on the marketing homepage, which does not set cookies and does not identify individuals.
• The support-chat widget on the marketing homepage may set its own cookies; it does not load inside the app.

We do not use advertising cookies or cross-site tracking, and we do not respond differently to "Do Not Track" signals because we don't track you across sites in the first place.

9. Your choices and rights

Anyone (organizer, attendee, or classmate) can email hello@reunionsoft.com to:

• See what we hold about you and receive a copy.
• Correct something that is wrong.
• Be removed from a class list, or opt out of further reunion contact. We will remove or suppress your contact details and tell the organizer not to contact you again.
• Delete your account and the reunions you organize.
• Object to or restrict a use of your information.

We answer within 30 days and will verify that the request comes from you, usually by replying to the email address on the record. We never charge for these requests and will not treat you differently for making one.

Every invitation email includes a way to opt out, and you can also reply to the organizer directly. If you are a classmate and don't want to deal with the organizer, write to us and we will handle it.

If you live in California, Colorado, Connecticut, Virginia, Texas, Oregon, or another U.S. state with a consumer-privacy law, the rights above are how you exercise your rights to access, correct, delete, and opt out under those laws; we do not sell or share personal information for targeted advertising. If you are in the European Economic Area or the United Kingdom, you also have the right to lodge a complaint with your local data-protection authority.

10. How long we keep information

• Organizer accounts and class lists: until the organizer deletes the reunion or account, or the account has been inactive for 3 years, whichever comes first. We may email before deleting an inactive account.
• Classmate records: as above, or sooner if you ask to be removed. A removed record keeps only the minimum needed to make sure you are not re-added by a later import (typically a hashed email).
• RSVPs and check-ins: with the reunion they belong to.
• Payment records and credit ledgers: 7 years, as required for tax and payment-dispute purposes, even if the reunion is deleted.
• Sign-in codes: 10 minutes. Server logs: 30 days.

11. Security

Data is encrypted in transit and at rest. Sign-in is by one-time code, so there are no passwords to leak. Only the organizer of a reunion can read its class list, enforced on every request. We limit staff access to production data to what is needed to support you. No system is perfectly secure; if we learn of a breach affecting your information, we will notify you and any regulator as the law requires.

12. Children

The Service is for adults. We do not knowingly collect information from anyone under 13, and we do not run contact lookups for anyone we believe to be under 18. If you think a child's information has been added to a class list, email us and we will remove it.

13. Where data is stored

We are based in the United States and store data with providers in the United States. If you use the Service from elsewhere, your information will be transferred to and processed in the U.S., where privacy laws may differ from your own.

14. Changes to this policy

We will post any changes here and update the effective date. If a change materially reduces your rights or expands how we use classmate data, we will email organizers and post a notice on the site at least 14 days before it takes effect.

15. Contact

Privacy questions, removal requests, and anything else: hello@reunionsoft.com. Reunionsoft, Tampa, FL.