1. Controller And Contact
Wedlune is operated by Blaz Poklar s.p., a sole proprietor in Slovenia, who is the controller for the account and service data described here. Support and privacy requests: support@wedlune.com.
For privacy requests, contact support@wedlune.com. This address is monitored for access, correction, deletion, objection, consent, and other data-protection requests.
2. Information We Collect
We collect information you provide or create in the app, on guest-facing pages, or through website feedback:
- Account information: email address, name, partner name, authentication identifiers, language, currency, theme, subscription status, and partner-invitation details.
- Wedding details: wedding date, venue style, location, ceremony preferences, budget range, guest count, questionnaire answers, notes, and recommendation preferences.
- Planning data: guests and RSVP details, RSVP page designs and images, wishlists, wishlist images, private gift reservations, meal and dietary notes, seating, budgets, vendors, venues, accommodation, transport, attire, legal documents, timelines, checklists, payment milestones, message templates, photos, and shared shot list links. Dietary, accessibility, and similar notes may reveal sensitive information, so add only what is necessary. For a reservation, we retain the wishlist item, quantity, and minimal RSVP-party reference needed to let that party change or cancel it. The couple and other guests are shown quantities, not the reserving party's identity.
- AI feature data when you consent: accepted messages and responses, conversation titles and summaries, action proposals, recommendation criteria and results, feedback, source titles and URLs, consent records, and operational metadata such as the routed model, usage, cost, cache, and generation details.
- Technical data: device, app, and browser metadata; IP address and request data for website and Edge requests; local sync state; redacted error logs; security logs; rate-limit records; and timestamps needed to operate and protect the service.
- Optional analytics: limited usage events only if you explicitly enable analytics in the app's Settings. AI prompt and message content is not sent to application analytics.
The public website feedback form collects your message, category, optional rating and optional email address. We use these to answer requests, investigate problems and improve the service, based on our legitimate interests in providing support and understanding feedback. Messages are stored privately with Supabase and accessed by the operator for these purposes. Feedback is not automatically linked to an app account. The submission service uses a pseudonymous value derived from the network address to prevent abuse; hosting providers also process request metadata. To request access or deletion without an account, contact support and provide enough context to locate your message. Do not send passwords or unnecessary sensitive information.
3. How We Use Your Information
Account and planning services: we use account, wedding, invitation, planning and subscription data to authenticate you, sync your plan, provide collaboration and deliver purchased access, based on our contract with the account holder. Supabase hosts these data; the authorized partner receives shared planning data; RevenueCat and the relevant store process purchase and entitlement information. Account and planning data are kept while the account or shared plan remains active, subject to deletion and the retention details below.
Guest participation: ordinary guest contact details, attendance and meal choices support invitations and event planning. For guests who are not account holders, our basis is the legitimate interests of the operator and organizers in providing and managing the requested wedding service, subject to guests’ rights. The couple and authorized partner see submitted RSVP and dietary information; hosting services process it to deliver the service. Sensitive information, such as allergies revealing health data, requires an additional lawful condition; this notice and agreement to the terms do not themselves establish explicit consent.
Optional features: AI processing and usage analytics rely on your separate choices and consent where applicable. Advertising choices are handled separately through the app’s ad-privacy controls. Device permissions are requested separately. The AI, analytics and provider sections explain the data and recipients; AI withdrawal and account deletion are described below. Accepting the terms or acknowledging this policy does not enable these optional choices.
Security and operations: essential error and request diagnostics, security logs and pseudonymous rate-limit records support our legitimate interests in keeping the service reliable and preventing abuse. They are separate from optional usage analytics and can be processed when analytics is off. Access is limited to the operator and relevant hosting/service providers. The retention section gives the scheduled cleanup periods. Records required by tax, accounting or other applicable laws are processed to meet those legal obligations; relevant records may also be needed to establish or defend legal claims.
Account details are required to create and secure an account; other fields are optional unless marked as required for a feature. We do not sell wedding-planning data or make solely automated decisions with legal or similarly significant effects. AI output is advisory and changes require your review or confirmation.
4. Storage, Security, And Transfers
Cloud data, including private AI chat history and recommendation history, is stored with Supabase using authentication, Row-Level Security, per-wedding access controls, and encrypted transport (TLS). Uploaded photos, RSVP design images, wishlist images, and documents are stored in Supabase Storage with access controls. Cloudflare provides DNS, delivery, security, and hosting for wedlune.com and its public RSVP, gallery, and authentication-callback pages, and processes traffic and request metadata such as IP addresses.
Some service providers, including the global OpenRouter connection and routed providers, may process relevant data outside the EEA. Transfers subject to GDPR require an applicable transfer mechanism, such as an adequacy decision or appropriate safeguards including Standard Contractual Clauses. Contact support@wedlune.com to ask which countries and safeguards apply to a provider and how to obtain information or a copy of the relevant safeguards. This notice does not certify that every provider agreement or backup arrangement has been verified.
5. Local Data And Notifications
The app stores secure session tokens, remember-me state, device preferences, planning caches, queued offline changes and local reminder schedules. Local reminders may contain task titles and due times. Signing out clears account sessions, account planning caches, queued changes and reminders on that device. Some device preferences, such as language, theme or remember-me choice, can remain. Clearing app data through device settings removes locally stored app data. Signing out or clearing local data does not delete your server account or shared wedding plan; use account deletion for that.
6. AI Features
AI chat, recommendations and business discovery, venue lookup, and missing-task suggestions share one optional consent for the current policy version. Consent is recorded per account, reused across signed-in devices, and independent for each wedding partner. It is checked before saved AI results, caches, quotas, wedding context, or model calls are accessed. Some features separately require Premium. Route calculations and deterministic timeline generation are outside this consent.
When you consent and use an AI feature, secure Supabase Edge Functions send only the data needed for that request to the AI and search services listed in Section 7. This may include your screened question, sanitized recent history, guest-safe planning summaries, relevant saved public business details, public location and search criteria, and a pseudonymous routing value. Guest and couple names, contacts and notes; account and planning identifiers; files; internal notes; private route labels; and route coordinates are excluded. Detection is not perfect, so do not manually enter third-party personal data. AI-generated action proposals cannot make changes themselves: the app resolves private fields locally and asks you to confirm the exact change.
Wedlune privately stores accepted messages and responses, conversation titles and summaries, proposals and their status, recommendation criteria and results, source titles and URLs, feedback, and operational metadata in Supabase. Raw web-search excerpts and page content are not stored. Revoking consent locks all covered AI features and permanently deletes your AI conversations, messages, proposals, feedback, recommendations, recommendation selections, and follow-up responses. Imported businesses, accepted tasks, and other confirmed planning changes remain. Required consent evidence and limited security or rate-limit records may be retained.
Separately, route geocoding sends the endpoint text and optional country hint you enter, followed by selected coordinates for distance and duration calculation, to openrouteservice. It does not receive wedding, user, guest, or planning-record identifiers. Do not enter a private home address or other third-party personal data.
AI results may be incomplete or incorrect. Always review and independently verify availability, pricing, legal, scheduling, and other important information before use.
Usage limits: Free recommendations allow one successful generation per section per wedding with up to two results; Premium allows 10 per rolling 24 hours with up to four results. Free missing-task scans allow one successful scan per wedding with up to three tasks; Premium allows five per rolling 24 hours with up to five tasks. Free venue lookup allows two successful unique lookups per wedding; Premium allows 20 per rolling 24 hours. Premium AI chat allows 20 completed turns per rolling hour and 100 per rolling 24 hours per account. Cached responses, failed provider calls, and released claims do not consume quota; background refreshes and refinements do. Separate burst-abuse limits may apply, and operational quota metadata is retained to enforce limits and protect the service.
7. Third-Party Services
We use the following services:
- Supabase: authentication, database, storage, and Edge Functions.
- Google Play or the Apple App Store, and RevenueCat: purchases, subscription status, product identifiers, expiry dates, and transaction metadata. We do not receive full payment-card details.
- Cloudflare: DNS, content delivery, security, and hosting for the public website, RSVP, gallery, and authentication-callback pages; it processes IP addresses and traffic/request metadata.
- Google AdMob: free-tier banner ads, which may collect device identifiers, approximate location, ad interactions, and diagnostics under Google's policies. Premium users do not see ads.
- OpenRouter and its routed model providers: processing of minimized AI-chat and verified business-discovery requests. Eligible model endpoints are limited to those OpenRouter marks as Zero Data Retention and non-collecting.
- Exa: public-web research queries and retrieval of public page evidence for verified business discovery. Wedlune does not persist the raw evidence.
- openrouteservice: geocoding of user-entered transport endpoint text and route calculation from selected coordinate pairs.
- Google Gemini: stateless missing-task suggestions. Provider notices explain processing practices and are not additional terms that users personally accept through Wedlune.
8. Partner Collaboration And Guest Data
Wedlune lets you invite a partner to a shared wedding plan. We store invitation emails, invitation status, partner permissions, and activity entries. Depending on the selected role, a partner may view or edit shared data such as guests, budget, vendors, timeline, photos, and documents.
Do not add third-party personal data, including guest contact or dietary information, unless you have a lawful reason to do so and can share this privacy information with them if needed.
A guest who opens a valid RSVP link can view a published wishlist and reserve quantities regardless of RSVP response. The reservation-party association is used to prevent duplicates and allow that same party to edit or cancel its reservation; it is not exposed in couple-facing or guest-facing responses.
If one member deletes their account while a partner remains, the shared wedding plan, contributions, activity history, and shared files remain with the partner. Account-specific data and private AI history are not transferred.
Guest information can come from the couple or an authorized partner, or directly from guests through RSVP forms. The couple and authorized partner can see RSVP responses, meal choices and dietary notes. Anyone holding a valid public link may access the guest-facing information and actions allowed by that link, including the relevant party’s details; share links only with intended recipients. Guests can ask the couple to correct or remove their information, or contact support@wedlune.com without creating an account. Include enough information to identify the wedding and record, but do not forward a private RSVP link or token. We may request proportionate verification before acting. Only provide necessary information about others and make this notice available to them; do not assume their sensitive-data consent.
One partner with edit or view access and activity history is included on Free. Either member's direct Premium subscription unlocks the shared wedding; disconnecting removes only derived shared access. A valid public RSVP token is checked before plan state. Free RSVP uses the default presentation at up to 50 invited people and excludes wishlist data. Above 50, responses pause without revealing subscription details. Premium may show the preserved published design and wishlist; expiry preserves them and renewal restores them.
9. Usage Analytics
Usage analytics are off by default. If you turn them on in Settings, we collect limited in-app events such as sign-up, sign-in, questionnaire completion, recommendation generation, task actions, and aggregated screen/session counts. Events may be linked to your account so we can improve the product and understand feature adoption. You can turn analytics off at any time; doing so stops collection and clears locally queued analytics.
Essential operational diagnostics are separate from optional analytics: redacted application errors, request metrics and security/rate-limit records help operate and protect the service even when usage analytics is off. Their scheduled cleanup periods are described under retention. No external crash-reporting SDK is used.
10. Retention And Deletion
We keep account and planning data while your account is active. You can delete your account in the app under Settings → Delete Account or through our
Feedback and support records are kept according to the time needed to handle the request, investigate the issue and meet applicable legal or dispute-handling needs. Limited security, consent evidence, tax/accounting and legal records may be retained where necessary for those purposes. These criteria do not promise a fixed feedback, support, backup or third-party retention period. Contact support for the applicable retention information; provider-held records follow the relevant provider’s practices and legal duties.
Scheduled daily cleanup removes application error diagnostics and request metrics older than 30 days, and RevenueCat webhook event IDs older than 90 days. Scheduled hourly cleanup removes rate-limit records older than one day. These are age thresholds for scheduled jobs, not guarantees of deletion at an exact instant. The 90-day threshold covers webhook event IDs only, not all subscription, transaction or provider-held records.
11. Your Rights
If GDPR applies, you may request access, correction, deletion, restriction, portability, objection to processing based on legitimate interests, and withdrawal of consent where processing is based on consent. You can withdraw AI consent in Settings; Section 6 explains the resulting deletion and preservation of confirmed planning changes. You may lodge a complaint with your local EU/EEA data-protection authority.
12. Children
Account holders must be at least 16; any higher local age or legal-capacity requirement also applies. This is an eligibility rule, not a statement that Wedlune verifies age. Guest records may include children whose details are supplied by the couple, a partner or a responsible adult; a guest record is not an account. Limit children’s information to what is needed for the event. Contact support@wedlune.com about an underage account or concerns about a child’s data so we can review correction or deletion.
13. Contact Us
For privacy-related questions or requests, contact support@wedlune.com.