Privacy

Private originals, reviewed gallery visibility.

This policy summarizes the production privacy posture for launch. It should be reviewed by counsel before paid public availability.

Contact support

What we collect

The Aisle collects event details from couples, account details for authenticated couple users, guest names and optional guest emails, uploaded photo files, upload metadata needed for security and limits, billing records from Stripe, and operational logs needed to run the service.

How photos are handled

Original uploads are stored in private object storage and are not placed in a public bucket. The app creates thumbnails, enhanced variants, and exports as separate files. Originals are not overwritten by AI output or thumbnails.

Gallery visibility

Guest uploads are private by default. Public gallery pages only show assets that pass the event's review workflow and are approved for gallery visibility. Couples can reject uploads or enhanced variants before guests can see them.

AI processing

When a couple requests enhancement, the service reads the private original, sends it to the configured image provider, stores the returned output separately, and records the model name, prompt version, and job status. Enhancement is for lighting, color, clarity, and crop polish, not identity or body alteration.

Sharing and subprocessors

The Aisle uses Supabase for authentication and database records, Cloudflare R2 for private object storage, Stripe for payments, OpenAI for requested image enhancement, Vercel for app hosting, and optional Sentry, PostHog, and Resend integrations when configured.

Deletion and retention

Package retention windows are visible to couples. Couples can request event deletion from the dashboard; deletion work runs in a background worker that removes private media objects and marks related records as deleted or anonymized where appropriate.