Privacy Policy

You drop photos; the Service reads them and makes a MEM you can share. To do that in a browser, your content is processed on our servers and by a small set of providers acting on our behalf. We do not sell your content, we do not use it to train outside models, and we do not share an understanding of one person with another without a deliberate, mutual opt-in. Your photos are yours. You can ask us to delete them, or everything, at any time.

Your content. The photos you drop and the words you add: the one line about a drop, titles and captions, journal pages, and the names you give the people in your photos. Video is not accepted at present.

Information inside your files. We read basic metadata from your photos — the date taken and the GPS location, if present — to place them on a day and in a place. The stored working copy is re-encoded at a reduced size, which removes that embedded camera data from the stored image.

Your email, if you choose to save. MEMGen works with no account. If you ask to save your progress, your email becomes your sign-in: there is no password, we send a one-time link. That is the only account detail we need. You may also give a first name; it is shown to the people you share with.

From people you share with. Recipients need no account. If you share a MEM, a recipient can open it, react, leave a line, save the link, claim their version, or send photos back. We store those reactions and contributions, any name they choose to give, and an anonymous cookie that ties their reactions to their browser. We do not infer or store anything else about them.

Usage and technical data. An anonymous session cookie, basic product events (which steps a session reaches), and — to keep the Service safe — technical signals such as IP address and browser user-agent used for rate-limiting and abuse prevention. We compute a content fingerprint (a SHA-256 hash) of each photo for de-duplication and tamper-evidence.

Cookies. We use strictly-functional cookies only: the anonymous session and, if you sign in, your sign-in. No advertising or cross-site tracking cookies.

Only to operate the Service for you: to read your photos and suggest what they show, to group faces and ask you who matters, to assemble and order a MEM and make its music, to let you share it and receive what comes back, to keep your journal, to email you the links and digests you ask for, to keep the Service secure, and to create the optional timestamp that proves when a MEM existed.

Photo reading runs in the cloud, on Google’s Gemini models acting on our behalf. Music is made by Google’s Lyria from the mood of the MEM, not from your photos. Those providers are limited to providing their service to us and do not train on your content.

Face grouping is computed in your own browser. It groups photos by the faces in them so the Service can ask “who is this?” for the people it wants to make a version for. Faces are never sent to a cloud face-recognition service. The Service never names a person by itself; a name is always something you type.

Your content is private by default; no one sees a MEM unless you share a link. A link opens one version for one person, with no account. Reactions and lines are private to you and that recipient unless the recipient marks a line public to others opening the same link. What a recipient sends back goes in only when you accept it. You can turn any link off; a turned-off link shows nothing.

Working copies of your photos are stored with Vercel (Blob); the words and structure of your archive, MEMs, journal, shares, and reactions are stored in an Upstash database. Both may process data in the United States. We keep this footprint minimal, and the Service is a prototype: do not treat it as long-term storage.

Your photos are yours. To delete a photo, a MEM, or everything you have added — your whole archive and, if you made one, your account — write to support@memoresse.com. We remove the files and their details from our active systems. Copies that people you shared with already hold are outside our control.

We rely on these providers, each limited by agreement to providing its service to us:

• Google Gemini — reading photos (what they show, when, the mood).
• Google Lyria — making the music under a MEM.
• Vercel — hosting the Service and storing photo working copies (Blob).
• Upstash — the database.
• Resend — sending sign-in links and the emails you ask for.
• Nominatim / OpenStreetMap — turning photo coordinates into place names.
• OpenTimestamps — the optional timestamp proving when a MEM existed, anchored on the Bitcoin network.

You can edit any line, title, name, or order; turn any link off; choose whether we email you; and ask us to delete any photo, any MEM, or everything. Depending on where you live, you may have additional rights (such as access, correction, deletion, or objection); to exercise any of them, contact us below.

MEMGen is for adults 18 or older. It is not directed to children, and we do not knowingly collect information from anyone under 18. If you believe a child has provided us information, contact us and we will delete it.

We protect your information with reasonable technical and organizational measures, including encryption in transit. No system is perfectly secure. MEMGen is a cloud web app; it is not the on-device, end-to-end-encrypted Memories Lockbox. Keep your own copies of anything you care about.

We may update this Policy as the Service evolves. If we make a change that materially affects how we handle your information, we will ask you to review it before it applies to you.

Questions, requests, or privacy concerns: support@memoresse.com.