Evans & Gifty

Privacy policy

Givans 2026 / Evans & Gifty · Effective date: October 7, 2026

This policy explains how Evans & Gifty’s wedding website uses information provided by invited guests and the people managing the wedding.

Information used by the site

Original files can contain embedded information, such as the date a photo was taken, camera details or location. Because originals are preserved, that information can remain in an original download.

How information is used

Information is used to manage invitations and RSVPs, coordinate wedding arrangements, operate the gallery, personalize photo collections, protect access and keep the couple’s wedding archive.

The couple and authorized wedding managers can access information through the site’s management tools. Uploads are intended for the wedding gallery and archive, rather than advertising or AI model training.

Who can see gallery files

Guest gallery access requires a confirmed RSVP and sign-in. Shared photos and videos can be viewed by other invited guests who have that access. Uploader names, captions and upload dates may appear with a file.

An invitation tag helps you find a file in your own collection; it does not make that file private to your invitation. Guests are offered original downloads only for files explicitly tagged to their invitation. Uploading a file yourself does not automatically give it a tag. The couple and authorized gallery managers can download gallery originals.

Removing a tag removes that guest’s original-download permission. Hiding a file removes it from guest browsing, but does not delete it from the private archive. Copies already downloaded or captured by someone else cannot be recalled through the site.

Where information is stored

Supabase provides authentication and stores invitation, RSVP and gallery records. Cloudflare hosts the gallery service and stores separate preview images in a private R2 bucket.

Original photos and videos are stored in one private Google Drive folder owned by the site owner. The site uploads original bytes without recompressing photos or transcoding videos. Separate, smaller previews are created for browsing; they do not replace the original files.

These providers process information to supply their services under their own terms and privacy policies. Service infrastructure can process information outside the country where a guest lives.

The site also loads some fonts from Google Fonts. Browser requests for those fonts are handled by Google.

Cloudflare Web Analytics measures page visits and site performance.

The owner’s archive connection

Only the site owner connects Google Drive. Guests do not need to connect a Google account for gallery uploads. The app requests permission to manage files created or selected for this app, rather than access to the owner’s entire Drive. The gallery uses the single configured archive folder.

The connection is used to create and retrieve wedding originals and verify uploads. Connection credentials are kept in private server configuration. The owner can revoke the app’s permission through their Google account. Revocation stops the archive connection; it does not automatically delete files already stored.

Cookies and browser storage

The site uses browser storage to keep session information, save unfinished RSVP answers and remember preferences. Clearing browser data can sign you out or remove unsent drafts; it does not delete information already submitted to the site.

Keeping information and requesting changes

Invitation and RSVP information supports wedding arrangements. Original uploads are retained as part of the couple’s wedding archive. There is currently no automatic deletion schedule for that archive.

Contact privacy@eng-26.com to request a correction, access to your information, removal of a gallery item or deletion of an archived upload. The couple will review the request, confirm identity where needed and explain what action can be taken. Removing a gallery item and deleting its archived original are separate actions.

Changes to this policy

If the site’s data practices change, this page will be updated with a new effective date.