This policy covers the digital services Azarestan operates for its members, staff and partners, including the internal application ABD Assistant. Section 5 gives the specifics for ABD Assistant, including how it handles data received from Google APIs.
To provide and secure the services, to send notices the user has asked for or that the work requires (in-app, web push, Telegram, SMS), and to comply with law. We do not sell personal data and do not use it for advertising.
ABD Assistant is Azarestan's internal application for board meetings and minutes, resolutions, tasks, requests, calendar and reminders, with a voice and text assistant. Accounts are created by the system administrator. Connecting a Google account is optional.
Scopes requested when a user connects Google Calendar:
What we do with it. Events in the user's primary Google Calendar (title, time, location, description, participant names and Meet link) are copied into the user's calendar in ABD Assistant, and events created or changed in ABD Assistant are written to Google Calendar. Nothing else in the Google account is accessed. Board meetings, minutes and recordings kept in ABD Assistant are not sent to Google.
Storage and protection. The Google refresh token is stored encrypted (AES-256-GCM) in the application's database, on servers operated by Azarestan. Calendar copies are stored in the same database. All traffic uses HTTPS.
Who can see it. The user's calendar, including events that came from Google, is visible to the user and, under the application's access rules, to the user's office manager and to people the user has shared the calendar with. It is not visible to other users.
The assistant. When a user asks the assistant about their schedule, the relevant calendar entries (which can include entries that came from Google Calendar) are included in the request to the AI service Azarestan uses to produce the answer. We do not use them to train models.
Limited Use. Azarestan's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
Disconnecting and deleting. A user can disconnect Google at any time in the application's Settings (the token is revoked at Google and deleted from our database), or remove access at myaccount.google.com/permissions. Events already copied stay in both calendars after disconnecting; the user can delete them in either place, and the administrator will delete them on request. To request deletion, write to abd@azarestan.com.
We may update this policy; the date above shows the latest version.