Say it Again

Privacy policy

Effective October 8, 2026 · Version 2026-10-08-groups

This policy explains how Say it Again handles information when you visit the site, make a keepsake, listen to one, or contact us. For privacy questions, email contact@sayitagainmemo.com.

Who is responsible for your information

Brodor Systems LLC operates Say it Again and is responsible for the personal information described in this policy. We are based in Albuquerque, New Mexico, United States. References to “we,” “us,” and “our” mean Brodor Systems LLC.

Business mailing address: 1209 Mountain Road Pl NE, STE R, Albuquerque, New Mexico 87110, United States.

Adults and family content

Creating, submitting, and purchasing a keepsake, and signing up for our newsletter, are for adults aged 18 or older. We do not invite children to submit information directly. An adult may submit family recordings or photographs that include children with the required rights and permissions, including permission from a parent or legal guardian where required. The adult chooses what to include and who receives the link; anyone with the link can access that content.

If you believe a child submitted personal information directly, or you need help with a child’s information in a keepsake, email contact@sayitagainmemo.com with the page link or other details that help us find it. We will investigate and take appropriate steps to remove information collected contrary to this policy or applicable law.

Messaging apps fetch a preview image of an unlisted page when its link is sent; the photo is already visible to anyone with the link.

Information we collect

We collect the recording, page text, photographs, waveform, optional transcript, and delivery email you provide. We also keep the keepsake and order identifiers needed to deliver downloads, provide support, correct information, and remove the page.

Stripe handles payment details. We receive transaction status, amount, receipt email, and identifiers needed to confirm or refund a purchase, but we do not receive or store your full card number.

We record your adult confirmation, Terms acceptance, Privacy acknowledgment, and content permission, including the wording or policy version and receipt time. For offline kiosk recordings, we preserve the original consent declaration and available device-recorded confirmation or queue time separately from the later upload receipt. When you submit a keepsake, we also store the submitting device’s IP address and browser information with the permission record. These records help document authorization, resolve disputes, and prevent abuse; they are separate from optional analytics. We also keep the details you send in support or content reports.

Our website and service providers receive technical information such as IP addresses, browser details, request times, and errors to deliver pages, protect access, and diagnose problems. Necessary security and payment processing continue when optional analytics are declined.

Our application uses keyed hashes for rate-limit identifiers and removes expired database rate-limit windows through scheduled maintenance. This does not remove the separate permission records or provider security logs described above. Optional analytics events explicitly suppress IP-based location enrichment.

Cookies and storage on your device

We use necessary cookies and browser storage for access, checkout recovery, your privacy choices, and unfinished drafts. On your own device, a draft can include your recording, photos, text, and delivery email so you can resume after an interruption. Draft media expires after about 24 hours and is cleared when the site next checks it; finishing or starting over also clears the relevant draft. Limited checkout identifiers can remain separately to prevent duplicate payments. Clearing this site’s browser data removes local drafts and remembered choices.

Transcription and speech services

For group keepsakes, Cloudflare Workers AI processes the submitted recording to suggest a transcript after collection closes. Audio analysis can suggest volume and trim adjustments without changing the stored recording. The organizer can correct and approve the transcript and playback settings before publishing them. We do not use this processing to identify speakers. The guest contribution screen discloses this processing before submission.

If you turn on live dictation, your browser or device may send speech to its platform speech-recognition service. The resulting draft is editable before publishing. We upload and store transcript text only when you choose to include it; manual edits remove word-level timing data so the published words do not appear falsely synchronized.

How we use information

Create and serve the unlisted keepsake page, QR, and recording download.
Send delivery, receipt, security-code, and support messages.
Provide owner downloads and process support corrections, reports, and removal requests.
Protect the service, diagnose failures, prevent abuse, and maintain backups.

We do not sell personal information or use keepsake content for targeted advertising.

Promotional invitation emails include an unsubscribe link. Unsubscribing stops future promotional invitations to that email address; it does not stop receipts, requested access codes, or messages needed to deliver and support a keepsake. We retain a digest of the email address and the associated unsubscribe record to honor that choice. Opening the link lets you review the choice before confirming it.

You can separately sign up for occasional emails with keepsake ideas, product news, and offers. Buying, creating, or receiving a paid or free keepsake does not subscribe you. We send a confirmation email and add you to the subscriber list only after you deliberately confirm through that link.

We keep your normalized email address, the signup page or entry point, the consent wording and version, request and confirmation times, and unsubscribe history in private storage and backups. Our email provider receives the address and confirmation message. We also use necessary request information to limit abusive signups. These records document your choice and help us honor it; expiration of a confirmation link does not itself delete the signup record.

Newsletter emails include an unsubscribe link. Unsubscribing stops newsletter messages; receipts, access codes, and messages needed for your keepsake remain available. Newsletter signup and promotional invitation preferences are separate: confirming a newsletter subscription does not restart invitations you previously stopped. We retain consent and preference records as needed to document permission, prevent unwanted messages, and resolve disputes. You can contact us to request access, correction, or deletion of these records.

Optional website analytics

We use PostHog to count visits to public informational pages and the create page. If you decline, we count the visit and creation step views without any identifier stored on your device. If you accept, we also see the actions you take, including clicks, scrolling, errors, and purchase outcomes. PostHog then uses a random browser identifier stored on your device to connect those actions. We may send campaign source labels, browser and device information, and purchase amounts. We do not send delivery emails, recordings, photographs, messages, transcripts, private links, or card or bank details through these analytics.

With your permission, we also measure page loading, responsiveness, and layout stability, and count unexpected browser errors. Error reports contain a general error type and, when available, the location in our compiled application code. We do not send error messages, stack traces, page content, or the names of elements you interact with. Performance reports cover the first public page load with analytics already allowed; they stop when you navigate to another page or withdraw permission.

We do not collect new session replays or heatmaps. The private creation editor is measured through action events and these limited performance and error reports. PostHog collection is disabled on keepsake, collection, event, copy, management, capture, handoff, login, and admin pages. We remove query strings and fragments from analytics page URLs. PostHog processes this analytics data in the United States for this site.

Session replays collected before this change remain subject to the previously stated 30-day retention period; disabling collection does not delete those earlier recordings. Analytics events have a separate retention setting. They help us understand how people use the site and investigate failures; they do not contain the private keepsake content listed above. We do not enable advertising trackers on this site.

You can decline without affecting your keepsake, or change your choice using “Analytics choices” in the footer. We honor browser Global Privacy Control and Do Not Track preferences by turning off PostHog collection. Declining clears the stored analytics identity and stops action tracking, performance and error reports; visit and creation step counts continue without stored identifiers. If you previously allowed analytics for a checkout, later server payment confirmations and refunds may still be linked to that visit. You can contact us about deletion of data already collected.

Optional playback counting

A keepsake can also have a playback counter, separate from PostHog. It counts a play only when counting is enabled for that keepsake and the listener allows it through “Playback privacy.” Allowing this stores the play time, keepsake identifier, IP address, and browser information to avoid duplicate counts and abuse. Scheduled cleanup combines raw records older than 30 days into totals and removes their IP and browser information. Aggregate totals can remain with the keepsake.

Listeners can play the recording without allowing the counter, change their choice in Playback privacy, or use Global Privacy Control or Do Not Track to decline it. Declining stops future counter records on that browser; it does not remove earlier records. Necessary page delivery and security processing still occur.

Sharing and service providers

Anyone with an unlisted keepsake link can access its published content. We otherwise share information only with providers that operate the service—such as hosting and limited public-page analytics, object storage, email, database, and payment providers—or when required for safety, fraud prevention, or law.

These are the providers we use, and what each one does:

Vercel — hosts the website and runs its server functions.
Supabase — the database that holds keepsake records, and operator sign-in.
Cloudflare — the domain, delivery of pages at the edge, and R2 storage for recordings, photos, and other files.
Resend — sends delivery, receipt, security-code, support, promotional invitation, and newsletter confirmation emails.
Stripe — processes payments, receipts, refunds, and disputes.
PostHog — visit and creation step counts without stored identifiers when declined; action analytics and limited performance and error reports with your permission.

We do not routinely inspect personal keepsakes as part of creating them. Limited access may be needed to resolve a support request, investigate a report, protect the service, or comply with law. A content complaint may be shared with the person who submitted the content when needed to investigate it or follow a legal process.

Retention and your choices

Group organizers use Supabase-managed sign-in, including email and Google where enabled. We associate their verified account ID with their books. Google supplies the account information needed to sign in; we do not obtain access to Google Photos, Drive or contacts through this sign-in. Guest contributors do not need accounts. Their private receipt is a capability to manage that contribution and should not be shared. Necessary rate-limit and security checks help protect event upload links.

A group guest draft can remain in that browser until it is successfully received, replaced by a new draft, or cleared by the person using the device. This is separate from the individual creator’s temporary draft expiry described above. After receipt, local media is cleared while a small receipt record may remain. An interrupted or rejected group submission is kept locally so it can be retried or downloaded. Browsers can evict local storage; a message is only confirmed received when the server says so.

Paid group content is included in our backups during collection and after publication, including a paid book that is never published. Withdrawn contributions and removed books are excluded from new backups after deletion reconciliation. Older backup copies are scheduled to age out after 35 days; maintenance can retry delayed cleanup. Current deletion records override an older backup during a restore. Limited permission, payment, legal-hold and deletion records can be retained for the purposes described below. Downloaded copies held by recipients are outside our control.

We host published keepsake content until the owner requests removal, subject to the removal and service-closure provisions in our Terms. Temporary private download links expire; the owner can get new downloads through Owner access. Removing a keepsake disables access and starts deletion of its stored media and personal page details. We retain limited payment, permission, security, and deletion records as needed for accounting, disputes, legal duties, and preventing deleted content from being restored.

Earlier backups may contain a copy until they expire or are deleted. Restores must preserve removal decisions, and new application backups exclude removed keepsake media. Backups and provider security logs have separate retention settings from the published page and optional analytics.

When an operator kiosk loses its connection, an unfinished raw recording may stay in that device’s browser only as a recovery copy. Successful uploads remove their local copy. After seven days, or after a definitive server rejection, automatic retries stop and the recording is marked for operator review; it remains on that device until an operator retries it, downloads it for recovery, or explicitly discards it.

A recording uploaded for online submission may briefly remain in a private server staging area while processing finishes. Every signed upload is reserved in the cleanup queue before the upload link is issued. Successful jobs remove the staging copy. Processing failures keep that private copy while retries are pending; a repeatedly failing upload is quarantined for up to 14 days so an operator can retry it. An operator can acknowledge deletion sooner, which queues the copy for the next cleanup sweep; otherwise it becomes eligible for removal when the quarantine expires. Ordinary uploads abandoned before submission become eligible for cleanup after 24 hours.

In the online creator, private staging files are normally eligible for cleanup after 24 hours when no payment needs recovery. Paid, processing, or uncertain payment attempts retain their files while delivery or payment reconciliation is pending. Successful delivery permits staging cleanup. Cleanup runs periodically and retries failures, so an expiry time is not a promise that every stored copy disappears at that exact moment.

Access, correction, and deletion requests

Use Owner access on your keepsake page to download your files or request removal. You can also email contact@sayitagainmemo.com to request access, correction, or deletion of personal information, including analytics already collected. Include your checkout email and page link when available, and tell us what you want changed. Do not send card details or an identity document with your first message.

We may ask for information needed to verify that the request concerns you or that you are authorized to act for someone else. We assess requests under applicable law and explain any information we need to retain. If your voice, photo, or private information appears on someone else’s page, use its Report link or contact us about the content.

Changes to this policy

We post revisions here with their effective date and version. For a material change, we provide a notice on the site before it takes effect and email affected customers when the change concerns information associated with their existing keepsakes. We seek new permission when required before using information for a new optional purpose.