Skip to content

Seat Maker

Privacy & Data Usage

Last updated

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.

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 when configured; 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.

Terms of Use · Open shared layout viewer