Supported submitted text
When enabled, the sensor records the latest user text from supported AI submissions. Drafts, earlier conversation turns, attachments and AI responses are excluded.
Privacy Policy
Last updated: 19 October 2026
This policy explains how Promptective handles personal information on our public website and in our browser monitoring service, including the extension, organisation portal and supporting APIs.
Your organisation controls browser collection. Authorised portal users can review supported AI activity and retained submitted prompt text. The browser-specific notices below describe manual Chrome pairing and managed Microsoft Edge deployment.
At a glance
Website analytics choices
Optional analytics follow the website’s regional setting and your choice. Use Privacy choices to turn them off. Advertising consent remains denied.
Organisation access
Your organisation’s portal permissions control access. Reading submitted prompt text requires a separate history permission. Collection and retention controls are in the portal.
Privacy requests
Contact your organisation about its monitoring settings. You can also ask Promptective about access, correction, deletion or a privacy concern.
01
Who we are and what this policy covers
The supplier is Promptective Pty Ltd, ABN 72701752936. This policy covers our public website, enquiries, browser sensor and connected organisation portal. A separate service or integration may provide an additional notice for its own data handling.
For the extension’s collection, permissions and setup, read the notice for the browser package your organisation uses.
02
Your organisation and Promptective
Promptective is responsible for the information we use to manage website enquiries, service accounts and our business relationship with you.
We process browser activity, submitted text and account-setting observations on the organisation’s behalf. Its administrators decide collection, exclusions, retention and access. Ask your organisation for its monitoring notice and the authority for its deployment. We assist it with privacy requests concerning those records.
03
Account and organisation information
For invited portal accounts and organisation access, we process:
- Account email and name, invitation and verification state, organisation membership, role and history-access permission;
- Password hashes, session and verification records, expiry information and optional authenticator or recovery-code records;
- Organisation settings, licence capacity and assignments, configured Microsoft tenant and directory records, and administrator actions;
- Browser credential hashes, installation public keys and enrolment records used to authenticate browsers and manage access. The extension keeps its own connection credential in the browser profile.
04
Website enquiries
Contact, demo and partner forms collect the details you submit, such as name, work email, company, role, phone, region, website, team or client size, selected topic and message. The form asks for consent to respond. Resend delivers the enquiry and that consent indication to the relevant Promptective mailbox; the form handler does not save enquiry content in the product database.
The enquiry service uses temporary source-network-address counters to limit abuse. Its per-source window is ten minutes. Enquiry emails remain subject to the email provider’s and recipient mailbox’s retention. Please avoid including passwords, prompt history or other sensitive records in a general enquiry.
05
Public website analytics
On public marketing pages, Google Tag Manager and its configured analytics tags load while the regional setting and your choice allow analytics. Visitors detected in Australia receive an on-by-default setting that can be turned off. Other and unknown regions require an affirmative choice. Global Privacy Control and Do Not Track signals disable this integration.
While analytics are enabled, Google’s configured tags may receive:
- Network address and approximate location;
- Page address, including query parameters, page title and referring address;
- Browser, operating system, device, language and screen information;
- Visit times and configured page or interaction events.
A prepared PostHog integration, if enabled, measures page visits, exits and selected website actions without session replay or form-value collection. It removes URL queries, fragments and referrer paths. PostHog uses the network address and browser user agent to calculate a server-side audience hash, then discards the raw values. This integration uses no PostHog cookies or browser storage. Website analytics are separate from the portal and extension; captured prompts and account records are not analytics events.
06
Trials and billing
The public contact and demo forms are enquiries; they do not create a product account, activate a trial or collect payment card details. Where regional pricing is enabled, the website uses the source network address to estimate a country with a locally held database, without sending that lookup to an external geolocation service. If you follow a separate registration, trial or payment link, the information and terms presented for that service describe its additional handling.
07
Browser AI activity
After manual pairing or managed enrolment, an enabled collection policy allows the sensor to record:
- Recognised or organisation-registered AI destination domains, service identity, time and whether an observation was a visit or connection;
- Possible AI destinations supported by multiple signals, with an explicit low-confidence classification;
- The browser installation, sensor version, connection health, delivery counters and last report;
- Regular or InPrivate browsing mode where observed, with earlier records retaining an unknown mode;
- The original organisation-account binding and its assurance when a valid binding exists at collection time.
Visits and connections are separate from prompt submissions. The sensor discards unrelated browsing and does not upload full page addresses, page titles or request headers. Ordinary browsing does not become prompt history.
08
Submitted prompt history
When the organisation enables prompt capture, supported generation requests contribute only the latest submitted user text, up to 8,000 characters, with its original length, service, time and observed outcome. The sensor excludes drafts, earlier conversation turns, attachments, file contents and AI responses. Coverage depends on the supported service and request format. This release observes submissions; it does not block or redact them before the AI provider receives them.
The portal displays history excerpts and lets authorised users open retained text. History access is a separate permission from the general portal role. Exporting or deleting history also requires administrator authority. Submitted text may contain personal, confidential, health, financial or authentication information, including information about other people. Server analysis can flag supported sensitive-information categories after collection; it does not remove the original text or guarantee that all secrets are recognised.
Organisation administrators control capture, exclusions and retention in the portal. The extension has no individual pause or recording opt-out switch. Pausing collection stops new ingestion and clears queued records when the browser receives that policy; previously uploaded history remains until expiry or authorised deletion. Uninstalling removes browser-held data, while uploaded records follow the organisation’s retention and deletion controls.
09
AI account settings and Microsoft identity
When enabled, bounded readers observe supported account, workspace and training settings in ChatGPT, Claude and Perplexity. Records can include hashed account/workspace fingerprints, a bounded workspace name, observed plan or personal/work environment, training preference, source and time. Fingerprints remain linkable to browser records and are not anonymous. Unsupported or ambiguous settings remain Unknown; current settings do not rewrite earlier submission snapshots.
An optional hourly ChatGPT refresh may open a temporary background Data controls tab when an eligible regular ChatGPT tab is available, then close it. It observes supported settings without changing provider preferences or submitting a prompt. Other supported providers are observed from pages loaded through normal use.
The reported browser-profile email can support licence grouping and server directory matching, labelled Directory matched. Optional Microsoft sign-in is verified separately by the server and labelled Sign-in verified. Neither a reported account nor a linked user proves who typed a prompt, which account was used at the AI provider or the device’s identity. Reported browser identifiers are not used as portal access credentials.
10
Managed Edge and InPrivate
Managed Edge receives its HTTPS server and enrolment settings from administrator policy. The organisation chooses whether to disable InPrivate, leave it unmonitored or require monitoring. InPrivate capture needs both monitored deployment scope and Edge permission for the extension to run there.
- Regular and InPrivate windows share the parent browser profile’s credential, queue and Microsoft attribution;
- Closing an InPrivate window does not delete records already retained by the organisation;
- Collection remains limited to supported AI activity and submissions. The extension does not collect general private-browsing history.
11
Diagnostics and service logs
Service infrastructure receives network and request metadata needed to deliver, authenticate and secure connections. The application uses bounded operational and security records. Captured prompt text, credentials and authentication responses are not intended for operational logs. Browser health reports describe the connection and supported capture pipeline rather than a full browsing record.
Where website error monitoring is enabled, Sentry receives a fixed route category, a generic error label and bounded code-stack locations. The marketing error hook removes form values, request/response content, headers, cookies, query strings and prompt text, and sends reports without browser credentials. Where enabled, Promptwatch receives recognised AI crawler requests to the public website: time, method, path, status, content type, network address, hostname and user agent, excluding queries and referrers.
12
How we use information
We use the information described in this policy to:
- Provide AI inventory, submitted prompt history, account-setting reports and governance assessments;
- Authenticate accounts and browser installations, allocate licences, prevent abuse and apply organisation collection settings;
- Analyse retained submitted text for supported sensitive-information findings and make the results available to authorised reviewers;
- Respond to enquiries and privacy requests, provide support and send account invitations, verification and recovery messages;
- Maintain the service, measure permitted public website use and comply with applicable obligations.
Captured prompts are sent only to the configured Promptective endpoint. The extension has no advertising or third-party telemetry integration and does not train models. Optional model analysis runs within the Promptective service environment. The AI provider receives your original submission through its own website and applies its own terms and privacy practices.
15
Retention and deletion
Different records have different retention:
- Prompt text defaults to seven days. Administrators can choose one, seven, 30 or 90 days. Prompt analysis follows the text’s retention and deletion;
- Activity and settings evidence defaults to 30 days, with seven, 30 or 90 days available. Removing prompt text leaves retained activity metadata and inventory totals intact;
- Inventory, current assessments and first/last observation totals remain until reset. Account, enrolment, credential and security records have separate service and access lifecycles;
- Website enquiries remain in Resend and recipient mailboxes under their configured retention. Analytics providers retain permitted events under the active property or project settings;
- Backups and exported copies have separate retention. Deleting a live record does not immediately erase earlier backups, storage media or recipient-held exports. Recovery applies recorded privacy changes before restored records become available.
Ask your administrator or the privacy contact for the retention and recovery arrangements that apply to your deployment. Verified deletion requests are handled within applicable legal or contractual requirements; this policy does not promise immediate erasure from all media.
16
Your rights and requests
Depending on applicable law, you may have rights to access, correct or delete personal information, restrict or object to processing, obtain a portable copy, withdraw consent or complain to a privacy regulator. Eligibility and exceptions depend on the law and processing involved.
In Australia, you can raise concerns with us and, where applicable, the Office of the Australian Information Commissioner. In the United Kingdom, European Economic Area, New Zealand, Canada and United States, the relevant national or local privacy regulator can explain the rights available to you.
Contact privacy@promptective.ai or use the privacy contact form. We may verify your identity and coordinate with the organisation responsible for its monitoring records. A request from someone whose information was included in another person’s submitted prompt can use the same contact.
17
Security
Hosted connections use HTTPS and verified database TLS. Cloud deployments encrypt retained prompt text and analysis findings before database storage with a separate KMS-wrapped key for each workspace. Database volumes and backups have separate encryption and access controls. The authorised API decrypts records for analysis and permitted history access; downloaded exports contain the requested readable text.
Password hashing, credential hashes, signed browser requests, replay protection and organisation-scoped permissions protect access. Field encryption does not hide records from an authorised running service, and browser-profile storage is not separately encrypted by the extension. No method of storage or transmission provides absolute security.
18
Processing locations
The current hosted portal is deployed in AWS’s Sydney region. Email, analytics and other service providers may process information in the United States and other countries. Processing locations and applicable safeguards depend on the service, provider and organisation agreement. Contact us for the arrangements that apply to your organisation.
19
Children
The service is organisation software and is not directed to children. Submitted text can include information about other people, so organisations must address any applicable children’s privacy requirements in their deployment and collection practices.
20
Changes to this policy
We publish changes on this page with a revised date. Material changes to collection or use will also be communicated through the extension or portal, with additional notice or consent where required.
21
Contact us
For a privacy question, request or complaint, email privacy@promptective.ai or use the privacy contact form below.