Privacy Policy
Effective: 8 September 2026 · Version: 1.1
Current operator: Utkarsh Prakash Verma. Until a registered company succeeds the project as operator, privacy questions and rights requests can be submitted through the Support & Community hub. A verified business correspondence address and dedicated privacy email will be published before commercial launch.
This policy explains how UVENARO handles information. Production disclosures must remain synchronized with the actual app, backend, SDKs and store Data Safety/App Privacy declarations.
Data we handle
- Local creative content: imported media, canvases, drafts and recovery snapshots stay on the device unless you explicitly request cloud sync, AI processing, sharing, support attachment or another online operation.
- Account and security: when connected, identifiers, authentication events, verified devices, sessions and security activity are processed to operate and protect your account.
- AI requests: prompts, selected media and job settings are sent only after an explicit AI action. The applicable retention choice and provider processing must be disclosed before production use.
- Support: issue descriptions, optional reply email and separately opted-in minimal diagnostics may be processed to resolve requests.
- Analytics and marketing: analytics and product news are opt-in. Project media, prompts, contacts, precise location and sensitive creative content are excluded from the analytics foundation.
- Payments: checkout is hosted by the configured payment provider. Uvenaro does not receive or store full card numbers.
Camera, microphone and permissions
Camera access is user-initiated. The camera workspace does not request audio. Permissions must be limited to current, disclosed features and can be withdrawn through device settings. Uvenaro does not silently extract precise location or identify faces.
Purposes and sharing
Information is used to provide requested features, secure accounts, recover projects, process opted-in AI jobs, deliver support, meet legal obligations and prevent abuse. It is shared only with configured processors necessary for those purposes, under appropriate protections. Personal or sensitive data is not sold.
Service providers and AI processing
Configured cloud foundation: Google Firebase is the project's currently configured cloud-service foundation for authentication, database and storage capabilities. These production cloud features remain disabled until security, consent, access-control and release gates pass.
Public website hosting: The public web site is currently delivered through GitHub Pages.
AI processing: No production AI model provider is currently selected or connected. Before any AI provider is enabled, Uvenaro will disclose the provider, processing purpose, categories of data sent, processing location, retention period, training policy, subprocessors, deletion controls and international-transfer safeguards, and obtain consent where required. Selected media and prompts will not be sent to an AI provider while the production AI service remains unconfigured.
Retention, deletion and control
Local data remains until you remove it, clear app/site storage or uninstall. Production services must publish exact retention periods. Account controls provide data export, consent withdrawal, session revocation and protected deletion requests. Deletion may retain narrowly required security, fraud, tax or legal records for documented periods.
Children and sensitive content
Uvenaro is not directed to children unless a separately reviewed age-appropriate experience, parental controls and legally required consent are implemented. Restricted content, non-consensual intimate material and prohibited face replacement are not allowed.
International processing and security
Production deployment must disclose processing locations and lawful transfer safeguards. Protections include encrypted transport, least privilege, authenticated services, audit trails, rate limits, incident response and immutable originals; no system can promise absolute security.
Changes and contact
Material changes will update the effective date and be communicated when required. Privacy questions, access or deletion requests, consent withdrawal and complaints can be submitted to the current operator, Utkarsh Prakash Verma, through the Support & Community hub. The verified business correspondence address and dedicated privacy email remain mandatory release gates and will be published before commercial launch or native-store submission.
This public policy is an engineering baseline, not legal advice. Qualified counsel must approve jurisdiction-specific production terms.