Your data

Data Deletion Instructions

Draft date: [[OWNER: EFFECTIVE DATE]]

Draft only — request handling is not yet configured. The supplied public support details appear below, but the owner must confirm that they are monitored and approved for privacy/deletion requests, define verification and response handling, and confirm that these instructions match the deployed product before publication or Meta configuration.

You may request deletion of BharatOS data by contacting bharatos.support@gmail.com · +91 8226036375. [[OWNER: CONFIRM CONTACT IS MONITORED AND APPROVED FOR PRIVACY / DELETION REQUESTS]]. Include the email address associated with your BharatOS account and identify which data or connected service you mean. Do not send your password, access token, verification code or payment details. We may ask for reasonable proof that you control the account before acting; the owner must define the verification method.

We aim to acknowledge requests within [[OWNER: RESPONSE TIME]] and complete eligible deletion within [[OWNER: COMPLETION TIME]], subject to applicable legal obligations and any disclosed backup-retention period. These are unresolved placeholders, not current service commitments.

Delete an optional app-data cloud snapshot

If you opted in to app-data sync, BharatOS can store an account-scoped snapshot in Supabase. The documented app includes a separate control to delete that cloud snapshot. Pausing sync alone does not delete the existing cloud copy. Use the in-app cloud-data deletion control for the signed-in account; if you cannot access the app or need help, contact the owner at the address above.

The snapshot can contain app content such as chats, companion chats, tasks, memories, artifacts, workflows, reminders, study material, goals and notes, up to the documented 5 MB snapshot limit. Free-text content may contain sensitive information or information about other people. The owner must publish the verified navigation steps and clarify any backup deletion period: [[OWNER: EXACT IN-APP MENU PATH AND BACKUP RETENTION]].

Google account and connected Google services

Google-backed BharatOS sign-in is separate from optional Gmail, Calendar and Drive connections. To stop future access, review and revoke BharatOS access in your Google account's third-party access settings. The owner must confirm the exact in-app disconnect and local-token removal behavior for the public release before adding further instructions.

Google controls data held in your Google account. A request to BharatOS does not itself delete your Gmail messages, Calendar events or Drive files. If you want those items removed, use the controls in the relevant Google service.

WhatsApp and Instagram cloud messaging

WhatsApp Business and Instagram Professional cloud messaging are not deployed or approved in the documented build, so there is no live BharatOS cloud messaging data set or public in-app deletion flow to claim at this time. If this service is launched, the planned design provides controls to pause, disconnect and delete the connected account's messaging data. The owner must update this page after live deployment and test deletion end-to-end.

The planned retention design redacts message/sender content after seven days and retains event, deduplication and status metadata for thirty days. This is not a verified live retention commitment. The owner must specify what happens to backups, provider records and deletion requests before enabling the service.

Other requests and account deletion

The project notes do not establish a complete BharatOS account-deletion workflow or final retention schedule. Contact bharatos.support@gmail.com · +91 8226036375 to request deletion of other personal information or ask a question. Before publication, the owner must state whether account deletion is supported, how identity is verified, what data is removed, what may be retained and why, and when backups expire.

Meta configuration note for the owner: this is a human-readable Data Deletion Instructions page. No Data Deletion Request callback endpoint is implemented in the documented project. Do not configure a callback URL unless a real, tested endpoint has been built and deployed.

Contact

[[OWNER: FULL LEGAL ENTITY NAME]]
bharatos.support@gmail.com · +91 8226036375
[[OWNER: POSTAL ADDRESS IF REQUIRED]]

Draft URL target: [[OWNER: FINAL DATA_DELETION_URL ON VERIFIED PUBLIC_DOMAIN]]. Privacy Policy · Terms · Home