What we collect. Why we collect it. What we do with it.

Simpli-FI Events is a sub-brand of Simpli-FI OS LLC, a Texas limited liability company. Reach us at events@simpli-fi-os.com.

When you submit the lead-intake form at /get-started, we collect the fields you fill in: name, email, organization, role, event size, events per year, next event date, current event app vendor, pain points, decision-maker status, decision factors, and any referral organization or referrer contact email you choose to provide. We store that record in a Supabase database owned by Simpli-FI OS LLC, use it to respond to your request, scope a possible event project, manage any referral credit, and notify our team by email so we can usually reply by the next business day.

When you submit the Beautiful Histories Travel Desk form at /travel, we collect the fields you choose to provide about your role, business-travel rhythm, rough monthly spend band, point programs, point-balance range, destination, travel window, trip purpose, cultural interests, and consent preferences. We use that record to create an internal handoff packet for Beautiful Histories. Do not submit card numbers, bank logins, passport files, dates of birth, account screenshots, or other sensitive financial or travel documents through this form.

We log standard request metadata at the edge (IP, user agent, referrer, path) for security and rate-limiting. If Vercel Web Analytics is enabled, we use it in privacy-first mode; it does not set cookies or track individual visitors across sites. We do not run third-party advertising trackers.

Lead-intake rate-limit keys are kept only to slow abusive or accidental repeated submissions. They reset after about ten minutes, and stale keys are deleted by the rate-limit service as new intake requests are processed.

When you interact with the feedback survey at /feedback, the page records a per-tab session identifier, the user agent string, the page referrer, and the in-page event you triggered (such as “step viewed” or “submission attempted”) into a Supabase analytics table owned by Simpli-FI OS LLC. The session identifier is created in your browser, lives only in your tab, and resets when you close the tab. We use this signal to make the survey work and to learn which steps lose people. We do not link it to your account or to third-party advertising profiles.

When a customer runs an event on our platform, the attendee data we handle is the data their organization has chosen to provide. This typically includes name, registration email, organization, role, and optional photo for digital badges. Sponsor lead retrieval is opt-in per attendee scan. We do not share attendee data across tenants. We do not sell attendee data to anyone, ever.

Live polling, Q and A, QR networking, attendee profiles, sponsor lead retrieval, room feedback, and message preferences may collect the choices, scans, comments, profile fields, device installation IDs, timestamps, and event context needed to provide the feature. Sponsor lead data is shared only when an attendee affirmatively scans, opts in, or otherwise consents through the event flow.

Voice memos or recording-related features are enabled only when an event contract and on-screen consent flow allow them. If enabled, we store the recording, transcript, related metadata, and retention status needed for the customer workflow. Some review and feedback tools also save local browser drafts in localStorage so a user can resume their own unsent notes.

Venue and city images are used as editorial references, not as endorsements unless a venue expressly agrees otherwise. We track source, permission status, credit requirements, approval notes, media-kit links, and audit dates for public venue imagery.

Lead-form data, Beautiful Histories partner referral data, and customer event data are stored in Supabase Postgres instances under Simpli-FI OS LLC, with production regions selected for the customer use case when we provision the project. Hosting, transactional email, security logs, backups, and other subprocessors may process the limited data needed to provide those services under their own security, subprocessor, and data-processing terms. We use database and application access controls to limit customer event data to authorized workflows.

We share lead-form data only with the subprocessors required to operate the site: Vercel for hosting, Supabase for storage, Resend for transactional email. A signed Data Processing Addendum with Resend is on file as of 2026-05-21 and covers EU SCCs and the UK Addendum. If you submit the Beautiful Histories Travel Desk form and consent to handoff, we share the request with Beautiful Histories so Shelli or the team can review and follow up. We use subprocessors under their published or signed security, subprocessor, and data-processing terms. We do not sell data. We do not share data with advertisers.

For internal venue intelligence and provider research used in customer engagements, we may use Firecrawl as a research subprocessor to fetch publicly available pages from venue and association websites. Lead-form data, attendee data, and customer event data are never sent to Firecrawl. Each Firecrawl call is recorded in an internal audit log with the requested URL, the allowlist decision, and the credits consumed.

Lead-form and Beautiful Histories partner-referral records are kept for 36 months from last contact, then deleted or archived with limited internal access for ordinary business recordkeeping for up to 7 years. Closed-lost leads are kept 12 months for win-back outreach, then deleted or archived under the same limit. Referral contact data follows the same schedule unless a credit is issued, in which case the credit record is retained while the credit is active and for ordinary business recordkeeping after it expires. Deleted records may remain in provider backups until those backups expire under the provider’s normal backup schedule. Customer event data is retained for the term of the contract plus 90 days, then exported to the customer and deleted or archived according to the signed order form.

You can ask us what we have, ask us to correct it, ask us to delete it, or ask for a copy in machine-readable form. Email events@simpli-fi-os.com with the subject line “Privacy request” and we will usually confirm within 5 business days.

When a customer’s event runs on our mobile app (for example the TEXPERS Events app), the app works without an account. It creates a random installation identifier on your device so the event can count opens, remember your message preferences, and attach the optional profile you choose to fill in (name, role, organization, email). If you turn on alerts, we collect a push notification token through Apple’s or Google’s notification service to deliver them. The camera is used only to read QR codes on screen; camera frames are processed on your device and are not stored or uploaded.

Anonymous session feedback is built to stay anonymous. When you rate a session, the app sends a random one-time token instead of your installation identifier, the stored rating carries no installation identity, and reports are produced as session-level totals. Other in-app activity (such as poll answers and screen opens) is recorded against the installation identifier and follows the customer event data retention schedule in section 10. The optional “claim your free Simpli-FI ID” link opens a separate product with its own privacy policy; nothing is shared with it unless you sign up there. The app is built with Expo and delivered through Apple and Google; their build and store services process the app binary, not attendee records.

This is a B2B platform. We do not knowingly collect data from anyone under 18. If you believe a child has submitted information to us, contact events@simpli-fi-os.com and we will remove it.

When we update this notice, we change the “last updated” date at the top. Material changes are emailed to active customers and posted to the home page for 30 days.