Oursi

Legal

Privacy Policy

Effective date: September 17, 2026  ·  Last updated: September 17, 2026

Privacy at a glance

1. Who we are and the scope of this policy

This Privacy Policy explains how Vishal Sharma, operating as Oursi ("Oursi," "we," "us," or "our"), processes personal information when you use the Oursi Android application, related support channels, and our account-deletion process (together, the "Service").

Data controller / business: Vishal Sharma, operating as Oursi

Principal address: Hamirpur, Himachal Pradesh, India

Privacy contact: vs.official.200985@gmail.com

EU/EEA and UK representative: Not applicable. Oursi is offered only in India.

This policy applies to information we process as a controller or business for the Service. Oursi is offered only in India. Google and your mobile platform may process information independently under their own terms and privacy notices. This policy does not cover their independent processing.

2. Information we process

We follow a data-minimization approach: we process information needed to provide a private messaging service, secure it, meet legal obligations, and handle support or rights requests. The categories below describe the Service's production data model and enabled integrations.

Category Examples Source and visibility
Google sign-in and account data Google/Firebase account identifier, email address made available by Google, Google display name, profile-photo URL, Oursi internal user ID, generated display alias, username, account state, and account timestamps. Provided by you through Google Sign-In or generated for the account. Your actual Google name, Firebase ID, and email are not shown to other Oursi users. Your generated display alias, username, and optional profile photo may be shown only as described below.
Username lookup and connection data Exact username entered for lookup, lookup rate-limit records, connection requests, relationship status, participant IDs, and associated conversation ID. Provided when you look up a username or manage a connection. Oursi does not provide a public directory, name search, email search, contact-book discovery, recommendations, fuzzy search, or prefix search. An authenticated person who enters your exact username may receive only your safe profile projection: display alias, username, and optional photo.
Messages and conversation data Text-message content, sender and recipient IDs, message and conversation IDs, timestamps, delivery/read cursor data, message status, locally saved drafts, queued-send data, and conversation metadata such as the latest-message preview. Created by you or another participant. Text messaging is limited to accepted one-to-one connections. The other participant can see messages and related delivery/read status in the conversation. We do not support group messages, media attachments, or delete-for-everyone in the current service design.
Typing and notification data Short-lived typing state, app-installation ID, push-notification registration token, notification preferences, conversation mute state, and minimal notification routing IDs. Generated by your device and the Service when these features are enabled. A notification may display the sender's alias and message text only when previews are enabled; otherwise it uses a privacy-safe fallback. Push notifications are alerts, not proof of message delivery or reading.
Local device data A protected installation ID, locally cached account/profile data, conversation cache, message cache, draft, outbox, and synchronization records. Created on your device to support session restoration, offline use, and reliable syncing. Local data is cleared when you sign out or after a deletion request has been accepted, subject to a recoverable cleanup failure on the device.
Service, security, and support information Function request metadata, rate-limit and anti-abuse records, operational timestamps, error category, app/package and device/service data processed by Firebase, and information you send in a support or privacy request. Generated while the Service operates or provided directly by you. We design logs to avoid message bodies, authentication tokens, email addresses, and private provider payloads.

Information we do not collect for the Service

Oursi does not use advertising, cross-app behavioral tracking, engagement analytics, contact-book discovery, precise location, camera, microphone, photos, videos, audio recordings, call logs, SMS, payment information, or health information. We do not sell or rent personal information. If a future release changes these practices, we will update this policy and provide any legally required notice or consent before the new processing begins.

3. How and why we use information

We process the categories above for the following purposes:

Where privacy law requires a legal basis, we generally rely on: performance of our contract with you to provide the Service; our legitimate interests in operating a secure, reliable, and abuse-resistant messaging service; your consent for processing that requires consent, such as notifications where required; and compliance with legal obligations. You may withdraw consent at any time where processing is based on consent, but this does not affect processing already carried out lawfully.

4. When information is disclosed

We do not sell personal information or disclose it for cross-context behavioral advertising. We disclose personal information only in the limited situations below:

We may also use and disclose aggregated or de-identified information that does not reasonably identify you, subject to applicable law.

5. Security and messaging privacy

We use reasonable administrative, technical, and organizational safeguards designed to protect information. These include authenticated access, access-control rules, server-authoritative security-sensitive actions, input validation, rate limiting, secured local storage for the installation ID, TLS/HTTPS for data in transit, and Firebase platform encryption at rest for supported services.

Important: Oursi is not end-to-end encrypted. Firebase-authorized access controls and transport/storage encryption help protect the Service, but they do not mean that Oursi or its infrastructure providers are technically unable to access message content. Do not use Oursi for information requiring end-to-end encryption or emergency communications.

No method of storage or transmission is completely secure. We cannot guarantee absolute security. Keep control of your Google account and device, do not share your credentials, and contact us promptly if you believe your account or device has been compromised.

6. Storage and international transfers

The Service uses Google Firebase infrastructure. Cloud Functions for the MVP are configured for the Mumbai, India region (asia-south1). Other Firebase services may process or store information in the United States or other countries where Google and its subprocessors operate. In particular, Firebase states that its Authentication service operates from U.S. data centers and that many Firebase services use global infrastructure unless a specific location is selected.

If information is transferred outside India, we will use safeguards required by applicable law. You can ask for more information using the contact details below.

7. Retention and account deletion

We retain personal information only for as long as reasonably necessary to provide the Service, meet the purposes described in this policy, resolve disputes, enforce agreements, maintain security, and meet legal obligations. Retention depends on the type of information and its purpose; we do not use a one-size-fits-all period.

How to delete your account

You can request deletion in Oursi through Settings → Account Settings → Delete Account. The Service requires recent Google reauthentication before it accepts the request. Once accepted, a trusted, retry-safe server workflow marks the account as deleting and completes cleanup asynchronously.

Subject to technical and legal limits, account deletion removes or disables the Firebase identity mapping, releases the username claim, removes private account/profile fields, removes active-installation and notification data, and clears local credentials and cached app data. The account profile is replaced with Deleted user in retained shared history. Existing messages are retained for the other participant and may remain in that participant's conversation history; Oursi does not currently offer delete-for-everyone. If you cannot access the app, request deletion through vs.official.200985@gmail.com.

We may retain limited information after deletion where necessary for security, fraud prevention, legal compliance, dispute resolution, or to establish, exercise, or defend legal claims. Where deletion cannot be completed immediately, we will explain the applicable status if you contact us.

8. Your choices and controls

9. Your privacy rights

Subject to applicable Indian law, you may request information about our processing, correction, completion, updating, or erasure of your personal information, withdrawal of consent, grievance redressal, and any other right available to you. Oursi does not sell personal information or use it for cross-context behavioral advertising.

To make a request, email vs.official.200985@gmail.com with enough information for us to verify your account and understand the request. We may ask for information necessary to verify your identity and authority, and we may deny or limit a request where allowed by law. If we deny a request, reply to our decision with the subject line Privacy Request Appeal.

10. Children and minimum age

Oursi is not directed to children under 13 and is offered only in India. You must be at least 13 years old to use the Service. If you are 13 to 17 years old, your parent or lawful guardian must consent to your use of Oursi. Where applicable law requires verifiable parent or guardian consent before we process a child's personal information, Oursi will obtain that consent before processing the information. Until a compliant guardian-verification flow is available, a person under 18 must not create or use an Oursi account where such verification is required.

We do not knowingly process personal information from a child in breach of this section. If you believe that this has happened, contact vs.official.200985@gmail.com so that we can take appropriate action.

11. Automated decisions

We do not use message content for advertising profiles or make decisions that produce legal or similarly significant effects solely through automated processing. The Service uses limited automated controls such as authentication checks, exact-username validation, rate limits, authorization rules, duplicate prevention, and notification-preference checks to operate securely and reliably.

12. Changes to this policy

We may update this policy when our data practices, the Service, or applicable law changes. We will post the updated policy with a revised "Last updated" date and, when legally required, provide additional notice or obtain consent before a material change takes effect. We encourage you to review this policy periodically.

13. Contact us

If you have a privacy question, concern, complaint, or rights request, contact:

Vishal Sharma / Oursi Privacy Team
Hamirpur, Himachal Pradesh, India
vs.official.200985@gmail.com

If you are dissatisfied with our response, you may pursue any grievance or other remedy available under applicable Indian law.

Implementation transparency

This policy reflects Oursi's approved Android-first product design: Google authentication; Firebase-managed authentication, database, functions, messaging, and optional short-lived typing state; private exact-username discovery; accepted one-to-one text messaging; local-first cached data; and privacy-aware push notifications. It does not describe features that Oursi does not offer, such as advertising, contact matching, public profiles, media messaging, group chat, calls, E2EE, or a public iOS release.