BUSINESS WORKSPACE01. Who operates SIGMUN
SIGMUN Intelligence OS is a private business workspace operated by SIGMUN management. It supports directives, tasks, suppliers, materials, formula drafts, experiments, and linked knowledge. Privacy requests can be sent to nezarhg@gmail.com.
This policy covers the application and these public information pages. Viewing the public pages does not provide access to the private workspace.
02. Data we process
We process account email addresses, account identifiers, workspace memberships and permissions, and records and notes entered by authorized users. Audit records associate changes with the person performing them to protect the integrity of business records.
Optional integrations require authorization information and connected-account details. Hosting providers may process technical request information, including IP addresses, browser details, and request times, to deliver and secure the service.
03. Google access and data use
Google integration is optional and managed by the workspace owner. We request basic Google identity and verified email through openid and userinfo.email. We request drive.readonly to list and search file names, identifiers, types, and modification times. This permission can cover files the authorized Google account can access; it is not restricted to a SIGMUN folder or individually selected files.
When the owner opts into Sheets, spreadsheets.readonly permits reading spreadsheet titles, worksheet names, and a preview of the first worksheet, limited to 50 rows and 20 columns. Requested data passes through the application server to the authorized user’s interface. The Drive and Sheets connection does not write to or delete those files. Optional synchronization of a selected materials sheet into SIGMUN is described below.
General Sheet previews are not automatically saved as business records. The exception is a materials sheet explicitly selected by the owner for import and synchronization, as described below. Information manually entered into SIGMUN is treated as workspace data. Opening a file in Google takes the user to Google’s service and policies.
04. Google Calendar task synchronization
When opted into, we request https://www.googleapis.com/auth/calendar.app.created to create a dedicated SIGMUN calendar and manage events on calendars created by this application. It does not provide access to your existing personal calendar. Synchronization starts only after Google authorization and explicit activation of the institution calendar.
A server worker runs approximately every minute in batches, even while the app is closed. Task titles, descriptions, dates and times are transferred in both directions. New ordinary events added to this calendar become institutional tasks visible to authorized workspace members. We do not send guest invitations; recurring events and events with guests require changes before synchronization.
Supabase retains calendar and event identifiers, task mappings, synchronization cursors, conflict snapshots for review, and audit records. Completing a task requires a result in SIGMUN and removes its calendar event. Deleting an event never deletes its task; the owner reviews the deletion and may clear its schedule. Conflicting edits remain pending until the owner chooses a version.
You may pause synchronization without deleting tasks or the calendar. Disconnecting Google or revoking authorization stops subsequent synchronization; an already-started request may finish. Revocation does not erase existing events, tasks, or records. Integration-data deletion can be requested through our contact email. Network failures and Google limits can delay synchronization; this is not a guarantee of immediate reminders.
05. Purpose and Limited Use
We use data to deliver user-requested workspace management, search, previews, storage, audit, and access protection. SIGMUN’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including Limited Use requirements.
We do not sell Google user data, use it for advertising, targeted marketing or creditworthiness decisions, or use it to train general-purpose AI models. Human access to Google content is limited to explicit agreement to access specific data, necessary security purposes, or legal obligations as permitted by Google’s policy.
06. Storage, security, and persistent connection
Cloud workspace records are stored in Supabase with membership-based access controls. Integration secrets and refresh tokens are encrypted in Supabase Vault; requests use HTTPS. The server uses the stored refresh token across sessions while Google authorization remains valid. A saved Client Secret is not returned for display.
Browser storage maintains the application session. Device-library notes can remain in the browser until removed or site data is cleared. A Google connection attempt uses temporary session-storage verification data. Persistent Google tokens and Client Secrets are not stored in browser storage.
Signing out does not delete workspace records or the saved connection. No system can promise absolute security or authorization that never expires; Google may revoke access or require new consent.
07. Notion and planned features
When enabled, Notion integration stores its token encrypted and reads only content made available to that integration. Imported content is saved as a final note only when the user saves it.
When Google Cloud Vision OCR is configured, the owner selects an image from their device and explicitly chooses Extract text. The browser prepares the image and sends it through the SIGMUN server to Google Vision for OCR. The global Google endpoint is used; processing is not restricted to the user’s country. OCR does not automatically access Drive, Sheets, or Notion files or expand the existing Google authorization.
SIGMUN does not automatically store the image or extracted text in its database. Text is returned for correction and can be opened as a draft; only an explicit save creates a workspace note. Closing the OCR panel clears its preview and unsaved text from the interface. Google processes the image under its applicable service terms and policies.
The Vision API key is encrypted in Supabase Vault and used only by the server after owner configuration. Request identifiers, an image hash, actor, timestamps, and status are retained for deduplication, conservative usage metering, and audit, without storing the image or text. Deleting the key does not erase saved notes or usage records. Data deletion can be requested by email.
Optional manual Gemini analysis and semantic search are described below. Each request requires an explicit user action and consent.
09. Retention, deletion, and revocation
Workspace records are retained while in use until removed through an available action or an authorized, verified request. To request deletion of an account, records, or saved integration credentials, contact nezarhg@gmail.com. We verify identity and authority before processing. Records required for audit or legal obligations may be retained; backup copies may remain until the provider’s retention cycle removes or replaces them.
Disconnecting Google in SIGMUN removes its refresh authorization but retains the encrypted OAuth client configuration for easier reconnection. Request deletion of that configuration by email if needed. Google access can also be revoked in Google Account connections. Revocation does not erase previously entered SIGMUN records or original Google files.
Clearing browser site data removes local device-library and session data, but does not automatically remove cloud records.
10. Your choices, contact, and updates
You may decline optional integrations, revoke them, or request access, correction, or deletion through nezarhg@gmail.com. Requests are reviewed in line with permissions and applicable obligations.
We add no advertising or marketing analytics trackers to these public pages. The hosting platform may use technical logs or technologies required to serve them.
The update date appears above. Changes to Google data use will be disclosed and new consent obtained before processing data for a new purpose.
11. Materials sheet import and synchronization
At the owner’s explicit request, the server reads one selected spreadsheet and tab and stores material names, quantities, properties and all source columns in the organization’s private materials catalog. Spreadsheet and tab identifiers, row positions, source fingerprints, sync timestamps and conflict copies are retained for review. Reads are bounded to 5,000 rows and 52 columns. Google permissions do not expand and no changes are written back to Sheets.
Optional synchronization runs approximately every 15 minutes even while the site is closed. The owner can request an update or pause synchronization from Materials. Disconnecting Google stops subsequent attempts. Network failures and provider limits can delay reads. Pausing does not delete existing catalog records; integration-data deletion can be requested through management.
Quantities are source references, not financial or stock postings. Zero and unknown quantities are preserved, and safety information is not automatically validated. Identity is based on the normalized name within the tab: moving rows does not create duplicates, while a renamed material may create a new record and flag the previous name for review. Local edits and missing materials are retained and marked for review rather than silently overwritten or deleted. Imported Google data is not used to train a general-purpose model.
12. Gemini, semantic memory and V1.1 operations
After the owner explicitly consents to each request, SIGMUN sends the selected directive, up to three explicitly selected knowledge excerpts of up to 1,500 characters each, and a limited server-selected tool summary to Gemini for an internal proposal. Optional semantic indexing sends the selected note title and first 1,500 characters, or a search query, to Google’s embedding model. Integration secrets and the entire database are never sent. Proposals, source versions, usage and request states are stored for review, deduplication and budget controls.
The free Gemini API tier may use inputs and outputs to improve Google products under its terms. Paid-tier handling differs; connecting an API key does not verify the organization’s processing settings. The formula-specific hiding policy has been withdrawn. Formula and laboratory records and notes are visible within organization permissions, and selected information may be sent to Gemini or optionally indexed with explicit consent. Abeer can use the cloud pathway after renewed consent; formulas are not automatically uploaded in bulk. Account and integration-key protections remain in place. Drive and Sheets content is not automatically sent to Gemini, and Google API data is not used to train a general-purpose model.
Proposals require review. Rashid creates tasks only after a separate acceptance action, and result approvals bind to a record version. Original documents are stored privately and fingerprinted for deduplication. OCR suggestions require human review before financial or inventory posting. Posted entries are corrected through documented reversals or adjustments.
All eight new schedules are disabled. No automatic external notifications, publishing or commitments are enabled. Existing Calendar sync is independent. Manual encrypted exports contain business rows and a separate recovery key, excluding Auth passwords, Vault secrets and original Storage file bytes. No new daily backup is active and this export alone is not a complete disaster-recovery guarantee.
13. Execution, knowledge and diagnostics
V1.2 records assistant assignment, versioned task results, review and approval reasons, and audit events. Prices, openings and orders remain drafts subject to authorized approval. No external correspondence is sent automatically.
Local chunk indexing requires an explicit action and stores text, source version, offsets and optional assistant or task scope. Changed or deleted sources invalidate old retrieval. Local indexing sends no text to an AI provider; external analysis uses only explicitly selected sources under application safeguards.
A limited connection diagnostic may retain non-sensitive synthetic output, provider state, attempts and usage measurements, without exposing connection keys. The eight backup and reporting schedules remain disabled and require separate activation approval. Encrypted business exports exclude Auth passwords, Vault secrets and Storage bytes and do not establish PITR coverage.