Data flows & privacy controls

• Everyday toolsBrowser ↔ ServiceNowNo SN Utils call for the local actionWork stays in the browser and your ServiceNow instance. Custom scripts and external links can make their own connections.

  Local extension and ServiceNow access

  Browser / SN Utils

  Request using your existing session

  Your ServiceNow instance

  Authorized record or schema response

  Browser / local tool

  This example stays between your browser and ServiceNow. The returned content is not automatically forwarded to the SN Utils backend. Other connected features have separate flows.

  Example payloadExample local request and response

  {
    "request": {
      "table": "incident",
      "fields": [
        "number",
        "state"
      ]
    },
    "response": {
      "number": "INC_EXAMPLE",
      "state": "New"
    }
  }

  Illustrative example with invented values, not an exact API schema or a complete network trace. Authentication headers and routine transport metadata are omitted. The example shows selected data categories, not every field.

  Data accessed or sent

  Page and record content needed for the action the user invokes, including scripts, fields, lists and schema. The extension uses the existing ServiceNow session. Regular and OnPrem builds have different browser host-permission scopes.

  Destination and storage

  The browser and the user’s ServiceNow instance. Local settings and caches use browser extension storage. Browser storage synchronization, where used, is governed separately by the browser/account configuration. Optional ScriptSync can write code to a local development environment.

  When it happens

  As the user navigates and uses extension tools. User-authored scripts and external links can make their own connections.

  Default and control

  Core functionality. Browser administrators can restrict permitted sites within the extension’s declared permissions. ServiceNow permissions still apply; installing the extension does not grant a new ServiceNow role.

  Retention and deletion

  Local settings and caches persist according to their individual lifecycle and browser profile. Local deletion is separate from deleting previously uploaded cloud data.

• License validationSN Utils cloudPeriodic / account actionsChecks entitlement for the connected browser, plus requests when connecting or managing your account.

  Account, browser activation and Pro licensing

  Connected browser

  Account / device authentication

  SN Utils API

  Read entitlement; update device activity

  Account database

  The API returns entitlement and applicable policy to the browser. Licensing does not require ServiceNow record contents. Source IP and operational metadata are separate from this example.

  Example payloadExample licensing data categories

  {
    "account": "example-account",
    "device": "example-browser",
    "entitlement": "Pro",
    "last_seen": "2026-10-05T09:00:00Z"
  }

  Illustrative example with invented values, not an exact API schema or a complete network trace. Authentication headers and routine transport metadata are omitted. The example shows selected data categories, not every field.

  Data accessed or sent

  Account identity such as email and user/account identifiers; subscription or entitlement information; connected-device identifiers, device name and activation/last-seen timestamps. HTTPS requests also expose a source IP to the receiving infrastructure. ServiceNow business-record contents are not needed to validate a license.

  Destination and storage

  The SN Utils website/API and account database. Payment and transactional-email services are separate supporting processors.

  When it happens

  Account creation, browser connection, license checks and related account/device administration.

  Default and control

  Required for connected Pro entitlement. Disabling AI, resource sync or usage sharing does not remove account and licensing traffic. Disconnecting a browser affects Pro activation.

  Retention and deletion

  Account, subscription and device records have separate lifecycles from optional resource content. Do not assume disconnecting a browser immediately deletes all operational records or backups; request clarification for a required deletion deadline.

• Resource syncSN Utils cloudOn change / syncResource sync synchronizes development resources, such as snippets, slash commands and shortcuts, not your ServiceNow business records. It does not automatically copy customer records. Resources may still contain sensitive information if users include it in code, URLs or configuration. Sync Resources is optional and defaults to on.

  Resource sync and shared development resources

  Resource editor

  User-authored resource content

  SN Utils API

  Save under user / selected sharing scope

  Resource database

  Cloud resources can also be read back into a connected browser. Scripts and command URLs may contain sensitive content entered by the user. Turning sync off does not delete existing cloud copies.

  Example payloadExample resource upload

  {
    "resource_type": "snippet",
    "name": "Example log message",
    "code": "gs.info('Example');",
    "owner": "example-user",
    "sharing_scope": "personal"
  }

  Illustrative example with invented values, not an exact API schema or a complete network trace. Authentication headers and routine transport metadata are omitted. The example shows selected data categories, not every field.

  Data accessed or sent

  User-authored snippets and code, slash commands and their URLs/scripts, switches and keyboard shortcuts, plus associated names, descriptions and ownership identifiers. These are development resources, not automatically copied ServiceNow business records. Their contents may still be confidential.

  Destination and storage

  SN Utils API and database. Resources explicitly shared through team or other sharing features are available to the audience selected by the user.

  When it happens

  When connected resource operations synchronize changes or retrieve cloud resources. Explicit sharing and website actions are separate operations.

  Default and control

  Sync Resources defaults to on for eligible connected Pro use. Change it in Settings > Backup & Sync. This is a user setting, not a claimed organization-enforced prohibition on every cloud operation.

  Retention and deletion

  Turning sync off does not erase resources already uploaded or shared. Delete existing cloud resources separately and review shared copies, operational logs and backup retention where relevant.

• Settings & instancesSN Utils cloudAutomatic / manualSettings backup runs automatically when enabled or on request. Instance changes, migration and queued uploads also generate traffic.

  Settings backup and instance configuration

  Browser configuration

  Settings snapshot or instance configuration

  SN Utils API

  Persist backup / configuration

  Configuration database

  Settings backup and instance synchronization are separate operations. Automatic instance migration or queued uploads can occur independently of Sync Resources; the example groups categories rather than representing one endpoint.

  Example payloadExample configuration data categories

  {
    "settings_snapshot": {
      "custom_command": "/example"
    },
    "instance_configuration": {
      "hostname": "example.service-now.com",
      "label": "Development",
      "environment": "non-production"
    }
  }

  Illustrative example with invented values, not an exact API schema or a complete network trace. Authentication headers and routine transport metadata are omitted. The example shows selected data categories, not every field.

  Data accessed or sent

  Settings snapshots and saved configuration. Treat these as potentially sensitive: configured URLs, instance hostnames, custom scripts and other user-entered values can disclose internal information. Instance-management APIs also support instance configuration and synchronization metadata.

  Destination and storage

  SN Utils backend and database for cloud operations; local browser storage for local configuration.

  When it happens

  Automatic settings backups, explicit backup/restore actions and connected instance-management operations. In the reviewed extension source, a migration can also automatically queue existing local instance configuration for upload when an eligible connected user opens Manage, without a new instance edit.

  Default and control

  Auto-Backup defaults to on and has its own switch in Settings > Backup & Sync. Sync Resources and Auto-Backup do not govern every instance-configuration path: automatic migration and queued instance uploads can occur independently of Sync Resources. These switches do not establish a prohibition on uploading instance configuration. Manual cloud actions also require separate review.

  Retention and deletion

  Disabling future backups does not remove existing backups. Delete cloud copies separately. Retention across operational backups and logs must be confirmed for a specific requirement.

• Usage statisticsSN Utils cloud, if sharedBatched countsActions are counted locally. With eligible Pro usage sharing enabled, aggregated daily counts are synchronized, not a separate request for each action.

  Usage statistics

  Local usage counters

  Daily action counts when sharing is enabled

  SN Utils API

  Store counts associated with the user

  Usage database

  Collect Only keeps these usage counters locally. Off stops new usage collection. Neither setting disables licensing, other connected features or operational logs.

  Example payloadExample aggregated usage upload

  {
    "date": "2026-10-05",
    "counts": {
      "example_action": 12,
      "another_action": 3
    },
    "associated_user": "authenticated-user"
  }

  Illustrative example with invented values, not an exact API schema or a complete network trace. Authentication headers and routine transport metadata are omitted. The example shows selected data categories, not every field.

  Data accessed or sent

  For Pro usage sharing: aggregated action counts by day, associated with the authenticated user. This is distinct from resource content and AI chat. Do not interpret a usage opt-out as an opt-out from all service/security logs.

  Destination and storage

  Local extension storage and, in Collect & Share mode with an eligible Pro license, the SN Utils backend/database.

  When it happens

  Local collection during use; automatic or manual usage synchronization when sharing is enabled.

  Default and control

  Collect & Share is the default. Collect Only keeps usage statistics locally. Off stops new usage collection; its confirmation offers keeping or deleting existing local history. These settings control usage statistics, not licensing, sync or AI.

  Retention and deletion

  Deleting local usage history does not delete previously shared server records. No universal automatic server-deletion period is asserted here.

• AI assistanceSN Utils cloud → AI providerUser-triggeredOptional AI requests send submitted prompts and relevant context when you use Send, Generate or another AI action.

  Optional AI features

  Browser AI feature

  Prompt, chat / editor content and context

  SN Utils API

  Model request prepared by the backend

  Selected AI provider

  The response returns through the API to the browser. A separate backend logging path can retain prompt/response content in the SN Utils database. Provider location and retention require separate review.

  Example payloadExample submitted AI request

  {
    "messages": [
      {
        "role": "user",
        "content": "Explain a GlideRecord query."
      }
    ],
    "context": {
      "pageType": "form",
      "tableName": "incident",
      "fieldNames": [
        "number",
        "state"
      ],
      "urlPath": "/incident.do",
      "hostname": "example",
      "tier": "metadata"
    }
  }

  Illustrative example with invented values, not an exact API schema or a complete network trace. Authentication headers and routine transport metadata are omitted. The example shows selected data categories, not every field.

  Data accessed or sent

  Submitted prompts, chat turns and editor content. Sidekick can add page type, table and field names, view, URL path and an instance label. Command generation can include field names, labels and types from schema lookup. Automatic context is intended to be metadata, but prompts and editor contents may include sensitive data supplied by the user.

  Destination and storage

  Browser → snutils.com API → the selected model provider, including OpenAI, Anthropic or Google. Backend request logs may also store content. The database location does not establish the AI provider’s processing location. No US-only processing commitment is offered.

  When it happens

  An explicit AI interaction, such as Send or Generate. AI and resource sync are independent features. Documentation Q&A is another AI entry point.

  Default and control

  Sidekick is opt-in and off by default; the account AI policy allows AI by default. Team owners/admins can set an account default and per-user overrides. Backend authorization enforces the effective user policy on extension AI endpoints; the extension also updates its UI when it receives the policy. Check per-user On overrides when disabling the account default.

  Retention and deletion

  AI logs can retain up to 2,000 prompt characters, 5,000 response characters and 1,000 error characters, plus identity and request metrics. Documentation Q&A can store a question of up to 32,768 characters. Short content may be retained in full. Closing a chat does not delete these logs. A fixed automatic deletion period and complete provider retention coverage are not asserted.

Frequency depends on your settings and use. Licensing remains active for connected Pro use. Existing instance configuration can also be uploaded through migration or queued operations, independently of Sync Resources. See the backup flow for details.