Whats91 app data deletion requests
The Whats91 Android and iOS apps use the same organisation account and central service data as the Whats91 web portal. Whats91 is operated by Wilford Technology. The organisation Owner, the first user who created its account, can request deletion of the organisation and its service data across both the portal and apps; this is not an app-only deletion request.
A team member who wants an individual work account removed should contact their organisation administrator. The organisation controls its staff accounts; a staff request does not authorise Whats91 to delete the whole organisation.
- Request: Email support@whats91.com with the subject “Whats91 app data deletion request”. Include the Owner's account email or phone number, the organisation name, and a clear request to delete the organisation account. No sign-in or installed app is needed.
- Verify: We match the request to the organisation and speak with its Owner to confirm authority and the intended deletion. Do not send a password, one-time code, API token, full payment-card number, or unnecessary identity document in the first message.
- Process: We acknowledge receipt within 48 hours. After Owner verification and confirmation, removal from active primary service systems takes up to two business weeks. We then email the Owner to confirm primary-system deletion.
- Legal hold: If a legal matter requires preservation, deletion pauses until written legal clearance is received. The processing period applies after verification and clearance.
Organisation account and active service data
The organisation's active account, user access, contacts, conversations, sent media, settings, and related service data are permanently removed from Whats91's live service systems. An active archive is not kept.
Further retention or condition: Primary-system deletion takes up to two business weeks after Owner verification and confirmation, subject to a legal hold.
Billing and plan records
Organisation-linked billing, usage, and plan records in the active service dataset are removed with the organisation. Its paid access ends when the organisation is deleted.
Further retention or condition: A legal matter requiring preservation pauses deletion until written clearance. Refund or billing-correction eligibility is governed separately by the Refund and Cancellation Policy.
Database backups
A backup created before primary-system deletion may still contain an older copy. Backups are not used as the active customer service dataset.
Further retention or condition: Rolling backups are automatically removed after seven days. The completion email confirms primary-system deletion; it does not mean every earlier backup has already expired.
Data stored in the mobile app
On its next connection, the app clears its local organisation data when the deleted organisation is no longer available.
Further retention or condition: An offline device may retain its local copy until it reconnects. Whats91 cannot promise immediate remote removal from an offline device.
Deletion request correspondence
Support emails and WhatsApp messages used to verify and document the Owner's request are retained as evidence of the instruction and its handling.
Further retention or condition: Normally retained for one year, then cleaned up; a legal hold may require longer preservation.
Firebase analytics and crash diagnostics
Firebase Analytics and Crashlytics records associated with an organisation ID are not currently removed by the organisation deletion workflow.
Further retention or condition: These records follow the applicable Firebase product retention settings. A specific period is not stated here until the configuration and provider behaviour are verified.
| Data category | What happens | Further retention or condition |
|---|---|---|
| Organisation account and active service data | The organisation's active account, user access, contacts, conversations, sent media, settings, and related service data are permanently removed from Whats91's live service systems. An active archive is not kept. | Primary-system deletion takes up to two business weeks after Owner verification and confirmation, subject to a legal hold. |
| Billing and plan records | Organisation-linked billing, usage, and plan records in the active service dataset are removed with the organisation. Its paid access ends when the organisation is deleted. | A legal matter requiring preservation pauses deletion until written clearance. Refund or billing-correction eligibility is governed separately by the Refund and Cancellation Policy. |
| Database backups | A backup created before primary-system deletion may still contain an older copy. Backups are not used as the active customer service dataset. | Rolling backups are automatically removed after seven days. The completion email confirms primary-system deletion; it does not mean every earlier backup has already expired. |
| Data stored in the mobile app | On its next connection, the app clears its local organisation data when the deleted organisation is no longer available. | An offline device may retain its local copy until it reconnects. Whats91 cannot promise immediate remote removal from an offline device. |
| Deletion request correspondence | Support emails and WhatsApp messages used to verify and document the Owner's request are retained as evidence of the instruction and its handling. | Normally retained for one year, then cleaned up; a legal hold may require longer preservation. |
| Firebase analytics and crash diagnostics | Firebase Analytics and Crashlytics records associated with an organisation ID are not currently removed by the organisation deletion workflow. | These records follow the applicable Firebase product retention settings. A specific period is not stated here until the configuration and provider behaviour are verified. |
Mobile app data and device access
- The app uses phone contacts on the device to help a user choose recipients. It does not sync the phone's entire address book to Whats91's servers for this purpose.
- Camera, photo-library, and microphone access let a user choose or create photos, media, and voice messages to send. Content sent through the service is stored with the organisation's service data.
- Location is accessed when a user chooses to send a current or live location. The app does not continuously track location in the background.
- Incoming-message notifications are delivered through Google Firebase. Message previews may appear on the lock screen; users can disable previews in their notification settings. Firebase Analytics and Crashlytics are also used for app usage and crash diagnostics.
Requests you can make
- Ask for information about personal data and processing where applicable law provides that right.
- Correct inaccurate or incomplete personal data.
- Request erasure where the purpose is complete and no retention requirement applies.
- Withdraw consent for future processing where consent is the basis.
- Raise a grievance about privacy, security, or an earlier request.
- Nominate another individual to exercise applicable DPDP rights in circumstances provided by law once that right applies.
How to submit a request
Email support@whats91.com with the subject “Privacy request”. Include your name, linked email or phone, organisation or Whats91 customer involved, requested right, and enough context to locate the information.
Do not send passwords, API keys, one-time codes, complete card numbers, or unnecessary identity documents in the first email.
Identity and authority verification
We may ask for proportionate information to verify identity, account authority, or a lawful representative. We will not disclose account or message data when the requester cannot be reliably connected to it.
Requests involving a Whats91 customer
If a business contacted you using Whats91, that business normally decides why your information is used. Contact it first. When Whats91 processes the data for that customer, we may forward the request and provide reasonable assistance without independently changing records unless authorised or legally required.
Response and limitations
We will acknowledge and respond within the period required by applicable law. A request may be limited where retention or disclosure is legally required, another person’s rights would be affected, identity cannot be verified, or the request is manifestly fraudulent or abusive.
Grievance and escalation
If you disagree with the response, reply with the original request reference and unresolved issue. Relevant DPDP rights require using the Data Fiduciary’s grievance process before approaching the Board. Other complaint routes may apply under other laws.
Contact Whats91
For questions, account notices, privacy requests, or legal correspondence, contact us directly. Include enough context to route the request, but do not send passwords, API keys, or one-time codes.