Arbitration Management System
Retention and erasure statement
Retention and erasure
| What | Kept | Then |
|---|---|---|
| The record of a reference (the timetable, the filings, the orders, the fees, the audit log) | Until the Tribunal's subscription is closed down | At the closing down the whole record is exported to the Tribunal's own Drive, where it remains the Tribunal's, and the database is removed; the system has no means of deleting a single reference |
| A party's portal access | Until three months after the award, or after the reference ends | The link stops working; the record is untouched |
| A remembered browser | Trusted for thirty days from its sign-in; the record of it kept with the record of the reference | Asks for a code again; the record of it is marked expired, and never deleted, so that each filing can be traced to the sign-in behind it |
| A sign-in code | Good for fifteen minutes | Void; a fingerprint of it, never the code, stays on the record of the message until the message is swept, thirty days after it was sent |
| The audit log | With the record; its oldest entries moved to an archive in the Tribunal's own database once the log grows past 50,000 entries | Never edited; leaves the log only for its archive; exported with the record to the Tribunal's Drive at the closing down (D-226) |
| The nightly copy of the record in the Tribunal's Drive | Overwritten each night | — |
| Firestore's point-in-time history | Seven days | Rolls off; removed with the database at the closing down |
| Firestore's daily backups | Fourteen days | Deleted by schedule; removed with the database at the closing down |
| The service's logs (Cloud Logging) | 180 days, in India, as the CERT-In directions of 28 April 2022 require | Rolls off; after the closing down, runs to the end of its 180 days |
| Messages the system sends | Thirty days after sending; ninety if one fails or is returned | Removed from the outbox; the audit log keeps that each was sent |
| Answered cards on the queue of decisions | With the record; the routine ones moved to an archive in the Tribunal's own database after six months | Never deleted by the system |
| The text of an order, on its card | While the card is open | Cleared when the card is answered |
| What Google may keep of what the system sends to the model | Up to ninety days, where Google's safety classifiers flag a request, unless Google has granted the Tribunal's project an exception | Deleted by Google |
| On suviQ's platform: the fingerprints of the office's addresses and of the addresses the parties' links go to, the reports of the Tribunal's daily jobs, the daily counts, suviQ's settings for the Tribunal, and the record of its setting up and the arbitrator's Google account, domain and project it names | For the life of the subscription | Deleted at the closing down, as its last step |
| On suviQ's platform: the subscription's licences, the payments, the invoices, the address, state and GSTIN the invoices are drawn on, the accounts of the office that open them, and the Tribunal's name and filing address | Eight years (the GST and income-tax record-keeping periods) | Kept through the closing down; deleted by suviQ by hand at the end of the eight years |
| On suviQ's platform: its audit of what suviQ did for the Tribunal (the subscription, the setting up, the versions, the closing down) | For the life of the subscription, and eight years after it | Every email address in it is taken out at the closing down; the rest is deleted by suviQ by hand with the invoices |
| On suviQ's platform: the fingerprints of an address a party signs in with and of the code sent to it, and the times at which codes were asked for that address | The code is good for fifteen minutes | Removed by the daily sweep once an hour has passed after that, and so kept not more than about a day; a code sent for the Tribunal, at its closing down |
| On suviQ's platform: its logs, which record each party's personal link in full, its access token included; and the alerts the Tribunal's system sends to suviQ's address when something fails, unless the Tribunal's alerts are set to go to another address | The logs, 180 days, in India (Mumbai) from 29 September 2026, those written before that day in Google's global location; the alerts, twelve months from their receipt | The logs roll off; the alerts are deleted by suviQ at the end of their twelve months |
Erasure on request. A person who asks the Tribunal to erase information about them is answered by the Tribunal. The Tribunal may be bound to keep the record of the reference (for the award, a challenge, or enforcement), and says so where it declines. Where it agrees, the Tribunal corrects a field on its Corrections screen, and a document it withdraws from the record stays in the reference's folder, marked as withdrawn. The system has no means of deleting a single reference; at the closing down the whole record is exported to the Tribunal's Drive, and what the Tribunal then keeps there is for the Tribunal to delete. suviQ answers any question about its own processing at ams@suviq.ai.
Offboarding. When a subscription ends, suviQ ends it, so that nothing opens and nothing is sent but the arbitrator's own warnings that the subscription has ended and of the Award Clock, and exports the whole record to the Tribunal's own Drive, as a workbook and as one file for each table. The Tribunal's administrator then runs the closing-down command suviQ provides, which removes from the Tribunal's project the system, its daily jobs, its database and backups, its key and account, and the permissions the setting up granted, suviQ's among them; the system's logs run to the end of their 180 days; and the administrator revokes the system's delegation in the Google Admin console. The documents in Drive, the export and the nightly copy are the Tribunal's and stay. At the closing down's last step, suviQ's platform deletes what it keeps of the Tribunal but its licences, payments and invoices, the accounts of its office that open them, its name, filing address and dates, and its audit of what was done, from which every email address is taken out.
Set, 24 September 2026: the 180-day retention on the Cloud Logging buckets of the platform and of the dev service (the default is 30 days), and in the setup and recovery scripts every new customer is provisioned with.
Moved, 29 September 2026: the platform's logs, into a bucket in India (Mumbai) kept 180 days; the entries written before that day stay in Google's global location until their 180 days run out.