Privacy Policy

1.1

The Platform is operated by Docuswift Solutions LLP, Hyderabad, Telangana, India. Questions about this policy go to support@casepdf.in.

1.2

This policy is linked from the CasePDF homepage and from the header of the marketing pages. The same link belongs in the signed-in application, where a user can open it without searching for it.

2.1 What we access

If you choose Sign in with Google, the sign-in service asks Google for the basic sign-in scopes openid, profile, and email. From that sign-in, CasePDF receives:

1. your name, if Google provides it;
2. your Google account email address; and
3. the account identifier Google uses for that sign-in.

CasePDF does not receive your Google password. CasePDF does not request access to Gmail, Google Drive, Google Calendar, Google Contacts, or any other Google product.

2.2 How we use it

We use that Google account data only to:

1. create and sign you in to your CasePDF account;
2. show your name and email in the account;
3. keep the account distinct from other accounts; and
4. write to you about the account, a subscription, support you asked for, or a change to this policy.

We do not use Google user data for advertising. We do not sell it. We do not use it to train a model. We do not allow our staff to read it except to secure the account, to answer a request you made, or where the law requires it.

2.3 How we store it

We store the name, email address, and account identifier with your CasePDF account, and in the signed session that keeps you signed in. We do not store a copy of your Google password, and we do not keep a Google access token for later use of other Google products.

2.4 Who we share it with

The sign-in is completed by our authentication provider, currently Clerk, and, where that path is still offered, Auth0. Those providers receive the Google sign-in so they can hand CasePDF the name, email, and account identifier. We also store the resulting account record with Amazon Web Services.

We do not share Google user data with a court, a tribunal, an advertiser, or a data broker. We do not transfer it except to the providers in this clause, and only so they can perform the sign-in and account storage described here.

2.5 Limited use

Google user data is used only to provide and secure the CasePDF account you signed in to. It is not sold, and it is not used for advertising.

3.1

If you sign in with an email and password instead of Google, we receive the name and email address you enter, and the authentication provider stores the credential. CasePDF receives the resulting account identifier, name, and email. We still do not receive or store the password in the CasePDF application.

3.2

We keep a record of the plan on the account, including whether it is Free or Pro, and the OCR page balance for that account. That record is stored so the limits on the account can be applied.

4.1

When you use the application, you may upload PDFs and images: petitions, affidavits, annexures, orders, and the other papers in a filing. Those files, and the case details you type (court, parties, and the names that appear on the book), are User Content. You keep ownership of them. The Terms of Use say so, and this policy does not change that.

4.2

The files are stored so you can reopen the matter, arrange the pages, and download the result. File bytes are stored in Amazon S3. The project record that points at those files is stored in Amazon DynamoDB, under your account.

4.3

Some tools run in your browser. A file that never leaves your browser is not sent to CasePDF. A file you save into a Workspace project, or a file you submit for OCR, is sent to CasePDF for that purpose.

5.1

If you run OCR, the PDF pages you submit are sent to an OCR provider so CasePDF can return a searchable PDF. The provider is either Google Cloud Document AI or Amazon Textract, depending on which engine is operating for that request.

5.2

When the engine is Google Document AI, Google receives the pages you submitted, processes them to produce text, and returns that result to CasePDF. This uses CasePDF’s own Google Cloud account. It is not access to your Gmail, Drive, or other Google account data.

5.3

We send those pages only to produce the OCR result you asked for. We do not sell them, and we do not use them for advertising. The Terms of Use explain the limit of what we control in an independent provider’s own systems. Read clause 8 of the Terms before you upload a privileged or confidential paper.

6.1

Paid plans are charged by Razorpay. Razorpay collects the payment details you enter on its checkout. CasePDF does not store your full card number or UPI secret.

6.2

We keep the fact of the payment against your account: the plan, the Razorpay order reference, and that the payment was verified. That is enough to apply Pro and to answer a billing question.

7.1

We use the information above to:

1. sign you in and keep the session;
2. prepare, store, and return the PDFs you ask for;
3. apply the Free and Pro limits, including the OCR page balance;
4. take and record a subscription payment;
5. answer a message you send to support; and
6. protect the Platform against abuse and fix faults.

7.2

We do not sell personal information. We do not use Google user data, or the documents you upload, to advertise to you or to anyone else.

7.3

On the public website at casepdf.in, we use Google Analytics to count page views and see which pages are opened, only after you turn on Count page visits in the cookie choices. Until then, that measurement does not run. Google receives the page address, a general location, and information about the browser and device. We do not send the contents of a PDF through this measurement, and we do not use it to advertise. The choices are described in the cookie policy.

8.1

We share information only with the providers that perform a function described in this policy:

1. Clerk, and Auth0 where that sign-in path is offered, to complete sign-in, including Sign in with Google;
2. Google, for the Google account fields in clause 2, for OCR pages when Document AI is the engine, and for website visit measurement on casepdf.in as described in clause 7.3;
3. Amazon Web Services, to store the account, the plan, and the project files, and for OCR when Textract is the engine; and
4. Razorpay, to take a subscription payment.

8.2

We may also disclose information if a law, a court, or a competent authority requires it, or if it is reasonably necessary to investigate abuse of the Platform. A filing you prepare is not sent to a court by CasePDF. You upload it yourself, if you choose to.

9.1

The Terms of Use state the document rule: unless a feature says otherwise, documents uploaded to CasePDF are kept for a maximum of 30 days and are then deleted. Download anything you need to keep. CasePDF does not promise that a deleted document can be recovered.

9.2

Account information, including a name and email received from Google, is kept while the account exists, and for as long after closure as we need to finish a payment, resolve a dispute, or meet a legal duty.

9.3

You can ask us to delete the account by writing to support@casepdf.in. Alternatively, you can also delete your account from the settings menu after you log in. We will delete the account record and the documents still stored for it, except for what we must keep for a payment record or a legal duty.

10.1

You can sign in with email instead of Google. If you have already used Sign in with Google, you can revoke CasePDF’s access from your Google Account permissions. Revoking it stops future Google sign-in. It does not by itself delete the CasePDF account already created. Write to us if you want that account deleted.

10.2

You choose which files to upload, and whether to run OCR. A file you do not upload is not received by CasePDF.

11.1

If we change this policy, we will change the “Last updated” date at the top. The current version is the one published at this URL.

11.2

If we change how CasePDF accesses, uses, stores, or shares Google user data, we will update this policy first and notify signed-in users by email, or by a notice in the application, before that change applies.