Invitation Studio and RSVP
The web studio saves invitation drafts to your account. An unfinished draft is not visible through a guest link. Publishing makes the chosen event details available to people with the invitation link; later edits go live when you publish again. Hosts can manage their invitations and guest lists after signing in.
We store your profile name, invitation details, household names, reserved seats, RSVP replies and answers. Passkey sign-in stores a public credential and uses an essential session cookie; we never receive your device password or biometric information. Guests can view and update the reply associated with the invitation their host sends them.
If the host chooses Connect Quinara on their own iPhone, the app receives a token for that one invitation (stored in the iPhone Keychain; only a hash is stored on our side). The app then reads that invitation's households, replies and guest links into the guest list on that iPhone, and can add guests the host already keeps in the app as households. Nothing else in the app is uploaded. The host can disconnect from the studio or the app at any time.
Studio and invitation pages do not load our GA4 or PostHog scripts. Cloudflare processes request metadata to serve and protect the service. Session cookies expire after 30 days, sign-in challenges after five minutes, and request-rate buckets within an hour; expired records are removed on subsequent writes. Invitation and RSVP data remains until the host deletes the invitation or the account. Unfinished drafts from a browser that never created an account are deleted 30 days after creation once their session has expired. Clearing browser data does not delete an invitation. Signed-in hosts can delete their account from the account menu in the studio; this permanently removes the account, its passkeys, every invitation, all guest replies and links, and app connections. Contact privacy@quinara.app for other privacy requests.
Quinara is a local-first event planner. This policy explains, in plain language, exactly what we collect, what we do with it, and what we never do.
The short version
- Your event database is stored locally on your device. Quinara does not operate servers that store that database.
- Starting with iOS version 1.0.19, Quinara sends PostHog a full-fidelity screenshot replay of every app session for product troubleshooting and analytics. Text inputs, images, and sandboxed views are not masked.
- Replays can include names, contact details, notes, amounts, images, and other event content visible or entered in the app, together with diagnostic logs and network request metadata.
- On eligible devices, Apple AdServices attribution can tell us whether an install came from our Apple Ads campaign. We use this only to measure our own campaign performance, not for cross-app tracking or personalized ads.
- Quinara does not collect health data, payment card numbers, or government identification of any kind.
- RevenueCat manages subscription status only — it never receives your event data.
- The quinara.app website uses Google Analytics 4 to measure aggregate site usage. Google Signals and ad personalization are turned off.
1. Who we are
Quinara is operated by Openverse. If you have questions about this policy, contact us at privacy@openverse.tech.
2. What we collect
Quinara stores the event database you enter — quinceañera's name, event date, budget, checklist items, padrino/madrina pledges, guest and court names, and vendor details — locally on your device using Apple's SwiftData framework. Quinara does not operate servers that store that database. Session replay can transmit the same content to PostHog when it is visible or entered in the app, as described below.
Analytics
Starting with iOS version 1.0.19, Quinara records every app session in full-fidelity screenshot mode and sends the replay to PostHog for product troubleshooting and analytics. Text inputs, images, and sandboxed views are not masked. Replays can include event names, guest and court names, contact details, padrino and vendor details, notes, checklist content, images, budgets, and other amounts visible or entered in the app. Replays also include diagnostic logs and network request metadata. Product analytics and replays use an app-generated identifier and are not used for advertising or tracking across other companies' apps or websites. Website tools send events and ranges such as a budget or guest-count bucket, not the exact values entered.
Website analytics
The quinara.app website uses Google Analytics 4 to measure aggregate website usage — pages viewed, referrer, device type, and approximate location derived from IP address. We do not enable Google Signals or ad personalization features, and this data is not used for advertising. See Google's privacy policy for how Google handles this data.
Apple Ads attribution
On eligible Apple devices, Quinara uses Apple's AdServices framework to learn whether an install came from an Apple Ads campaign. When Apple reports a match, we send the campaign, ad group, keyword and ad identifiers, conversion and placement details, country, and claim type from Apple's standard attribution response to PostHog with the app-generated identifier and subsequent product and purchase events. Quinara does not request App Tracking Transparency permission, so it does not receive the detailed response that can include click or impression dates. We use this Advertising Data only to measure our own Apple Ads performance, not to show personalized ads or track you across other companies' apps or websites. When Apple reports no match, we record only an organic attribution status.
Purchases
Subscription purchases are processed by Apple and RevenueCat. RevenueCat receives a device identifier and purchase/receipt data to validate your subscription status — it does not receive your event data.
No health, no payment, no government ID data
Quinara does not collect health data, payment card numbers, or government identification of any kind.
3. Your choices
You can delete locally stored event data from Settings → Reset All Data. Uninstalling the app also removes it from your device. These actions do not delete records already sent to PostHog. To request deletion of pseudonymous analytics or visual records, contact privacy@quinara.app.
4. Who we share your data with
Quinara works with a small number of infrastructure providers:
- PostHog — Product analytics, Apple Ads attribution measurement, and current full-fidelity iOS session replay, which can contain app content visible or entered on screen, diagnostic logs, and network request metadata.
- RevenueCat — Subscription management via a device identifier and purchase/receipt data, not your event data.
- Apple (App Store and AdServices) — App distribution, payment processing, and first-party Apple Ads attribution, governed by Apple's terms.
- Google Analytics — Aggregate website usage measurement for quinara.app via Google Analytics 4, with Google Signals and ad personalization disabled.
We do not sell, rent, or license your data to any third party.
5. Children's privacy
Quinara is an event-planning tool, not designed for and does not knowingly collect data from children under 13. If you believe a child under 13 has used the app and shared personal information with us, please contact us and we will address it promptly.
6. Changes to this policy
If we make material changes to this policy, the updated date at the top of this page will reflect the most recent revision. Continued use of the app after changes take effect constitutes your acceptance of the revised policy.
7. Contact
Questions about this policy? Contact us at privacy@openverse.tech.