Privacy

Control without unnecessary exposure

MitraSetu follows a privacy-by-design approach: collect and expose only what is needed for platform functionality, account security, and responsible safety.

Who can see your profile

Profile visibility can be PRIVATE, CONNECTIONS, or PLATFORM. PLATFORM means authenticated MitraSetu users—not the unrestricted public internet. Blocking applies in both directions to social visibility.

Discovery and connections

Username discovery is optional and off by default. Discovery respects profile visibility, active-account status, and blocks. Connection-request policy is separately controlled and defaults to the most restrictive option.

Private messages and voice recordings

One-to-one messaging in the current testing service is available between accepted connections. Messages and attachments are stored on our servers to deliver conversations and allow later access. They are not end-to-end encrypted. Access through the service depends on an active account, an accepted connection and current blocking rules.

Photo and video sharing is optional. You can select media from your device or choose Camera to take a photo or record a video. Camera access is requested when you choose capture; microphone access is used for audio in videos you choose to record. Captured media is uploaded when attached in the app, before you tap Send. Tapping Send shares it with your chosen recipient. Upload and deletion rules below also apply to this media.

Voice messaging is optional. Microphone permission is requested when you choose to record. In-app voice recording stops when the app goes into the background. When you submit a voice recording, its audio is uploaded and processed on our servers for delivery and playback by your chosen recipient. We do not use voice recordings for advertising, analytics or personalization.

You can delete messages you sent. This removes their text from the conversation and makes attached media unavailable through the service. Account deletion also removes the text of one-to-one conversations involving that account and makes its uploaded media unavailable. Limited reference records may remain.

Deleted media files are removed by a separate cleanup process rather than immediately when a message or account is deleted. Uploads not attached to a message or post become eligible for cleanup after 24 hours. Media under a preservation hold is excluded from cleanup for safety or legal preservation; access is restricted and holds have a review date. Existing infrastructure backups are handled as described below.

Group messaging in testing

When enabled in the testing service, group chats require an accepted invitation. Invitations expire after seven days. Accepting shares your username and membership with the group. Group messages, photos, videos and voice recordings are stored on our servers and are not end-to-end encrypted. New or rejoining members can access messages from their latest joining time onward.

Only current members can access group content. Admins manage group information, invitations and ordinary members; the owner manages admin roles and ownership. Admins can delete group messages. Removing or leaving a group revokes access through the service, but cannot erase copies someone already saved. Blocking a current member makes group content unavailable to the affected accounts until the block or shared membership changes. Group management and leaving remain available where authorized.

Unread counts use a stored read boundary. Sharing named group read receipts is off by default. Enabling it allows your own read state to be shown to the sender for new messages from that point onward; disabling it hides your shared receipts. Muting a group stops new queued group alerts where possible; an alert already delivered to a device cannot be recalled. Alerts contain generic text, not group names or message contents.

Deleting your account removes the text of group messages you sent and makes your uploaded media unavailable. Groups you still own are closed and their message text is removed; transfer ownership first if the group should continue. Other members' messages in groups you do not own remain. Minimal membership and message reference records may remain for integrity. Cleanup and preservation rules above apply to group media and group photos as well.

Use the in-app account report option to report an abusive member. Group message content is not automatically attached to an account report. Any context you choose to submit is sent for review.

Message alerts and unread status

Push notifications are optional and depend on your device notification permission. We use Expo push services and Google Firebase Cloud Messaging to deliver Android alerts. Delivery uses a device push token and limited routing information, including opaque sender and recipient account identifiers. The alert contains generic text rather than your message text or attachments. Tapping a new message alert opens the relevant conversation after account and access checks.

We store message read state to show unread counts for your account. Opening a conversation updates this state for messages through the loaded message boundary. One-to-one conversations do not show read or seen receipts to the sender.

Sessions and devices

Security records use privacy-minimized device and session information needed to recognize sessions and revoke access. The interface does not display raw authentication tokens, IP addresses, internal session IDs, device IDs, or fingerprints.

Notifications and safety records

Notifications contain narrow relationship events and redact or suppress actors when current privacy rules require it. Security events and tamper-evident audit records support platform integrity but are not publicly exposed; audit hashes and internal security details are never shown in member interfaces.

Account deletion and retained records

Use the Delete account option in app Profile or website Settings, or visit the MitraSetu deletion page. Sign in, enter your password and confirm DELETE. Ordinary profile, authentication, relationship and post-content data is removed from the live service. Circles you own close; other memberships end.

Limited account reference rows, safety reports submitted by others, security events, tamper-evident audit records, Circle history and financial evidence remain for security, fraud prevention and record integrity. Historical audit records may include former usernames. Details on reports submitted by you are removed. Access to retained records is restricted.

Deletion does not immediately erase existing infrastructure backups. Deletion must be reapplied before a restored backup is returned to service. Provider-held records and applicable retention periods require separate review before production release.

The current implementation does not add analytics, advertising trackers, behavioral fingerprinting, contact scraping, or location collection.

Grievance Officer and complaints

Grievance Officer: Muthuka Eswar Rao.

Email support@mitrasetu.in to submit a complaint about MitraSetu content, privacy, account issues, or platform decisions. Include the relevant username, post or report reference, a brief description, and a reply contact. You may also use the in-app post or account reporting options.

For child safety concerns, contact safety@mitrasetu.in. Never send passwords, login codes, or suspected child sexual abuse material as attachments.

Complaints are handled under applicable legal time limits. If you disagree with a response, reply with your complaint reference and explain the concern.