Privacy Policy

Privacy Policy

Last updated: 14 November 2026. Operator: Azarestan Business Development Group and its subsidiaries ("Azarestan", "we"). Contact: abd@azarestan.com — No. 337, opposite Dafineh Museum, Mirdamad Blvd., Tehran, Iran.

1. Scope

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.

2. Data we process

  • Account data: name, username, title, mobile number and e-mail where given, and a salted password hash.
  • Data users enter or generate in a service: for example meetings, minutes, resolutions, tasks, requests, calendar events and notifications.
  • Technical data: sign-in and security logs and an audit trail of changes to sensitive data.

3. How we use it

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.

4. Sharing, retention, security and your rights

  • Sharing: only with service providers needed to run a service (hosting, notification channels, and the AI service named in section 5) and where the law requires.
  • Retention: data is kept while the account or the business purpose lasts; deleting an account deletes its personal data.
  • Security: access is limited by role and company, passwords are hashed, connections are encrypted and changes to sensitive data are logged.
  • Your rights: to access, correct or delete your data, write to abd@azarestan.com.

5. ABD Assistant and Google user data

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:

  • https://www.googleapis.com/auth/calendar.events — to read, create, change and delete events on the user's primary calendar, and to ask Google to create a Google Meet link for an online meeting created in ABD Assistant.
  • openid and email — only to show which Google account is connected.

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:

  • We use Google user data only to provide and improve the user-facing calendar synchronization and assistant features described here.
  • We do not sell Google user data and do not use it for advertising.
  • We do not use Google user data to develop, improve or train generalized AI or machine-learning models.
  • We do not allow people to read Google user data, except with the user's consent, to investigate abuse or security issues, to comply with law, or under the access rules above.

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.

6. Changes

We may update this policy; the date above shows the latest version.