How Memoriam handles personal and memorial information

Memoriam is a web application for creating memorial pages, uploading photos and videos, building slideshows, publishing public tribute pages, and exporting memorial videos. This policy applies to the public site, the authenticated dashboard, the organization portal, and published public memorial routes such as /tribute/{id} and organization-branded variants.

This policy covers information we process when you visit the site, create an account, upload memorial content, publish a tribute, manage an organization, or complete a memorial or subscription purchase.

Depending on how you use the service, we may process:

• Account and profile information, such as your email address, authentication identifiers, display name, and organization membership details.
• Memorial content, including memorial names, dates, written tributes, photo uploads, video uploads, slideshow settings, captions, and organization branding assets such as logos and colors.
• Payment and billing records, including the purchases or subscription status associated with your account. Payment card details are handled by Stripe rather than stored directly in Memoriam.
• Communications data, such as operational emails we send for account onboarding, purchase confirmation, and video-completion notices.
• Technical and service data, such as request logs, upload metadata, basic device or browser context, security events, and error information needed to operate and protect the app.

We use this information to:

• create and secure user accounts
• store, organize, and display memorial content
• publish public tribute pages when you choose to publish
• process purchases, subscriptions, and payment reconciliation
• render and deliver exported memorial videos
• send operational emails related to the service
• monitor abuse, resolve failures, and maintain platform security

Memorial drafts are managed inside the authenticated app. When a memorial is published, that memorial becomes available on a public route that can be viewed without signing in.

Public memorials may appear at Memoriam-hosted URLs such as /tribute/{id} or on organization-branded subdomain or slug-based routes for professional customers. Do not publish content unless you are comfortable making it available to anyone who receives or visits the public link.

Memoriam relies on third-party providers to operate the service. Based on the current stack, those providers include:

• AWS Cognito and Amplify for authentication and session management
• Cloudflare R2 for uploaded media storage
• Stripe for checkout, subscriptions, and payment processing
• AWS SES for transactional email delivery
• Railway-hosted application services for the web app and video-rendering infrastructure

We may also process data where required to comply with law, enforce our terms, protect users, or support corporate transactions involving the service.

Memoriam does not implement a separate marketing or advertising cookie layer in the current app. We do not rely on in-app analytics trackers to personalize ads or sell browsing profiles.

The service does rely on essential authentication and session mechanisms provided by AWS Cognito and Amplify, and it stores limited browser data needed for product operation. For example, the app currently uses browser storage for theme preferences and for in-progress memorial-creation state inside the authenticated experience.

Your browser or underlying infrastructure may still use technical storage needed to keep sign-in, security, and content delivery working. If you block essential browser storage, some features may not work correctly.

We keep account, memorial, and organization data for as long as needed to operate the service, maintain public memorials you choose to publish, and preserve billing and security records.

When memorial content is deleted inside the app, related media may first move through a deleted or detached lifecycle before final cleanup. Some operational, security, and financial records may be retained longer when necessary for reconciliation, fraud-prevention, or legal compliance.

Memoriam may update this policy as the product, legal obligations, or service providers change. When we do, we will update the date at the top of this page and publish the revised version here.