Privacy

Awaiting legal review. This describes what the system actually does today, written by the engineers who built it. It is not a lawyer-reviewed privacy policy and must be replaced beforePicSoar takes payment or processes anyone's personal data at scale.

What we hold

DataWhyRetention
Email addressAccount identity and login linksUntil the account is deleted
Organization, project, origin and preset configurationTo operate the serviceUntil deleted, then 30 days
Usage ledgerBilling and dispute resolution7 years (financial record)
Operational analyticsDashboards and debugging. Sampled.Per plan: 7 to 365 days
Audit eventsSecurity and accountabilityPer plan
Hashed IP and user-agent on sessionsDetecting session theftSession lifetime, 14 days

Your images

Images delivered through the CDN are read from your origin and cached as derivatives at the edge. We do not copy them into our own storage, we do not index their contents, and we do not use them to train anything. Purging a project makes every cached derivative unreachable immediately.

Images processed in the browser-based compressor are never transmitted to us at all. That is a property of how the page works, not a policy we could quietly change.

What we deliberately do not collect

Deletion

Deleting a project removes its delivery configuration from the edge immediately and marks its records deleted; they are purged after 30 days. The usage ledger is retained, because it is the evidence behind invoices you have already received.

Account deletion is not yet self-service. Email support@picsoar.com and it will be done manually.

Subprocessors

Cloudflare (compute, storage, CDN, DNS resolution for origin verification). No others today. Adding one is a change to this page, announced before it takes effect.