Privacy at Camlo

This describes the data flow in this preview of Camlo. Before public launch, the service operator must publish its identity, contact details, retention schedule and jurisdiction-specific privacy information.

What is stored

Google sign-in provides your verified email, name, profile image and Google account identifier. Camlo stores these with your generation balance and subscription identifiers. Signing in does not connect your social accounts or give Camlo access to your Google photos.

Your photos

Your photo stays in your browser while you choose and crop it. A local draft can be saved in this browser to keep it through sign-in. When you tap Generate while signed in, the cropped photo is sent to the Camlo server and OpenAI for editing. Originals and completed results are stored in the application’s Neon database and are accessible through your signed-in account.

You can permanently remove your originals and results using Delete my photos in your account. This also removes the draft from that browser. Deletion from Camlo does not change any retention obligations or processing records of infrastructure providers. Provider backups may retain data under their own retention policies.

Payments and cookies

Stripe handles checkout and billing. Camlo stores customer and subscription identifiers, but does not receive your full card details. Essential session cookies keep you signed in. This version does not include advertising trackers.

Service providers

Camlo uses Google for authentication, Neon for application storage, OpenAI for image processing and Stripe for payments. Each provider processes data according to its own terms and privacy policy. Upload only photos you have permission to process.