Sarva Privacy Policy

Last updated: October 4, 2026

Sarva is designed to be local-first. Your Password Store and Me Docs data is primarily stored on your Android device. Sarva does not operate a cloud database for storing the contents of these features. Google Drive is an optional backup and restore destination selected by the user.

This Privacy Policy explains how Yuddhaa ("Yuddhaa", "we", "us", or "our") handles information in connection with the Sarva Android application ("Sarva" or the "Application").

Sarva is a privacy-focused, offline-first utility suite. The current application includes features such as Password Store and Me Docs.

This policy describes:

What information Sarva handles.
What information remains only on your device.
How optional Google Sign-In works.
How optional Google Drive backup and restore works.
How Sarva protects backup data before uploading it.
What Google processes independently when you use Google's services.
How you can delete your Sarva data and backups.

Sarva's Android package identifier is com.yuddhaa.sarva.

1. Developer

Sarva is developed and published under Yuddhaa.

For privacy-related questions, requests, or concerns, contact:

Email: main.yuddhaa@gmail.com

2. Sarva Does Not Have a Traditional Cloud Account System

Sarva does not operate a traditional Sarva cloud account system.

Google Sign-In is used to authenticate the user for functionality involving Google services, particularly the optional Google Drive backup and restore functionality. Signing in with Google does not create a separate cloud account on a Yuddhaa-operated Sarva server.

Sarva does not operate its own authentication server and does not maintain a Yuddhaa cloud database containing users' Password Store or Me Docs contents.

3. Local-First Storage

Sarva is primarily designed to store user data locally on the Android device.

Under normal operation, your Password Store and Me Docs data is not transmitted to Yuddhaa-operated servers.

Sarva can be used without connecting a Google account or enabling Google Drive backup.

4. Password Store

Password Store allows you to store information such as usernames, passwords, descriptions, and related password-store data.

This information is stored locally on your Android device in an encrypted SQLite database using SQLCipher and AES-256 encryption.

Sarva does not upload the contents of your Password Store to a Yuddhaa-operated server as part of normal Password Store operation.

Password Store contents are not used by Yuddhaa for advertising, behavioral profiling, analytics, or AI model training.

5. Me Docs

Me Docs allows you to store documents and files locally on your Android device.

Me Docs is designed for local and offline storage. Sarva does not operate a Yuddhaa cloud storage service for your Me Docs documents.

Your documents remain on your device unless you explicitly use a feature that transfers them, such as the optional Google Drive backup functionality.

6. Google Sign-In

Sarva supports Google Sign-In.

Google Sign-In is used primarily to authenticate the user for Google-related functionality and to obtain authorization for Sarva's optional Google Drive backup and restore functionality.

During Google Sign-In, Google may make profile information available to Sarva, including, where available:

Name
Email address
Profile image

Sarva keeps the current Google user information in application memory during the active session so that the application can display the signed-in account.

Sarva does not operate a separate backend that permanently stores this Google profile information.

Sarva does not claim to permanently store your Google profile information beyond what is required by the current application session and implementation.

Important: Google independently processes information associated with your Google account and Google services. Sarva does not control Google's independent data processing.

For information about Google's handling of information, please review Google's Privacy Policy .

7. Google Drive Access

Google Drive integration is optional. You can use Sarva without connecting Google Drive.

Sarva currently requests the Google Drive OAuth scope:

https://www.googleapis.com/auth/drive.file

This scope is used to allow Sarva to create, upload, update, and download the Sarva backup files that the application works with.

Sarva does not request full access to the user's entire Google Drive.

When you authorize Google Drive access, Sarva creates and uses a Sarva backup folder structure in your Google Drive.

My Drive/
            └── Sarva/
            ├── pwdStore/
            │ └── pwdStore.sarva
            └── meDocs/
            └── meDocs.sarva

These backup files are stored in your Google Drive. Google Drive is not Sarva's primary storage and is not operated by Yuddhaa.

Google processes information relating to your Google account and Google Drive according to Google's own policies, terms, and systems.

You can review Google's documentation concerning OAuth scopes here .

8. Password Store Backup

Password Store backups are encrypted locally before being uploaded to Google Drive.

The current backup process works generally as follows:

Password Store data is serialized locally on the device.
An AES-256-GCM encryption key is derived using SHA-256 from the application's Password Store secret.
A random 12-byte initialization vector (IV) is generated for each backup.
The backup is encrypted locally using AES-256-GCM.
The resulting encrypted backup is uploaded to Google Drive as a .sarva file.

Sarva does not upload the plaintext contents of the Password Store as the Google Drive backup.

Google Drive therefore receives the encrypted backup file produced by Sarva rather than the plaintext Password Store records.

9. Me Docs Backup

Me Docs backups are also encrypted locally before being uploaded to Google Drive.

During backup, Sarva collects the selected Me Docs data locally. Certain internal/system items, including profileInstalled and restore_* folders, are excluded from the backup process.

The selected data is compressed locally into a ZIP archive.

The ZIP archive is then encrypted locally using AES-256-GCM.

The resulting encrypted backup is uploaded to Google Drive as:

meDocs.sarva

The backup system does not upload the plaintext Me Docs documents as individual files to Google Drive.

10. Restore

Restore operations are initiated by the user.

10.1 Password Store Restore

When you choose to restore a Password Store backup, Sarva downloads the encrypted backup from your Google Drive.

The backup is decrypted locally on the device and the Password Store data is restored into the local encrypted SQLCipher database.

Yuddhaa does not receive the backup for server-side decryption.

10.2 Me Docs Restore

When you choose to restore a Me Docs backup, Sarva downloads the encrypted backup from Google Drive and decrypts and validates it locally.

Restored documents are placed into a new restore_* folder rather than silently overwriting existing Me Docs data.

11. Information Sarva Does Not Intentionally Collect

Based on the current implementation, Sarva does not intentionally collect or transmit the following categories of information for analytics, advertising, profiling, or unrelated purposes:

Phone numbers
Location data
Browsing history
Advertising identifiers
Analytics data
Behavioral tracking data
Marketing profiles
Chat transcripts
Usage-tracking statistics

Sarva also does not intentionally operate a service that collects users' Password Store passwords or Me Docs documents on Yuddhaa servers.

12. Analytics, Advertising, and Tracking

Sarva does not intentionally use third-party advertising, analytics, tracking, remarketing, or data-broker SDKs.

Sarva does not intentionally collect usage statistics for behavioral profiling or advertising.

Sarva does not display third-party advertisements as part of the current functionality described in this policy.

Sarva does not sell user data.

13. Third-Party Libraries and Services

Sarva uses third-party libraries and services required to provide application functionality. These include technologies such as:

Capacitor
SQLite / SQLCipher
Google Sign-In
Google Drive API
Encryption libraries
Document and file handling libraries

These technologies are used to provide Sarva's functionality. Sarva does not intentionally use third-party advertising, analytics, tracking, or data-broker SDKs.

Third-party services such as Google may independently process information according to their own privacy policies. Yuddhaa does not control that independent processing.

14. Data Sharing

Yuddhaa does not sell your personal information.

Yuddhaa does not share the contents of your Password Store or Me Docs data with advertisers, data brokers, or other third parties for advertising, behavioral profiling, or unrelated commercial purposes.

Google

When you choose to use Google Sign-In or Google Drive backup, information necessary for those features is processed through Google's services.

This may include Google authentication information, the profile information made available during sign-in, authorization information, and encrypted Sarva backup files stored in your Google Drive.

Google is an independent provider of these services. Google's processing is governed by Google's own policies and terms.

Legal requirements

Yuddhaa may disclose information when required to do so by applicable law, valid legal process, or a lawful request from a competent authority.

15. Data Retention

Local Sarva data

Password Store data and Me Docs data remain on your device until you delete the relevant data using Sarva's available functionality, clear the application's storage, uninstall the application, or Android otherwise removes the application's local storage.

Yuddhaa does not maintain a separate cloud copy of this local Password Store or Me Docs data.

Google profile information

The current Google user information received during Google Sign-In is kept in application memory for the active session so that Sarva can display the signed-in account.

Sarva does not operate a separate backend that retains this profile information as a permanent user account database.

Google Drive backups

Google Drive backups are separate from local Sarva storage.

An encrypted .sarva backup remains in your Google Drive until you delete it or it is otherwise removed from your Google Drive.

Deleting local Sarva data does not automatically delete an existing backup from Google Drive.

16. Deleting Your Data

Local data

You can delete your local Sarva data using the deletion functionality available in the application.

Clearing Sarva's application storage or uninstalling the application removes its normal application-local storage according to Android's application storage behavior.

Because Sarva does not maintain a central cloud copy of Password Store or Me Docs contents, there is no Yuddhaa server database from which those local files need to be separately deleted.

Google Drive backups

Google Drive backups are separate from local Sarva data.

If you want to completely remove a backup created by Sarva, you must delete the corresponding .sarva backup from your Google Drive.

Deleting local Sarva data does not automatically delete the encrypted backup stored in Google Drive.

Google Sign-In and authorization

Sarva supports Google sign-out. Signing out clears the currently signed-in Google user from the Sarva application.

Signing out of Sarva does not delete your Google account.

If you want to completely revoke Sarva's previously granted Google authorization, you can manage or revoke the relevant authorization through your Google account's security settings.

Revoking authorization through Google may prevent Sarva from accessing Google Drive until you authorize it again.

17. Google Authentication Tokens

Google authentication and access tokens are handled by the Google Sign-In integration and are used to authenticate requests to Google services such as Google Drive.

Sarva does not operate its own authentication server and does not store Google authentication tokens on a Yuddhaa server.

This policy does not make a claim about a specific persistent local token-storage mechanism because token management is handled by the Google Sign-In integration.

18. Security

Sarva is designed around a local-first architecture that reduces the need to transmit sensitive user data to remote servers.

Security-related measures used by Sarva include:

Password Store data is stored in a SQLCipher-encrypted SQLite database using AES-256 encryption.
Password Store backups are encrypted locally using AES-256-GCM before upload.
Me Docs backups are compressed locally and encrypted using AES-256-GCM before upload.
Password Store backup encryption uses a newly generated random 12-byte IV for each backup.
Backup decryption takes place locally during restore.

Sarva does not intentionally upload plaintext Password Store passwords or plaintext Me Docs documents to Google Drive as part of its backup system.

No security system is completely secure. Sarva is designed to provide strong local and backup protection, but no software, encryption system, device, or electronic storage method can guarantee absolute security.

You should also protect your Android device, Google account, authentication credentials, and any secrets used with Sarva.

19. Google as an Independent Service Provider

Sarva uses Google services for Google Sign-In and optional Google Drive functionality.

Google may independently collect and process information when you use Google's services. Such processing may include information associated with your Google account, devices, requests, and Google Drive.

Yuddhaa does not control Google's independent processing of such information.

Please review:

20. International Processing

Yuddhaa operates Sarva from India.

When you use Google Sign-In or Google Drive, information associated with those Google services may be processed or stored by Google in locations determined by Google.

Such processing is subject to Google's own terms and privacy practices.

21. Your Privacy Rights

Depending on where you live and which privacy laws apply to you, you may have rights concerning personal information processed by Yuddhaa. These may include:

Requesting access to personal information concerning you.
Requesting correction of inaccurate information.
Requesting deletion of personal information where applicable.
Withdrawing consent where processing is based on consent.
Objecting to or restricting certain processing where applicable.
Requesting information about how your information is handled.

You may submit a privacy request to:

main.yuddhaa@gmail.com

Some information is controlled directly by Google rather than Yuddhaa. For example, information stored in your Google account or Google Drive may need to be managed using Google's own account and privacy controls.

22. India and Applicable Data Protection Law

Yuddhaa operates from India and intends to handle personal data in accordance with applicable Indian privacy and data-protection requirements.

Where applicable, this includes the Digital Personal Data Protection Act, 2023 and rules or requirements that are legally in force and applicable to Yuddhaa and Sarva at the relevant time.

The specific rights and obligations applicable to an individual user may depend on the user's circumstances, the type of data involved, the processing activity, and the law in force at the relevant time.

Nothing in this policy is intended to limit rights that cannot lawfully be excluded under applicable law.

23. European Economic Area and United Kingdom Users

If you are located in the European Economic Area, the United Kingdom, or another jurisdiction with similar data-protection requirements, applicable law may provide you with additional rights.

Where such laws apply to Yuddhaa's processing, we will process personal information only for appropriate purposes and on a lawful basis available under applicable law.

Depending on the circumstances, applicable legal bases may include providing functionality requested by you, complying with legal obligations, pursuing legitimate interests that are not overridden by applicable rights, or obtaining consent where required.

You may contact us regarding applicable privacy requests at:

main.yuddhaa@gmail.com

24. California and Other U.S. State Privacy Rights

If you are a resident of California or another U.S. state with an applicable privacy law, you may have additional rights concerning personal information.

Sarva does not sell personal information and does not intentionally use personal information for targeted advertising.

You may contact us at main.yuddhaa@gmail.com regarding applicable privacy requests.

Because Sarva is primarily local-first and does not maintain a central database containing users' Password Store or Me Docs contents, some requests may need to be performed directly by the user on their device or through Google for information controlled by Google.

25. Children's Privacy

Sarva is a general-purpose utility and productivity application and is not specifically directed toward children.

Sarva does not intentionally seek to collect personal information from children for purposes unrelated to the application's functionality.

Google Sign-In is subject to Google's own account eligibility requirements and policies.

If you believe that a child has provided personal information to Yuddhaa in circumstances where applicable law requires us not to collect it, please contact:

main.yuddhaa@gmail.com

26. Device and File Access

Sarva may use Android and application file-storage capabilities necessary to provide features such as Password Store, Me Docs, backup, restore, and document/file handling.

File access is used to provide the functionality requested by the user and is not intentionally used for unrelated advertising, profiling, or behavioral tracking.

Sarva does not claim access to information merely because Android technically makes such information available. Access depends on the permissions, APIs, and functionality implemented by the current version of Sarva.

27. No Sale of User Data

Yuddhaa does not sell Sarva users' personal information.

Yuddhaa does not sell or provide Password Store or Me Docs contents to advertisers, data brokers, or advertising networks.

Password Store and Me Docs data is not used by Yuddhaa for advertising or behavioral profiling.

28. Changes to This Privacy Policy

We may update this Privacy Policy when Sarva's functionality, information practices, third-party services, or applicable legal requirements change.

When this policy is updated, we will update the "Last updated" date displayed at the beginning of the policy.

The current version of this Privacy Policy will be available at the privacy-policy URL provided for Sarva.

You should review this policy periodically to remain informed about how Sarva handles information.

29. Contact Us

If you have questions about this Privacy Policy, want to submit a privacy request, or believe that Sarva is handling information incorrectly, please contact Yuddhaa:

Yuddhaa
Privacy contact: main.yuddhaa@gmail.com