Seat Maker

Privacy & Data Usage

Last updated October 26, 2026

What We Collect

Account identifiers from email and password, Sign in with Apple, Google Sign-In, and Firebase anonymous authentication.
Email address and display name when a sign-in provider returns them.
An optional phone number when you explicitly choose to receive Seat Maker planning tips and product updates.
Push notification identifiers when notifications are enabled.
Onboarding answers, product activity events, feedback submissions, crash diagnostics, performance diagnostics, and subscription status.
App and device identifiers, advertising identifiers when permitted, installation and campaign attribution, and events such as registration, onboarding completion, paywall views, trial starts, and purchases.
Purchase details used for measurement, including product identifiers, transaction identifiers, the amount charged, and currency. Seat Maker does not receive your payment card details from Apple or Stripe.
On our website, page visits, referral and ad-click information, browser and cookie identifiers, and signup, checkout, and purchase activity.
Shared seating snapshots when you create an optional public web link.

Guest names, imported contact selections, table assignments, room layouts, and seating arrangements are edited on your device. When cloud sync is enabled, the resulting seating data is synced to your account so it is available the next time you sign in on another device. Contact permission is used to help you choose names; Seat Maker does not send your address book to advertisers.

Product analytics and session replay

PostHog collects page and screen visits, feature use, clicks, performance and error diagnostics, session or installation identifiers, and referral information. App events can be associated with your signed-in account. Website session replay can record page content and interactions; inputs, the shared seating viewer’s guest areas, and our Help & chat panel are configured to be masked. Native version 3.2.4 supports PostHog and Amplitude recordings of selected public onboarding screens. The app is configured to stop recording for personal planning content, account details, guest data, imports, sharing, payment screens, and background or system interfaces. Recording privacy controls are still being verified; these controls do not establish that sensitive content can never appear in recordings. Browser cookies or local storage may remember analytics identifiers. Declining iOS advertising tracking does not disable product analytics.

Event websites, RSVPs, and venue discovery

When you use online event tools, we process the event details, photos, guest details, invitations, and RSVP responses you provide. Published website content is available to people who can access its link; include only information you intend to share. Hosts sign in to manage online events. Invited guests can respond in a browser without an app or account. Venue searches process the area and filters you choose. Online services require internet. Invitation email delivery processes recipient email addresses, invitation content, personalized links, and delivery records. Resend handles delivery and, when enabled, email opens and link clicks. Emails are sent from a Seat Maker subdomain, not from the host’s personal mailbox. We use delivery and complaint records to manage retries and suppress further sends to blocked addresses. Private host–guest conversations and delivery records are stored online. Google Sheets and spreadsheet imports read the list you select; imported guest details may be included in account sync and online events.

Assistant and support conversations

Seat Maker Assistant stores chat history on your device. Supported AI planning uses Apple’s on-device models. AI diagnostics sent to PostHog include timing, outcomes, and tool metadata, not prompts, replies, or guest details. Website Help & chat answers are handled locally until you choose Send to support; that action sends your question to our team through PostHog Conversations. Avoid including sensitive guest information in support messages. The public browser assistant at /assistant runs AI on your device through WebLLM. When a question needs the optional browser model, the assistant downloads model files from their hosting providers and caches them locally. Reviewed product answers can work without that download. Chats are saved in this browser, do not sync with your account, and can be deleted from its sidebar. Browser or device cleanup can remove them. Questions and replies are not sent to a cloud AI service.

Why We Use It

Save and sync your tables, guests, and room layouts across devices when you sign in.
Associate account records with Firebase Authentication.
Store onboarding responses, feedback, and product activity so we can improve the app.
Render shared seating layouts in the optional public web viewer.
Diagnose crashes and reliability issues.
Understand feature usage and conversion behavior.
Measure which advertisements lead to app installs, registrations, trials, and purchases, and improve our advertising campaigns.
Send optional push notifications and measure notification engagement.
Send optional planning tips and Seat Maker product updates by text message when you provide a phone number.
Manage subscription state through Apple and Superwall.

Third-Party Services

Seat Maker uses Firebase Authentication, Firestore, and Analytics; Google Sign-In; Sign in with Apple; Amplitude; PostHog; Sentry; OneSignal; Superwall; AppsFlyer; TikTok Business; Meta advertising tools; Apple StoreKit subscription services; Stripe for web payments; DataFast and Vercel for website measurement; and standard platform sharing tools. Each provider processes data under its own privacy terms. Optional phone numbers are stored with your onboarding record and registered with OneSignal only after you choose to submit them.

Advertising Measurement

We use AppsFlyer to attribute app installs and activity to advertising campaigns. When a partner integration is enabled, AppsFlyer shares selected app events with advertising partners, including Meta. The app also uses TikTok Business to report app activity. Purchase measurement includes the product, transaction identifier, amount charged, and currency from verified Apple transactions. Trial-start events are separate from paid purchases. We do not send imported contacts or seating-chart guest lists as advertising event data.

On iOS, we request App Tracking Transparency permission where available before starting advertising SDK sessions. Declining prevents access to Apple's advertising identifier. Account services, product analytics, and Apple's aggregate attribution can still operate. You can review or change your permission in your device settings; see Apple's tracking controls.

Our website uses the Meta pixel on signup and purchase pages to measure visits and conversions. It can send page URLs, browser information, cookie identifiers, and event details such as checkout and purchase amounts to Meta. When server-side conversion reporting is enabled, we also send purchase or subscription events and a hashed email address, plus browser or ad-click identifiers when available, to help match conversions. Hashing changes the email's format; it does not make this matching data anonymous.

Your Choices

Use the app without signing in.
Deny Contacts or Photo Library permission.
Choose Ask App Not to Track when the iOS tracking prompt appears, or change Seat Maker's permission in Settings, Privacy & Security, Tracking. You can still use the app if you decline.
Use your browser's cookie and tracking controls to limit website measurement. The iOS tracking setting applies to the app, not to a separate web browser.
Avoid creating public share links.
Skip the optional phone-number step or reply STOP to opt out of text messages at any time.
Clear local seating history from inside the app.
Clear planning data with Settings, Account, Delete All Data, or request full account deletion at seatmakerapp.com/delete-account.

Account Deletion

Delete All Data in Settings, Account clears local seating history and the synced planning data for the signed-in user, then signs you out. It does not by itself delete the Firebase Authentication account. To delete that account and request removal of account records, use the request form below or email us.

If you cannot access the app, submit a request at seatmakerapp.com/delete-account or email hello@seatmakerapp.com with the email address tied to your Seat Maker account. You can also call or text (570) 661-1277. We process deletion requests within 30 days.

To remove specific data without deleting your account, use seatmakerapp.com/delete-data. This includes requests to remove analytics records linked to you. Deleting your account does not cancel an Apple or Stripe subscription; manage it with the provider you paid.

Data Retention

Synced planning data persists until you delete it or request account deletion. Shared snapshots created from the in-app share flow expire automatically 30 days after creation. Diagnostic, analytics, feedback, and payment records may remain with the relevant provider for the period required by its policy, security, fraud-prevention, tax, or legal obligations.

October 26, 2026 feature update: governing English text

This update applies to the app, website, and connected event and partner services. It supplements the sections above.

Optional founder conversations and linked product activity

Paid customers may receive an optional invitation to speak with a Seat Maker founder. If you submit it, we store the name and phone number you provide, your permission and its date, and your account identifier so a founder can contact you about your Seat Maker experience. You can skip this invitation without affecting paid access and can withdraw permission or request deletion at hello@seatmakerapp.com. Our private owner dashboard connects this request to available account, purchase, onboarding, referral, and product-usage records through verified account identifiers. The form is configured to exclude phone numbers and names from analytics events and session recordings. Browser recording controls are configured to mask inputs and private planner text. Starting with native version 3.2.4, PostHog and Amplitude can record selected onboarding screens containing public setup choices. The app is configured to pause native recording for personal planning content, account details, guest data, imports, sharing, payment screens, and background or system interfaces. Recording privacy controls are still being verified; these controls do not establish that sensitive content can never appear in recordings. Recorded usage and first-observed dates may be incomplete and do not necessarily establish when an app was downloaded. Contact permission does not subscribe you to automated marketing messages.

Responsibility, sources, and privacy rights

Austin Frankel provides Seat Maker and can be contacted at hello@seatmakerapp.com. Account and service information comes from you, your sign-in and payment providers, and the devices and services described above. Hosts and authorized collaborators provide guest information; guests can provide their RSVP answers. Where applicable law requires a legal basis, we process necessary account and service data to provide the service you request, payment and compliance records to meet legal obligations, and security and reliability data for legitimate interests subject to your rights. Optional permission-based features rely on your permission or consent where required. Depending on your location, you may request access, correction, deletion, a portable copy, restriction, or objection, withdraw consent for processing based on consent, and complain to your local privacy regulator. Contact us to exercise these rights; limitations needed to protect other people and meet legal duties can apply. Withdrawing consent does not undo earlier lawful processing.

Browser AI and local planning context

When a question needs the optional browser model, the website Assistant downloads a free Qwen model and WebLLM runtime into a compatible browser. Reviewed product answers can work without the download. Downloads are served by Hugging Face and GitHub/CDN infrastructure; these providers receive normal network information such as your IP address and request headers, but our assistant does not send your questions, replies, or optional planning details to them for inference. AI processing happens on your device. Conversations are saved in this browser and can be deleted from the sidebar. They do not sync with your account; clearing browser site data also removes them. Model files may remain in browser caches until cleared through your browser’s site-data controls. We exclude the assistant panel from our analytics autocapture and session replay. Ordinary page visits and navigation outside the panel may still be measured. Browser AI is a different model from Apple’s native assistant. No paid AI API or AI account is required. The basic product guide works without enabling the model.

Recent planning and invitation features

Guest records can include names, contact information, notes, dietary details, RSVP answers, seating assignments, and invitation status. Enter sensitive details only when needed and when you have authority to use them. Contacts access reads the selections you choose. CSV, spreadsheet, Google Sheets, room-plan, and photo imports process the content you select; using sync, online events, or publishing can store the resulting content online. Event dates, venue details, checklist progress, preferences, and locally scheduled reminder settings support planning. Notifications depend on your permissions. Appearance changes do not change your seating assignments. Invitation cards, personalized invitation links, QR codes, previews, and exports may contain guest or event information. A preview is not a published site, and a saved card is not a sent invitation. Public event pages and shared links are accessible to recipients who have access to their links; exported copies can be kept or forwarded by recipients.

Partner workspaces, service providers, and retention

Authorized partner workspaces store event content, membership and access-window information, synchronization revisions, edit leases, and access or administrative records. Event administrators and authorized contributors can access content according to their role; ending sponsored access is separate from cancelling an independently purchased subscription. Firebase and hosting providers process online data; Resend handles invitation emails and delivery, bounce, complaint, and optional open/click records. Opens and clicks do not prove that a person read a message. Local plans remain available offline; account sync, venues, publishing, online RSVPs, invitation delivery, and collaborative work require internet. Drafts, published event records, and guest responses are distinct from the 30-day public seating snapshots described above. Retention depends on the feature, deletion request, provider, and applicable legal obligations. Deletion can leave limited payment, security, and backup records while retention obligations or backup expiry apply, and cannot recall exported copies.

Privacy requests, security, and policy changes

Contact hello@seatmakerapp.com for access, correction, deletion, or other privacy requests available under the law that applies to you. We may verify your identity before releasing or changing personal information. Hosts should provide their guests with appropriate information about the guest data they collect and respond to requests concerning their events. Service providers may process data in countries other than yours under their applicable terms and safeguards. We use access controls and other protective measures, but cannot guarantee that every device, link, or online service is free of security risks. We update this policy as our features and data practices change and display the review date. Contact us before submitting information you do not have authority to share.

Guest information about children

Hosts using Seat Maker for family events or classrooms must have the authority and any parent, guardian, school, or other permission required to enter information about children. Avoid adding unnecessary contact information, sensitive notes, photos, or identifying details to public pages or exports. A seating-list entry does not create a child’s account. Contact hello@seatmakerapp.com if information about a child was submitted without the required authority so we can review and remove it as appropriate.