1. Controller and scope
Anass Anedjar, a sole proprietor trading as Oruva, based in Casablanca, Morocco, is the data controller for personal data processed through Oruva's website, desktop application, account, trial, licensing and conversion services, and direct correspondence. Contact and data-rights requests: hello@oruva.app. Paddle separately controls the personal data it processes for its sale and payment services, as explained below.
Oruva is local-first, but it is not offline-only. An account is required to use Oruva 1.3.2. Asset files, previews, library records, tags, captions, search data, settings, and local diagnostics stay on your computer unless you export them, open them elsewhere, choose an external service, or use a network feature described below.
The desktop app does not use browser cookies for account authentication. It keeps sign-in credentials in secure local storage. When you visit oruva.app, our infrastructure providers process IP address, browser information, requested page and time for security and troubleshooting. The website sets no cookies and uses no analytics or advertising trackers. It may store a display preference, such as your color theme, in your browser; this stays in your browser. Payment pages operated by Paddle have their own privacy and cookie information.
2. Account, trial, and abuse prevention
Oruva accounts are for people aged 18 and over. If you believe someone under 18 has provided personal data through an Oruva account, contact hello@oruva.app so we can review the account and take appropriate action.
When you register, Oruva processes your email address, a name if provided, and protected password information. Oruva does not store your plaintext password. Account-verification, sign-in, password-reset, device, entitlement, and security records authenticate you, associate licensed devices with your account, enforce the trial, and secure the service. Ordinary requests expose connection data such as IP address and browser or app information to Oruva and its infrastructure and security providers.
An eligible new account receives a 14-day trial of the full application, including ten scene conversions in total. Using all ten ends trial conversion access; the rest of the application remains available until the 14-day period ends. The trial uses the earliest applicable account or device trial date. Deleting local account state, wiping app data, reinstalling Oruva, or registering another account does not restart a trial already used on that device.
Oruva processes a device identifier, first and most recent use times, the earliest trial date, and related account links to recognize a device, preserve trial limits, and limit account creation. It also processes device-authentication records and security-event records, including device identity, time, and partial network information, to detect copied device identities and unauthorized license sharing. An optional, read-only description of device security capabilities may include availability, compatibility level, manufacturer, and certificate availability, to plan security improvements. No security keys, certificates, or security-chip identifiers are sent as part of that description.
Oruva uses IP-based registration limits and checks for disposable email addresses to prevent abuse; these checks do not inspect mailbox content. Registration-limit records contain the source IP address and time and are pruned after a rolling 24-hour period.
We use your account email for service messages such as verification and password resets. If you change your account email, Oruva records the old and new addresses and the time, signs out existing sessions, and notifies the old address. When you contact us, we process your email address, topic, message, optional order number, and any attachments you choose to send to answer your request and maintain the relevant support, order, or privacy-request record. Do not send passwords, payment-card details, or confidential asset files with an initial request.
3. Licensing and scene conversion
Oruva processes entitlement and conversion-authorization records to enforce trial limits and paid-license access. For conversions that require license authorization, these records may include device and scene identifiers, file sizes, software compatibility information, transaction references, times, and completion status. These categories let Oruva authorize conversion, record usage, and prevent abuse.
Oruva does not upload the source scene, asset names, textures, previews, or scene contents for authorization. Conversion runs on your computer; only authorization and completion records are sent to the account service.
Active licenses may receive offline conversion access for up to 30 days for Individual licenses or 90 days for Studio seats. The service records the associated device, software eligibility, issue and expiry times and, on renewal, the number of distinct scenes converted offline, never the scenes themselves. License-check records include partial network information, rather than a full IP address, and are kept for 90 days to detect shared licenses. Revocation records include the operator and reason.
4. Payments
The Paddle entity identified at checkout and on your receipt processes purchases as merchant of record and authorized reseller. You deal directly with Paddle for the purchase. Paddle is a separate data controller for payment details, billing, taxes, receipts, refunds, and payment-risk checks under its Buyer Terms and Privacy Policy. Oruva does not receive or store full card or bank details. Oruva receives customer, transaction, purchase-status, refund or chargeback, and entitlement information needed to associate a purchase with an account.
5. Optional external actions and downloads
Search by Image is an optional, user-triggered upload. Choosing an external image-search provider sends a copy of the selected image directly from your computer to that provider. Oruva's servers do not receive or relay the image. The provider receives the image and ordinary connection metadata and may retain or use it under its own privacy policy. Selecting an asset alone does not upload it; choosing a provider is the explicit upload action.
Optional image-matching plugins may send a copy of the selected image directly to an external search or asset service when you run them. Some search actions send search terms drawn from the asset's caption, tags, or file name. Nothing is sent until you run the relevant action. Other plugins and external links may send data described in their permission disclosure. Review that disclosure and the selected service's terms before continuing.
Oruva may connect to provide the following services:
- Account registration, verification, sign-in, security, licensing, conversion authorization, and purchase or refund status.
- Paddle checkout when you choose to purchase.
- Windows update checks at startup no more than once per 24 hours and when you request a manual check. Oruva does not auto-download or install an available update.
- Plugin browsing and installation when you open the Plugin Center or install a plugin.
- Import from links, which downloads the address you provide directly from your computer to that site.
- Assistant or Visual Search setup at your request. The selected AI files are delivered from Oruva's servers and our content-delivery partners.
- User-selected plugin, external-link, or web-search actions.
Download and external-service providers receive ordinary connection metadata, such as IP address, browser or app information, the requested file or page, and request time, under their applicable privacy terms. Oruva does not sell personal information and does not use advertising or third-party usage analytics in the desktop app.
6. Local AI, diagnostics, and support reports
Oruva's Assistant and Visual Search process prompts, images, captions, and search data on your computer. Crash information stays on the computer and is not uploaded automatically.
Choose Save support report in Preferences → Diagnostics, or on the startup screen, to save a report locally. Support reports contain a record ID and creation time, app version and release channel, operating-system version and device architecture, coarse device classes (memory size, graphics class, and whether disk space is low or sufficient), opaque check codes with status and approximate age, and at most four recent opaque event codes with approximate age. They contain no asset contents, file names or paths, account details, device identifiers, or detailed error text. Reports are encrypted so only Oruva support can read them. Nothing is uploaded automatically. Email support@oruva.app with the record ID and a short description of the problem; attach the saved report if you choose to share it. The record ID alone does not upload or give support access to the report on your computer.
Local failure reports follow the same limited-content and encryption rules. Failed and canceled Generator work is eligible for local cleanup after seven days when a later run starts; retained successful or partial output remains until you remove it. A support report you save remains where you save it until you remove it.
Oruva has no general usage telemetry beyond the operational account, security, licensing, update-check, download, and user-selected external requests described here. Local diagnostics and support reports are not automatically sent to Oruva.
7. Purposes and lawful bases
We process account, authentication, license and entitlement information to provide the account and software access you request, and correspondence to answer support or pre-purchase requests. Where the GDPR or UK GDPR applies, the relevant basis is taking requested steps before a contract or performing the applicable contract. We process device identifiers, trial links, registration limits, and security records for our legitimate interests in securing accounts, enforcing license and trial limits, and preventing fraud and abuse, subject to balancing those interests against your rights. We keep transaction or legal records where a legal obligation requires them. When we rely on consent, we explain the activity and how to withdraw consent at collection. Optional external actions are initiated by you and are also governed by the selected service's terms.
Oruva is operated from Morocco. Applicable data-protection requirements may include Morocco's Law No. 09-08 and, where their territorial conditions are met, the EU GDPR or UK GDPR. This notice does not remove rights under the law applicable to you.
8. Sharing, transfers, and security
Information is shared only as needed with contracted infrastructure, security, content-delivery, email-delivery, and mailbox providers; Paddle for purchases; external services you deliberately select; or recipients required by law. Email-delivery and mailbox providers process recipient addresses and message contents to deliver or store correspondence. Providers acting for Oruva process personal data on our instructions. Paddle and external services you choose process data under their own privacy notices for their own purposes.
Oruva operates in Morocco, and providers may process data outside your country. Where applicable law requires safeguards for an international transfer, those requirements apply. Email hello@oruva.app for information about the countries and safeguards applicable to your data. Oruva uses technical and organizational measures designed to protect personal information, but no system can guarantee absolute security.
9. Retention and your rights
Local library and AI data remains until you remove it. Uninstalling Oruva does not automatically delete user-created libraries, downloaded AI files, or all application data.
Account and active-license records are kept while needed to provide the account and document entitlements. When a device is released or replaced, Oruva records account and device references, related offline-access references and expiry, times, release type, the reason category you chose and, for a manual override, the operator. These records contain no computer names, hardware details, file paths, or locations and are deleted or anonymized after 12 months. Device trial records and related anti-abuse records may be retained after account deletion where reasonably necessary to preserve a trial already used and prevent repeated abuse.
Registration-limit records are pruned after 24 hours and license-check records after 90 days, as described above. Website security and troubleshooting records, support correspondence and reports you send us are kept only while reasonably needed to secure the service, resolve your request, and handle related follow-up or disputes. Security, authorization, transaction, tax, dispute, and legal records may be retained for the applicable legal period or while needed to establish, exercise, or defend legal claims. Records are then deleted or anonymized when no longer needed. Paddle determines retention for the records it controls under its own privacy policy.
Subject to applicable law, you may request access, correction, deletion, restriction, objection, or portability, and may withdraw consent without affecting earlier lawful processing. Email hello@oruva.app; we may request information proportionate to verifying your identity before acting. We respond within the period required by applicable law and explain any permitted extension or refusal. Deleting an account may end account-based trial and license services. Some records may be retained for entitlement, security, anti-abuse, or legal-claims needs. You may complain to Morocco's CNDP or another competent data-protection authority where you have that right.
10. Changes to this policy
We publish changes with a new last-updated date and privacy revision. We notify affected users of material changes before they take effect where required, and obtain consent where required for a new use of personal data.
11. Governing law, contact, and complaints
This notice and related privacy questions are governed by the laws of Morocco without displacing mandatory data-protection or consumer rights that apply where you live. Subject to any mandatory right to bring proceedings elsewhere, the courts of Casablanca, Morocco have non-exclusive jurisdiction. Nothing in this notice limits mandatory privacy rights or available legal remedies.
Controller: Anass Anedjar, sole proprietor trading as Oruva, Casablanca, Morocco. Privacy and legal contact: hello@oruva.app. Product support: support@oruva.app.