Privacy Policy

RosenVows is a service operated by Mohamed El Assri, Bahnhofstrasse 14, 3904 Naters, Switzerland. RosenVows is currently a brand and service operated by an individual; it is not an incorporated or registered company.

For all general and privacy-related enquiries, contact hello@rosenvows.com or write to RosenVows, c/o Mohamed El Assri, Bahnhofstrasse 14, 3904 Naters, Switzerland.

Depending on how the platform is used, RosenVows may process information relating to:

• couples creating or claiming invitations and wedding workspaces
• professional wedding planners and their team members
• CRM leads / prospective clients entered by a wedding planner
• wedding guests and their +1 companions
• vendors and service providers saved to a wedding
• people appearing in uploaded documents, photos or other media
• website visitors

When an account is created or a business profile is set up, we process information such as name, email address, authentication and account information, business name, planner contact information, team membership, account type and account status.

Wedding workspaces and invitations may contain the couple's names, wedding date, venue and location, wedding schedule and timeline, tasks, budget entries, saved vendors, seating plans, notes, documents, invitation content and design, and the permission settings that control what a wedding planner may access.

Invitations and RSVP forms may collect a guest's name, email or contact information where provided, household or group information, attendance response, +1 information, menu selection, dietary preference, RSVP responses and answers to custom questions.

Guest information can sometimes be entered by a couple or their wedding planner before the guest directly interacts with RosenVows (for example when a guest list is imported or prepared in advance). Guests can read this Privacy Policy at any time without creating an account; a link is available on public invitation and RSVP pages.

Optional Google Contacts import: for Save the Date and Digital Invitation features where offered (not Smart Invitation or printed-only products), a signed-in couple may choose to connect their own Google account and grant RosenVows read-only access to Google Contacts through the Google People API. The permission requested is https://www.googleapis.com/auth/contacts.readonly. RosenVows uses this access only to display the contact names, email addresses and phone numbers available in that user's Google Contacts so the user can choose which people to add to their wedding guest list. RosenVows cannot edit or delete the user's Google Contacts.

Google Contacts are not imported automatically. Contacts that the user does not select are not created as RosenVows Guest records. Only the contacts the user explicitly selects are saved to the relevant wedding guest list, where the selected name, email address and/or phone number then follow the same access, retention, correction and deletion rules as other Guest information described in this Policy. Importing a contact does not itself send an invitation or message; sharing by email, SMS, WhatsApp or another channel is a separate user action.

Optional iPhone Contacts import: where supported in the RosenVows iOS app, a user may open Apple's system contact picker and choose specific people to add to the wedding guest list. RosenVows receives only the contact details returned for the people the user selects; it does not automatically receive or copy the user's full iPhone address book or unselected contacts. The selected details are then treated under the same rules as other Guest information in this Policy.

RosenVows does not sell Google user data, use it for advertising or retargeting, use it for profiling, credit decisions or unrelated purposes, or use Google Contacts data to train generalized or personalized AI/ML models. Human access to Google-derived contact data is not permitted except where necessary for security, legal compliance, or support specifically requested and authorized by the user. RosenVows' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Users can revoke RosenVows' Google access at any time through their Google Account permissions; revoking access prevents future reads but does not automatically delete Guest records the user previously chose to import, which can be deleted from RosenVows separately.

We treat allergy and medically relevant dietary information separately from ordinary preferences such as vegetarian or vegan. Entering this information is always voluntary.

When a guest chooses to enter allergy or health-related information in an RSVP, it is collected for one purpose only: so the guest can be accommodated at the event. It may be visible to the couple, their authorized wedding planner and team, and may be passed on to relevant wedding service providers (for example the caterer) when necessary to accommodate the guest. It is not used for any other purpose.

Consent for this information is handled separately from general acceptance of our Terms; it is never bundled into other agreements.

AI-assisted organization: to make this information usable in practice (for example for a caterer), RosenVows may use an automated AI step that only organizes what the guest wrote — it groups the statement into practical categories such as nuts, gluten or dairy and produces a short neutral restatement. The guest's original wording is always stored unchanged and remains the authoritative record, and it is always shown alongside any organized output. This step adds no information the guest did not write. It does not diagnose, does not assess or determine severity, and does not decide anything about the guest: a statement that the allergy is severe is only recorded because the guest wrote it themselves. Where the wording cannot be organized with confidence, it is flagged so that a person reads the guest's original text. If this step fails it changes nothing — the RSVP and the original wording are already saved. The organized output is stored with the same RSVP, is deleted together with it, and is also removed immediately if the guest's allergy information is cleared or the guest changes their answer to not attending.

Professional wedding planners can use RosenVows to create client weddings and invitations, store client details, manage CRM leads, prepare and send service proposals and planning contracts, record client responses and electronic signatures, assign questionnaires, manage guests and RSVPs, manage tasks, budgets, professional timelines, seating, venue floor plans, vendors, documents and shared notes, collaborate with authorized team members, use reusable workflow templates and automations, manage consultation scheduling and client communications, and use the platform's business-finance and reporting tools.

Planner scheduling can process booking-type settings and availability together with client booking records such as name, email, phone, requested time, timezone, meeting mode or location, notes, answers, booking status, cancellation/rescheduling tokens and, where the Planner chooses to sync a booking, connected-calendar event identifiers and meeting links. A booking can also create or update the related CRM lead and communication history.

The Communications Hub can consolidate records of business emails, wedding messages, meetings, proposals, contracts, invoices, payment-status events and questionnaires so that the Planner has one chronological client history. RosenVows stores the content or summary, direction, channel, status, timestamps, relevant client/workspace identifiers and provider metadata needed to provide this history. Planner-authored email templates remain under the Planner's control.

Reusable workflow templates and automations can store the Planner's template configuration, triggers, steps, timing, generated tasks, budget structures, timeline events, questionnaire assignments, run status and technical error information. Automations carry out the actions configured by the Planner; they are operational workflow tools and are not used by RosenVows to make significant legal or similarly important decisions about clients or guests.

Venue floor plans can store room dimensions, object labels and types, positions, dimensions, rotation, locking state and links to seating tables. These layouts are operational planning diagrams and do not represent precise device geolocation or a certified architectural or safety plan.

Planner business-finance tools can process planner-service invoices, installment schedules, amounts received, expenses, service-package information, lead-source and profitability data, tax/VAT fields and operational reporting summaries. Where a Planner adds an external payment URL for a service installment, that URL belongs to the Planner or its chosen provider; RosenVows can record the URL and payment status but does not receive the Planner's service revenue through that external link.

When a couple claims their wedding, they become the owner of their wedding data. Permission settings chosen by the couple then determine which areas the planner and their team members can continue to access.

Optional planner account connections: a professional planner may connect their own Google Workspace or Microsoft 365 account so RosenVows can perform actions they explicitly request, such as sending an email from their mailbox or creating a calendar event with a Google Meet or Microsoft Teams link. RosenVows receives the minimum OAuth permissions configured for these features and uses the provider access token only for the connected planner's requested business workflow. Provider credentials and OAuth tokens are managed by Base44's app-user connector infrastructure rather than stored in RosenVows application records. A planner can disconnect the account at any time, which prevents future provider actions.

Wedding planners may assign questionnaires to their couples. Questions marked as private/internal planner questions are never shown to the couple. Questionnaire responses are stored with the specific wedding they belong to and are used only for planning that wedding; they are visible to the couple's authorized planner and team, not to other planners or businesses.

Wedding workspaces can contain uploaded documents (for example contracts, quotes or floor plans) and notes. Documents and notes are either planner-private or shared with the couple, according to the visibility chosen when they are created. Documents are stored privately and downloaded only through time-limited access links after a permission check. RosenVows does not manually review the contents of these documents.

The Live Wall lets guests upload photos, videos, voice notes and messages for the event. The host can moderate or remove posts. Participants are responsible for the media they upload.

Three months after the wedding date, a daily process removes the event's Live Wall posts from RosenVows. We attempt email reminders 30 and 7 days beforehand, and the host can download media before removal. Failed removals remain eligible for retry; review media is stored separately.

Removing a post from the application is not the same as erasing its hosted file or every backup. Files and backups held by Base44 are subject to its separate storage-deletion processes. We cannot promise that every hosted copy is erased at the three-month deadline. Contact hello@rosenvows.com for a storage-level erasure request.

Live Wall safety: participants can report posts or comments and block contributors from their own view; hosts can ban contributors from their event and require approval before guest posts appear. RosenVows administrators can review reports, remove content and restrict contributors across Live Walls. Basic text checks can hold some content for review; they do not automatically assess every image, video or recording.

For these safety features, we store a random browser identifier (rv_livewall_guest_key) or use the signed-in account ID, derive internal identifiers and a separate contributor identifier for each wall, and keep block settings, report reasons, optional details, a text excerpt and moderation decisions. These are used for abuse prevention and moderation, not advertising. Reports and internal identity records are accessible to authorised RosenVows administrators, not other participants. A host can see their event's posts and event bans, but not private reports or internal account identifiers.

Temporary Live Wall media expires from the wall after 10 minutes. Safety records are kept separately to review reports and enforce blocks; they do not automatically disappear with the post. Browser-based blocks depend on that browser identifier and cannot identify the same anonymous person after a browser or device change. Contact hello@rosenvows.com to request review of a report, restriction or safety record.

Verified customers may attach photos and one short video to a written review — for example photos of their printed invitations after delivery. Attaching media is always optional; a review can be submitted without it.

Publication requires two separate things, and both must be present: the reviewer must give explicit consent for their media to be displayed publicly (this consent is asked separately from the consent to publish the written review and is never implied by it), and each individual file must be approved by RosenVows moderation. Until both are satisfied, uploaded media is not shown publicly. Media without media consent is not accepted at all.

Review media is stored separately from Live Wall media. It is not subject to the Live Wall 3-month deletion; it is retained for as long as the review exists and can be deleted at any time by the reviewer or by RosenVows, independently of the written review. A reviewer can ask us at any time to remove their media or withdraw their consent to its publication.

For RosenVows product purchases we store the product purchased, transaction and order status, amount, applied discounts, refunds, purchase mode, referral attribution, commission records, reseller pricing records and payout history.

Separately, a professional Planner can create invoices and installment schedules for its own wedding-planning services. Those records can contain client identity/contact information, line items, taxes, discounts, issue and due dates, received amounts, installment labels/dates/statuses, bank-transfer instructions and external payment URLs supplied by the Planner. These planner-service invoices are between the Planner and its client; an external payment URL is not a RosenVows checkout and RosenVows does not become merchant of record for the Planner's service fees merely by recording that link or status.

Payment card details for RosenVows purchases are entered on and handled by our payment provider. RosenVows never stores full card numbers.

For approved wedding planner partners, RosenVows processes the data needed to administer the partner program: referral attribution, partner status, commission calculations and eligibility, reversals for refunded orders, and payout administration. Financial and accounting records may be retained longer than ordinary wedding content where bookkeeping and legal obligations require it.

If you order printed invitation cards, fulfilling the order requires sharing the necessary information with an authorized printing and fulfilment provider: the print-ready design, quantity, delivery recipient, delivery address and relevant order data. This information is used solely for producing and delivering your order. Our current printing and fulfilment providers are listed in the Recipients & Processors section below.

Paid physical orders are not sent to production automatically. Each paid physical order first enters RosenVows' internal order management, where it is reviewed and must be explicitly approved by RosenVows before it is submitted to the external printing provider. Only after that submission does production begin.

Optional tracking is off until you make a current choice. Rejecting optional tracking does not prevent you from browsing, personalising, purchasing, or using your wedding planner.

Analytics consent enables Google Analytics and RosenVows usage measurements, including Base44's analytics service. These measure visits, page and feature usage, approximate visit duration and the purchase journey. Data may include a browser-generated identifier, timestamps, page paths, referring site, device/browser information, language, timezone and, for signed-in visits, the account identifier.

With analytics consent, IP-based lookup services can provide approximate country, region, city and map coordinates for visitor statistics and location suggestions. This is an estimate from the network connection, not GPS access or your precise physical position.

Marketing consent separately enables Google Ads conversion measurement and automatic campaign/referral attribution. This can use ad-click identifiers, campaign parameters, the referring partner, product, purchase value, currency and transaction references. Guest, RSVP, allergy and payment-card details are not included in advertising events.

OpenAI advertising tracking is disabled. The current marketing choice does not authorise a future OpenAI pixel; a new disclosure and consent choice would be required.

Necessary cookies and browser storage support authentication, security, saved consent, language, shopping selections and drafts you ask us to keep. A referral code you apply yourself is retained for that tab's checkout session even if you reject optional tracking.

Your category choice is stored for up to 180 days. Older choices made under a different tracking disclosure are not silently upgraded. You can change or withdraw consent through Cookie Settings in the website footer.

Analytics identifiers include base44_analytics_session_id, rosenvows-presence-session and rosenvows-consumer-visit-v2. A measured visit expires after 30 minutes of inactivity; longer-lived browser identifiers are removed when analytics is rejected or the consent is no longer valid. Google Analytics cookies are configured for up to 180 days.

With marketing consent, rv_referral_attribution and campaign first/last-touch records are retained for up to 90 days. Google Ads can also use its own advertising cookies. Rejecting a category stops its trackers and clears the known optional first-party cookies/storage for that category. This does not erase previously received server records or cookies on a third party's own domain.

The website's font files are hosted by RosenVows. Hosting, authentication, security, media delivery, payments and services you explicitly request still involve network requests and technical logs; rejecting optional tracking does not mean that no data is processed.

The Live Wall identifier rv_livewall_guest_key supports the reporting and blocking features you use. It is necessary functional/security storage rather than an analytics or advertising identifier; rejecting optional tracking does not disable those safety controls.

We use the following service providers to operate RosenVows. We only share the data each provider needs for its purpose, and we do not sell personal data.

• Base44 — Application hosting, database, file storage, authentication and requested AI-assisted features; optional Base44 usage analytics only with analytics consent. Processing location: EU / Israel / United States and locations in Base44's published subprocessor list. Safeguard: Base44 DPA (https://base44.com/dpa): applicable adequacy decisions, Data Privacy Framework coverage or standard contractual clauses with Swiss adaptations.
• Base44 Payments — Payment processing at checkout. Payment card credentials are entered on and handled by the payment provider; RosenVows never stores full card numbers.. Processing location: EU / United States. Safeguard: Applicable payment-provider privacy and data-transfer terms; PCI DSS is a security standard, not a transfer mechanism.
• Expresta — Printing and fulfilment of physical invitation card orders (print-ready design, quantity, delivery recipient and address). Processing location: European Union. Safeguard: EU adequacy recognized by the Swiss FDPIC.
• Resend — Transactional emails, including orders, accounts, collaboration, retention reminders and withdrawal receipts. Processing location: United States. Safeguard: Resend DPA (https://resend.com/legal/dpa), including its applicable contractual transfer provisions.
• Google Analytics — Website usage analytics — loaded only after cookie consent. Processing location: EU / United States. Safeguard: Google's applicable data-processing and international-transfer terms; analytics consent is required separately.
• Google Ads — Advertising / marketing conversion measurement — loaded only after cookie consent. This is an advertising technology, not analytics.. Processing location: EU / United States. Safeguard: Google's applicable data-processing and international-transfer terms; marketing consent is required separately.
• Google Contacts / Google People API — Optional user-authorized, read-only contact import: contact names, email addresses and phone numbers are read only when a signed-in user chooses to connect Google Contacts and are used only to let that user select people for their wedding guest list. Processing location: EU / United States. Safeguard: Google's applicable data-processing and transfer terms and Google API Services User Data Policy Limited Use requirements; user OAuth permission is required separately.
• Google Workspace APIs — Optional planner-authorized Gmail and Calendar access: send business emails from the planner's own Gmail account and create calendar events with Google Meet links when the planner explicitly requests those actions. Processing location: EU / United States. Safeguard: Google's applicable data-processing and transfer terms and Google API Services User Data Policy Limited Use requirements; planner OAuth permission is required separately.
• Microsoft 365 / Microsoft Graph — Optional planner-authorized Outlook and Calendar access: send business emails from the planner's own Microsoft mailbox and create calendar events with Microsoft Teams links when the planner explicitly requests those actions. Processing location: EU / United States. Safeguard: Microsoft's applicable data-protection and international-transfer terms; planner OAuth permission is required separately.
• Google Places / Google Maps — Vendor directory search and venue maps: search terms and approximate location are sent to Google to return public business listings and maps. Processing location: EU / United States. Safeguard: Google's data-processing terms.
• ipwho.is / IPWHOIS.io — IP-based approximate country, region, city and coordinates for consented visitor analytics/location suggestions. Processing location: International infrastructure; provider does not list every destination in its privacy policy. Safeguard: Published privacy terms: https://ipwhois.io/privacy. No specific contractual transfer mechanism is asserted here..
• ipapi.co / Kloudend — Fallback IP-based approximate location for consented visitor analytics/location suggestions. Processing location: United States / international infrastructure. Safeguard: Published privacy terms: https://ipapi.co/privacy/. No specific contractual transfer mechanism is asserted here..

Providers may process information outside Switzerland, including the EU, Israel and the United States, and on international delivery networks. The provider list identifies the recipient and its published processing or transfer terms.

Base44's published DPA describes adequacy decisions, applicable Data Privacy Framework coverage and standard contractual clauses with Swiss adaptations. Resend's published DPA describes its contractual transfer arrangements. For other recipients, the relevant provider terms and the destination determine which safeguards apply.

A cookie choice, OAuth permission or PCI DSS payment-security certification is not by itself an international-transfer safeguard. You can contact hello@rosenvows.com for information about the arrangements applicable to your data and copies or references for relevant safeguards.

We keep different categories of data for different periods:

• Account data — kept while your account is active; you can request deletion of your account at any time.
• Active wedding workspace data (invitations, tasks, budget, seating, vendors) — kept while the related account and wedding remain active.
• Guest and RSVP information — kept with the invitation it belongs to; the couple can export or delete it from their dashboard.
• Questionnaire responses — kept with the wedding they belong to.
• Documents and notes — kept until deleted by their owner or until the workspace is deleted.
• Live Wall posts — scheduled for removal from the application three months after the wedding date, with retry on failure. Hosted files and backups follow separate storage-deletion processes. See section 10.
• Live Wall posts — scheduled for removal from the application three months after the wedding date, with retry on failure. Hosted files and backups follow separate storage-deletion processes. See section 10.
• CRM leads, consultation bookings, communication-history records, planner email templates, workflow templates and automation configuration/run records — kept by the planner business while needed for its professional client relationship or business workflow, until deleted or the business account is closed, subject to lawful retention requirements.
• Venue floor plans and other wedding operational records — kept with the wedding workspace until deleted by an authorized user or until the relevant workspace/account is deleted, subject to records that must lawfully be retained.
• Planner proposals, contracts and electronic-signature evidence — kept with the Planner's client records while needed for the professional relationship and may be retained after ordinary client deletion where reasonably necessary to establish, exercise or defend legal claims or where a legal retention obligation applies. When no such purpose remains, the data is deleted or anonymized in accordance with our retention processes.
• Planner-service invoices, installment records, expenses, reporting inputs, transaction and order data, commissions, payouts and accounting records — retained for as long as the Planner's business workflow and applicable bookkeeping or legal obligations require, even after an account is closed where retention is legally necessary.
• Deleted accounts — deletion removes the account's personal content; financial records that must legally be retained are kept for the required period.

Browser consent and attribution lifetimes are described in section 17. Server-side analytics records are separate from browser identifiers: withdrawing consent stops future collection but does not delete records already received. Contact us to exercise access or erasure rights. Where no fixed retention period is specified, records are kept only while needed for the stated purpose or an applicable legal obligation.

Under Swiss data protection law (nDSG) and, where it applies, the GDPR, you have the right to access your personal data, have it corrected, request deletion where applicable, request restriction of or object to certain processing, withdraw consent you have given, receive a copy of data you provided (portability) where applicable, and lodge a complaint with a competent supervisory authority.

To exercise any of these rights, contact hello@rosenvows.com. If a guest's data was entered by a couple or planner, we may coordinate with the responsible couple or planner to fulfil the request.

Data is encrypted in transit and at rest. Access to wedding data is controlled by ownership, collaboration and permission rules; support access by authorized RosenVows personnel is restricted and used only to assist you. No online service can guarantee absolute security, but we apply appropriate technical and organisational measures to protect your information.

We maintain processes for handling personal-data breaches, including assessing the incident, mitigating it, and notifying affected persons and authorities where legally required.

RosenVows is not designed as a service for children. Minors may appear as wedding guests on a guest list; in that case their information is minimized and processed only for wedding administration (for example attendance and seating).

RosenVows does not perform automated decision-making or profiling that produces legal or similarly significant effects for you. Optional AI-assisted features (such as text suggestions) only generate content you review and choose to use.

This also applies to the AI-assisted organization of allergy information described in section 6: it only sorts and restates what a guest wrote so the information can be acted on operationally. It makes no decision about the guest, performs no medical assessment, and never replaces the guest's own wording, which stays authoritative and visible.

For privacy-related enquiries, contact hello@rosenvows.com or write to RosenVows, c/o Mohamed El Assri, Bahnhofstrasse 14, 3904 Naters, Switzerland.

When a professional wedding planner uses RosenVows to manage a prospective or existing client relationship, the platform may process proposal and contract information including the client's name and email address, services and line items, fees, discounts, tax fields, validity dates, proposal terms, contract text and clauses, document version and status, and timestamps showing when a document was sent, viewed, accepted, declined or signed.

For native electronic contract signing, RosenVows records evidence linked to the exact contract version. This can include the signer's typed name, email address, signing timestamp, the cryptographic hash of the contract, the electronic-consent version, device/browser user-agent information and, where available, a one-way hash derived from the connection IP address. RosenVows does not store the raw IP address in the signature-evidence record created by this feature.

This information is used to deliver the proposal/contract workflow, maintain document integrity and version history, provide audit evidence to the Planner and client, prevent misuse, investigate security issues and, where necessary, establish, exercise or defend legal claims. Planner-authored proposal and contract content is processed on the Planner's instructions where RosenVows acts as processor; RosenVows may act as controller for its own security, fraud-prevention, compliance and legal-record obligations as described in this Policy and the Planner DPA.

RosenVows is the platform provider and is not a party to the commercial planning-services contract between a Planner and their client. The platform's native signature evidence is not used for advertising, profiling or automated decision-making.

Where the GDPR applies, account, invitation, planning and purchase operations rely on contractual necessity (Article 6(1)(b)); accounting and mandatory consumer-rights records on legal obligations (Article 6(1)(c)); and proportionate security, fraud prevention and defence of claims on legitimate interests (Article 6(1)(f)). Optional analytics/marketing rely on consent (Article 6(1)(a)). Voluntary allergy/health processing additionally requires explicit consent (Article 9(2)(a)). Where RosenVows processes a planner's client data on instructions, the planner is responsible for its legal basis.

The public withdrawal form at /withdraw-contract collects your name, confirmation email, order reference or description, optional part-of-order details, chosen language, submission identifier and a server-stamped receipt time. We store your declaration, delivery status and receipt to handle the request, meet consumer obligations and document its timely receipt. Resend sends the receipt to you and the operator. Records are retained while the request is handled and thereafter where needed for applicable accounting obligations or the establishment, exercise or defence of related legal claims.

Consent withdrawal stops future optional tracking. It does not invalidate earlier lawful processing or automatically erase data already received. You can separately request access or deletion using the contact details in this policy.