Managed Edge extension privacy

What the extension collects

Collection starts after the extension receives valid organisation settings, enrols with the configured server and receives an enabled collection policy. Depending on your organisation's settings, it records:

• AI destination activity: the domain, service, time and whether an observation was a visit or an AI connection. Low-confidence possible AI destinations are labelled separately. Full page addresses and unrelated browsing history are not retained.
• Supported submitted prompts: the latest user text from recognised AI generation requests, limited to 8,000 characters, with its original length, submission time, service and observed request outcome. Prompts can include any personal or sensitive information that you place in them, including information about other people. Sensitive-information analysis takes place after collection and does not remove the original text.
• Supported account settings: account and workspace fingerprints for supported ChatGPT, Claude and Perplexity layouts, a bounded workspace name where available, observed plan and training preferences, and the time and source of those observations. Provider identifiers are hashed before leaving the page reader. These records can still be associated with your browser and organisation identity.
• Browser identity and health: installation and sensor identifiers, extension version, connection status, upload counts and supported capture diagnostics. The signed-in Edge profile email can be sent for enrolment, licence attribution and matching to your organisation's Microsoft directory. Optional Microsoft sign-in allows the server to verify a separate account binding.
• Browsing mode: whether a supported observation came from a regular or InPrivate window. InPrivate collection requires both your organisation's monitored InPrivate setting and Edge's permission for the extension to run there.

Supported formats vary by AI service. The extension excludes drafts, old conversation turns, AI responses, attachments and file contents. It does not retain complete request bodies, request headers, page titles or full URLs. It reads only allowlisted account metadata and supported settings controls on ChatGPT, Claude and Perplexity. Its Copilot and Character.AI readers observe supported outgoing submissions, without reading incoming socket messages.

If your organisation enables hourly ChatGPT settings refresh, the extension may briefly open and close a background settings tab while an eligible regular ChatGPT tab is available. This refresh collects supported account settings, without adding activity or prompt records for the refresh itself.

Why the information is used

The configured Promptective service uses these records to show your organisation its observed AI services, review supported submitted prompts, distinguish supported personal and work-account use, analyse retained text for sensitive information, and maintain governance assessments and browser health. This extension observes submissions; it does not block or redact them.

Microsoft directory matching uses reported browser account information. A separate verified Microsoft sign-in is identified as such. Neither proves who typed a particular prompt. Provider training settings describe observed configuration and do not prove whether a provider trained on a particular submission.

Where information goes and who can access it

The extension sends its records only to the HTTPS Promptective server configured by your organisation. It contains no third-party advertising or analytics integration. Microsoft handles a Microsoft sign-in when that feature is used; the authorisation response is returned to the configured server for validation.

Your organisation's authorised portal users can review the records available to their role. Submitted text requires a separate history permission. Exporting or deleting prompt history additionally requires administrator authority. An exported copy is then controlled by its recipient.

The operator of your organisation's configured service and its hosting and backup providers process information needed to run that deployment. Ask your administrator or the privacy contact below for the applicable operator, providers, processing locations and arrangements before collection begins. The extension does not send captured prompts to a public AI service for analysis; configured model analysis runs on the Promptective server.

Promptective's hosted service uses Amazon Web Services for application hosting, databases, storage, backups and infrastructure monitoring. Resend delivers portal account emails and does not receive captured prompt history for email delivery. See the Promptective privacy policy for shared service and website handling.

Storage, retention and deletion

The extension stores its connection credential, cached policy and a bounded delivery queue in its browser profile. The queue holds at most 500 records within 2 MB. Pending submissions and document state use session storage. The extension uses a browser-held signing key to authenticate server requests and HTTPS to transmit records.

The server keeps prompt text separately from activity metadata. Cloud deployments encrypt retained prompt text and analysis findings before database storage, using a separate key for each workspace. Authorised service processing decrypts the records when needed for review and analysis. Prompt text defaults to seven-day retention; your organisation can choose one, seven, 30 or 90 days. Activity and settings evidence defaults to 30 days, with seven, 30 or 90 days available. Authorised administrators can delete prompt text or reset the workspace. Deleting prompt text leaves inventory totals and retained activity metadata intact.

Turning off prompt collection stops new server ingestion and removes queued text when the browser next receives that policy. Previously uploaded history remains until its retention expires or an authorised administrator deletes it. Offline browsers use the last policy they received. Uninstalling the extension removes its browser-held data; it does not delete records already uploaded to the server.

Backup copies and exported records have separate retention. Deleting a live record does not immediately erase all backup media or recipient-held exports. Your administrator can provide the retention and recovery arrangements for your deployment.

Your organisation's controls and your requests

Your organisation controls collection, service exclusions, retention, account-settings observation and InPrivate scope in the portal. The managed extension has connection health, sign-in and portal links; it has no employee pause or recording opt-out control. Contact your administrator about collection settings or access to records associated with you.

For access, correction, deletion or a privacy concern, contact your organisation's administrator or email privacy@promptective.ai. The same contact can receive requests from a person whose information was included in a submitted prompt. We may need to verify a request and coordinate with the organisation responsible for the records.

Changes to this policy

An updated notice will be published with a revised date when this extension's data handling changes. Your organisation is responsible for communicating its deployment settings and any collection notice that applies to your use.