SF Societies Privacy Policy

SF Societies operates community, member and event experiences at sfsocieties.com and sfsociety.vip. This policy explains how information is used in those experiences. For privacy questions or requests, contact hello@sfsocieties.com.

Information we collect

• Account and login information: your email address, name, identifiers supplied by a login provider, session records and login activity. If you choose Facebook Login, we request your app-specific Facebook user ID, name and email address, when Facebook makes it available. We do not request your Facebook password, friends list or permission to post to Facebook.
• Information you provide: member profile details, social links, photos, interests, recommendations, messages, nominations and other submissions. Information you publish in a member profile or submit for an approved public event or contestant page may appear publicly.
• Event and participation records: invitations, registrations, guest and membership information, referrals, raffle entries, votes and royal campaign gifts. We also receive event and contact information from organizers, connected Luma and Folk accounts, and imported lists. These records can include contact details, organizations, social links, registration answers, preferences and organizer notes.
• Transaction information: payment status, order amount and payment-provider references. Stripe processes payments for royal campaign gifts; external ticket services process their own ticket purchases.
• Technical and communication records: login and site activity, browser/device information, approximate location where available, referral information, email delivery and engagement events, preferences and suppression records.

How we use information

We use information to sign you in, maintain your account, operate profiles and events, manage invitations and participation, process gifts, respond to requests, maintain contact records, measure use of the service and protect accounts and event integrity. Records may be matched across sources using contact identifiers and other available evidence; administrators can review uncertain matches.

Event admission can include automated checks of registration status, membership records or organizer restrictions. Contact us if you believe an account match or event decision is incorrect.

Email preferences govern applicable event and promotional messages. Signing in with Facebook does not itself enroll you in marketing or publish a profile. Authentication and service messages are separate from promotional subscriptions.

Facebook Login

We use Facebook information to authenticate you and connect your Facebook identity to your SF Societies account. A first connection requires an email confirmation or an explicit connection from your signed-in SF Societies profile. We retain the account association so later Facebook logins return to that account. Facebook access tokens are used during verification and are not retained by our application.

You may request removal of the Facebook connection or deletion of your SF Societies account using our data deletion instructions. Removing access in Facebook does not itself delete information already held by SF Societies.

Service providers and other recipients

Social login connects to your existing SF Societies account using a verified email, or creates an account if you are new. You can also connect supported methods in My profile. X / Twitter login uses your authenticated X identifier, name and confirmed email when available. If X does not share a confirmed email, we ask you to verify one during login. These connections are private. Temporary authorization credentials protect login, and X user access tokens are discarded after verification. ChatGPT login shares only sign-in identity details, not chats, files or other ChatGPT account content.

Providers help deliver the service, including OpenAI Sites and Cloudflare for hosting and storage, Resend for email, Stripe for payments, and Luma for event registration. Connected login providers process login requests under their own policies. Folk and organizer-supplied lists support contact and event administration.

Where enabled, OpenAI services assist with email replies, event commentary or generating portraits. Information needed for the selected feature, such as message content or a source image, is processed by that service. Publicly published content can be viewed and shared by others. Authorized administrators access private records to operate the service.

External services, including ticketing and login providers, have their own privacy policies and request processes. An SF Societies request does not automatically delete an independent account you hold with them.

Cookies, retention and security

We use cookies and similar session mechanisms to keep you signed in and protect login flows. Signing out or clearing these cookies ends or disrupts the corresponding browser session.

We retain information to operate accounts and events, maintain transaction and historical records, resolve issues, honor communication preferences and prevent abuse. Retention depends on the type and purpose of the record. Account deletion requests are reviewed across relevant records; limited information may need to be retained for transaction, security, dispute or legal purposes. We will explain relevant exceptions when responding to a request.

We use access controls and other technical safeguards, but no online service can guarantee absolute security.

Your choices and requests

You can edit available profile fields, use email unsubscribe controls, or contact hello@sfsocieties.com to request access, correction or deletion of information. We may need to verify that the information belongs to you before acting. Do not send passwords, login codes, payment-card details or identity documents in an initial request.

We will update this page when our practices change and identify the effective date of the updated policy.