Privacy Policy

This Privacy Policy explains how Joshua Rodriguez as Galashare handles personal information when you visit https://galashare.com or use the GalaShare service to collect and keep photos, videos and notes from an event. In this policy, "we" and "us" mean Joshua Rodriguez as Galashare, operating as GalaShare and based in the United States, and "you" means anyone who visits the site, signs in as a host, or sends something to a host's event as a guest. We decide why and how the personal information described here is handled.

It covers the website and the service only. It does not cover other sites you reach through a link, or copies of your content that other people keep outside GalaShare. Our Terms of Service set out the rest of the rules for using the service. By using the website or the service you confirm that you have read this policy. Where the law requires separate consent for something, we ask for it at that point, and you can withdraw it by emailing compliance@galashare.com.

Questions and requests about your information go to our privacy team at compliance@galashare.com.

Two kinds of users

Hosts are the people who sign in, create an event, and share its link or QR code. Guests are the people who open that link to add photos, videos, a name or a guestbook note. Guests do not create an account. The host decides who gets the link and what to do with what arrives, and we store and deliver the content for the host.

What we collect

From hosts

• Email address. We use it to send you a sign-in link. There is no password. Our sign-in provider (see "Who we share information with") also keeps sign-in records for your account, including the IP address and the browser or device details your connection reports.
• Event details. The names you enter for the couple, the event date, a welcome message, a cover photo, the visual theme, and your settings (whether uploads are open, whether guests can see a shared gallery, whether the guestbook is on, and whether you approve uploads first). The couple's names are also turned into part of the event's web address. The names, date, welcome message and cover photo are shown on the guest page to anyone who has the guest link.

From guests

• Photos and videos you upload, plus the file name, file type, size, and, where your browser reports them, the dimensions or running time.
• A name, if you choose to type one. It is optional.
• Guestbook notes you write.
• A random identifier. Your browser makes a long random code the first time you open an event page. We do not keep the code itself. We keep only a one-way scrambled version of it, which lets us tie your uploads and notes together and let you remove your own uploads later from that same browser.

Payments

When a host upgrades an event, the card or bank details are typed into a page run by Stripe. We never receive full card numbers. We keep an order record for each purchase (amount, currency, status, the dates, and the Stripe reference numbers) and we keep the event notifications Stripe sends us about the payment. Those notifications can include the buyer's name, email address, billing details, and the card brand and last four digits, depending on what Stripe collected. We send Stripe the host's account email, a payment description that contains the couple's names (so they appear on Stripe's side too), and internal reference numbers for the event and the account. See our Purchase Terms and Refund Policy for how purchases and refunds work.

Contact form

If you write to us through the contact form, we receive your name, email address, the topic you pick and your message. We store these so we can read and answer them; we do not promise that a copy is also sent to an inbox. The form also uses the short-lived abuse-protection record described under "Technical information", which is not saved with your message. If you email us directly, we keep what you send for as long as we need to deal with your request.

Technical information

• Abuse protection. To stop automated misuse, we limit how often certain actions can happen (starting uploads, adding guestbook notes or names, submitting the contact form, and sending invalid payment notifications). To do that we process your IP address and, for guests, the random browser identifier described above. The counters we keep contain only a salted, one-way hash of your IP address or of that identifier, not the address or the identifier itself, and they are deleted within 3 days.
• Our hosting network. GalaShare runs on Cloudflare. Cloudflare processes each request to the site, including the IP address and browser details, and keeps its own logs under its own policies.
• Server logs. Our site's Cloudflare Workers logs hold request and error logs (the page address, the response status and error messages). They are kept for up to 7 days, for troubleshooting.
• Bot check. The contact page runs Cloudflare Turnstile, which looks at signals from your browser to tell people from bots. We pass your IP address to Cloudflare when we verify the result.

Administrative records

When we act on an event, for example extending its dates or granting a plan manually after a payment problem, we log what was done and which team member did it. That log is used to answer support questions and to keep our own actions accountable.

Information inside uploaded files

We store each original photo or video exactly as it arrived, without editing it. That means any data your phone or camera embedded in the file, such as the date and time, the device model and the GPS location where it was taken, stays in the original. The host can see it, and anyone the host sends an original to can see it too. The small previews and thumbnails that the uploader's browser creates for viewing do not carry that data over.

If a file contains something you would rather not hand over, take it out before you upload. Pictures of other people can be personal, and sometimes sensitive, so check that the people in them are comfortable with the pictures being shared. We do not look for or sort files by what they show.

How we use information

We use personal information to:

• run the website and the service, and keep each event working through its upload and download windows;
• let hosts sign in, by sending a sign-in link to their email address;
• take payments, apply refunds, and keep accurate purchase records;
• store, preview, deliver and let hosts download the photos, videos and notes sent to their event;
• answer messages and help with problems;
• protect the service, our users and our payment flow from abuse, fraud and attacks, and enforce our terms; and
• meet our legal obligations and respond to lawful requests.

We do not:

• run analytics, advertising or tracking tools on the site;
• sell personal information, or share it for advertising across other sites;
• use uploaded photos, videos or notes to train artificial intelligence systems; or
• use anyone's content to promote GalaShare unless that person gives separate permission.

Today the only emails the service sends are sign-in links, plus our replies when you write to us. We may send reminder emails about upload and download deadlines when that becomes available, but do not rely on them. Keep track of your own dates and download your files in good time.

If the law of your country requires a legal basis for processing, ours are: providing the service you asked for (a contract), our legitimate interest in keeping the service secure and free of abuse, our legal obligations such as tax records, and your consent in the few cases where we ask for it. Where you gave consent, you can withdraw it at any time by emailing compliance@galashare.com.

Who can see what

• The host sees everything sent to their event: every photo, video and note, including items that are hidden or waiting for approval, with the guest names attached.
• A guest sees their own uploads from the browser they used, including ones still waiting for the host's approval or hidden by the host.
• Other guests see nothing from an event unless the host turns on the shared gallery. If it is on, anyone with the guest link can view the uploads the host has left visible, together with the names of the people who sent them and the original file names. Hidden and unapproved items are not shown there. Guestbook notes are never shown to guests; only the host reads them.
• The live slideshow link works for anyone who has it. There is no sign-in, and the host cannot switch the link off or replace it. It shows the most recent visible uploads with the guest names and original file names, and it keeps working until the event's files are deleted.
• Behind the scenes, the viewing pages receive links to the original files so videos can play. Someone with a slideshow or gallery link who knows how to inspect browser traffic could therefore fetch the original files, along with any metadata inside them.
• Our team can see account emails, event names and settings, order records, payment notifications and contact messages in our administration tools. Those tools do not display the photos, videos or guestbook notes. People with direct database or storage access can technically reach more, and we limit that access to what the work requires.

Whoever receives a guest link, slideshow link or QR code can pass it on, photograph it or post it, and we cannot tell who ends up with one. Once someone downloads a file, a copy exists that we cannot reach or delete.

Who we share information with

We use a small number of companies to run the service. Each handles information only for the purpose described and under its own privacy policy.

• Cloudflare runs the website on its global network, stores uploaded media in its R2 storage (set to the U.S. jurisdiction), and provides the Turnstile bot check on our contact page. Cloudflare privacy policy.
• Supabase hosts our database and the sign-in system, in Amazon Web Services' us-east-1 region (Northern Virginia, USA). Supabase privacy policy.
• Purelymail is the mail service that delivers sign-in emails for Supabase, so it handles the recipient address and the message. Purelymail privacy policy.
• Stripe processes payments through its hosted checkout page. Stripe privacy policy.

We do not use a separate analytics, advertising or error-monitoring company. The site's fonts are served from our own pages, so loading them does not send your browser to Google or any other font service.

We may also disclose information when the law requires it, when we believe it is needed to protect people from harm or to defend our legal rights, or in a sale, merger or other transfer of the business, in which case the new owner would have to honor this policy for the information it receives.

Where information is stored

Uploaded media is stored in the United States. The database and sign-in records are kept in Northern Virginia, USA. Our website is delivered by Cloudflare's network, so a request from your device is answered by a nearby data center and may pass through other countries on the way. If you use GalaShare from outside the United States, your information is sent to and handled in the United States, where privacy laws may differ from those where you live. Where the law requires a safeguard for that transfer, we rely on measures such as our providers' standard contractual clauses or their Data Privacy Framework certifications.

How long we keep information

Deleting media from GalaShare does not remove copies that a host, guest or anyone else has already downloaded. Deleted data may also sit in provider backups for a limited period before it is overwritten.

Hosts cannot yet close their own account from the dashboard. Email compliance@galashare.com and we will delete the account, its events and the media in them, apart from the records we must keep.

Cookies and browser storage

• Hosts. When you sign in, our site sets cookies in your browser (managed by Supabase's sign-in library) to keep you signed in. They can last up to 400 days unless you sign out or clear them.
• Guests. We set no cookies for guests. The event page uses your browser's local storage to remember the random identifier and the name you typed. Clearing your browser data erases both, and you then lose the ability to remove your earlier uploads from that browser.
• Downloads. To build a ZIP of an event's files, the host's browser installs a small service worker that streams the files to the host's device.
• Third parties. Cloudflare Turnstile on the contact page and Stripe's checkout page may set their own cookies or storage.

There are no analytics or advertising cookies on GalaShare. We do not track you across other sites, so Do Not Track and Global Privacy Control signals do not change anything.

Your choices and rights

Depending on where you live, you may have the right to:

• ask what personal information we hold about you and get a copy;
• have wrong information corrected;
• have your information deleted;
• receive your information in a portable format;
• object to, or ask us to limit, certain uses; and
• withdraw consent you gave earlier.

Europe and the United Kingdom. These rights come from the GDPR and UK GDPR. You may also complain to your local data protection authority.

United States. Residents of some states have similar rights to know, correct, delete and obtain a copy of their information, and to refuse its sale or use for targeted advertising. We do neither of those things. If we turn down a request, you can reply and ask us to take another look, and we will explain our decision.

Mexico. You may exercise your rights of access, rectification, cancellation and opposition (ARCO). To do so, email compliance@galashare.com with your name, the email address you used with us, what you are asking for, and anything that helps us find your data. We may ask you to confirm your identity first.

To use any of these rights, email compliance@galashare.com and tell us what you want. For guest content, include the event's web address and describe the photo, video or note. We may ask you to confirm who you are before we act, and we reply within the time the law gives us. A host controls the content in their own event, so we may refer a request about it to the host, or ask you to speak to them first. We will not charge you for making a request, and we will not treat you worse for making one.

Children

GalaShare is not aimed at children under 16, and we do not knowingly collect personal information from them. A guest under 16 may upload only with a parent's or guardian's permission. Guests do not give us their age, so a host who invites children should make sure a parent or guardian agrees to their pictures and notes being shared.

If you are a parent or guardian and want a photo, video or note of your child taken down, tell the host, who can delete it right away, or email compliance@galashare.com with the event's web address and a description of the item, and we will remove it. If you believe a child under 16 has given us information about themselves, contact us and we will delete it.

Security

Connections to the site are encrypted. Media is not placed at public addresses; it is reached through links that expire (an hour for uploads, six hours for viewing and downloads), and our database limits each host to their own events. Our providers also encrypt stored data. Anyone who holds an unexpired link can use it, so treat links like keys. No system is perfectly secure. If a breach affects your information, we will notify you and the authorities as the law requires.

Changes to this policy

This policy can change whenever the service itself, or the law around it, changes. The "Last updated" date at the bottom of this page shows the latest revision. For changes that matter, we will make a visible announcement on the site before they take effect.

Contact

Privacy and data questions: compliance@galashare.com. Purchases and account help: contact@galashare.com. Anything else: hi@galashare.com. You can also use the contact form.

Last updated: October 23, 2026