Retention & Deletion

Retention criteria

• Workspace and user records: retained while needed to administer the service, provide authorized access and meet applicable security or legal obligations.
• Reporting history: retained for the reporting periods agreed with the institution, including historical comparison and reconciliation, until no longer needed or deleted following a verified request.
• Provider credentials: retained while the connection is maintained. Disconnection removes the corresponding saved credentials and selected-account links. Expiry or provider revocation can prevent use before local records are removed.
• AI questions, answers and evidence: stored on the server to support history and follow-up analysis. Limiting the visible conversation or closing a chat session does not delete its stored records. AI Analytics No blocks access; it does not erase previous conversations.
• Operational records and backups: retained according to security, troubleshooting, legal needs and the applicable hosting and backup arrangements. Exact schedules depend on the customer agreement and deployment configuration.

Disconnecting or revoking access

An authorized user can remove an integration in Connections, or revoke authorization at Google or Meta. Disconnection does not remove historical reporting facts or saved AI conversations. If authorization is revoked directly at a provider, the service may discover this at its next access check. Reporting history may remain until a separate deletion request is processed.

Permanently deleting a university

An authorized Aadhyant administrator can review and confirm permanent deletion of an eligible university in the university management screen. This removes the university and its associated records from the active application database, including saved reports, sync and audit history, saved connections, AI conversations, invitations, and user accounts belonging only to that university. Shared and platform accounts retain their other access; the deleted university association is removed. No restorable archive or deletion log containing the university identity is kept by this operation.

Workspaces archived under an earlier release still retain their records until permanent deletion is completed. Protected platform and pilot workspaces require separate operational review. Approval and AI access settings do not erase data. Hosting backups, server logs, external source accounts and previously exported files are outside the application deletion operation.

Requesting deletion or closure

Email info@aadhyant.co.in with the workspace name, your relationship to the institution and the data or account you want removed. Do not include credentials or student contact lists. We verify identity and authority, agree the scope, identify any contractual or legal retention requirements, and confirm the applicable deletion process and timing. A request by one user does not authorize deletion of another institution's or other users' records.

Copies in backups are handled under the applicable backup expiry schedule and recovery controls; deleting active records does not imply immediate erasure of every backup. Provider-side copies, including data already sent to an enabled AI service, are governed by that provider's account controls and retention terms and may require a separate request.

Questions about your configuration

Contact Aadhyant for the retention and backup schedule applying to your institution before agreeing a fixed deletion deadline. We do not promise automatic expiry or a universal deletion period that the service does not implement. See the Privacy Policy for data uses and sharing.