Memory & Likeness Consent

1. Obtain appropriate authorization

Before uploading or generating content involving another person's identity, likeness, voice or private communications, obtain the appropriate authorization and rights for the intended use. Consider the rights of living people depicted, speakers, authors, photographers and other affected people.

Being a relative, possessing a recording or creating a memorial does not automatically establish all necessary permissions. Do not upload disputed, unlawfully obtained or unauthorized private material. If authority is uncertain, do not proceed until it is resolved.

2. Keep permissions specific

Permission to preserve a photo or story does not automatically permit public sharing, AI processing, voice cloning, avatar generation or deceptive impersonation. Explain the intended purpose, audience and relevant processing before obtaining permission.

Signup and Memory Space acknowledgement boxes are not proof of the represented person's consent and do not replace evidence of authorization. Existing feature-specific voice-clone and avatar controls remain separate and unchanged.

3. What this application records

This local review implementation displays versioned draft notices and requires unchecked form acknowledgements before proceeding. The signup and Memory Space acknowledgement values are temporary UI state: they are not sent as versioned legal-consent records to a backend.

No legal-consent receipt, evidence verification, policy-history ledger or automatic re-consent system is implemented for these general policies. Existing users and existing Memory Spaces are not retroactively recorded as having agreed.

4. Unauthorized-content reports

If you believe content is unauthorized, prepare the relevant content identifier or page, your relationship/authority, the concern, the action requested and minimal supporting evidence. Do not circulate the disputed content further or send passwords, recovery codes or unnecessary identity documents.

See Grievance & Support for the proposed reporting steps and current contact gap. There is no working report-submission/takedown endpoint on these pages. Where you control a memory, its existing delete action may remove its record, but this does not guarantee removal of every media or provider copy.

[REQUIRES CONFIRMATION] A monitored reporting channel, authority verification, disputed-estate procedure, temporary restriction process, response targets and appeal route require approval before public release.