MADHUMATI · DIAMOND JUBILEE

Privacy Policy

Policy updated: 16 October 2026

This Privacy Policy applies to the MADHUMATI application and its public support and privacy pages. It explains how information is handled when you use the app or contact the event administration team.

About the Application

MADHUMATI is an event information and participation app for authorised or invited participants of a Diamond Jubilee celebration. It provides event programmes and schedules, registration and attendance responses, family attendance information, venue information, and in-app announcements.

Access uses credentials supplied or managed by the administration team. There is no unrestricted public account sign-up. Signing in with authorised guest credentials can create a guest record linked to that app installation; guests then enter their registration details.

Information We Collect

How Information Is Used

Information is used to authenticate authorised participants, maintain sessions, recognise returning guest installations, manage registration and attendance, organise family participation, display relevant event information and announcements, record announcement read status, provide administrator account recovery, respond to support requests, and maintain app security and functionality.

Data Storage and Security

Backend services are hosted through Replit. Account, registration, attendance, announcement/read-status, session and recovery records are stored in Replit-managed PostgreSQL. Passwords are stored as salted PBKDF2-SHA512 hashes. The backend manages authentication itself; it does not use an external identity provider. Random bearer session tokens are checked against server-side hashes and expiry dates.

On native Android and iOS, Expo SecureStore stores the session token, guest-installation tokens and any tokens awaiting logout revocation, using Android encrypted storage backed by the Android Keystore or iOS Keychain respectively. Optional directory details use local AsyncStorage. Browser access uses browser-backed AsyncStorage for these authentication values. Temporary app data may also be held in memory while the app runs.

Access controls separate administrative functions from guest functions. These measures reduce risk, but no storage or transmission system can be guaranteed completely secure.

Third-Party Services

Expo SecureStore and AsyncStorage are local-storage libraries, not external authentication providers. Email sent to our support Gmail address is processed by Google’s email service. External services handle information according to their own privacy policies.

Data Sharing

Authorised administrators can view, search and export registration and attendance information to organise the event. Guest registration exports are Excel files received by the app administrator for event administration. Our policy is no onward sharing of those exports or guest details with other recipients. Administrators must protect and delete their downloaded copies in accordance with the retention policy below. Information is processed by the hosting, database and email providers as needed to provide the functions described above. Opening a map link or contacting support shares the information needed for that action with the relevant external service. Disclosure may also be necessary to comply with applicable legal obligations.

We do not sell users’ personal information. The current app does not include advertising or data-sale integrations.

Analytics and Tracking

The current app does not integrate advertising, behavioural analytics, cross-app tracking, or advertising-identifier SDKs. Its login uses bearer tokens rather than authentication cookies. The app-generated guest-installation token is used for registration continuity, not advertising or cross-app tracking. Announcement read records and operational logs are used for app functionality, not an advertising profile.

This privacy page contains no scripts, analytics, cookies, external fonts, or externally loaded images. External sites and hosting providers may independently process technical request information.

Location Information

MADHUMATI does not access or collect the device’s precise or approximate GPS location. Venue buttons open external Google Maps search links containing venue information. Any location access you permit within that external service is governed by its settings and privacy policy. A location voluntarily typed into the optional directory form is stored locally as described above; it is not obtained from device location services.

Push Notifications

In-app announcements remain available without push permission. On supported devices, push notifications are optional: you can decline the permission prompt, turn notifications off in the app where available, or disable MADHUMATI notifications in your device settings. Push alerts use Expo and APNs (iOS) or FCM (Android); they do not use OneSignal.

Lock-screen alerts contain only “MADHUMATI” and “New announcement available”, plus an announcement identifier used to open the announcements screen. Announcement content, profile, family, travel and contact details are not included in push payloads. Delivery depends on provider and device conditions and is not guaranteed.

Device registrations are linked to a server-side session hash, never a raw session token. Server-side sign-out revocation removes that session’s push registration and queued jobs. Expired or revoked sessions, inactive accounts, administrators and guests without completed registration are excluded from new sends. Offline sign-out revocation takes effect when the server receives it; a message already handed to a delivery provider cannot be recalled. Device settings can block alerts immediately.

Unregistering a device removes its push registration and related queued jobs. Account deletion also removes associated push records from the active database. Session expiry stops delivery but does not itself erase stored records; provider logs and recovery copies are subject to provider retention rather than immediate deletion by the app.

Data Retention

Organisation-controlled event records: within 7 days after the event is completed. Our retention policy requires the administration team to delete event participant account records and their associated registration, family, travel, meal, attendance and announcement-read information within this period. The same deadline applies to event details in administrator-held Excel exports and support correspondence. Deletion is administered by the organisation; the current app does not provide an automatic post-event purge. Requests for earlier account deletion can be made using the instructions below.

Provider-held copies have separate retention periods. Deleting an active application record does not immediately erase provider logs or historical backups. Replit documents 30-day deployment-log retention and production database recovery windows of up to 7 days on Core or up to 28 days on Pro/Enterprise, depending on the configured plan and settings. Resend documents 30-day email/log retention on Free, Pro and Scale, with custom options for Enterprise. These provider periods are not measured from the end of our event. We do not promise that these copies disappear within 7 days after the event. Provider settings and any legally required retention may differ; contact the administration team for details relevant to a deletion request.

See Replit log retention, Replit backup and recovery retention, and Resend retention information. Deleting event support correspondence also requires the administrator to remove mailbox copies; the app cannot remotely erase email-provider backups or files held on another device. Locally saved directory entries must be removed from the device separately.

Login sessions are valid for up to 30 days unless revoked earlier. Administrator password-reset links expire after 30 minutes and are single-use. Expiry invalidates access; it does not necessarily erase the stored record. Signing out clears the local session and requests server-side session revocation, with retry if connectivity is unavailable. Signing out does not delete registration, attendance, guest-installation identifiers, or locally saved directory details.

Access, Correction and Deletion

Request MADHUMATI account deletion

You can request deletion without signing in, reinstalling the app, or completing registration. This is a request to the administration team, not an automatic deletion button.

Email an account deletion request. If an email app does not open, copy illuminatistnov13@gmail.com into your email service and use the subject “MADHUMATI Account Deletion Request”. Include your registered name and registered contact detail or account identifier; say if registration was never completed. Do not send your password or verification codes.

An administrator monitors the request inbox daily. We will reply within two days of receiving your request and delete the verified account and its associated personal records from the active application database within two days of identity verification. Administrator-controlled exported copies containing your information will be cleaned up within seven days of identity verification. These are separate deadlines: active-database deletion does not mean all copies have already been removed.

The administration team may verify your identity before acting. Ask the team to confirm receipt, the expected completion time, and any information that must be retained with its reason and retention period. Contact the team using the support page if you need help identifying your account, including an administrator or officer account. Another active administrator must handle an administrator's account deletion after responsibility has been transferred.

Registered guests can view and edit their guest registration details under More → My Profile. Saving a profile updates the existing registration and does not change event-specific attendance responses.

To request access to your information, correction of inaccurate details, or deletion of your account or personal information, contact the administrator by emailing illuminatistnov13@gmail.com. Describe the request and provide enough information to identify your registration or account. Do not send your password or verification codes. We may need to verify your identity before acting on a request.

Only an administrator can delete a guest account; guests cannot delete their own accounts in the app. The administrator must confirm the permanent deletion. Deletion removes your guest identity (including its server-side installation identifier and travel details), registration (including contact, birth-date, meal and family details), attendance responses, announcement read records and all sessions from the active application database. It does not delete shared invitation credentials, administrator accounts, other guests or event announcements. Apple review accounts remain isolated from real participant accounts.

After successful deletion, the deleted guest’s sessions no longer work. Administrator deletion does not remotely erase remembered installation identifiers, cached profile data or locally saved directory entries on guest devices, downloaded administrator exports, or provider backups. Contact the administration team about those copies or if you cannot access your account. If you join again using an active invitation, you start as a new guest. Logout or deactivation alone does not delete your account.

Requests also cover guest identities created before registration was completed, officer accounts and administrator accounts. For those accounts, administrator deletion removes the selected identity, its sessions, password-reset records, attendance responses, announcement read records and any associated guest registration from the active database. Other participants, shared invitation credentials and event announcements remain.

On Android, use system Settings → Apps → MADHUMATI → Storage → Clear storage to remove local app data from that device; menu names vary by device. This signs you out and removes locally saved details. It does not itself delete your server account, administrator exports, copies on other devices or device/cloud backups. Do not sign in again with an invitation unless you intend to create a new guest identity.

Support emails and attachments, including administrator-controlled trash and copies, are deleted within 30 days after request completion. This short period allows follow-up questions about delivery or fulfilment to be resolved. A minimal deletion record containing the request reference, dates, outcome and any outstanding expiry is retained for up to 90 days after completion for accountability; it does not contain a copy of the deleted profile.

The active-database, export and support-mail deadlines do not promise erasure of service logs or provider recovery copies within those periods. Provider retention periods are not yet confirmed. Ask the administrator for the applicable period and reason, and for a final confirmation distinguishing completed deletion from copies still pending. Deleting an email from our mailbox does not establish that every provider backup has been erased.

Children’s Privacy

The app is intended for authorised event participants, rather than as a service directed at children. Participants may provide children’s names, attendance counts and ages for family event planning. Older guest registrations may retain a date of birth; the current registration form no longer asks for it. Parents or guardians should provide or authorise information about children and may contact us to request access, correction or deletion of that information. We do not use this information for advertising.

Changes to This Privacy Policy

This policy may be updated when app features or data practices change. The latest version and its effective date will be published on this page.

Contact Us

For privacy questions or support, contact the MADHUMATI administration team:

Email: illuminatistnov13@gmail.com
Phone: +91 87658 37477
Visit the public support page