Privacy
What GlideLens does with your data
Last updated 30 October 2026 · applies to GlideLens v0.11.1 and later
There is no GlideLens server. No account, no telemetry, no analytics, no error reporting, no third parties. Nothing GlideLens reads is sent anywhere we control, because there is nowhere for it to go.
It reads your ServiceNow instance the same way you do — through that
instance's own API, on your own logged-in session, with your own
permissions. It cannot see anything you could not already see, and it works
only on *.service-now.com pages.
What it reads, and why
All of this is processed on your device, in your browser, while you are using the feature that needs it. None of it is transmitted anywhere except back to the ServiceNow instance it came from — or, when you ask Variable Prefill to copy a ticket from another instance you have open, to the instance whose form you are filling, and when you ask Update Set Lens to check another instance you have open, to that instance, as described below.
| What | Why |
|---|---|
| Page content on ServiceNow tabs — form labels, fields, catalog variables and their values | To place variable icons, to list the fields a form shows for Translation Lens, and to read and set values on catalog forms |
| Records from your instance's Table API — dictionary entries, the summary fields you choose to search, catalog variables, client scripts, UI policies, script source, attachment filenames | Record search, code search, catalog debugging, translation lookups and variable prefill. These are ordinary API reads on your session |
| The current tab's URL, table name and record sys_id | To work out which record you are on, for Record Search preselection, "Copy sys_id", and the record-scoped commands |
| Your username and display name, and the instance's node and version | Shown in the toolbar popup so you can tell which instance and which identity you are working against |
While Debug Timeline is recording: g_form calls, field
events, GlideAjax requests and responses, and JavaScript errors |
To produce the timeline. See the caveat below |
| When you run Update Set Lens: the update set's details, and for each update it holds, its name, type and fingerprint (update id and content hash), with the same for the versions of those records, including who recorded them and when, and, when you click Open record, that record's table and sys_id. Never the updates' contents | To tell which updates are no longer the version that runs, and where the newer one is. With Check on, each update's name and fingerprint go to the other instance you chose, through a tab you have open there, to compare with what runs there; for an update that differs there, when the version running there was saved and the name of the update set it was saved in come back, and for each update, the table and sys_id of its record there and the sys_id of the version that runs there, so the row can link to them |
| When you run Translation Assistant: the text of the catalog item open on the Localization Framework comparison page, including the messages its scripts show and its rich text as HTML, and the language names on your instance | To build the file you hand to your AI tool, and to fill its reply back into that page for you to review. See the section below |
Authentication
Reading your instance's API requires ServiceNow's CSRF token
(g_ck). GlideLens reads it inside the instance's own page, attaches
it as a header on requests to that same instance, and does
nothing else with it. It is never stored, never copied into extension storage,
and never sent to any other destination. Your session cookie is handled by the
browser exactly as it is for any other request to that instance.
Debug Timeline traces
A Debug Timeline recording captures what your form actually did, which means a trace can contain real data from the record you were working on — field values, GlideAjax parameters and responses. Values whose field or parameter names look like secrets are redacted, and the trace is capped and discarded when you close the page. But it is your data, and it only leaves your device if you copy it out and paste it somewhere. Read a trace before you share it in a ticket or a chat.
What is stored on your device
GlideLens uses your browser's local extension storage for exactly four things. All of it stays on your machine, and all of it disappears when you uninstall the extension.
- Which command you pinned in the palette.
- A per-instance map of what code search can reach — table and field names from your instance's search configuration, cached for seven days so a search does not re-check it every time.
- A per-instance record of which fields exist on the tables code search reads, cached the same way.
- The tables you starred in Record Lens, per instance — each table's name and label, the names of the fields you search and filter it by and of the columns you show for it, and when you starred and last changed it. Only tables you star yourself are kept. They are never expired on a timer, and unstarring removes them; only if you starred tables on more than 100 instances would the list changed longest ago be dropped to make room, and Record Lens says so when it happens. No search term, filter value or result is stored with them.
The last three hold configuration metadata — names of tables and columns — not the contents of any record. Nothing else is persisted: everything else GlideLens reads lives in memory while a panel is open and is gone when you close it.
One thing lives in memory a little longer. Translation Assistant keeps up to five of the drafts it has exported in the browser's session storage — memory, not disk — so that a reply can be matched to the page it answers even after the extension's background process has been restarted in between. A draft holds that item's text. It is never written to disk and is gone when the browser closes.
What leaves your device
Nothing, other than requests to the ServiceNow instance you are
already signed in to. The extension makes network requests to the
origin of the ServiceNow tab you are on. When you ask Variable Prefill to read
a ticket from another instance, or Update Set Lens to check another instance,
GlideLens reads it through a tab you already have open on that instance, with
that tab's own session, in the same way. It
never signs in anywhere itself. It has permission to reach
https://*.service-now.com/* and nothing else, so it could not
contact a third party even if it tried to.
There is no analytics, no crash reporting, no usage counter, no A/B testing and no remote configuration. The extension contains no remotely-loaded code: every line that runs ships inside it and is readable in the public repository.
Translation Assistant and your AI tool
Translation Assistant is the one feature that produces something meant to leave your device: a JSON file holding the untranslated text of the catalog item in front of you, including the messages its scripts show and its rich text as HTML, with instructions for an AI tool to translate it. GlideLens does not upload that file, does not connect to any AI service, and does not know which one you use. The file leaves your device only when you upload it, or paste its contents, into a tool of your own choosing, and from that point it is handled under that tool's terms, not ours. The panel says so beside the download button. Check your organisation's rules on sharing instance text with such a tool before you do, and read the file first — it holds your item's text, and nothing else.
What GlideLens writes
It is a read-only tool with three deliberate exceptions, and it is worth being precise about the difference — because two of them change a page you are looking at, and the third changes something on the instance: who your own session is, which Prefill can also do when you confirm it.
It never writes to your ServiceNow records and never submits a form. Record search, code search, catalog insight, variable values, Translation Lens and Debug Timeline only read.
Prefill changes unsaved fields on the catalog form in front of you, which is the entire point of it — it copies values from a ticket you name into the form you are filling in, so you can review them and submit yourself. The ticket can be on this instance or on another instance you name and have open; in that case GlideLens first looks up the records the values refer to on the instance you are filling, and leaves out any it cannot find there. It fills the form; you decide what happens to it. Nothing is saved to the instance unless you submit it. Check your organisation's rules before copying production data into a non-production form.
While you are impersonating someone, the account you are acting as often cannot read another person's ticket. Prefill can then offer to switch your session back to your own account, read the ticket, impersonate the same person again and fill the form as them. It does this only after you confirm it, in a step that names the person and the ticket and says what will happen. It uses the same session change as Impersonate below, so ServiceNow records both switches in its audit log, and for that moment your other tabs on that instance act as you.
Translation Assistant fills unsaved translations on the Localization Framework comparison page in front of you, in the same way: it puts your AI tool's reply into the page's own boxes, through the page's own update channel — or, for rich text, the page's own editor — and only for rows that still pass its checks. A reply's own markup is never written: a rich field keeps the source's tags exactly, and only its words change. The panel then lists every row it did not fill and why, and keeps the old text of any translation it replaced. Nothing is saved to the instance unless you press the page's own Publish; reloading the page discards every fill.
Impersonate changes your own ServiceNow session, and that one is different in kind. The other two put text into a page and leave saving to you; a reload undoes them. This one asks the instance to make your session act as another user, so it takes effect on the instance and on every tab, and a reload does not undo it. It is the only server-changing thing GlideLens does, apart from Prefill's confirmed switch above, which uses this same session change.
What it does not do matters as much. It changes no user record and administers nothing — the only thing it alters is who your own session is acting as. It never starts without an explicit confirmation naming the person in full, and a click on a result opens that confirmation rather than doing anything. ServiceNow records impersonation in its own audit log, as it would if you had used the platform's user menu; that record belongs to your instance, and GlideLens neither writes nor reads it. Searching for someone to impersonate reads only the identity fields needed to recognise a colleague — user ID, name, email, title, and the country, department and company shown on each result — plus whichever filterable fields your instance's own dictionary offers, role membership when you pick a role, and group names and group membership when you pick a group. A confirmation also reads the roles of the person it names, and which of those roles contain others, so you can see what you are about to act as. When the panel opens it also reads ServiceNow's own list of the people you recently impersonated, the one the platform keeps for its Impersonate dialog, and then the same identity fields for each of them. A Service Portal page does not say whether you are impersonating, and a Workspace page does not say which account to return to, so on those pages it fetches a page from your own instance and reads only those two facts from it. Inactive, locked-out and web-service-only accounts are never listed, because impersonating one can end your own session. GlideLens stores no search term, result, role, group or impersonation history anywhere; the account to return to is held only in the extension's session memory, for the one instance it came from, and is gone when the browser closes.
Permissions, and what each is for
| Permission | Used for |
|---|---|
https://*.service-now.com/* |
The only sites the extension runs on at all |
scripting |
Reading page globals like g_form, and injecting the code
search panels only when you first use them |
storage |
The four local items listed above |
clipboardWrite |
"Copy sys_id", "Copy list" and copying a Debug Timeline trace — only when you click them |
What we never do
- We do not sell or transfer your data to third parties.
- We do not use or transfer your data for anything unrelated to the extension's single purpose.
- We do not use or transfer your data to determine creditworthiness or for lending purposes.
- We do not use your data for advertising, personalisation, profiling or re-targeting.
These are not aspirations. There is no server to send data to and no permission to reach one.
Children
GlideLens is a developer tool for people working in a ServiceNow instance at work. It is not directed at children and is not intended for use by anyone under 13.
Changes to this policy
If how GlideLens handles data ever changes, this page is updated and the change is described in the changelog for the release that makes it, before or with the release that makes it — not quietly afterwards. The date at the top of this page always reflects the last substantive change.
Contact
Questions, or something here that does not match what you observe: open an issue. The source is public, so you are welcome to check any claim on this page against it — that is rather the point of it being public.