Privacy Policy
Last updated May 18, 2026
Memento is operated by Kri Labs. This policy explains what personal data we collect when you use the service, where it is stored, how long we keep it, and how to ask us to delete it.
1. Who we are
Memento is an event photo-sharing service at memento.kri-labs.com. A "host" creates an event and shares a QR code; "guests" scan the QR code and upload photos to a private gallery for that event.
2. What we collect
From hosts
- Email address (for magic-link sign-in and account notifications).
- Display name and time zone, if you set them in Settings.
- Event metadata: title, date, type, cover image, plan tier.
- Payment-provider customer/order IDs and payment metadata (our processor, Razorpay, handles card data; we never see it).
From guests
- The photos and short videos you upload to an event.
- An optional display name and optional email, if you choose to enter them.
- A signed session cookie that identifies your device within a single event.
- A hashed IP address (sha256, not reversible) and a User-Agent string, used to detect abuse and troubleshoot failed uploads.
Automatically, from everyone
- Error reports via Sentry, for diagnosing crashes. Sentry receives a stack trace and a request ID.
- EXIF metadata stripped from uploaded photos. We preserve orientation and timestamp only; GPS is removed before storage.
3. Where data lives
- Photos and videos: Amazon S3 (us-east-1), served through CloudFront.
- Account and event records: MongoDB Atlas.
- Transactional email: ZeptoMail (India region).
- Payments: Razorpay.
- Error monitoring: Sentry.
- Background jobs: Inngest.
4. How long we keep it
Photo retention depends on the host's plan: Free — 7 days, Standard — 6 months, Premium — 12 months. The clock starts when the upload window closes. After retention expires, photos are automatically deleted.
Account records are kept for as long as your host account exists. When a host deletes their account, the cleanup runs out-of-band and removes events, photos, guests, and S3 prefixes within a few minutes.
5. Content moderation and image analysis
On plans with a public cross-guest gallery (Standard and Premium), every uploaded photo is automatically scanned by AWS Rekognition for explicit content before it appears in the cross-guest view. Flagged photos are quarantined for host review.
On Standard and Premium events we also use AWS Rekognition to label photo contents (e.g. “cake”, “beach”) and to detect faces present in each photo so the gallery can show face counts and attributes. Label and face data is stored alongside the photo in our database and is deleted when the underlying photo is deleted.
On Premium events we additionally create a per-event face index in AWS Rekognition. Each detected face is stored as a mathematical vector (not an image) so that photos of the same person can be grouped together and so guests can find photos of themselves using the optional “Find my photos” selfie tool. Face vectors are scoped to a single event, stored in our AWS account in the event’s region, and deleted automatically when the event’s retention window ends or when you submit a data deletion request. Selfies submitted to “Find my photos” are used once for matching and discarded immediately — we do not store them.
Biometric information is treated as sensitive data. If you are a guest at an event you have the right to ask the host to disable face grouping for that event, or to submit a self-serve deletion request which removes your photos and your face vectors from our systems.
6. Cookies
mem_session— host session JWT, set on sign-in. HttpOnly, Secure, SameSite=Lax.mem_guest_*— guest session token, one per event, used to identify your uploads in that event.- A small localStorage breadcrumb so returning guests can resume the gallery without re-entering their name.
We do not use advertising or cross-site tracking cookies.
7. Your rights
You can ask us to access, correct, port, or delete the personal data we hold about you. For guest data the fastest path is the self-serve data deletion form. For host data, sign in and use the Settings page, which triggers the same cascade. You can email privacy@kri-labs.com for any other request.
8. International transfers
Data is stored in the United States (S3, MongoDB Atlas) and India (ZeptoMail). By using the service you consent to these transfers. Standard Contractual Clauses are in place with our processors where applicable.
9. Children
The service is not intended for users under 16. We do not knowingly collect data from children. If you believe a minor has uploaded data, email us and we will delete it.
10. Changes
We may update this policy. We will revise the "last updated" date above and, for material changes, notify hosts by email.
11. Contact
Privacy questions: privacy@kri-labs.com.