01Who this policy covers
This policy covers Marhaba Wedding visitors, account holders and guests who view invitations, submit responses or add photos to a shared album. Marhaba provides digital invitations for weddings, surprises and class reunions, shared through a link. Direct data enquiries to the Marhaba support contact at the end of this page.
02Account and order details
When you register with email and password, we store your name, email address, account identifier and the date and version of your agreement to the documents. Supabase Auth handles passwords, email verification and password recovery. If a Google option is available on the sign-in page and you select it, we use the email, name and basic profile details Google provides to create or access your account.
Your order number, design, amount, creation and approval times, status and administrator notes are linked to your account. You send payment receipts and your order number to the administrator contact on the order page. Telegram is used for support, receipt submission and link sharing; messages and their contents may also be stored by the relevant messaging service.
03Invitation content
Depending on the design, we store names, family or class details, host and guest names, invitation or letter text, event dates and times, venues, addresses, map links, schedules, dress guidance, contacts, photos and audio. Surprise invitations may also include proposed activities and travel details. An optional gift section may display a card number and holder name.
Marhaba payment details are separate from the gift-card details shown to guests. The site does not request a PIN, CVC/CVV or bank verification codes. Do not include them in invitations or support messages.
04What a link makes accessible
After order approval, anyone with the link can open the invitation without an account or password. Treat saved invitation text, contacts, photos and gift details as accessible through the link. Turning a section off hides it on the page but does not make the saved content private. Remove details that should not be accessible from the fields and save your changes, or contact support.
Uploaded photos and audio are kept in public file storage. Anyone with a direct file URL may access it even before order approval. Removing a file from an invitation does not automatically delete its stored copy. Do not upload identity documents, payment receipts or confidential files here.
Guests can forward links, take screenshots or save files. Editing an invitation cannot recall copies already shared. Names, the event date and venue can also appear in messenger link previews.
05Guest responses
Where RSVP is enabled, we store the guest's name, attendance response, party size and submission time for event planning. The invitation owner and authorized administrators can view these responses; they are not published as a guest list on the invitation. Guests do not need an account to respond.
For surprise invitations, we store the selected option and its submission time. The latest choice is visible to the owner and may also appear to other people opening the link. This is not an identity-verified poll: someone else with the same link can also change the choice.
07Purposes and service providers
We use data to provide and recover account access, store invitations and files, review orders and payments, display invitations, manage guest responses and shared albums, prevent abuse and handle support requests. Authorized administrators may access account, order and invitation details needed to provide the service and resolve problems.
We use Supabase for accounts, database and file storage, together with website hosting and verification email delivery services. Choosing Google sign-in, opening an external map or social link, and messaging or sharing through Telegram/WhatsApp may disclose data to the relevant external service. Those services have their own privacy policies and may operate infrastructure in other countries.
08Cookies and browser storage
Cookies and browser storage support sessions, language preferences, email verification and password recovery progress, the document acknowledgement passed through Google sign-in, repeat guest responses and shared album upload limits. Passwords and email verification codes are not saved in browser storage. Request limits use a protected identifier derived from an IP address; servers and service providers may keep technical request and error logs.
Clearing cookies or browser storage may sign you out or reset language and verification progress. It does not automatically delete saved orders.
09Retention and data requests
The event date or editing deadline does not automatically delete an account, invitation, guest responses or album. These may be kept to provide the service, with relevant order and payment records retained as needed to resolve disputes and meet legal obligations. There is no single automatic deletion period for all data. Removing a file from a page does not delete its stored copy; contact support about complete removal.
Contact support to request access, correction, deletion or withdrawal of consent. For an account request, include the email address or order number; as a guest, include the invitation link and identify the response or photo concerned. We may verify that the data belongs to you before acting. Legal retention requirements and other people's rights may apply; Marhaba cannot control copies saved by others or messages held by messaging services.
10Policy updates
The version date appears at the top of this page. We update the policy when the service or its data practices change. Where fresh consent is needed, it will be requested separately. Use the support link below for questions or requests.
Questions and requests
Contact Marhaba Wedding support. Include the order number for order enquiries; do not send passwords or verification codes.
@marhaba_admin