SPB Management

SPB Management Privacy Policy

Effective date: 2 November 2026 · Application: SPB Management · Terms: Terms of Use

1. Who operates SPB Management

SPB Management is an office and project management application for engineering teams, developed and operated by Dercell (“Dercell”, “we”, “us”). The application is provided to organizations for use by their authorized team members; it is not a public consumer product.

For any privacy question, data-access request, or deletion request, contact us at itamar@dercell.co.il or through our contact page.

2. Information we process

Depending on how the application is used, we process:

  • Account and profile information, and the access permissions assigned to each account.
  • Work information: project membership, tasks, schedules and timelines, reported work hours, employee progress reports, internal messages, references to the network locations of project files, and — for users whose permissions allow it — financial records.
  • Google connection information: the identity of a connected Google account, the calendar information needed for the features the user enabled, the permissions granted to the connection, and related operational and audit metadata.

What any given user can see or do is limited by their account permissions and project membership.

3. How we use this information

We use the information above to operate the application’s features:

  • Managing projects, tasks, schedules, and staff workloads.
  • Recording work hours and producing progress reports.
  • Delivering internal messages between team members.
  • Coordinating availability and planning meetings where a Google Calendar is connected.
  • Providing the AI assistant features described below.
  • Maintaining security, auditing access, and operating the service reliably.

4. Google Calendar connection

Connecting Google is optional. A user can keep their default Google account connected and add other Google accounts separately. The application requests the Google permissions openid, email, and calendar.events.owned.

The calendar permission Google grants can technically cover viewing, creating, changing, and deleting events on calendars the user owns. The application’s current Calendar features use it to read meetings, coordinate availability between colleagues, and create meetings and invitations after the user reviews them.

Optional manual calendar import requires additional, separately reviewed Google consent. The permissions calendar.calendarlist.readonly, calendar.events.readonly, and calendar.events.freebusy allow the application to discover the calendars available to the connected Google account and read events or availability from the calendars the user selects. Discovery reads calendar names, colors, time zones and access roles so the user can choose one, several or all available calendars while keeping them separate.

Imported calendars are private to the importing SPB user by default. Importing a calendar does not automatically share it with colleagues, publish it for visitors, or make a secondary calendar available to the AI assistant. The application respects Google’s calendar access roles; shared calendars available only for reading remain read only in SPB, and free/busy-only access does not reveal meeting titles or guests. Meeting creation with the existing owned-calendar permission is limited to calendars that the connected Google account owns.

Each additional Google account has its own connection and calendar selection. Its imported calendars remain private to the connecting SPB user and do not inherit the default calendar’s colleague sharing or AI permissions. The account and destination calendar are shown when planning a meeting so the user can review which Google account will create it.

A user may separately choose a public display name, working hours and available openings for a calendar in SPB Public Booking. This requires an explicit publication choice; internal sharing and calendar import do not publish availability automatically. Public booking presents openings rather than private event details, and meeting requests require office approval. The SPB Public Booking privacy notice describes that separate visitor service.

  • The connected Google account can be different from the email address used to sign in to SPB Management.
  • The normal Calendar connection and the AI Calendar features are separate connections with separate consent. Connecting a calendar does not give the AI assistant access to it.
  • Calendar owners choose which colleagues may see their availability, see meeting details, or schedule meetings with them.
  • Sharing a calendar with a colleague does not permit that colleague’s AI assistant to access it. Delegated AI access to a calendar requires an additional explicit grant by the calendar owner.
  • Office managers have no automatic access to another person’s connected calendar.
  • The application does not request access to Gmail inboxes. Features that share by Gmail or WhatsApp prepare a draft for the user to review and send themselves.

5. AI assistant processing

When a user works with the AI assistant, their instructions and the selected information they are permitted to access can be sent to OpenAI for processing, in order to produce an answer or a proposed action.

  • This information can contain identifiable business information — for example names, email addresses, descriptions, financial values, or file-link metadata. It is not anonymous.
  • The assistant does not automatically receive an unrestricted export of the entire database; it works with the information relevant to the user’s request that the user is permitted to access.
  • Assistant access to connected Google Calendar information requires the separate AI Calendar connection and the applicable sharing permissions. Optional manual calendar import does not expand that consent or automatically give the assistant access to imported secondary calendars.
  • Changes the assistant proposes are presented to the user for review before they are executed.

6. Service providers

SPB Management relies on the following categories of providers:

  • Supabase — application authentication, database, and messaging infrastructure.
  • Google — optional calendar connection, where a user enables it.
  • OpenAI — processing of AI assistant requests, where a user uses the assistant.

Each provider processes information only as needed to deliver its part of the service.

7. Sharing

We do not sell personal information. Information is shared only with the service providers above as needed to operate the application, within the user’s organization according to account permissions and project membership, or where required by law.

When a user explicitly publishes booking availability, visitors can see that calendar’s chosen public display name and available openings. Existing event titles, descriptions and guests are not published through the booking page.

8. Security

  • Google connection tokens are encrypted and stored on the server.
  • OpenAI and Google client secrets remain server-side and are not exposed to users’ devices.
  • Internal messages are protected by application access permissions; they are not end-to-end encrypted.
  • References to network file locations do not upload or index the contents of office files.

We apply reasonable technical and organizational measures to protect the information we process, but no method of storage or transmission is completely secure, and we cannot guarantee absolute security.

9. Retention

We keep account and project information for as long as the relevant account or project is active and as needed afterwards for the operation of the service, legitimate business records, and legal obligations. Backup copies are removed in the ordinary course of our backup cycle. For questions about retention of specific records, contact us at itamar@dercell.co.il.

10. Disconnecting Google and deleting data

Users can control their Google connection from within the application:

  • Choose calendars — users can review their imported calendars and deselect any they no longer want the application to use. Deselecting a calendar withdraws any linked public booking entry; importing it again does not automatically restore publication. This does not delete events from Google Calendar.
  • Disable AI Calendar access — removes the stored AI Calendar connection while keeping the normal Calendar connection working.
  • Disconnect the default Google account — removes that account’s normal and paired AI connections and their sharing permissions. The application attempts to revoke Google authorization for that Google account. Separately connected Google accounts remain connected.
  • Disconnect an additional account — deletes that account’s saved access credentials in SPB and withdraws its imported calendars and public booking entries. Other Google accounts and the default AI connection remain connected. This stops access within SPB without automatically revoking the Google application’s broader authorization; the account can be reconnected later with consent.
  • Access can also be removed at any time from the user’s Google Account settings, under third-party apps with account access.

Disconnecting Google does not delete events that already exist in Google Calendar, and it does not by itself erase SPB Management accounts, projects, messages, audit records, or backups.

To request access to your data or deletion of your account and associated data, contact us at itamar@dercell.co.il or through our contact page. We handle each request individually and will confirm what was done.

11. Changes to this policy

If we change this policy, we will update the version on this page and its effective date. Material changes will be communicated to the organizations using the application.