What this covers
This preview covers the Juriva marketing website, account and download flows, and the desktop workspace described on this site. It is an overview, not a substitute for the final privacy notice that will be published with the legal operator’s identity and support contact.
Juriva is designed for professional legal work. Do not upload material unless you are authorised to handle it and have checked the confidentiality obligations that apply to your matter.
Account information
The website may handle a name, professional role, email address, sign-in challenges, session and device records, subscription status, payment references and download entitlements so that we can authenticate an account, deliver a purchase and provide support.
Checkout acceptance records contain the account reference, policy version, selected offer, server time and request IP address. They record the affirmative action submitted to Juriva; they are not consent to marketing or cloud case processing. Account, security, billing and acceptance retention periods and request handling must be finalised before launch.
Payment card and bank details are handled by the payment provider shown at checkout. Juriva does not ask you to send OTPs, passwords or full card details through support messages.
Local case files
The current desktop workspace is designed to keep records and original case files on your computer. You control local copies, exports and backups. Removing a file from your device or backup is your responsibility; the website cannot delete a local file for you.
The desktop workspace is shared by licence accounts using the same Windows profile. Sign-out is not a data lock; read-only access can remain. Juriva does not encrypt local records or exported backups. Use separate Windows accounts for different people, protect the device and keep secure backups. Local files are not automatically deleted after 24 hours.
Future cloud processing
Cloud document processing, AI research and automatic translation require a separate release with verified access controls, provider contracts and retention behaviour. They are not enabled by this preview page.
If cloud uploads are introduced, the final notice will state what is uploaded, why it is processed, which providers receive it, how derivatives are handled and whether the proposed 24-hour deletion target is actually enforced. Until that notice is published, do not treat the 24-hour rule as a guarantee for local files, exports, account records or payment records.
Service providers
The code integrates Resend for sign-in and delivery emails, and Razorpay for payments and subscriptions. Production sender, payment and hosting configuration still need live verification. Production AI/cloud document processing remains disabled; a development pilot is not a production privacy guarantee. The final privacy notice will identify the providers and the categories of data involved before those services are activated.
Links to courts, publishers and legal news sites are third-party services with their own terms and privacy practices.
Your choices
You can use the account page to review available account, billing and device controls. You may also keep working files local, export your records and stop using the website or desktop app.
Requests to access, correct or delete account information will need to use the verified support channel published before launch. Mandatory rights under applicable law remain available.
Questions and requests
Operator location supplied for this draft: Uttar Pradesh, India. The legal operator name and full business address remain pending; this is not a completed registered address or an exclusive-jurisdiction clause.
Legal operator and address: not finalised.
Privacy contact: not finalised.
Effective date: pending final review and publication.
Do not send confidential case documents, sign-in codes or payment credentials while the official support channel is being finalised.