Astrid AI Assistant Desktop Application
Retention Schedule for Personal Use
When Astrid AI Assistance is under personal license, Astrid assumes the role of a Data Controller, individual users are data owners, and the following data retention schedule is used:
| Data Subjects | Subsets | Retention Period | Reason for keeping |
|---|---|---|---|
| MacOS App Users | Email address | 1 year after users leave the products (i) or when owners (ii) request deletion | User login, password reset, PII deletion confirmation/cancellation, sending coaching and feedback |
| Calendar meeting names and time | immediately after the day, data never leave users’ laptop | For product functionalities | |
| Users’ application setting eg: goals, received language, etc | 1 year after users leave the products (i) or when owners (ii) request deletion | For product functionalities | |
| Scoring, performance analysis | 1 year after users leave the products (i) or when owners (ii) request deletion | For app functionality and Quality Assurance (QA) purposes | |
| Voice recordings and transcripts | 1 year after users leave the products (i) or when owners (ii) request deletion | For Quality Assurance (QA) purposes and for continuous services improvement | |
| System logs and application performance reports that are not needed for app functionalities | Automatic deletion after 90 days | For Service Level Agreement (SLA), monitoring, and customer supports | |
| IP address, device locales and other non-PII device information, eg: Mac OS version, etc | 1 year after users leave the products (i) or when owners (ii) request deletion | For Service Level Agreement (SLA), monitoring, and customer supports | |
| Application-user interaction events, eg: notification shown, pop up displayed | 1 year after users leave the products (i) or when owners (ii) request deletion | For product continuous improvement, monitoring, and customer supports |
(i): leave product = paid subscription has ended, or no recording activities for 1 year within free-license. (ii): owner = lawful data owner as defined by GDPR.
Retention Schedule for Commercial Use
When utilizing Astrid for commercial objectives, Astrid assumes the role of the Data Processor, while the customer takes on the role of the data controller. The specifics concerning data retention, along with other related facets, are governed by the Data Processing Agreements (DPA) established between the two parties. These agreements provide a clear framework for how data is managed, stored, and protected, ensuring both parties adhere to the agreed-upon guidelines and regulations. This arrangement ensures a smooth and efficient data processing operation, with each party understanding and fulfilling their respective roles and responsibilities. In the absence of a DPA, the default schedule is implemented.
Astrid AI Assistant Platform
When utilizing Astrid for commercial objectives, Astrid assumes the role of the Data Processor, while the customer takes on the role of the data controller. The specifics concerning data retention, along with other related facets, are governed by the Data Processing Agreements (DPA) established between the two parties. These agreements provide a clear framework for how data is managed, stored, and protected, ensuring both parties adhere to the agreed-upon guidelines and regulations. This arrangement ensures a smooth and efficient data processing operation, with each party understanding and fulfilling their respective roles and responsibilities. In the absence of a DPA, the default schedule is implemented.
Default Retention Schedule
| Data | Retention Period | Reason for keeping |
|---|---|---|
| Scoring, performance analysis | 1 year after users leave the products (i) or when owners (ii) request deletion | For app functionality and Quality Assurance (QA) purposes |
| Voice recordings, associated metadata, and transcripts | 1 year after users leave the products (i) or when owners (ii) request deletion | For Quality Assurance (QA) purposes and for continuous services improvement |
| System logs and application performance reports that are not needed for app functionalities | Automatic deletion after 90 days | For Service Level Agreement (SLA), monitoring, and customer supports |
| Application-user interaction events, eg: notification shown, pop up displayed | 1 year after users leave the products (i) or when owners (ii) request deletion | For product continuous improvement, monitoring, and customer supports |
(i): leave product = paid subscription has ended, or no recording activities for 1 year within free-license. (ii): owner = lawful data owner as defined by GDPR.
Astrid School Product
Retention Schedule for Personal Use
Astrid’s School product includes Astrid Junior mobile App & Astrid Teacher platform. When Astrid AI Assistance is under personal license, Astrid assumes the role of a Data Controller, individual users are data owners, and the following data retention schedule is used:
| Data Subjects | Subsets | Retention Period | Reason for keeping |
|---|---|---|---|
| Mobile App Users | Full name | 1 year after users leave the products (i) or when owners (ii) request deletion | Display reports to teachers in Astrid Teacher Platform |
| Email address | 1 year after users leave the products (i) or when owners (ii) request deletion | User login, password reset, PII deletion confirmation/cancellation, SSO user correlation | |
| School and class name | 1 year after users leave the products (i) or when owners (ii) request deletion | Display reports to teachers in Astrid Teacher Platform | |
| Scoring, performance analysis and exercise assessment | 6 years after users leave the products (i) or when owners (ii) request deletion | For mobile app functionality, for reporting to teachers in Astrid Teacher Platform, and service improvement | |
| Voice recordings | 6 years after users leave the products (i) or when owners (ii) request deletion | For continuous services improvement | |
| Device locales | 1 year after users leave the products (i) or when owners (ii) request deletion | For app functionality (for communication) | |
| Users’ activity such as book content and time stamp | 1 year after users leave the products (i) or when owners (ii) request deletion | For mobile app functionality and for reporting to teachers in Astrid Teacher Platform | |
| System logs and application performance reports that are not needed for app functionalities | Automatic deletion after 90 days | For Service Level Agreement (SLA) and monitoring | |
| Emails and push notification | Automatic deletion after 90 days | For app functionality (for communication, if applicable by subscription) | |
| Insight platform users (eg. teachers, parents) | Name and email address | 1 year after users leave the products (i) or when owners (ii) request deletion | For app functionality |
| School name | 1 year after users leave the products (i) or when owners (ii) request deletion | For app functionality, manage subscription and contracts. |
(i): leave product = no learning activities for 1 month after subscription has ended, or other reasonable triggers for leaving the product. (ii): owner = lawful data owner such as end users as defined by GDPR.
Retention Schedule for Commercial Use
When utilizing Astrid School Products for commercial objectives, Astrid assumes the role of the Data Processor with an optional Data Controller role on certain data subsets. The customer takes on the role of the data controller. The specifics concerning data retention, along with other related facets, are governed by the Data Processing Agreements (DPA) established between the two parties. These agreements provide a clear framework for how data is managed, stored, and protected, ensuring both parties adhere to the agreed-upon guidelines and regulations. This arrangement ensures a smooth and efficient data processing operation, with each party understanding and fulfilling their respective roles and responsibilities. In the absence of a DPA, the default schedule is implemented.