Privacy for the PhotoMind private beta

Short version

PhotoMind Pilot processes the photo and brief you provide to generate an AI-assisted photography report. In the current pilot, PhotoMind does not intentionally store original uploaded images in its own database. The service is still a private beta and this notice should be reviewed by a qualified privacy/legal professional before public launch or paid advertising.

What we process

• The image you select for analysis.
• The optimized rendered JPEG used for AI analysis.
• Your capture intent, editing goal, selected language, and editor.
• Technical metadata such as dimensions, file type, size bucket, and rendered-image measurements.
• Optional feedback or email details if you choose to send them.

Why we process it

• To generate the PhotoMind report.
• To make the report more relevant to your photographic intent.
• To improve reliability, debugging, and beta product quality.
• To respond to feedback when you choose to provide it.

AI provider

PhotoMind sends the analysis request to OpenAI from the server. The OpenAI API key is never sent to the browser. The report is generated from the image, brief, and available technical metadata.

Image storage

The current pilot is designed without permanent app-side storage of original uploaded images. Images may still be processed temporarily in the browser, server, network, and AI provider flow so the report can be generated.

Analytics and marketing

PhotoMind can be configured with Meta Pixel for analytics/advertising measurement, but the app does not load Meta Pixel unless a separate marketing-consent flag is present. Marketing email capture should use a separate, explicit consent step.

Cookies and local storage

PhotoMind uses an essential server session cookie to keep signed-in beta users authenticated. This cookie is necessary for account access. The browser may also remember local beta acknowledgements, such as the Terms/Privacy acknowledgement and any future marketing-consent choice.

Your choices

• Do not upload images you do not have permission to process.
• Avoid including sensitive personal information in the brief.
• If feedback/email capture is enabled, consent should be separate from analysis use.
• You should be able to request deletion or withdrawal for stored feedback/email data.

Legal note

This beta notice follows the product design documented in the repo and is intended as a practical starting point. GDPR consent and privacy implementation should be reviewed against the official GDPR text and EDPB consent guidance before public launch.