Privacy Policy

Last updated: June 26, 2026

Brindis is an event seating planner. This policy explains what information the app handles, where it lives, and your rights. The short version: Brindis is local-first. By default everything you create stays on your own device. Cloud sync exists, but it is an optional, opt-in feature you turn on only if you choose to sign in.

Who runs Brindis

Brindis is operated by the Brindis team (San Francisco, California, USA). For any privacy question you can reach us at brindis.support@gmail.com.

What information Brindis handles

Unless you choose to sign in and turn on cloud sync, Brindis does not collect your event data — everything you create stays on your own device. The information the app stores locally for you is:

• Event details you enter: names of guests, table layouts, meal preferences, allergies / dietary notes, side / group assignments, captain assignments, and other planning information you type in. This belongs to you.
• Venue images you add: optional photos or floorplans of your venue, kept on your device as a background reference for your seating chart.
• Language preference: stored to keep the app in your chosen language.
• No analytics or tracking: the app contains no third-party analytics, advertising, or tracking SDKs.

Where your data lives by default

• On your device: by default everything is stored in your device's local storage. There is no account and no login required to use Brindis, and without sign-in nothing is uploaded to any server.
• Automatic local backups: Brindis keeps a small rolling history of your event on your device so you can restore an earlier version if you delete something by accident. These backups are local and never leave your device.
• Multi-device note: because everything is local by default, an event you create on your phone is not visible from your computer or vice versa unless you turn on cloud sync. Each device otherwise has its own independent storage.

Optional cloud sync (Premium / Pro)

Cloud sync is an opt-in feature. It is off until you sign in. If you sign in to sync, here is exactly what happens:

• What gets uploaded: a copy of the event(s) you choose to sync — guest names, table layouts, meal preferences, allergies / dietary notes, and your venue image (a downscaled copy) — is stored in the cloud so it appears on your other devices. Premium syncs one pinned event; Pro syncs all of your events.
• Why: solely to sync your own devices, so the event you build on your phone shows up on your computer and vice versa. We do not use it for anything else.
• Where: your synced event data is stored on Google Firebase (United States region), which acts as our hosting and database processor.
• How you sign in: your sign-in identifier is your email address. We use it only to authenticate you and link your synced events to you. There is no third-party social login.

Processors we use

• Google Firebase — hosting, authentication, and database for optional cloud sync (US region). Only used if you sign in to sync.
• RevenueCat — purchase management, used only if you buy Premium or subscribe to Pro (see Purchases below).

These are the only third parties that ever process your data, and each acts as our processor for the narrow purpose described. See Google's, Firebase's, and RevenueCat's privacy policies for how they handle data on our behalf.

Purchases

If you buy Premium or subscribe to Pro, that transaction is processed by the platform store (Apple App Store or Google Play) and by RevenueCat, our purchase-management provider, solely to validate, unlock, and restore what you bought. This is limited to the store receipt and an anonymous, app-generated user ID — it never includes your guests or your event data. RevenueCat acts as our processor for store transactions; see Apple's, Google's, and RevenueCat's privacy policies for how they handle them. If you never make a purchase, no purchase data is processed at all.

What we do not do

• We do not sell your data.
• We do not share your event data with anyone, and we never use it for any purpose other than syncing your own devices.
• We do not access your contacts, microphone, or location. The camera and photo library are used only when you choose to add a venue image — to take or pick that photo. That image stays on your device unless you turn on cloud sync, in which case a downscaled copy is synced together with the rest of that event (see "Optional cloud sync" above).
• We do not run analytics, advertising, or third-party trackers.

Your rights

• Delete data: from the menu you can delete any event, or clear your device's storage to remove everything locally.
• Delete your account and cloud data: if you signed in for sync, you can delete your account and all of your cloud-stored event data directly in the app. Deleting your account removes your synced data from Firebase.
• Export: you can export your guest list, seating chart, and meal report as PNG or text at any time.
• Access: your data lives on your device, and (if you turned on sync) a copy of your synced events lives in your own cloud account, which you can view, export, or delete in-app.

Guest information you enter

Brindis lets you enter information about your guests: their names, and optionally meal preferences and allergy or dietary notes. You enter this on their behalf, and Brindis stores and syncs it only so you can plan your event. Allergy and dietary notes are used only for that purpose.

Your rights under privacy laws

Depending on where you live, you may have rights over your personal data, such as to access, correct, delete, export, or restrict its processing, and to withdraw consent. You can exercise most of these in the app: delete events, delete your account and all cloud data, and export your data. For anything else, email brindis.support@gmail.com.

How long we keep your data

Data on your device stays until you delete it or remove the app. Synced data stays in the cloud while your account is active; when you delete an event it is removed, and when you delete your account all of your cloud data is permanently deleted shortly afterward. We do not retain copies of your event data beyond what is needed to run the sync service.

Changes

If this policy changes, the revised version will be published at the same URL with an updated date.

Contact

brindis.support@gmail.com