Demo policy template. Replace with reviewed legal text before production deployment.

Photo Eraser policies

Privacy Policy

Demo version · Not effective

1. Scope

This demonstration describes the structure of a future Photo Eraser privacy policy. It is not an approved statement of actual product behavior and must not be used as production legal text.

The final policy should identify the legal entity responsible for Photo Eraser, the covered applications and websites, the effective date, and the regions where the policy applies.

2. Information handled by the service

The approved policy should accurately describe each category of information processed by the released product. Depending on the final implementation, categories may include:

  • Photos selected by the user and edit instructions needed to provide the requested result.
  • Device, application version, language, and diagnostic information.
  • Purchase or subscription status received from an application marketplace.
  • Support messages and information voluntarily provided by the user.

Do not retain a category in the final policy unless it matches verified application and backend behavior.

3. How information is used

The final policy should connect every collected category to a specific purpose, such as delivering an edit, maintaining account or subscription state, preventing abuse, responding to support, or improving reliability.

Any use for analytics, advertising, model improvement, or product research requires an explicit and accurate disclosure based on the production implementation.

4. Sharing and service providers

The production policy should name or categorize service providers that process information on behalf of Photo Eraser, explain why access is necessary, and document any legal or safety disclosures. It should also state whether personal information is sold or used for cross-context behavioral advertising.

5. Storage, security, and retention

Replace this section with verified storage locations, retention periods, deletion behavior, security controls, and cross-border transfer terms. Retention should be expressed by category or by a clear criterion, not as an unlimited period.

6. Your choices and rights

The final version should explain available device permissions, account controls, photo deletion behavior, marketing choices, and applicable privacy rights. It must provide a functioning request channel and any required identity-verification process.

7. Children

Specify the minimum permitted age and the process for handling information involving children based on the intended audience, marketplace rating, and applicable law.

8. Policy changes

Published versions should include an effective date. Material changes should be communicated through the application or another appropriate channel, and prior versions should remain available for audit.

9. Contact

Replace this paragraph with the approved legal entity name, postal address, privacy email address, regional representative information, and appeal channel where required.