On this page
Who we are and what this policy coversInformation we collectHow we use informationSecurity, encryption and history recoveryWho receives informationYour device permissions and choicesHow long information is keptAccess, correction, deletion and other rightsInternational use and transfersAdults only and child safetyCookies and local device storageContact and changes to this policyClear information. Informed choices.
We collect information to deliver the features you choose. Permissions, sharing choices and account controls matter. Our current server-managed recovery system can recover eligible content; it is not exclusively device-only end-to-end encryption.
01Who we are and what this policy covers
SajPe Chat is operated by MK Tech IT Solution Private Limited, India. This Privacy Policy explains how we handle personal information when you use our Android application, web application, messaging, voice and video calls, groups, channels, meetings, status updates and related support services.
The company is responsible for the personal information processed to operate these services. Channel owners, group administrators, businesses and other participants may independently use information you share with them. Their own activities and any third-party service you open are not governed solely by this policy.
Our contact details appear at the end of this policy. You can read this page without an account or an app installation.
02Information we collect
| Information | When and why it is processed |
|---|---|
| Account and sign-in details | Your mobile number and country code, display name, optional email, username, profile photo, account identifiers, verification records and authentication/session information. We use these to register you, authenticate access, recover access and maintain your profile. PINs and passwords are stored as hashes; verification codes are short-lived. |
| Messages and shared content | Messages, photos, videos, documents, voice notes, captions, replies, reactions, polls, events, status updates and content you send to support. We process content and delivery/read metadata to provide the conversations and sharing features you choose. |
| Groups, channels and meetings | Memberships, roles, permissions, invitation tokens, moderation actions, meeting participation and call-related identifiers, timing and connection information. Public channel content is visible to the audience permitted by that channel. |
| Contacts you allow us to use | When you allow contact discovery, names and phone numbers are read from your device. Phone numbers are sent to our server to match registered SajPe users. Names and selected contact labels may be saved when you save contacts. Other people’s contact details should only be shared where you are entitled to do so. |
| Location you choose to share | Approximate or precise coordinates when you send a location or start live-location sharing. An active live-location session may continue sending updates while the app is in the background until it expires or you stop it. Location is processed on our server and shown to authorized conversation participants. |
| Camera, microphone and screen sharing | Camera images, microphone audio and the screen or window you choose to share are processed when you capture media, make calls or join enabled meeting features. Screen capture requires the device’s capture approval. Shared content can reveal information visible on your screen. |
| Device, network and diagnostic information | IP address, app/browser and operating-system version, device/session or installation identifiers, push notification tokens, error categories, code stack coordinates, connection status and performance information. These help deliver notifications, investigate faults, secure sessions and prevent misuse. |
| Optional linked accounts and correspondence | If you use Google sign-in or an authorized SajPe Community integration, we receive the identity/profile details needed to link your account. We also process the information you send in support, privacy, safety or deletion requests. |
03How we use information
We use information to provide and maintain the features you request; identify recipients and registered contacts; deliver messages, calls and notifications; manage memberships and permissions; enable the supported history-recovery flow; respond to requests; and keep the service reliable.
We also use limited information to detect spam, fraud, unauthorized access and prohibited activity, investigate reports, enforce our Terms and comply with applicable legal obligations. We do not use the current app release for targeted advertising or sell personal information. We do not read your SMS inbox or WhatsApp message inbox to obtain verification codes; you may type, paste or use supported device autofill/consent features.
Where a privacy law requires a legal basis, processing necessary to supply your requested service is based on performance of our contract; optional device access and other consent-based features depend on your consent where required; security, fraud prevention and service administration may rely on legitimate interests; and legally required processing relies on legal obligations. Where consent is required, you may withdraw it for future processing.
04Security, encryption and history recovery
We use HTTPS for connections to our service, access controls and encrypted storage for sensitive credentials and recovery key material. Device/browser storage can contain session data, cached content and cryptographic material needed to operate the app.
The current account-managed history-recovery implementation stores encrypted recovery keys on our server. Our service can use those keys to recover eligible message history after authorized login. This means that the recoverable service is not exclusively device-only end-to-end encrypted, and we do not promise that only the sender and recipient can technically decrypt every message.
Group/channel posts, support conversations, account data, live location and operational metadata are processed by the service and should not be assumed to have the same protection as a device-only encrypted conversation. A feature that offers different security properties should explain them before use.
No internet service is completely secure. Protect your device, PIN, email account and verification codes. We never need you to send a password, PIN or OTP in a support or privacy request. There is currently no promise of automatic daily email backups; any backup/export feature is governed by the feature that is actually offered and selected.
05Who receives information
Recipients and participants receive the content and profile information needed for the conversations, calls, channels, groups or meetings you join. Their devices may save, forward, copy, record or screenshot what you share. Removing a message or closing your account cannot recall copies already held by other people.
Service providers process information needed to operate the service. These may include our hosting/network infrastructure, Google/Firebase Cloud Messaging for push delivery, Interakt and WhatsApp/Meta for WhatsApp verification codes, the SMTP/email provider configured for email verification, Google for optional sign-in, and the configured real-time calling/meeting infrastructure using LiveKit/WebRTC. The exact provider used can depend on the feature and deployment. A provider receives only information relevant to its role; its own policies also apply to its independent processing.
Authorized personnel may access information where needed to provide support, operate recovery, administer the service or investigate a report. We may disclose information when required by applicable law or valid legal process, to address an urgent safety threat, or to protect users and the service. In a lawful corporate restructuring or transfer, information may transfer subject to appropriate safeguards and notice where required.
06Your device permissions and choices
| Permission or feature | Your control |
|---|---|
| Contacts | Used to find registered people and choose contacts. You can deny or revoke access and enter numbers manually. |
| Camera and microphone | Used for capture, voice messages, calls and meeting features you activate. Revoke access in device settings when you do not want these features. |
| Location | Used for location/live-location sharing you start. Stop an active share in the conversation or revoke location access. Live-location features may use a visible foreground service while active. |
| Notifications, full-screen calls and overlay access | Used for message alerts, ongoing call/meeting controls and incoming-call presentation. Message previews and caller/sender details may appear on the lock screen. Control visibility in your notification settings. Availability depends on OS permissions and device settings. Overlay access is optional and used for calling presentation, not advertising. |
| Files, photos and saved downloads | Used when you choose a file, take a photo or save an attachment. Older supported Android versions may request storage permission; newer versions can use system pickers and save dialogs. |
| Bluetooth, audio routing and foreground services | Support headsets, connected-call audio, active calls/meetings, screen sharing and active live-location sessions. A foreground-service notification can remain while a feature is running. |
| Screen sharing and device security | Screen sharing uses the system’s approval flow. Any supported biometric/device-lock check is performed by the device; the app does not receive or store your raw fingerprint or face template. |
07How long information is kept
Account details and conversation records are kept while needed to provide your account, deliver shared history and operate the service, unless an applicable deletion or retention rule requires otherwise. Ordinary chat history does not have a single fixed automatic deletion period. A disappearing-message or status timer controls ordinary feature visibility and must not be treated as proof that every server, backup or recipient copy is instantly erased.
Sign-in OTPs are normally valid for five minutes; profile email-verification codes may have a separate short validity window. Diagnostic logging currently uses rotation windows of approximately 14–30 days, depending on the diagnostic stream. Authentication, security, moderation and support records may be retained longer where needed to investigate misuse, resolve a request, protect legal rights or meet a legal requirement.
The in-app account-closing action deactivates and de-identifies the account, revokes its sessions, removes profile/sign-in credentials and removes group memberships as described in that flow. Shared messages and certain associated operational or recovery records can remain. To request review and deletion of associated personal data, use the public Account deletion page or contact us. We assess what can be removed or anonymized and explain any legitimate reason for retention.
We do not claim that account closure instantly removes all data from every system. Recipient-held copies and records that another participant is entitled to retain may remain. If a backup or archive exists, deletion may be completed through its ordinary replacement cycle unless a legal preservation duty applies.
08Access, correction, deletion and other rights
You can edit supported profile fields, control visibility and notifications, stop optional sharing, revoke device permissions and manage available account-security settings. Where offered, the account-information export provides a copy of supported account data.
Depending on where you live and which laws apply, you may have rights to access, correct, delete or obtain a copy of your personal information; restrict or object to certain processing; withdraw consent; or raise a complaint with your local data-protection authority. These rights may be subject to identity verification, lawful exceptions and other people’s rights.
For a request, write to contact@mktechitsolution.com or use the Account deletion instructions. Tell us which right you want to exercise and enough information to locate your account. Do not send passwords, PINs, OTPs or unnecessary identity documents. We may ask you to verify ownership through an appropriate secure method. We respond within applicable legal time limits and explain any permitted extension or refusal.
09International use and transfers
MK Tech IT Solution Private Limited is based in India, and SajPe Chat is intended to be available internationally subject to the regions enabled by the service. Your information may be processed in India and in locations used by our infrastructure and service providers. Privacy laws in those locations may differ from those where you live.
Where applicable law requires safeguards for a cross-border transfer, we are responsible for applying the required lawful transfer arrangement. This notice does not waive your mandatory local rights or claim that a particular transfer agreement or certification exists where it has not been put in place.
10Adults only and child safety
SajPe Chat is intended for people aged 18 or older. Do not register or use the service if you are under 18. We do not knowingly seek to collect personal information from children. If you believe a child has an account or that child exploitation is occurring, contact contact@mktechitsolution.com so the issue can be investigated and appropriate action taken.
Child sexual abuse and exploitation, grooming, sexual solicitation of minors and related content are prohibited. Our public Child safety standards explain reporting options. Do not forward suspected illegal material in an ordinary email; report the account, link and relevant context so appropriate handling can be arranged.
11Cookies and local device storage
The website/app uses session cookies and local storage for sign-in, request security, preferences, cached data and feature state. Push delivery also uses device registration tokens. Clearing browser/app data can remove locally stored history, preferences or key material and can require a new login or supported recovery.
The current release does not use an advertising cookie banner to obtain permission for tracking advertisements. If non-essential analytics or advertising processing is added later, this policy and any consent choices will be updated as required before that processing begins.
12Contact and changes to this policy
Privacy and account-data contact: contact@mktechitsolution.com. Postal address: MK Tech IT Solution Private Limited, Shop Nos. 18–19–20, First Floor, Balaji Market, Opposite Indu Hospital, Khemi Sati Road, Jhunjhunu, Rajasthan 333001, India.
We update this policy when the service or legal requirements change. The date and version appear at the top of the page. Material changes will be communicated through an appropriate in-app or website notice, and fresh consent will be obtained where applicable law requires it.