Tappal · Collectorate, Kumuram Bheem Asifabad

Privacy Policy

Effective 14 October 2026

This policy explains how Tappal handles information in its Android, iOS, and desktop apps, the officer and administrator web platform, and the public website at tappal.network. Tappal is an official workspace provided for authorised officers of the Collectorate, Kumuram Bheem Asifabad, Telangana, India. Accounts are provisioned by the administration; the public cannot self-register.

Information we handle

Officer identity and access: name, employee identifier, phone number or email where provided, department, role, post, jurisdiction, work location or institution, account status, authentication details, device and session identifiers, and security or access logs.
Communications: messages, group membership and related metadata, files, photos, videos, audio, read receipts, typing indicators, and other content that users choose to send. Private Matrix rooms may use end-to-end encryption; room membership, delivery information, and other metadata are still processed. Official rooms and records may follow different access and retention rules.
Official work: tasks, assignments, forms, submissions, announcements, acknowledgements, calendar entries, documents, evidence, and audit history. A submission may contain personal information about other people when an officer enters it.
Optional device inputs: camera, microphone, selected photos or files, and location when a user grants permission and uses a feature that needs them, such as recording a voice note, sharing a location, or attaching field evidence. The app requests location while in use; it does not need continuous background location.
Technical information: app version, device and push tokens, IP address, browser or device information, connection events, errors, and service logs needed to operate and protect the platform.
AI assistant interactions: questions, responses, and relevant authorised workspace context when an officer uses TIRA or an administrator enables an AI-assisted workflow.

Why we use it

We use this information to verify and manage access; deliver chat, tasks, forms, and other official workflows; route notifications; maintain records and accountability; answer authorised AI-assistant requests; investigate security or service problems; and meet applicable administrative and legal obligations. We do not use Tappal as an advertising service.

Information is available to authorised participants, supervisors, and administrators according to their roles and the applicable workspace or conversation settings. Hostinger provides server infrastructure. Google Firebase Cloud Messaging and Apple Push Notification service process device tokens and notification delivery data; a notification may display limited task or message information on a device, depending on its settings. Encrypted chat notifications use a generic preview.

Where an AI feature uses an external provider such as OpenRouter, the request and relevant authorised context may be sent to that provider to perform the requested function. Administrator-enabled integrations may exchange authorised data with connected government systems or Google Workspace. We may also disclose information when required for lawful official administration or legal process. The public landing page loads fonts from Google, which may receive normal browser request information.

Security and encryption

We use HTTPS for network access, role-based permissions, authenticated sessions, audit records, and operational backups. Some private chats use Matrix end-to-end encryption and optional encrypted key backup. End-to-end encryption does not cover every feature, official room, metadata item, notification, or local backup. The app automatically keeps local message history for up to 365 days and 5,000 messages per room. In version 1.0.14 and later, message content in that archive is encrypted using a device-held key; routing metadata remains in local storage. This history can survive logout and is shown only for the signed-in account. Automatic OS and iCloud archive copying is disabled; copies made by earlier versions may remain in the user’s cloud account. Removing the app or losing the device key can make local history unrecoverable. A user-created Documents backup may be stored outside the app in plaintext; users should protect or delete that separate copy themselves. No internet service can promise absolute security.

Retention and deletion

We keep account and work information while needed to operate the official service and meet applicable recordkeeping, security, audit, or legal duties. Retention differs by record type and may be set by the administration. Deleting a local app copy or redacting a private chat message does not necessarily remove official records, other participants’ copies, server data, or backups immediately. Backups are removed under their operational rotation. We do not represent the private-chat disappearing-message timer as a guaranteed server retention period.

Your choices and requests

You can manage device permissions in iOS or Android settings, adjust available notification and chat privacy controls in Tappal, and contact the Collectorate to request access, correction, or deletion of your account information. Because accounts are issued for official work, an administrator may need to verify your identity and retain records that must remain under applicable duties. We will explain any data that cannot be deleted and why. Stopping use or uninstalling the app does not by itself delete a provisioned account.

Request account and data deletion

Email uv.marmat@gmail.com with the subject “Tappal account and data deletion request”. Include your name, department, and the phone number or email associated with your account; do not send a password or recovery key. The Collectorate will verify the request and coordinate account and associated-data deletion where permitted, explaining any official records it must retain. You may make the same request through your administrator.

Public website

The public tappal.network landing page does not offer account sign-up. Its server processes ordinary request data such as IP address, time, and requested page for delivery and security. The page uses Google Fonts; your browser may contact Google to load them. The landing page itself does not use advertising cookies.

Changes and contact

We may update this policy when the service or its data practices change. The effective date above identifies the current version. For privacy questions or requests, email uv.marmat@gmail.com. You may also contact the Collectorate by telephone at 08733-279401 or write to YTC Building / Collectorate, Jankapur, Kumuram Bheem Asifabad – 504293, Telangana, India.