Privacy Policy

When you create an event as a Host, you are the controller of the guest data and content captured for that event. We are a processor acting on your instructions. For your own account information (name, email, billing), we are the controller.

Hosts must have an appropriate basis to invite guests and to display, share, or export their photos. Guests retain rights to their own content; the “Request removal” flow on every photo is the primary way a guest exercises those rights against the host.

We collect information directly from you:

• Account. Name and email when a Host creates an account, plus a password or passkey credential. Authentication is performed by Supabase Auth on our behalf.
• Event metadata. Title, date, location, brand color, retention settings, and moderation preferences for each event you create.
• Guest profile. Display name; optionally email and phone if a guest opts in. Consent flags for live-wall display and recap inclusion.
• Media. Photos and videos uploaded by guests or staff, plus their captions, tags, aesthetic scores, and moderation decisions.
• Reactions and reports. Emoji reactions to a photo and the reason text when a guest reports a photo for review.
• Operational logs. Audit-log records of moderation actions, reveals, exports, and retention purges. Server logs and crash reports.
• Payments. If you upgrade, Paystack collects card data and returns a transaction reference, tier, and amount; we do not see card numbers.

• Run the event: ingest uploads, moderate, display the live wall, deliver recaps.
• Enforce safety: AI moderation (Gemini), human moderation queues, content reports.
• Keep things working: error monitoring, performance metrics, fraud / abuse signals.
• Send transactional email: recap-ready notices, staff invites, your replies to support.
• Process payments and apply tier entitlements when you upgrade.

We do not sell your photos or guest data. We do not use your content to train external models. AI moderation and recap generation use the Gemini API; per Google’s terms for paid Gemini API access, those inputs are not used to train Google’s models.

We use the following subprocessors. Each handles a specific slice of the workflow.

Some of these process data outside Nigeria. By using Snappi, you acknowledge that processing may occur in those regions.

• Photos and videos. Each event has a media retention window (defaults to 365 days after the event date; the Host can shorten this in settings). When the window passes, our retention cron archives the media (visibilityState=REMOVED) and writes an audit record. Storage objects may persist for a short clean-up window before hard deletion.
• Exports. Generated archives and recap exports persist for 30 days by default.
• Account information. Retained for as long as your account exists. You can request deletion (see “Your rights”).
• Audit logs. Retained indefinitely for safety and compliance.
• Payments. Held by Paystack under their retention rules; we keep the transaction reference and tier entitlement.

Photos uploaded to an event are private by default to that event’s ecosystem — visible to the Host, staff with explicit capability grants, and guests who joined that event via its link or QR code. A Host can choose to make an event public, in which case the public live wall is reachable without a guest token.

Each guest is asked at join time to consent (or not) to inclusion in the live wall and the post-event recap. Reactions, reveals, and visibility changes are recorded.

You can request access, correction, export, or deletion of your personal data. For guests, the per-photo “Report” flow on the live wall and recap is the fastest way to request removal of a specific item. For broader requests:

• Email us at hello@getsnappi.app with the event slug and a description of what you’d like actioned.
• We respond within 30 days.
• Hosts also retain the ability to delete an event from their dashboard, which cascades to its associated guests, media, moderation decisions, and reactions.

We use the browser’s storage in three ways:

• Session cookies (Supabase Auth) to keep Hosts signed in.
• A short-lived guest-token cookie scoped to a specific event.
• A localStorage flag for guest UX (hiddenPhotoIds, analytics opt-out).

We do not use third-party advertising cookies. Analytics events via PostHog are anonymous unless a guest signs in.

Snappi is not intended for children under 13. If you believe we have collected information about a child under 13 without appropriate consent, write to us and we will delete it.

We may update this policy. Material changes will be posted to this page with a new “Last updated” date. Continued use after a change indicates acceptance.