This Privacy Policy explains how KametiBook (“we”, “us”, or “our”) handles information when you create an account, participate in a kameti group, record contributions, communicate with other users, or use reports and notification features.
KametiBook is a record-keeping and coordination application for private kameti groups. It is intended for adults aged 18 and over.
For privacy questions or requests concerning your information, contact: darpanchelani12@gmail.com
Information we collect
Account and profile information
We process information you provide when registering, signing in, or maintaining your account. This can include:
- Full name and username.
- Email address and phone number.
- City.
- Account identifier.
- Profile image information, if already provided or associated with your sign-in profile.
- Sign-in provider and verification status.
- Account creation, update, and sign-in timestamps.
Firebase Authentication processes the credentials needed for email/password or Google sign-in.
We do not require your banking password, payment card security code, or online banking login credentials.
New profile-photo uploads are currently disabled.
Kameti and financial records
We process information entered by organizers and members to operate their groups, including:
- Group details and membership.
- Contribution amounts and due dates.
- Payment status and recorded payment methods.
- Payment notes.
- Existing proof references, if present.
- Receiver allocations and payout records.
- Bids and allocation results.
- Ledger entries and adjustments.
- Report history.
New file attachments are currently disabled. Users can still record payment amounts, methods, and notes.
These records help participants coordinate their arrangements. A payment status or existing receipt is not independent verification that money has been transferred.
Messages, disputes, and other content
We process content you submit through the app, including chat messages, disputes, user reports, and information recorded in audit history.
Organizers may also enter information about members. Depending on the fields used, this may include contact information, optional identity information, and notes.
Only provide information that you are authorized to share. Avoid including unnecessary CNIC numbers, bank account details, passwords, or other sensitive information in messages, notes, or reports.
Device and notification information
The app can register device notification tokens with Firebase Cloud Messaging.
Notification delivery depends on device permissions and the notification services configured for the app. Automatic background reminders are not currently provided by a deployed server worker.
The app requests notification permission where required by your device. You can manage notification permissions through your device settings.
Your city is entered manually. The app does not request access to your contacts, SMS messages, call history, or precise device location.
How we use information
We use information to:
- Create, authenticate, and maintain accounts.
- Find and link members.
- Operate kameti groups.
- Record contributions, payment methods, and payment notes.
- Review existing payment information.
- Coordinate receiver allocations.
- Maintain ledgers and financial history.
- Generate reports and account exports.
- Support messages and available notification features.
- Investigate disputes, abuse reports, and security incidents.
- Review and fulfil support and deletion requests.
- Maintain the service.
Information visible to other users
KametiBook is designed for collaboration between group participants.
Organizers and members can access information according to their roles and the app’s permissions. This may include membership details, contribution records, payment status, existing proofs, messages, and ledger information.
Other signed-in users may discover your profile through account search. Account discovery can expose profile and contact fields. Available privacy settings do not necessarily hide every field used in account discovery.
Consider what you share with organizers, members, and other users before entering personal or financial information.
Service providers and disclosures
We use Google Firebase services for authentication, database storage, and messaging. New file uploads are currently disabled.
These providers process information needed to deliver their services. Depending on their infrastructure and configuration, information may be processed outside your country.
We may disclose information where required by applicable law or a valid legal request, or when necessary to investigate fraud, abuse, or security incidents.
We do not sell personal information. The app does not currently serve advertisements.
Usage analytics
Usage analytics is disabled by default in the current app configuration.
The app includes an integration with PostHog. If enabled in a release, it can process account identifiers, profile name, username, city, account role and status, account creation time, screen views, and usage events for product analytics.
Session replay is disabled.
Any change that enables analytics must be reflected in the applicable privacy disclosures and the app’s published data declarations.
Photographs, files, and permissions
New file attachments and profile-photo uploads are currently disabled.
Upload controls do not open the camera or image picker in the current app configuration. Earlier records may contain file references or profile images; linked personal copies are reviewed during deletion.
Reports can still be generated, saved, printed, or shared at your request. Share only with recipients you intend to receive the information.
Data storage and security
Cloud services use encrypted connections to transmit information. Access rules restrict access to cloud records according to account and group permissions.
No storage or transmission system can guarantee absolute security.
Protect your sign-in credentials, secure your device, and contact us if you suspect unauthorized account access.
Retention and account deletion
While your account is active, we store information needed to provide the service.
You can request deletion through:
Profile → Security Center → Request account deletion
You can also email: darpanchelani12@gmail.com
Save the reference shown when you submit an in-app request.
Manual processing
Support reviews and processes deletion requests manually.
Submitting a request does not immediately delete your account. Account deletion is not automatically processed in the background.
Support verifies account ownership and confirms the consequences before performing cleanup.
Information removed during cleanup
Following verification and confirmation, support removes:
- Your sign-in account.
- Your private and public profiles.
- Your username reservation.
- Profile files, if present.
- Linked personal payment and allocation records.
- Legacy proof files associated with those records, if present.
- Messages and identified copies of your account information.
- Shared conversations and cached reports where necessary to remove linked personal information.
Group totals without personal details may remain.
We do not intentionally retain personal shared records after cleanup.
Groups you organize
A group you organize passes to an existing active co-organizer. If none is available, the group closes.
You do not need to close a group before requesting deletion.
Requests made under an older deletion policy require renewed confirmation of these consequences.
Temporary security information and finalization
A temporary security lock containing the account ID has a two-hour access-revocation window. This prevents old sessions from recreating deleted data.
Once that window has elapsed, support manually finalizes the request and removes the lock and the request record.
Finalization is manual. The two-hour window is not a promise that the complete request will automatically finish after two hours.
Identifying support correspondence is removed after resolution.
Processing failures and updates
If cleanup fails, support must resolve the failure and retry.
Submitting a request is not confirmation that deletion is complete. Contact support for an update or confirmation if your request is delayed.
Recovery versions and external copies
Database recovery versions may persist for up to one hour after removal from the active database. This does not keep your account active or make deleted records available through the app.
Copies previously exported or retained by other people are outside our control.
Deleting an account does not settle or cancel financial commitments between participants.
Exported and externally shared information
If you export a report or share information outside the app, the recipient receives a separate copy.
We cannot recall copies already downloaded, printed, forwarded, or otherwise retained by other people.
Your choices and requests
Depending on the feature, you can:
- Edit your profile.
- Manage notification preferences.
- Change device notification permissions.
- Use available privacy settings.
- Export account information through Security Center.
- Request account deletion.
You can also contact us to request access to, correction of, or deletion of your personal information, or to raise a privacy concern.
Available rights may depend on your location and applicable law.
Do not include passwords, banking credentials, or complete identity documents in your request.
Children
KametiBook is intended for adults aged 18 and over.
If you believe a child has provided personal information through the service, contact us so we can investigate and take appropriate action.
Changes to this policy
We may update this policy when the app or our data practices change.
The last-updated date identifies the current version. We will communicate material changes before they take effect.
Contact
For privacy questions, support, or requests concerning your information:
KametiBook Email: darpanchelani12@gmail.com