This is a translation for convenience. The legally binding version is the one in Hebrew. If the translation and the original differ, the Hebrew text prevails.
Sign in with Google
- Information access is requested to
- Email address and basic profile shown by Google when signing in.
- Why RBM Solutions uses it
- Identifying the user, opening an RBM Solutions account or signing in to an existing account.
- When the permission is requested
- When the user clicks the sign in with Google button on the sign-in screen.
- Scopes
- openid · email · profile
- What is stored
- RBM Solutions keeps the user's email address and display name in the system. The Google sign-in token is not stored in the database by RBM Solutions.
- Token storage
- The user's session is kept as a NextAuth JWT cookie; no Google refresh token is stored for sign-in.
- Deletion
- Account deletion can be requested through the privacy address. Deletion is subject to legal retention obligations and required operational records.
Google Calendar
- Information access is requested to
- A basic list of calendars to choose from, and reading, creating, updating and deleting events in the connected calendar according to the sync mode chosen.
- Why RBM Solutions uses it
- Syncing meetings, measurements, tasks and project events between RBM Solutions and Google Calendar.
- When the permission is requested
- When an Owner or Admin chooses to connect Google Calendar from Settings > Integrations.
- Scopes
- https://www.googleapis.com/auth/calendar.events · https://www.googleapis.com/auth/calendar.calendarlist.readonly
- What is stored
- Tokens are stored encrypted on the server side. Events imported or created for syncing are kept in the organization's calendar tables, together with mapping identifiers and brief conflict summaries.
- Token storage
- calendar_integrations.access_token_encrypted and calendar_integrations.refresh_token_encrypted, with token_key_version. Encryption is done with AES-256-GCM as implemented in src/lib/security.ts.
- Deletion
- Disconnecting Google Calendar revokes the token with Google on a reasonable-effort basis, deletes the local tokens and stops the webhook/sync. RBM events already saved are not deleted automatically, only on an explicit deletion request.
Gmail
- Information access is requested to
- The address of the connected Gmail account and permission to send emails on the user's behalf.
- Why RBM Solutions uses it
- Sending emails to clients from actions the user takes in RBM Solutions.
- When the permission is requested
- When the user chooses to connect Gmail from the integrations area.
- Scopes
- https://www.googleapis.com/auth/gmail.send · https://www.googleapis.com/auth/userinfo.email
- What is stored
- The email address is kept to show the connection status. The access token and refresh token are stored encrypted while the connection is on.
- Token storage
- org_gmail.access_token and org_gmail.refresh_token in the active Gmail route; in the Integration Hub route they are stored encrypted in integration_credentials.
- Deletion
- Disconnecting Gmail deactivates the connection, deletes the local tokens in the active Gmail route and attempts to revoke the token with Google on a reasonable-effort basis. Deletion of other Google data associated with the connection is done on a deletion request sent to the privacy address.
Data retention
- Google tokens are kept as long as the connection is active, or until disconnection or a deletion request.
- Calendar events imported or created as part of syncing are kept as part of the organization's calendar data as long as the account is active, unless an explicit deletion request has been made or another retention obligation applies.
- Technical logs and audit events are kept for operation, security and compliance with legal obligations, according to the RBM Solutions information retention policy.
For deletion requests or privacy questions: support@rbmsolutions.co.il