Help.

Sign in → Dashboard → Create event. Pick a date, an event type (wedding / memorial / corporate / other), and a plan. You'll get a QR code and a short link you can put on tables, invitations, or send by message.

From your event dashboard, go to Guests → Add. Paste a list of emails or import a CSV. Guests get an email with a personal QR + RSVP link. They never need to create an account.

Settings → Cloud mirror → connect Google Drive, Dropbox, or OneDrive. Every approved upload gets copied to your own cloud, typically within minutes. The mirror status page shows progress, failures, and retries.

That depends on the event and plan. For a standard Free event, Galeira keeps hosted originals for about 30 days after the first upload, or 90 days when a cloud is connected; memorial and other sensitive events receive a longer 180-day or 365-day window. Event Duo and Account events include a one-year hosted gallery from the event date, followed by a warning and grace process before Galeira releases its hosted copy. Files already mirrored to your connected cloud remain subject to that provider's storage and deletion rules, whether or not Galeira is available.

Open the event QR screen and use Test guest link to verify the upload page. Send one test photo, then check the event readiness card and storage status. A test confirms the route works; it does not count as a real guest contribution.

Refresh the event seating page and check that you have host, partner, or co-host access. If the problem continues, contact support with the event name and approximate time; do not share guest details.

Scan the host's QR code. Tap the upload button. Pick photos from your camera roll or take new ones. No app to install, no account to create.

Yes. On the gallery page, find your upload (it shows your guest name) and tap the menu → Delete. If you've left the page, you can ask the host to remove it.

Only the name you typed when uploading. If you skipped that, the upload shows as 'Guest'. Galeira doesn't read or store phone numbers, emails, or location from your upload. One thing to know: the original photo file can itself contain camera metadata, including GPS, and the host can download the originals — so that metadata travels with the file. The public gallery shows a metadata-stripped copy.

Every plan is a one-time purchase — there is no subscription to downgrade or cancel. Dashboard → Event → Upgrade applies an Event Duo credit or an account plan immediately after Stripe checkout; a plan simply runs out at the end of its term.

Paid plans include a setup guarantee: if your QR upload page or connected cloud backup isn't working before your event, email support@galeira.com from your host account and we either fix it fast or refund the plan within 24 hours. After an event has successfully collected uploads, refunds are reviewed case by case.

Open the event billing page and check the receipt status. Do not retry a completed charge repeatedly. If the status is still wrong, contact support with the receipt reference and account email, without sharing card details.

Check the event plan and the account that owns the event. Some professional features require an eligible paid plan or an approved add-on. Refresh the plan status before retrying, and contact support with the feature name if access still looks wrong.

Phone cameras need to focus on the QR for a couple of seconds. If your QR is on a printed sheet, make sure it's at least 5 cm × 5 cm and not laminated with a glossy finish (which causes glare). If problems persist, ask guests to type the short link in their browser instead.

If you have auto-moderation enabled (default), uploads pass through Amazon Rekognition for content review. This usually takes under 30 seconds. If stuck longer than 5 minutes, check Settings → Moderation → toggle off and on.

Clear your browser cookies for galeira.com and sign in again. If it keeps happening, contact support@galeira.com with your account email and rough time of day.

Check that the invitation link is current and that all required questions are answered. Try again once with a stable connection. If it still fails, contact support with the event link but never include a guest token in the message.

Open the event export page and retry the failed job once. Keep the page open until the job reports success or a clear error. If it fails again, contact support with the event and job reference, never with a signed storage URL.

Check the event moderation queue and wait for the status to update before retrying. If it remains stuck beyond the normal processing window, contact support with the event and upload reference, never with the original file URL.

Use the privacy or support request path from the account that owns the event. Include only the event reference and the request type. Do not send passwords, guest tokens, signed URLs, or exported files by email.

Ask the event owner to confirm your role and the specific permission you need. Editors and viewers cannot change owner-only settings. Never work around a permission message by sharing someone else’s session.

The event plan and connected storage determine the retention window. Check the event storage status for the current warning and export important files before the displayed deadline. Files already copied to your own cloud follow that provider’s rules.

Use the Galeira CSV template, keep the header row, and remove duplicate or malformed email addresses. Preview the rows before saving. If the import is rejected again, contact support with the import reference, never with guest data pasted into a message.

Confirm that you have access to the proofing project and that its selection limit has not been reached. Retry once with a stable connection. If the project is locked or expired, ask the project owner to reopen it rather than sharing a private link.

Confirm that the CNAME and ownership TXT record match the values shown in Galeira and allow DNS time to propagate. Use a subdomain instead of an apex A record unless your DNS provider supports the required alias. Do not share ownership tokens in support requests.

Check the event and account notification preferences, browser or device permission, and quiet hours. Safety alerts may remain immediate even when digests are paused. If delivery still fails, contact support with the notification reference and never include a session token.