Pilot terms and agreement status
A draft pilot agreement with processing terms has been prepared for counsel review. It has not been reviewed by counsel, agreed or signed, and it must be reviewed and agreed before any enrollment.
The pilot observes activity and records findings and would-be policy outcomes without policy-driven blocking, redaction, quarantine, revocation, delivery holds, or workflow interruption. Authentication, authorization, tenant isolation, privacy, and retention controls still apply.
An audit-only description on this website does not configure or verify a backend deployment. Agree and verify the operating mode and handling controls before placing customer data on a path.
- Pilot agreement
- The written pilot scope, support responsibilities and term. The guided pilot is free; manual invoicing applies to paid conversion. Draft prepared for counsel review; not reviewed by counsel, agreed or signed. Must be reviewed and agreed before any enrollment. Enrollment. No device is enrolled before the agreement is reviewed and signed.
- Data processing addendum
- The processing terms: purpose limitation, confidentiality and personnel, subprocessor flow-down and notice, return and destruction, incident notification inside your own reporting clock, and a right to audit. Internal draft only; not counsel-reviewed or available as approved terms. Enrollment until the processing terms are reviewed and agreed.
Contact data and request records
Email to support@redactwall.com sends your address, message and any attachments to Microsoft 365 for support and pilot inquiries. Only the owner, Eric, has access to that mailbox: its access list was verified on 2026-09-25, with no delegates, send-as grants or forwarding.
When identity-based requests are enabled, Auth0 handles verification and keeps authentication logs. RedactWall records your verified email, identity-provider and account references, a request identifier and timestamps. Authorized RedactWall employees review the contact and request; approval and setup status are recorded separately. Verification does not grant pilot access.
Contact records follow a retention schedule adopted on 2026-09-25, not yet reviewed by counsel. Support and pilot-inquiry email is deleted 24 months after receipt, enforced by an Exchange Online retention policy applied on 2026-09-25; the oldest message was received on 2026-08-24, so none reaches that age before 2028-08. A deleted message is then purged after Exchange's recoverable-items window. Auth0 keeps its own authentication logs for 1 to 30 days by plan; the plan on this tenant was not read back. Our streamed copy of those logs is deleted after 365 days by an enforced retention setting. Auth0 identities with no workspace and no sign-in for 24 months are removed at a quarterly review. Pilot request, requester, contact and approval records in the platform database have no deletion today: the database refuses to delete them because they anchor the identity audit chain, so they are kept for the life of the service. A backup set expires about 9 weeks after it is superseded, but new backups keep capturing the retained database records. Requests about your own data are answered within 30 days. The employee activity and training retention periods do not cover these records.
For an initial email, use your work email address and ask about the status of the pilot terms. Keep organization and workflow details, customer records, credentials, prompt contents and attachments out of the initial message.
Inspection and agreed scope
Processing depends on the exact sources and paths agreed for your organization. The following recorded handling descriptions define distinct inspection paths; neither a website illustration nor an account request proves live compatibility.
Typed or pasted text in the ChatGPT composer
The browser path is limited to typed or pasted text in the standard signed-in ChatGPT composer, in an enrolled browser profile on managed Windows 11 with Chrome. Managed installation and composer interception still require verification on a managed endpoint before enrollment. The extension decides locally and posts a content-free signed event; it does not proxy what the page sends.
An explicitly routed Anthropic gateway application
An application explicitly configured to route through the Anthropic hosted gateway is a separate path and requires independent verification. Its requests and responses are inspected before forwarding only when they use that route. Direct provider traffic remains outside it. The dated gateway proof does not establish current release readiness or browser coverage.
Outside the first pilot: the Windows sensor and other endpoint components; files, images, voice, alternative ChatGPT modes and browser responses; Edge, BYOD and other apps. Cloud drive inspection, outbound-mail inspection, MCP tool-call inspection and other gateway providers are also outside this first pilot scope.
Storage and retention
The audit record
The audit record stores decision metadata, including the kinds of finding and the action taken, rather than prompt bodies.
The employee activity store
Employee activity can retain encrypted content under separate access and retention controls. Content access is role controlled and reads are audited. These are two different stores, and this page does not blur them into one answer.
Evidence you send to your own systems
Evidence delivered to a SIEM, a ticketing system, a chat channel or a mail digest carries decision records, not content.
Raw content excluded from evidence and holds
Durable custody of raw content is not implemented for evidence or holds. For durable evidence, the commercial disclosure schema fixes raw content retention at 0 days, and the two evidence capabilities that would need it stay refused pending a threat model, an encryption design and a retention policy that nobody has approved. This evidence limit does not govern the separate employee activity store described above.
Hosted logs and traces
Content sent to the inspection service is processed in memory for the length of the decision. Raw content is not written to hosted logs, traces or error bodies: content-bearing fields use non-loggable types, and errors are sanitized before they leave the process. Automated privacy gates in the product repository fail its build when a hosted binary reaches a path that would break that boundary.
- Decision metadata in the audit record is kept for the audit period stated in your agreement.
- A separate employee activity store can retain encrypted content after mandatory hard-stop values are removed. Content access is role controlled and reads are audited. Operational retention defaults to 30 days, with a maximum of 90 days.
- Samples eligible for training remain subject to their ordinary retention period of 365 days.
Departure and deletion
Return and destruction at the end of a pilot is a drafted contractual obligation, not a product feature. There is no mechanism today that issues a destruction certificate, and this page does not claim one. Destruction at the end of a pilot cannot be certified today, and pilot request, requester, contact and approval records are kept for the life of the service.
Consent and learning
The training policy requires explicit opt-in before future customer data is collected for training. Legacy samples are excluded from training until their rights are reviewed; they remain subject to their ordinary retention period of 365 days.
Pilot observation does not authorize learning from customer content. Source rights, purpose, approved access, and withdrawal requirements apply separately.
The opt-in policy is merged to the product main branch and shipped in release 0.1.12, which was installed on production on 2026-09-24. The live collection path has not been independently exercised, so this page does not claim that collection is already disabled in the live service. Do not use customer data until applicable terms have been reviewed and agreed.
Subprocessors and services
These are the services RedactWall itself buys and runs the pilot on. Each is listed with what it does for us and where it runs. The pilot service has not yet processed customer content, so this list is the standing disclosure of who would process what rather than a record of processing that has already happened. Processing commitments must be reviewed and agreed in writing before any enrollment; the pilot agreement is a draft for counsel review, and there is no executed pilot agreement today.
Recorded service review: 2026-09-25. Reviewed annually, and restated on every change to this list.
Amazon Web Services: S3 and CloudFront
- Purpose:
- Stores and delivers this marketing site. It holds published pages and no customer data.
- Location:
- Origin bucket in AWS US East (Ohio), us-east-2. CloudFront serves from its global edge locations, and its certificate is issued in AWS US East (N. Virginia), us-east-1, because CloudFront accepts one only from that Region.
- Recorded status:
- In service. This is the only entry on the list serving today that a reader can check from where they are sitting: it is delivering this page.
Amazon Web Services: EC2 and EBS
- Purpose:
- Is where the console, the API, the AI gateway and the mail relay are deployed, together with the PostgreSQL databases that would hold the audit record and the employee activity store. Volumes are encrypted with a customer-managed KMS key chosen when the volume is created.
- Location:
- AWS US East (Ohio), us-east-2.
- Recorded status:
- In service since August 2026: the production cell runs on one instance with both databases, and holds requester and operator identities and pilot requests. Its location was verified against the running account on 2026-09-25. Not claimed as processing customer content: no customer device is enrolled, so no employee AI activity or member content has been inspected or stored.
Amazon Web Services: SES and CloudWatch
- Purpose:
- Delivers transactional sign-in and notification email, and records aggregate delivery metrics. Open, click and subscription events are deliberately not published, so those metrics carry no recipient-level payload.
- Location:
- AWS US East (Ohio), us-east-2.
- Recorded status:
- In service for pilot and workspace notification email and for relaying Auth0 sign-in email; the notice record we keep carries no address or body. No production mail server has submitted to the outbound mail relay in any recorded observation. SES handles each recipient address and message in transit.
Auth0
- Purpose:
- Runs the only sign-in interface. It receives the account email address and keeps its own authentication logs. RedactWall requests an identity token only, calls no Auth0 API and holds no client secret.
- Location:
- Auth0 tenant redactwall, United States region.
- Recorded status:
- In service for operator sign-ins and the pilot-request identity flow, on a tenant the infrastructure record tags DEVELOPMENT rather than production. Sign-in by work email was observed live on 2026-08-25. A requester can create their own identity before approval; no customer device has been enrolled. That does not establish whether a prospective requester email has reached Auth0.
Porkbun
- Purpose:
- Registers the domain and answers authoritative DNS. It receives no customer content.
- Location:
- Not recorded. Every infrastructure record naming the registrar names it as the registrar and authoritative DNS and nothing else, so no jurisdiction has been checked, and naming one would be worse than saying so.
- Recorded status:
- In service.
Microsoft 365
- Purpose:
- Email to support@redactwall.com sends your address, message and any attachments to Microsoft 365 for support and pilot inquiries. Only the owner, Eric, has access to that mailbox: its access list was verified on 2026-09-25, with no delegates, send-as grants or forwarding.
- Location:
- Not read back from the tenant. Exchange server naming indicates North America; that is an inference, not a verified location.
- Recorded status:
- In service for support and pilot inquiries through the published mailbox, whose access list was verified on 2026-09-25. Prospective requesters may also provide a work email to Auth0 for sign-in; Microsoft 365 is not the only service that may receive information from outside the company.
Providers selected by your organization
Model providers you select are reached under your own contract with that provider, and are not RedactWall subprocessors. This table covers the broader product catalog. Only the ChatGPT text path and separately verified Anthropic gateway path described in the pilot privacy notice are in the proposed first pilot.
- Your model provider: Anthropic, an OpenAI-compatible provider, Google Gemini or Amazon Bedrock The AI gateway, for compatible applications you explicitly configure to route through RedactWall. The request your application was already sending, after our decision, and the response coming back. Contract: Yours, with that provider.
- Microsoft Graph and Google Drive The cloud drive connector, under your own OAuth credential. Read requests only. The connector reads from them and writes nothing, against a closed host allowlist, following no redirects. Contract: Yours, with Microsoft or Google.
- Your next-hop mail server The outbound mail relay. The message you were already sending. Contract: Yours.
- Your evidence destinations: SIEM, ticketing, chat and mail digest The evidence worker. Decision records, not content. Contract: Yours.
The current draft proposes 30 days of notice before a new subprocessor begins processing. That clause has not been reviewed by counsel; any notice obligation must be agreed before enrollment.
No RedactWall-operated component sends your content to a model provider for our own processing. If that ever changes, that provider becomes a subprocessor of ours and appears here before it is used.
Commercial terms
Paid use is $8 USD, per seat, per month. A paid seat is the licensed quantity agreed in your order. Licensed quantity, allocated capacity, and pilot device allowance are separate. A RedactWall employee confirms the quantity and terms before billing. The site does not take payment.
Manual invoicing is the default. Card payment is offered only where the console deployment is configured for it; the recorded integration runs in test mode. No website change alters invoices, payment-provider prices, or backend metering.
Pricing and conversionGood-faith security research
Test only your own account and data, avoid service disruption, and report findings through the security reporting path. We will not pursue legal action for good-faith research that follows these boundaries. No NDA is required to submit a report.
Security reporting and testing boundariesUpdates and questions
This notice is restated on every change to what the product inspects, stores or retains, and reviewed annually regardless.
Contact RedactWall about handling terms