Privacy Policy

Account information: email address, authentication provider, selected plan, organization/account identifiers, project identifiers, API key metadata, and dashboard activity needed to operate the service.

Moderation data: uploaded images, image keys, moderation labels, categories, risk scores, policy decisions, review status, webhook events, delivery logs, usage counts, timestamps, and technical metadata.

Payment information: subscription, customer, invoice, and payment status information from Stripe. Visora does not store raw payment card numbers.

Technical information: request IDs, route names, error logs, authentication events, IP-related infrastructure logs, user agent information, and operational logs needed for security, debugging, abuse prevention, and reliability.

We use information to provide image moderation, generate upload URLs, apply project policies, maintain review queues, deliver webhooks, enforce API limits, operate billing, provide support, secure the service, debug errors, and improve product reliability.

We do not sell customer images or moderation logs. We do not use customer images to build unrelated advertising profiles.

Images submitted through Visora may be stored so the product can process moderation, show moderation details, support review workflows, maintain logs, troubleshoot failures, and comply with retention settings.

Customers control what images they submit. Customers are responsible for giving end users appropriate notices and obtaining any required permissions before sending images to Visora.

Visora uses service providers to run the product, including cloud infrastructure, authentication, payment processing, email/authentication delivery, analytics-free operational logging, and related security tooling.

We may disclose information when required by law, to protect the service, to investigate abuse or security incidents, to enforce our terms, or as part of a business transaction such as a merger, financing, or acquisition.

Retention depends on your plan, your account settings, and the operational needs of the service. See the Data Retention page for the current default retention periods.

Deletion from active systems may not immediately remove data from backups, security logs, billing records, or audit records. Those systems are retained for limited periods for security, legal, tax, fraud prevention, and operational reasons.

We use account-scoped object paths, API key hashing, token-based dashboard authentication, webhook signatures, access controls, and operational logging to protect the service.

No system is perfectly secure. You are responsible for securing your own API keys, webhook endpoints, dashboard sessions, and applications.

You can update account settings, revoke or rotate API keys, delete projects, cancel paid plans through billing flows, and delete your Visora account from the dashboard where available.

You can contact privacy@visoracloud.com for privacy requests, including access, correction, deletion, or questions about how data is processed.

Visora is not directed to children. Customers must not use Visora to knowingly collect or process children's personal information unless they have a lawful basis, appropriate notices, parental consent where required, and any additional agreement required by Visora.

If you use Visora from outside the United States or submit data about people outside the United States, you are responsible for ensuring your use complies with applicable privacy, data protection, and transfer laws.

Privacy questions: privacy@visoracloud.com. Support questions: support@visoracloud.com. Security reports: security@visoracloud.com.